These docs are for v4.0.2. Click to read the latest docs for v4.3.0.

Callback

This is to callback from the 3DS Server to the 3DS Requestor side. 3DS Server will return to user “redirect result” to ReturnURL (13 step) with challenge result data as a query string in GET method.

Note:
• Please refer to the step number 25 in the above diagram.

Request

Field nameTypeDescription
threeDsServerTransIdStringGenerated by 3DS provider. This value is in lookup response and callback.
externalReferenceIdStringUnique authentication Id which is generated by 3DS Requestor. Conditional only if available.
statusStringTransactions status result identifier.

Possible Values:

Y - Successful Authentication

N - Failed Authentication / Account Not Verified / Transaction Denied

U - Unable to Complete Authentication

A - Successful Attempts Transaction

C** - Challenge Required for Authentication

R** - Authentication Rejected (Merchant must not submit for authorization)
Statuses of C and R only apply to Consumer authentication 2.0. Decoupled authentication is not supported at this time.

D - Challenge Required; Decoupled Authentication confirmed.

I - Informational Only; 3DS Requestor challenge preference acknowledged.

NOTE: Statuses of C and R only apply to Consumer authentication 2.0. Decoupled authentication is not supported at this time.
{
  "externalReferenceId": "795baa56-204d-42bd-a9c8-4cf0b7a567bd",
  "threeDsServerTransId": "8a880dc0-d2d2-4067-bcb1-b08d1690b26e",
  "status": "Y"
}

Response

The response will be a form post or redirection between merchant and Ant’s endpoint which will trigger transaction enquiry on step 27.