Secondary RDF Reference

👍

Notice

These new RDFs are in an introductory state, and so this guide contains preliminary information that will be updated as the RDFs are further refined.

This page contains details about each of the secondary RDFs, which contain all of the possible fields for each of the standard RDFs instead of a curated subset. Unlike the standard RDFs, the secondary RDFs are CSV (comma-separated-value) files. If you are already receiving the standard RDFs you can switch to the secondary RDFs by request. Keep in mind that you would have to refactor your RDF intake process to account for the comma separation, the additional number of fields, and in some cases the new field order.

📘

Note

New fields will be appended to these files as the need arises. For new data elements (DEs), Galileo will add them periodically as the networks provide them and will communicate these additions prior to their implementation. You can also request additional fields, subject to approval, by submitting a client request.

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.

This table contains all possible fields for the Customer Master RDF. The primary key for this file is GALILEO ACCOUNT ID + UNIQUE PROGRAM ID. All DATETIME fields have the format MMDDYYYY hh24:mm:ss. "Signed" amounts have a + (credit) or - (debit) sign after the amount to indicate which way the funds moved relative to the account, for example: 30.25- for a debit or 23.67+ for a credit.

RDF fieldData typeDescription
UNIQUE PROGRAM IDNUMBER (18)The identifier that Galileo has assigned to your program.
ISSUED DATEDATETIMEThe date-time when the customer account was activated: MMDDYYYY hh24:mm:ss
IDVARCHAR2 (100)The customer's ID that was used for KYC/CIP, 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 TYPENUMBER (18)The type of identifier in the ID field, such as SSN or driver license. See the Customer ID Types enumeration or the Lookup file for the possible values.
PRIMARY CARDHOLDER'S FIRST NAMEVARCHAR2 (32)The customer's first name
PRIMARY CARDHOLDER'S LAST NAMEVARCHAR2 (32)The customer's last name
ADDRESS LINE 1VARCHAR2 (48)Customer's address line 1
ADDRESS LINE 2VARCHAR2 (48)Customer's address line 2
CITYVARCHAR2 (48)The city of the customer's primary address
STATEVARCHAR2 (16)The state or province of the customer's primary address
ZIP CODEVARCHAR2 (10)The postal code of the customer's primary address
PRIMARY PHONE NUMBERVARCHAR2 (53)The phone number that the customer gave as the primary number
SECONDARY PHONE NUMBERVARCHAR2 (29)Encrypted phone number that the customer gave as the secondary (other) number. Decrypted for PCI-compliant clients
STATUSCHAR (1)The status of the account.
CURRENT BALANCENUMBER (10,2)Signed. The balance of the account as of 23:59:59 on the previous day. This is the ledger balance, which is the total of all posted transactions. Pending transactions such as authorization holds are not subtracted out.
CREATED DATEDATETIMEThe date-time when a customer first applied for an account, regardless of whether the application is approved or denied: MMDDYYYY hh24:mm:ss
NEGATIVE BALANCE DATEDATETIMEDate-time on which the available balance was driven negative: MMDDYYYY hh24:mm:ss
NEGATIVE BALANCE FEE AMOUNTNUMBER (9,2)Fee assessed to the account when it was driven negative
RELOADABLE INDICATORCHAR (1)Whether the card is reloadable: 0 (not reloadable) or 1 (reloadable)
GALILEO ACCOUNT IDNUMBER (18)The balance ID, which is different from the PRN. It is possible for multiple PRNs to share the same balance ID.
TYPE OF ACCOUNTNUMBER (18)The ID of the account type; see the Lookup file to interpret the values.
AVAILABLE BALANCENUMBER (9,2)Signed. The available balance (OTB) as of 23:59:59 on the previous day. This is the CURRENT BALANCE with pending transactions subtracted out.
EXTERNAL ACCOUNT NUMBERCHAR (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.
LAST TRANSACTION DATEDATETIMEThe date-time 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: MMDDYYYY hh24:mm:ss
DATE OF BIRTHVARCHAR2 (29)Account holder date of birth, encrypted. Decrypted only for PCI compliant clients: MMDDYYYY
BILL CYCLE DAYNUMBER (18)Day of the month for the billing cycle.
LOCATION IDNUMBER (18)Location at which the account was created, if applicable. Value can be provided by you or by Galileo.
AGENT USER IDVARCHAR2 (30)ID of the CST agent who submitted the account application
ID 2VARCHAR2 (100)Secondary identity number, if provided, such as driver license or SSN. See the Customer ID Types enumeration for the possible values.
ID TYPE 2NUMBER (18)The type of identifier in ID 2, such as SSN or driver license. See the Customer ID Types enumeration or the Lookup file for the possible values.
PRNCHAR (12)The payment reference number, a unique Galileo-generated identifier for an account
PRODUCT IDNUMBER (18)Identifier for the account's product in the Galileo system.
ACCOUNT STATUS CHANGE DATEDATETIMEDate-time when the account status was last changed: MMDDYYYY hh24:mm:ss
AFFILIATE HIT IDVARCHAR2 (50)The contents of the userData parameter in the account-enrollment endpoint request
APPLICATION IDNUMBER (18)Identifier (appId) as returned by the account-enrollment endpoints
WATCH FLAGCHAR (1)Account-level watch flag: F (fraudulent), S (suspicious) or N (normal, default)
BUSINESS NAMEVARCHAR2 (150)Name of the business that owns the business account
CIP APPLICATION IDNUMBER (18)Galileo-generated identifier for the call to the CIP system.
CIP IDVARCHAR2 (50 bytes)String returned in the CIP call to Galileo
CIP STATUSCHAR (1)CIP status: F (failed), R (referral), S (system issue) or P (pass)
GALILEO CLIENT IDNUMBER (18)The balance ID, which is different from the PRN. It is possible for two or more PRNs to share the same balance ID.
COUNTRYVARCHAR2 (3)ISO 3166-1 code for the customer's country of residence
CREDIT LIMITNUMBER (9,2)Credit limit
EMAIL ADDRESSVARCHAR2 (64)Email address of the account holder
SSNVARCHAR2 (29)Encrypted Social Security number; decrypted for PCI-compliant clients
IP ADDRESSVARCHAR2 (16)IP address of the user who applied for the account
BUSINESS PRODUCT INDICATORCHAR (1)Whether the account is a business product account: Y (business account) or N (not a business account)
LAST FREEZE DATEDATETIMEDate-time at which the card was last frozen: MMDDYYYY hh24:mm:ss
XIDNUMBER (18)Internal account identifier; has a 1:1 relationship with the PRN
THIRD PHONE NUMBERVARCHAR2 (100)Third or other phone number, often a mobile number
CIP INFORMATIONVARCHAR2 (4000)Contents of the model_results object in the enrollment endpoint responses
OCCUPATIONVARCHAR2 (60)Contents of the occupation parameter in enrollment endpoint requests
OD BAL IDNUMBERBalance ID for the overdraft account, if any
OVERDRAFT LIMITVARCHAR2 (20)Overdraft limit
OPTED IN DATEDATETIMEDate-time when the account holder last opted in to overdraft: MMDDYYYY hh24:mm:ss
OPTED OUT DATEDATETIMEDate-time when the account holder last opted out of overdraft MMDDYYYY hh24:mm:ss
TOTAL ID OVERRIDECHAR (1)Whether ID verification was skipped for manual approval: Y (skipped) or N (not skipped)
PRIMARY ACCOUNT ACTIVE FLAGCHAR (1)Specifies whether the primary account is active: Y (active) or N (not active)
PRIMARY ACCOUNT STATUSCHAR (1)Status of the primary account
SAVINGS GALILEO IDNUMBERBalance ID of the savings account that is associated with the primary account
TOTAL ID PASSCHAR (1)Whether the account holder passed ID verification: Y (passed) or N (did not pass)

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.

📘

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 all of the possible fields for the Account Card RDF. The primary key for this file is UNIQUE PROGRAM ID + CARD ID. All DATETIME fields have the format MMDDYYYY hh24:mm:ss.

RDF field nameData typeDescription
UNIQUE PROGRAM IDCHAR (12)The identifier that Galileo assigned to the program
GROUP IDNUMBERSource or affiliate ID. Usually the same as LOCATION ID in the Customer Master RDF.
PRODUCT IDNUMBER (18)Identifier for the account's product in the Galileo system.
GALILEO ACCOUNT IDNUMBERThe balance ID, which is different from the PRN. It is possible for multiple PRNs to share the same balance ID.
PRNNUMBERThe payment reference number, a Galileo-generated ID for the card's account
EXPIRATION DATEDATETIMEThe card's expiration date-time. If you are not PCI compliant you will receive empty spaces for this value: MMDDYYYY hh24:mm:ss
CARD STATUSCHAR (1)The card status.
CARD IDENTIFIERNUMBERSometimes called the CAD, 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.
CARD NUMBERVARCHAR2 (53)The card's PAN. If you are not PCI compliant you will get empty spaces for this value.
TYPE OF CARDNUMBERThe 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.
ACCOUNT TYPECHAR (1)Account type
ACTIVATION DATEDATETIMEDate-time at which the card was activated: MMDDYYYY hh24:mm:ss
CARD STATUS CHANGE DATEDATETIMEDate-time on which the card status last changed MMDDYYYY hh24:mm:ss
GALILEO CLIENT IDNUMBERIdentifier that Galileo assigned to the cardholder
EMBOSS DATEDATETIMEDate-time at which the card was last embossed: MMDDYYYY hh24:mm:ss
EMBOSS EXPIRY DATEDATETIMEExpiry date-time of the latest embossed card: MMDDYYYY hh24:mm:ss
FROZENCHAR (1)Whether the card is currently frozen: Y (frozen) or N (unfrozen)
LAST 4 PANVARCHAR2 (4)Last 4 digits of the PAN
LOCK END DATEDATETIMEDate-time when the card was last frozen: MMDDYYYY hh24:mm:ss
LOCK START DATEDATETIMEDate-time when the card was last unfrozen: MMDDYYYY hh24:mm:ss
SEMI ENCRYPTED PANVARCHAR2 (32)16-digit masked PAN: first 6 and last 4 digits visible and middle 6 digits encrypted
PRIMARY ACCOUNT STATUSCHAR (1)Status of the primary account
SHIP TYPECHAR (1)Shipment type: 1 (standard) or 2 (express)
XIDNUMBERInternal account identifier; has a 1:1 correspondence with the PRN
ZIPVARCHAR2 (10)Ship-to postal code
ACTIVATION CHANNELVARCHAR2 (20)Method by which the card was activated: CST, Web or IVR (automated phone system)
EADDR1VARCHAR2 (73)Ship-to address, line 1
EADDR2VARCHAR2 (73)Ship-to address, line 2
ECITYVARCHAR2 (93)Ship-to city
ESHIPTO_NAMEVARCHAR2 (136)Ship-to name
ESTATEVARCHAR2 (26)Ship-to state
IS ACCOUNT ACTIVECHAR (1)Whether the card is active: Y (active) or N (not active)
UPDATE TSDATETIMEDate-time of the last card status update: MMDDYYYY hh24:mm:ss

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:

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.

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.

"Signed" amounts have a + (credit) or - (debit) sign after the amount to indicate which way the funds moved relative to the account, for example: 30.25- for a debit or 23.67+ for a credit.

RDF fieldSourceData typeDescription
UNIQUE PROGRAM IDGalileoNUMBERThe identifier that Galileo has assigned to your program
GALILEO ACCOUNT IDGalileoNUMBERThe balance ID, which is different from the PRN. It is possible for two or more PRNs to share the same balance ID.
CARD IDENTIFIERGalileoNUMBERSometimes called the CAD, 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.
TRANSACTION DATE/TIMEGalileoDATETIMEThe time that Galileo responded to the authorization request. MMDDYYYY hh24:mm:ss
TRANSACTION CURRENCY CODEDE049CHAR (3)The currency code at the point of sale
ADDRESS VERIFICATION RESPONSEGalileoCHAR (1)The single-character result of the AVS check that Galileo passed to the network. See AVS-only checks in the Authorization guide.
AUTHORIZATION RESPONSEDE039CHAR (2)The response code that you or Galileo returned to the network. See the Authorization Response Codes enumeration for possible values.
TRANSACTION AMOUNTDE004NUMBERSigned. The amount that you or Galileo authorized for the transaction, in the currency of the account. This amount may be different from the authorization request in the case of a partial authorization. If AUTHORIZATION RESPONSE is 10 or 87, the amount is a partial authorization.
AUTHORIZATION CODEGalileoNUMBER (18)A Galileo-generated identifier (auth_id). 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) or STAR networks (STAR, MoneyPass, Presto). See Mapping Transactions Within Your System for more information.
NETWORK CODEGalileoCHAR (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 CODEGalileoCHAR (2)A numeric value that corresponds to the type of transaction that is being attempted
MERCHANT COUNTRY CODEDE049VARCHAR2 (3)The ISO 3166-1 three-digit code for the country where the merchant is officially located
PRNGalileoCHAR (12)The payment reference number, a unique Galileo-generated identifier for an account
PRODUCT IDGalileoNUMBERIdentifier for the account's product in the Galileo system
ACQUIRING IDDE032VARCHAR2 (11)Identifier for the merchant's acquirer
ACTIVITY IDGalileoNUMBER (18)Identifier for the transaction in the activity table, which includes anything that affects the available balance
ASSOCIATION TRANS IDDE062VARCHAR2 (15)Visa only. The transaction ID provided by the network
AUTHORIZATION STATUSGalileoCHAR (1)Status of the authorization
AUTH TRANSACTION CODEGalileoVARCHAR2 (10)The transaction type (otype)
BAIDE104VARCHAR2 (3)Business Application Identifier. A value provided by Visa to identify the type of Visa Money Transfer that is being performed
BILLING AMOUNTDE006NUMBER (16,4)Signed. Transaction amount in the billing currency, which is the same as the account's 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
CONTACTLESS TRANSACTIONSDE022CHAR (1)Whether the card was authenticated using contactless technology: Y (contactless) or N (not contactless)
CARD PRESENT INDICATORDE061CHAR (1)Whether this was a card-present transaction: Y (card present) or N (card not present)
CREDIT INDICATORGalileoCHAR (1)Whether the transaction arrived at Galileo over credit rails: Y (credit rails) or N (debit rails)
DE28DE028
DE046 (Allpoint)
VARCHAR2 (9)Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator
RETRIEVAL_REFERENCE_NUMBERDE037VARCHAR2 (12)Retrieval reference number. Julian date plus number: YDDDxxxxxxxx
EXTERNAL TRANSACTION IDDE038CHAR (6)The authorization identification response, 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.
OTC_FLAGDE003CHAR (1)Whether the transaction included an over-the-counter cash advance. Y (cash advance) or N (no cash advance)
PIN FLAGGalileoCHAR (1)Whether a PIN was used to authenticate the card: Y (PIN) or N (no PIN)
LOCAL AMOUNTDE004NUMBER (16,4)Signed. Transaction amount in the currency at the point of sale
LOCAL CURRENCY CODEDE049CHAR (3)Currency code for LOCAL AMOUNT
LOCAL SURCHARGE AMOUNTDE028NUMBER (16,4)Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator
MERCHANT POSTAL CODEVARCHAR2 (5)Postal code for the merchant's location
MOBILE TRANSACTIONSGalileoCHAR (1)Whether a token requestor ID was present: Y (mobile wallet) or N (not mobile wallet)
MESSAGE TYPE FLAGGalileoCHAR (2)The otype of the authorization
Message Type IdentifiersCHAR (3)The MTI for the authorization request, minus the first digit
PIN ENTRY CAPABILITYDE022CHAR (1)Third character of DE022. Whether the card reader had PIN-entry capability. See DE022 Codes.
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.
POS TYPEDE003CHAR (3)Type of card authentication at the point of sale: SIG (signature) or PIN
REVERSAL IDGalileoNUMBERContains 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.
RISK SCOREDE048VARCHAR2 (10)Risk score that was calculated by the network
SETTLE AMOUNTDE005NUMBER (16,4)Signed. Transaction amount in the settlement currency
SETTLE CURRENCY CODEDE050CHAR (3)Currency code for SETTLEMENT AMOUNT
SLI INDICATORDE048SE42CHAR (1)Security level indicator, included with Mastercard 3DS authentication.
SOURCEGalileoNUMBERUnique number assigned to a network: 1 (Maestro), 2 (Mastercard credit), 3 (STAR), 4 (Visa), 5 (Discover), 6 (Allpoint) or 7 (Pulse)
TERMINAL IDDE041CHAR (8)Identifier of the card reader
TERMINAL NETWORKGalileoVARCHAR2 (50)Visa only. Network that the card reader used
TOKEN_REQUESTOR_IDVARCHAR2 (11)Identifier for the token requestor. See the Lookup file for valid values.
TOKEN TYPEVARCHAR2 (30)Type of token requested: Apple Pay, Samsung Pay or Google Pay
XIDGalileoNUMBERInternal account identifier; has a 1:1 relationship with the PRN.
AAV INDICATORDE048SE43CHAR (2)Universal cardholder authentication field (UCAF) or account holder authentication value (AAV)
Conversion RateDE010VARCHAR2 (8)The conversion rate from TRANSACTION AMOUNT to BILLING AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
Conversion RateDE009VARCHAR2 (8)The conversion rate from TRANSACTION AMOUNT to SETTLE AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
STIP ResponseDE039CHAR (2)The response code that the network returned to the merchant during stand-in processing (STIP)
SLIVARCHAR2 (19)Security level indicator
STIP STATUSGalileoVARCHAR2 (20)Whether the STIP transaction was an approval or denial: STIP (transaction approved) or STIP Decline (transaction denied)
Authorizing Agent ID CodeDE121CHAR (11)The actual processing facility that approved or declined an authorization request message
AUTHORIZATION IDENTIFICATION RESPONSEDE038Authorization identification response
Advice Reason CodeDE060VARCHAR2 (61)Indicates the specific reason for an advice.
Banknet Reference NumberDE063VARCHAR2 (9)Value received for Maestro updates
TRANSACTION LIFECYCLE IDDE063VARCHAR2 (16)Mastercard only. ID that allows tracking throughout a transaction's lifecycle
IAC_TAXNUMBERMastercard only. Impuesto al valor agregado. Value-added tax. Colombia only.
IVA_TAXNUMBERMastercard only. Impuesto al consumo. Consumption tax. Colombia only.
POS CARDHOLDER PRESENCECHAR(1)Indicates whether cardholder is present at point of sale: 0 (present) or 1 (not present)

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 ORIGINAL AUTH CODE for the fee contains the AUTHORIZATION CODE of the original ATM authorization.
  • 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.

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.

The Source column indicates where the value came from: Galileo, a Nacha file 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.

"Signed" amounts have a + (credit) or - (debit) sign to indicate which way the funds moved relative to the account, for example: 30.25- for a debit or 23.67+ for a credit.

RDF fieldSourceData typeDescription
UNIQUE PROGRAM IDGalileoNUMBER (18)The identifier that Galileo has assigned your program
GALILEO ACCOUNT IDGalileoNUMBER (18)The balance ID, which is different from the account ID (PRN). It is possible for two or more accounts to share the same balance ID.
CARD IDENTIFIERGalileoNUMBER (18)Sometimes called the CAD, this identifier is given to each unique card that is issued to an account. If you are not PCI compliant, you can use this identifier instead of the PAN.
TRANSACTION DATE/TIMEGalileoDATETIMEThe time that Galileo responded to the authorization request, or when a non-card transaction posted to the account: MMDDYYYY hh24:mm:ss
TRANSACTION CODE/TYPEGalileoCHAR (6)The 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 AMOUNTGalileoNUMBER (9,2)Signed. The amount that was posted to the account, in the currency of the account. In the case of a settlement, the amount may be different from its corresponding authorization amount.
TRANSACTION CURRENCY CODEDE049CHAR (3)The currency code at the point of sale, for card transactions
AUTHORIZATION CODEGalileoNUMBER (18)A Galileo-generated identifier for an authorization, called auth_id in other contexts. For non-network transactions, this field contains the ID for the payment, adjustment, or fee. This ID is unique only per subnetwork or transaction type (payment, adjustment, fee), so there could be an ID collision between an authorization from Mastercard Banknet and a payment, for example. See Mapping Transactions Within Your System for more information.
POST DATEGalileoDATEThe date when Galileo posted the transaction to the customer account: MMDDYYYY
NETWORK CODEGalileoVARCHAR2 (1)A single letter to specify the subnetwork over which the authorization request arrived. This field is populated only for card transactions. See Network Codes for possible values.
MERCHANT NUMBERDE042CHAR (25)An identifier that each network assigns to a merchant location. For non-card transactions, this may be a location ID provided by you or Galileo.
MERCHANT DESCRIPTIONDE043CHAR (40)Descriptive text provided by the merchant to identify the merchant name and location and sometimes the transaction type
MERCHANT CATEGORY CODEDE018NUMBER (18)The ISO 18245 four-digit identifier that specifies the type of merchant, such as ATM, gas pump, bookseller, airline, hotel, and so on
MERCHANT COUNTRY CODEDE049VARCHAR2 (3)The ISO 3166-1 three-digit code for the country where the merchant is officially located
INTERCHANGE FEE AMOUNTNUMBER (9,2)Signed. The amount of interchange or fee associated with this transaction. ATM fees and interchange reversals are negative; interchange earned is positive. This field is populated only for card transactions.

This value is rounded to 2 decimal places; for the full amount without rounding, see IC FEE AMT.
EXTERNAL TRANSACTION IDDE038VARCHAR2 (60)For network transactions, the authorization identification response in DE038, which is a numeric code that Galileo returns to a merchant to verify that the transaction was authorized. This number is often printed on customer receipts. For 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.
PRNGalileoCHAR (12)The payment reference number, a unique Galileo-generated identifier for an account
PRODUCT IDGalileoNUMBER (18)Identifier for the account's product in the Galileo system.
SETTLE DTL IDGalileoNUMBER (18)The identifier for the transaction in the settlement table. This field is populated only for card transactions.
Actual Post DateGalileoDATETIMEDate-time when the ACH credit was posted to the account: MMDDYYYY hh24:mm:ss
Original Settlement DateNacha fileDATETIMEDate-time when the ACH credit was originally to be posted: MMDDYYYY hh24:mm:ss
ACH RETURN CODENacha fileCHAR (3)Code that indicates why an ACH request was returned
ACQUIRING IDDE032VARCHAR2 (11)Identifier for the merchant's acquirer
ACTIVITY IDGalileoNUMBERIdentifier for the transaction in the activity table, which includes anything that affects the available balance; ID is unique per core
CST AGENT NAMEGalileoVARCHAR2 (125)Name of the CST agent that initiated the transaction
ARNVARCHAR2 (23)Mastercard only. Acquirer reference number
ASSOCIATIONGalileoCHAR (3)Three-letter abbreviation for the card network: DEB (Maestro), MAS (Mastercard credit), STA (STAR), VIS (Visa), DIS (Discover), ALL (Allpoint) or PLS (Pulse)
ASSOCIATION TRANS IDDE062VARCHAR2 (15)Visa only. Transaction identifier that was assigned by the network
AUTH AMOUNTNUMBER (9,2)Signed. Amount that was authorized.
AUTHORIZATION RESPONSEDE039CHAR (2)Response code that was returned to the merchant
AUTHORIZATION STATUSGalileoCHAR (1)Status of the authorization
AUTH TRANSACTION CODEGalileoVARCHAR2 (10)Transaction code for the original authorization
BAIDE104VARCHAR2 (3)Visa only. Business Application Identifier, which identifies the type of Visa card load
BATCH HEADERNacha fileVARCHAR2 (94)Record header for incoming ACH credits
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
CASE SENSITIVE FLAGGalileoVARCHAR2 (1)Which case the otype in TRANSACTION CODE/TYPE is: Y(uppercase) , N (lowercase) or blank (not specified)
CASHBACK AMOUNTDE054NUMBER (9,2)Amount of the transaction that was given to the cardholder as cash
CCA FEEDE111NUMBER (9,2)Currency conversion assessment (CCA) fee
CCA FEE AMOUNT SETTLEDE111NUMBER (9,2)Amount of the settlement on which the CCA fee was assessed
CCA FEE CURRENCY CODEDE111VARCHAR2 (3)Currency code for CCA FEE
CCA FEE SIGNGalileoVARCHAR2 (1)CCA fee sign: C (credit) or D (debit)
CHECK NUMBERGalileoNUMBER (19)Number of the check that was cashed
company_descNacha fileVARCHAR2 (15)Company description for incoming ACH transactions
company_nameNacha fileVARCHAR2 (20)Company name for incoming ACH transactions
CONTACTLESS TRANSACTIONSDE022CHAR (1)Whether the card was authenticated using contactless technology: Y (contactless) or N (not contactless)
Conversion Rate - BillingDE010VARCHAR2 (9)The currency conversion rate when converting TRANSACTION AMOUNT to BILLING AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
Conversion Rate - ReconciliationDE009VARCHAR2 (8)The currency conversion rate when converting TRANSACTION AMOUNT to SETTLE AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
CARD PRESENT INDICATORDE061CHAR (1)Whether it was a card-present transaction: Y (card present) or N (card not present)
CREDIT INDICATORGalileoCHAR (1)Whether the transaction arrived at Galileo over credit rails: Y (credit rails) or N (debit rails)
Settlement DateDE015CHAR (4)Date on which the card transaction settled: MMDDYYYY
DE28DE028VARCHAR2 (9)Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator
RETRIEVAL_REFERENCE_NUMBERDE037VARCHAR2 (12)Retrieval reference number. Julian date plus number YDDDxxxxxxxx
RESPONSE SOURCE/REASON CODESDE044VARCHAR2 (25)Visa only. Identifies the source of the DE039 authorization response decision
AVS CHECKDE063VARCHAR2 (50)AVS check information
ICAVARCHAR2 (6)Mastercard only. Interbank Card Association number, assigned by Mastercard to a financial institution
Drawdown Settlement DateDATETIMEDate-time when the amount was taken from the issuing bank account: MMDDYYYY hh24:mm:ss
EFFECTIVE_DTNacha fileDATETIMEFor an ACH transaction, the effective date-time when the ACH payment should post. Usually set by the bank to the actual date when the payment is posted, in case Galileo posts the payment early: MMDDYYYY hh24:mm:ss
EXPIRED AUTH CODEGalileoNUMBER (10)AUTHORIZATION CODE of the expired authorization that corresponds to this force-posted transaction. This field is populated only for card transactions.
FEE PROGRAM INDICATORDE063SE19VARCHAR2 (3)Visa only. Interchange reimbursement fee program indicator, applied to select ATM transactions
FULL MERCHANT DESCRIPTIONDE043VARCHAR2Merchant name and full address and store number if provided by the network at the time of settlement
IC FEE AMOUNTFLOAT (126)Signed. Interchange fee amount
INTERCHANGE RATE DESIGNATORDE063SE2VARCHAR2 (2 bytes)Identifies the transaction as domestic or international: 0 (U.S. region) 1 (Canada, Asia Pacific, Europe, Latin America, Middle East/Africa regions) or 2 (Intra-country)
IS AFT TRANSACTIONDE003CHAR (1)Whether this is an account funding transaction: Y (AFT) or N (not AFT)
FOREIGN TRANSACTION INDICATORGalileoCHAR (1)Whether the transaction is foreign relative to the account's country: Y (foreign) or N or null (domestic). This field is populated only for card transactions.
OTC_FLAGDE003CHAR (1)Whether the transaction included an over-the-counter cash advance. Y (cash advance) or N (no cash advance)
PIN FLAGGalileoCHAR (1)Whether a PIN was used to authenticate the card: Y (PIN) or N (no PIN)
LOAD_DTNacha fileDATETIMEACH load date (the date-time the incoming ACH was loaded) MMDDYYYY hh24:mm:ss
LOCAL AMOUNTDE004NUMBER (16,4)Signed. Transaction amount in the currency at the point of sale
LOCAL CURRENCY CODEDE049CHAR (3)Currency code for LOCAL AMOUNT
LOCAL SURCHARGE AMOUNTDE028NUMBER (16,4)Signed. Local surcharge amount, a fee applied to the ATM withdrawal amount by the ATM's operator
MC_SEQ_CNTSettlement fileNUMBER (2)Multi-clearing sequence count. Total number of clearings in this sequence
MC_SEQ_NOSettlement fileNUMBER (2)Multi-clearing sequence number. Position of this clearing in the sequence
MOBILE TRANSACTIONSGalileoCHAR (1)Whether a token requestor ID was present: Y (mobile wallet) or N (not mobile wallet)
MESSAGE TYPE FLAGGalileoCHAR (2)The otype of the authorization
NAMENacha fileVARCHAR2Payee name for direct deposit
FILE IDSettlement fileVARCHAR2 (25)Visa only. Identifier for the settlement file
ON_USVARCHAR2Number of the remote-deposit check
ROLLING BALANCEGalileoNUMBER (9,2)Signed. Available balance after this transaction took place. If you are the system of record instead of Galileo, this value may be inaccurate.
ORIGINAL AUTH CODEGalileoNUMBERSource ID for the transaction that this fee was assessed to
SECURE CODESettlement fileVARCHAR2Mastercard only. Secure code from the settlement file
POS CONDITION CODEDE025VARCHAR2 (2)The conditions under which the transaction took place at the point of sale. See DE025 Codes.
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.
POS TYPEGalileoCHAR (3)Type of card authentication at the point of sale: SIG (signature) or PIN
POSTED_EARLYNacha fileCHAR (1)Whether the ACH transaction was posted early: Y (early) or N (not early)
ENDORSEMENT DATEDATETIMEPresentment date-time for a paper check: MMDDYYYY hh24:mm:ss
PRIOR IDGalileoNUMBER (12)The ID of a transaction that is linked to this transaction, such as the transaction that triggered this transaction
RECURRING TRANSACTION FLAGDE061CHAR (1)Whether this is a recurring transaction: Y (recurring) or N (not recurring)
RECEIVE_DTNacha fileDATETIMEDate-time that the Nacha file arrived at Galileo. MMDDYYYY hh24:mm:ss
CHECK RETURN CODECHAR (3)Code to indicate why a paper check was returned
REVERSAL IDGalileoNUMBERContains the authorization ID of the previous authorization in a series, such as with incremental authorizations, reversals, and completions. This field is populated only for card transactions. See Linking transactions in the About Transactions guide for more information.
SETTLE AMOUNTDE005NUMBER (16,4)Signed. Transaction amount in the settlement currency
SETTLE CURRENCY CODEDE050CHAR (3)Currency code for SETTLEMENT AMOUNT
SETTLE SERVICE IDSettlement fileVARCHAR2 (10)Identifier for the transaction within the settlement service
SETTLE DATESettlement fileDATETIMEDate and time when the transaction was settled: MMDDYYYY hh24:mm:ss
SETTLEMENT SERVICE CODESettlement fileCHAR (1)Uniquely identifies the settlement service
SETTLEMENT SERVICE IDSettlement fileCHAR (10)Settlement service ID
SLI INDICATORDE048SE42CHAR (1)Security level indicator, included with Mastercard 3DS authentication.
SOURCEGalileoNUMBER (1)Number assigned to a network: 1 (Maestro), 2 (Mastercard credit), 3 (STAR), 4 (Visa), 5 (Discover), 6 (Allpoint) or 7 (Pulse)
SOURCE IDGalileoNUMBER (18)For card transactions, the source ID is the same as the authorization ID. For other types of transactions, the source ID maps back to the original transaction, such as payment ID, adjustment ID or ACH transaction ID. The ID field in the CST corresponds to the source ID.

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.
SOURCE INSTITUTION NAMENacha fileVARCHAR2 (35 bytes)The source institution name for the incoming ACH credit
SOURCE_TRACENacha fileVARCHAR2 (20 bytes)ACH trace number assigned by the external originating institution to incoming ACH transactions
SOURCE TYPECHAR (1)Type of source: S (settlements) or A (activity)
TERMINAL IDDE041CHAR (8)Identifier of the card reader
TERMINAL NETWORKGalileoVARCHAR2 (50)Network that the card reader used
TOKEN_REQUESTOR_IDVARCHAR2 (11)Identifier for the token requestor. See the Lookup file for valid values.
TRACE NUMBERDE011
Nacha file
VARCHAR2 (20)For a card transaction, an identifier from the merchant that is included with all messages related to that transaction.

For an ACH transaction the trace number assigned by Galileo to outgoing ACH transactions.
TRANSACTION DESCRIPTIONVARCHAR2 (100)Description for certain transactions
XIDGalileoNUMBERInternal account identifier; has a 1:1 relationship with the PRN
LOADS AUTH IDGalileoNUMBEROriginal authorization ID for card loads
PDS1002Settlement fileVARCHAR2 (13)Custom field
PDS1018Settlement fileVARCHAR2 (13)Custom field
RESPONSE SOURCE/REASON CODESVARCHAR2 (1)Response source/reason codes, if provided by the network
ach_trace_numberVARCHAR2 (20)ACH trace number
IVA_TAXNUMBERMastercard only. Impuesto al valor agregado. Value-added tax. Colombia only.
IAC_TAXNUMBERMastercard only. Impuesto al consumo. Consumption tax. Colombia only.
ipm_auth_codeSettlement fileCHAR (6)Authorization ID response from the issuer that authorized the transaction
Message Reason CodeSettlement fileCHAR (4)Mastercard only. Indicates why a transaction was initiated
MERCHANT POSTAL CODEVARCHAR2 (5)Postal code for the merchant's location.
Conversion Rate DE9DE009VARCHAR2 (8)The currency conversion rate when converting TRANSACTION AMOUNT to SETTLE AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
Conversion Rate DE10DE010VARCHAR2 (8)The currency conversion rate when converting TRANSACTION AMOUNT to BILLING AMOUNT. The string has the pattern <shift digit><exchange rate digits>. The first digit specifies how many places from the right the decimal is moved. For example, 69985022 translates to an exchange rate of 9.985022%
TRANSACTION LIFECYCLE IDSettlement fileVARCHAR2 (16)Mastercard only. Transaction lifecycle identifier, which allows tracking throughout a transaction's lifecycle
TRANSACTION LIFECYCLE ID/ ASSOCIATION TRANSACTION ID FOR ALL NETWORKSVARCHAR2 (15)Transaction lifecycle ID/ association transaction ID for all networks
PDS0185Settlement fileVARCHAR2 (33)Accountholder authentication value (AAV) (Mastercard) or cardholder authentication verification value (CAAV) (Visa), returned for 3DS transactions.
PIN_ENTRY_CAPABILITYDE022CHAR (1)Indicates methods available at the terminal for PIN entry. See PIN entry capability.
Advice Reason CodeDE060VARCHAR2 (61)Indicates the specific reason for an advice
Authorizing Agent ID CodeDE121CHAR (11)The actual processing facility that approved or declined an authorization request message
Banknet Reference NumberDE063VARCHAR2 (9)Value received for Maestro updates
Domestic Card Acceptor Tax IDPDS 0180VARCHAR2 (20)U.S. tax ID of the card acceptor

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. All fields are strings.

FieldLengthDescription
RECORD TYPE1The type of record. D — Detail; H — Header; T — Trailer
FILE TYPE1The RDF that contains the field: A (Authorized Transactions), C (Customer Master), D (Account Card), or P (Posted Transactions)
FIELD NAME30Name of the field in the RDF
CODE10Possible values for the field
DESCRIPTION50Description of the CODE value