Payouts
Payouts to contractors, partners and creators are triggered from your own system. Every request is signed with your secret key, and larger batches go through a second confirmation step.
A withdrawal is signed with the X-Timestamp and X-Merchant-Signature headers: an HMAC-SHA256 of the amount, token, network and destination address. The timestamp is valid for ±30 seconds, so an intercepted request will not replay.
By default a withdrawal is created, validated and only then confirmed with a separate request. For trusted flows there is a single-step mode via skipConfirmation.
Every payout reports its status over IPN: created, confirmed, in progress, successful or error. The same channel delivers refund and service-fee statuses.
Withdrawals are only allowed to an address on the same network as the source wallet. The address is checked against the network format before funds move.
Amount, token, network and destination address. These are what you sign with your merchant secret.
The request goes to POST /merchants/{uuid}/withdraw together with the signature and timestamp.
With a separate PATCH /withdraw/{uuid}/confirm — or immediately, if you use skipConfirmation.
An IPN hits your webhook_url on every status change, through to successful completion.
The full list of assets, networks and limits lives on the supported assets page.
Questions
If your answer is not here, message support — we reply around the clock.
Create an account, fill in the project questionnaire and attach your company documents. Once reviewed, create a merchant: set your website, return URLs and the list of assets your customers will be able to pay with.
With a ready-made CMS module it takes about fifteen minutes: install the plugin and paste two keys. An API integration usually takes anywhere from a few hours to one business day.
The service fee is 1% of the incoming payment. It is deducted when funds move from the invoice’s temporary address to your merchant wallet, in the same token the buyer paid with. At higher volume the rate is negotiated individually. The network fee is charged separately.
The payable amount is calculated when the currency and network are chosen and locked until the invoice expires — the deadline arrives in the expires_at field. If the buyer misses it, the invoice is cancelled, and funds sent after cancellation are likely lost. To take the rate out of the equation entirely, invoice in stablecoins.
Where AML is enabled for the network, the transaction is scored before funds move to your merchant wallet. On a low-risk result the invoice proceeds automatically; on a high-risk one it stops at “awaiting AML decision”, where you can approve the credit or refund the sender. The report is available per invoice via the API.
We will help with the integration, match the terms to your volume, and advise which assets and networks are worth enabling at checkout.