Authorization Events Webhook

Galileo POSTs to /Authorization to send Authorization Events to the client. An Authorization Event is triggered when a card financial transaction with an association occurs. This includes card authorizations and denied card authorizations due to invalid PIN, insufficient funds, inactive card, etc.


The event data (described in the index pages that follow) will be in the body of the request, as JSON or form data.

JSON example (application/json):

  "type": "denied_auth_gas",
  "account_id": "2011",
  "amount": "10.25",
  "balance": "500.00",
  "card_id": "12534",
  "mcc": "5712",
  "merch_loc": "NEW YORK, NY",
  "merch_name": "Widgets Incorporated",
  "merch_num": "L4DIV6D5LM4X7LF",
  "network": "V",
  "pmt_ref_no": "155200002022",
  "prod_id": "1701",
  "prog_id": "305",
  "timestamp": "2019-10-09 11:20:33 MST",
  "auth_id": "12303090"

Form example (application/x-www-form-urlencoded):



JSON example:

  "success_code": "0"

XML responses should use the webhook name (Authorization) as the envelope. Example:


Response Schema


Response ("success") codes. Possible values:

  • 0 - Success
  • 1 - Parameters do not pass validation
  • 2 - Cardholder account not in system
  • 3 - General system failure
  • 4 - Authentication failed
  • 5 - Not ready to accept messages. Event will be retransmitted.

For all but 5, the event will not be retransmitted.