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 AccountsNewly 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.0 instead of 15.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 DATETIME fields are YYYY-MM-DD h24:mm:ss.
  • Consult ACH Tracking and Troubleshooting for more information on the various transaction IDs.
Field nameData typeDescription
NameVARCHAR2 (80)Name of recipient
Source NameVARCHAR (30)Source institution name
AmountNUMBERAmount of the ACH transaction
Deb Cred IndicatorCHAR (1)Debit/credit indicator. D = debit; C = credit
Received DateDATETIMETimestamp for when we received the returned transaction
Effective DateDATETIMETimestamp for when the ACH transaction was to take effect (without early ACH)
Return DateDATETIMEDate the transaction was returned
Return Reason CodeCHAR (3)Return reason code
Return Reason DescriptionVARCHAR2 (255)Return reason description
Trans IDCHAR (2)Transaction ID
XIDNUMBERSystem-generated internal account ID; has a 1:1 relationship with the PRN
PRNNUMBERThe payment reference number, a unique system-generated, customer-facing identifier for an account
TraceNUMBERSource trace number
Source RoutingNUMBERSource routing number
Destination RoutingNUMBERDestination routing number
Company IDNUMBERSource company ID
Return TraceNUMBERReturn trace number
Program IDNUMBERID for your program as assigned by SoFi Tech Solutions
Product IDNUMBERID for a product as assigned by SoFi Tech Solutions
Settlement DateDATETIMETimestamp 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.0 instead of 15.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 DATETIME fields are YYYY-MM-DD h24:mm:ss.
  • Consult ACH Tracking and Troubleshooting for more information on the various transaction IDs.
