Skip to main content

​
The path

​
Timing

An exchange withdrawal can take hours — that’s the exchange’s processing, not the chain. The address stays valid, so it arrives whenever it arrives.

​
What you receive

You receive the settlement token you chose, in your pool, on the chain the customer paid on.
Amounts are stored and reported in token base units. On most chains USDC, USDT, and EURC use 6 decimals, so 49000000 is 49.00.Do not hardcode 6. Token decimals vary by chain — on BNB Chain these tokens are 18-decimal. Always scale by the tokenDecimals returned with the payment.

​
Cross-token and cross-chain arrivals

The deposit rail accepts value, not one exact token on one exact chain. A customer who pays the right value in a different enabled stablecoin, or on a different enabled chain, is reconciled rather than rejected. Something you haven’t enabled surfaces as wrong_token for you to handle. Edge cases.

​
Tolerance

Quotes carry a small tolerance band, because exchange withdrawals often deduct a network fee from the amount sent. A customer who intended to send exactly right can land slightly under through no fault of their own. Inside the band, the payment settles as paid. Outside it, underpaid or overpaid.

​
Watching it

Webhooks

Push. The one to build against.

Status API

Pull. Good for reconciliation.

Dashboard

Human view, with CSV export.

​
What can go wrong

Usually the customer hasn’t sent yet, or their exchange is slow. The address stays valid indefinitely — there’s nothing to reissue.
Often an exchange fee deducted from the send. Inside tolerance it settles normally; outside it becomes underpaid. Edge cases.
Still credited, flagged as paid late. You decide whether to honour the original price.
Someone reused an old address. The money is safe, but matching it to a customer is manual — it appears in Payments without a matching order. A dedicated Unsettled view is coming.