Merchant deposit infrastructure
Crypto deposit address API for business payment flows
Create a reusable crypto deposit address for a merchant-side customer or account reference, receive signed transaction webhooks, and reconcile deposits in your backend.
API workflow
Create a deposit address for each customer reference
The API returns a generated address and QR-code URL for a supported asset and network. Your backend keeps the customer context and decides how each processed deposit updates its own account or order state.
B2B payment acceptance
Reconcile repeat deposits from signed webhook events
Signed webhook payloads provide the deposit address context and transaction details your backend needs. Your merchant system remains the source of truth for customer balances, accounts and orders.
Why CoinsSend
Everything you need in one gateway
CoinsSend generates the address and monitors supported-chain transactions. Your backend keeps the customer mapping and decides how each deposit updates its own payment or account state.
Create a reusable address through the merchant API
Store the address against your customer or account reference
Reconcile processed deposits with signed webhook payloads
From the blog
Practical articles
Practical guides and product updates for this payment workflow.
Keep exploring
Related payment guides
More CoinsSend workflows for crypto checkout, deposits and payment operations.
Have questions?We got answers.
Who is the deposit address API for?
It is designed for merchants and platforms that accept inbound crypto payments inside their own products. Your application keeps its customer and account records and decides how each processed deposit updates its ledger.
When should I use a deposit address instead of an invoice?
Use a reusable deposit address for repeat payments or account funding. Use an invoice when a single order needs a fixed amount, checkout state and expiration.
How are deposit events delivered?
CoinsSend sends signed webhook payloads to the address-specific callback URL when configured, or to the merchant callback URL. The payload includes address, network, asset, label and transaction details for backend reconciliation.
