Introduction - Merchant Warrior API 2.0

3D Secure 2 aims to provide merchants with an improved online experience by offering both frictionless and challenge authentication flows, coupled with additional authentication mechanisms.

As there are some issuers that are not ready to support 3DS Secure 2, you should also take into consideration a fallback mechanism to be able to handle a 3D Secure 1 request. Our APIs will help you determine if a card is not ready for 3D Secure 2.

Those who have implemented 3D Secure 1 will remember a redirect (via browser, or within an iFrame) taking place for all authentication requests. 3D Secure 2 modifies this behaviour to authenticate the customer within your application (web or mobile) and provide a more seamless payments experience for the consumer.

You can find test cards here for your sandbox testing of the different 3DS2 scenarios.

A sample of the full manual implementation can be found here - https://jsfiddle.net/merchantwarrior/nt1fpq9g/137/

A sample of performing a tokenized payment with 3DSv2 with our WebSDK can be found here - https://jsfiddle.net/merchantwarrior/dmgzsth9/3/