Your API credentials
You find your credentials in the merchant dashboard under Developer Tools → Credentials. Each credential has one specific job:Rotating your keys
If you suspect your Client Secret has been exposed, click Rotate Keys on the Credentials page. This generates a new Client Secret (and a new HMAC Validation Key) and immediately invalidates every existing access token. After you rotate:- Replace the Client Secret in your server configuration.
- Request a new access token.
- Validate incoming webhooks with the new Client Secret.
Obtain an access token
Request a JWT access token using your Client ID, API Key, and Client Secret from the merchant dashboard. Request a token usingPOST /api/v1.1/access-token/b2b, listed under Security in the API reference sidebar (OpenAPI-generated endpoint page).
Older integrations can still use
POST /api/v1.0/access-token/b2b, which takes an Authorization: Basic {base64(client_id:client_secret)} header instead of X-CLIENT-ID and X-Signature.Token request headers
Token request body
The response includes a Bearer token and expiry time. Request a new token before the current one expires.
Authenticated API requests
Include these headers on every REST API call after you obtain a token:Signed requests (selected endpoints)
Some money-out operations require additional headers for request signing:
Endpoints that typically require signing include:
- Disbursement transfer (
POST /api/v2.0/disbursement/transfer) - QRIS issuer payment credit and related money-out flows
- E-Wallet trigger top-up (
POST /api/v2.0/ewallet/trigger-topup)
IP whitelist
Merchant API routes may require your server IP to be registered on the merchant account before requests are accepted. Configure allowed IPs in the merchant dashboard before going to production.Environments
Use Sandbox for development and testing. No real money moves in Sandbox.
