Getting Started With Cardinal Centinel

Welcome to Cardinal Consumer Authentication. We're excited to get your activation process started. This guide provides an overview of the Cardinal Centinel integration process for Cardinal Consumer Authentication (CCA) including general integration, testing, and API usage instructions. This section also covers the API fields necessary to meet the new EMV 3DS (3DS 2.0) requirements and enable even richer data sharing between Merchants and Issuing banks, while also supporting native authentication. 

The goal of connecting to CCA is to allow your platform to be ready for any protocol version of 3DS.  Once complete, our Cardinal Consumer Authentication will enable you to participate in the various individual card authentication programs such as Verified by Visa, Mastercard Identity Check, American Express SafeKey, Discover ProtectBuy, JCB J/Secure, and Diners Club ProtectBuy.

This documentation guide assumes a familiarity with your website and payment processing procedures, as well as a working knowledge of the technologies and programming languages used by your eCommerce website and non-web-based applications. 


TLS Global Mandate

It is important to note that the Cardinal Cruise integration of Javascript, specifically Songbird.js, uses TLS 1.2 cipher suites and protocols and above. If you are currently using a deprecated TLS cipher suite and protocol (Ie: TLS 1.0 or 1.1) you will be required to upgrade to the latest and approved TLS 1.2 cipher suites and protocols. You can find the approved cipher suite list here.