RDF Reference

This document contains details about each of the standard RDFs, including field descriptions:

Customer Master RDF

The Customer Master RDF is a list of all of your primary account holders. The first Customer Master RDF that you receive contains all of your account records. The RDFs after that contain only the new records and the changed records from the previous day. You can arrange with Galileo to receive a full list of accounts every day instead of the differential file.

This table contains the default fields for the Customer Master RDF. The primary key for this file is GALILEO ACCOUNT ID + UNIQUE PROGRAM ID. Also see Customizing the RDFs to see fields to add.

RDF field nameDescription
UNIQUE PROGRAM IDThe identifier that Galileo has assigned to your program.
ISSUED DATEThe date/time when the customer account was activated.
IDThe customer's ID that was used for KYCKYC - Know your customer. Banks are required to verify the identities of potential customers. KYC requirements are specific to each country. Galileo sometimes uses the term "CIP" (customer identification program) to refer to the combination of KYC and CIP./CIPCIP - Customer identification program. In the United States, financial entities that want to engage in financial transactions with a potential customer must have a CIP to ensure that potential customers are not on terrorist watch lists. This provision of the Patriot Act is designed to increase security and guard against money-laundering. Galileo sometimes uses this term to encompass CIP and Know Your Customer (KYC)., usually the SSN. You can see an SSN only if you are PCI compliant; otherwise, you get blank spaces. See the Customer ID Types enumeration for the possible values.
ID TYPEThe type of identifier in the ID field, such as SSN or driver license. See the Customer ID Types enumeration for the possible values.
PRIMARY CARDHOLDER'S FIRST NAMEThe customer's first name
PRIMARY CARDHOLDER'S LAST NAMEThe customer's last name
ADDRESS LINE 1The first line of the customer's primary address
ADDRESS LINE 2The second line of the customer's primary address, if any.
CITYThe city of the customer's primary address
STATEThe state or province of the customer's primary address
ZIP CODEThe postal code of the customer's primary address
PRIMARY PHONE NUMBERThe phone number that the customer gave as their primary number.
SECONDARY PHONE NUMBERThe phone number that the customer gave as their secondary number, if any
STATUSThe status of the account.
CURRENT BALANCEThe balance of the account as of 23:59:59 on the previous day. This is the ledger balance, which includes all posted transactions but not pending transactions such as authorization holds.
CURRENT BALANCE SIGNA + or - sign to indicate whether the account balance is positive or negative.
CREATED DATEThe date/time when a customer first applies for an account. A record with this value is created regardless of whether the customer application is approved or denied.
NEGATIVE BALANCE DATEDate on which the available balance was driven negative.
NEGATIVE BALANCE FEE AMOUNTFee assessed to an account that was driven negative.
RELOADABLE INDICATORBoolean (0 or 1) to indicate whether the card is reloadable. 1 means reloadable.
GALILEO ACCOUNT IDThe balance ID, which is different from the account ID (PRNPRN - Payment reference number (pmt_ref_no). The 12-digit Galileo-generated account identifier, which exists independently of the PAN or other identifiers.). It is possible for two or more accounts to share the same balance ID.
TYPE OF ACCOUNTThe name given to the product, such as "Mastercard Debit" or "Visa Instant Issue."
AVAILABLE BALANCEThe available balance as of 23:59:59 on the previous day. This amount includes pending transactions such as authorization holds.
AVAILABLE BALANCE SIGNA + or - sign to indicate whether the available balance is positive or negative.
EXTERNAL ACCOUNT NUMBERAn 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.
LAST TRANS DATEThe date of the last posted transaction on this account as of 23:59:59 on the previous day, including payments, settlements, adjustments, and fees. This value does not include unsettled authorizations or pending transactions.
DATE OF BIRTHAccount holder date of birth.
BILL CYCLE DAYDay of the month for the billing cycle.
LOCATION IDLocation at which the account was created, if applicable. Value can be provided by you or by Galileo.
AGENT USER IDID of the agent who created the account.
ID 2Secondary identity number, if provided, such as driver license or SSN. See the Customer ID Types enumeration for the possible values.
ID TYPE 2The type of identifier in the ID 2 field, such as SSN or driver license. See the Customer ID Types enumeration for the possible values.
PRNThe payment resource number, a unique Galileo-generated identifier for an account.

