REST API

Combining Services

You can use the enrollment check and card authorization services in the same request or in separate requests. Using the same request is recommended.
  • Same request: Attempts to authorize the card after authentication are made if step-up payer authentication is not required. In this case, the field values that are required to prove that you attempted to check enrollment are passed automatically to the authorization service. With same request transactions, a different endpoint must be referenced and an additional element must be added to the JSON. If step-up authentication is required, processing stops to allow completion, and authorization is not called. This integration method is recommended.
  • Separate requests: You must manually include the enrollment check result values (Enrollment Check Response Fields) in the authorization service request (Card Authorization Request Fields).
Depending on your card type and whether it is a 3-D Secure 1.0 or 2.x transaction, you might not receive the XID. If you receive this field back under a frictionless scenario, it is required for authorization.
The following table lists these fields.
Enrollment Check and Response Fields
Identifier
Enrollment Check Response Field
Card Authorization Request Field
consumerAuthenticationInformation.indicator
processingInformation.commerceIndicator
Collection indicator (Mastercard only)
consumerAuthenticationInformation.ucafCollectionIndicator
consumerAuthenticationInformation.ucafCollectionIndicator
CAVV
consumerAuthenticationInformation.cavv
consumerAuthenticationInformation.cavv
AAV
consumerAuthenticationInformation.ucafAuthenticationData
consumerAuthenticationInformation.ucafAuthenticationData
XID
consumerAuthenticationInformation.xid
and
consumerAuthenticationInformation.xid
Result of the enrollment check for Asia, Middle East, and Africa Gateway
consumerAuthenticationInformation.veresEnrolled
consumerAuthenticationInformation.veresEnrolled
3-D Secure version
consumerAuthenticationInformation.specificationVersion
consumerAuthenticationInformation.paSpecificationVersion
Directory server transaction ID
(Not required for 3-D Secure 1.0.)
consumerAuthenticationInformation.directoryServerTransactionId
consumerAuthenticationInformation.directoryServerTransactionId