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:
Identifier | Enrollment Check Response Field | Card Authorization Request Field |
|---|---|---|
E-commerce indicator | payerAuthEnrollReply_commerceIndicator | ccAuthService_commerceIndicator |
Collection indicator | payerAuthEnrollReply_ucaf CollectionIndicator | ucaf_collectionIndicator |
CAVV | payerAuthValidateReply_cavv | ccAuthService_cavv |
AAV | payerAuthValidateReply_ucafAuthenticationData | ucaf_authenticationData |
XID | payerAuthEnrollReply_xid
| ccAuthService_xid |
Result of the enrollment check for Asia, Middle East, and
Africa Gateway | payerAuthEnrollReply_veresEnrolled | |
3-D Secure version | payerAuthEnrollReply_specificationVersion | ccAuthService_paSpecificationVersion |
Directory server transaction ID | payerAuthEnrollReply_direc
toryServerTransactionID | ccAuthService_directorySer
verTransactionID |