Using multi-chain payments

Two ways in and one set of fund controls — the whole payment service:

• Two integration paths: the checkout (configure and send a link, no code) and an app plus API (your system creates orders and receives webhooks)
• Pick a custody model: platform custody collects into the central wallet and enables withdrawals; self-custody sends funds straight to your own addresses with no collection
• App settings: App Key and Secret, callback and redirect URLs, rotation or 1-to-1 receiving, order-creation signing and webhook signature verification
• Fund pages: address pool, assets (with collection settings and history), transactions, and the withdrawal API which only spends collected assets
• Token precision and receiving offset shape the trailing digits of the amount due — several orders on one address are told apart by those digits, so amounts must match exactly

Frequently Asked Questions

A customer paid but my system was not notified.

Check the webhook logs first. No record means the callback URL on the app is likely wrong; a failed record means your server did not respond properly. With signature verification on, confirm your logic matches the push key.

Why must customers pay the exact amount shown?

One receiving address can carry several unpaid orders at once, and the system tells them apart by the offset in the trailing decimals. A mismatched amount may not map to an order automatically.

Related pages: Help Center · Guides & FAQ · Multi-Chain Crypto Payment Gateway · Tovanix API Documentation