Account Card RDF

The Account Card RDF is a list of all cards that you have issued. The first Account Card RDF that you receive contains all of your card records. The RDFs after that contain only the new records and the changed records from the previous day. You can arrange with Galileo to receive a full list of cards every day instead of the differential file.

📘

Note

Any changes to a card record, including resetting the PIN fail count by a backend process, results in the card record being included in the differential file. Some of these changes are not reflected in the data in the RDF.

This table contains the default fields for the Account Card RDF. The primary key for this file is UNIQUE PROGRAM ID + CARD ID. Also see Customizing the RDFs to see fields to add.

RDF field nameDescription
UNIQUE PROGRAM IDThe identifier that Galileo has assigned to your program.
GROUP IDSource or affiliate ID. Usually the same as LOCATION ID in the Customer Master RDF.
PRODUCT IDThe numeric code that is assigned to the product the card belongs to.
GALILEO ACCOUNT IDThe balance ID, which is different from the account ID (PRNPRN - Payment reference number (pmt_ref_no). The 12-digit Galileo-generated account identifier, which exists independently of the PAN or other identifiers.). It is possible for multiple accounts to share the same balance ID.
PRNThe payment reference number, a Galileo-generated ID for the card's account.
EXPIRATION DATEThe card's expiration date. If you are not PCI compliant you will receive empty spaces for this value.
STATUSThe card status, such as N (active), S (stolen) or C (canceled)
CARD IDSometimes called the CAD, this identifier is given to each unique card that is issued to an account. There is a one-to-one relationship between a card ID and a PAN. If you are not PCI compliant, you can use this identifier instead of the PAN.
CARD NUMBERThe card's PAN. If you are not PCI compliant you will get empty spaces for this value.
TYPE OF CARDThe 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.

Authorized Transactions RDF

The Authorized Transactions RDF contains transactions that passed through the authorization stream during the previous day. These transactions include authorization requests, AVS-only checks, reversal advices and completion advices. This RDF does not include these authorization events:

  • Mastercard Banknet merchant credits (adjustments)
  • Visa Money Transfer and ReadyLink card loads (payments)

Only a subset of the transactions in this RDF will also be included in a Posted Transactions RDF. For example, authorization reversals, AVS-only checks, and denied transactions are not in the Posted Transactions RDF because they do not settle.

Foreign authorizations

When a transaction takes place in a country that is foreign relative to the account's country, the AUTHORIZATION AMOUNT is in the currency of the account. For example, if an account is located in the United States and the cardholder makes a purchase in Canada, the AUTHORIZATION AMOUNT is in U.S. dollars and the TRANSACTION CURRENCY CODE is 124 (Canadian dollar). The currency conversion is performed by the card network, and it reflects the conversion rate at the time of the authorization.

Keep in mind that some online merchants conduct business in the currency of the customer instead of the location of the merchant, depending on where the customer is located. For example, a website that is based in the U.K. could have a U.S. version of its website, and so transactions on that version would be conducted in U.S. dollars.

For examples of foreign transactions see International transaction in Card Transaction Examples and these scenarios in the Card Transaction Scenarios PDF:

  • Scenario 13: International authorization
  • Scenario 14: International reversal

Authorized Transactions RDF fields

This table contains the default fields for the Authorized Transactions RDF. The primary key for this file is UNIQUE PROGRAM ID + AUTHORIZATION CODE + NETWORK CODE. Also see Customizing the RDFs to see fields to add.

The Source column indicates where the value came from: Galileo-provided or a data element (DE) in the ISO 8583 message from the network. The actual DE number for a field may vary by network, and not all DEs are present for all networks.

