3.1 Merchant Application Account
Before merchants start integrating with Offline Payment API, merchants must register an application account with a payment gateway. For every Application Code provided it will have its own secret key. If merchants already have an account then they may skip this step. Payment gateway will provide the account information as below for merchant integration and production processing purposes.
| Type | Remark |
|---|---|
| Application Code | Unique code to identify merchant applications which integrate with Offline Payment API. |
| Secret Key | A server-side shared secret key which will be used to generate signatures for API communication. |
3.2 IP Address Whitelist
This is optional and applicable only for merchants or partners that process huge volumes (more than 10 transactions per second). After the merchant obtains the Offline Payment API account, the merchant is recommended to provide outgoing IP address(es) of the merchant server for whitelisting purposes. This is to ensure only servers authorized by merchants are able to connect to the payment gateway.
3.3 Version
The version represents the functionality or enhancement provided by each iteration. Use the version that best fits your integration.
V1
- Add payment API
- Add inquiry API
- Add reversal API
- Add refund API
- Add precreate API
V2
- Add channelId into the response parameter for all API.
- payment API
- inquiry API
- reversal API
- refund API
- precreate API
- Fix errorCode not included in response signature calculation when reversal failed.
- Fix missing errorCode not included in response when statusCode is 99 for refund API.
- Remove md5 hashing algorithm as an option to generate signatures.
V3
- Adding extraInfo in response for all API.
- Payment API
- Inquiry API
- Reversal API
- Refund API
- Precreate API
V4
- Add metadata in request and response for below API.
- Precreate API
- Payment API