Sandbox Testing
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.
Note
Test all your required payment types in the sandbox environment before going live.
It is advised to generate:
Successful
Declined
Error results.
Sandbox Token and Secret
Each Token and Secret pair will have specific permissions configured.
Tip
Double check these permissions before using the Token and Secret.
From the Judopay Portal:
To view the Sandbox Token and Secret:
![]() |
STEP | DESCRIPTION |
---|---|
![]() | From the side menu, select Your apps Select the app to view the Token and Secret credentials |
![]() | Select Sandbox tokens to see both the Token and Secret for the Sandbox Environment. |
![]() | The Sandbox Token information is displayed. You can: View the Token | Secret | View and Edit Permissions | Disable the token | Add a new Sandbox token |
Note
A live Token and Secret will only be visible within the app once your account is activated.
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.
View Test Cards
From the Judopay Portal:
To view Test Card Details:
![]() |
Step | Description |
---|---|
![]() | From the side menu, select Tools |
![]() | Select Generating transactions |
![]() | The Test Card Details screen appears. Use these Test Card details to generate a successful transaction. |
![]() | Use these Test Card details to generate a declined transaction. |
Tip
If you would like to test CheckCard or Google Pay in the Sandbox, please contact customer support.
Test Scenarios
Successful Payments
To generate a Successful Transaction use the test cards provided in the Judopay Portal
Capture and record the
receipt ID
for this transactionTo support repeat payments (one-click payments) capture the card token | consumer token | consumer reference
Note
All three fields need to be provided in a repeat payment for it to be successful.
Ensure all transactions reach your back-office
Declined Payments
To generate a Declined Payment status for Card Payments | Pre-Authorizations | Repeat Card Payments, use the Test Cards provided in the Judopay Portal
When testing for a Payment Declined status, process transactions with the following variables:
Incorrect CV2 (card security code) values
Incorrect/Invalid dates
Invalid card numbers
For repeat payments, use an incorrect match of card token and consumer reference
Payment Errors
To test an unexpected error occurring during a payment (an upstream error processing a transaction), ensure this is handled by your app or backend (depending on your integration).
One example of a test:
Pass an invalid Token and Secret.
See how your app handles the error.
Test Card Details
Below are details of test card data that can be used when integrating with the Gateway.
Note
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 | No | For cards that are not 3D Secure enrolled and will be authorised. They still might be declined by the AVS/CV2 checks. |
2 | Declined | No | For cards that are not 3D Secure enrolled. They will always result in the authorisation being declined, even if they pass the AVS/CV2 checks. |
3 | Referred | No | For cards that are not 3D Secure enrolled. They will always result in the authorisation being referred, even if they pass the AVS/CV2 checks. |
4 | 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. |
5 | 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. |
6 | 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 1: (based on your account’s AVS/CV2 policies), the transaction can still be declined if an incorrect CV2 is submitted.
Test Case 4: A decline can still be achieved if the 3D Secure result = failed in the ACS simulator.
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 |
Test Case 1
Authorisation Successful with no 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | John Watson | 4976 0000 0000 3436 | 12/25 | 11/20 | 452 | 32 Mulberry Street, Eastfort, Violetdell VL14 8PA |
Visa Debit | James Jackson | 4921 8100 0000 5462 | 12/25 | 11/20 | 441 | 11 Jackson Close, Stoneden, Wildefay WL2 7DQ |
Mastercard | Luke Johns | 5100 0000 0000 5460 | 12/25 | 11/20 | 524 | 22 Victoria Court, Newwell, Stonehill ST20 5EJ |
Visa Electron | Patrick Smith | 4508 7500 0000 5461 | 12/25 | 11/20 | 568 | 29 Front Street, Aelfield, Summermoor SU21 5QP |
Visa Purchasing | Geoff Lewis | 4001 6580 3548 6204 | 12/25 | 11/20 | 234 | 18 Hamilton Road, Goldspring, Starrymarsh ST4 5QN |
Maestro | Paul Taylor | 6759 0000 0000 5462 | 12/25 | 11/20 | 789 | 7 Woodland Avenue, Aldfog, Brightpine BR4 8NL |
Amex | Jake Keaton | 3400 0043 2128 428 | 12/25 | 11/20 | 3469 | 45 Augusta Drive, Mallowsnow, Wayholt WA6 7BB |
JCB | Sam Burton | 3528 0080 3548 6208 | 12/25 | 11/20 | 135 | 32 Pennsylvania Avenue, Lorwynne, Newbutter NB34 4EH |
Test Case 2
Authorisation Declined with no 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | Ian Lee | 4221690000004963 | 12/25 | 11/20 | 125 | 274 Grove Street, Rayvale, Vertland VT22 6JN |
Visa Debit | Jack Lewis | 4921810000009076 | 12/25 | 11/20 | 875 | 4 Laurel Drive, Prywynne, Swynbeach SY7 0JB |
Maestro | Mandy Hunt | 6759000000009076 | 12/25 | 11/20 | 671 | 39 Virginia Street, Crystaldell, Stoneshore SS14 3AL |
Mastercard | Nick Podd | 5100000000009074 | 12/25 | 11/20 | 915 | 288 Cottage Street, Glassden, Merrowville ME5 7AJ |
Electron | Paul Link | 4508750000009075 | 12/25 | 11/20 | 025 | 20 Adams Avenue, Redice, Courtmere CM13 7AN |
Visa Purchasing | Jerry Gough | 4001651503580749 | 12/25 | 11/20 | 089 | 22 Colonial Avenue, Havenhollow, Winterfield WF6 1RP |
Amex | Lee Chase | 340000150358074 | 12/25 | 11/20 | 7654 | 334 Dogwood Drive, Faydeer, Lightpond LP1 1BH |
JCB | Richard MacDonald | 3528001503580743 | 12/25 | 11/20 | 349 | 100 Willow Lane, Whitehill, Ashmarsh AM4 2BL |
Test Case 3
Authorisation Referred with no 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | George Toole | 4792840000009202 | 12/25 | 11/20 | 654 | 9 Pearl Street, Dracmeadow, Byhedge BH11 9BB |
Visa Debit | Peter Long | 4921810000005850 | 12/25 | 11/20 | 217 | 54 Madison Avenue, Aldapple, Rayland RL5 0HA |
Maestro | Henry McBride | 6759000000005850 | 12/25 | 11/20 | 458 | 11 Magnolia Drive, Aldmallow, Janlake JL16 7UD |
Mastercard | Susan Kitchen | 5100000000005858 | 12/25 | 11/20 | 844 | 17 Fairway Drive, Whitewall, Coldlea CL2 7QH |
Electron | Richard Ross | 4508750000005859 | 12/25 | 11/20 | 751 | 24 Schoolhouse Lane, Dorhedge, Shadowfay SF20 6AS |
Visa Purchasing | William Nicolson | 4001655504826456 | 12/25 | 11/20 | 454 | 32 Hillside Drive, Icemill, Vertgold VG7 9QF |
Amex | Kim Hall | 340000550482649 | 12/25 | 11/20 | 3674 | 671 Franklin Court, Summercourt, Morhollow MH19 5DE |
JCB | Patrick Williams | 3528005504826450 | 12/20 | 11/20 | 454 | 678 Devon Court, Corlake, Lormarsh LM14 1RZ |
Test Case 4
Authorisation Successful with 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | Geoff Wayne | 4976 3500 0000 6891 | 12/25 | 11/20 | 341 | 113 Broad Street West, Oldpine, Strongbarrow SB42 1SX |
Visa Debit | James Marshall | 4921 8100 0000 1909 | 12/25 | 11/20 | 642 | 109 Church Street South, Morcoast, Sagebridge SB1 5JZ |
Maestro | Anthony Walker | 6759 0000 0000 1909 | 12/25 | 11/20 | 784 | 100 Clark Street, Millkeep, Brightburn BB31 2BH |
Mastercard | Jon Robb | 5100 0000 0000 1907 | 12/25 | 11/20 | 654 | 9 Fawn Lane, Edgenesse, Havenfield HF15 8DW |
Electron | Timothy Taylor | 4508 7500 0000 1908 | 12/25 | 11/20 | 159 | 79 Main Street North, Woodhedge, Dorley DO67 9WN |
Visa Purchasing | Ray Sheen | 4001 6506 1790 7186 | 12/25 | 11/20 | 534 | 34 Meadow Lane, Esterbourne, Whitemallow WM10 9RL |
Amex | Mark Dalton | 3400 0006 1790 712 | 12/25 | 11/20 | 5464 | 45 West Street, Silverpond, Faircastle, FC3 1LX |
JCB | Shirley Anderson | 3528 0006 1790 7180 | 12/25 | 11/20 | 642 | 79 Lexington Court, Merrowhaven, Ironelf IE13 4RY |
Test Case 5
Authorisation Declined with 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | Kirsty Catlin | 4282 7300 0000 2397 | 12/25 | 11/20 | 985 | 30 Edgewood Drive, Marbledale, Riverwick RW8 4BZ |
Visa Debit | Fiona Gates | 4921810000008011 | 12/25 | 11/20 | 857 | 3 Windsor Drive, Westerwood, Aldpond AP10 4AY |
Maestro | John Askwith | 6759000000008011 | 12/25 | 11/20 | 078 | 28 Bank Street, Blacknesse, Winterhall WH2 7XN |
Mastercard | Graeme Brown | 5100000000008019 | 12/25 | 11/20 | 871 | 46 Holly Drive, Eastrock, Fairston FS61 4TH |
Electron | Victoria Bury | 4508750000008010 | 12/25 | 11/20 | 656 | 15 Canterbury Road, Fayhollow, Glassrose GR6 1UA |
Visa Purchasing | James O’Hara | 4001651463041773 | 12/25 | 11/20 | 664 | 141 Grant Street, Valvale, Valfort VF5 4BT |
Amex | Damon Corrigan | 340000146304174 | 12/25 | 11/20 | 2445 | 48 Pheasant Run, Castlehaven, Springmage SM4 4BL |
JCB | Philip Ramsey | 3528001463041777 | 12/25 | 11/20 | 724 | 78 Creek Road, Morbridge, Summerwynne SW5 2QA |
Test Case 6
Authorisation Referred with 3D Secure
Card Type | Card Name | Card Number | Expiry Date | Start Date | CV2 | Address |
---|---|---|---|---|---|---|
Visa Credit | Julie Bean | 4104710000005315 | 12/25 | 11/20 | 487 | 84 Chestnut Street, Butterby, Shoremere SM10 4RR |
Visa Debit | Nigel Munroe | 4921810000000471 | 12/25 | 11/20 | 874 | 55 Somerset Drive, Swynbourne, Fallcastle FC9 1ND |
Maestro | Alice Shouler | 6759000000000471 | 12/25 | 11/20 | 679 | 76 Ridge Road, Vertwick, Wayston WS5 3HQ |
Mastercard | Harry Boot | 5100000000000479 | 12/25 | 11/20 | 555 | 64 Olive Street, Spellfort, Snowwyn SW16 9AD |
Electron | Philippa Waye | 4508750000000470 | 12/25 | 11/20 | 784 | 100 Magnolia Avenue, Cliffhall, Highshore HS15 1AE |
Visa Purchasing | Heston Gibbs | 4001653139120510 | 12/25 | 11/20 | 289 | 45 Garfield Avenue, Brightholt, Estercrystal EC2 6UT |
Amex | Hugh Lowe | 340000041582957 | 12/25 | 11/20 | 2465 | 35 Highland Avenue, Summerham, Ashview AV15 0QX |
JCB | Annette Irons | 3528003139120514 | 12/25 | 11/20 | 232 | 45 Bridge Street, Springwyn, Maplehedge MH3 5UZ |
Verify your 3D Secure 2 Integration
Note
All examples within the Judopay documentation use the sandbox environment, so you can process test transactions while developing your app.: https://api-sandbox.judopay.com/transactions/...
To verify your sandbox integration to 3D Secure 2 is correct, use the test card information to test the outcome of different transaction results. The cardHolderName corresponds to an expected transaction result.
For example to test for the result: AUTHENTICATION_ISSUER_REJECTED, add FL-ISSUER-REJECTED as the cardHolderName in the request.
To verify your sandbox integration:
Authenticate the 3D Secure 2 test transaction, either by:
Creating a
Payment-Session.
Calling directly to the API using your 3D Secure 2 enabled API token.
Add a
cardHolderName
in the request:
Note
If you specify a different cardHolderName to any found in the table below, the FL-SUCCESS flow will be the default flow.
CardHolder Name | Flow Type | Transaction Result | ECI* |
---|---|---|---|
FL-SUCCESS | Frictionless | AUTHENTICATION_SUCCESSFUL | 5 |
FL-ATTEMPT-NO-SUCCESS | Frictionless | AUTHENTICATION_ATTEMPTED_BUT_NOT_SUCCESSFUL | 6 |
FL-FAILED | Frictionless | AUTHENTICATION_FAILED | 7 |
FL-ISSUER-REJECTED | Frictionless | AUTHENTICATION_ISSUER_REJECTED | 7 |
FL-AUTH-ERROR | Frictionless | AUTHENTICATION_COULD_NOT_BE_PERFORMED | 7 |
CHALLENGE | Challenge | CHALLENGE_REQUIRED | N/A |
*Electronic Commerce Indicator (ECI)
The Electronic Commerce Indicator as received from the 3D Secure Server. Denotes the 3D Secure Authentication status, used to show liability status.
Note
You should check how your app responds to the different transaction results.
When you are ready to go live:
Delete
-sandbox
from the URLUse your live token and secret