Wallets
Create, address, and manage merchant wallets.
What this API does
Signed requests requiredCreate wallets
Generate addresses
Inspect balances & metadata
Per-wallet webhooks
UI vs API Wallets
Often confusedCreated from the CoinPayments dashboard. Visible in the UI, but not accessible from the API.
Created via POST /merchant/wallets and scoped to the integration that created it. Only this kind is addressable from the API.
Temporary vs Permanent Addresses
Set via usePermanentAddressesAccount-based addresses that recycle back to the CoinPayments pool once their job is done or after a period of inactivity. Any residual balance is auto-credited to your account. Cheaper for short-lived attribution like a single invoice.
Addresses that never expire — funds stay put until you consolidate them. One-time activation fee on the first sweep or spend; subsequent operations are cheaper. Best for per-customer addresses.
Integration scope
Wallets are bound to the integration that created them. If you rotate integrations or work with multiple, you'll need a corresponding wallet on each — secrets are not shared. See Integration Options for the shapes this can take.
Where to next?
Pick the most useful next step.
