Skip to main content
Blockradar sends webhook notifications when a Deposit Fiat payment order is created or reaches a terminal state. Configure a webhook URL on the wallet used to create the payment order to receive these events.
See the Webhooks guide for endpoint configuration, signature verification, retries, and delivery troubleshooting.

Events

onramp.payment-order.created

Sent after Blockradar successfully creates the payment order with the selected provider. The payload contains the payment instructions your customer uses to complete the fiat transfer.

onramp.payment-order.paid

Sent when Blockradar confirms that the fiat payment was received and the payment order was settled successfully. When available, transactionId identifies the related Blockradar transaction.

onramp.payment-order.failed

Sent when the payment order cannot be completed. Fetch the payment order using its id if you need the latest provider response and failure details.

onramp.payment-order.cancelled

Sent when the payment order is cancelled before successful settlement. This can be triggered by a successful cancellation request or by a provider status update.

Payload

All payment-order webhook requests use the following envelope:
The same data shape is used for every event. Fields that are not available at the current stage can be null. In particular, transactionId, amountFiatReceived, and amountSettled might not be populated on the onramp.payment-order.created event.

Handling events

  • Return a successful 2xx response as soon as the event is accepted.
  • Use data.id as the payment-order identifier and make processing idempotent.
  • Do not assume events arrive only once or in a particular order.
  • Use event and data.status together when updating the order in your system.
  • Treat onramp.payment-order.paid as the successful terminal event.