On This Page
Simple Order API
Combining Services
You can combine the enrollment check and card authorization services into the same
request or use a separate request for each service. 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. If step-up authentication is required, processing stops to allow completion, and authorization is not called. This integration method is recommended.
- Separate requests: Manually include the enrollment check result values (Enrollment Check Response Fields) in the authorization service request (Card Authorization Request Fields). Refer to the fields that are listed in the table.
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 under a
frictionless scenario, it is required for authorization.
This table lists these fields.
Identifier | Enrollment Check Response Field | Card Authorization Request Field |
---|---|---|
payerAuthEnrollReply_com
merceIndicator | ccAuthService_commerceIn dicator | |
Collection indicator (Mastercard only) | payerAuthEnrollReply_ucaf CollectionIndicator | ucaf_collectionIndicator |
payerAuthEnrollReply_cavv | ccAuthService_cavv | |
payerAuthEnrollReply_ucaf AuthenticationData | ucaf_authenticationData | |
payerAuthEnrollReply_xid | ccAuthService_xid | |
Result of the enrollment check for Asia, Middle East, and
Africa Gateway | payerAuthEnrollReply_vere
sEnrolled | |
3-D Secure version | payerAuthEnrollReply_spec ificationVersion | ccAuthService_paSpecifica
tionVersion |
Directory server transaction ID | payerAuthEnrollReply_direc
toryServerTransactionID | ccAuthService_directorySer
verTransactionID |