Crypto payment gateways for WordPress and WooCommerce

Why third-party plugins are excluded#

Every provider indexed here can be bolted onto WooCommerce by some plugin somebody published. This list only counts providers that name WooCommerce among their own integrations, because a first-party plugin has a maintainer with a commercial reason to keep it working.

That is not pedantry about attribution. A payment plugin sits in the checkout path of a WordPress install, and an abandoned one is both a broken checkout waiting to happen and an unpatched entry point in the software handling your orders.

What a maintained plugin is actually worth#

It receives security updates, which is the whole argument. WooCommerce and WordPress both change, PHP versions move, and a plugin nobody updates eventually fails in one of those directions. When it fails in the payment path, you find out from customers.

It also means the provider has committed publicly to supporting a platform, which is a weak but real signal about where its attention goes. A provider that lists five maintained plugins is a different kind of company from one that lists an API and nothing else.

Many providers, and they are not interchangeable#

CoinGate maintains plugins for five platforms and publishes the most complete fee table in this index, which makes it the default recommendation for a European store that wants a defensible cost figure. Its published asset list is the narrowest of the general-purpose processors, and that is the trade.

Cryptomus and Plisio both cover WooCommerce alongside several other platforms at low published entry rates, and Plisio is additionally non-custodial, which few plugin-carrying providers are.

CoinRemitter and Apirone both charge nothing to accept and move the fee to withdrawal, which for a small WordPress store with modest volume is a genuinely different cost shape from the rest of this list.

Among the newer entries, BTCPay Server is the outlier in both directions: no fee at all, no company behind it, and a plugin shelf longer than any commercial provider on this page. Bitnovo Pay and PassimPay sit at the opposite end, publishing entry rates under one percent alongside plugins for five and eleven platforms respectively.

Plugin coverage is not integration quality#

A listed plugin tells you an integration path exists. It does not tell you whether the plugin handles partial payments, whether it writes order notes you can reconcile against, or whether it leaves orders stuck in pending when a webhook is missed.

Install it on a staging site and deliberately break things: underpay an invoice, let one expire, fire a webhook twice. What the plugin does in those three cases is the actual integration quality, and it takes an hour to find out.

Where the money goes after the sale#

Most of this list is custodial, meaning funds sit in a provider balance until you withdraw. Plisio, Apirone, BTCPay Server, GoUrl and DePay are the exceptions, routing payments to a wallet you control. For a small store that difference is often invisible until it is not, and the custody guide covers the moment it stops being invisible.

Neither shape is wrong for WordPress specifically. What matters is that a store owner who assumed a plugin meant money arrives in their bank account should check that assumption, because on most of these providers it does not without a further step.

The hosting question WordPress raises and others do not#

A self-hosted WordPress install is your responsibility to keep patched, and a payment plugin raises the cost of getting that wrong. If your site is on a host that does not apply updates, adding a payment path is a reason to fix that first rather than a reason to postpone it.

Webhook delivery deserves a check too. Plugins receive payment confirmations at a public endpoint, and some security plugins and caching layers block or cache those requests. The webhooks guide covers how to verify delivery actually works from the outside.

Setting expectations for a small store#

A plugin install plus API keys is genuinely a short job, often under an hour. The longer part is everything after: deciding what happens to underpaid orders, how refunds work when the original payment was in a volatile asset, and who reconciles the balance monthly.

The chargebacks and refunds guide covers the refund question, which surprises most merchants: crypto payments do not reverse, so refunds are new outgoing payments and cost you the network fee and the price move.

What this list leaves to you#

Whether the plugin is currently maintained, which changes month to month and which this index does not track per release. Check the last update date in the WordPress plugin directory before installing, regardless of what the provider publishes.

And whether your theme and checkout customisations survive it. A payment plugin that renders its own checkout step can conflict with a heavily customised WooCommerce flow, and that is discovered on staging rather than read off a page like this one.

Check the last update date yourself#

Whether a plugin is currently maintained changes month to month, and this index does not track it per release. The WordPress plugin directory shows the last update date on every listing.

A payment plugin last touched two years ago is a broken checkout waiting for the next WooCommerce release, whatever the provider publishes about supporting it.

Test the plugin on staging, deliberately#

Underpay an invoice, let one expire, and fire the same webhook twice. What the plugin does in those three cases is the actual integration quality.

It takes an hour and it is the difference between a plugin that reconciles and one that leaves orders stuck in pending while customers email you.