The API
Below are the API endpoints use to perform both PAC and PMC transaction,
The API definition for both PAC and PMC is same and below,
Header
Parameter | Type | Description |
---|---|---|
Content-Type | String | Use value 'application/json' |
Accept | String | Use value 'application/json' |
x-api-version | String | Use value 1 |
Key | String | API key |
Parameters
Field | Type | Required | Description |
---|---|---|---|
money | Object | true | The Object containing two String attributes: amount and currency of the transfer |
description | String | Optional | Description for this transfer which min character is 1 and max characters are 25 |
expiryDate | String | true | Card expiry date |
sourceAccount | String | true | Account number from which the amount of money will be debited |
traceId | String | true | Unique transaction identifier. You can assign any value |
cardNumber | String | true | Card number. Your business contact can provide more test numbers
|
cardHolderCountryCode | String | true | Card holder country code (ISO 3166-1) |
cardHolderNationality | String | true | Card holder nationality (ISO 3166-1) |
cardHolderAddress | String | Optional | Card holder address |
cardName | String | true | Name on card |
cardHolderEmail | String | Optional | Card holder email (this is required by our processors) |
dob | String | true | Date of birth of the card holder. Format: YYYY-MM-DD |
cardHolderStreet | String | Conditional | Mandatory when card holder country code is either Canada (CA) or United States(US) |
cardHolderCity | String | Conditional | Mandatory when card holder city is either Canada (CA) or United States(US) |
cardHolderState | String | Conditional | Mandatory when card holder state is either Canada (CA) or United States(US) |
money
Field | Type | Required | Description |
---|---|---|---|
amount | Number | true | Transaction value |
currency | String | true | Currency code (ISO 4217) |
There are some edge case scenarios in which the system might not provide a timely response to an API payment request. In the event that you receive a timeout when sending the request, do NOT assume that the transaction is failed. In such cases, you can safely retry the transaction using the SAME traceID, and if the transaction was initially received, then the API will return a duplicate request error. In case it wasn't initially received, the request would be consumed accordingly.
If in any doubt, please reach out to our support team or send an email to [email protected].
Updated 16 days ago