What a Payment Webhook Is, in Plain Language
A webhook is an automatic message from a payment service to your site confirming a payment. How it works, why it's safe, and what happens if a delivery fails.

A payment webhook is an automatic message from the payment service to your site: "payment received for order number X, here are all the details." Your site receives it, acts on it, and delivers the result to the customer: opens access, changes the order status, sends a file.
Why it matters
Without webhooks your site has no way to know someone paid. You could poll your database every minute, but that's slow and adds load. A webhook works the other way: the service contacts you the instant it registers a payment. No waiting, no manual refresh.
How it looks in practice: a customer pays an invoice. The payment service sends a request to your site with the data: which order, what amount, what status. Your site checks that the data is genuine and takes the right action. The customer sees a confirmation in seconds.
Why it's safe
Every webhook is signed: it carries a digital mark that only your payment service can create. You don't need to set up the verification yourself; the service handles it. The signature cannot be forged.
What to do if a webhook doesn't arrive
A reliable service retries automatically if your site doesn't respond. The full delivery history is visible in your dashboard, and you can trigger a resend manually from there. The money is already on your balance at that point; the only question is whether your site processed the event.
For a business this means: you don't have to watch payments by hand. Your site learns about a payment on its own and handles everything automatically.



