For frictionless authentication, it’s recommended to use xendit.js or SDK as the SDK has already handled the frictionless flow required by EMV 3DS, or else you will need to implement EMV 3DS frictionless flow and integration yourself. The difference between 3DS and 3DS 2.0 (EMV 3DS) is that for EMV 3DS, you can choose to provide additional data (such as
customer object) in the 3DS Authentication request to try and achieve frictionless authentication. This is not mandatory. If you do not provide any additional data, Xendit will still attempt to process 3DS as EMV 3DS even the frictionless is not attempted.
If you’re using Xendit tokens and performing Tokenization + 3DS using our xendit.js or SDK libraries, then the additional data must be provided in the Tokenization request. For additional data, Xendit recommends adding at least the
customer object as so that frictionless authentication can happen for cards which support it
Specific data params (see here for descriptions)
You can use our demo page that’s using xendit.js [reference] for performing authentication:
If you have successfully performed EMV 3DS, then you should see the demo 3DS page looking like this
You can check our testing card list for EMV 3DS enabled cards to be used for demo.