Other Features
Appendices
Challenge Result - Sample Request and Response
Title: Returns the challenge result of the specified transaction ID
GET /3ds2/challenge_result/{threeDSServerTransID}
important
You must use the threeDSServerTransID value you received in the /3ds2/authenticate response in the request.
Sample URL
Test: https://uat.gw.fraud.eu.elavonaws.com/3ds2/challenge_result/102f8f6e-8472-4ada-8deb-91d5bd51de90
Production: https://gw.fraud.elavon.com/3ds2/challenge_result/102f8f6e-8472-4ada-8deb-91d5bd51de90
Headers
| Header name | Description | Required | Values |
|---|---|---|---|
| Content-Type | The MIME type of the request body. | Required | application/json |
| Authorization | Authorization type (Basic) and the base64 encoded username and password Or Bearer followed by token | Required | Basic <encoded_auth_data> Or Bearer <token_value> |
note
The sample request and response on this page assume that the acctNumber supported 3DS 2.1 authentication, but the issuer needed additional information from the cardholder to authenticate the transaction i.e. a challenge flow. After the cardholder provided additional information to the issuer, it authenticates the transaction i.e. transStatus = Y.
If transStatus = N, the response will also have the transStatusReason field.
Sample response
{
"messageType" : "RReq",
"messageVersion" : "2.1.0",
"threeDSServerTransID" : "102f8f6e-8472-4ada-8deb-91d5bd51de90",
"dsTransID" : "d9efdb88-2277-408b-859a-a16ec843395b",
"acsTransID" : "7a3378fe-cea0-4762-8035-c0b91d7e7d0e",
"authenticationType" : "01",
"authenticationValue" : "CQXYpVZrNni678cpEUQK0DZRTfQ=",
"eci" : "05",
"interactionCounter" : "01",
"messageCategory" : "01",
"transStatus" : "Y"
}