Glossary · Payments

What is Signed webhook?

A webhook is the server-to-server tap on the shoulder: when an event happens, payment seen, confirmed, completed, the platform POSTs the fact to your endpoint instead of waiting for you to ask. Polling is checking the mailbox; webhooks are the mail arriving.

The 'signed' part is what makes it infrastructure rather than a suggestion: each payload carries a cryptographic signature your server verifies before acting, because an endpoint that trusts anonymous POSTs is an endpoint anyone can lie to.

Signed webhook on U.CASH

U.CASH fires signed webhooks on every payment state change against your confirmation policy, so inventory, access, and ledgers update themselves with verified events, no polling loops.

See also

Confirmation policyCheckout embed

Signed webhook: FAQ

What if my endpoint is down when the webhook fires?
Retries with backoff are the platform's job; idempotency, keying on the event id, is yours, so a redelivered event updates once, not twice.
Why verify the signature?
Because your endpoint is public: anyone who finds it can POST a fake 'payment completed'. The signature is the difference between acting on an event and acting on a rumor.
Keep reading

The glossary, A to Z

Every term behind the rails, the assets, and the settlement.