Transaction Share
Overview
To provide customers with offers for cash back rewards on purchases, Cardlytics requires you as the Publisher to share customer transactions.
Transaction data, including customers, cards and accounts, is integral to the success of the Cardlytics system. Data feeds have two distinct uses:
- Historical or “look-back” data, which is loaded before Cardlytics Go Live.
- Daily data feeds used to support the ongoing operation of the Cardlytics system.
Note that both feeds refer only to current customers, cards, and open accounts.
Transaction Lookback
Cardlytics first needs a one-time export of a 13-month back book of transactions in order to facilitate targeting at program launch. Cardlytics will only need settlement transaction and the data input following the schema outlined in the transaction ingest.
Transaction Ingest
Cardlytics makes available a transaction ingestion service for Publishers to share customer transactions with Cardlytics' systems. There is a standard JSON over HTTPS endpoint available for sending one or more transactions to Cardlytics in near-real-time. There are also bulk file base transaction options. "Required For" column indicates the data we expect to receive for the respective type of transaction. In the case where the data cannot be provided, Cardlytics will work through alternatives and mitigations during the transaction mapping phase of our engagement.
Note: During design and integration, Cardlytics will work closely with your Publisher teams to understand which of the fields are available and to provide additional guidance on default values, etc.
"Required For" column shows when the field should be filled in. In the case where the data cannot be provided, Cardlytics will work through alternatives and mitigations during the transaction mapping phase of our engagement:
- (All) Transactions
- (Auth)orization Transactions
- (Post)ed Transactions
| Field | Description | Data Type | Required For | Length |
|---|---|---|---|---|
| Source Customer ID | Unique ID for the customer - Should not be actual customer number to protect consumer data. The financial institution will need to be able to match this number to the actual customer number to resolve service issues. This value is immutable once set -- it cannot be changed via any process | String | All | 120 |
| Source Organization ID | Indicates which rewards portfolio/program for the customer (ex: Publisher name, etc.) This ID will be developed in conjunction with Cardlytics. An organization will be created during the implementation process. | String | All | 120 |
| Postal Code | The postal code of the customer | String | All | 10 |
| Source Account ID | Unique ID for an account that made the transaction | String | All | 120 |
| Source Transaction ID | Unique transaction ID from the network or a unique ID for the transaction from the Publisher | String | All | 120 |
| Source Transaction Date(Local Time) [yyymmddhhmmss] | The date/time the transaction occurred using the local time where the purchase was made. Please do not include any special characters (ex. 201702132200028) | Date-time | All | 24 |
| Source Transaction Date UTC Offset | The offset between the Source Transaction Date (Local Time) and the Source Transaction Date (GMT) Data format: +/-##.## Example: +05.00 |
String | All | 6 |
| Source Posting Date [yyymmddhhmmss] | The date/time the transaction cleared. Please do not include any special characters. (ex. 20170213220028) | Date-time | Post | 24 |
| Source Transaction Type ID | Can be variable based on account. If this is a traditional DDA account, this would indicate things like Deposit, Check, Debit Card activity, Online Bill Pay, etc. If this is a Credit Card, this would indicate debits and credits, disputes, etc. | String | All | 20 |
| Source SIC | This is the Standard Industry Code (SIC). If both the MCC and SIC are available, please provide both. (Populate with spaces if the field is not available) | String | All | 10 |
| Source Merchant Category ID | 4 digit merchant category code (MCC) | String | All | 10 |
| Source Transaction Merchant | The description of the transaction as it appears on the customer’s statement. This field should contain enough information to determine the merchant and store of the transaction. | String | All | 350 |
| Source Transaction City | City where the purchase was made | String | All | 100 |
| Source Transaction State | Abbreviation of the state or province where the purchase was made | String | All | 5 |
| Source Transaction ZIP | Purchase Postal Code - May be listed as the city code in the transaction record | String | All | 10 |
| Source Merchant IDs | Colon separated key value pair of all merchant IDs associated with a given transaction (including aggregator Sub-MIDs) along with their associated MID type (ie. CAID, CLEAR MID, AUTH MID) | String | All | 1000 |
| Mobile Indicator | Boolean value if a mobile wallet was used at point of sale | String | All | 1 |
| Wallet Description | When a wallet is used at point of sale, the token_requestor_id being used (e.g. 40010030273 – APPLE_PAY using a VISA) | String | All | 25 |
| IIN/BIN | The first 6 digits of the Primary Account Number (PAN) | String | All | 6 |
| Card Present Indicator | Network field indicating whether card was present at point of sale VISA: 0 = Cardholder present 1 = Cardholder not present, unspecified 2 = Cardholder Not present, mail/telephone 5 = E-commerce Request Mastercard: 0 = Cardholder Present 1 = Cardholder not Present, unspecified 2 = Cardholder not present, mail/facsimile order 3 = Cardholder not present, phone/ARU order 4 = Cardholder not present, standing order/recurring transaction 5 = E-commerce order (home PC, Internet, mobile phone, PDA) |
String | All | 5 |
| Recurring Transaction Indicator | Indicator representing whether the transaction has been designated as recurring (i.e. Netflix Subscription) | String | All | 1 |
| Authorization Amount | The amount of the transaction at time of authorization (or swipe). The system will assume the last two digits represent ‘cents’, so do not round off trailing zeros (i.e. $5.00 = 500) | String | All | 13(right justified) |
| Cashback at Point of Sale Amount | For select debit transactions, the amount of cashback that was given as part of the total transaction amount. The system will assume the last two digits represent ‘cents’, so do not round off trailing zeros (i.e. $5.00 = 500) | String | All | 13(right justified) |
| Posted Amount | The amount of the posted transaction. Do not include the decimal point. The system will assume the last two digits represent ‘cents’, so do not round off trailing zeros (i.e. $5.00 = 500) | String | All | 13(right justified) |
| Currency Code | Standard network currency code (i.e. $US = USD or 840) | String | All | 3 |
| Last 4 Digits of Card | For all debit (PIN and Signature) and credit transactions, the last 4 digits of the card used for the transactions | String | All | 4 |
| Debit Credit Type Indicator | Typically 'C' or 'D' to identify credits (funds back to card) and debits (purchases) | String | All | 1 |
| Online Indicator | Indicates whether the purchase was made online | String | All | 10 |
| Multiple Clearing Sequence Number | Indicates whether the transaction is a part of a larger transaction group resulting from a split shipment and if so the number of the installment payment. If not part of an installment, payment this number must be zero. | String | All | 5 |
| Multiple Clearing Sequence Count | Indicates the total number of installment payments in conjunction with Multiple Clearing Sequence Number. If not part of an installment, payment count must be zero. | String | All | 5 |
| Authorization Approval Code | Provided by the issuing bank to verify sufficient funds available when a card transaction is made | String | All | 10 |
| Acquirer Refrence Number | A unique number that tags a card transaction when it goes from the acquiring bank to the cardholder’s issuing bank | String | All | 25 |