Sandbox Environment

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 docid obafnuc1umhk vihhs5d 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 mailto\ help\@judopay com 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