Consumer Authentication

Owned by Jacob Gries (Unlicensed)
Last updated: Sept 09, 2020 by Chris Bohatka
1 min read

This is the first transaction of the Lookup/Authenticate pair that is used to process the Consumer Authentication transaction request. The TransactionType value represented on the transaction request will dictate how the transaction will be processed. 

The CardNumber value dictates the program that will be used in processing the transaction. Currently, Verified by Visa, Mastercard SecureCode/Identity Check, American Express SafeKey, Discover ProtectBuy, JCB J/Secure and Diners Club ProtectBuy are supported by Centinel.

Merchants must ensure that Cardinal has the proper Acquiring Merchant Identification Number and corresponding Acquiring Bank Identification Numbers (BINs) configured in your account. The identifiers may vary based on card acceptance with your acquirer and processor. Please contact us to verify your credentials.


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.