For the complete documentation index, see llms.txt. This page is also available as Markdown.

Webhooks

Customer Onboarding

Webhook
Description
Link

Onboarding

Dispatched when a customer has been successfully onboarded and their account is ready for use.

This is the trigger your integration should listen for before allowing a customer to initiate a funding request.

Document

Dispatched when an individual document submitted during onboarding has its status updated to VERIFIED or PENDING_RESUBMISSION. This is distinct from the Onboarding Status Webhook above: this event reports on a single document, whereas CUSTOMER_ACCOUNT_READY reports on the overall customer and account readiness once all onboarding requirements have been met.

Funding Requests

Webhook
Description
Link

Funding Request Deposit Received

The Funding Request Deposit Received webhook notifies you when an incoming deposit associated with a funding request has been successfully received and processed. This notification provides details about the deposit, funding request, beneficiary account, blockchain transaction, and conversion rate and currencies.

Payouts

Webhook
Description
Link

Payouts

The Payout notification webhook publishes status changes and payout details. These notifications allow client applications to update operational dashboards, customer portals, reconciliation systems, and audit records without continuously polling the API.

Merchant Settlements

Webhook
Description
Link

Withdrawal

Notification to inform the client of the status of requested withdrawals. Dispatched for fiat and crypto withdrawals and initiated by a POST /v1/withdrawals call.

Transfers

Dispatched when a transfer between two platform accounts is performed.

Deposits

"Completed" notification informs of the completed deposit of crypto or fiat to a customer's account. At this point account balances have been updated to reflect the deposit.

For crypto deposits, "Confirming" status informs the client that a deposit has been detected on the blockchain but the number of block confirmations has not reached the minimum threshold for the transaction to be to be considered "completed".

Last updated