Network Codes

In the table below, the second row 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.

¹ The network codes for dispute-related events are in the Dispute events network codes table.
² Authorization Events
³ Settlement Events
⁴ This network-code collision occurs only in the RDFs. To distinguish between the two networks, use the SOURCE field in the Authorized Transactions RDF and SOURCE or ASSOCIATION fields in the Posted Transactions RDF.

---

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

These are the network codes for the fee_auth field in the BFEE: fee event:

Dispute events network codes

These codes are in the network field for the dispute_x events.