{
"id": "evt_9pQ2vX7mKdR4tYb1nZ3sLwCe",
"created_at": "2026-07-28T18:41:03Z",
"type": "withdrawal.updated",
"data": {
"id": "wd_2xN6bK9mR4tQ7vC1sZ8pLwYe",
"amount_cents": 123,
"fee_cents": 123,
"currency": "MXN",
"requested_at": "2023-11-07T05:31:56Z",
"due_at": "2023-11-07T05:31:56Z",
"resolved_at": "2023-11-07T05:31:56Z",
"clave_de_rastreo": "MBAN01002608120001234567",
"test": true
},
"test": true
}A withdrawal was settled
Sent when a withdrawal stops being a request: it was paid, or it failed.
A withdrawal that is still pending announces nothing, because you
already hold that state as the create response.
This is the only way you learn the outcome. It is settled by a human hours or days later, with no request of yours in flight to answer.
{
"id": "evt_9pQ2vX7mKdR4tYb1nZ3sLwCe",
"created_at": "2026-07-28T18:41:03Z",
"type": "withdrawal.updated",
"data": {
"id": "wd_2xN6bK9mR4tQ7vC1sZ8pLwYe",
"amount_cents": 123,
"fee_cents": 123,
"currency": "MXN",
"requested_at": "2023-11-07T05:31:56Z",
"due_at": "2023-11-07T05:31:56Z",
"resolved_at": "2023-11-07T05:31:56Z",
"clave_de_rastreo": "MBAN01002608120001234567",
"test": true
},
"test": true
}Headers
Proves the event came from us. The value is t=<unix seconds>,v1=<hex>,
where the hex is an HMAC-SHA256, keyed on your signing secret, over the
string "<t>.<raw request body>".
To verify: split the header on the comma, rebuild "<t>.<body>" from
the RAW bytes you received (never a parsed and re-serialized object, or
whitespace and escape sequences will change the digest), compute the
HMAC, and compare it to v1 in constant time. Reject anything that does
not match.
Then check the clock. Reject an event whose t is more than 5 minutes
away from now in EITHER direction: a t far in the past is the replay
this scheme exists to stop, and one far in the future is the same attack
with a clock nobody checked.
Two secrets can be active at once so you can rotate without downtime: add the new one, accept either, promote it, then drop the old one. We always sign with the primary.
"t=1753728063,v1=8d2f4a1b6c7e9f0a1b2c3d4e5f60718293a4b5c6d7e8f90a1b2c3d4e5f607182"
Body
The fields every event shares. Delivery is at-least-once and unordered
by design: dedupe on id, and order by created_at or by the object's
own timestamps rather than by arrival. type and data are added by
each event, because their values depend on which event it is.
The event id, evt_ prefixed. Dedupe on this.
"evt_9pQ2vX7mKdR4tYb1nZ3sLwCe"
When the event was recorded, ISO-8601 in UTC.
"2026-07-28T18:41:03Z"
Which event this is.
withdrawal.updated A request to move money out of your balance to your bank account.
Show child attributes
Show child attributes
Present, and true, only on a test event you asked for with
POST /v1/test_webhooks. A real event does not carry the field at
all. A test event's data is a sample whose ids resolve to nothing.
true
Response
Return any 2xx to acknowledge the event.