Webhooks
PLANNEDRoute and settlement events.
Webhooks ship with transactions in the production build. The event catalog and delivery guarantees below are the design, published for review — not yet live.
Planned event catalog
| Event | Fires when |
|---|---|
| route.selected | HQ locks a route for a transaction (with TTL). |
| intake.confirmed | The origin door confirms value has entered. |
| route.rerouted | A leg degraded and an alternative route was selected under the same id. |
| settlement.completed | Value delivered to the destination; receipt attached. |
| settlement.failed | No viable route remained; transaction parked with reason. |
Delivery guarantees (design)
Signed payloads (HMAC over the raw body with a per-endpoint secret), at-least-once delivery with exponential backoff, and an idempotency key on every event so replays are safe. The runtime already models door webhooks internally with the same idempotent discipline.
Conceptual payload
{
"id": "evt_…",
"type": "settlement.completed",
"created": "2026-09-29T14:02:11Z",
"data": {
"transaction_id": "pay_…",
"route_id": "rt_…",
"destination": { "asset": "USDC", "network": "solana" },
"receipt": { "ref": "ldi_…", "amount_usd": 1000 }
}
}