To start using the SNAP version of Payouts, merchants will first need to do credentials exchange with Midtrans. To do this, merchants need to prepare and submit the following items as part of the onboarding process.
| No. | Items to prepare | Definition |
|---|---|---|
| 1 | Merchant's public and private key | Merchant needs to create their public and private key for signature generation that will be used when calling Access Token API. Notes: 1. Public key is merchant’s key that will be shared with Midtrans for signature decryption purpose 2. Private key is merchant’s confidential key that will be saved on merchant’s side |
| 2 | Merchant’s outgoing IP | Merchant’s IP that will be whitelisted on Midtrans side. Only shared IP will be allowed to call Midtrans’ API |
| 3 | Merchant ID (MID) | Merchant needs to complete registration on midtrans.com to acquire Merchant ID. Merchant can use an existing MID if wishes to. |
Midtrans will then share the following items for merchant to store and use when calling Midtrans' API.
| No. | Items provided by Midtrans | Definition |
|---|---|---|
| 1 | Client ID | Merchant’s client ID that will be given by Midtrans, will be used as X-CLIENT-KEY on request’s header in B2B Access Token API |
| 2 | Client Secret | Merchant’s secret key that will be given by Midtrans, will be used for symmetric signature generation for API’s header |
| 3 | Partner ID | Merchant’s partner ID that will be given by Midtrans, will be used as X-PARTNER-ID on API’s header |
| 4 | Channel ID | Static value given by Midtrans, will be used as CHANNEL-ID on API's header |