RDF field nameSourceDescription
UNIQUE PROGRAM IDGalileoThe identifier that Galileo has assigned to your program.
GALILEO ACCOUNT IDGalileoThe balance ID, which is different from the account ID (PRN). It is possible for two or more accounts to share the same balance ID.
CARD IDGalileoSometimes called the CAD, this identifier is given to each unique card that is issued to an account. If you are not PCI compliant, you can use this identifier instead of the PANPAN - Primary account number. The 16-digit number that is printed on a card, beginning with the BIN. This number is not the same as the account identifier, which is the PRN, or the card identifier, which is the CAD..
TRANSACTION DATE/TIMEGalileoThis date/time stamp identifies the time that Galileo responds to the authorization request.
TRANSACTION CURRENCY CODEDE049The currency code at the point of sale.
ADDRESS VERIFICATION RESPONSEGalileoThe single-character result of the AVSAVS - Address verification service. An authentication method whereby the merchant submits a card's billing address in an authorization request. check that Galileo passed to the network. For more information see AVS-only checks in the Authorization guide.
AUTHORIZATION RESPONSEDE039The response code that you or Galileo returned to the network. See the Authorization Response Codes enumeration for possible values.
AUTHORIZATION AMOUNTDE004 times the conversion rate in DE009The amount that you or Galileo authorized for the transaction. This amount may be different from the amount of the authorization request in the case of a partial authorization. If AUTHORIZATION RESPONSE is 10 or 87, the amount is a partial authorization. This amount is in the currency of the account.
AUTHORIZATION AMOUNT SIGNGalileoA + or - sign to indicate whether the amount is to be debited (-) or credited (+) to the cardholder account.
AUTHORIZATION CODEGalileoA Galileo-generated identifier for the authorization, called auth_id in other contexts. This ID is unique only per subnetwork, so there could be an ID collision between an authorization from Mastercard Banknet and an authorization from Visa Interlink, for example. However, there is no collision among identifiers for the Visa networks (Visa credit, Interlink, Plus). See Mapping Transactions Within Your System for more information for more information.
NETWORK CODEGalileoA single-letter identifier to specify the subnetwork over which the authorization request arrived. See Mapping Transactions Within Your System for possible values.
MERCHANT NUMBERDE042An identifier that each network assigns to a merchant location.
MERCHANT NAMEDE043Descriptive text provided by the merchant to identify the merchant name and location and sometimes the transaction type.
MERCHANT CATEGORY CODEDE018The ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on.
TRANSACTION CODE*GalileoA numeric value that corresponds to the type of transaction that is being attempted.
MERCHANT COUNTRY CODEDE018The ISO 3166-1 three-digit code for the country where the merchant is officially located.
PRNGalileoThe payment resource number, a unique Galileo-generated identifier for an account.

* The TRANSACTION CODE field in the Authorized Transactions RDF does not correspond to the TRANSACTION CODE/TYPE field in the Posted Transactions RDF. The data in the TRANSACTION CODE is unique to the Authorized Transactions RDF. See the Authorization types table in the Transactions Types enumeration for the values or consult the Lookup file for the RDFs.

Posted Transactions RDF

The Posted Transactions RDF contains every transaction that has posted to a customer account during a 24-hour period: settlements, payments, adjustments and fees. To match a settlement with its corresponding authorization, use the AUTHORIZATION CODE or SOURCE ID (which are identical for card transactions).

These types of transactions do not have corresponding entries in the Authorized Transactions RDF:

  • Adjustments
  • Most payments, except for Mastercard and Maestro loads (PMML, PMMX)
  • Visa, Green Dot, and MoneyGram card loads
  • Account transfers
  • Mastercard Banknet merchant credits
  • Most fees.
    • The authorization request amount from an ATM includes all fees.
    • ATM fees that you assess are broken out separately in the Posted Transactions RDF. The REVERSAL ID for the fee contains the AUTHORIZATION CODE of the original ATM authorization. For an example see ATM withdrawal in Card Transaction Examples.
  • ACH transactions
  • Direct deposit
  • Bill pay
  • Chargebacks, second presentments, provisional credit, and arbitration
  • Charge offs
  • Force-posted settlements
  • Roundups

Post time for completions

