Step 3 - 3DS Method Data - Merchant Warrior API 2.0

The 3DS Method Data is used by issuers to gather a device fingerprint from your customer directly.

Render a hidden HTML iframe in the cardholder's browser

Create a form with an input field named threeDSMethodData

This field must contain the paReq (retrieved from Step2 ) and be Base64-URL encoded

Post the form to the acsURL (retrieved from Step2 ), with the HTML iframe as a target

Example

Add an iframe to the user's browser using JavaScript

Resulting in the following html

 <iframe name="threeDSMethodIframe" class="hidden"/>

Create a HTML form that contains the input field:

<form class="" id="threeDSMethodForm"> 
  <input type="hidden" name="threeDSMethodData" id="threeDSMethodData"/> 
</form>

This form can be submitted using the following JavaScript:

The acsURL will respond with the threeDSServerTransID which will be submitted via POST to the notifyURL you specified in your Step 1 - getAccessToken request.

If the callback from the acsURL is not received by your notifyURL within 10 seconds from the POST call above, it is deemed to have failed. In this situation you should proceed to Step 4 and set the 3DS Completion Indicator (threeDSCompInd) to N.

{"threeDSServerTransID": "eyJ0aHJlZURTU2VydmVyVHJhbnNJRCI6ImY3OGYyM2ZlLTEzNzAtNDYyNC1iNDI5LThhYjhkODQ1NWJkYyJ9"}

If your notifyURL receives a threeDSServerTransID you can proceed to Step 4 and set the 3DS Completion Indicator (threeDSCompInd) to Y. You may want to communicate with your frontend after gathering a device fingerprint using the 3DS Method Data above. If this is the case see postMessage Notifications for further information.