Any best bitcoin payment plugin comparison comes down to one question: who holds the money between your customer's payment and your wallet? A plugin connected to your own BTCPay Server sends coins straight to a wallet you control. A processor plugin parks them with a third party that charges a percentage and may ask you for ID. Builder support, confirmations and refunds matter, but they come second.
TL;DR:
- Sort plugins into four types (custodial processor, self-hosted gateway, static address, manual) before comparing features, because the type fixes your custody and fee exposure.
- A flat $29 monthly cost beats a 1% processor fee once you sell more than $2,900 a month in bitcoin.
- Confirm the plugin creates a unique address per invoice, sets an expiry, and updates order status through webhooks.
- Check the plugin's last update date, tested-up-to version and open issues before installing, since checkout code that goes stale breaks quietly.
- Test an underpayment and a late payment on a real order before launch, because that is where most plugins misbehave.
Table of Contents
- Best Bitcoin Payment Plugin Comparison: The Four Types That Exist
- Custody and Fees: The Two Checks That Decide Everything
- Builder Fit: Native Plugin, API Hook or Manual Workaround
- Invoice Behavior: Addresses, Expiry, Underpayments and Late Payments
- Confirmations and Refunds: Settings You Will Actually Touch
- Maintenance Signals: How to Judge a Plugin Before You Install It
- Compliance and Exit Costs: What a Plugin Choice Locks In
- Get a Self-Custodial Bitcoin Checkout Wired Into Your Builder for $29 a Month
- Frequently Asked Questions
- Sources
Best Bitcoin Payment Plugin Comparison: The Four Types That Exist
Plugins look different on a marketplace page, but nearly all of them fall into one of four designs. The design decides who controls your funds, what you pay per sale, and what breaks when something goes wrong. If you want the full walkthrough for a shop, see How to Accept Bitcoin in Your Online Store Without a Middleman. This article covers only how to choose the plugin.
| Plugin type | Who holds funds | Typical cost model | Setup effort | Main failure mode |
|---|---|---|---|---|
| Custodial processor plugin | The processor, until payout | Percentage per sale, often around 1% | Low: paste an API key | Account freeze, KYC request, payout delays |
| Self-hosted gateway plugin (BTCPay Server) | You, in your own wallet | Hosting cost only, no per-sale cut | Medium unless the server is managed | Node falls behind or goes offline |
| Static address plugin | You | None | Low | Address reuse, no automatic order matching |
| Manual "pay and email proof" workflow | You | None | Very low | You reconcile every order by hand |
The two middle rows are the ones worth a serious look if you want bitcoin straight to your wallet. Static address plugins are fine for a donation page and poor for a store. Manual workflows work for ten orders a month and become a part-time job at fifty.
My pick is the self-hosted gateway type, specifically the plugin that talks to BTCPay Server. It is free software under the MIT license, according to its public GitHub repository, so nobody can raise its price or close your account.
Custody and Fees: The Two Checks That Decide Everything

