VCAS provided identifier for the partner. Max. 24 characters.

VCAS provided identifier for the partner. Max. 24 characters.

VCAS generated transaction reference id. Max. 36 characters. GUID format.

Directory Server (DS) generated transaction reference id. GUID format.

Indicates the type of 3RI request for EMV transactions. Values are defined as follows:

• RecurringTransaction
• InstallmentTransaction
• AddCard
• MaintainCardInformation
• AccountVerification
• SplitOrDelayedShipment
• TopUp
• MailOrder
• TelephoneOrder
• WhitelistStatusCheck
• OtherPayment

Indicates the type of Authentication request. This data element provides additional information to the ACS to determine the best approach for handling an authentication request. Values are defined as follows:

• 01 - Payment Transaction
• 02 - Recurring Transaction
• 03 - Installment Transaction
• 04 - Add Card
• 05 - Maintain Card
• 06 - Cardholder verification as part of EMV token ID&V
• 07 - Billing Agreement
• 08 - Split shipment
• 09 - Delayed shipment
• 10 - Split payment
• 11-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)
• 80 - Reserved for Visa Payment Passkeys (Visa transactions only)
• 81-99 - Reserved for future network program usage.
  Reserved values may be introduced by network program updates. New values will be defined and published as they become available.

Unique identifier to identify the particular Stepup request. Length is 36 characters.

Device Locale from the browser header or from the app’s language settings. This value can be a single locale value or multiple concatenated together via commas. In 3DS1 this value will be directly from the browser’s “Accept-Language” header. However, in 3DS2 this is not available due to new flows so this will be a single language value following BCP 47 format e.g. en-US or en,es-PE;q=0.9,es;q=0.8

Device user agent from the browser header or the app's device identifier. Max. 2048 characters.

Version of the message based on 3DS spec. Examples 2.1.0, 2.2.0

Version of the RDX protocol being used. This will be used to enable new features without breaking current integrations. Example: 2.2.3 and 2.2.4

Identifies the category of the message for a specific use case; 01=PA, 02=NPA

Used to identify the reason the Stepup request was initiated. Only available for Cardholder Resend, future values and scenarios may be added.

Name of the card network for a specific transaction.

The issuer must redirect to this URL when validation is complete, during an Embedded OOB challenge.