Webhook Event Types
HellOOpass bill/order webhook events and the action each one triggers.
Webhook contract
Event names are final. The signature header and payload fields remain illustrative until the full webhook specification is published.
HellOOpass sends four bill/order events — branch on the type field inside the signed payload.
Events
| Type | When it fires | Your action |
|---|---|---|
placed | A bill/order was created and sent to the user. | Mark it in progress — do not fulfill yet. |
confirmed | The user confirmed the bill/order. | Record the confirmation and proceed. |
rejected | The user rejected the bill/order. | Log the rejection and release any holds. |
success | The bill/order completed successfully. | Fulfill once and notify the customer. |
Example delivery
{
"id": "evt_01HZX9K2EXAMPLE",
"type": "success"
}Subscribing
SandboxConfigure subscriptions in the sandbox project and trigger test events first.
ProductionRepeat the subscription setup per project before going live.
- Subscribe separately per environment — sandbox and production are configured independently.
- Subscribe only to events your handler processes, and log unknown
typevalues instead of failing. - Events are registered per project via Webhook Configuration.
Before you act
- Read the envelope for the event id and bill/order data (Webhook Payload Structure).
- Verify the request signature before trusting the body.
- Process
successexactly once — redelivery is normal (Webhook Payload Structure).