Sandbox Environment
Sign up for your Judopay Sandbox Account
You need your sandbox account so you can process test transactions while developing your app.
Updates are released to our sandbox environment on a regular basis. Continually test your app to ensure your integration is working with the latest updates, mirroring the live environment.
Purpose of the Sandbox
The purpose of the sandbox environment is to allow you to test and replicate various use cases, payment flows and scenarios that your app should support.
Use the test cards and data to test your integration is working correctly. This will give you confidence that all is working as expected when your integration goes live.
Limitations Within the Sandbox Environment
There are some limitations within the sandbox environment to be considered:
-
Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens.
-
If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.
-
Contact Customer Support to set this up.
-
Sandbox Endpoints
Target endpoint: https://api-sandbox.judopay.com/...
Sandbox Tokens
Ensure Judopay has enabled 3D Secure in your sandbox account. If this is not enabled the test transaction may appear successful without following the correct payment flow.
Contact Customer Support to set this up.
Tokens can be used for different configurations.
For example:
-
3D Secure transactions
-
Non 3D Secure transactions
-
Moto transactions
-
Ecom transactions
-
CV2 transactions
-
Non CV2 transactions
Only sandbox API tokens will work in the sandbox, if you use live tokens in the sandbox environment, it will result in an authorisation failure.
To get your sandbox tokens, sign up for your sandbox account.
Functional and Load Testing
Judopay’s sandbox environment accommodates functional testing of your integration and is not designed for load or stress testing scenarios.
Due to lower rate limits applied in sandbox, we recommend simulating test requests with a prudent level of latency applied.
When you change environments, remember to use the correct API Token and API Secret for that environment.
Using the wrong tokens and secrets will result in an authorisation failure.
Test Cards
To test transactions, use the test cards in the Judopay Portal to process transactions in the sandbox environment.
The test cards will behave as valid cards and will only work in the sandbox.
Below are details of test card data that can be used when integrating with the Gateway.
Please note that ONLY these card details will work in test mode – real card numbers will NOT work.
Test Case |
Card Result* |
Card Enrolled for 3D Secure? |
Description |
---|---|---|---|
1 |
Authorised |
Yes |
For cards that are 3D Secure enrolled and will be authorised. They still might be declined by the AVS/CV2 checks, or if the 3D Secure password is incorrect. |
2 |
Declined |
Yes |
For cards that are 3D Secure enrolled. They will always result in the authorisation being declined, even if they pass the AVS/CV2 or 3D Secure checks. |
3 |
Referred |
Yes |
For cards that are 3D Secure enrolled. They will always result in the authorisation being referred, even if they pass the AVS/CV2 or 3D Secure checks. |
*This is the authorisation phase result – the ultimate result of whether the transaction is accepted or declined can still be influenced by the:
-
CV2
-
Address data
-
3D Secure
result that is submitted with the transaction.
For example: Test Case - Authorisation Successful without 3D Secure 2: (based on your account’s AVS/CV2 policies), the transaction can still be declined if an incorrect CV2 is submitted.
Test Case - Card Abbreviation Keys:
Card Abbreviation |
Card Type |
---|---|
VC |
Visa |
VD |
Visa Debit (Delta) |
MA |
Maestro |
MC |
MasterCard |
EL |
Visa Electron |
VP |
Visa Purchasing (Corporate) |
AM |
American Express |
JCB |
JCB |
Authorisation Successful without 3D Secure 2
For these test cards:
-
Use sandbox tokens that are not enabled for 3DS2.
-
Supply any value for the card name, for example Adam Smith.
To trigger specific 3D Secure 2 user journeys, see Testing 3D Secure 2 Payment Flows.
Card Type |
Card Number |
Expiry Date |
CV2 |
Address |
---|---|---|---|---|
Visa |
4976 0000 0000 3436 |
12/25 |
452 |
32 Mulberry Street, Eastfort, Violetdell VL14 8PA |
Visa |
4921 8100 0000 5462 |
12/25 |
441 |
11 Jackson Close, Stoneden, Wildefay WL2 7DQ |
Mastercard |
5100 0000 0000 5460 |
12/25 |
524 |
22 Victoria Court, Newwell, Stonehill ST20 5EJ |
Visa Electron |
4508 7500 0000 5461 |
12/25 |
568 |
29 Front Street, Aelfield, Summermoor SU21 5QP |
Visa Purchasing |
4001 6580 3548 6204 |
12/25 |
234 |
18 Hamilton Road, Goldspring, Starrymarsh ST4 5QN |
Maestro |
6759 0000 0000 5462 |
12/25 |
789 |
7 Woodland Avenue, Aldfog, Brightpine BR4 8NL |
Amex |
3400 0043 2128 428 |
12/25 |
3469 |
45 Augusta Drive, Mallowsnow, Wayholt WA6 7BB |
JCB
You can use any start date for JCB cards. |
3528 0080 3548 6208 |
12/25 |
135 |
32 Pennsylvania Avenue, Lorwynne, Newbutter NB34 4EH |
Authorisation Declined without 3D Secure 2
For these test cards:
-
Use sandbox tokens that are not enabled for 3DS2.
-
Supply any value for the card name, for example Adam Smith.
To trigger specific 3D Secure 2 user journeys, see Testing 3D Secure 2 Payment Flows.
Card Type |
Card Number |
Expiry Date |
CV2 |
Address |
---|---|---|---|---|
Visa |
4221690000004963 |
12/25 |
125 |
274 Grove Street, Rayvale, Vertland VT22 6JN |
Visa |
4921810000009076 |
12/25 |
875 |
4 Laurel Drive, Prywynne, Swynbeach SY7 0JB |
Maestro |
6759000000009076 |
12/25 |
671 |
39 Virginia Street, Crystaldell, Stoneshore SS14 3AL |
Mastercard |
5100000000009074 |
12/25 |
915 |
288 Cottage Street, Glassden, Merrowville ME5 7AJ |
Electron |
4508750000009075 |
12/25 |
025 |
20 Adams Avenue, Redice, Courtmere CM13 7AN |
Visa Purchasing |
4001651503580749 |
12/25 |
089 |
22 Colonial Avenue, Havenhollow, Winterfield WF6 1RP |
Amex |
340000150358074 |
12/25 |
7654 |
334 Dogwood Drive, Faydeer, Lightpond LP1 1BH |
JCB
You can use any start date for JCB cards. |
3528001503580743 |
12/25 |
349 |
100 Willow Lane, Whitehill, Ashmarsh AM4 2BL |
Authorisation Referred without 3D Secure 2
For these test cards:
-
Use sandbox tokens that are not enabled for 3DS2.
-
Supply any value for the card name, for example Adam Smith.
To trigger specific 3D Secure 2 user journeys, see Testing 3D Secure 2 Payment Flows.
Card Type |
Card Number |
Expiry Date |
CV2 |
Address |
---|---|---|---|---|
Visa |
4792840000009202 |
12/25 |
654 |
9 Pearl Street, Dracmeadow, Byhedge BH11 9BB |
Visa |
4921810000005850 |
12/25 |
217 |
54 Madison Avenue, Aldapple, Rayland RL5 0HA |
Maestro |
6759000000005850 |
12/25 |
458 |
11 Magnolia Drive, Aldmallow, Janlake JL16 7UD |
Mastercard |
5100000000005858 |
12/25 |
844 |
17 Fairway Drive, Whitewall, Coldlea CL2 7QH |
Electron |
4508750000005859 |
12/25 |
751 |
24 Schoolhouse Lane, Dorhedge, Shadowfay SF20 6AS |
Visa Purchasing |
4001655504826456 |
12/25 |
454 |
32 Hillside Drive, Icemill, Vertgold VG7 9QF |
Amex |
340000550482649 |
12/25 |
3674 |
671 Franklin Court, Summercourt, Morhollow MH19 5DE |
JCB
You can use any start date for JCB cards. |
3528005504826450 |
12/20 |
454 |
678 Devon Court, Corlake, Lormarsh LM14 1RZ |
Related Topics