post https://example.com/Transaction
Galileo POST
s 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
)
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
)
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×tamp=2019-10-09+11%3A20%3A33+MST
Responses
Value | Description | Retransmit |
---|---|---|
0 | Success | No |
1 | Parameters do not pass validation (parsing error) | No |
2 | Cardholder account not in system | No |
3 | General system failure | No |
4 | Authentication failed | No |
5 | Not ready to accept messages | Yes |
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>