Bolt provides developers the ability to leverage webhooks events to handle checkout events according to the business rules of your ecommerce store. Once configured, the Webhook endpoint will be used by Bolt to update your external server asynchronously on the occurrence of an event that you have subscribed to.
If the response to a webhook request is not HTTP 200 OK or response body is not a valid JSON, Bolt will keep retrying with exponential back-off.
Important use cases include:
| Hook Type | Description | Status |
|---|---|---|
| Pending | A transaction occurred; it is pending review. | pending |
| Payment | A sale occurred (only on auth+capture after fraud approval). | completed |
| Capture | A capture occurred (only on manual capture). | completed |
| Auth | An authorization was issued (only on manual capture after fraud approval). | authorized |
| failed_payment | A credit card authorization failed (important if an order was created during the pre-auth endpoint). | failed |
| rejected_reversible | A transaction was rejected, but the decision can be overridden. | rejected_reversible |
| rejected_irreversible | A transaction was rejected, and the decision cannot be overridden. | rejected_irreversible |
| credit | A credit/refund was issued. | refunded |
| void | A void has occurred. | canceled |
This is in Beta for custom cart implementations, ask your implementation manager about enablement. See our API reference for more information.
Important use cases include: