Wallet Consolidation
Move funds out of permanent addresses, three ways.
Three approaches
Dashboard · API · API- WhereDashboard → Wallets → expand the target currency.
- TriggerA balance threshold you set per wallet.
- DestinationAn address you specify — typically a cold or treasury wallet.
- Best forTreasury automation — sweeping accumulated funds without writing code.
- EndpointPOST /merchant/wallets/:id/spend-request
- ControlCoinPayments picks the address combination that minimises fees and activation costs.
- Best forYou want the funds out; you don't care which permanent addresses get touched.
- Single walletPOST /merchant/wallets/:id/consolidation/:to
- Multi-walletPOST /merchant/wallets/consolidation/:id
- PreviewPOST /merchant/wallets/consolidation/preview
- Best forYou need to preserve specific addresses, or move funds between same-currency wallets you choose.
Convert as you consolidate
Consolidation can double as a currency conversion — the swept funds can land in a different asset as part of the same atomic operation. Handy when you want incoming coin to settle directly as a stablecoin, with no separate spend request to swap afterwards.
Fees
Per address, per consolidationCharged once per permanent address, the first time it's consolidated. Initialises the address so subsequent operations are cheaper.
Charged per address on every consolidation transaction — the on-chain cost of moving the funds.
Consolidation must target a temporary-address wallet
When you trigger a consolidation, the :to destination wallet must be one configured with temporary addresses. Consolidating into another permanent-address wallet is not supported — the sweep needs a wallet-level balance to land in.
Sequential processing
Spend requests against a permanent-address wallet must be processed one at a time. Confirm and finalize the current request before submitting a new one — the automatic consolidation step required for each send will reject concurrent attempts.
Where to next?
Pick the most useful next step.
