Testing the latest Safepay Checkout integration
When integrating Safepay into your checkout flow, you can take advantage of our sandbox environment to simulate payments made by your customers through Safepay. This allows you and your team to get familiar with the customer journey as well as how payments are reconciled with your system and Safepay.
What is a sandbox environment
Using the sandbox environment gives you greater flexibility and allows you to make sure payments are being correctly captured, displayed and responded to before you enable your website to accept live payments. We also enable you to simulate refunds (both partial and full), check email receipts and debug payments while you’re integrating Safepay.
3D Secure testing
Card based transactions also require Safepay to authenticate the customer before we can authorize and capture the payment. This is commonly referred to as 3D Secure Authentication, Payer Authentication or Customer Authentication. All these three terms basically refer to the same flow whereby your customer is redirected to a secure website hosted by his bank and prompted with an OTP (One Time Passcode) to authenticate and confirm the payment. With Safepay’s sandbox environment, you can now test and simulate the 3D Secure flow which will enable you to test a variety of scenarios including successful authentication, unsuccessful authentication and partial authentication.
To explain briefly, when testing Safepay in a sandbox environment you can use any one of the Dummy Cards we have provided here, or search Google for one. We recommend that you do not use your real card numbers while testing, even though this environment is completely simulated. Once you enter in all the required information and hit the “Make Payment” button, Safepay will begin the payment simulation process. If the details are accurate and valid, Safepay will redirect you to our 3D Secure emulator which you can use to simulate various payer authentication flows as well as payment failure scenarios. Refer to the screenshot below to see what the emulator looks like.
Once you’re done testing various payment flows during your integration, you can also see the payment data Safepay has captured on your sandbox dashboard. You can access your sandbox dashboard by using the link below.
https://sandbox.api.getsafepay.com/dashboard/login
Find the payment you were testing and click into it to view more details. Once on the payment details page, you can scroll around and check authentication details for the payment. Knowing how to do this will help you judge live payments made by real customers and check whether your customer was correctly authenticated before making the payment.
Key terms
Key terms to understand about 3D Secure:
ECI (Electronic Commerce Indicator) Values:
01: Authentication attempted (Mastercard)
02: Successful authentication (Mastercard)
05: Successful authentication (Visa)
06: Authentication attempted (Visa)
07: The card cannot be enrolled. No liability shift.
PARes status code (the threeDResult returned by the API)
A: Proof of authentication attempt was generated.
B: Bypassed authentication.
N: Customer failed or canceled authentication. Transaction denied.
R: Authentication rejected (used for 3D Secure 2.x transactions only)
U: Authentication not completed regardless of the reason.
Y: Customer was successfully authenticated.
VeRes Enrolled (Cardholder enrollment or activation in the Verified by Visa program)
Y: Card enrolled; you must authenticate. Liability shift.
N: Card not enrolled; proceed with authorization. Liability shift.
U: Unable to authenticate regardless of the reason. No liability shift.