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