CoinPayments paused EU service. Here is a way out where a pause cannot strand you.
CoinPayments states on its own support pages that it is unable to continue serving clients based in the EU and EEA after 1 July 2026. Accounts there are paused, and remaining balances are released through support after identity verification. If that sentence describes your store, this page is the practical version of what to do next, and an argument for picking a replacement where a platform pause cannot strand your revenue, because the platform never holds it.
How EU merchants got here, from CoinPayments' own documents
Three dated events, each verifiable on their site as of August 2026. In May 2025, CoinPayments launched a new platform that operates as an independent system, and every user, including long-standing legacy merchants, had to sign up again and complete verification. In September 2025, a re-papered User Agreement spelled out the custody mechanics: received assets are held by a counterparty and, unless agreed otherwise, pooled in a multi-client omnibus wallet, with users sharing any shortfall pro rata. The same agreement discloses a dormant-account fee of 5.5 percent of all funds per twelve months of inactivity. Then, ahead of 1 July 2026, EU and EEA service was paused, with the company saying it is working to resume service and giving no confirmed timing.
None of that makes CoinPayments a bad actor. It makes it a custodial one. Every step of the story, the forced re-verification, the pooled balances, the paused withdrawals pending identity checks, is only possible because merchant revenue sits on the platform's books between payment and payout. That is the structural property to change when you migrate.
The migration, step by step
- Recover your CoinPayments balance first, through their support flow. Nothing in this migration depends on it, but do not leave funds behind while the process is fresh.
- Create a NoHoldPay account with an email address, and add the wallets you want paid: an extended public key for Bitcoin-family coins, an address per account-based chain, a view key for Monero. Funds from every future payment settle there directly, so this step replaces "add a payout address" and "schedule withdrawals" at once.
- Swap the store plugin. If you were on CoinPayments' WooCommerce integration, install the NoHoldPay WooCommerce plugin. OpenCart stores use the OpenCart extension. Custom carts point their create-payment call at the Merchant API.
- Re-point webhooks: register the plugin's webhook URL on your API key and store the signing secret. Order statuses then advance exactly as before, on signed and re-verified events.
- Dry-run on a testnet with a pk_test_ key and the test credit every account starts with, then switch the key to pk_live_.
Pricing afterward is 0.5% per confirmed payment with no fixed fee and no withdrawal step. The $50 signup credit covers roughly your first $10,000 of volume, which for most stores means the migration itself processes free.
What changes structurally when you switch
At CoinPayments, a customer pays a platform-generated address, the payment becomes a balance entry, and reaching your wallet is a withdrawal with a network fee. At NoHoldPay, the address your customer pays is derived from your own wallet material, or is a forwarder contract whose destination is fixed to your treasury in bytecode. There is no balance to pause. A jurisdiction exit like the EU pause would mean NoHoldPay stops serving new payments, and every cent from past ones would already be sitting in your wallets. The non-custodial gateway page walks through the full mechanics, including the downloadable Recovery Kit that re-derives every address without our servers.
Where CoinPayments still fits better
Honest scorekeeping: CoinPayments' new platform lists more coins than we route, its personal wallet product and balance model suit merchants who want the platform to hold a spendable float, and none of the EU situation affects merchants elsewhere. Merchants outside the EU/EEA never lost service, and some genuinely prefer a platform-held float they can spend from. Add a coin list longer than ours, and CoinPayments still does a job for them. Our claim is narrower: if July 2026 taught you that your revenue should not live on a processor's books, that lesson has an architectural answer.
Common questions
- Can NoHoldPay recover my paused CoinPayments balance?
- No. Only CoinPayments can release funds held on its platform, through its support and verification process. What a migration changes is the future: payments accepted through NoHoldPay settle to your wallets directly, so there is no platform balance to pause again.
- Is NoHoldPay licensed in the EU where CoinPayments paused?
- We do not promise a license status per country. What we can state precisely is the architecture: NoHoldPay never takes custody of customer funds, so the custody-driven obligations that reshaped custodial processors under MiCA do not attach the same way. Read our terms for the specifics of what we do and do not claim.
- How long does the switch actually take?
- For a WooCommerce or OpenCart store, usually an afternoon: create an account, add wallets, install the plugin, wire the webhook, and run one testnet order end to end. Custom integrations depend on your cart, and the API surface is one create-payment call plus one webhook consumer.
- Will my EU customers notice anything different?
- They see a hosted checkout with a QR code, wallet-connect options, and live status, and they never create an account or verify identity to pay. The coin list they can choose from follows what you enable, shown on the checkout at payment time.
Sourcing: CoinPayments' EU/EEA service pause, re-verification requirement, omnibus custody language, and dormancy fee are stated in its own FAQ and User Agreement, checked 5 August 2026. Quotes are paraphrased to their published meaning. Re-verify against their live pages before relying on them, and tell us if something changed.
Migrate this week, not this quarter
Account, wallets, plugin, webhook, testnet order. Most stores finish in an afternoon.
Start the migration