Bolt uses a transaction webhooks service to update when payment status changes occur. Within the webhook delivery system, Bolt can directly integrate into APIs set up on your module.
To leverage these webhooks, build out a receiving endpoint that maps between Bolt’s transaction statuses and your order statuses.
Register that endpoint under Administration > Developers > Webhooks in the Merchant Dashboard, not under Merchant Callbacks. One endpoint receives every event Bolt emits, so your handler must switch on both the notification type and the object it concerns. See transaction webhooks for the full list, the delivery semantics, and why a pending payment sends two notifications.
Transaction Status
| Webhook Type | Bolt Status | Definition |
|---|---|---|
| Pending | pending |
(Fraud only) Payment has been authorized / order created. |
| Failed | failed |
(Fraud only) Payment has failed. |
| Rejected Irreversible | rejected_irreversible |
(Fraud only) Payment is fully rejected for suspected fraud. |
| Rejected Reversible | rejected_reversible |
(Fraud only) Payment is conditionally rejected for suspected fraud. You may choose to manually approve. |
| Payment | completed |
Payment has been fully captured. |
| Webhook Type | Bolt Status | Description |
|---|---|---|
| Auth | authorized |
An authorization was issued. |
| Capture | completed |
A capture occurred. |
| Void | cancelled |
Transaction has been cancelled. |
| Credit | refunded |
Payment has been refunded. |
NOTE
Refunded is not a transaction status. It is a separate transaction object that shows the completed refund.