1. How do we get the integration kit for Payment Gateway?
Once the merchant is onboarded on the payment gateway successfully, the bank will be sharing the integration kit for payment gateway integration.
2. What will be available in the integration kit?
- Integration document
- Tranportal ID – ID for connecting the payment gateway
- Tranportal password – Password for validating the merchant
- Resource/Encryption Key – Used for encryption and decryption of data during data transmission between the Payment Gateway and Merchant
- Tranportal password – Password for validating the merchant
- Tranportal ID – ID for connecting the payment gateway
3. Where will Tranportal ID, Password and Resource/Encryption Key be configured?
During terminal onboarding in Payment Gateway, all the information will be configured in the application.
4. What are the mandatory parameters that need to be shared during a transaction to ensure successful processing?
In each request, we need to share trandata and tranportal ID. Refer to the above list of request session.
5. What is the format of the amount?
Amount format will be in 2 decimals format.
6. What is the format of Track ID field?
Track ID will be in Alphanumeric characters. Refer to the section of the tabular data of field for more clarification.
7. What are the special characters that are not allowed in the Track ID field?
No special character is allowed in the system.
8. What is the minimum android version supported?
SDK supports Android 7.0 (API 24) and above.
9. How will the merchant application receive the transaction response?
SDK will return results in callback method.
10. How does merchant update the SDK?
SDK will be provided in .aar file format. Merchant will be provided with the updated file and merchant can upload the .aar file in their mobile application.
11. Does SDK store sensitive information?
SDK doesn't store any sensitive information like card numbers, user id, password, and any credentials.
12. Which are the test cards I can use for transactions on Test environment?
Replace X with 0 and Y with 1. You may try using any future date as expiry.
| Card Brand | Purpose | Card Number | 3DS2 Enrolled | Expiry | CVV |
|---|---|---|---|---|---|
| Mastercard | Challenge | 512345XXXXXXXXXX8 | Yes | 01/39 | 123 |
| 2223XXXXXXXXXXX7 | Yes | 01/39 | 123 | ||
| 52XXXX XX XXXX 2151 | Yes | 01/39 | 123 | ||
| Frictionless | 5123456789X12346 | Yes | 01/39 | 123 | |
| Frictionless | 5555555555XXXX18 | Yes | 01/39 | 123 | |
| Authentication Attempted | 55XXXX5555555559 | Yes | 01/39 | 123 | |
| Authentication Rejected | 55069XX1401XX503 | Yes | 01/39 | 123 | |
| Error during INITIATE AUTHENTICATION operation resulting in Generic Error Response | 521X76XX0000004 | Exception | 01/39 | 123 | |
| Error during AUTHENTICATE PAYER operation resulting in Generic Error Response | 5455X31257390496 | Yes | 01/39 | 123 | |
| 5455X31252665454 | Yes | 01/39 | 123 | ||
| Not Enrolled Response | 5YYYY1111111118 | No | 01/39 | 123 | |
| 2223XX0000000023 | No | 01/39 | 123 | ||
| Authentication Unavailable Error during Authenticate Payer operation resulting in a response of authenticationStatus = AUTHENTICATION_UNAVAILABLE | 5X2345999999822X | Yes | 01/39 | 123 | |
| Visa | Challenge | 44400000099XXX10 | Yes | 01/39 | 123 |
| 4XXXXXXXXXXX2503 | Yes | 01/39 | 123 | ||
| Frictionless | 44400000422XXX14 | Yes | 01/39 | 123 | |
| Authentication Attempted | 44400000422XXX22 | Yes | 01/39 | 123 | |
| American Express | Challenge | 3400000999XXX51 | Yes | 01/39 | 123 |
| Frictionless | 34035327808X9XX | Yes | 01/39 | 123 |