The timestamp for a posted transaction usually corresponds to the time Galileo posts the transaction to the cardholder account. However, in the case of completions (transaction type C), the completion time in the Posted Transactions RDF is the time of the completion, whereas the amount is settled later, after Galileo receives the batch settlement file.

For example, a cardholder gets a preauthorization at a gas pump for 75.00 at 09:00:01 and Galileo places a 75.00 hold on the account. The completion for 35.00 arrives through the authorization stream at 09:04:30. Galileo backs out the 75.00 and places a 35.00 hold on the account. The timestamp for the completion in the Authorized Transactions RDF and the Posted Transactions RDF is 09:04:30, but the actual settlement will be a day or so later. This later settlement is visible in the CST and Program API responses but not in the Posted Transactions RDF.

For an example of a completion at a gas pump see Five-step sequence in Card Transaction Examples and "Scenario 2: Preauthorization with completion" in the Card Transaction Scenarios PDF.

Foreign settlements

When a foreign transaction is settled, TRANSACTION AMOUNT is in the currency of the account rather than the currency of the merchant. The currency conversion is performed by the card network, and it reflects the conversion rate at the time the transaction cleared, which may be a different rate than when the transaction was authorized.

See Foreign authorizations for more information.

Posted Transactions RDF fields

This table contains the default fields for the Posted Transactions RDF. The primary key for this file is UNIQUE PROGRAM ID + AUTHORIZATION CODE + TRANSACTION CODE/TYPE. Also see Customizing the RDFs to see fields to add.

The Source column indicates where the value came from: Galileo-provided or a data element (DE) in the ISO 8583 message from the network. The actual DE number for a field may vary by network, and not all DEs are present for all networks.

RDF field nameSourceDescription
UNIQUE PROGRAM IDGalileoThe identifier that Galileo has assigned your program.
GALILEO ACCOUNT IDGalileoThe balance ID, which is different from the account ID (PRN). It is possible for two or more accounts to share the same balance ID.
CARD IDGalileoSometimes called the CAD, this identifier is given to each unique card that is issued to an account. If you are not PCI compliant, you can use this identifier instead of the PAN.
TRANSACTION DATE/TIMEGalileoThe time that Galileo responds to the authorization request.
TRANSACTION CODE/TYPEGalileoThe concatenation of the activity type (act_type) and the transaction type (otype). For an explanation of transaction codes see Classifying transactions in the About Transactions guide.
TRANSACTION AMOUNTGalileoThe amount that was posted to the account. In the case of a settlement, the amount may be different from its corresponding authorization amount. This amount is in the currency of the account.
TRANSACTION AMOUNT SIGNGalileoA + or - sign to indicate whether the amount was debited (-) or credited (+) to the cardholder account.
TRANSACTION CURRENCY CODEDE049The currency code at the point of sale, in the case of card transactions.
AUTHORIZATION CODEGalileoA Galileo-generated identifier for an authorization, called auth_id in other contexts. For non-network transactions, this field contains the ID for the payment, adjustment, or fee. This ID is unique only per subnetwork or transaction type (payment, adjustment, fee), so there could be an ID collision between an authorization from Mastercard Banknet and a payment, for example. See Mapping Transactions Within Your System for more information.
POST DATEGalileoThe date/time when Galileo posted the transaction to the customer account.
NETWORK CODEGalileoA single-letter identifier to specify the subnetwork over which the authorization request arrived. This field is populated only for card transactions. See Mapping Transactions Within Your System for possible values.
MERCHANT NUMBERDE042An identifier that each network assigns to a merchant location. This field is populated only for card transactions.
MERCHANT NAMEDE043Descriptive text provided by the merchant to identify the merchant name and location and sometimes the transaction type. This field is populated only for card transactions.
MERCHANT CATEGORY CODEDE018The ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on. This field is populated only for card transactions.
MERCHANT COUNTRY CODEDE019The ISO 3166-1 three-digit code for the country where the merchant is officially located. This field is populated only for card transactions.
INTERCHANGE FEE AMOUNTGalileoThe amount of interchange or fee associated with this transaction. ATM fees and interchange reversals are negative; interchange earned is positive. This field is populated only for card transactions.
EXTERNAL TRANSACTION IDvariesFor network transactions, the authorization identification response in DE038, which is a numeric code that Galileo returns to a merchant to verify that the transaction was authorized. This number is often printed on customer receipts. For outgoing ACH transactions other transactions initiated by the Program API, this is the transactionId of the API request. This field may be populated in other ways according to your setup and the transaction type.
PRNGalileoThe payment resource number, a unique Galileo-generated identifier for an account.

