3DS2 is a payments industry standard that promotes secure, frictionless consumer authentication for online payments. 3DS2 allows you to reduce fraud by providing methods to verify the authenticity of online payments.
The steps required to implement 3DS2 using Fat Zebra will depend on:
- If you have already have an MPI (Merchant Plug-in) or require Fat Zebra to act as your MPI
- Your PCI level
- Your preferred integration method
If you have an existing MPI integration you will need to follow your MPI's instructions in order to authenticate a payment transaction. After authentication your MPI will provide you with 3DS data which may include:
- Cryptogram, CAV, CAVV or AAV
- Ecommerce Indicator (ECI) or Security Level Indicator (SLI)
You will then need to set the 3D Secure fields on your Fat Zebra Purchase or Refund API calls in order to complete a 3DS2 transaction.
Fat Zebra can act as your MPI. Please contact your Fat Zebra representative for more information on how to add Fat Zebra's 3DS2 MPI to your account.
Using Fat Zebra's MPI, there are various integration methods to choose from depending on your PCI level:
3DS Integration Guide
Hosted Payments Page
PCI SAQ A required
Your website uses Fat Zebra’s payment form through the Fat Zebra Hosted Payments Page iframe.
Payment processing is entirely outsourced to FatZebra, meaning you do not need to handle any raw card data.
PCI A-EP required
Your website hosts the payment form and you are responsible for collecting card details on front end code you host.
Card data exchange with Fat Zebra will take place via an AJAX call from your frontend directly to Fat Zebra.
PCI SAQ D required
Your website hosts the payment form and you are responsible for collecting card details in both your backend and frontend.
Card data exchange with Fat Zebra will take place via API calls from your backend system to Fat Zebra.
Updated almost 2 years ago