RDX Specification

ValidateRequest

The Validate request is communicated by the VCAS platform to the client. The client responds with success, failure or retry logic.

Suggest Edits

ValidateRequest API Reference: Interactive request/response specification

ValidateRequest Code Recipe: Pseudocode resource with code snippets

NameDescriptionTypeLengthRequired
ProcessorId VCAS provided identifier for the client.StringUp to 24 charactersRequired
IssuerId VCAS provided identifier for the client.StringUp to 24 charactersRequired
TransactionId VCAS generated transaction reference id: 36-character GUID value.StringUp to 36 charactersRequired
StepupType The StepupType value that was returned in the RDX Stepup Response, RDX will echo back this field on the Validate request.

Stepup Type Values		StringEnumOptional
DSTransactionId Directory Server (DS) generated transaction reference id. GUID Format.String36 charactersConditional
StepupRequestId Unique identifier to identify the particular Stepup request.StringUp to 36 charactersOptional
FirstFactorOutcomeWill provide the outcome of the first authentication. Validate Response values:
  • SUCCESS: Continues the transaction with a successful authentication status of the first factor.
  • FAILURE: Continues the transaction with a failed authentication status of the first factor.
  • RETRY: Allows the cardholder to re-attempt authentication and validation logic can be built to limit the number of authentication attempts. Note: This status is only applicable when VCAS is not validating the issuer’s OTP or Token value.

    The following status should not apply for First Factor Outcome unless the client is performing the validation on the first factor and returns them on the first factor RDX Validate response.
  • PENDING: Will initiate another Validate Request from VCAS to the issuer after 2 seconds and will only be used when StepUpResponse ➤ Type is OUTOFBANDOTHER or BIOMETRIC
  • FAILWITHFEEDBACK:- Presents a screen to the cardholder with instructions to get help and will send back a failed authentication status to the merchant.
  • BLOCKED:- Blocks the card and returns a failed authentication status to the merchant, future authentication attempts are failed until unblocked.
  • REJECTED: Only supported for 2.x.x transactions. This status ends the transaction with a rejected authentication status to the merchant and indicates they should not proceed with authorization.

    Note: Error and Stepup aren’t available status values because RDX will not continue with the second factor portion. Error will return an unavailable authentication status and Stepup will send a new RDX Stepup Request.
    		• StringEnumOptional
    StepupCounter Counter for tracking the number of Stepup calls. Each Stepup can go from Stepup ➤ InitiateAction ➤ Validate.

    If the user requests a "resend" via the browser or native app templates it will initiate another Stepup request.

    Note: Initial value will be 0 (zero).    		IntegerRequired
    MessageVersion Version of the 3DS protocol based on 3DS spec.

    This version will increment with each new specification released by EMVCo for 2.2. This will typically follow a X.Y.Z version format. Example: 2.2.0    		StringUp to 8 characters.Required
    RDXMessageVersion Message Version of the RDX protocol being used. This will be used to enable new features without breaking current integrations. Example: 2.2.3StringUp to 8 charactersOptional
    BehavioralBiometricsResultObject to validate result in behavioral biometrics authentication.

    ValidateRequest.BehavioralBiometricsResult    		List.ObjectNARequired
    CredentialResponseA list of Credential Response Objects. Must contain at least one credential object. This object is used to validate the challenge and can contain values input by the consumer; e.g. the record will contain the OTP value to validate.

    ValidateRequest.CredentialResponse    		List.ObjectNARequired

    Updated about 1 year ago