The second row of this table shows the field that contains the network code or text. For example, in the Auth API, the subnetwork
field contains Visa
for the Visa credit (signature) network, whereas in the Events API Visa is represented as network: V
, in the responses to the Program API it's network_code: V
, and in the RDFs it's NETWORK CODE V
.
Network | Auth API | Events API | Program API | RDFs |
---|---|---|---|---|
subnetwork | network | network_code | NETWORK CODE | |
Allpoint | Allpoint | A | A | A |
Cirrus | Mastercard Debit Switch | P | C | P |
Discover | Discover | D | D | D |
Maestro | Mastercard Debit Switch | P | P | P |
Mastercard | Mastercard Banknet | M | M | M |
MoneyPass | Star MoneyPass | S* O** | S | S |
Presto | Star Presto | S* R** | S | S |
Pulse | Pulse | B | B | B |
STAR | Star | S | S | S |
Visa | Visa | V | V | V |
Visa Interlink | Visa Interlink | V* I** | I | I |
Visa Plus | Visa PLUS | V* E** | Z | P |
* Authorization Events
** Settlement Events
When Galileo sends an Authorization Event message for the Visa or STAR networks, the network
field contains the network, whereas for the Settlement Event message, network
contains the subnetwork. For example, an auth
message for the Visa Plus subnetwork has network: V
and for the corresponding Settlement Event it has network: E
. For your events webhooks you may want to create a lookup table to identify networks V
, I
and E
as Visa networks, for example, and networks S
, R
and O
as STAR networks.
fee_auth
codes
fee_auth
codesThese are the network codes for the fee_auth
field in the BFEE: fee
event:
Code | Network |
---|---|
A | Allpoint |
B | Pulse |
C | Discover |
D | Mastercard Maestro/Cirrus (debit) |
M | Mastercard Banknet (credit) |
O | MoneyPass |
P | Visa Plus |
R | Presto |
S | Star |
V | Visa and Visa Interlink |