General Information
A webhook is a callback mechanism used to receive real-time notifications about payment events. When a relevant status change occurs, the platform sends an HTTP POST request to the URL configured for that event type.
The Webhook expects your server to respond with a status code in the 2xx range. If it receives any other status code, it will retry sending the request up to 10 times until a successful response is received.
Each request includes a Signature in the header, which must be validated to prevent potential attacks. The algorithm for verifying the signature validity can be found here.
For security reasons, please make sure to verify the sender’s IP address on your server. Our IPs are: 164.90.231.203, 104.248.248.64
Webhook Types
The platform supports three categories of webhooks, each triggered by different event types:
PayIn
Order-based deposit status changes (invoice payments via transit wallets)
url_callback specified during invoice creation
PayOut
Payout and withdrawal status changes
url_callback specified during payout creation
Static Deposit
Deposit status changes on static wallets (no order required)
callback_url specified during static wallet creation
For PayIn and Payout webhooks, the callback URL is set per-operation at creation time. For Static Deposit webhooks, the callback URL is set once at wallet creation and applies to all deposits on that address. If no callback_url is configured for a static wallet, notifications are delivered via email to the project owner instead.
For detailed descriptions of statuses, event flows, and payload formats, see:
Webhooks → PayIn Webhook
Webhooks → Payout Webhook
Webhooks → Static Deposit Webhook
Last updated