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
Auth APIGet Authorization History and GAOGet Transaction History and GAOGet All Transaction History and CSTAuthorized Transactions RDFPosted Transactions RDFEvents API
Approved authorizationXXXXBAUT
Approved preauthorizationXXXXBAUT
Denied authorizationXXXDAUT
ReversalXXXXAAAU
CompletionXXXXAAAU
BackoutX
SettlementXXXSETL
Merchant creditXXXXXSETL
Merchant credit, MastercardXXXBADJ
Card loadXXXXXXAAPM
BPMT
SETL
Card load reversalXXXXXXAAPM
BADJ
SETL
AVS-only checkXXXAAAU
ACHXXXBADJ
BPMT
API payment or adjustmentXXXBADJ
BPMT
FeeXX*XXXBFEE
Fee reversalXXXFREV
RTF transferXXX
DisputeXXXDSPC
BADJ
HoldCRHD
EXHD

* Included with the amount, not broken out separately

Transaction resources

These are the data outputs that contain transaction data:

  • Auth API — A webhook that contains 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.
  • 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:

Back to top


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:

Back to top


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:

Back to top


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:

Back to top


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:

Back to top


Backout

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

Backouts are visible as follows:

  • Get All Transaction History and CST

Back to top


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:

Back to top


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:

Back to top


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:

Back to top


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:

Back to top


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:

Back to top


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:

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

Back to top


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:

Back to top


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:

Back to top


Back to top


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:

Back to top


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:

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

Back to top


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:

Back to top


Hold

Identifier: act_type: TH

Holds and hold expiries are visible as follows:

Back to top