Finding Transaction Data

Consult this page to see where to find each type of transaction. This table summarizes where you can see the transactions; click on the link in the left column to see details on each transaction type's availability.

• GAO — Get Account Overview

* Included with the amount, not broken out separately

Transaction resources

These are the data outputs that contain transaction data:

• Auth API — A webhook that relays information from an authorization request, which is presented to participating Galileo clients so that they can participate in authorization decisions.
• Program API responses — The Program API has several endpoints that return transactions, including these:
  • Get Account Overview — The authorizations section in the response returns the same data as Get Authorization History, and the transactions section returns the same data as Get Transaction History.
  • Get Authorization History — All approved authorizations that have not been settled, reversed, completed, or expired
  • Get Transaction HIstory — All posted transactions: settlements, payments, adjustments and fees. Does not include pending authorizations
  • Get All Transaction History — All ledger activity including authorizations backouts
  • Other specific transaction-retrieval endpoints, as described in Program API in the Transaction History guide.
• About the Raw Data Files (RDFs) — Text files that contain all activity for a program during the previous day.
  • Authorized Transactions RDF — All transactions that arrived at Galileo through the authorization stream.
  • Posted Transactions RDF — All posted transactions: settlements, payments, adjustments and fees.
• Events API webhooks — Real-time notifications of account activity.
• CST — Web-based application for customer support functions. The Account Info > All Transactions screen returns the same transactions as Get All Transaction History.

Transaction details

This section details how to identify each transaction type and the conditions under which the transaction type appears in the data source.

Approved authorization

Identifier: otype: A

An approved authorization is available as follows:

• Auth API with auth_type: Auth and response_code: 00.
• Get Authorization History and the authorizations section of Get Account Overview, until the authorization is settled, reversed, completed or expired
• Get All Transaction History and CST
• Authorized Transactions RDF
• BAUT: auth event messages
• BEXP: auth_exp upon expiry, if it's not settled, reversed, or completed

Also see:

• Authorization
• Scenario 13: International Authorization

---

Approved preauthorization

Identifier: otype: L

An approved preauthorization is available as follows:

• Auth API with auth_type: Auth and response_code: 00.
• Get Authorization History and the authorizations section of Get Account Overview, until the authorization is settled, reversed, completed or expired
• Get All Transaction History and CST
• Authorized Transactions RDF
• BAUT: auth event messages
• BEXP: auth_exp upon expiry, if it's not settled, reversed, or completed

Also see:

• Identifying preauthorizations in the Authorization guide
• Scenario 2: Preauthorization with Completion

Denied authorization

Identifier: otype: n/a

A denied authorization is available as follows:

• Auth API when auth_type: Auth and response_code != 00.
• Get All Transaction History and CST with deny_code populated
• Authorized Transactions RDF
• DAUT: denied_auth or other denied_auth_x event message

Also see:

• Authorization checks in the Authorization guide

Reversal

Identifier: otype: R

A reversal is available as follows:

• Auth API with auth_type: Reversal
• Get Auth History and the authorizations section of Get Account Overview, until it expires
• Get All Transaction History and CST
• Authorized Transactions RDF
• AAAU: auth event message
• BEXR: auth_exp_reversal event message, upon expiry

Also see:

• Reversals in the Crediting Cardholder Accounts guide
• Scenario 4: Reversal on Authorization Before Clearing (Mastercard)
• Scenario 5: Reversal on Preauthorization Before Clearing (Visa)

Completion

Identifier: otype: C

A completion is available as follows:

• Auth API with auth_type: Advice and transaction_type: Auth
• Get Auth History and the authorizations section of Get Account Overview
• Get All Transaction History and CST
• Authorized Transactions RDF
• AAAU: auth event message

Also see:

• Completion in the Settlement guide
• Scenario 2: Preauthorization with Completion
• Scenario 23: Account Funding Transaction

Backout

Identifier: See Backout in the Settlement guide for backout activity types.

Backouts are visible as follows:

• Get All Transaction History and CST

Settlement

Identifier: See Settlement file in the Transaction Types enumeration for settlement transaction codes

A settled authorization is available as follows:

• Get Transaction History and the transactions section of Get Account Overview
• Get All Transaction History and CST
• Posted Transactions RDF
• SETL: setl event message

Also see:

• Settlement
• Scenario 1: Authorization with Settlement

Merchant credit

Identifier: otype: Z

A merchant credit for any network but Mastercard credit is available as follows:

• Auth API with transaction_type: Merchant Credit
• Get Auth History and the authorizations section of Get Account Overview
• Get All Transaction History and CST
• Authorized Transactions RDF
• Posted Transactions RDF
• SETL: setl event message

Also see:

• Merchant credits in the Crediting Cardholder Accounts guide
• Scenario 10: Merchant Credit (Visa)

Merchant credit, Mastercard

Identifier: trans_code: ADC

A Mastercard merchant credit is available as follows:

• Auth API with transaction_type: Merchant Credit
• Get All Transaction History and CST
• Posted Transactions RDF
• BADJ adj event message

Also see:

