Quick-Start Checklist

Complete every step below before making your first live API call.

Step 1 — Get Your Credentials

Contact your Centiwise account manager to receive sandbox or production credentials:

Centiwise provide two types of credentials:

1. API credential
2. Dashboard login credential

For API credential, you have two specify the currency, card or APM, vertical, type of licencing/Incorporation, Merchant IP for whitelist and for production fees as negotiated with the merchant.

For API credentials we provide:

While for Dashboard login credentials we provide:

• Dashboard url

• Admin Username

• Admin Password

  Never expose credentials in client-side code, logs, or version control.

Step 2 — Store Credentials Securely

Add your credentials to environment variables:

# .env  (add this file to .gitignore)
CENTIWISE_ENDPOINT_ID=your_endpoint_id
CENTIWISE_LOGIN=your_merchant_login
CENTIWISE_CONTROL_KEY=your_control_key

Step 3 — For Deposit use

A. /api/v2/sale

Sale is initiated through HTTPS POST request by using URLs and the parameters specified. Use SHA-1 for authentication. See Statuses.

B. /api/v2/sale-form

Sale-form is initiated through HTTPS POST request by using URLs and the parameters specified below. Use SHA-1 for authentication. See Statuses.

Step 4 — For payout use

A. /api/v4/payout

Payout is initiated through HTTPS POST request by using URLs and the parameters specified below. Use OAuth RSA-SHA256 for authentication.

OAuth RSA-SHA256
To generate request with OAuth RSA-SHA256 authentication:

• Generate Key Pair,
• Generate Signature,
• Generate Headers,
• Generate Request.
• Generating Key Pair

To authorize future requests with RSA-SHA256, generate the key pair:

A PRIVATE key to sign the request. This private key must be kept secret from everyone.

A PUBLIC key to verify that the request was signed with the respective private key. Send it to support manager for it to be updated to your endpointID.

There are two ways to generate the key pair:

Using a Key-Pair-Factory tool - the native cross-platform desktop app.

Using OpenSSL library. - This is easier

Step 5 — Set Up Your Callback Endpoint

If server_callback_url is sent, Payment Gateway sends callback notification only when original transaction receives final status. If notify_url is sent, Payment Gateway sends callback notification once the original transaction receives final status, and about every future update for this original transaction (reversal, chargeback, etc).

Requirements:

• Must return HTTP 200 within 10 seconds
• Must handle duplicate deliveries idempotently
• Must be served over HTTPS (TLS 1.2+)

→ See Webhooks for the full callback specification.

Step 6 — Test in Sandbox

Run end-to-end tests against the sandbox environment before going live. Verify:

• Payin request signs correctly and returns success
• Payout request signs correctly and returns success
• Your callback endpoint receives and acknowledges the webhook
• DECLINED and PROCESSING responses are handled gracefully

Step 7 — Go Live

Switch to your production endpoint_id and remove any sandbox overrides.

→ Review the full Go-Live Checklist before flipping the switch.