Events Catalog

Each event is named <operation>_<status> and travels in the payload's event_type field. The groups below match the endpoint form in Developers › Webhooks, and each group has a fixed payload format. Which groups apply to you depends on how you integrated Tonder; the format is not chosen per endpoint. The conceptual model is in the Webhooks model.

Formats

Payments — API Direct (Short)

API Direct payments and refunds. Hosted Checkout 2.0 processes payments through the Direct API, so a payment made on the hosted page sends these events too.

A payment goes through only the states its method and flow use, so subscribe to the ones your integration acts on. On SPEI Success, the payload adds sender info: sender_name, sender_clabe, sender_bank, among others. Argentina's QR and bank-transfer payments use these same events; their payer fields are listed in Argentina.

A payment_Success event:

{
  "id": "bf370a48-ffcf-4fbe-bab9-ecb791b0b684",
  "event_type": "payment_Success",
  "operation_type": "payment",
  "status": "Success",
  "amount": "500.00",
  "currency": "MXN",
  "country": "MX",
  "client_reference": "ORD-001",
  "transaction_id": "1464",
  "payment_method_type": "card",
  "decline_code": null,
  "decline_reason": null,
  "created": "2026-10-20T18:52:10Z",
  "metadata": { "external_id": "ORD-001" },
  "action": "MODIFY"
}

• id is the transaction id the API returned when you created the payment (/process/); use it to match the webhook to your order.
• client_reference and metadata are the values you sent when creating the transaction.
• Payloads can also carry fields that identify the institution that processed the transaction. Don't build logic on them.

Checkout sessions — Hosted & SDK (Long)

Events from earlier integrations — SDK 1.0, the previous Hosted Checkout flow and the withdrawals API v1/v2. The legacy_ prefix identifies them, and the payloads are in Legacy webhooks.

Withdrawals (Long)

withdrawal_Canceled is spelled with one L, unlike payment_Cancelled and refund_Cancelled. Match the event names exactly. Without Webhooks 2.0, withdrawals emit five events and none for a cancellation.

A withdrawal sends the pending event and then its terminal one; withdrawal_Returned comes on top, when the receiving bank returns the funds after Success. The payload comes in one of two formats, set by your account's configuration: a flat payload with the same shape as the Short payment format (status: Pending, transfer_method_type instead of payment_method_type), or an extended payload that nests the full withdrawal record under withdrawal{} with the status in the internal names (PAID_FULL). Both, with examples, in Withdrawals.

Other

The catalog through the API

GET /v1/event-types returns the catalog with each event's description, plus the retry policy — see Webhooks API.

Next steps