Transaction Events Webhook

Galileo POSTs to /Transaction to send Transaction Events to the client. A Transaction Event is triggered for all other financial transactions that occur against an account, but don't go through an association (fee, payments, adjustments, etc.).

Requests

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": "ach_credit_fail",
  "account_id": "2011",
  "amount": "45.00",
  "pmt_ref_no": "155200002022",
  "prod_id": "1701",
  "prog_id": "305",
  "return_code": "R01",
  "source": "Chase Bank",
  "source_id": "6426460",
  "timestamp": "2019-10-09 11:20:33 MST"
}

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

type=ach_credit_fail&account_id=2011&amount=45&pmt_ref_no=155200002022&prod_id=1701&prog_id=305&return_code=R01&source=Chase+Bank&source_id=6426460&timestamp=2019-10-09+11%3A20%3A33+MST

Responses

ValueDescriptionRetransmit
0SuccessNo
1Parameters do not pass validation (parsing error)No
2Cardholder account not in systemNo
3General system failureNo
4Authentication failedNo
5Not ready to accept messagesYes

JSON example

{
  "success_code": "0"
}

XML responses should use the webhook name (Transaction) as the envelope.

XML example

<Transaction><success_code>0</success_code></Transaction>
Language

Galileo Financial Technologies, LLC 2024

All documentation, including but not limited to text, graphics, images, and any other content, are the exclusive property of Galileo Financial Technologies, LLC and are protected by copyright laws. These materials may not be reproduced, distributed, transmitted, displayed, or otherwise used without the prior written permission of Galileo Financial Technologies, LLC. Any unauthorized use or reproduction of these materials are expressly prohibited.