Start with custody, because no setting can fix it later. If the plugin routes payments through someone else's wallet, you are trusting that company's solvency, its compliance team and its support queue. Read the terms for three phrases: "settlement," "payout threshold" and "right to suspend." Our guide to vetting a custodial bitcoin processor walks through seven checks if you are leaning that way.
The fee math fits on a napkin. A 1% processor cut on $10,000 of monthly sales is $100. A flat $29 hosting plan costs the same as that 1% fee at $2,900 in monthly bitcoin sales, and every dollar above that favors the flat plan.
$2,900 a month. At a 1% processor fee, that is the bitcoin sales volume where a flat $29 hosting plan costs the same.
Below that volume, a percentage fee is cheaper on paper. Set it against a cost you cannot price: a frozen balance during a payout dispute. Network fees are separate in every model. The customer's wallet pays them when sending, and you pay a small one when you later move coins.
Builder Fit: Native Plugin, API Hook or Manual Workaround
"Supports my builder" can mean three different things, and vendors use the phrase for all of them.
Native plugin
A native plugin installs inside the platform and adds bitcoin to the checkout list. WooCommerce has the most mature version of this for a self-hosted gateway. Check that the plugin shows the payment method at checkout without custom code, and that it marks orders paid or failed on its own.
Webhook or API integration
Some builders let you connect a gateway only through webhooks and a custom payment method. That works, but you own the glue. Confirm the plugin documents its webhook events (invoice created, paid, settled, expired) and that your builder can act on each one. If you plan to write your own connection, ask whether the gateway has a documented API with API keys scoped to specific permissions.
Manual or redirect workaround
Hosted builders that restrict third-party checkout code, Shopify among them, often push you toward a redirect or manual payment flow. Expect a clunkier checkout and more reconciliation. If your builder allows plugins, choose it over one that doesn't, all else equal. If it doesn't, ask the vendor how order status gets back into your admin before you commit.
Invoice Behavior: Addresses, Expiry, Underpayments and Late Payments
Plugins that look identical in a screenshot diverge here. A bitcoin payment is not a card authorization. The customer sends coins on their own schedule, from a wallet you do not control, at an exchange rate that moves.
- Unique address per invoice. The plugin should derive a fresh address for every order from your wallet's public key, so you can match payment to order and your customers' payments are not linked on-chain. A single reused address makes reconciliation guesswork.
- Rate lock and expiry. The plugin quotes a bitcoin amount and holds it for a window. BTCPay Server defaults to 15 minutes, adjustable per store. Too short and slow wallets time out. Too long and you carry price risk.
- Underpayment handling. Customers sometimes send slightly less because their wallet deducted fees. Look for a documented tolerance and a "paid partially" state, not a silent failure.
- Late payment handling. Coins can arrive after an invoice expires. A good plugin flags the order for review instead of ignoring the funds or marking it fulfilled.
- Overpayment. Decide in advance whether you refund the difference or credit it, and confirm the plugin records the excess.
Pro Tip: Before launch, place a real order and deliberately pay it 5% short, then place another and pay it after the invoice expires. Most plugin documentation only describes the happy path, and these two tests show you in ten minutes what your support inbox will look like in a month.
Confirmations and Refunds: Settings You Will Actually Touch
A confirmation is a block that includes your customer's transaction. More confirmations mean lower reversal risk and a longer wait. BTCPay Server's speed policy ranges from zero confirmations to six, and the right setting depends on what you sell.
- Digital goods or low-value items. Zero or one confirmation is usually acceptable, especially if you can revoke access later.
- Physical goods above a few hundred dollars. Wait for at least one, and consider two or three before shipping.
- Large custom orders. Use six, and ship after the invoice settles.
Refunds are the least polished area of most plugins. Bitcoin payments cannot be reversed, so a refund is a new payment you send. Check whether the plugin can generate a refund link the customer fills in with their own address. Without that, you will be asking customers for addresses over email and pasting them into a wallet by hand.
Maintenance Signals: How to Judge a Plugin Before You Install It
A checkout plugin is code that handles money, so the age of the code matters. If your builder runs on WordPress, the WordPress.org plugin directory lists a last-updated date, the highest tested version and the support forum on every plugin page. Use them as a quick filter.
- Last update. A plugin untouched for a year or more on an actively changing platform is a risk.
- Tested-up-to version. If it trails the current platform release by several versions, expect conflicts.
- Issue tracker. Skim the open issues. Unanswered payment bugs matter more than feature requests.
- Server side. The plugin is only half the system. The node or gateway behind it needs updates and must stay synced to the network. A plugin that works against a node three versions behind can fail in confusing ways.
That last point is the honest cost of the self-hosted route. The plugin is free, and the server needs a person or a service to keep it healthy.
Compliance and Exit Costs: What a Plugin Choice Locks In
Your plugin choice affects your regulatory position. The Financial Action Task Force, the global anti-money-laundering standard setter, defines virtual asset service providers as businesses that hold, transfer or exchange virtual assets for other people. A custodial processor falls under that definition and so must collect identity information. A merchant who only receives payments into their own wallet is selling goods, not running a transfer service. Local tax and licensing rules still apply, so check whether accepting bitcoin is legal where you operate.
Leaving is the other cost. With a custodial plugin, switching means rebuilding the integration and chasing any balance still held. With a self-hosted gateway, your keys and store settings export with you. If you are coming from a processor, the steps in migrating from custodial to self-custody payments without lost sales cover the order of operations.
Get a Self-Custodial Bitcoin Checkout Wired Into Your Builder for $29 a Month
The setup that follows from all this is a BTCPay Server behind a plugin, paying into a wallet you own, with someone keeping the node synced. Myntli handles that last part. For $29 a month you get a hosted BTCPay Server store on its node, with monitoring, updates and sync maintenance included, plus integration setup for WooCommerce, Shopify, Ghost, Magento, PrestaShop, Drupal Commerce, Invoice Ninja and ReplaPay. No percentage comes off your sales, Myntli never holds your funds, and your store does not go through KYC.
If you would rather own the hardware, a full node installed on your own server is $449 one time. If you do not have a self-custody wallet yet, wallet setup guidance is part of onboarding, and API access is there for custom builds. One limit: on a hosted builder that restricts third-party checkout code, the Shopify integration follows that platform's constraints, so check the checkout flow against your own spec sheet, including ours, before you commit.
Frequently Asked Questions
Which bitcoin payment plugin is best for a small store?
For most small stores, a plugin that connects to BTCPay Server is the best choice, because funds go straight to your wallet and there is no per-sale percentage. If you sell under roughly $2,900 a month and want zero setup, a custodial processor plugin can cost less in raw fees, but you accept custody and account risk.
Do I need Lightning support in a bitcoin payment plugin?
Not on day one, but it helps for small purchases because on-chain network fees can exceed the value of a $5 order. If the plugin connects to BTCPay Server, Lightning can be added later by connecting a Lightning node to the same store.
Can a bitcoin payment plugin refund a customer automatically?
Not in the card-network sense. Bitcoin payments cannot be reversed, so a refund is a new transaction you send to an address the customer provides. Look for a plugin that generates a refund link so the customer enters their own address rather than emailing it to you.
How many confirmations should I require before shipping?
One confirmation suits most physical goods under a few hundred dollars. Use two or three for higher-value orders and six for large custom work. Digital goods that you can revoke are often fine at zero or one.
Is a free bitcoin payment plugin really free?
The plugin itself usually costs nothing, but the gateway behind it needs a running, synced server. That means either your own time and hosting or a managed host. Count that cost, then compare it with the percentage a processor would take.
Sources
- BTCPay Server Documentation | BTCPay Server Project
- btcpayserver/btcpayserver (source code and license) | GitHub
- FATF Virtual Assets and Virtual Asset Service Providers | Financial Action Task Force
- WordPress Plugin Directory | WordPress.org
