Glossary
Webhook
A webhook is an HTTP request the platform sends to a URL the merchant configured when something happens to a payment: it was paid, declined, refunded, charged back, a payout was sent. It carries the payment's identifier, the merchant's reference, the new status and the amounts, and it is signed so the merchant can verify it came from the platform. Webhooks replace polling and the unreliable redirect; because networks fail, they are retried and may arrive more than once.
What a good webhook does
Signs the body with a key the merchant can rotate; retries on a schedule when the merchant’s server does not answer with success, for hours or days; keeps the order of events or carries enough state to make order irrelevant; lets the merchant see and resend deliveries; never contains card numbers.
What a merchant must do
Answer quickly with success and process asynchronously; verify the signature; look the payment up by its identifier rather than trusting the body alone; make processing idempotent, since the same event may come twice; and keep a fallback status call for the case where every delivery failed.
On the platform
Tranzify sends webhooks for every payment, refund, chargeback and payout change, signs them, retries them on a schedule, shows each delivery with the merchant’s response in the back office and lets the operations team resend one by hand; the same events feed the merchant cabinet.
Updated: 2026-11-08