Product RDFs
The Product RDFs contain data for specific SoFi Tech Solutions products. See About the Raw Data Files (RDFs) for general information on RDFs.
- ACH
- ACH Returns — Data on ACH transactions that were returned on the previous day.
- Early ACH — Data for incoming ACH credit transactions that were posted early, along with the number of days they were posted early.
- Incoming ACH — Data on all incoming ACH transactions for the prior day, including both ACH debits and ACH credits.
- Incoming ACH Manual Review — Data on all incoming ACH transactions available in the manual review queue.
- Outgoing ACH — Data on all outgoing ACH credits for the prior day, excepting bank holidays and weekends.
- B2B Customer Master Supplemental — Showing which RTF or Corporate Credit funding accounts are linked to which spending accounts.
- Bad PAN Authorizations — Authorization requests from card numbers with your BIN, but the PAN does not exist in the system.
- Credit — Data on credit accounts (primary and authorized users)
- Direct Deposit Switch — Data on direct deposits set up using the switch.
- Fleet Data — Data on all transaction activity of fleet-card profiles along with additional level 2 and 3 data.
- Fraud Rule Detail — Data on transactions that triggered fraud rules.
- Frequent Disputer — Dispute-related data on individual accounts, including statistics on dispute frequency and funds lost and won.
- Interest Savings Supplemental (ISS) — Data on interest-bearing accounts: interest accrual, interest year-to-date, and annual percentage yield earned for a savings account
- Monthly Interest Savings — Soon-to-come replacement for the ISS RDF.
- MSI Installments — Data on MSI installments, a Mexico product.
- Overdraft Details — Information related to overdraft accounts and transactions.
- Payment Method Switch — Data on payment method switch transactions.
- Secondary Accounts — Newly documented. All accounts not included in the Customer Master RDF.
ACH Returns RDF
The ACH Returns RDF offers insights into returns that SoFi Tech Solutions performs for incoming ACH transactions. When processing an incoming ACH transaction, SoFi Tech Solutions may return a transaction in any of the following ways:
- The SoFi Tech Solutions platform automatically initiates a return based on Nacha rules.
- A SoFi Tech Solutions or client-side operations agent manually initiates a return through the CST.
- A client-side operations agent uses a third-party web tool that calls the Program API to initiate the return.
This report does not include data on returns for ACH transactions originated on the SoFi Tech Solutions platform. You can find that data in the Outgoing ACH RDF.
July–Aug 2026 changes to this RDF
- Currency amounts are now rendered as
15.0instead of15.00.- Trailing spaces have been removed from
Transaction Type.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- Duplicate entries are no longer produced.
- New fields added at the end:
PRN,Program ID,Product ID- PascalCase field names are now separate words:
Source Name,Deb Cred Indicator,Received Date,Effective Date,Return Date,Return Reason Code,Return Reason Description,Trans ID
Insights for you
- Identify the reasons for high return rates and develop a plan in place to address it
- Identify potential fraudulent ACH activity based on return codes
This table contains default fields for the ACH Returns RDF.
- The primary key for this file is
Trans ID. - The filename format is
ach_returns_report_%Y%m%d.csv. - All
DATETIMEfields areYYYY-MM-DD h24:mm:ss. - Consult ACH Tracking and Troubleshooting for more information on the various transaction IDs.
| Field name | Data type | Description |
|---|---|---|
Name | VARCHAR2 (80) | Name of recipient |
Source Name | VARCHAR (30) | Source institution name |
Amount | NUMBER | Amount of the ACH transaction |
Deb Cred Indicator | CHAR (1) | Debit/credit indicator. D = debit; C = credit |
Received Date | DATETIME | Timestamp for when we received the returned transaction |
Effective Date | DATETIME | Timestamp for when the ACH transaction was to take effect (without early ACH) |
Return Date | DATETIME | Date the transaction was returned |
Return Reason Code | CHAR (3) | Return reason code |
Return Reason Description | VARCHAR2 (255) | Return reason description |
Trans ID | CHAR (2) | Transaction ID |
XID | NUMBER | System-generated internal account ID; has a 1:1 relationship with the PRN |
PRN | NUMBER | The payment reference number, a unique system-generated, customer-facing identifier for an account |
Trace | NUMBER | Source trace number |
Source Routing | NUMBER | Source routing number |
Destination Routing | NUMBER | Destination routing number |
Company ID | NUMBER | Source company ID |
Return Trace | NUMBER | Return trace number |
Program ID | NUMBER | ID for your program as assigned by SoFi Tech Solutions |
Product ID | NUMBER | ID for a product as assigned by SoFi Tech Solutions |
Settlement Date | DATETIME | Timestamp for when the transaction was posted |
Early ACH RDF
The Early ACH RDF provides data for incoming ACH credit transactions that were posted early, along with the number of days they were posted early. You can use this data to analyze the benefit of using early ACH as a service and for your reconciliation needs. Because early ACH applies to incoming ACH transactions, you can also see these transactions in the Incoming ACH RDF.
July–Aug 2026 changes to this RDF
- Currency amounts are now rendered as
15.0instead of15.00.- Trailing spaces have been removed from
Transaction Type.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- New fields added:
CAD,Category,Subcategory,Early Days,Posting Date
Insights for you
- In conjunction with other RDFs, correlate the effects of early ACH on driving spend
- Identify changes in direct-deposit enrollment rate.
This table contains standard fields for the Early ACH RDF.
- The primary key for this file is
Transaction ID. - The filename format is
early_ach_report_%Y%m%d.csv. - All
DATETIMEfields areYYYY-MM-DD h24:mm:ss. - Consult ACH Tracking and Troubleshooting for more information on the various transaction IDs.
| Field name | Data type | Description |
|---|---|---|
Transaction ID | VARCHAR2 (2) | Maps as identifier for the source of load/payment or source of the 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 client or partner |
Transaction Time | DATE | Transaction time of the ACH record |
Authorization Code | NUMBER (18) | A system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions. |
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 | DATETIME | ACH effective date (when the Nacha file says it would have posted without early ACH) |
Settlement Date | DATETIME | The date the transaction was settled/posted |
Receive Date | DATETIME | ACH file date (the date the Nacha file was received) |
Load Date | DATETIME | ACH load date (the date the ACH transaction was written to a Nacha file) |
Amount | NUMBER | Amount of the ACH transaction |
PRN | CHAR (12) | The payment reference number, a unique system-generated, customer-facing identifier for an account |
Trace Number | NUMBER | ACH trace number as received by SoFi Tech Solutions |
Product ID | NUMBER | ID for a product as assigned by SoFi Tech Solutions |
Program ID | NUMBER | ID for your program as assigned by SoFi Tech Solutions |
CAD | NUMBER | Card identifier or card_id, a system-generated ID that has a 1:1 relationship to the PAN. Use this ID when you are not PCI-compliant. |
Category | VARCHAR | High-level ACH transaction type |
Subcategory | VARCHAR | Detailed ACH transaction type within the category. |
Early Days | NUMBER | The number of days the transaction is made available early. |
Posting Date | DATETIME | Timestamp for when the transaction was posted to the account. |
Incoming ACH RDF
The Incoming ACH RDF provides data for all incoming ACH transactions for the prior day, including both ACH debits and ACH credits. This file helps you reconcile ACH transactions.
July–Aug 2026 changes to this RDF
- Description updates to
Company Name,Company ID,Company Name- Currency amounts are now rendered as
15.0instead of15.00.- Trailing spaces have been removed from
Transaction Type.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- Non-ACH transactions are no longer included in this file.
Autorizationchanged toAuthorization
This table contains default fields for the Incoming ACH RDF.
- The primary key for this file is
Authorization Code+Transaction Type. - The filename format is
incoming_ach_report_%Y%m%d.csv.
| Field name | Data type | Description |
|---|---|---|
Company Name | VARCHAR2 (20) | Originator name from the Nacha Batch Header Record (positions 5–20, 16 chars). Identifies the company or individual that initiated the ACH entry. |
Company ID | NUMBER | Originator identification from the Nacha Batch Header Record (positions 41–50, 10 chars). Typically a FEIN preceded by a number-type indicator. |
Company Description | VARCHAR2 (15) | Company Entry Description from the Nacha Batch Header Record (positions 54–63, 10 chars). Describes the purpose of the entries as established by the Originator (e.g., PAYROLL, PAYMENT, REFUND). |
Individual Name | VARCHAR2 (80) | Individual name |
Individual ID | NUMBER | Individual ID |
Authorization Code | NUMBER | A system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions. |
Transaction Type | VARCHAR2 (2) | Transaction type |
Amount | NUMBER | Amount. One place after the decimal. |
Trace Number | NUMBER | Trace number |
PRN | CHAR (12) | The payment reference number, a unique system-generated, customer-facing identifier for an account |
Incoming ACH Manual Review RDF
The Incoming ACH Manual Review RDF offers data on transactions added to the manual review queue and actioned on the previous day, as well as any unactioned transactions added within the last 7 days.
July–Aug 2026 changes to this RDF
- Description updates to
COMPANY_NAME,COMPANY_ID,COMPANY_NAMEGALILEO_SYSTEM_MIDDLE_NAME→GALILEO_MIDDLE_NAMEGALILEO_SYSTEM_LAST_NAME→GALILEO_LAST_NAMEDESTINATION_ACCOUNT_NOis now decrypted.- Now including the transactions added to the manual review queue on the previous day plus unactioned transactions from the last 7 days.
- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- Non-ACH transactions are no longer included in this file.
AMOUNTis unsigned: noDorCto indicate debit or credit; useCOMPANY_ENTRY_DESC
Insights for you
Transactions that meet certain criteria enabled for the program are queued, such as threshold validation or name mismatch.
This table contains default fields for the Incoming ACH Manual Review RDF.
- The primary key for this file is
TRANS_ID. - The filename format is
incoming_ach_manual_review_%Y%m%d.csv. - All
DATETIMEfields areYYYY-MM-DD h24:mm:ss.
| Field name | Data type | Description |
|---|---|---|
COMPANY_NAME | VARCHAR2 | Originator name from the Nacha Batch Header Record (positions 5–20, 16 chars). Name of the institution sending a credit or debit to a Galileo account |
COMPANY_ID | VARCHAR2 | Originator identification from the Nacha Batch Header Record (positions 41–50, 10 chars). ID of the institution |
COMPANY_ENTRY_DESC | VARCHAR2 | Company Entry Description from the Nacha Batch Header Record (positions 54–63, 10 chars). Describes the purpose of the entries as established by the Originator (e.g., PAYROLL, PAYMENT, REFUND). |
INDIVIDUAL_NAME | VARCHAR2 | Receiver’s name. |
GALILEO_SYSTEM_FIRST_NAME | VARCHAR2 | First name in system records. |
GALILEO_SYSTEM_MIDDLE_NAME | VARCHAR2 | Middle name in system records. |
GALILEO_SYSTEM_LAST_NAME | VARCHAR2 | Last name in system records. |
AMOUNT | NUMBER | Transaction amount |
TRACE_NUMBER | VARCHAR2 | 15-digit number used to track inbound ACH transfers. See ACH Tracking and Troubleshooting to see how this value is represented across the systems. |
DESTINATION_ACCOUNT_NO | VARCHAR2 | The payment reference number, a unique system-generated, customer-facing identifier for an account. |
SETTLEMENT_DATE | DATETIME | Timestamp for when the transaction was settled. |
PRESENTMENT_DATE | DATETIME | Timestamp for when the transaction was returned. |
TRANS_ID | NUMBER | Unique system-generated identifier for the ACH transaction. Corresponds to the pmt_id and/or adj_id. |
RETURN_CODE | VARCHAR2 | Standard code selected by the agent if the action taken on the transaction is a return. |
RETURN_DESC | VARCHAR2 | CST field that provides the description of the return. Not included in the Nacha file. |
ACTION | VARCHAR2 | Action taken by the CST agent on the transaction in manual review. Valid values are Post, Force Post, Return, or Pending Action. |
CST_USER_ID | NUMBER | The user ID of the CST agent that reviewed the transaction and took action on it. This field is blank if an action was not taken at the time this report was generated. |
CST_USER_NAME | VARCHAR2 | The name of the CST agent that reviewed the transaction and took action on it. This field is blank if an action was not taken at the time this report was generated. |
Outgoing ACH RDF
The Outgoing ACH RDF provides data for ACH credits and debits that SoFi Tech Solutions originated on the previous day. This file includes transactions that either debit or credit the SoFi Tech Solutions account.
July–Aug 2026 changes to this RDF
- New fields:
REMITTANCE_INFO,RECORD_TYPE,PMT_ID,XID,DSCR- New primary key, as shown below. Was:
ORIG_TRACE- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>RECORD_TYPE: Frows will not have return data in these fields:RETURN_DT,RETURN_CODE- You will see more rows for returns, because we will include the original forward.
- You will see fewer rows because we won't include non-financial ACH activities (
Ccodes); we only showR(return) codes.- Currency amounts are now rendered as
15.0instead of15.00.- Column header
RECIEVED→RECEIVED.- The
NAMEfield supports this character set.
This table contains default fields for the Outgoing ACH RDF.
- The primary key for this file is
SOURCE_TRACE+RECORD_TYPE+ADJ_ID+RETURN_DT - The filename format is
ach_out_report_%Y%m%d.csv.
Notice
On weekends (Saturday and Sunday) and bank holidays, our internal processes generate and send empty files for this RDF. For example, if the 10th is a Saturday and the 11th is a Sunday, then the RDFs you receive on the 11th and the 12th will contain no data.
| Field name | Data type | Description |
|---|---|---|
ORIG_TRACE | NUMBER | Trace number |
NAME | VACHAR | Name, which supports this character set |
PMT_REF_NO | NUMBER | The payment reference number, a unique system-generated, customer-facing identifier for an account |
SCHEDULED_DT | DATE | Scheduled date |
DEB_CRED_IND | CHAR (1) | Debit/credit indicator: C (credit); D (debit) |
FILE_DT | DATE | File date |
AMOUNT | NUMBER | Amount of the transaction |
FILENAME | VARCHAR2 (255) | File name |
TRANS_TYPE | CHAR (6) | Transaction type |
RETURN_CODE | VARCHAR2 (20) | Return reason code |
RECEIVED | VARCHAR2 (20) | Transaction received |
RETURN_DT | DATE | Date the transaction was returned |
SOURCE_TRACE | NUMBER | Source trace number |
EFFECTIVE_DT | DATE | Date range for the transaction originated |
SAME_DAY | CHAR (1) | Indicates whether the transaction was sent as a Same Day ACH |
PROG_ID | NUMBER | Program ID |
PROD_ID | NUMBER | Product ID |
ADJ_ID | NUMBER | Identifier for funds removed from the local account. |
REMITTANCE_INFO | VARCHAR | Description for the remittance as provided in the remittanceInfo field of the Create ACH Transaction endpoint. |
RECORD_TYPE | VARCHAR | F for forward or R for return |
PMT_ID | NUMBER | Identifier for funds added to the local account. |
XID | NUMBER | System-generated internal account ID; has a 1:1 relationship with the PRN |
DSCR | VARCHAR | ACH transaction description, from the description field of the Create ACH Transaction endpoint. |
B2B Customer Master Supplemental RDF
The B2B Customer Master Supplemental RDF shows the relationship between Real-Time Funding or Corporate Credit spending accounts and their respective funding accounts. It also provides balances for the funding accounts.
July–Aug 2026 changes to this RDF
CH_GROUP_IDis now being populated.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- The
_BALANCEfields now contain15.0instead of15.00.
This table contains default fields for the B2B Customer Master Supplemental RDF.
- The primary key for this file is
PRNorXID. - The filename format is
b2b_custmaster_supplemental_%y%m%d.csv
| Field name | Data type | Description |
|---|---|---|
PROG_ID | VARCHAR2 (250) | Program ID |
PROD_ID | VARCHAR2 (250) | Product ID of the account in PMT_REF_NO. With this field you can distinguish between funding and spending accounts. |
BAL_ID | VARCHAR2 (250) | The balance ID, or galileo_account_number of the account in PMT_REF_NO. |
XID | VARCHAR2 (250) | Internal account ID of the account in PMT_REF_NO. |
PMT_REF_NO | VARCHAR2 (12) | The payment reference number, a unique system-generated, customer-facing identifier for an account |
FUNDING_PRN | VARCHAR2 (12) | PRN of the funding account that is associated with the spending account in PMT_REF_NO. When this field is not populated, then PMT_REF_NO is a funding account. |
CH_GROUP_ID | VARCHAR2 (10) | Group ID, if the account is part of a Corporate Hierarchy. |
AVAILABLE_BALANCE | NUMBER (10,2) | The amount available to spend (open to buy) for the funding account, meaning the total posted/settled minus the pending authorizations of all related spending accounts. This field should be 0 for spending accounts. |
RTF_CURRENT_BALANCE | NUMBER (10,2) | The ledger balance of the RTF funding account. This field should be 0 for spending accounts. |
Bad PAN Authorizations RDF
The Bad PAN Authorizations RDF contains a list of authorization requests from card numbers with your BIN, but the PAN does not exist in the system. These attempted transactions could be fraudulent.
July–Aug 2026 changes to this RDF
- This RDF replaces the Invalid Card Transaction RDF.
BILLING AMOUNTretains the original sign.SLI INDICATORshows a single digit rather than the full DE048 string.TRANSACTION TYPEcontains theauth_tran_typevalue instead of the whole DE003 string.NETWORK CODEcontains the correct value instead ofMfor all instances.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- New fields added:
AUTHORIZATION CODE(first column),REVERSAL ID,ASSOCIATION TRANS ID,BAI,TERMINAL NETWORK- Some RDFs had a
CADfield; this file containsAUTHORIZATION CODEinstead.- Currency amounts are now rendered as
15.0instead of15.00.- Trailing spaces trimmed from these fields:
ADVICE REASON CODE,MESSAGE TYPE FLAG,TERMINAL ID
This table contains default fields for the Bad PAN Authorizations RDF.
- The primary key for this file is
AUTHORIZATION CODE. - The filename format is
[client]_badpan_authorizations_%Y%m%d.csv - All
DATETIMEfields areYYYY-MM-DD h24:mm:ss. - See Data Elements to correlate the DEs with other SoFi Tech Solutions resources.
| Field name | Source | Data type | Description |
|---|---|---|---|
AUTHORIZATION CODE | SoFi Tech Solutions | NUMBER | A system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions. |
TRANSACTION DATE/TIME | SoFi Tech Solutions | DATETIME | Timestamp when SoFi Tech Solutions responded to the authorization request, or when a non-card transaction posted to the account |
TRANSACTION CURRENCY CODE | DE049 | CHAR (3) | The currency code at the point of sale, for card transactions |
ADDRESS VERIFICATION RESPONSE | SoFi Tech Solutions | CHAR (1) | The single-character result of the AVS check that SoFi Tech Solutions passed to the network. See AVS-only checks in the _Authorization_ guide. |
AUTHORIZATION RESPONSE | DE039 | CHAR (2) | The response code that you or SoFi Tech Solutions returned to the network. See the Authorization Response Codes enumeration for possible values. |
TRANSACTION AMOUNT | DE004 | NUMBER | Signed. The amount in the authorization request. |
NETWORK CODE | SoFi Tech Solutions | VARCHAR2 (1) | A single-letter identifier to specify the subnetwork over which the authorization request arrived. See Network Codes for possible values. |
MERCHANT NUMBER | DE042 | CHAR (15) | An identifier that each network assigns to a merchant location |
MERCHANT DESCRIPTION | DE043 | CHAR (40) | Descriptive text provided by the merchant to identify the merchant name, location and sometimes the transaction type |
MERCHANT CATEGORY CODE | DE018 | NUMBER | The ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on |
TRANSACTION CODE | DE003 | CHAR (2) | A version of the processing code, which corresponds to the type of transaction. |
MERCHANT COUNTRY CODE | DE049 | VARCHAR2 (3) | The ISO 3166-1 three-digit code for the country where the merchant is officially located |
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 SETTLE 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 |
CASHBACK AMOUNT | DE005 | NUMBER (9,2) | Amount of the transaction to give to the cardholder as cash |
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 DE022 Codes. |
PIN ENTRY CAPABILITY | DE022 | CHAR (1) | Third character of DE022. Whether the card reader had PIN-entry capability. See DE022 Codes. |
LOCAL SURCHARGE AMOUNT | DE028 | NUMBER (16,4) | Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator |
MESSAGE TYPE FLAG | SoFi Tech Solutions | CHAR (2) | The otype of the authorization |
AUTHORIZATION STATUS | SoFi Tech Solutions | CHAR (1) | Status of the authorization |
POS CARDHOLDER PRESENCE | CHAR(1) | Indicates whether the cardholder was present at the point of sale: 0 (present) or 1 (not present) | |
AUTHORIZATION IDENTIFICATION RESPONSE | DE038 | Transaction response identification code assigned by the authorizing institution | |
SLI | VARCHAR2 (19) | Security level indicator | |
SLI INDICATOR | DE048 SE42 | CHAR (1) | Security level indicator, included with Mastercard 3DS authentication |
TERMINAL ID | DE041 | CHAR (8) | Identifier of the card reader |
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. | |
AAV INDICATOR | DE048 SE43 | CHAR (2) | Universal cardholder authentication field (UCAF) or account holder authentication value (AAV) |
STIP RESPONSE | DE039 | CHAR (2) | _Mastercard only_. The response code that the network returned to the merchant during stand-in processing (STIP) |
ADVICE REASON CODE | DE060 | VARCHAR2 (61) | Indicates the specific reason for an advice. |
AUTHORIZING AGENT ID CODE | DE121 | CHAR (11) | Authorizing agent ID code. The actual processing facility that approved or declined an authorization request message |
MESSAGE TYPE IDENTIFIERS | CHAR (3) | The message type identifier for the authorization request, minus the first digit | |
BANKNET REFERENCE NUMBER | DE063 | VARCHAR2 (9) | Value received for Maestro updates |
REVERSAL ID | SoFi Tech Solutions | NUMBER | Contains the authorization ID of the previous authorization in a series, such as with incremental authorizations, reversals, and completions. |
ASSOCIATION TRANS ID | DE062 | VARCHAR2 (15) | Visa only. Transaction identifier that was assigned by the network |
BAI | DE104 | VARCHAR2 (3) | Visa only. Business Application Identifier, which identifies the type of Visa card load |
TERMINAL NETWORK | SoFi Tech Solutions | VARCHAR2 (50) | Network that the card reader used |
Credit RDF
The Credit RDF is the primary data source about credit accounts and includes information related to billing cycle activity and delinquency for compliance reporting, reconciliation, and internal analytics. The Credit RDF is delivered daily via secure file transfer (SFTP).
- The primary key for this file is
BAL_ID - The filename format is
credit_rdf_YYYYMMDD.csv
| Field Name | Data type | Description |
|---|---|---|
BAL_ID | NUMBER | The balance ID, also called the Galileo account number, of the primary account. This is different from the PRN. |
PROD_ID | NUMBER(18) | Identifier for the account's product in the system |
ACCOUNT_STATUS | VARCHAR | Specifies the state of an account. See Account Statuses for a complete list. |
PMT_REF_NO | VARCHAR(12) | The payment reference number, a unique system-generated, customer-facing identifier for an account |
LAST_CYCLE_PAYMENT_STATUS | VARCHAR | Payment status of the last complete billing cycle. Possible values: UNPAIDPAIDPAST DUEZERO_BALANCE |
LAST_CYCLE_CLOSE_DATE | DATE | Date the last billing cycle ended |
LAST_CYCLE_DUE_DATE | DATE | Due date of last billing cycle |
LAST_CYCLE_DELINQUENCY_DATE | DATE | Date when the account became delinquent in the last billing cycle, if applicable |
LAST_CYCLE_BILL_AMOUNT | NUMBER | Total amount due at the end of the last billing cycle, including late fees |
LAST_CYCLE_AMOUNT_PAID | NUMBER | Total amount paid towards the last billing cycle |
LAST_CYCLE_AMOUNT_PAST_DUE | NUMBER(16,2) | Total amount due from unpaid minimum payments in prior billing cycles |
LAST_CYCLE_PAYMENT_RECEIVED_DATE | DATE | The timestamp of the most recent payment applied to any unpaid billing cycles on the account |
TOTAL_LATE_FEES_DUE | NUMBER(16,2) | The total amount of late fees currently due |
CURRENT_CYCLE CLOSE_DATE | DATE | Forecasted last date of the current billing cycle |
CURRENT_CYCLE_DUE_DATE | DATE | Due date of the current billing cycle |
CURRENT_CYCLE_AMOUNT_PAID | NUMBER | Total amount paid in the current billing cycle |
Direct Deposit Switch RDF
The Direct Deposit Switch RDF provides data on direct deposit switch transactions.
July–Aug 2026 changes to this RDF
- File name in all lower-case letters.
- Field names are now in CAPITAL_SNAKE_CASE instead of snake_case.
- New fields:
PRODUCT,PAYMENT_TYPE,COMPANY,ACCOUNT_TYPE- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>
This table contains default fields for the Direct Deposit Switch RDF.
- The primary key for this file is
GALILEO_GUID. - The filename format is
ddswitch_transactions_%Y%m%d.csv.
| Field name | Data type | Description |
|---|---|---|
PROD_ID | NUMBER (10,0) | Product ID |
XID | NUMBER (12,0) | Internal Galileo account number |
GALILEO_GUID | VARCHAR (32) | Unique ID for the direct deposit switch transaction |
GALILEO_TIMESTAMP | TIMESTAMP | Timestamp in UTC for 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 Direct Deposit Switch Failure Status Reasons for valid values. |
VENDOR_SELECTION | VARCHAR (10) | Direct deposit switch vendor: Atomic |
PRODUCT | VARCHAR | Product name |
PAYMENT_TYPE | VARCHAR | Payment type |
COMPANY | VARCHAR | Name of employer company |
ACCOUNT_TYPE | VARCHAR | Account type |
Fleet Data RDF
The Fleet Card RDF provides data on all transaction activity of fleet-card profiles along with additional level 2 and 3 data. This file can be used to predict transaction volume and interchange revenue by forecasting driver spend, expected fuel refill timing and transaction amount. Additionally, you can identify any dormant fleet cards, monitor for any fraudulent transactions outside of normal fleet-card operations, utilize fleet-card data to develop spend and driver controls, etc.
This RDF also contains specific data that will help provide insights to corporate customers of driver spend patterns and vehicle usage. Additionally, given Mastercard's new fleet mandates, this RDF also includes all new enhanced data elements needed to meet the new fleet card data capabilities.
Insights
This file provides key insights for both you and your business customers. For example, it helps you calculate the AMPG:
AMPG = (current odometer reading (PDS 0629) – previous odometer reading) / (previous number of fuel gallons purchased (PDS 0643))
Insights for your business customers
- Vehicle lifetime value
- Average vehicle lifetime mileage
- Percentage each vehicle has reached
- Driver performance
- AMPG per driver
- Budgeting
- ((driver AMPG) x (number of fuel gallons filled)) / (miles driven per day) = predict when the driver will refuel next
Insights for you
- Number of inactive fleet cards that you deactivate to save costs
- Identify and block atypical transactions based on driver's spend history
- Provide rewards and promote stickiness utilizing fuel company brand data
- Forecast revenue using frequency of driver refueling events and average spend.
Expected monthly interchange = (interchange %) x (average cost of fuel refill) x (days in month) /(((AMPG) x (number of fuel gallons purchased)) / (miles driven per day))
File information
- 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 RDF, 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) or18(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 RDF 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.
| Field name | Data type | Description |
|---|---|---|
prog_id | NUMBER (18) | The identifier that SoFi Tech Solutions has assigned to your program |
bal_id | NUMBER | The balance ID or SoFi Tech Solutions account ID, which is different from the PRN. It is possible for multiple PRNs to share the same balance ID. |
cad | NUMBER | Sometimes called the card_id, this identifier is given to each unique card that is issued to an account. There is a 1:1 relationship between a card ID and a PAN. If you are not PCI compliant, you can use this identifier instead of the PAN. |
trans_ts | DATE-TIME | Date-time when you or SoFi Tech Solutions approved the transaction |
trans_type | CHAR (6) | Transaction type |
auth_code | NUMBER | A system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions. |
post_ts | DATE-TIME | Date-time when the transaction posted to the account |
network_code | VARCHAR2 (1) | Network code. This is the same as the NETWORK CODE field in the Posted Transactions RDF. |
pmt_ref_no | CHAR (12) | The payment reference number, a unique system-generated, customer-facing identifier for an account |
prod_id | NUMBER (18) | Identifier for the account's product in the system. |
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: 000 — Corporate card common data002 — Corporate fleet transaction information950 — 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: corporate_card_detailfleet_detailline_item_detail |
Click to see examples and subfields
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.
| 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
{
"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.
| 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 | CHAR2 (35) | Raw, non-parsed contents of the object as sent by Mastercard. |
motor_fuel_product_code | CHAR2 (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 | CHAR2 (12) | Price per unit |
motor_fuel_unit_of_measure | CHAR2 (1) | Motor fuel unit of measure |
motor_fuel_quantity | CHAR2 (6) | Motor fuel quantity |
motor_fuel_quantity_exponent | CHAR (1) | Contains the exponent indicating the decimal position of the quantity of the motor fuel item being purchased |
motor_fuel_sale_amount | CHAR2 (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 |
fleet_spend_control_enforced | CHAR2 (16) | Informs issuers of the purchase restrictions enforced by the merchant point of sale from PDS 0781. Must be a fixed length of 16 and cannot contain all zeros or all spaces |
fleet_fuel_information | OBJECT | Contains the acquirer's Fleet fuel product code translated from the information the attendant entered from PDS 0782 |
_raw | CHAR2 (35) | Raw, non-parsed contents of the object as sent by Mastercard |
fleet_fuel_product_code | CHAR2 (3) | Contains a three-digit code that identifies the fuel item purchased |
fleet_fuel_unit_price | CHAR2 (12) | Contains the price per unit of the item being purchased |
fleet_fuel_unit_of_measure | CHAR (1) | Contains the code indicating the unit of measure for the fuel item purchased |
fleet_fuel_quantity | CHAR (6) | Contains quantity of the fuel item purchased |
fleet_fuel_quantity_exponent | CHAR (1) | Contains the exponent indicating the decimal position of the quantity of the fuel item being purchased |
fleet_fuel_sale_amount | CHAR (12) | Contains the sale amount of the fuel item being purchased |
fleet_prompted_data_1 | OBJECT | Contains the Prompt Code read from a card chip that indicates prompts that occur at the point of interaction and the data entered in response by the cardholder into the point-of-sale device from PDS 0790 |
_raw | VARCHAR (38) | Raw, non-parsed contents of the object as sent by Mastercard |
prompt_code_1 | CHAR (3) | Contains a code that specifies the information requested to be provided by the cardholder at the POI, e.g. 005 (odometer) |
driver_related_data_1 | VARCHAR (35) | Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 81523 |
fleet_prompted_data_2 | OBJECT | Contains the Prompt Code read from a card chip that indicates prompts that occur at the point of interaction and the data entered in response by the cardholder into the point-of-sale device from PDS 0791 |
_raw | VARCHAR (38) | Raw, non-parsed contents of the object as sent by Mastercard |
prompt_code_2 | CHAR (3) | Contains a code that specifies the information requested to be provided by the cardholder at the POI, e.g. 010 (invoice number) |
driver_related_data_2 | VARCHAR (35) | Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 17364557 |
fleet_prompted_data_3 | OBJECT | Contains the Prompt Code read from a card chip that indicates prompts that occur at the point of interaction and the data entered in response by the cardholder into the point-of-sale device from PDS 0792 |
_raw | VARCHAR (38) | Raw, non-parsed contents of the object as sent by Mastercard |
prompt_code_3 | CHAR (3) | Contains a code that specifies the information requested to be provided by the cardholder at the POI, e.g. 024 (trailer number) |
driver_related_data_3 | VARCHAR (35) | Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 1856 |
fleet_prompted_data_4 | OBJECT | Contains the Prompt Code read from a card chip that indicates prompts that occur at the point of interaction and the data entered in response by the cardholder into the point-of-sale device from PDS 0793 |
_raw | VARCHAR (38) | Raw, non-parsed contents of the object as sent by Mastercard |
prompt_code_4 | CHAR (3) | Contains a code that specifies the information requested to be provided by the cardholder at the POI, e.g. 012 (unit number) |
driver_related_data_4 | VARCHAR (35) | Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 1045 |
fleet_prompted_data_5 | OBJECT | Contains the Prompt Code read from a card chip that indicates prompts that occur at the point of interaction and the data entered in response by the cardholder into the point-of-sale device from PDS 0794 |
_raw | VARCHAR (38) | Raw, non-parsed contents of the object as sent by Mastercard |
prompt_code_5 | CHAR (3) | Contains a code that specifies the information requested to be provided by the cardholder at the POI, e.g. 035 (transaction number) |
driver_related_data_5 | VARCHAR (35) | Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 451122365456154 |
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_quantity_exponent":"4",
"motor_fuel_sale_amount":"000000000992"
},
"odometer_reading":"0001000",
"vehicle_number":"5369569",
"driver_number":"1234 ",
"product_type_code":"1",
"fleet_spend_control_enforced":"null",
"fleet_fuel_information":{
"_raw":"00100000000015810001255000000000248",
"fleet_fuel_product_code":"001",
"fleet_fuel_unit_price":"000000000158",
"fleet_fuel_unit_of_measure":"1",
"fleet_fuel_quantity":"000125",
"fleet_fuel_quantity_exponent":"5",
"fleet_fuel_sale_amount":"000000000248"
},
"fleet_prompted_data_1":{
"_raw":"00581523",
"prompt_code_1":"005",
"driver_related_data_1":"81523"
},
"fleet_prompted_data_2":{
"_raw":"01017364557",
"prompt_code_2":"010",
"driver_related_data_2":"17364557"
},
"fleet_prompted_data_3":{
"_raw":"0241856",
"prompt_code_3":"024",
"driver_related_data_3":"1856"
},
"fleet_prompted_data_4":{
"_raw":"0121045",
"prompt_code_4":"012",
"driver_related_data_4":"1045"
},
"fleet_prompted_data_5":{
"_raw":"035451122365456154",
"prompt_code_5":"035",
"driver_related_data_5":"451122365456154"
},
}
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.
| 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 | CHAR2 (13) | Raw, non-parsed contents of the object as sent by Mastercard. |
quantity | CHAR2 (12) | Number of items purchased |
quantity_exponent | CHAR2 (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 | CHAR2 (13) | Raw, non-parsed contents of the object as sent by Mastercard |
unit_price | CHAR2 (12) | Amount charged per unit purchased |
unit_exponent | CHAR2 (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 | CHAR2 (14) | Raw, non-parsed contents of the object as sent by Mastercard |
extended_amount | CHAR2 (12) | The individual item amount that is normally calculated as price multiplied by quantity |
extended_amount_sign | CHAR2 (1) | Whether the extended amount is a credit (C) or debit (D). |
debit_or_credit_indicator | CHAR2 (1) | Whether the net of extended_item_amount is a debit (D) or a credit (C) to the cardholder account from PDS 0654 |
fleet_product_code | VARCHAR2 (15) | Contains the non-fuel related product code of the individual item purchased from PDS 0783 |
fleet_item_description | VARCHAR (35) | Contains the description of the non-fuel item being purchased from PDS 0784 |
fleet_item_quantity | OBJECT | Indicates the quantity of the item purchased and the associated decimal point location from PDS 0785 |
_raw | CHAR2 (13) | Raw, non-parsed contents of the object as sent by Mastercard |
fleet_item_quantity | CHAR2 (12) | Subfield that If present, must be numeric and greater than zero |
fleet_item_quantity_exponent | CHAR2 (1) | Indicates the decimal location for the Item Quantity subfield |
fleet_item_unit_of_measure | CHAR2 (12) | Contains the line-item unit of measurement code from PDS 0786 |
fleet_extended_item_amount | OBJECT | Contains the individual item amount that is normally calculated as price multiplied by quantity from PDS 0787 |
_raw | CHAR2 (14) | Raw, non-parsed contents of the object as sent by Mastercard |
fleet_extended_item_amount | CHAR2 (12) | Subfield that if present, must contain the amount and be numeric and greater than zero, unless PDS 0650 (Zero Cost to Customer) is present and equal to Y |
fleet_extended_item_amount_exponent | CHAR2 (1) | Subfield that if present, must be numeric and contain a value of 0 to 5 |
fleet_extended_item_amount_sign | CHAR2 (1) | Subfield that if present, must contain a value of D or C. This subfield identifies whether PDS 0787 is a debit (D) or credit (C) from the perspective of the cardholder |
Example
{
"product_code":"099",
"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":"0000000002991D",
"extended_amount":"000000000299",
"extended_amount_exponent":"1",
"extended_amount_sign":"D"
},
"debit_or_credit_indicator":"D",
"fleet_product_code":"101",
"fleet_item_description":"DIESEL PREMIUM",
"fleet_item_quantity":{
"_raw":"0000000000121",
"fleet_item_quantity":"000000000012",
"fleet_item_quantity_exponent":"1"
},
"fleet_item_unit_of_measure":"055",
"fleet_extended_item_amount":{
"_raw":"0000000000122C",
"fleet_extended_item_amount":"000000000012",
"fleet_extended_item_amount_exponent":"2",
"fleet_extended_item_amount_sign":"C"
},
}
Fraud Rule Detail RDF
The Fraud Rule Details RDF provides detailed information on fraud rules and the resulting actions taken by the fraud engine. This RDF includes only the authorizations that triggered DFE/PRP rules (including those in WARN mode).
July–Aug 2026 changes to this RDF
- The primary key is now
PROG_ID+ERROR_ID.ERROR_IDis a new field.- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>PROD_DESCnow contains the latest, updated description instead of only the original.TRANSACTION_RESULTmight contain trailing spaces.MERCHANT_NAMEwill contain the latest version, and any commas are escaped.AUTH_AMT,BALANCEare formatted as15.0instead of15.
This table contains default fields for the Fraud Rule Detail RDF.
- The primary key is
PROG_ID+ERROR_ID - To reconcile the entries in this file with the Authorized Transactions RDF match
AUTH_IDin this file withAUTHORIZATION CODEin the Authorized Transactions RDF. - The filename format is
fraud_rule_detail_%Y%m%d.csv.
| Field name | Data type | Description |
|---|---|---|
PROD_ID | NUMBER | Identifier for the account's product in the system. |
PROD_DESC | VARCHAR2 (50) | Product description. |
PROG_ID | NUMBER | The identifier that SoFi Tech Solutions has assigned to your program. |
PROG_NAME | VARCHAR2 (20) | The SoFi Tech Solutions program name. |
AUTH_ID | NUMBER | A system-generated identifier for an incoming card transaction. |
ACQUIRER_ID | CHAR (11) | Identifier for the merchant's acquirer. |
MERCH_ID | CHAR (15) | Number identifying the merchant submitting the transaction. For non-network transactions, this may be a location ID provided by you or SoFi Tech Solutions. |
MCC | NUMBER | The MCC, which represents the merchant's line of business. |
MERCHANT_NAME | VARCHAR2 (40) | Name of the merchant submitting the transaction. |
TRANSACTION_COUNTRY | CHAR (3) | Three-digit numerical code for the country at the point of sale. |
CARDHOLDER_STATE | VARCHAR2 (16) | Cardholder's state of residence. |
AUTH_AMT | NUMBER | Amount of the authorization request. |
BALANCE | NUMBER | Available balance. |
POS_DATA_CODE | VARCHAR (12) | Point of sale data code. |
PIN | CHAR (1) | Whether a PIN was used to authenticate the card: Y (PIN) or N (no PIN). |
RESPONSE_CODE | CHAR (2) | Response code for the request. |
AUTH_TS | DATETIME | Timestamp for when SoFi Tech Solutions responded to the authorization request. |
RULE | VARCHAR2 (100) | Name of the fraud rule. |
RULE_RESULT | VARCHAR2 (50) | Fraud rule result. |
NETWORK_RISK_SCORE | VARCHAR2 (3) | Risk score that the network provided. |
NETWORK_CODE | VARCHAR2 (10) | The code identifying the network. |
XID | NUMBER (18) | System-generated internal account ID. |
PMT_REF_NO | CHAR (12) | The PRN, a unique system-generated identifier for an account. Has a 1:1 relationship with the XID |
CAD | NUMBER | CAD of the latest active card associated with the account. |
MPAN | VARCHAR2 (32) | Masked PAN of the card. |
TERMINAL_ID | CHAR (8) | Identifier of the card reader. |
MERCHANT_COUNT | NUMBER | Merchant count. |
MERCHANT_TYPE | VARCHAR2 (255) | Merchant type. |
TRANSACTION_RESULT | VARCHAR2 (4000) | Reason(s) the transaction was declined. |
ERROR_ID | NUMBER | The unique ID for an error |
Frequent Disputer RDF
The Frequent Disputer RDF provides information on how often your customers dispute transactions. This information can help you detect chargeback fraud.
July–Aug 2026 changes to this RDF
- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>AVG_DISPUTE_CNT_PER_EVENTis rounded to two decimal places:1.67instead of1.66666666666667.PROGRAM_IDadded as the first column.WIP_AMT_PCTis formatted as15.0instead of15.00.
- The primary key for this file is
XIDorPMT_REF_NO. - The filename format is
frequent_disputer_%Y%m%d.csv. - We do not support historical file generation requests for this particular RDF.
This table contains default fields for the Frequent Disputer RDF.
| Field name | Data type | Description |
|---|---|---|
PROGRAM_ID | NUMBER | Identifier for the account's program in the system. |
PROD_ID | NUMBER | Identifier for the account's product in the system. |
XID | NUMBER | System-generated internal account ID; has a 1:1 relationship with the PRN |
PMT_REF_NO | NUMBER | Payment reference number |
EVENT_DAY_CNT | NUMBER | The total number of days that experienced disputes within the previous 30-day period. |
DISPUTE_CNT | NUMBER | The total count of disputes that occurred in the last 30 days. |
DISPUTE_AMT | NUMBER | The total amount of disputes that occurred in the last 30 days. |
AVG_DISPUTE_CNT_PER_EVENT | NUMBER | The average count of disputes on the days that had disputes within the last 30 days. |
TOT_DISPUTE_CNT | NUMBER | The total count of disputes over the entire lifetime of the account. |
TOT_SETTLEMENT_CNT | NUMBER | The total count of settlements over the entire lifetime of the account. |
DISPUTE_RATE | NUMBER | Calculated by dividing the total lifetime count of disputes by the total lifetime count of settlements. |
CHARGEBACK_AMT_PCT | NUMBER | The proportion of the disputed sum for cases resolved as chargebacks compared to the total amount of all disputes over the past 30 days. |
CUSTOMER_LOSS_AMT_PCT | NUMBER | The proportion of the disputed sum for cases resolved as customer loss compared to the total amount of all disputes over the past 30 days. |
WRITE_OFF_AMT_PCT | NUMBER | The proportion of the disputed sum for cases resolved as write off compared to the total amount of all disputes over the past 30 days. |
MERCH_SENT_CREDIT_AMT_PCT | NUMBER | The proportion of the disputed sum for cases resolved as merchant sent credit compared to the total amount of all disputes over the past 30 days. |
WIP_AMT_PCT | NUMBER | The proportion of the disputed sum for cases still under WIP or resolution status not posted compared to the total amount of all disputes over the past 30 days. |
ISS RDF
The Interest Savings Supplemental (ISS) RDF contains data about rates and accumulated interest for interest-bearing accounts.
Attention
This RDF will be deprecated soon. An official communication will contain the details. This RDF will be superseded by the Monthly Interest Savings RDF.
This table contains default fields for the ISS RDF.
- The primary key for this file is
SAVINGS_ACCOUNT_ID. - The filename format is
ISS_%Y%m%d.csv.
| Field name | Data type | Description |
|---|---|---|
PROGRAM_ID | NUMBER (18) | The identifier that SoFi Tech Solutions has assigned to your program |
SAVING_ACCOUNT_ID | NUMBER | ID assigned to customer's interest-bearing account. Unique within a program |
PROD_ID | NUMBER | Identifier for the account's product in the system. |
STATUS_DATE | DATE | Latest account-status change date |
INTEREST_RATE | STRING | Interest rate set up for the product/program |
INTEREST_FACTOR | NUMBER | Interest factor |
DAILY_INTEREST | NUMBER | Daily interest accrued |
QUARTERLY_INTEREST | NUMBER | Quarterly interest accrued |
QUARTERLY_INTEREST_FORFEITED | NUMBER | Quarterly interest forfeited |
PRN | NUMBER (12) | The payment reference number, a unique system-generated identifier for an account |
TAX_WITHHOLDING | STRING | Flag to indicate whether tax is being withheld on the account |
Monthly Interest Savings RDF
Coming soon!
MSI Installments RDF
The MSI Installments RDF contains information about MSI Installments. Only transactions related to MSI Installments are included in this file.
July–Aug 2026 changes to this RDF
- The column headers in this RDF have been standardized to be identical to the Posted Transactions RDF — This RDF adds a
PDS0663column at the end.- New filename is
msi_installments_posted_trans_%Y%m%d.csv- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>
This table contains the MSI-related field that is added at the end of Posted Transactions RDF columns.
| Field name | Source | Data type | Description |
|---|---|---|---|
PDS0663 | PDS0663 | NUMBER (9) | Details of the installment payments. Positions:03 Installments without interest) |
Overdraft Details RDF
The Overdraft (OD) Details RDF provides information related to overdraft and DDA accounts for prior days.
July–Aug 2026 changes to this RDF
- The column-header names are separate words instead of PascalCase.
- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- Balances will be as of the end of the day on the report date.
- The currency fields display
15.0instead of15.00.GPR_XIDhas been removed- Two new fields:
OD Principal BalanceandOD Fee Balance
This table contains default fields for the OD RDF.
- The primary key for this file is
OD Program ID+GPR account ID - The filename format is
od_details_DDA_%Y%m%d.csv. - In this file,
GPRrefers to the primary account that draws on the overdraft account.
| Field name | Data type | Description |
|---|---|---|
OD Program ID | NUMBER | The identifier that SoFi Tech Solutions has assigned to your overdraft program |
OD Account ID | NUMBER (18) | Galileo account number of the overdraft account |
GPR Account ID | NUMBER (18) | Galileo account number of the primary account. |
OD Account Status | VARCHAR2 (2) | Overdraft account status |
OD Eligibility Status | VARCHAR2 (2) | Overdraft eligibility status of the primary account: E (eligible), I (ineligible), P (participating) |
OD Opt-In Date | DATETIME | Overdraft opt-in date |
OD Opt-Out Date | DATETIME | Overdraft opt-out date |
OD Total Balance | Decimal (18,2) | Available balance of the overdraft account |
OD Principal Balance | Decimal (18,2) | Available balance of the primary account |
OD Fee Balance | Decimal (18,2) | Outstanding unpaid overdraft fees Overdraft fee balance |
OD Limit | Decimal (18,2) | Overdraft upper limit |
GPR PRN | String (12-digit) | Payment reference number (PRN) of the primary account |
OD PRN | String (12-digit) | PRN of the overdraft account |
Secondary Accounts RDF
The Secondary Accounts RDF contains all of the accounts with changes that are not included in the Customer Master RDF.
July–Aug 2026 changes to this RDF
- A trailer record has been added to the end of the file to indicate the number of rows in the file, not counting the header row:
TTRAILER <8 spaces> <rows>- This RDF now includes all modified accounts that are not in the Customer Master RDF, even when they have the same client ID.
- Date formatting was
MMDDYYYYbut now isYYYY-MM-DD h24:mm:ss.
This table contains default fields for the Secondary Accounts RDF.
- The primary key for this file is
PRNorXID - The filename format is
secondary_accts_%Y%m%d.csv - To match the accounts in this file to their respective primary accounts in the Customer Master RDF, use one of these pairs:
BAL_IDwithGALILEO ACCOUNT ID— Sharing the same balanceCLIENT IDwithGALILEO CLIENT ID— Belonging to the same account holder
| Field name | Data type | Description |
|---|---|---|
PROG_ID | NUMBER (18) | The identifier that SoFi Tech Solutions has assigned to your program |
START_DATE | DATETIME | The date-time when the account holder's account was first changed to status: N (active). Called issued_date in other contexts. |
ID1 | VARCHAR2 (100) | The account holder's ID that was used for identity verification, usually the SSN. You can see an SSN only if you are PCI compliant; otherwise, you get blank spaces. |
ID1_TYPE | NUMBER (18) | The type of identifier in the ID field, such as SSN or driver license. See the Customer ID Types enumeration for the possible values. |
FNAME | VARCHAR2 (32) | Account holder's first name |
LNAME | VARCHAR2 (32) | Account holder's last name |
ADDR1 | VARCHAR2 (48) | Account holder's primary address line 1 |
ADDR2 | VARCHAR2 (48) | Account holder's primary address line 2 |
CITY | VARCHAR2 (48) | The city of the account holder's primary address |
STATE | VARCHAR2 (16) | The state or province of the account holder's primary address |
ZIP | VARCHAR2 (10) | The postal code of the account holder's primary address |
PHONE1 | VARCHAR2 (53) | The phone number that the account holder gave as the primary number |
PHONE2 | VARCHAR2 (29) | Encrypted phone number that the account holder gave as the secondary (other) number; decrypted for PCI-compliant clients |
ACCOUNT_STATUS | CHAR (1) | The status of the account |
APP_DATE | DATETIME | The date-time when an account holder first applied for an account, regardless of whether the application was approved or denied. Called created_date in other contexts. |
IS_CARD_RELOADABLE | CHAR (1) | Whether the card is reloadable: 0 (not reloadable) or 1 (reloadable) |
BAL_ID | NUMBER (18) | The balance ID, sometimes called the Galileo account number. |
XID | NUMBER (18) | Internal account identifier; has a 1:1 relationship with the PRN |
ACCOUNT_TYPE | NUMBER (18) | The branded network to which the card belongs, such as Mastercard or Visa, as well as the type of card, such as personalized or instant issue. See the Lookup file to interpret the values. |
EXT_ACCT_ID | CHAR (53) | An identifier that you provide for your own tracking purposes; you pass this value in the externalAccountId parameter of the Create Account or Update Account endpoint. |
DOB | VARCHAR2 (29) | Account holder's date of birth, encrypted. Decrypted only for PCI-compliant clients: MMDDYYYY |
BILL_CYCLE | NUMBER (18) | Day of the month for the billing cycle |
APP_LOCATION_ID | NUMBER (18) | Identifier for where the account was created, if applicable. Use Get Locations to get a location_id. |
APP_USER_ID | VARCHAR2 (80) | ID of the CST agent who submitted the account application |
ID2 | VARCHAR2 (100) | Secondary identity number, if provided, such as driver license or information provided to the embosser |
ID2_TYPE | NUMBER (18) | The type of identifier in ID2, such as driver license or client-generated ID. See the Customer ID Types enumeration for the possible values. |
AFF_HIT_ID | VARCHAR2 (50) | The contents of the userData parameter in the account-enrollment endpoint request |
EMAIL | VARCHAR2 (64) | Email address of the account holder |
PROD_ID | NUMBER (18) | Identifier for the account's product in the system |
PMT_REF_NO | CHAR (12) | The payment reference number |
CLIENT_ID | NUMBER (18) | System-generated identifier for the secondary account holder |
OVERRIDE_IND | CHAR (1) | Whether ID verification was skipped for manual approval: Y (skipped) or N (not skipped) |
TOTID_PASS | CHAR (1) | Whether the account holder passed ID verification: Y (passed) or N (did not pass) |
Updated 4 days ago

