CoinPayments

CoinPayments is a merchant crypto-payment service for businesses that need checkout, invoicing, wallets, and programmable integration in one system. It suits online sellers and developers able to use its WooCommerce/WHMCS plugins or REST API. The broad payment toolkit is appealing, but the 3% processing charges, network fees, and EU/EEA availability cutoff can materially affect the decision.

Overview

Founded in 2013, CoinPayments accepts more than 40 cryptocurrencies. Merchants can receive funds in a wallet or settle them in batches, while invoice creation can lock an exchange rate. That combination is useful when a business wants to accept volatile assets without leaving every invoice exposed to price movement.

Incoming deposits may be detected within seconds and screened for risk before blockchain confirmation. This supports prompt order handling, but detection should not be confused with final on-chain confirmation. Custodial arrangements may include insurance coverage for merchant funds. CoinPayments also describes MPC-backed signing, which avoids keeping a complete private key in one place, alongside ISO 27001 certification and AML/KYC frameworks.

Key features

Merchants can offer hosted checkout, invoice links, Buy Now buttons, white-label checkout, payment buttons, e-commerce plugins, and API-generated invoices. That range works for a simple payment page as well as a branded or fully integrated checkout.

The REST JSON API handles wallets, transactions, invoices, and signed webhooks. Official SDKs cover Python, JavaScript/Node.js/TypeScript, and PHP, giving development teams several established routes into the service. Personalized integration support is offered through a call with the Integrations team, a practical benefit for a bespoke implementation.

Official plugins support WooCommerce 6.0+ and WHMCS 9.0+. Merchants using other storefronts may need API work because additional platform support is still in development. Batch withdrawals can combine funds from multiple callback addresses into one transaction fee, with savings of up to 90% according to the homepage. The withdrawal minimum varies by coin and is generally twice the network fee, so small balances may not be economical to move.

Pricing

CoinPayments uses a paid model with three free-to-start modes, each charging 3% rather than a subscription. ASAP Mode costs nothing and adds a 3% fee plus the network fee to each individual payment. It fits merchants who need funds handled per payment, but frequent small transactions can make the combined charge significant.

Payment processing to balance also costs nothing, with a 3% fee for coins and tokens and payments deposited to the wallet. This is the straightforward choice for merchants comfortable holding balances and arranging withdrawals separately.

Nightly Mode costs nothing and applies 3% plus the network fee to the whole batch settlement. It can reduce repeated settlement overhead for businesses willing to wait for a nightly batch, while it is less suitable when immediate settlement is important. The separate settlement fee is 0.5%, and network charges remain relevant where a plan expressly includes them.

Platforms

CoinPayments provides web and API access. Its integration routes include WooCommerce and WordPress, with official WooCommerce support for version 6.0 or newer, plus WHMCS 9.0 or newer. The SDK choices make it viable for teams building on Python, JavaScript/Node.js/TypeScript, or PHP.

Who it's for

CoinPayments is a good fit for merchants that want many crypto checkout formats, exchange-rate protection on invoices, and a choice between wallet receipt and batch settlement. It is especially appropriate for WooCommerce or WHMCS stores and developers prepared to integrate REST endpoints and signed webhooks.

It is a weaker choice for EU/EEA businesses: CoinPayments says it cannot serve clients based there after 1 July 2026 because of MiCA requirements. Businesses with low-value payments should also model the 3% charge, network fees, 0.5% settlement fee, and coin-specific withdrawal minimum before committing.

Pros and cons

Pros

• More than 40 accepted cryptocurrencies give merchants broad payment coverage.
• Hosted, branded, button-based, plugin, invoice, and API checkout options accommodate different storefronts.
• Exchange-rate locking on invoices can limit volatility between billing and payment.
• Batch withdrawals can consolidate addresses and potentially reduce transaction-fee spending.
• MPC signing, stated ISO 27001 certification, and AML/KYC frameworks provide a more structured custody and compliance posture.

Cons

• All three modes carry a 3% processing charge, with network fees in the stated settlement options.
• A separate 0.5% settlement fee and coin-specific withdrawal minimums complicate cost forecasting.
• Plugin coverage is concentrated on WooCommerce and WHMCS, leaving other platforms to API integration.
• EU/EEA service ends after 1 July 2026.

Alternatives

Browse Crypto Payment Processors for a wider category comparison. Choose BitPay when broad device coverage and a free plan matter more than CoinPayments' specific settlement modes. KuCoin Pay suits consumer payments where KuCoin says it charges no fees, while merchant pricing is volume-based. Pick Plisio for a freemium wallet and gateway API structure. BTCPay Server is the alternative for self-hosting with no subscriptions or transaction fees. NOWPayments offers standard processing with blockchain network fees still payable. Apirone uses fixed service fees by cryptocurrency and transfer type. CoinRemitter provides a free tier with 0.23% per transaction and published request and address caps. Blockonomics is aimed at Bitcoin payments, with its first 10 merchant payments free before a 1% charge.

Verdict

Choose CoinPayments if your business needs multi-crypto acceptance, several checkout formats, and wallet or batch-settlement flexibility backed by developer tooling. Look elsewhere if 3% processing and settlement costs undermine your margins, your platform is outside its plugin coverage, or you operate in the EU/EEA after the stated cutoff.