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.

Name of the card network for a specific transaction.

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.

Used to identify the method of Stepup.

This is a unique value generated with each new OTP value or “VerificationToken”. In the instance where the consumer can receive multiple OTPs for the same transaction, this can be leveraged to show the consumer which OTP the system is expecting to be entered. This value should be sent in the SMS or Email along with the VerificationToken and then displayed on the consumer screen.

URL provided by VCAS to be used by issuer to return the OOBCallBackValidateStatus response back to the RDX/VCAS service during the OOB CallBack flow. Issuer will append the transaction status to the URL.

Token to be sent to cardholder.

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