Lookup file

Use the Lookup file to interpret the codes in some of the RDF fields. The Lookup file for a particular day contains only those values that are included with the other RDFs on that day, so this file will include some values on one day that it does not include on other days.

The DESCRIPTION field contains a short description rather than a long description, because the specific meaning for some fields is different for each Galileo client according to their setup.

The primary key for this table is FILE TYPE + FIELD NAME + CODE. There is no foreign key to link this file to the other RDFs.

FieldDescription
FILE TYPEThe RDF that contains the field: A (Authorized Transactions), C (Customer Master), D (Account Card), or P (Posted Transactions)
FIELD NAMEName of the field in the RDF
CODEPossible values for the field
DESCRIPTIONDescription of the CODE value

Customizing the RDFs

You can customize your RDFs to meet your business needs. In general, if Galileo stores a value in its databases, it can provide the value in an RDF. Galileo recommends that you customize your RDFs during preliminary setup, although you can also add and delete fields later.

📘

Note

If you would like to include a subfield or subelement of an ISO 8583 data element, as opposed to the whole element, it will require development work to parse the subfield or subelement and include it in the RDF.

This table contains a list of fields that you might want to add to the default RDF layouts. These are fields that Galileo clients commonly add. The actual DE number for a field may vary by network, and not all DEs are present for all networks.

Field nameSourceDescriptionRDF
POS ENTRY MODEDE022First two characters of DE022. How the PAN was entered, such as magnetic stripe, EMV chip, or contactless.Authorized, Posted
PIN ENTRY CAPABILITYDE022Third character of DE022. Whether the card reader had PIN-entry capability.Authorized, Posted
SOURCE IDGalileoFor card transactions, the source ID is the same as the authorization ID. For other types of transactions, the source ID maps back to the original transaction, such as payment ID, adjustment ID and ACH transaction ID. This value is useful to track transactions across Galileo systems. The ID field in the CST corresponds to the source ID.

Keep in mind that the source ID is unique only to the transaction type or the subnetwork, so there could be a collision between a source ID for a payment and a source ID for an authorization, for example. You will need to devise a way to mark source IDs with their respective activity types. See Mapping Transactions Within Your System for more information.
Authorized, Posted
PRODUCT IDGalileoIdentifier for the account's product in the Galileo system.Authorized, Posted
LOCAL SURCHARGE AMOUNTDE028
DE046 (Allpoint)
Fee applied to the ATM withdrawal amount by the ATM's operator.Authorized, Posted
REVERSAL IDGalileoMaps back to the original_auth_id, original_id, and prior_id in other Galileo contexts. It contains the authorization ID of the previous authorization in a series, such as with incremental authorizations, reversals, and completions. See Linking transactions in the About Transactions guide for more information.Authorized, Posted
MESSAGE TYPE FLAGGalileoThe transaction type (otype).Authorized, Posted
TRANSACTION DESCRIPTIONVariousThe description for the transaction as provided by various sources.Posted
CREDIT INDICATORGalileoIndicates whether the transaction used credit or debit rails. N — PIN transaction (debit); Y — signature (credit)Authorized, Posted
CASHBACK AMOUNTGalileoThe amount of cashback that was included in the transaction.Authorized, Posted
TRACE NUMBERDE011An identifier for a transaction, generated by the message initiator (usually the merchant), that is included with all messages related to that transaction.Authorized, Posted
FROZENGalileoA Boolean to indicate whether the card is frozen. Accompanied by LOCK START DATE and LOCK END DATE.Account Card
EXPIRED AUTH CODEGalileoThe AUTHORIZATION CODE of the expired authorization that the settlement matches.Posted

Did this page help you?