A crypto payment gateway for forex brokers and trading firms

1. 01The client asks to fund their account. Your backend calls POST /v1/invoices with the amount, the network and asset, and your own referenceId — the client or deposit ID in your system.
2. 02Payaries returns a one-time deposit address and locks the rate. You show the address and the network to the client.
3. 03The invoice moves pending → detected → confirming → confirmed.
4. 04A signed invoice.status_changed webhook fires on every change. You verify the signature, dedupe on the idempotency key and credit the account — see verifying webhook signatures.
5. 05Funds are swept to your own wallet on that network, and you withdraw when you need to.

Because every deposit has its own address and reference, there's no shared deposit wallet to reconcile by memo or by amount.

A dollar stablecoin lets a client fund a dollar-denominated account without a price swing between sending and crediting. Payaries supports USDT on Ethereum, BNB Smart Chain, Polygon, Arbitrum and Tron, and USDC on Ethereum, BNB Smart Chain, Polygon and Arbitrum — the full table is here.

• Underpayments are flagged underpaid with the shortfall shown, so you can ask for the balance or refund.
• Late payments (mined after the deadline) are held for review, then refunded or settled; a settled one moves the invoice out of expired with latePayment: true in the webhook.
• Money that fits no invoice is recorded as an unclaimed deposit instead of being dropped.
• Wrong network: the deposit address is valid on one network only, so show the network beside it. See how to handle underpaid and late payments.

Withdrawals go to any address on demand — from the dashboard with two-factor authentication, or from the API. API-created withdrawals run immediately below an auto-approve threshold you set and wait for your own approval above it. Bitcoin withdrawals are not supported yet.