For AI agents: the complete documentation index is at /llms.txt, and the full text of every page is at /llms-full.txt. Most pages are also available as Markdown by adding .md to the URL.

Test Case Scenarios

Ready your Integration to go live by running these scenarios.

Overview

This section guides developers through real-world key test-cases and edge-cases they may encounter when integrating with us. By walking through these examples, you will gain a clear understanding of how our APIs behave under normal and boundary conditions. We highly recommend that developers follow these guidelines while building integrations and using these guidelines as part of your internal QA testing before go-live.

In order to determine whether below capabilities suit your business needs and are applicable to your region, please contact your account manager or our sales team for further details.

Test Cards

You may use our simulated credit cards to test different scenarios

When testing your integration, never use real card details or banking information. This is why we provide simulated payment methods including test card numbers that you may use to test different scenarios for your application or website.

Test Card Number	Card Brand	Expiry	CVV	Result
4263970000005262	Visa	05/39	599	Successful transaction
5425230000004415	Mastercard	05/39	599	Successful transaction
374101000000608	American Express	05/39	1234	Successful transaction
36256000000725	Diners Club	05/39	1234	Successful transaction
6011000000000087	Discover	05/39	599	Successful transaction
3566000000000000	JCB	05/39	599	Successful transaction
135400000007187	UATP	05/39	599	Successful transaction

Test Cases

The API Platform's sandbox environment lets you test your integration without needing to make real charges or payments. To make testing easier, we suggest using the below test cases in the specified amount with information available in the API Explorer and Postman Collection.

Simulated Error Scenarios

Transaction Type	Error Message	HTTP Code	Trigger Amount	Test Card Details	Expected Result	Next Step
PREAUTHORIZE TRANSACTION Channel : CNP, CP	Internal Server Error	500	27251	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"SYSTEM_ERROR", "Detailed_error_code":"50001", "detailed_error_description":"Internal Server Error"}	Perform a REVERSAL transaction using the reference number passed in the original transaction
PREAUTHORIZE TRANSACTION Channel : CNP, CP	Internal Server Error	500	27259	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"SYSTEM_ERROR" ,"detailed_error_code":"50001", "detailed_error_description":"Internal Server Error"}	Perform a REVERSAL transaction using the reference number passed in the original transaction
PREAUTHORIZE TRANSACTION Channel : CNP, CP	Bad Gateway	502	27252	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"SYSTEM_ERROR", "Detailed_error_code":"50002", "detailed_error_description":"Bad Gateway"}	Retry the transaction
PREAUTHORIZE TRANSACTION Channel : CNP	Bad Gateway	502	27254	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"SYSTEM_ERROR_DOWNSTREAM", "Detailed_error_code":"50014", "detailed_error_description":"320,3xx,Error with GP Systems"}	Retry the transaction
PREAUTHORIZE TRANSACTION Channel : CNP	Bad Gateway	502	27258	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"ACTION_FAILED", "Detailed_error_code":"50012", "detailed_error_description":"Action failed unexpectedly. An automatic reversal was successful. Please try original transaction again."}	Retry the transaction
PREAUTHORIZE TRANSACTION Channel : CNP	Bad Gateway	502	27260	Visa MasterCard American Express Diners Club Discover JCB	{"error_code":"SYSTEM_ERROR", "Detailed_error_code":"50002", "detailed_error_description":"Bad Gateway"}	Retry the transaction
PREAUTHORIZE TRANSACTION Channel :CP

Access Token

Resource	Postman Reference	Steps / Trigger	Description and Expected Result
Access Token	BASIC ACCESS TOKEN Description : A basic access token is a unique, single-use key that allows access to API actions for a limited time. It is required for every request that creates, edits, or reads resources.	The NONCE value must be generated by the client and should be unique for each request.	A successful request returns a Bearer Token, which must be included in the Authorization header of subsequent API calls.
Access Token	SINGLE PERMISSION ACCESS TOKEN Description : A restricted access token with single permission is used for specific operations such as tokenization, reporting, or other predefined actions for a certain amount of time.	Permissions: Restrict the token by specifying required permissions, for example: "permissions": ["PMT_POST_Create_Single"] Expiration: Limit token validity by setting an interval, for example: "interval_to_expire": "10_MINUTES"	The token is returned as a Bearer Token with single-use permissions. This token can be used for API calls that generate a single-use card token.
Access Token	HANDLE EXPIRED TOKEN Description : This scenario ensures the system can detect an expired access token and automatically issue a new token to continue processing API requests.	Set the access token to expire quickly: "seconds_to_expire": 60 Call the VERIFY API immediately; it should succeed because the token is still valid. Wait 61 seconds and call the VERIFY API again, it should return: "Access token expired" The system should automatically generate a new access token and continue processing requests.	A new Bearer token is issued automatically when the old token expires. Subsequent API calls continue successfully using the newly issued token.

Policies

Connect