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](🔗)
[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 |
### 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 |
### 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 |
### 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 |
### 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 |
### 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 |
### 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) | |
### 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 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 |
### 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 ` |
### 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 |