Method Url Populated
You are here because the Authentication Response contained
MethodData fields. This step is required only if these fields are populated.
- Render a hidden iFrame
- Send an
MethodUrlfrom the Authentication Response, containing the
- Interpret the results sent back to your supplied
Your expected output is to be able to resend the Authentication Request, this time with the field
MethodCompletionIndicator set to either Y or N.
Render a hidden iFrame and send
Although separate steps, these are effectively completed in a single block of code.
POST request should be sent to the
MethodUrl with the following parameters:
|Field Name||State||Data Type||Description|
|threeDSMethodData||Mandatory||String||This is the value as provided in the Authentication Response.|
It is a Base64-encoded string containing the Transaction ID and your NotificationUrl, previosuly supplied. You should simply pass it in 'as is'.
POST example code
threeDSMethodData (for information only, this step is NOT required):
Interpret the Results sent back
Once the ACS has completed their Cardholder interaction, the ACS will send a form back to your
MethodNotificationUrl via an
HTTP POST. You should then send a new Authentication Request containing the
ThreeDsServerTransactionId from the initial Authentication Response and
MethodCompletionIndicator set to
If there is a timeout where the ACS has not responded within 10 seconds then the
MethodCompletionIndicator should be set to
N in the Authentication Request
You should now complete a second Authentication Request, completing the two additional fields;
This second Authentication Response will confirm whether to proceed to the Challenge Flow, or if this is Frictionless and you can proceed to Using your Results.