Skip to main content
PUT

3DS Authentication Guide

Store and manage 3D Secure authentication data
Stores 3D Secure authentication results on an existing token. Use this when you have performed 3DS authentication outside of PCI Booking and need to attach the authentication data (CAVV, ECI, XID) to the token for use in subsequent payment transactions.

Error Responses

Parameter Constraints

  • ThreeDSecIndication is required and must be Authenticated or TechnicalProblem.
  • AuthenticationValue has a max length of 256 characters and is required when ThreeDSecIndication is Authenticated.
  • Eci has a max length of 2 characters.
  • Version must start with “1.” or “2.”.

Parameters

Headers

string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. See the Authentication guide.

Path Parameters

string
required
The token ID as returned by one of the tokenization methods. For example, 2821a46d80e14d1b96a7f18f1b81926d.

Request Body

string
required
The cardholder’s Authentication Verification Value (AVV). e.g. 1234567890. Max 256 characters.
string
required
The version of 3DS authentication used. Should start with either “1” or “2”. Max 5 characters.
string
The Electronic Commerce Indicator (ECI) value. e.g. 12.
string
The 3D Secure authentication decision. Accepted values: Authenticated, TechnicalProblem, CardNotEnrolled.
string
The 3DS transaction ID for 3DS version 1.0 (XID) and version 2.0 (3DS_Trans_ID). Max 40 characters.
string
Unique transaction identifier assigned by the Access Control Server (ACS) to identify a single 3D Secure transaction.

Response

201 - 3D Secure data stored successfully.