Transaction Types

The transaction type, also called the otype, is a code that is combined with the activity type (act_type) for a complete transaction code (trans_code). Transaction codes identify where a transaction originated and what kind of transaction it is.

The first two characters of a transaction code are the Activity Type and the remaining characters are the transaction type. For example, a Mastercard Banknet retail settlement is SE5, which is activity type SE (Mastercard Banknet settlement) plus transaction type 5 (retail sale), whereas an Interlink preauthorization is VIL, which is activity type VI (Visa authorization) plus transaction type L (preauthorization). See Classifying transactions in the About Transactions guide for more information.

The tables below show the transaction types for authorization and settlement transactions. Your program may not use all of the types shown here. Use the lookup file that Galileo supplies to see all of the transaction types that you will be using.

📘

Note

For payments (PM), adjustments (AD) and fee (FE) activity types, Galileo will supply you with a curated list of transaction types that are specific to your use case and bank requirements. However, some payments and adjustments take place over network rails; these transactions are included in the Additional network transactions table.

Authorization and settlement transaction types

This table shows how transaction types are paired with activity types for each card network. Where there are two activity types shown, the first is for authorizations and the second for settlements. For example, the transaction code for a retail Interlink authorization is VIA and its settlement is ISA.

These transaction codes are visible in the Posted Transactions RDF, Program API responses, and the CST. (In the CST, the activity type is spelled out in the Type field, and the transaction code is labeled Type Code.) For the TRANSACTION CODE in the Authorized Transactions RDF, see Authorization types, below.

TypeDescriptionBanknet (MC credit)Maestro (MC debit)VisaInterlinkPlusSTARAllpointMoneyPassDiscoverPulsePresto
5Retail settlementSE5
7Cash disbursementSE7
8Mobile wallet or cash-transfer app settlementSE8
11Completion without preauthorizationAU11
AAuthorization, or purchase with PINAUADBA
SDA
VIA
VSA
VIA
ISA
VIA
PLA
STA
SSA
PUA
SPA
PRA
BBalance inquiryAUBDBBVIBVIBSTB
CPreauthorization completionSDCVSCISCSSCSPC
FFee collectionVSFISF
IBalance inquirySDI
JAdjustment (debit or credit)VSJISJPLJ
LPreauthorization or Discover authorizationAULDBLVILVILVILSSLDCL
SCL
MForce post*SDMVSMISMPLMSSMASMMPMSCMSPM
RReversalAURDBR
SDR
VIR
VSR
VIR
ISR
PLRSTR
SSR
APR
ASR
MPRSCRSPRPRR
RWCash reversalVSRW
VReversal debiting balanceSDVVSV
WATM withdrawal, cashDBW
SDW
VIW
VSW
VIW
ISW
VIW
PLW
STW
SSW
APW
ASW
MPWPUW
SPW
PRW
YATM withdrawal, creditVIY
VSY
ZMerchant credit**DBZ
SDZ
VIZ
VSZ
VIZ
ISZ
VIZ
PLZ
SSZSCZSPZ

* For Mastercard Banknet, a force post has the transaction code SE5.
** For Mastercard Banknet, merchant credits are adjustments with transaction code ADC.

Additional network transactions

Some transactions that take place on network rails are classified as adjustments (AD) and payments (PM). Card loads are payments, and Mastercard Banknet merchant credits and chargeback-related transactions are adjustments.

The chargeback-related codes (chargeback, second presentment, exceptions) are valid only when using Galileo's disputes process. All of these transaction types are case-sensitive.

TypeDescriptionBanknet (MC credit)Maestro (MC debit)VisaInterlinkPlusSTARAllpointDiscoverPulse
adChargebackADad
AOAllpoint loadPMAO
apSecond presentmentADap
asExceptionADas
CMerchant creditADC
DCChargebackADDC
DEExceptionsADDE
dhChargebackADdh
djSecond presentmentADdj
dkExceptionADdk
dsSecond presentmentADds
fdFinal disputeADfdADfdADfdADfdADfdADfdADfdADfdADfd
HChargebackADH
hChargebackADhADhADh
ISecond presentmentADI
JArbitrationADJ
jSecond presentmentADjADjADj
kExceptionADkADkADk
LCDiscover loadPMLC
MLMastercard loadPMML
MXMaestro loadPMMX
pdChargebackADpd
peSecond presentmentADpe
pzExceptionADpz
SCSecond presentmentADSC
seChargebackADse
SSExceptionADSS
tcTemporary creditADtcADtcADtcADtcADtcADtcADtcADtcADtc
VA*Visa Money TransferPMVA
VH*Visa Money TransferPMVH
VLVisa ReadyLinkPMVL
VT*Visa Money TransferPMVT

* The Visa Money Transfer types are differentiated by the BAI. See the Business Application Identifier enumeration for the definitions.

  • VAAA
  • VHBP, CP, FD, GD, GP, LO, MD, OG, PD
  • VT — All other BAIs

Authorization types

In the Authorized Transactions RDF, the TRANSACTION CODE field may contain these values.

TypeDescription
4Convenience check
5Purchase
6Merchant credits
7Cash disbursements
8Unique transactions
9ATM disbursements
10Balance inquiry
11Transfer
13Quasi-cash
28Load
50Bill pay

These transaction types are also present in Authorization Events API webhooks as auth_tran_type. They are not available in the Program or Auth APIs.