What is a webhook
How a server receives events and why receiving a notification requires verification.
Updated:
A webhook is a notification one service sends to another application's address when an event occurs. Cryptanio can, for example, tell a shop's server that a cryptocurrency payment state has changed. The application need not repeatedly request the same status to learn about that change.
This integration needs an accessible server-side HTTPS receiver. It differs from ready-made Telegram or Discord alerts: your server receives data and applies its own logic. Keep the verification secret on the server, outside browser code, messages and logs.
Before processing, verify the signature against the original request bytes and check the message's allowed time window. Then identify the event, locate the associated invoice and check its state. A valid signature establishes message origin but does not replace business checks of amount, asset and order.
Delivery can repeat. Store the event identifier and update the order so a repeat cannot deliver goods twice. Apply a transfer's state changes in an allowed order. If the server is temporarily unavailable, recovery should reconcile current data while preserving accepted-event history.
Use Cryptanio's pinned public API v1 contract. Receiving an HTTP request alone is not a reason to fulfil an order: a detected transaction, a confirmed transfer and a fully paid order are different conditions. Handle transaction reversals and payment exceptions.