Overview
Understand the requirements for mutual authentication and sharing of historical data
Security & Authentication Requirements
Cardlytics employs mutual authentication, where both parties in a connection verify each other's identity using the TLS protocol, following standard security practices. The tasks and high-level implementation steps for mTLS are described in detail in mTLS Implementation. To work successfully with Publisher v2.0 APIs, publishers and partners must establish connectivity for ongoing data transfer and services.
Data Requirements
In addition, there is a requirement for the sharing of historical data. That means, Cardlytics requires Publishers to share customer transaction data, including customers, cards, and accounts, in order to provide cash back rewards. This data is used in two ways: (a) as historical "look-back" data before Cardlytics Go Live and (b) as daily data feeds used to support the ongoing operation of the Cardlytics system, involving only current customers, cards and open accounts.
Refer to Transaction & CAC (Customer, Account, Card) Data Share for more information on this requirement.
(Optional) File Transfer Configuration
Updated 29 days ago