CDF Reference

Custom data files (CDFs) are made available through the same method as RDFs. In general, CDFs are available a few hours after the RDFs. CDF data sets are securely delivered via SFTP in CSV format.

This document contains details about each of the CDFs, including field descriptions:

• Expired Auth
• Early ACH
• ACH Returns
• Incoming ACH
• Overdraft
• Settlement
• MC SAFE Report
• Chargeback and Disputes
• Direct Deposit Switch
• B2B Customer Master Supplemental
• MSI Installments
• Fleet Data

Expired Auth CDF

The Expired Auth CDF provides the expired authorizations for the prior day.

This table contains default fields for the Expired Auth CDF.

• The primary key for this file is Program ID + Transaction ID + Network Code.
• The filename format is expired_auth_%Y%m%d.csv.

📘

Note

The Expired Auth CDF contains data from these networks only: Mastercard debit, Mastercard credit, Visa, STAR.

Back to top

Early ACH CDF

The Early ACH CDF provides the ACH details along with the number of days of early posting.

This table contains standard fields for the Early ACH CDF.

• The primary key for this file is Transaction ID.
• The filename format is early_ach_report_%Y%m%d.csv.

Back to top

ACH Returns CDF

The ACH Returns CDF provides details on returned ACH transactions for the prior day.

This table contains default fields for the ACH Returns CDF.

• The primary key for this file is TransID.
• The filename format is ach_returns_report_%Y%m%d.csv.

Back to top

Incoming ACH CDF

The Incoming ACH CDF provides all incoming ACH for the prior day.

This table contains default fields for the Incoming ACH CDF.

• The primary key for this file is Authorization Code + Transaction Type.
• The filename format is incoming_ach_report_%Y%m%d.csv.

Back to top

Overdraft CDF

The Overdraft (OD) CDF provides information related to overdraft DDA accounts for prior days.

This table contains default fields for the OD CDF.

• The primary key for this file is GPR_XID.
• The filename format is od_details_DDA_%Y%m%d.csv.

Back to top

Settlement CDF

The Settlement CDF provides a BIN settlement summary report (similar to gAnalytics).

This table contains default fields for the Settlement CDF.

• The primary key for this file is Basebin + Date + Network.
• The filename format is settlement_%Y%m%d.csv.

📘

Note

This report looks back one day for Visa, Mastercard, and Discover; two days for Pulse, Allpoint and STAR; and three days for Maestro/Cirrus. In comparison, the gAnalytics report looks back one day for all.

Back to top

MC SAFE Report CDF

The MC SAFE Report CDF provides a BIN settlement summary report (similar to gAnalytics).

This table contains default fields for the MC SAFE Report CDF.

• The primary key for this file is ARN.
• The filename format is mc_safe_<ica>%Y%m%d.csv.

Back to top

Chargeback and Dispute CDF

The Chargeback and Dispute CDF provides chargeback and dispute information for the prior day. It is similar to the Dispute Tracker Log report in gAnalytics. This CDF includes all current (open) disputes, so an open dispute will be included every day until it is closed.

This table contains default fields for the Chargeback and Dispute CDF.

• The primary key for this file is DISPUTE_ID.
• The filename format is Dispute_Chargeback_Report_%Y%m%d.csv.
• To link the transactions in this file to the original transactions in the Posted Transactions RDF, match the AUTHORIZATION_CODE + ASSOCIATION in this file with the AUTHORIZATION CODE + NETWORK CODE of the RDF.

Back to top

Direct Deposit Switch CDF

The Direct Deposit Switch CDF provides data on direct deposit switch transactions.

This table contains default fields for the Direct Deposit Switch CDF.

• The primary key for this file is galileo_guid.
• The filename format is ddswitch_trans_%Y%m%d.csv.

Back to top

B2B Customer Master Supplemental CDF

The B2B Customer Master Supplemental CDF shows the relationship between Real-Time Funding or Corporate Credit Limit spending accounts and their respective funding accounts.

• The primary key for this file is XID or BAL_ID.
• The filename format is b2b_custmaster_supplemental_%y%m%d.csv

Back to top

MSI Installments CDF

The MSI Installments CDF contains information about MSI Installments. Only transactions related to MSI Installments are included in this file.

• The primary key for this file is UNIQUE PROGRAM ID + AUTHORIZATION CODE + TRANSACTION CODE/TYPE.
• The filename format is Installments_Posted_Trans_[clientname]_%Y%m%d.csv
• The Source column indicates where the value came from: Galileo, a Nacha file, a private data subelement (PDS) from a network settlement file, or a data element (DE) in the ISO 8583 message in the authorization stream. The actual element/subelement number for a field may vary by network, and not all elements/subelements are present for all networks.
• "Signed" amounts have a - sign for debits and no sign for credits: -30.25 for a debit and 23.67 for a credit.
• All DATETIME fields are YYYY-MM-DD h24:mm:ss.

