Transaction Types

The transaction type, also called the otype, is a code that is combined with the activity type (act_type) to create 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 otype. For example:

  • SE5 — Mastercard Banknet retail settlement
    • activity type SE (Mastercard Banknet settlement)
    • otype 5 (retail sale)
  • VIL — Visa preauthorization
    • activity type VI (Visa authorization)
    • otype L (preauthorization

See Classifying transactions in the About Transactions guide for more information.

📘

Note

Most payment (PM), adjustment (AD) and fee (FE) otypes are in the Funds Flow document that Galileo provides you. (You can see your custom otypes in the CST under System Administration > Web Services > Provider Transaction Types with Right ID 165.) However, some payments and adjustments are triggered by card transactions; those universal otypes are included in the tables below.

To see where these codes are visible, go to Activity type and transaction type in the Galileo system in the About Transactions guide.

Transaction type (otype) lookup

This table provides a quick reference for standalone otypes that are related to card transactions. To see how the otypes combine with the activity types, see Transaction codes. These codes are case-sensitive.

Type (otype)Description
5Mastercard retail purchase
7Mastercard cash disbursement
8Mastercard mobile wallet or cash-transfer app settlement
11Mastercard completion without preauthorization
AAuthorization, or purchase with PIN
adAllpoint chargeback
AOAllpoint card load
aoAllpoint card load reversal
apAllpoint second presentment
asAllpoint exception
BBalance inquiry
CCompletion
DMastercard merchant credit reversal
DCDiscover chargeback
DEDiscover exception
dhMaestro chargeback
djMaestro second presentment
dkMaestro exception
dsDiscover second presentment
FFee collection
HMastercard chargeback
hVisa chargeback
IMastercard second presentment
JMastercard arbitration or Visa, Interlink, Plus adjustment
KLoad reversal
kVisa exception
LPreauthorization not fully completed
MForce post
MLMastercard load
MXMaestro card load or reversal
PPreauthorization fully completed
pdPulse chargeback
pePulse second presentment
pzPulse exception
QTokenization request
qMastercard load reversal
RAuth reversal
RWVisa cash reversal
SCSTAR second presentment
SSSTAR exception
seSTAR chargeback
TCard load authorization request
tcTemporary credit
VReversal debiting balance
VHVisa Money Transfer load
VLVisa ReadyLink load
VTVisa Money Transfer load
WATM withdrawal, cash, or in-person cash withdrawal (Mastercard credit)
YATM withdrawal, credit
yVisa ReadyLink load reversal
ytVisa Direct OTC load reversal
ZMerchant credit

Transaction codes

The tables below show how the activity type combines with the otype to create a transaction code (trans_code). Your program may not use all of the codes shown here. Use the curated list that Galileo gave you to see all of the otypes for your program.

Authorization and settlement

These tables show transaction codes for transactions over card networks. The first table contains the codes associated with transactions that arrive through the authorization stream, and the second contains codes associated with transactions from the settlement batch files.

Authorization stream

See Authorization for more information.

NetworkAuthPreauthCompletionReversalATM authMerchant credit authBalance inquiry
Banknet (MC credit)AUAAUL
AUP
AUC
AU11*
AURAUW§AUZAUB
Maestro (MC debit)DBADBLSDCDBRDBWDBZDBB
SDI
VisaVIAVILVICVIRVIYVIZVIB
InterlinkVIAVILVICVIRVIWVIZVIB
PlusVIAVILVICVIRVIWVIZVIB
STARSTASTLSTCSTRSTWSTB
AllpointAPRAPW
MoneyPassMPRMPW
DiscoverDCLSCR
PulsePUAPUW
PrestoPRAPRRPRW

§In-person cash withdrawals, not ATMs
* Completion without prior authorization, similar to a force-post.

Settlement file

See Settlement for more information.

NetworkSettle*Settle reversalMerchant credit settleForce postATM settle
Banknet (MC credit)SEADC§
ADD
SE5
Maestro (MC debit)SDA
SDC
SDRSDZSDMSDW
VisaVSA
VSC
VSRVSZVSMVSW
InterlinkISA
ISC
ISRISZISMISW
PlusPLAPLZPLMPLW
STARSSA
SSL
SSRSSZSSMSSW
AllpointASRASMASW
MoneyPassMPMMPW
DiscoverSCLSCZSCM
PulseSPASPZSPMSPW
PrestoPRW

* Includes settlements of both standard auths and completions.
§ Mastercard merchant credits are processed as adjustments, and ADD is the merchant credit reversal.
Mastercard settlements (SE) have different codes depending on the type of transaction being settled:

  • SE5 — Retail settlement or settled completion
  • SE7 — Cash disbursement settlement
  • SE8 — Mobile wallet or cash-transfer app settlement

Other transaction codes

You may also encounter some of these network-related transaction codes:

  • SDV — Maestro reversal debiting balance
  • VSV — Visa reversal debiting balance
  • VSRW — Visa cash reversal
  • VSF, ISF — Visa and Interlink fee collection
  • VSJ, ISJ, PLJ — Visa, Interlink and Plus adjustments

Card loads

Card loads that take place on network rails are classified as adjustments (AD) and payments (PM) in the Galileo system. Card loads are payments and load reversals are adjustments. All of these transaction codes are case-sensitive. See Card loads for more information.

NetworkCard loadCard load reversal
AllpointPMAOADao
Green Dot load§PMGTADgd
Green Dot direct deposit§PMGOADGO
Banknet (MC credit)PMMLADq
DiscoverPMLC
MoneyGram§PMMGADmg
Maestro (MC debit)PMMXADMX
STARPMSDADsd
Western Union§PMSPADwu
Visa ReadyLinkPMVLADy
Visa MoneyTransfer*PMVT
PMVH
ADyt

§ These loads do not arrive at Galileo over card-network rails but rather via special APIs. Do not include these transactions with settlement totals when doing reconciliation
* The Visa Money Transfer types are differentiated by the BAI. See the Business Application Identifier enumeration for the definitions.

  • VHAA ,BP, CP, FD, GD, GP, LO, MD, OG, PD
  • VT — All other BAIs

Disputes

The dispute-related codes (chargeback, second presentment, exception, arbitration) are valid only when using Galileo's disputes process. All of these transaction codes are case-sensitive. See Transaction codes for disputes in the Disputes at Galileo guide for definitions of the table columns.

These transaction codes apply to all networks:

  • ADfd — Final dispute
  • ADtc — Temporary credit
NetworkChargebackSecond presentmentExceptionArbitration
Banknet (MC credit)ADHADIADJ
Maestro (MC debit)ADdhADdjADdk
Visa
Interlink
Plus
ADhADjADk
STARADSCADSSADse
AllpointADadADapADas
DiscoverADDCADdsADDE
PulseADpdADpeADpz

Authorization types

These authorization types are derived from DE003 and may be present in the following data sources:

These values are not available from the Program API.

CodeDescription
4Convenience check
5Purchase
6Merchant credits
7Cash disbursements
8Unique transactions
9ATM disbursements
10Balance inquiry
11Transfer
13Quasi-cash
26Visa Direct OCT
28Card load, including Visa ReadyLink
30Visa account funding transaction
50Bill pay