Where to find your keys
Open the Developer section of the EximPe Dashboard. You get:- Client ID
- Client Secret
Environments
Build and test against sandbox. Nothing there moves real money, and you can simulate an incoming transfer instead of making one.
Headers on every call
Which calls take
X-Merchant-ID. A PSP sends it on the calls that name a sub-merchant before there is a payment to read one from — POST /pg/orders/, POST /pg/vba/, POST /pg/lrs/*, POST /pg/payment-links/ and the rest of the create routes. The /pg/payments/<id>/… routes — verification, document upload, settlement submit — derive the sub-merchant from the payment itself.X-API-Version is not a credential. If you omit it, the call still succeeds and the response echoes your account’s default version. Send 3.0.0 explicitly.Keep your Client Secret on your server. It is not safe in a browser or a mobile app.
If you are a PSP
You call the API on behalf of the businesses you onboard, so there is one extra step before your first call.1
Add the merchant
In sandbox a dummy merchant is created for you at signup. Otherwise see Adding Merchants.
2
Wait for activation
Sandbox activates instantly. In production it follows due diligence under RBI rules.
3
Use their merchant ID
Once active you get a
merchant_id. Send it as X-Merchant-ID on the calls that ask for it, as above.A PSP cannot collect for a sub-merchant until that sub-merchant is active.