Events API (formerly known as Alerts API) is a collection of webhooks that Galileo clients can receive to be informed of system events in real time. For example, when a card authorization is approved, Galileo can send an event to you with information about the authorization, within seconds of the approval.
In addition to the information provided here, see the About the Events API guide.
Events are grouped into the following categories:
- Account Events — Account changes that do not affect the available balance*
- Authorization Events — Transactions that arrive at Galileo over network rails
- Settlement Events — Settlements that arrive at Galileo in the settlement batch file
- Transaction Events — Transactions that do not originate on network rails§
Each category is posted to a separate webhook. For example, account events are posted to /AccountEvent and transaction events are posted to /Transaction.
Events are identified by the type field in the request body. For example, when a cardholder has successfully completed the enrollment process for a card, the event type will be app_completed. Some events have further distinguishing fields; for example, for mobile tokenization events, there is a wallet_type field that identifes the wallet "vendor" (Apple, Google, Samsung, etc.).
Galileo also uses a 4-character code (msg_id) for the events in other systems like the CST. For example, CAPP corresponds to the app_completed type. You can find a list of the msg_ids with their respective types on the Event Codes page.
Each category has an index that lists each event along with its description, 4-character msg_id, event type field, and a table of the fields that are sent in the event.
Note
Galileo sends all events asynchronously so that they don't block or slow down transaction and backoffice processing. Unlike Auth API and External Trans API, the response you send to an event message does not control the outcome of a transaction.
* An exception is DSPC: dispute_pc, which notifies that provisional credit has been applied to an account for a dispute.
§ Card loads that originate over network rails have a corresponding payment transaction, indicated by BPMT: pmt.