Back to top

Fleet Data CDF

The Fleet Data CDF contains the fleet data to enrich posted transactions.

• The filename format is fleetfile_%Y%m%d.csv.
• See Fleet Cards for more information about the product.
• To interpret the codes in the fields, obtain the IPM Clearing Formats guide from Mastercard.

For this CDF, three or more addendum rows are provided per transaction, according to this criteria:

• Row 1 — Corporate card common data. Provided when the associated first presentment/1240 message meets all of these conditions:
  • The product is any corporate product.
  • The card acceptor country code (DE045 subfield 6) is "USA".
  • The cardholder transaction type (DE003 subfield 1) is 00 (purchase) or 18 (unique).
  • The transaction is not a reversal.
• Row 2 — Corporate fleet transaction information. Provided when the associated first presentment/1240 message is a Mastercard Corporate Fleet Card transaction for a fuel or non-fuel purchase.
• Rows 3–n — Corporate line-item detail. Provided when non-fuel items are purchased alongside fuel, using a fleet card.

The corporate line-item detail is provided for each additional non-fuel item purchased using a fleet card, so if a cardholder purchases five items in one transaction, the CDF will contain seven rows: one common data requirements row, one fleet transaction information row and five detail addendum rows. All rows that belong to the same transaction will have the same auth_code + network_code.

The auth_code + network_code is the foreign key to the associated financial transaction in the Posted Transactions RDF, matching the AUTHORIZATION CODE and NETWORK CODE fields in the RDF.

All rows

This table contains fields that are present in all row types.

Example

The three addenda types will be denoted as follows, assuming the purchase of three items:

Row 1: Corporate card common data requirement
usage_code: 98
industry_red_no: 000
occurrence_ind: 001

Row 2: Corporate fleet transaction info
usage_code: 98
industry_rec_no: 002
occurrence_ind: 001

Row 3: Corporate line-item detail
usage_code: 98
industry_rec_num: 950
occurrence_ind: 001

Row 4: Corporate line-item detail
usage_code: 98
industry_rec_num: 950
occurrence_ind: 002

Row 5: Corporate line-item detail
usage_code: 98
industry_rec_num: 950
occurrence_ind: 003

Row 1 fields

These fields will be inside the corporate_card_detail field in a row that has industry_rec_no: 000. All of the top-level fields will be present, even if the value is Null.

Example

{  
    "card_acceptor_type":{  
        "_raw":"1000YNNN",  
        "business_type":"1",  
        "business_owner_type":"0",  
        "business_cert_type":"0",  
        "business_eth_type":"0",  
        "business_type_code":"Y",  
        "business_owner_type_code":"N",  
        "business_cert_type_code":"N",  
        "business_eth_type_code":"N"  
        },  
    "card_acceptor_tax_id":{  
        "_raw":"830197092           Y",  
        "tax_id":"830197092           ",  
        "tax_id_code":"Y"  
        }  
  }

Row 2 fields

These fields will be inside the fleet_detail field in a row that has industry_rec_no: 002. All of the top-level fields will be present, even if the value is Null.

Example

{  
    "oil_company_brand_name":"9999",  
    "purchase_time":"0809",  
    "motor_fuel_service_type":"1",  
    "motor_fuel_information":{  
        "_raw":"00300000000409910002422000000000992",  
        "motor_fuel_product_code":"003",  
        "motor_fuel_unit_price":"000000004099",  
        "motor_fuel_unit_of_measure":"1",  
        "motor_fuel_quantity":"000242",  
        "motor_fuel_sale_amount":"000000000992"  
        },  
    "odometer_reading":"0001000",  
    "vehicle_number":"5369569",  
    "driver_number":"1234  ",  
    "product_type_code":"1"  
}

Rows 3-n fields

These fields will be inside the line_item_detail field in a row that has industry_rec_no: 950. All of the top-level fields will be present, even if the value is Null.

Example

{  
    "product_code":"5693655016",  
    "item_description":"Coca Cola Soda",  
    "item_quantity":{  
        "_raw":"0000000000010",  
        "quantity":"000000000001",  
        "quantity_exponent":"0"  
        },  
    "item_unit_of_measure":"23",  
    "item_unit_price":{  
        "_raw":"0000000003990",  
        "unit_price":"000000000399",  
        "unit_price_exponent":"0"  
        },  
    "extended_item_amount":{  
        "_raw":"00000000029912",  
        "extended_amount":"000000000299",  
        "extended_amount_exponent":"1",  
        "extended_amount_sign":"D"  
        },  
    "debit_or_credit_indicator":"D"  
}

Back to top