If performing 3DS in the browser, you must prepare the Challenge Request (CReq), send it to the ACS, and decode the Challenge Response (CRes). See the Browser Integration Guide for more information.
The formats of the CReq and CRes are shown below.
If performing 3DS in a mobile app using the 3DS SDKs, the SDKs will prepare the CReq and decode the CRes for you. See the App Integration Guide for more information.
2.1.0
2.2.0
APP
BRW
required
|
The 3DS message type. Must always be set to
Example:
"CReq"
|
||||||||||
2.1.0
2.2.0
APP
BRW
required
|
The 3DS protocol version identifier. Should be set to the same value as in the Authenticate Response. |
||||||||||
2.1.0
2.2.0
APP
BRW
required
|
The unique identifier (UUID) for tracking the transaction throughout the 3DS process, as found in the Authenticate Response.
Example:
"c5584543-b67e-5117-bb34-3567ac6a1123"
|
||||||||||
2.1.0
2.2.0
APP
BRW
required
|
The unique identifier (UUID) for tracking the transaction throughout the 3DS process, as found in the Authenticate Response.
Example:
"214a549e-2310-4359-b590-c53a20adcc78"
|
||||||||||
2.1.0
2.2.0
BRW
required
|
Dimensions of the challenge window that will been displayed to the cardholder. The ACS shall reply with content that is formatted to appropriately render in this window to provide the best possible user experience. Preconfigured sizes are width x height in pixels.
Options:
|
2.1.0
2.2.0
APP
BRW
|
The 3DS message type. Will always be
Example:
"CRes"
|
||||||
2.1.0
2.2.0
APP
BRW
|
The 3DS protocol version identifier. |
||||||
2.1.0
2.2.0
APP
BRW
|
The unique identifier (UUID) for tracking the transaction throughout the 3DS process.
Example:
"c5584543-b67e-5117-bb34-3567ac6a1123"
|
||||||
2.1.0
2.2.0
APP
BRW
|
The unique identifier (UUID) used by the ACS for tracking the transaction throughout the 3DS process.
Example:
"214a549e-2310-4359-b590-c53a20adcc78"
|
||||||
2.1.0
2.2.0
APP
BRW
|
Indicates the outcome of the challenge request.
Options:
|
Was this page helpful?