Combining Check Enrollment and the Authorization Services

Receiving certain responses from checking enrollment allows the authorization to be requested immediately afterwards. The possible checking enrollment responses are:

Successful frictionless authentication

Attempted stand-in frictionless authentication

Issuer does not support the payer authentication program

Account is not eligible for a payer authentication program

Unavailable frictionless authentication

Failed frictionless authentication

Rejected frictionless authentication

In all checking enrollment scenarios, it is recommended that you integrate these services by combining the checking enrollment and authorization services into a single transaction. When the services are combined, one of these conditions occurs:

No additional integration work is required to manually map the appropriate check enrollment results to the corresponding authorization request fields.

If further authentication is needed, the authorization cannot happen until after authentication completes and you can proceed to the next steps for challenging.

With same request transactions, a different endpoint must be referenced for the authorization, and an additional element must be added to the JSON. Depending on your card type, you might not receive the XID value. If you receive this field under a frictionless scenario, it is required for authorization.

Check Enrollment Response Fields and Their Equivalent Authorization Request Fields

When a customer is authenticated without a challenge, the transaction can be authorized either in the same request or in a separate authorization request. Whether authorization occurs in the same request or a separate request, the values from the check enrollment response must be passed to the authorization request to qualify for a liability shift. This table matches the check enrollment fields with their equivalent authorization fields. Sometimes a check enrollment response field is the same field used in the authorization request.

Be sure to include the following card-specific information in your authorization request:

For Visa, American Express, JCB, Diners Club, Discover, China UnionPay, and Elo, include the CAVV (Cardholder Authentication Verification Value).

For Mastercard only, include the collection indicator and the AAV (also known as UCAF).

Enrollment Check and Response Fields
Identifier	Enrollment Check Response Field	Card Authorization Request Field
E-commerce indicator	consumerAuthenticationInfo rmation.ecommerceIndicator	processingInformation.commerceIndicator
Collection indicator	consumerAuthenticationInfo rmation.ucafCollectionIndicator	consumerAuthenticationInfo rmation.ucafCollectionIndicator
CAVV	consumerAuthenticationInformation.cavv	consumerAuthenticationInfo rmation.cavv
AAV	consumerAuthenticationInfo rmation.ucafAuthentication Data	consumerAuthenticationInfo rmation.ucafAuthentication Data
XID	consumerAuthenticationInformation.xid	consumerAuthenticationInfo rmation.xid
Result of the enrollment check for Asia, Middle East, and Africa Gateway	consumerAuthenticationInfo rmation.veresEnrolled	consumerAuthenticationInfo rmation.veresEnrolled
3-D Secure version	consumerAuthenticationInfo rmation.specificationVersion	consumerAuthenticationInfo rmation.paSpecificationVersion
Directory server transaction ID	consumerAuthenticationInfo rmation.directoryServerTran sactionId	consumerAuthenticationInfo rmation.directoryServerTransactionId