INTEGRATION
TRANSACTION ASSURANCE
CHARGES
DISPUTES & FRAUD
Sandbox
The sandbox environment is a controlled and simulated environment that allows clients to test and validate their integrations. Developers can use the sandbox to simulate various scenarios and test different functionalities of their applications. This includes testing data inputs, processing logic, error handling, and other critical integration aspects.
Replication of Production Environment
The primary purpose of the sandbox is to mimic the production environment as closely as possible, enabling clients to identify and resolve any issues or bugs without affecting genuine users and data.
The sandbox environment replicates the key components and configurations of the production environment. This includes APIs, service configurations, and other dependencies to closely mimic the real-world scenario in which the integration will operate.
The sandbox environment is isolated from the live system, ensuring that any tests or experiments conducted within the sandbox do not impact the actual production environment. This isolation provides a safe space to make changes and troubleshoot without risking disruption to live services.
AVS and CVC test scenarios
AVS and CVC response result codes in the sandbox can be triggered. The values can be found in the authorizationIsoFields.networkSpecificFields
object in the charge response where the responses are presented as follows:
avsResultCode
(Visa) andavsResponse
(Mastercard)cvv2ResultCode
(Visa) andcvcResult
(Mastercard).
The following cards can be used to complete the testing:
Mastercard: 5412332469619927
Visa: 4796089999934950
Below is an overview listing the amounts that can be used to trigger the various AVS and CVC response codes:
Amount | Mastercard | Visa |
1000 | AVS - A | AVS - Y |
2000 | AVS - N | AVS - N |
3000 | AVS - R | AVS - A |
4000 | AVS - W | AVS - Z |
5000 | AVS - X | AVS - R |
6000 | AVS - Y | AVS - U |
7000 | AVS - Z | CVV - M |
8000 | CVC - M | CVV - N |
9000 | CVC - N | CVV - P |
10000 | CVC - P | CVV - S |
11000 | CVC - U | CVV - U |
Partial Approval Test Scenario
Send a charge request with allowPartialApproval
set to true and the amount equal to 1010:
To verify that the payment is partially approved, check the amount.value
. The value in the response is smaller than the original requested amount, and the issuer response code is 10.
The merchant shall be able to display to the cardholder that this request is partially approved and offer other means for the rest of the payment. If the cardholder does not agree, the merchant can reverse this transaction.
Trigger Scenarios based on Amount
The sandbox does not restrict what cards can be used on all charges endpoints, including card-present.
Only a limited set of pre-configured test cards are supported for the 3DS endpoints, as shown in the table.
A variety of transaction flow scenarios can be triggered based on the amount submitted in the amount.value
field in the request body on the /charges endpoints.
Visa
|
| Endpoint |
1005 | 05 |
|
1010 | 10 |
|
1014 | 14 |
|
1030 | 30 |
|
1051 | 51 |
|
1055 & | 55 |
|
1065 | 65 |
|
1075 | 75 |
|
1085 | 85 |
|
1091 | 91 |
|
Mastercard
|
| Endpoint |
1005 | 05 |
|
1010 | 10 |
|
1014 | 14 |
|
1030 | 30 |
|
1051 | 51 |
|
1055 & | 55 |
|
1065 | 65 |
|
1565 | 65 |
|
20.65 & | 65 |
|
1075 | 75 |
|
1085 | 85 |
|
10.87 | 87 |
|
10.91 | 91 |
|
Pre-configured test cards
The cards in the following table can be used in the sandbox and have certain pre-configured countries and supported 3DS versions to aid in several 3DS testing scenarios.
Network | Card Number | CVC | AVS Required | CVC Required | EEA | 3DS | Card Country |
---|---|---|---|---|---|---|---|
Mastercard | 5413530000000501 | 196 | No | Yes | Yes | 2.1 | BELGIUM |
Mastercard | 5413530000000402 | 196 | No | Yes | Yes | 2.2 | BELGIUM |
Mastercard | 5413530000000303 | 196 | Yes | Yes | Yes | 2.2 | BELGIUM |
Mastercard | 5286940020000304 | 196 | No | Yes | No | None | USA |
Mastercard | 5286940020000205 | 196 | No | No | No | None | USA |
Mastercard | 5286940020000106 | 196 | Yes | Yes | No | None | USA |
Mastercard | 5286940020000007 | 196 | Yes | No | No | None | USA |
Mastercard | 5286940020000908 | 196 | No | Yes | No | 2.1 | USA |
Mastercard | 5286940020000809 | 196 | No | Yes | No | 2.2 | USA |
Visa | 4200350000000801 | 196 | No | Yes | Yes | 2.1 | GERMANY |
Visa | 4200350000000702 | 196 | No | Yes | Yes | 2.2 | GERMANY |
Visa | 4200350000000603 | 196 | Yes | Yes | Yes | 2.2 | GERMANY |
Visa | 4761070000000004 | 196 | No | Yes | No | None | USA |
Visa | 4761070000000905 | 196 | No | No | No | None | USA |
Visa | 4761070000000806 | 196 | Yes | Yes | No | None | USA |
Visa | 4761070000000707 | 196 | Yes | No | No | None | USA |
Visa | 4761070000000608 | 196 | No | Yes | No | 2.1 | USA |
Visa | 4761070000000509 | 196 | No | Yes | No | 2.2 | USA |
Bancontact | 2952000000000038 | N/A | No | No | Yes | 2.2 | BELGIUM |
Test cards supporting 3DS method URL
Network | Card Number |
---|---|
Mastercard | 5520330000002233 |
Visa | 4635440000002233 |
Bancontact | 2952000000000039 |