• Merchant credits in the Crediting Cardholder Accounts guide
• Scenario 9: Merchant Credit (Mastercard Banknet)

Force post

Identifier: otype: M

A force post is available as follows:

• Get All Transaction History and CST
• Authorized Transactions RDF
• Posted Transactions RDF
• SETL: setl event message

Also see:

• Driving an account negative in the Settlement guide
• Scenario 19: Force Post

Card load

Identifier: See Card loads in the Transaction Types enumeration for card-load otypes.

A card load is available as follows:

• Auth API with transaction_type: Payment
• Get All Transaction History and CST
• Authorized Transactions RDF
• Posted Transactions RDF
• BPMT: pmt
• AAPM: auth_payment (not force post)
• SETL: setl (force post only)

Also see:

• Card loads in the Crediting Cardholder Accounts guide
• Scenario 17: Card Load (Maestro)
• Scenario 21: Card Load (Visa)

Card load reversal

Identifier: See Card loads in the Transaction Types enumeration for card-load reversal otypes

A card load reversal is available as follows:

• Auth API with auth_type: Reversal and transaction_type: Payment
• Get All Transaction History and CST
• Authorized Transactions RDF
• Posted Transactions RDF
• BPMT: pmt
• AAPM: auth_payment (not force post)
• SETL: setl (force post only)

Also see:

• Scenario 20: Card Load Reversal (Maestro)
• Scenario 22: Card Load Reversal (Visa)
  | |
  | :-: |
  | Back to top |

AVS-only check

Identifier: trans_code: DA0

An AVS-only check is available as follows:

• Auth API with avs_result populated and trans_amount: 0.00
• Get All Transaction History and CST
• Authorized Transactions RDF
• AAAU: auth

RTF transfer

Identifier: otypes: FY, SY, FZ, SZ

The funds transfers between RTF or CCL funding accounts and spending accounts is as follows:

• Get Transaction History and the transactions section of Get Account Overview, funding account only
• Get All Transaction History and CST, funding and spending accounts
• Posted Transactions RDF, funding and spending accounts

Also see:

• Real-Time Funding
• Corporate Credit
• Real-Time Funding Transaction Examples
• Corporate Credit Transaction Examples

ACH transaction

Identifier: act_types: PM and AD, otypes determined by your funds-flow configuration.

Successful ACH transactions (incoming and outgoing, credit and debit) are visible as follows:

• Get Transaction History and the transactions section of Get Account Overview
• Get All Transaction History and CST
• Posted Transactions RDF
• Get ACH Transaction History and Get Deposit History
• BADJ: adj and BPMT: pmt event messages

Also see:

• About ACH

Wire transfer

Identifier: otypes: wi, wo, WR

Successful wire transactions are visible as follows:

• Get Transaction History and the transactions section of Get Account Overview
• Get All Transaction History and CST
• Posted Transactions RDF
• BADJ and BPMT event messages

Returned incoming wire.

• RTNG: pmt_hub_returned

Also see:

• About Wires
• Creating a Wire Transaction

API payment or adjustment

Identifier: act_types: PM or AD, otype determined by funds flow configuration.

Transactions initiated by Create Payment, Create Adjustment, and Create Account Transfer are visible as follows:

• Get Transaction History and the transactions section of Get Account Overview
• Get All Transaction History and CST
• Posted Transactions RDF
• BADJ: adj and BPMT: pmt event messages

Also see:

• Creating a Payment
• Creating an Adjustment
• Creating an Internal Transfer

Fee

Identifier: act_type: FE, otype determined by funds flow configuration.

Fees are visible as follows:

• Auth API for card-transaction fees, broken out in fee_amount and included in amount
• Get Authorization History and GAO, included in amount in authorizations section
• Get Transaction History and the transactions section of Get Account Overview, broken out as FExxxx
• Authorized Transactions RDF, included in amount
• Posted Transactions RDF, broken out as FExxxx
• Get Fee History
• BFEE: fee event message

Also see:

• Scenario 11: ATM Withdrawal
  | |
  | :-: |
  | Back to top |

Fee reversal

Identifier: act_type: FE, otype determined by funds flow configuration.

Fees reversals are visible as follows:

• Auth API for card-transaction fees, broken out in fee_amount and included in amount
• Get Authorization History and GAO, included in amount in authorizations section
• Get Transaction History and the transactions section of Get Account Overview, broken out as FExxxx
• Authorized Transactions RDF, included in amount
• Posted Transactions RDF, broken out as FExxxx
• FREV: fee_reversal event message

Disputes

Identifier: See Disputes in the Transaction Types enumeration for dispute-related otypes

Dispute transactions are visible as follows:

• Get Transaction History and the transactions section of Get Account Overview
• Get All Transaction History and CST
• Posted Transactions RDF
• DSPC: dispute_pc for provisional credit along with BADJ: adj

Also see:

• Transaction codes for disputes in the Disputes at Galileo guide
• Disputes in the Card Transaction Examples guide.

Hold

Identifier: act_type: TH

Holds and hold expiries are visible as follows:

• Get Hold History
• CRHD: create_hold and EXHD: expire_hold event messages
  | |
  | :-: |
  | Back to top |