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.
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.
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
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.
|Type||Description||Banknet (MC credit)||Maestro (MC debit)||Visa||Interlink||Plus||STAR||Allpoint||MoneyPass||Discover||Pulse||Presto|
|8||Mobile wallet or cash-transfer app settlement||SE8|
|11||Completion without preauthorization||AU11|
|A||Authorization, or purchase with PIN||AUA||DBA|
|J||Adjustment (debit or credit)||VSJ||ISJ||PLJ|
|L||Preauthorization or Discover authorization||AUL||DBL||VIL||VIL||VIL||SSL||DCL|
|V||Reversal debiting balance||SDV||VSV|
|W||ATM withdrawal, cash||DBW|
|Y||ATM withdrawal, credit||VIY|
* For Mastercard Banknet, a force post has the transaction code
** For Mastercard Banknet, merchant credits are adjustments with transaction code
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.
|Type||Description||Banknet (MC credit)||Maestro (MC debit)||Visa||Interlink||Plus||STAR||Allpoint||Discover||Pulse|
|ao||Allpoint load reversal||ADao|
|VH*||Visa Money Transfer||PMVH|
|VT*||Visa Money Transfer||PMVT|
* The Visa Money Transfer types are differentiated by the BAI. See the Business Application Identifier enumeration for the definitions.
VT— All other BAIs
In the Authorized Transactions RDF, the
TRANSACTION CODE field may contain these values.
These transaction types are also present in Authorization Events API webhooks as
auth_tran_type. They are not available in the Program API.