Recommended Integration

Four types of integration are available for 3-D Secure 2.x:

If you are currently using Payer Authentication services in your existing business processes and need to upgrade to 3-D Secure 2.x, we recommend using the Cardinal Cruise Direct Connection API integration. The Cardinal Cruise Direct Connection API integration most closely resembles the current process in which you request the Enrollment Check service to verify that the customer is enrolled in one of the card authentication programs and receive a response. With 3-D Secure 2.x, that response includes a new value, the processor transaction ID.

For enrolled cards, include the ACS URL, payload, and processor transaction ID to proceed with the authentication session. Then request the validation service, sending the processor transaction ID with your request, and receive a response with the e-commerce indicator and CAVV or AAV.

For more information about the Cardinal Cruise Direct Connection API, see Implementing Cardinal Cruise Direct Connection API Payer Authentication.

For details about the other integrations, see Implementing SDK Payer Authentication or Implementing Hybrid or Standard Payer Authentication.