Single-call payout endpoint with external_id idempotency and per-payout callbacks. Drive payroll, affiliate, treasury, or customer withdrawals from your own logic.
Payouts are enabled after business KYB. Cryptoway runs a single-call API — every request handles one recipient. Throughput is bounded by the per-IP rate limit (15 req / 15 s).
POST one payout per request — predictable behaviour at scale, no group-dispatch surprises
Idempotent by external_id
Supply your own ID per payout; retries with the same value are de-duplicated server-side
Per-payout callbacks
Each request can declare its own callback_url — status events delivered to you
~60 payouts/minute
Rate limit: 15 req / 15 s per IP. Design schedulers around this ceiling
Tier rate + network fee
Standard tier pricing (Starter 0.5% / Business 0.3%) + per-withdrawal network fee on top
Standard merchant KYB
No payouts-specific KYC step — once your merchant KYB is approved, payouts work
Developer integration
Single-call API — idempotent, callback-driven
POST a single withdrawal at a time — schedule, threshold, per-event, whatever your business logic needs. Supply external_id for safe retries and callback_url for status events. The operator owns the volume; the API owns the delivery.
Each request handles exactly one recipient. To send N payouts you make N calls. This is intentional — every payout has its own status, its own callback, its own audit trail. Plan your scheduler accordingly.
02
external_id is the merchant key
Supply your own unique identifier on each payout (UUID, order ID, payroll cycle, whatever fits). Cryptoway uses it for idempotency and you use it for reconciliation against your own ledger. Retries with the same external_id are de-duplicated.
03
Throughput is bounded by rate-limit
15 requests per 15 seconds per IP — about 60 payouts/minute on a single worker. For higher throughput, spread across multiple IPs or contact sales for high-volume contract terms.
Who uses it
Where automated payouts pay off
Payroll for contractors
Pay remote contractors in USDT on a schedule. external_id = contractor + period, callback_url updates your HR system on delivery.
Affiliate program rewards
Automated tier-based payouts on attribution events. Drive from your own attribution engine; Cryptoway delivers.
Customer / player withdrawals
Wire withdrawal requests from your product UI directly into the API. Idempotency keeps retries safe under load.
Treasury & operations
Periodic transfers between wallets, scripted from your own ops scheduler — loop the single-call API at the rate-limit ceiling.
Comparison
Cryptoway payouts vs traditional bank rails
Traditional bank payoutsCryptoway payouts API
Setup timeDays — wire arrangements, beneficiary verification per recipientMinutes — merchant KYB once, then API access
Per-payout settlementT+1 to T+3 banking daysMinutes on most networks, depends on chain confirmation
IdempotencyBank-dependent — usually missing, manual reconciliationexternal_id de-duplicates retries server-side
Status updatesPull statements end-of-dayPush callbacks per payout (callback_url)
FeeWire fee + FX spread per recipientTier rate + network fee per payout
FAQ
Automated crypto payouts via API
No. The API is single-call — POST /api/user/balance/withdrawal/ handles one recipient per request. To send N payouts, make N calls. This is by design: each payout has its own status, callback, and audit trail.
15 requests per 15 seconds per IP — roughly 60 payouts/minute on a single worker. Need more? Spread across multiple IPs or contact sales for high-volume contract terms.
Supply external_id on each payout — a unique identifier you control. Retries with the same external_id are de-duplicated server-side. Pick a value tied to your own ledger (UUID, order ID, payroll cycle) for clean reconciliation.
Minutes on most networks. The exact time depends on chain confirmation — TRC20 and Polygon typically clear in 1-3 minutes, BTC and ETH can take longer at high gas. Cryptoway does not promise instant settlement.
If a payout fails (invalid address, insufficient gas, network down), funds return to your merchant balance and your callback_url receives a failure event. Re-submit with a new external_id once the underlying issue is resolved.
Standard tier pricing applies (Starter 0.5%, Business 0.3% — see /pricing) plus a per-withdrawal network fee. There is no separate "payouts pricing" SKU.
