- Combining the Authentication and the Authorization Services
- Implementing SDK Payer Authentication
- Payer Authentication Use Cases
- Authentication with TMS Tokens
- Authentication with Flex Micro Form Tokens
- Authentication with Tokenized Cards
- Testing Payer Authentication
On This Page
REST API
Combining the Validation and the Authorization Services
After the customer is successfully authenticated, you must get authorization from the
issuing bank to proceed with the transaction. While these are separate processes, you
should integrate these two services into a single process whenever possible. When you do
so, no additional integration work is required on your part to manually map the
appropriate validation results to corresponding authorization request fields.
With the same request transactions, a different endpoint must be referenced for the
authorization, and an additional element must be added to the JSON. When step-up
authentication is required, transaction processing stops to allow authentication to
complete, and authorization is not called until after the challenge response is
validated. This integration method is highly recommended. 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.