- Introducing Payer Authentication
- Implementing Cardinal Cruise Direct Connection API Payer Authentication
- Implementing SDK Payer Authentication
- API Fields
- Testing Payer Authentication
- 3-D Secure 1.0 Testing
On This Page
REST API
Implementing Cardinal Cruise Direct Connection API Payer Authentication
The Cardinal Cruise Direct Connection API supports 3-D Secure 2.x and is
backward-compatible with 3-D Secure 1.0 when the issuer, acquirer, or both, are not
ready for 2.x. This integration enables you to use an iframe to complete the device
profiling and 3-D Secure authentication requirements without including third-party
JavaScript directly on your site.
The implementation still requires the use of JavaScript on the page, and it uses
CardinalCommerce JavaScript to leverage the authentication. However, the
CardinalCommerce JavaScript is hosted and contained in the iframe and does not directly
access your web page.