Service RDFs

The Service RDFs contain data related to basic program functionality, in addition to the Base RDFs.

See About the Raw Data Files (RDFs) for general information about these files.

• Expired Authorizations — Data on authorizations that expired the previous day. (The time elapsed between authorization and expiry is based on your program's settings.)
• Settlement — A BIN-summary report that is the equivalent of the Settlement Bin - Summary report in gAnalytics. It includes all of the settled transactions per BIN.
• Dispute and Chargeback — Dispute information for the prior day. It is similar to the Dispute Tracker Log report in gAnalytics. Includes all current (open) disputes, so an open dispute will be included every day until it is closed.
  • Reg E — Disputes that fall under Regulation E
• MC SAFE report — The SAFE report that was sent to Mastercard over the last seven days, which is a BIN settlement summary report (similar to gAnalytics).

Expired Authorizations RDF

The Expired Authorizations RDF provides data on authorizations that expired the previous day. (The time elapsed before expiry is based on your program's authorization expiry settings.) This RDF helps you reconcile and clear authorized transactions that affected the available balance but that did not settle before expiry. This allows you to return funds that were reserved by an authorization, which gives your cardholders more spending power.

Insights for you:

• Determine the steady state of unsettled funds and capital allocation
• Determine the likelihood of an authorization expiring based on its characteristics

This table contains default fields for the Expired Authorizations RDF.

• The primary key for this file is Program ID + Transaction ID + Network Code.
• The filename format is expired_auth_%Y%m%d.csv.
• To reconcile the entries in this file with the Authorized Transactions RDF, match Transaction ID in this file with AUTHORIZATION CODE in the Authorized Transactions RDF.

📘

Note

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

Settlement RDF

The Settlement RDF provides a BIN-summary report that is the equivalent of the Settlement Bin - Summary report in gAnalytics. It includes all of the settled transactions per BIN. The RDF emphasizes all of the key components of the settlement amount.

📘

Note

This RDF 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.

Because this RDF summarizes the final settled transactions for a period of time, this RDF can be used for reconciliation purposes—either at the summary total level or to find specific settled transactions.

Key values that are represented in this RDF are:

• Load — Card loads that come in on Visa, Interlink, or Maestro rails but not ACH or other methods. Card loads credit cardholder accounts.
• Cash Disb — Cash disbursement as cash back at a POS or bank. They debit cardholder accounts.
• Credits — Merchant credits, which credit cardholder accounts.
• ATM Disb — ATM withdrawals, which debit cardholder accounts
• Interchange Fee — Fees that are paid by the card network to your program
• Chargeback — Part of the dispute process, a chargeback is not posted to the cardholder account until the dispute is resolved.
• Net Settle — The amount owed to the card network. It is the amount of the drawdown that the card network removes from your account.

Insights for you

• Foundational data to reconcile with networks on a periodic basis at a BIN level.

This table contains default fields for the Settlement RDF.

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

MC SAFE Report RDF

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

This table contains default fields for the MC SAFE Report.

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

Dispute and Chargeback RDF

The Dispute and Chargeback RDF provides dispute information for the previous day. It is similar to the Dispute Tracker Log in gAnalytics.

Insights for you:

This comprehensive RDF can be used instead for 2 separate reports. It provides important information like Dispute/chargeback status, reason, resolution and card holder notice date etc.

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

• 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 posted transactions.

Reg E RDF

The Reg E RDF includes both disputes and chargebacks and Sutton bank’s required data fields so that you can understand the dispute/chargeback status/details and the Reg E data for reporting to banks.

This table contains default fields for the Reg E RDF.

• The primary key for this file is DISPUTE_ID.
• The filename format is chargeback_disputes_rege_%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 posted transactions.