Custom data files (CDFs) are made available through the same method as <<glossary:RDF>>s. 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.
| CDF field name | Data type | Description |
`Account Number` | NUMBER | Galileo account ID, <<glossary:balance ID>> |
`Card ID` | NUMBER | Card identifier |
`PRN` | CHAR (12) | Payment reference number |
`Program ID` | NUMBER | Program ID |
`Product` | NUMBER | Product ID |
`Transaction ID` | NUMBER | Authorization ID, ‘auth_id’ |
`Authorization TS` | DATE | Datetime timestamp of when the transaction was authorized |
`Expired TS` | DATE | Datetime when the authorization expired |
`Amount` | NUMBER | Authorization amount |
`Trans Currency Code` | CHAR (3) | Currency code for `auth_amt` |
`Merchant Number` | CHAR (15) | Merchant ID |
`Merchant Description` | CHAR (40) | Merchant description |
`Network Code` | CHAR (1) | Network code |
`Retrieval Reference Number` | VARCHAR (12) | Retrieval reference number |
[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 <<glossary:ACH>> CDF.
The primary key for this file is `
Transaction ID`.The filename format is `
early_ach_report_%Y%m%d.csv`.
| CDF field name | Data type | Description |
`Transaction ID` | VARCHAR2 (2) | Maps as identifier for the source of load/<<glossary:payment>> or source of the <<glossary:adjustment>> |
`Transaction Type` | CHAR (6) | Concatenation of activity type (`act_type`) and transaction type (`otype`) |
`Source ID` | NUMBER (18) | For `PMxx` transaction types, this field contains the payment ID (`pmt_id`), and for `ADxx` transaction types, this field contains the adjustment ID (`adj_id`) |
`External Transaction ID` | VARCHAR2 (60) | ACH transaction ID provided by <<glossary:client>> or partner |
`Transaction Time` | DATE | Transaction time of the ACH record |
`Authorization Code` | NUMBER | Unique identifier for the transaction |
`Number of Days Early` | NUMBER | The number of days early the ACH transaction is |
`Posted Early` | CHAR (1) | Flag for early ACH (`Y` for early ACH) |
`Effective Date` | DATE | ACH effective date (when the <<glossary:Nacha file>> says it would have posted without early ACH) |
`Settlement Date` | DATE | The date the transaction was settled/posted |
`Receive Date` | DATE | ACH file date (the date the Nacha file was received) |
`Load Date` | DATE | ACH load date (the date the ACH transaction was loaded to a Nacha file) |
`Amount` | NUMBER | Amount of the ACH transaction |
`PRN` | CHAR (12) | Payment reference number |
`Trace Number` | NUMBER | ACH trace number as received by Galileo |
[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`.
| CDF field name | Data type | Description |
`Name` | VARCHAR2 (80) | Name |
`SourceName` | VARCHAR (30) | Source institution name |
`Amount` | NUMBER | Amount of the ACH transaction |
`DebCredIndicator` | CHAR (1) | Debit/credit indicator. `D` = debit; `C` = credit |
`ReceivedDate` | DATE | Date that Galileo received the returned transaction |
`EffectiveDate` | DATE | Date when the ACH transaction was to take effect (without early ACH) |
`ReturnDate` | DATE | Date the transaction was returned |
`ReturnReasonCode` | CHAR (3) | Return reason code |
`ReturnReasonDescription` | VARCHAR2 (255) | Return reason description |
`TransID` | CHAR (2) | Transaction ID |
`XID` | NUMBER | Internal Galileo account ID |
[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`.
| CDF field name | Data type | Description |
`Company Name` | VARCHAR2 (20) | Company name |
`Company ID` | NUMBER | Company ID |
`Company Description` | VARCHAR2 (15) | Company description |
`Individual Name` | VARCHAR2 (80) | Individual name |
`Individual ID` | NUMBER | Individual ID |
`Authorization Code` | NUMBER | Authorization code |
`Transaction Type` | VARCHAR2 (2) | Transaction type |
`Amount` | NUMBER | Amount |
`Trace Number` | NUMBER | Trace number |
`PRN` | CHAR (12) | Payment reference number |
[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`.
| CDF field name | Data type | Description |
`ODProgramID` | NUMBER | Company name |
`ODAccountID` | NUMBER (18) | Galileo account ID, balance ID |
`GPRAccountID` | NUMBER | GPR Galileo account ID |
`ODAccountStatus` | VARCHAR2 (2) | Overdraft account status |
`ODEligibilityStatus` | VARCHAR2 (2) | Overdraft eligibility status |
`ODOpt-InDate` | DATE | Overdraft opt-in date |
`ODOpt-OutDate` | DATE | Overdraft opt-out date |
`ODTotalBalance` | NUMBER | Total overdraft balance |
`ODLimit` | NUMBER | Overdraft limit |
`GPR_XID` | NUMBER (13) | Unique account identifier within a program |
[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.
| CDF field name | Data type | Description |
`Basebin` | CHAR (8) | Base BIN |
`Date` | DATE | Date |
`Network` | VARCHAR2 (255) | Card network |
`Load` | NUMBER | Load amount |
`Load Reversal` | NUMBER | Load reversal amount |
`Cash Disb` | NUMBER | Cash disbursement amount |
`Cash Disb Fee` | NUMBER | Cash disbursement fee amount |
`Retail Sales` | NUMBER | Retail sales amount |
`Credits` | NUMBER | Credits amount |
`Unique Trans` | NUMBER | Unique transaction amount |
`ATM Disb` | NUMBER | ATM disbursement amount |
`ATM Disb Fee` | NUMBER | ATM disbursement fee amount |
`Interchange Fee` | NUMBER | Interchange fee amount |
`Special Trans` | NUMBER | Special transaction amount |
`Misc Trans` | NUMBER | Miscellaneous transaction amount |
`Chargebacks` | NUMBER | Chargebacks amount |
`Sec Present` | NUMBER | Second presentments amount |
`Arbitration` | NUMBER | Arbitration amount |
`Switch Fee` | NUMBER | Switch fee amount |
`Net Settle` | NUMBER | Net <<glossary:settlement>> amount |
`Net Trans` | NUMBER | Net transaction amount |
`Settle Total` | NUMBER | Settlement total amount |
`Net Interchange Fee` | NUMBER | Network interchange fee amount |
[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`.
| CDF field name | Data type | Description |
`RECORD_TYPE` | CHAR (3) | Record type |
`ISSUER_CUSTOMER_NUMBER` | CHAR (6) | Issuer customer number |
`AUDIT_CONTROL_NUMBER` | NUMBER | Audit control number |
`ACQ_ID` | CHAR (11) | Acquirer ID |
`ARN` | CHAR (23) | Acquirer reference number |
`FRAUD_POSTED_DT` | DATE | Fraud posted date |
`ENP` | VARCHAR2 (53) | Encrypted PAN |
`TRANS_DATE` | VARCHAR2 (8) | Date when the transaction was authorized |
`TRANS_AMT` | VARCHAR2 (10) | Amount of the authorization |
`TRANS_CRNCY_CD` | NUMBER | Currency code for `TRANS_AMT` |
`TRANS_AMT_CH_BILL_CRNCY` | VARCHAR2 (9) | Billing amount of the transaction |
`CH_BILL_CRNCY_CD` | CHAR (3) | Currency code for `TRANS_AMT_CH_BILL_CRNCY` |
`CARD_PROD_CODE` | CHAR (3) | Card product code |
`MERCHANT_NAME` | VARCHAR2 (22) | Name of the merchant from DE043 |
`MERCHANT_ID` | VARCHAR2 (15) | Merchant ID from DE042 |
`MERCHANT_CITY` | VARCHAR2 (50) | Merchant city from DE043 |
`MERCHANT_STATE_CD` | VARCHAR2 (3) | Merchant state or province, two-character abbreviation |
`MERCHANT_COUNTRY` | VARCHAR2 (3) | ISO 3166-1 three-digit merchant country code |
`MERCHANT_POSTAL_CODE` | VARCHAR2 (5) | Merchant postal code from DE043 |
`MCC` | NUMBER | Merchant category code |
`POS_TERM_ATTD_IND` | VARCHAR2 (1) | |
`POS_CARD_PRES_IND` | VARCHAR2 (1) | Point-of-sale <<glossary:card-present>> indicator |
`CAT_LEVEL_IND` | VARCHAR2 (1) | Category level indicator |
`POS_CDTIC_IND` | VARCHAR2 (1) | |
`ELEC_COM_IND` | CHAR (1) | E-commerce indicator (3-D Secure) |
`POS_ENTRY_MODE` | VARCHAR2 (1) | Point-of-sale entry mode, first two characters of DE022 |
`TERMINAL_ID` | VARCHAR2 (8) | ID for the card-reading device |
`FRAUD_TYPE_CODE` | VARCHAR2 (8) | Fraud type |
`SUB_FRAUD_TYPE_CODE` | CHAR (1) | Sub-fraud type code |
`CHARGEBACK_IND` | NUMBER | Whether the transaction has been charged back |
`SETTLE_DATE` | VARCHAR2 (8) | Date when the transaction was settled |
`AUTH_RESP_CD` | CHAR (2) | Response code for the authorization request |
`PROC_DATE` | VARCHAR2 (8) | |
`CVC_IND` | VARCHAR2 (1) | CVC indicator |
`ACCT_DEVICE_TYPE` | CHAR (1) | Account device type |
`SECURE_CD` | CHAR (1) | Secure code |
`AVS_RESP_CD` | CHAR (1) | Address verification service response code |
`CARD_PRESENT_IND` | NUMBER | Card-present indicator |
`TERM_OPER_CD` | CHAR (1) | |
[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.
| CDF field name | Data type | Description |
`PROG_ID` | VARCHAR2 (250) | Program ID |
`PROGRAM` | VARCHAR2 (250) | Program name |
`AGENT` | VARCHAR2 (250) | Dispute agent name |
`DISPUTE_CASE` | VARCHAR2 (250) | Case number for all disputes files |
`SYSTEM_CASE_NO` | VARCHAR2 (250) | Not used |
`DISPUTE_ID` | VARCHAR2 (250) | ID assigned to each disputed transaction |
`BAL_ID` | VARCHAR2 (250) | Galileo ID or balance ID |
`XID` | VARCHAR2 (250) | Internal Galileo account ID |
`BASE_BIN` | VARCHAR2 (250) | Base BIN (6-8 digits) |
`CH_NOTICE_DATE` | VARCHAR2 (250) | Cardholder notification date |
`LTR_DATE` | VARCHAR2 (250) | Date when the written confirmation letter was received |
`DATE_LOGGED` | VARCHAR2 (250) | Date when the dispute was logged in the system |
`WRITTEN_CONFIRMATION_REQUEST` | VARCHAR2 (250) | Date when the written confirmation was requested |
`LOST_STOLEN` | VARCHAR2 (250) | Whether the dispute is for a card after it was lost or stolen |
`CH_DISCOVERY_DT` | VARCHAR2 (250) | Date when the cardholder noticed the erroneous transaction |
`ERROR_DESCRIPTION` | NVARCHAR2 (250) | Description of dispute reason (selected from drop-down) |
`TRANSACTION_TYPE` | VARCHAR2 (250) | Transaction type from drop-down menu: NEW (account \<30 days from first load) FOR (foreign-initiated), ATM, POS, OTH (other) |
`FOLLOWUP_DATE` | VARCHAR2 (250) | Follow-up date |
`reg_e` | VARCHAR2 (250) | Whether the dispute falls under Regulation E |
`REGE_RESOLUTION` | VARCHAR2 (250) | Date when the Regulation E dispute should be resolved: 45 or 90 days |
`MERCHANT_NAME` | VARCHAR2 (250) | Merchant where the transaction took place |
`SETTLE_DATE` | VARCHAR2 (250) | Date on which the disputed transaction settled |
`DISPUTE_AMOUNT` | VARCHAR2 (250) | Amount disputed |
`PC_DATE` | VARCHAR2 (250) | Date when provisional credit was issued |
`PC_AMT` | VARCHAR2 (250) | Amount of provisional credit issued |
`PC_LETTER_DATE` | VARCHAR2 (250) | Date when a provisional credit letter was sent |
`PC_REVERSAL_DATE` | VARCHAR2 (250) | Date when a provisional credit was reversed |
`CH_LIABILITY_AMT` | VARCHAR2 (250) | Amount for which the cardholder is liable |
`RESOLUTION` | VARCHAR2 (250) | How the dispute was resolved |
`DATE_COMPLETE` | VARCHAR2 (250) | Date the dispute was resolved |
`CURRENT_STATUS` | VARCHAR2 (250) | Current status of the dispute |
`MCC` | VARCHAR2 (250) | Merchant category code for the transaction under dispute |
`CB_DATE` | VARCHAR2 (250) | Chargeback date |
`CB_AMT` | VARCHAR2 (250) | Chargeback amount |
`CB_REASON_CODE` | VARCHAR2 (250) | Chargeback reason code |
`SEC_PRESENTMENT_DATE` | VARCHAR2 (250) | Date of the second presentment |
`PRE_ARB_DATE` | VARCHAR2 (250) | Arbitration chargeback date |
`ENDING_STATUS` | VARCHAR2 (250) | Final status of dispute |
`FINAL_STATUS_DATE` | VARCHAR2 (250) | Date when `ENDING_STATUS` was input |
`CRED_RESOLUTION` | VARCHAR2 (250) | Date when provisional credit was finalized |
`AUTH_DATE` | VARCHAR2 (250) | Date when disputed transaction was authorized |
`AUTHORIZATION_CODE` | VARCHAR2 (250) | Authorization ID (`auth_id`) of the disputed transaction |
`SETTLE_DTL_ID` | VARCHAR2 (250) | Settlement detail ID |
`ASSOCIATION` | VARCHAR2 (250) | Association |
`PRN` | VARCHAR2 (250) | Payment reference number |
[Back to top](🔗)
### Direct Deposit Switch CDF
The Direct Deposit Switch CDF provides data on <a href="ref:direct-deposit-switch" target="_blank">direct deposit switch</a> 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`.
| CDF field name | Data type | Description |
`prod_id` | NUMBER (10,0) | Product ID |
`xid` | NUMBER (12,0) | Internal Galileo account ID |
`ddswitch_id` | VARCHAR (32) | Sequence number that is the primary key in the backend database |
`galileo_guid` | VARCHAR (32) | Unique ID for the direct deposit switch transaction |
`galileo_timestamp` | TIMESTAMP | Transaction timestamp in UTC of when the transaction was completed in ISO 8601 format |
`event_status` | VARCHAR (30) | Final status of the direct deposit switch transaction: `COMPLETED` or `FAILURE`. Incomplete transactions are not included. |
`distribution_type` | VARCHAR (10) | Type of distribution in `distribution_amount`: `Fixed`, `Percentage`, `Total` |
`distribution_amount` | NUMBER (20,2) | Amount of the deposit. |
`event_status_reason` | VARCHAR (50) | The reason for the status when `event_status: FAILURE`. See <a href="ref:api-reference-direct-deposit-switch-failure-status-reasons" target="_blank">Direct Deposit Switch Failure Status Reasons</a> for valid values. |
`vendor_selection` | VARCHAR (10) | Direct deposit switch vendor: `Atomic` or `Pinwheel` |
[Back to top](🔗)
### B2B Customer Master Supplemental CDF
The B2B Customer Master Supplemental CDF shows the relationship between <a href="doc:real-time-funding" target="_blank">Real-Time Funding</a> or <a href="doc:corporate-credit-limit" target="_blank">Corporate Credit Limit</a> 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`
| CDF field name | Data type | Description |
`BAL_ID` | VARCHAR2 (250) | The balance ID, or `galileo_account_number` of the spending account |
`PROG_ID` | VARCHAR2 (250) | Program ID |
`XID` | VARCHAR2 (250) | Internal account ID of the spending account |
`PRIMARY_PRN` | VARCHAR2 (12) | <<glossary:PRN>> of the spending account |
`FUNDING_PRN` | VARCHAR2 (12) | PRN of the funding account that is associated with `PRIMARY_PRN` |
`CH_GROUP_ID` | VARCHAR2 (10) | Group ID, if the account is part of a <a href="doc:about-corporate-hierarchy" target="_blank">Corporate Hierarchy</a>. |
[Back to top](🔗)
### MSI Installments CDF
The MSI Installments CDF contains information about <a href="doc:msi-installments" target="_blank">MSI Installments</a>. 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`.
| CDF field name | Source | Data type | Description |
`UNIQUE PROGRAM ID` | Galileo | NUMBER (18) | The identifier that Galileo has assigned to your <a href="doc:partners-programs-and-products" target="_blank">program</a>. |
`GALILEO ACCOUNT ID` | Galileo | NUMBER (18) | The balance ID, which is different from the account ID (PRN). It is possible for two or more accounts to share the same balance ID. |
`CARD IDENTIFIER` | Galileo | NUMBER (18) | Sometimes called the CAD, this identifier is given to each unique card that is issued to an account. If you are not PCI compliant, you can sometimes use this identifier instead of the PAN. |
`TRANSACTION DATE/TIME` | Galileo | DATETIME | The time that Galileo responded to the authorization request, or when a non-card transaction posted to the account |
`POST DATE` | Galileo | DATETIME | The date when Galileo posted the transaction to the customer account |
`TRANSACTION AMOUNT` | Galileo | NUMBER (9,2) | _Signed_. The amount that was posted to the account, in the currency of the account. In the case of a settlement, the amount may be different from its corresponding authorization amount. |
`INTERCHANGE FEE AMOUNT` | | NUMBER (9,2) | _Signed_. The amount of interchange or fee associated with this transaction. ATM fees and interchange reversals are negative; interchange earned is positive. This field is populated only for card transactions.<br><br>This value is rounded to 2 decimal places; for the full amount without rounding, see `IC FEE AMOUNT`. |
`TRANSACTION CODE/TYPE` | Galileo | CHAR (6) | The concatenation of the activity type (`act_type`) and the transaction type (`otype`). For an explanation of transaction codes see <a href="doc:about-transactions#classifying-transactions" target="_blank">Classifying transactions</a> in the _About Transactions_ guide. |
`TRANSACTION CURRENCY CODE` | DE049 | CHAR (3) | The currency code at the point of sale, for card transactions |
`AUTHORIZATION CODE` | Galileo | NUMBER (18) | A Galileo-generated identifier for an authorization, called `auth_id` in other contexts. For non-network transactions, this field contains the ID for the payment, adjustment, or fee. This ID is unique only per subnetwork or transaction type (payment, adjustment, fee), so there could be an ID collision between an authorization from Mastercard Banknet and a payment, for example. See <a href="doc:mapping-transactions-within-your-system" target="_blank">Mapping Transactions Within Your System</a> for more information. |
`MERCHANT NUMBER` | DE042 | CHAR (25) | An identifier that each network assigns to a merchant location. For non-card transactions, this may be a location ID provided by you or Galileo. |
`MERCHANT DESCRIPTION` | DE043 | CHAR (40) | Descriptive text provided by the merchant to identify the merchant name and location and sometimes the transaction type |
`MERCHANT CATEGORY CODE` | DE018 | NUMBER (18) | The ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on |
`MERCHANT COUNTRY CODE` | DE049 | VARCHAR2 (3) | The ISO 3166-1 three-digit code for the country where the merchant is officially located |
`EXTERNAL TRANSACTION ID` | DE038 | VARCHAR2 (60) | For network transactions, the authorization identification response in DE038, which is a numeric code that Galileo returns to a merchant to verify that the transaction was authorized. This number is often printed on customer receipts. For transactions initiated by the Program API, this is the `transactionId` of the API request. This field may be populated in other ways according to your setup and the transaction type. |
`NETWORK CODE` | Galileo | VARCHAR2 (1) | A single letter to specify the subnetwork over which the authorization request arrived. This field is populated only for card transactions. See <a href="ref:api-reference-card-authorization-network-codes" target="_blank">Network Codes</a> for possible values. |
`SOURCE ID` | Galileo | NUMBER (18) | For card transactions, the source ID is the same as the authorization ID. For other types of transactions, the source ID maps back to the original transaction, such as payment ID, adjustment ID or ACH transaction ID. The **ID** field in the CST corresponds to the source ID.<br><br>Keep in mind that the source ID is unique only to the transaction type or the subnetwork, so there could be a collision between a source ID for a payment and a source ID for an authorization, for example. |
`SOURCE TYPE` | | CHAR (1) | Type of source: `S` (settlements) or `A` (activity) |
`PRODUCT ID` | Galileo | NUMBER (18) | Identifier for the account's <a href="doc:partners-programs-and-products" target="_blank">product</a> in the Galileo system |
`TRANSACTION DESCRIPTION` | | VARCHAR2 (100) | Description for certain transactions |
`PRN` | Galileo | CHAR (12) | The payment reference number, a unique Galileo-generated identifier for an account |
`ACTIVITY ID` | Galileo | NUMBER | Identifier for the transaction in the activity table, which includes anything that affects the available balance; ID is unique per core |
`BATCH HEADER` | Nacha file | VARCHAR2 (94) | Record header for incoming ACH credits |
`SOURCE INSTITUTION NAME` | Nacha file | VARCHAR2 (35 bytes) | The source institution name for the incoming ACH credit |
`XID` | Galileo | NUMBER | Internal account identifier; has a 1:1 relationship with the PRN |
`GROUP ID` | | NUMBER | Identifier of the store where the card was sold |
`AUTH AMOUNT` | | NUMBER (9,2) | Amount that was authorized. |
`FOREIGN TRANSACTION INDICATOR` | Galileo | CHAR (1) | Whether the transaction is foreign relative to the account's country: `Y` (foreign) or `N` or null (domestic). This field is populated only for card transactions. |
`ROLLING BALANCE` | Galileo | NUMBER (9,2) | _Signed_. Available balance after this transaction took place. If you are the system of record instead of Galileo, this value may be inaccurate. |
`CASHBACK AMOUNT` | DE005 | NUMBER (9,2) | Amount of the transaction to give to the cardholder as cash |
`ARN` | | VARCHAR2 (23) | _Mastercard only_. Acquirer reference number |
`MESSAGE TYPE FLAG` | Galileo | CHAR (2) | The <a href="ref:api-reference-transaction-types" target="_blank">otype</a> of the authorization |
`LOCAL AMOUNT` | DE004 | NUMBER (16,4) | _Signed_. Transaction amount in the currency at the point of sale |
`LOCAL CURRENCY CODE` | DE049 | CHAR (3) | Currency code for `LOCAL AMOUNT` |
`SETTLE AMOUNT` | DE005 | NUMBER (16,4) | _Signed_. Transaction amount in the settlement currency |
`SETTLE CURRENCY CODE` | DE050 | CHAR (3) | Currency code for `SETTLEMENT AMOUNT` |
`BILLING AMOUNT` | DE006 | NUMBER (16,4) | _Signed_. Transaction amount in the billing currency, which is the cardholder account currency |
`BILLING CURRENCY CODE` | DE051 | CHAR (3) | Currency code for `BILLING AMOUNT` |
`REVERSAL ID` | Galileo | NUMBER | Contains the authorization ID of the previous authorization in a series, such as with incremental authorizations, reversals, and completions. See <a href="doc:about-transactions#linking-transactions" target="_blank">Linking transactions</a> in the _About Transactions_ guide for more information. |
`ORIGINAL AUTH CODE` | Galileo | NUMBER | Source ID for the transaction that this fee was assessed to |
`ASSOCIATION TRANS ID` | DE062 | VARCHAR2 (15) | _Visa only_. The transaction ID provided by the network |
`FULL MERCHANT DESCRIPTION` | DE043 | VARCHAR2 | Merchant name and full address and store number if provided by the network at the time of settlement |
`CCA FEE` | DE111 | NUMBER (9,2) | Currency conversion assessment (CCA) fee |
`MC SEQ COUNT` | Galileo | NUMBER (2) | Multi-clearing sequence count. Total number of clearings in this sequence |
`MC SEQ NUMBER` | Galileo | NUMBER (2) | Multi-clearing sequence number. Position of this clearing in the sequence |
`FILE ID` | Settlement file | VARCHAR2 (25) | _Visa only_. Identifier for the settlement file |
`SETTLE DATE` | Galileo | DATETIME | Date and time when the transaction was settled |
`TRACE NUMBER` | DE011<br>Nacha file | VARCHAR2 (20) | For a card transaction, an identifier from the merchant that is included with all messages related to that transaction.<br><br>For an ACH transaction the trace number assigned by Galileo to outgoing ACH transactions. |
`CARD PRESENT INDICATOR` | DE061 | CHAR (1) | Whether this was a card-present transaction: `Y` (card present) or `N` (card not present) |
`RECURRING TRANSACTION FLAG` | DE061 | CHAR (1) | Whether this is a recurring transaction: `Y` (recurring) or `N` (not recurring) |
`POS ENTRY MODE` | DE022 | NUMBER (2) | First two characters of DE022. How the PAN was entered, such as magnetic stripe, EMV chip, or contactless. See <a href="ref:api-reference-de022-codes" target="_blank">DE022 Codes</a>. |
`IS AFT TRANSACTION` | DE003 | CHAR (1) | Whether this is an account funding transaction: `Y` (AFT) or `N` (not AFT) |
`LOCAL SURCHARGE AMOUNT` | DE028 | NUMBER (16,4) | _Signed_. Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator |
`CASE SENSITIVE FLAG` | Galileo | VARCHAR2 (1) | Which case the otype in `TRANSACTION CODE/TYPE` is: `Y` (uppercase) , `N` (lowercase) or blank (not specified) |
`CONVERSION RATE – RECON` | DE009 | VARCHAR2 (8) | The currency conversion rate when converting `TRANSACTION AMOUNT` to `SETTLE AMOUNT`. See <a href="doc: secondary-rdf-reference#conversion-rates " target="_blank">Conversion rates</a> to interpret the value. |
`CONVERSION RATE – BILLING` | DE010 | VARCHAR2 (9) | The currency conversion rate when converting `TRANSACTION AMOUNT` to `BILLING AMOUNT`. See <a href="doc: secondary-rdf-reference#conversion-rates " target="_blank">Conversion rates</a> to interpret the value. |
`DRAWDOWN SETTLEMENT DATE` | | DATETIME | Date-time when the amount was taken from the issuing bank account |
`SETTLEMENT DATE` | DE015 | CHAR (4) | Date on which the card transaction settled |
`CREDIT INDICATOR` | Galileo | CHAR (1) | Whether the transaction arrived at Galileo over credit rails: `Y` (credit rails) or `N` (debit rails) |
`CONTACTLESS TRANSACTIONS` | DE022 | CHAR (1) | Whether the card was authenticated using contactless technology: `Y` (contactless) or `N` (not contactless) |
`MOBILE TRANSACTIONS` | Galileo | CHAR (1) | Whether a token requestor ID was present: `Y` (mobile wallet) or `N` (not mobile wallet) |
`ACTUAL POST DATE` | Galileo | DATETIME | Date-time when the ACH credit was posted to the account |
`ORIGINAL SETTLEMENT DATE` | Nacha file | DATETIME | Date-time when the ACH credit was originally to be posted |
`SETTLE DTL ID` | Galileo | NUMBER (18) | The identifier for the transaction in the settlement table. This field is populated only for card transactions. |
`ASSOCIATION` | Galileo | CHAR (3) | Three-letter abbreviation for the card network: <li>`DEB` (Maestro)<li>`MAS` (Mastercard credit)<li>`STA` (STAR)<li>`VIS` (Visa)<li>`DIS` (Discover)<li>`ALL` (Allpoint)<li>`PLS` (Pulse) |
`SOURCE` | Galileo | NUMBER (1) | Number assigned to a network: <li>`1` (Maestro)<li>`2` (Mastercard credit)<li>`3` (STAR)<li>`4` (Visa)<li>`5` (Discover)<li>`6` (Allpoint)<li>`7` (Pulse) |
`TOKEN REQUESTOR ID` | | VARCHAR2 (11) | Identifier for the token requestor. Present for mobile-wallet transactions. |
`ON_US` | | VARCHAR2 (20) | Remote deposit capture (RDC) check number |
`INTERCHANGE FEE AMOUNT` | | FLOAT (12,6) | _Signed_. Interchange fee amount |
`NAME` | Nacha file | VARCHAR2 | Payee name for direct deposit |
`DE28` | DE028<br>DE046 (Allpoint) | VARCHAR2 (9) | Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator |
`BAI` | DE104 | VARCHAR2 (3) | _Visa only_. <a href="ref:api-reference-business-application-identifier" target="_blank">Business Application Identifier</a>, which identifies the type of Visa card load |
`ICA` | | VARCHAR2 (6) | _Mastercard only_. Interbank Card Association number, assigned by Mastercard to a financial institution |
`POS TYPE` | DE003 | CHAR (3) | Type of card authentication at the point of sale: `SIG` (signature) or `PIN` |
`POS CONDITION CODE` | DE025 | VARCHAR2 (2) | The conditions under which the transaction took place at the point of sale. See <a href="ref:api-reference-de025-codes" target="_blank">DE025 Codes</a>. |
`ACQUIRING ID` | DE032 | VARCHAR2 (11) | Identifier for the merchant's acquirer |
`SETTLE SERVICE ID` | PDS0159SE4 | CHAR (10) | Uniquely identifies the settlement service |
`AVS CHECK` | DE063 | VARCHAR2 (50) | AVS check information |
`AUTHORIZATION STATUS` | Galileo | CHAR (1) | <a href="page:authorization-status-codes" target="_blank">Status</a> of the authorization |
`OTC_Flag` | DE003 | CHAR (1) | Whether the transaction included an over-the-counter cash advance: `Y` (cash advance) or `N` (no cash advance) |
`FEE PROGRAM INDICATOR` | DE063SE19 | VARCHAR2 (3) | _Visa only_. Interchange reimbursement fee program indicator, applied to select ATM transactions |
`AUTHORIZATION RESPONSE` | DE039 | CHAR (2) | The response code that you or Galileo returned to the network. See the <a href="ref:api-reference-events-authorization-response-codes" target="_blank">Authorization Response Codes</a> enumeration for possible values. |
`CHECK RETURN CODE` | | CHAR (3) | <a href="ref:api-reference-events-ach-return-codes" target="_blank">Code to indicate</a> why a paper check was returned |
`PRIOR ID` | Galileo | NUMBER (12) | The ID of a transaction that is linked to this transaction, such as the transaction that triggered this transaction |
`SECURE CODE` | PDS0052 | VARCHAR2 | _Mastercard only_. Secure code from the settlement file |
`CHECK NUMBER` | Galileo | NUMBER (19) | Number of the check |
`CST AGENT NAME` | Galileo | VARCHAR2 (125) | Name of the CST agent that initiated the transaction |
`TERMINAL ID` | DE041 | CHAR (8) | Identifier of the card reader |
`AUTH TRANSACTION CODE` | Galileo | VARCHAR2 (10) | The <a href="ref:api-reference-transaction-types" target="_blank">transaction code</a> (`act_type` + `otype`) |
`PIN FLAG` | Galileo | CHAR (1) | Whether a PIN was used to authenticate the card: `Y` (PIN) or `N` (no PIN) |
`SLI INDICATOR` | DE048SE42 | CHAR (1) | Security level indicator, included with Mastercard 3DS authentication |
`COMPANY NAME` | Nacha file | VARCHAR2 (20) | Company name for incoming ACH transactions |
`COMPANY DESC` | Nacha file | VARCHAR2 (15) | Company description for incoming ACH transactions |
`SETTLEMENT SERVICE CODE` | PDS0159SE3 | CHAR (1) | Identifies the settlement level of the settlement service: `1` or (regional) `3` (intracurrency) |
`SETTLEMENT SERVICE ID` | PDS0159SE4 | CHAR (10) | Uniquely identifies the settlement service |
`INTERCHANGE RATE DESIGNATOR` | PDS0158 | VARCHAR2 (2 bytes) | The interchange rate and editing rules applied to the transaction |
`POSTED EARLY` | Nacha file | CHAR (1) | Whether the ACH transaction was posted early: `Y` (early) or `N` (not early) |
`EFFECTIVE_DT` | Nacha file | DATETIME | For an ACH transaction, the effective date-time when the ACH payment should post. Usually set by the bank to the actual date when the payment is posted, in case Galileo posts the payment early. |
`RECEIVE DT` | Nacha file | DATETIME | Date-time that the Nacha file arrived at Galileo |
`LOAD_DT` | Nacha file | DATETIME | ACH load date (the date-time the incoming ACH was loaded) |
`SOURCE TRACE` | Nacha file | VARCHAR2 (20 bytes) | ACH trace number assigned by the external originating institution to incoming ACH transactions |
`ACH_RETURN CODE` | Nacha file | CHAR (3) | <a href="ref:api-reference-events-ach-return-codes" target="_blank">Code that indicates</a> why an ACH request was returned. |
`CST AGENT NAME` | Galileo | VARCHAR2 (125) | Name of the <<glossary:CST>> agent that initiated the transaction |
`TERMINAL NETWORK` | Galileo | VARCHAR2 (50) | Network that the card reader used |
`EXPIRED AUTH CODE` | Galileo | NUMBER (10) | `AUTHORIZATION CODE` of the expired authorization that corresponds to this force-posted transaction. This field is populated only for card transactions. |
`CCA FEE CURRENCY CODE` | DE111 | VARCHAR2 (3) | Currency code for `CCA FEE` |
`CCA FEE AMOUNT SETTLE` | DE111 | NUMBER (9,2) | Amount of the settlement on which the CCA fee was assessed |
`CCA FEE SIGN` | Galileo | VARCHAR2 (1) | CCA fee sign: `C` (credit) or `D` (debit) |
`RETRIEVAL_ REFERENCE_NUMBER` | DE037 | VARCHAR2 (12) | Retrieval reference number |
`REASON CODES` | DE044 | VARCHAR2 (25) | _Visa only_. Full contents of DE044, additional response data. |
`PDS0185` | PDS0185 | VARCHAR2 (33) | Accountholder authentication value (AAV) (Mastercard) or cardholder authentication verification value (CAAV) (Visa), returned for 3DS transactions |
`LOADS AUTH ID` | Galileo | NUMBER | Original authorization ID for card loads |
`PDS1002` | PDS1002 | VARCHAR2 (13) | Custom field |
`PDS1018` | PDS1018 | VARCHAR2 (13) | Custom field |
`REASON CODES` | | VARCHAR2 (1) | _Visa only_. First character only of DE044. The response source/reason code that identifies the source of the DE039 response. |
`ACH TRACE NUMBER` | | VARCHAR2 (20) | ACH trace number |
`IVA_TAX` | | NUMBER | _Mastercard only_. Impuesto al valor agregado. Value-added tax. Colombia only. |
`IAC_TAX` | | NUMBER | _Mastercard only_. Impuesto al consumo. Consumption tax. Colombia only. |
`IPM AUTH CODE` | Galileo | CHAR (6) | Numeric tag generated by Galileo during authorization, which is sent in the response, and then is returned in the settlement batch file to help link authorizations with settlements |
`MSG REASON CODE` | DE025 | CHAR (4) | _Mastercard only_. Indicates why a message was sent. Consult the Mastercard IPM Clearing Formats document to interpret the code. |
`MERCHANT POSTAL CODE` | | VARCHAR2 (5) | Postal code for the merchant's location. |
`CONVERSION RATE SETTLEMENT` | DE009 | VARCHAR2 (8) | _Visa only_. The currency conversion rate when converting `TRANSACTION AMOUNT` to `SETTLE AMOUNT`. See <a href="doc: secondary-rdf-reference#conversion-rates " target="_blank">Conversion rates</a> to interpret the value. |
`CONVERSION RATE` | DE010 | VARCHAR2 (8) | _Visa only_. The currency conversion rate when converting `TRANSACTION AMOUNT` to `BILLING AMOUNT`. See <a href="doc: secondary-rdf-reference#conversion-rates " target="_blank">Conversion rates</a> to interpret the value. |
`TRANSACTION LIFECYCLE ID` | DE063 | VARCHAR2 (16) | _Mastercard only_. Transaction lifecycle identifier, which allows tracking throughout a transaction's lifecycle |
`TRANSACTION LIFECYCLE ID/ ASSOCIATION TRANSACTION ID FOR ALL NETWORKS` | | VARCHAR2 (15) | Transaction lifecycle ID/ association transaction ID for all networks |
`PIN ENTRY CAPABILITY` | DE022 | CHAR (1) | Third character of DE022. Whether the card reader had PIN-entry capability. See <a href="ref:api-reference-de022-codes" target="_blank">DE022 Codes</a>. |
`DE60` | DE060 | VARCHAR2 (61) | Indicates the specific reason for an advice |
`DE121` | DE121 | CHAR (11) | Authorizing agent ID code, the actual processing facility that approved or declined an authorization request message |
`DE63_BRN` | DE063 | VARCHAR2 (9) | Banknet reference number; value received for Maestro updates |
`PDS0180` | PDS0180 | VARCHAR2 (20) | Domestic card acceptor tax ID. U.S. tax ID of the card acceptor |
`INSTALLMENTS CONDITIONS` | PDS0663 | NUMBER (9) | Details of the installment payments. Positions:<li>**1–2** — Type of credit (`03` Installments without interest)<li>**3–4** — Total number of installments<li>**5–6** — Grace period in months<li>**7–9** — Currency code |
[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 <a href="doc:fleet-cards" target="_blank">Fleet Cards</a> 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 <a href="doc:secondary-rdf-reference#posted-transactions-rdf-fields" target="_blank">Posted Transactions RDF</a>, matching the `AUTHORIZATION CODE` and `NETWORK CODE` fields in the RDF.
#### All rows
This table contains fields that are present in all row types.
| CDF field name | Data type | Description |
`prog_id` | NUMBER | <a href="doc:partners-programs-and-products" target="_blank">Program ID</a> of the card |
`bal_id` | NUMBER | Balance ID, Galileo account number of the card |
`cad` | NUMBER | Card ID |
`trans_ts` | DATE-TIME | Date-time when you or Galileo approved the transaction |
`trans_type` | CHAR (6) | <a href="ref:api-reference-transaction-types" target="_blank">Transaction type</a> |
`auth_code` | NUMBER | Authorization code or `auth_id`. This is the same as the `AUTHORIZATION CODE` in the Posted Transactions RDF. |
`post_ts` | DATE-TIME | Date-time when the transaction posted to the account |
`network_code` | VARCHAR2 (1) | <a href="ref:api-reference-card-authorization-network-codes" target="_blank">Network code</a>. This is the same as the `NETWORK CODE` field in the Posted Transactions RDF. |
`pmt_ref_no` | CHAR (12) | Payment reference number (PRN) of the card |
`prod_id` | NUMBER (18) | <a href="doc:partners-programs-and-products" target="_blank">Product ID</a> of the card |
`usage_code` | VARCHAR (2) | Indicates the type of addendum data provided. This value will always be `98` for any fleet-related addendum. |
`industry_rec_no` | NUMBER (3) | Industry record number: <li>`000` — Corporate card common data<li>`002` — Corporate fleet transaction information<li>`950` — Corporate line-item detail |
`occurrence_ind` | NUMBER (3) | Occurrence indicator. Specifies the position of the addendum relative to the original transaction, so line items 1–5 would have values 001–005, respectively. |
| Parsed data | VARCHAR (4000) | Further transaction data, according to the row: <li>[Row 1](🔗) — `corporate_card_detail`<li>[Row 2](🔗) — `fleet_detail`<li>[Rows 3–n](🔗) — `line_item_detail` |
##### 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`.
| CDF field name | Data type | Description |
`card_acceptor_type` | OBJECT | Contains all of the fields that begin with `business_`. Describes the type of business where the purchase was made, from PDS 0595. |
`_raw` | VARCHAR2 (8) | Raw, non-parsed contents of the object as sent by Mastercard. |
`business_type` | VARCHAR2 (1) | Code to identify the business type |
`business_owner_type` | VARCHAR2 (1) | Code to identify the type of business owner |
`business_cert_type` | VARCHAR (1) | Code to indicate the certification type of the business |
`business_eth_type` | VARCHAR (1) | Code to indicate the ethnicity of the majority owner of the business |
`business_type_code` | VARCHAR (1) | Whether the business type is provided |
`business_owner_type_code` | VARCHAR (1) | Whether the business owner type is provided |
`business_cert_type_code` | VARCHAR (1) | Whether the certification type is provided |
`business_eth_type_code` | VARCHAR (1) | Whether the business ethnic type is provided |
`card_acceptor_tax_id` | OBJECT | Contains the next three fields, which describe the U.S. federal tax ID or value-added tax ID from PDS 0596 |
`_raw` | VARCHAR2 (21) | Raw, non-parsed contents of the object as sent by Mastercard. |
`tax_id` | VARCHAR2 (20) | The tax ID of the card acceptor |
`tax_id_code` | VARCHAR2 (1) | Whether the card acceptor tax ID was provided |
##### Example
#### 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`.
| CDF field name | Data type | Description |
`oil_company_brand_name` | CHAR (4) | Code to indicate the brand name from PDS 0620 |
`purchase_time` | CHAR (4) | Purchase time at the point of sale from PDS 0621: `hhmm` |
`motor_fuel_service_type` | CHAR (1) | Type of service received at the card acceptor site from PDS 0622 |
`motor_fuel_information` | OBJECT | Object containing the fields that begin with `motor_`, which contain details about the motor fuel from PDS 0623 |
`_raw` | VARCHAR (35) | Raw, non-parsed contents of the object as sent by Mastercard. |
`motor_fuel_product_code` | VARCHAR2 (3) | The acquirer's motor fuel product code transacted from the information the attendant entered. The code refers to characteristics such as unleaded, diesel, regular leaded and methanol |
`motor_fuel_unit_price` | VARCHAR2 (12) | Price per unit |
`motor_fuel_unit_of_measure` | VARCHAR2 (1) | Motor fuel unit of measure |
`motor_fuel_quantity` | VARCHAR2 (6) | Motor fuel quantity |
`motor_fuel_sale_amount` | VARCHAR2 (12) | Total fuel sale price |
`odometer_reading` | VARCHAR2 (7) | Odometer reading from PDS 0629 |
`vehicle_number` | VARCHAR2 (17) | Vehicle number from PDS 0630 |
`driver_number` | VARCHAR2 (17) | ID of the driver from PDS 0631 |
`product_type_code` | CHAR (1) | Contains a code from the card's magnetic stripe that indicates prompts that occurred at the point of interaction, from PDS 0632 |
##### Example
#### 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`.
| CDF field name | Data type | Description |
`product_code` | VARCHAR2 (15) | Non fuel–related product code of the individual item purchased from PDS 0641 |
`item_description` | VARCHAR2 (35) | Object containing the fields that Item description from PDS 0642 |
`item_quantity` | OBJECT | Object containing the next three fields, which contain the item quantity from PDS 0643 |
`_raw` | VARCHAR2 (13) | Raw, non-parsed contents of the object as sent by Mastercard. |
`quantity` | VARCHAR2 (12) | Number of items purchased |
`quantity_exponent` | VARCHAR (1) | Identifies the implicit decimal point locations associated with each ISO standard currency code used in a message. For example, `2` means there are two positions after the decimal. |
`item_unit_of_measure` | VARCHAR2 (12) | Item unit of measure from PDS 0645 |
`item_unit_price` | OBJECT | Object containing the next three fields, which contain information about the unit price from PDS 0646 |
`_raw` | VARCHAR2 (13) | Raw, non-parsed contents of the object as sent by Mastercard. |
`unit_price` | VARCHAR (12) | Amount charged per unit purchased |
`unit_exponent` | VARCHAR (1) | Identifies the implicit decimal point locations associated with each ISO standard currency code used in a message. For example, `2` means there are two positions after the decimal. |
`extended_item_amount` | OBJECT | Object containing the next three fields, which contain information about the extended amount from PDS 0647. |
`_raw` | VARCHAR2 (14) | Raw, non-parsed contents of the object as sent by Mastercard. |
`extended_amount` | VARCHAR2 (12) | The individual item amount that is normally calculated as price multiplied by quantity |
`extended_amount_sign` | VARCHAR2 (1) | Whether the extended amount is a credit (`C`) or debit (`D`). |
`debit_or_credit_indicator` | VARCHAR2 (1) | Whether the net of `extended_item_amount` is a debit (`D`) or a credit (`C`) to the cardholder account |
##### Example
[Back to top](🔗)