To start using the BI-SNAP version of QoinHub API, merchants will first need to do credentials exchange with QoinHub. To do this, merchants need to prepare and submit the following items as part of the onboarding process.
| No | Item to prepare | Definition |
|---|---|---|
| 1 | Merchant public and private key | Merchant needs to create their public and private key (generated using PKCS8 standard) 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 QoinHub for signature decryption purpose. 2. Private key is merchant’s confidential key that will be saved on merchant’s side |
| 2 | Merchant Redirect Finish URL | Merchant needs to share the redirection URL that will be used as redirection Finish URL. |
| 3 | Merchant outgoing IP | Merchant’s IP that will be whitelisted on QoinHub side. Only shared IP will be allowed to call QoinHub API |
| 4 | Merchant Callback Notification Required if merchant consumed notification from QoinHub | QoinHub will send payment notification to the merchant callback notification URL shared by merchants |
| 5 | Merchant Code | Merchant needs to complete registration on Qoinhub.id to acquire Merchant ID. |
QoinHub will then share the following items for merchant to store and use when calling QoinHub API.
| No | Items provided by QoinHub | Definition |
|---|---|---|
| 1 | QoinHub public key Required if merchant consumed notification from QoinHub | QoinHub will share its public key to merchant. By using QoinHub public key, merchant will be able to decrypt signature that is sent from QoinHub when calling merchant’s notification endpoint |
| 2 | QoinHub outgoing IP | QoinHub IP that merchant needs to whitelist to receive notification from QoinHub Staging: 115.85.90.156 115.85.82.120 Production: 115.85.90.227 115.85.82.120 |