API · Webhooks
API v1Recurrence#
Six fields configured when creating or editing a plan. All optional.
| Field | What it is |
|---|---|
webhook_subscribe | Subscription webhook |
webhook_payment | Charge webhook |
webhook_rejected | Rejected charge webhook |
webhook_unsubscribe | Unsubscribe webhook |
webhook_reactive | Reactivation webhook |
thanks_url | Not a webhook: it is a GET callback |
Payment links#
webhook_url is configured when creating the link.
Retries#
| Source | Attempts | When it retries |
|---|---|---|
| Recurrence | 5 | When your response is 400, 404, 502, 504 or 403 |
| Purchases | 1 | — |
Delivery is considered successful on an HTTP 200. Respond 200 as soon as you receive the event and process it separately: anything else counts as a failure, and purchases have no second attempt.
Format#
JSON.
The card token#
| Source | Token |
|---|---|
| Recurrence | Not sent |
| Purchases | Sent and usable |
Origin verification#
The only origin verification available is the orderHash, and its algorithm is not public:
it is delivered to merchants who request it by writing to sac@tilopay.com.
Until you have the algorithm, do not take irreversible business decisions from webhook content alone: confirm the state against the API before shipping or releasing a service.
Main flow webhook#
processPayment also has a webhook. Its contract is delivered to merchants who request it:
write to sac@tilopay.com to receive it.
Last verified: 2026-08-28 · Owner: equipo-integraciones