Field nameData typeDescription
Transaction IDVARCHAR2 (2)Maps as identifier for the source of load/payment or source of the adjustment
Transaction TypeCHAR (6)Concatenation of activity type (act_type) and transaction type (otype)
Source IDNUMBER (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 IDVARCHAR2 (60)ACH transaction ID provided by client or partner
Transaction TimeDATETransaction time of the ACH record
Authorization CodeNUMBER (18)A system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions.
Number of Days EarlyNUMBERThe number of days early the ACH transaction is
Posted EarlyCHAR (1)Flag for early ACH (Y for early ACH)
Effective DateDATETIMEACH effective date (when the Nacha file says it would have posted without early ACH)
Settlement DateDATETIMEThe date the transaction was settled/posted
Receive DateDATETIMEACH file date (the date the Nacha file was received)
Load DateDATETIMEACH load date (the date the ACH transaction was written to a Nacha file)
AmountNUMBERAmount of the ACH transaction
PRNCHAR (12)The payment reference number, a unique system-generated, customer-facing identifier for an account
Trace NumberNUMBERACH trace number as received by SoFi Tech Solutions
Product IDNUMBERID for a product as assigned by SoFi Tech Solutions
Program IDNUMBERID for your program as assigned by SoFi Tech Solutions
CADNUMBERCard 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.
CategoryVARCHARHigh-level ACH transaction type
SubcategoryVARCHARDetailed ACH transaction type within the category.
Early DaysNUMBERThe number of days the transaction is made available early.
Posting DateDATETIMETimestamp 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.0 instead of 15.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.
  • Autorization changed to Authorization

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 nameData typeDescription
Company NameVARCHAR2 (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 IDNUMBEROriginator identification from the Nacha Batch Header Record (positions 41–50, 10 chars). Typically a FEIN preceded by a number-type indicator.
Company DescriptionVARCHAR2 (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 NameVARCHAR2 (80)Individual name
Individual IDNUMBERIndividual ID
Authorization CodeNUMBERA system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions.
Transaction TypeVARCHAR2 (2)Transaction type
AmountNUMBERAmount. One place after the decimal.
Trace NumberNUMBERTrace number
PRNCHAR (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_NAME
  • GALILEO_SYSTEM_MIDDLE_NAMEGALILEO_MIDDLE_NAME
  • GALILEO_SYSTEM_LAST_NAME GALILEO_LAST_NAME
  • DESTINATION_ACCOUNT_NO is 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.
  • AMOUNT is unsigned: no D or C to indicate debit or credit; use COMPANY_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 DATETIME fields are YYYY-MM-DD h24:mm:ss.
Field nameData typeDescription
COMPANY_NAMEVARCHAR2Originator 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_IDVARCHAR2Originator identification from the Nacha Batch Header Record (positions 41–50, 10 chars). ID of the institution
COMPANY_ENTRY_DESCVARCHAR2Company 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_NAMEVARCHAR2Receiver’s name.
GALILEO_SYSTEM_FIRST_NAMEVARCHAR2First name in system records.
GALILEO_SYSTEM_MIDDLE_NAMEVARCHAR2Middle name in system records.
GALILEO_SYSTEM_LAST_NAMEVARCHAR2Last name in system records.
AMOUNTNUMBERTransaction amount
TRACE_NUMBERVARCHAR215-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_NOVARCHAR2The payment reference number, a unique system-generated, customer-facing identifier for an account.
SETTLEMENT_DATEDATETIMETimestamp for when the transaction was settled.
PRESENTMENT_DATEDATETIMETimestamp for when the transaction was returned.
TRANS_IDNUMBERUnique system-generated identifier for the ACH transaction. Corresponds to the pmt_id and/or adj_id.
RETURN_CODEVARCHAR2Standard code selected by the agent if the action taken on the transaction is a return.
RETURN_DESCVARCHAR2CST field that provides the description of the return. Not included in the Nacha file.
ACTIONVARCHAR2Action taken by the CST agent on the transaction in manual review. Valid values are Post, Force Post, Return, or Pending Action.
CST_USER_IDNUMBERThe 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_NAMEVARCHAR2The 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: F rows 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 (C codes); we only show R (return) codes.
  • Currency amounts are now rendered as 15.0 instead of 15.00.
  • Column header RECIEVEDRECEIVED.
  • The NAME field 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 nameData typeDescription
ORIG_TRACENUMBERTrace number
NAMEVACHARName, which supports this character set
PMT_REF_NONUMBERThe payment reference number, a unique system-generated, customer-facing identifier for an account
SCHEDULED_DTDATEScheduled date
DEB_CRED_INDCHAR (1)Debit/credit indicator: C (credit); D (debit)
FILE_DTDATEFile date
AMOUNTNUMBERAmount of the transaction
FILENAMEVARCHAR2 (255)File name
TRANS_TYPECHAR (6)Transaction type
RETURN_CODEVARCHAR2 (20)Return reason code
RECEIVEDVARCHAR2 (20)Transaction received
RETURN_DTDATEDate the transaction was returned
SOURCE_TRACENUMBERSource trace number
EFFECTIVE_DTDATEDate range for the transaction originated
SAME_DAYCHAR (1)Indicates whether the transaction was sent as a Same Day ACH
PROG_IDNUMBERProgram ID
PROD_IDNUMBERProduct ID
ADJ_IDNUMBERIdentifier for funds removed from the local account.
REMITTANCE_INFOVARCHARDescription for the remittance as provided in the remittanceInfo field of the Create ACH Transaction endpoint.
RECORD_TYPEVARCHARF for forward or R for return
PMT_IDNUMBERIdentifier for funds added to the local account.
XIDNUMBERSystem-generated internal account ID; has a 1:1 relationship with the PRN
DSCRVARCHARACH 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_ID is 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 _BALANCE fields now contain 15.0 instead of 15.00.

This table contains default fields for the B2B Customer Master Supplemental RDF.

  • The primary key for this file is PRN or XID.
  • The filename format is b2b_custmaster_supplemental_%y%m%d.csv
Field nameData typeDescription
PROG_IDVARCHAR2 (250)Program ID
PROD_IDVARCHAR2 (250)Product ID of the account in PMT_REF_NO. With this field you can distinguish between funding and spending accounts.
BAL_IDVARCHAR2 (250)The balance ID, or galileo_account_number of the account in PMT_REF_NO.
XIDVARCHAR2 (250)Internal account ID of the account in PMT_REF_NO.
PMT_REF_NOVARCHAR2 (12)The payment reference number, a unique system-generated, customer-facing identifier for an account
FUNDING_PRNVARCHAR2 (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_IDVARCHAR2 (10)Group ID, if the account is part of a Corporate Hierarchy.
AVAILABLE_BALANCENUMBER (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_BALANCENUMBER (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 AMOUNT retains the original sign.
  • SLI INDICATOR shows a single digit rather than the full DE048 string.
  • TRANSACTION TYPE contains the auth_tran_type value instead of the whole DE003 string.
  • NETWORK CODE contains the correct value instead of M for 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 CAD field; this file contains AUTHORIZATION CODE instead.
  • Currency amounts are now rendered as 15.0 instead of 15.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 DATETIME fields are YYYY-MM-DD h24:mm:ss.
  • See Data Elements to correlate the DEs with other SoFi Tech Solutions resources.
Field nameSourceData typeDescription
AUTHORIZATION CODESoFi Tech SolutionsNUMBERA system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions.
TRANSACTION DATE/TIMESoFi Tech SolutionsDATETIMETimestamp when SoFi Tech Solutions responded to the authorization request, or when a non-card transaction posted to the account
TRANSACTION CURRENCY CODEDE049CHAR (3)The currency code at the point of sale, for card transactions
ADDRESS VERIFICATION RESPONSESoFi Tech SolutionsCHAR (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 RESPONSEDE039CHAR (2)The response code that you or SoFi Tech Solutions returned to the network. See the Authorization Response Codes enumeration for possible values.
TRANSACTION AMOUNTDE004NUMBERSigned. The amount in the authorization request.
NETWORK CODESoFi Tech SolutionsVARCHAR2 (1)A single-letter identifier to specify the subnetwork over which the authorization request arrived. See Network Codes for possible values.
MERCHANT NUMBERDE042CHAR (15)An identifier that each network assigns to a merchant location
MERCHANT DESCRIPTIONDE043CHAR (40)Descriptive text provided by the merchant to identify the merchant name, location and sometimes the transaction type
MERCHANT CATEGORY CODEDE018NUMBERThe ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on
TRANSACTION CODEDE003CHAR (2)A version of the processing code, which corresponds to the type of transaction.
MERCHANT COUNTRY CODEDE049VARCHAR2 (3)The ISO 3166-1 three-digit code for the country where the merchant is officially located
LOCAL AMOUNTDE004NUMBER (16,4)Signed. Transaction amount in the currency at the point of sale
LOCAL CURRENCY CODEDE049CHAR (3)Currency code for LOCAL AMOUNT
SETTLE AMOUNTDE005NUMBER (16,4)Signed. Transaction amount in the settlement currency
SETTLE CURRENCY CODEDE050CHAR (3)Currency code for SETTLE AMOUNT
BILLING AMOUNTDE006NUMBER (16,4)Signed. Transaction amount in the billing currency, which is the cardholder account currency
BILLING CURRENCY CODEDE051CHAR (3)Currency code for BILLING AMOUNT
CASHBACK AMOUNTDE005NUMBER (9,2)Amount of the transaction to give to the cardholder as cash
POS ENTRY MODEDE022NUMBER (2)First two characters of DE022. How the PAN was entered, such as magnetic stripe, EMV chip, or contactless. See DE022 Codes.
PIN ENTRY CAPABILITYDE022CHAR (1)Third character of DE022. Whether the card reader had PIN-entry capability. See DE022 Codes.
LOCAL SURCHARGE AMOUNTDE028NUMBER (16,4)Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator
MESSAGE TYPE FLAGSoFi Tech SolutionsCHAR (2)The otype of the authorization
AUTHORIZATION STATUSSoFi Tech SolutionsCHAR (1)Status of the authorization
POS CARDHOLDER PRESENCECHAR(1)Indicates whether the cardholder was present at the point of sale: 0 (present) or 1 (not present)
AUTHORIZATION IDENTIFICATION RESPONSEDE038Transaction response identification code assigned by the authorizing institution
SLIVARCHAR2 (19)Security level indicator
SLI INDICATORDE048 SE42CHAR (1)Security level indicator, included with Mastercard 3DS authentication
TERMINAL IDDE041CHAR (8)Identifier of the card reader
IVA_TAXNUMBER_Mastercard only._ Impuesto al valor agregado. Value-added tax. Colombia only.
IAC_TAXNUMBER_Mastercard only._ Impuesto al consumo. Consumption tax. Colombia only.
AAV INDICATORDE048 SE43CHAR (2)Universal cardholder authentication field (UCAF) or account holder authentication value (AAV)
STIP RESPONSEDE039CHAR (2)_Mastercard only_. The response code that the network returned to the merchant during stand-in processing (STIP)
ADVICE REASON CODEDE060VARCHAR2 (61)Indicates the specific reason for an advice.
AUTHORIZING AGENT ID CODEDE121CHAR (11)Authorizing agent ID code. The actual processing facility that approved or declined an authorization request message
MESSAGE TYPE IDENTIFIERSCHAR (3)The message type identifier for the authorization request, minus the first digit
BANKNET REFERENCE NUMBERDE063VARCHAR2 (9)Value received for Maestro updates
REVERSAL IDSoFi Tech SolutionsNUMBERContains the authorization ID of the previous authorization in a series, such as with incremental authorizations, reversals, and completions.
ASSOCIATION TRANS IDDE062VARCHAR2 (15)Visa only. Transaction identifier that was assigned by the network
BAIDE104VARCHAR2 (3)Visa only. Business Application Identifier, which identifies the type of Visa card load
TERMINAL NETWORKSoFi Tech SolutionsVARCHAR2 (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 NameData typeDescription
BAL_IDNUMBERThe balance ID, also called the Galileo account number, of the primary account. This is different from the PRN.
PROD_IDNUMBER(18)Identifier for the account's product in the system
ACCOUNT_STATUSVARCHARSpecifies the state of an account. See Account Statuses for a complete list.
PMT_REF_NOVARCHAR(12)The payment reference number, a unique system-generated, customer-facing identifier for an account
LAST_CYCLE_PAYMENT_STATUSVARCHARPayment status of the last complete billing cycle. Possible values:
  • UNPAID
  • PAID
  • PAST DUE
  • ZERO_BALANCE
  • LAST_CYCLE_CLOSE_DATEDATEDate the last billing cycle ended
    LAST_CYCLE_DUE_DATEDATEDue date of last billing cycle
    LAST_CYCLE_DELINQUENCY_DATEDATEDate when the account became delinquent in the last billing cycle, if applicable
    LAST_CYCLE_BILL_AMOUNTNUMBERTotal amount due at the end of the last billing cycle, including late fees
    LAST_CYCLE_AMOUNT_PAIDNUMBERTotal amount paid towards the last billing cycle
    LAST_CYCLE_AMOUNT_PAST_DUENUMBER(16,2)Total amount due from unpaid minimum payments in prior billing cycles
    LAST_CYCLE_PAYMENT_RECEIVED_DATEDATEThe timestamp of the most recent payment applied to any unpaid billing cycles on the account
    TOTAL_LATE_FEES_DUENUMBER(16,2)The total amount of late fees currently due
    CURRENT_CYCLE CLOSE_DATEDATEForecasted last date of the current billing cycle
    CURRENT_CYCLE_DUE_DATEDATEDue date of the current billing cycle
    CURRENT_CYCLE_AMOUNT_PAIDNUMBERTotal 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 nameData typeDescription
    PROD_IDNUMBER (10,0)Product ID
    XIDNUMBER (12,0)Internal Galileo account number
    GALILEO_GUIDVARCHAR (32)Unique ID for the direct deposit switch transaction
    GALILEO_TIMESTAMPTIMESTAMPTimestamp in UTC for when the transaction was completed, in ISO 8601 format
    EVENT_STATUSVARCHAR (30)Final status of the direct deposit switch transaction: COMPLETED or FAILURE. Incomplete transactions are not included.
    DISTRIBUTION_TYPEVARCHAR (10)Type of distribution in distribution_amount: Fixed, Percentage, Total
    DISTRIBUTION_AMOUNTNUMBER (20,2)Amount of the deposit.
    EVENT_STATUS_REASONVARCHAR (50)The reason for the status when event_status: FAILURE. See Direct Deposit Switch Failure Status Reasons for valid values.
    VENDOR_SELECTIONVARCHAR (10)Direct deposit switch vendor: Atomic
    PRODUCTVARCHARProduct name
    PAYMENT_TYPEVARCHARPayment type
    COMPANYVARCHARName of employer company
    ACCOUNT_TYPEVARCHARAccount 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) 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 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 nameData typeDescription
    prog_idNUMBER (18)The identifier that SoFi Tech Solutions has assigned to your program
    bal_idNUMBERThe 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.
    cadNUMBERSometimes 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_tsDATE-TIMEDate-time when you or SoFi Tech Solutions approved the transaction
    trans_typeCHAR (6)Transaction type
    auth_codeNUMBERA system-generated identifier (auth_id). See Transaction IDs for information about unique identifiers and ID collisions.
    post_tsDATE-TIMEDate-time when the transaction posted to the account
    network_codeVARCHAR2 (1)Network code. This is the same as the NETWORK CODE field in the Posted Transactions RDF.
    pmt_ref_noCHAR (12)The payment reference number, a unique system-generated, customer-facing identifier for an account
    prod_idNUMBER (18)Identifier for the account's product in the system.
    usage_codeVARCHAR (2)Indicates the type of addendum data provided. This value will always be 98 for any fleet-related addendum.
    industry_rec_noNUMBER (3)Industry record number:
  • 000 — Corporate card common data
  • 002 — Corporate fleet transaction information
  • 950 — Corporate line-item detail
  • occurrence_indNUMBER (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 dataVARCHAR (4000)Further transaction data, according to the row:
  • [Row 1](#row-1-fields) — corporate_card_detail
  • [Row 2](#row-2-fields) — fleet_detail
  • [Rows 3–n](#rows-3-n-fields) — line_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 nameData typeDescription
    card_acceptor_typeOBJECTContains all of the fields that begin with business_. Describes the type of business where the purchase was made, from PDS 0595.
    _rawVARCHAR2 (8)Raw, non-parsed contents of the object as sent by Mastercard.
    business_typeVARCHAR2 (1)Code to identify the business type
    business_owner_typeVARCHAR2 (1)Code to identify the type of business owner
    business_cert_typeVARCHAR (1)Code to indicate the certification type of the business
    business_eth_typeVARCHAR (1)Code to indicate the ethnicity of the majority owner of the business
    business_type_codeVARCHAR (1)Whether the business type is provided
    business_owner_type_codeVARCHAR (1)Whether the business owner type is provided
    business_cert_type_codeVARCHAR (1)Whether the certification type is provided
    business_eth_type_codeVARCHAR (1)Whether the business ethnic type is provided
    card_acceptor_tax_idOBJECTContains the next three fields, which describe the U.S. federal tax ID or value-added tax ID from PDS 0596
    _rawVARCHAR2 (21)Raw, non-parsed contents of the object as sent by Mastercard.
    tax_idVARCHAR2 (20)The tax ID of the card acceptor
    tax_id_codeVARCHAR2 (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 nameData typeDescription
    oil_company_brand_nameCHAR (4)Code to indicate the brand name from PDS 0620
    purchase_timeCHAR (4)Purchase time at the point of sale from PDS 0621: hhmm
    motor_fuel_service_typeCHAR (1)Type of service received at the card acceptor site from PDS 0622
    motor_fuel_informationOBJECTObject containing the fields that begin with motor_, which contain details about the motor fuel from PDS 0623
    _rawCHAR2 (35)Raw, non-parsed contents of the object as sent by Mastercard.
    motor_fuel_product_codeCHAR2 (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_priceCHAR2 (12)Price per unit
    motor_fuel_unit_of_measureCHAR2 (1)Motor fuel unit of measure
    motor_fuel_quantityCHAR2 (6)Motor fuel quantity
    motor_fuel_quantity_exponentCHAR (1)Contains the exponent indicating the decimal position of the quantity of the motor fuel item being purchased
    motor_fuel_sale_amountCHAR2 (12)Total fuel sale price
    odometer_readingVARCHAR2 (7)Odometer reading from PDS 0629
    vehicle_numberVARCHAR2 (17)Vehicle number from PDS 0630
    driver_numberVARCHAR2 (17)ID of the driver from PDS 0631
    product_type_codeCHAR (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_enforcedCHAR2 (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_informationOBJECTContains the acquirer's Fleet fuel product code translated from the information the attendant entered from PDS 0782
    _rawCHAR2 (35)Raw, non-parsed contents of the object as sent by Mastercard
    fleet_fuel_product_codeCHAR2 (3)Contains a three-digit code that identifies the fuel item purchased
    fleet_fuel_unit_priceCHAR2 (12)Contains the price per unit of the item being purchased
    fleet_fuel_unit_of_measureCHAR (1)Contains the code indicating the unit of measure for the fuel item purchased
    fleet_fuel_quantityCHAR (6)Contains quantity of the fuel item purchased
    fleet_fuel_quantity_exponentCHAR (1)Contains the exponent indicating the decimal position of the quantity of the fuel item being purchased
    fleet_fuel_sale_amountCHAR (12)Contains the sale amount of the fuel item being purchased
    fleet_prompted_data_1OBJECTContains 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
    _rawVARCHAR (38)Raw, non-parsed contents of the object as sent by Mastercard
    prompt_code_1CHAR (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_1VARCHAR (35)Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 81523
    fleet_prompted_data_2OBJECTContains 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
    _rawVARCHAR (38)Raw, non-parsed contents of the object as sent by Mastercard
    prompt_code_2CHAR (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_2VARCHAR (35)Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 17364557
    fleet_prompted_data_3OBJECTContains 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
    _rawVARCHAR (38)Raw, non-parsed contents of the object as sent by Mastercard
    prompt_code_3CHAR (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_3VARCHAR (35)Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 1856
    fleet_prompted_data_4OBJECTContains 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
    _rawVARCHAR (38)Raw, non-parsed contents of the object as sent by Mastercard
    prompt_code_4CHAR (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_4VARCHAR (35)Contains the data entered in response to the Prompt Code obtained at the POS, e.g. 1045
    fleet_prompted_data_5OBJECTContains 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
    _rawVARCHAR (38)Raw, non-parsed contents of the object as sent by Mastercard
    prompt_code_5CHAR (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_5VARCHAR (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 nameData typeDescription
    product_codeVARCHAR2 (15)Non fuel–related product code of the individual item purchased from PDS 0641
    item_descriptionVARCHAR2 (35)Object containing the fields that Item description from PDS 0642
    item_quantityOBJECTObject containing the next three fields, which contain the item quantity from PDS 0643
    _rawCHAR2 (13)Raw, non-parsed contents of the object as sent by Mastercard.
    quantityCHAR2 (12)Number of items purchased
    quantity_exponentCHAR2 (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_measureVARCHAR2 (12)Item unit of measure from PDS 0645
    item_unit_priceOBJECTObject containing the next three fields, which contain information about the unit price from PDS 0646
    _rawCHAR2 (13)Raw, non-parsed contents of the object as sent by Mastercard
    unit_priceCHAR2 (12)Amount charged per unit purchased
    unit_exponentCHAR2 (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_amountOBJECTObject containing the next three fields, which contain information about the extended amount from PDS 0647
    _rawCHAR2 (14)Raw, non-parsed contents of the object as sent by Mastercard
    extended_amountCHAR2 (12)The individual item amount that is normally calculated as price multiplied by quantity
    extended_amount_signCHAR2 (1)Whether the extended amount is a credit (C) or debit (D).
    debit_or_credit_indicatorCHAR2 (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_codeVARCHAR2 (15)Contains the non-fuel related product code of the individual item purchased from PDS 0783
    fleet_item_descriptionVARCHAR (35)Contains the description of the non-fuel item being purchased from PDS 0784
    fleet_item_quantityOBJECTIndicates the quantity of the item purchased and the associated decimal point location from PDS 0785
    _rawCHAR2 (13)Raw, non-parsed contents of the object as sent by Mastercard
    fleet_item_quantityCHAR2 (12)Subfield that If present, must be numeric and greater than zero
    fleet_item_quantity_exponentCHAR2 (1)Indicates the decimal location for the Item Quantity subfield
    fleet_item_unit_of_measureCHAR2 (12)Contains the line-item unit of measurement code from PDS 0786
    fleet_extended_item_amountOBJECTContains the individual item amount that is normally calculated as price multiplied by quantity from PDS 0787
    _rawCHAR2 (14)Raw, non-parsed contents of the object as sent by Mastercard
    fleet_extended_item_amountCHAR2 (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_exponentCHAR2 (1)Subfield that if present, must be numeric and contain a value of 0 to 5
    fleet_extended_item_amount_signCHAR2 (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_ID is 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_DESC now contains the latest, updated description instead of only the original.
    • TRANSACTION_RESULT might contain trailing spaces.
    • MERCHANT_NAME will contain the latest version, and any commas are escaped.
    • AUTH_AMT, BALANCE are formatted as 15.0 instead of 15.

    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_ID in this file with AUTHORIZATION CODE in the Authorized Transactions RDF.
    • The filename format is fraud_rule_detail_%Y%m%d.csv.
    Field nameData typeDescription
    PROD_IDNUMBERIdentifier for the account's product in the system.
    PROD_DESCVARCHAR2 (50)Product description.
    PROG_IDNUMBERThe identifier that SoFi Tech Solutions has assigned to your program.
    PROG_NAMEVARCHAR2 (20)The SoFi Tech Solutions program name.
    AUTH_IDNUMBERA system-generated identifier for an incoming card transaction.
    ACQUIRER_IDCHAR (11)Identifier for the merchant's acquirer.
    MERCH_IDCHAR (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.
    MCCNUMBERThe MCC, which represents the merchant's line of business.
    MERCHANT_NAMEVARCHAR2 (40)Name of the merchant submitting the transaction.
    TRANSACTION_COUNTRYCHAR (3)Three-digit numerical code for the country at the point of sale.
    CARDHOLDER_STATEVARCHAR2 (16)Cardholder's state of residence.
    AUTH_AMTNUMBERAmount of the authorization request.
    BALANCENUMBERAvailable balance.
    POS_DATA_CODEVARCHAR (12)Point of sale data code.
    PINCHAR (1)Whether a PIN was used to authenticate the card: Y (PIN) or N (no PIN).
    RESPONSE_CODECHAR (2)Response code for the request.
    AUTH_TSDATETIMETimestamp for when SoFi Tech Solutions responded to the authorization request.
    RULEVARCHAR2 (100)Name of the fraud rule.
    RULE_RESULTVARCHAR2 (50)Fraud rule result.
    NETWORK_RISK_SCOREVARCHAR2 (3)Risk score that the network provided.
    NETWORK_CODEVARCHAR2 (10)The code identifying the network.
    XIDNUMBER (18)System-generated internal account ID.
    PMT_REF_NOCHAR (12)The PRN, a unique system-generated identifier for an account. Has a 1:1 relationship with the XID
    CADNUMBERCAD of the latest active card associated with the account.
    MPANVARCHAR2 (32)Masked PAN of the card.
    TERMINAL_IDCHAR (8)Identifier of the card reader.
    MERCHANT_COUNTNUMBERMerchant count.
    MERCHANT_TYPEVARCHAR2 (255)Merchant type.
    TRANSACTION_RESULTVARCHAR2 (4000)Reason(s) the transaction was declined.
    ERROR_IDNUMBERThe 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_EVENT is rounded to two decimal places: 1.67 instead of 1.66666666666667.
    • PROGRAM_ID added as the first column.
    • WIP_AMT_PCT is formatted as 15.0 instead of 15.00.
    • The primary key for this file is XID or PMT_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 nameData typeDescription
    PROGRAM_IDNUMBERIdentifier for the account's program in the system.
    PROD_IDNUMBERIdentifier for the account's product in the system.
    XIDNUMBERSystem-generated internal account ID; has a 1:1 relationship with the PRN
    PMT_REF_NONUMBERPayment reference number
    EVENT_DAY_CNTNUMBERThe total number of days that experienced disputes within the previous 30-day period.
    DISPUTE_CNTNUMBERThe total count of disputes that occurred in the last 30 days.
    DISPUTE_AMTNUMBERThe total amount of disputes that occurred in the last 30 days.
    AVG_DISPUTE_CNT_PER_EVENTNUMBERThe average count of disputes on the days that had disputes within the last 30 days.
    TOT_DISPUTE_CNTNUMBERThe total count of disputes over the entire lifetime of the account.
    TOT_SETTLEMENT_CNTNUMBERThe total count of settlements over the entire lifetime of the account.
    DISPUTE_RATENUMBERCalculated by dividing the total lifetime count of disputes by the total lifetime count of settlements.
    CHARGEBACK_AMT_PCTNUMBERThe 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_PCTNUMBERThe 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_PCTNUMBERThe 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_PCTNUMBERThe 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_PCTNUMBERThe 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 nameData typeDescription
    PROGRAM_IDNUMBER (18)The identifier that SoFi Tech Solutions has assigned to your program
    SAVING_ACCOUNT_IDNUMBERID assigned to customer's interest-bearing account. Unique within a program
    PROD_IDNUMBERIdentifier for the account's product in the system.
    STATUS_DATEDATELatest account-status change date
    INTEREST_RATESTRINGInterest rate set up for the product/program
    INTEREST_FACTORNUMBERInterest factor
    DAILY_INTERESTNUMBERDaily interest accrued
    QUARTERLY_INTERESTNUMBERQuarterly interest accrued
    QUARTERLY_INTEREST_FORFEITEDNUMBERQuarterly interest forfeited
    PRNNUMBER (12)The payment reference number, a unique system-generated identifier for an account
    TAX_WITHHOLDINGSTRINGFlag 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 PDS0663 column 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 nameSourceData typeDescription
    PDS0663PDS0663NUMBER (9)Details of the installment payments. Positions:
  • 1–2 — Type of credit (03 Installments without interest)
  • 3–4 — Total number of installments
  • 5–6 — Grace period in months
  • 7–9 — Currency code
  • 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.0 instead of 15.00.
    • GPR_XID has been removed
    • Two new fields: OD Principal Balance and OD 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, GPR refers to the primary account that draws on the overdraft account.
    Field nameData typeDescription
    OD Program IDNUMBERThe identifier that SoFi Tech Solutions has assigned to your overdraft program
    OD Account IDNUMBER (18)Galileo account number of the overdraft account
    GPR Account IDNUMBER (18)Galileo account number of the primary account.
    OD Account StatusVARCHAR2 (2)Overdraft account status
    OD Eligibility StatusVARCHAR2 (2)Overdraft eligibility status of the primary account: E (eligible), I (ineligible), P (participating)
    OD Opt-In DateDATETIMEOverdraft opt-in date
    OD Opt-Out DateDATETIMEOverdraft opt-out date
    OD Total BalanceDecimal (18,2)Available balance of the overdraft account
    OD Principal BalanceDecimal (18,2)Available balance of the primary account
    OD Fee BalanceDecimal (18,2)Outstanding unpaid overdraft fees Overdraft fee balance
    OD LimitDecimal (18,2)Overdraft upper limit
    GPR PRNString (12-digit)Payment reference number (PRN) of the primary account
    OD PRNString (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 MMDDYYYY but now is YYYY-MM-DD h24:mm:ss.

    This table contains default fields for the Secondary Accounts RDF.

    • The primary key for this file is PRN or XID
    • 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_ID with GALILEO ACCOUNT ID — Sharing the same balance
      • CLIENT ID with GALILEO CLIENT ID — Belonging to the same account holder
    Field nameData typeDescription
    PROG_IDNUMBER (18)The identifier that SoFi Tech Solutions has assigned to your program
    START_DATEDATETIMEThe date-time when the account holder's account was first changed to status: N (active). Called issued_date in other contexts.
    ID1VARCHAR2 (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_TYPENUMBER (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.
    FNAMEVARCHAR2 (32)Account holder's first name
    LNAMEVARCHAR2 (32)Account holder's last name
    ADDR1VARCHAR2 (48)Account holder's primary address line 1
    ADDR2VARCHAR2 (48)Account holder's primary address line 2
    CITYVARCHAR2 (48)The city of the account holder's primary address
    STATEVARCHAR2 (16)The state or province of the account holder's primary address
    ZIPVARCHAR2 (10)The postal code of the account holder's primary address
    PHONE1VARCHAR2 (53)The phone number that the account holder gave as the primary number
    PHONE2VARCHAR2 (29)Encrypted phone number that the account holder gave as the secondary (other) number; decrypted for PCI-compliant clients
    ACCOUNT_STATUSCHAR (1)The status of the account
    APP_DATEDATETIMEThe 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_RELOADABLECHAR (1)Whether the card is reloadable: 0 (not reloadable) or 1 (reloadable)
    BAL_IDNUMBER (18)The balance ID, sometimes called the Galileo account number.
    XIDNUMBER (18)Internal account identifier; has a 1:1 relationship with the PRN
    ACCOUNT_TYPENUMBER (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_IDCHAR (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.
    DOBVARCHAR2 (29)Account holder's date of birth, encrypted. Decrypted only for PCI-compliant clients: MMDDYYYY
    BILL_CYCLENUMBER (18)Day of the month for the billing cycle
    APP_LOCATION_IDNUMBER (18)Identifier for where the account was created, if applicable. Use Get Locations to get a location_id.
    APP_USER_IDVARCHAR2 (80)ID of the CST agent who submitted the account application
    ID2VARCHAR2 (100)Secondary identity number, if provided, such as driver license or information provided to the embosser
    ID2_TYPENUMBER (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_IDVARCHAR2 (50)The contents of the userData parameter in the account-enrollment endpoint request
    EMAILVARCHAR2 (64)Email address of the account holder
    PROD_IDNUMBER (18)Identifier for the account's product in the system
    PMT_REF_NOCHAR (12)The payment reference number
    CLIENT_IDNUMBER (18)System-generated identifier for the secondary account holder
    OVERRIDE_INDCHAR (1)Whether ID verification was skipped for manual approval: Y (skipped) or N (not skipped)
    TOTID_PASSCHAR (1)Whether the account holder passed ID verification: Y (passed) or N (did not pass)

    Did this page help you?

    © SoFi Technology Solutions, LLC 2026    Privacy Disclosure

    All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of SoFi Technology Solutions, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of SoFi Technology Solutions, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.