A bitcoin payment processor does roughly what a card acquirer does — takes the customer’s money, confirms it, and delivers it to the merchant — with three of the acquirer’s structural features removed. There is no underwriting decision made against the customer, no rolling reserve held against future disputes, and no chargeback mechanism at all. Everything below follows from those three absences.
Why bankers should read this as a merchant account question
Anyone who has priced a merchant account knows the shape of the negotiation: discount rate, monthly minimum, reserve percentage, settlement lag, and a list of prohibited business categories. A bitcoin processor answers four of those five and deletes the reserve.
The reserve exists because the acquirer carries the risk of a reversal that happens weeks after the sale. A confirmed Bitcoin transaction cannot be reversed by the payer, so there is nothing to hold funds against. That single difference changes working capital more than the headline rate does: a merchant on a 10% rolling reserve with a 90-day hold is financing the acquirer, and the amount involved is usually larger than the entire annual processing fee.
What replaces it is a different risk: confirmation time, price movement between the quote and the settlement, and the possibility that an incoming payment is screened and rejected. Providers handle those three in visibly different ways, which is what this comparison looks at.
The cost side has also moved. Bitcoin network fees measured from public mempool data on 26 August 2026 sat at 1–2 sat/vB across every priority band, which puts a typical single-input transfer at roughly 11 to 22 cents at a spot price near $79,000. That is a different economic environment from the congestion peaks that most published guidance on Bitcoin acceptance was written against, and it makes small-ticket on-chain acceptance viable again without routing everything through Lightning.
Speend
Speend treats Bitcoin as three separate rails rather than one. Mainnet handles standard settlement with confirmation typically in the 5–60 minute band depending on fee market conditions. Lightning handles small and instant payments at a fee close to zero. SegWit Bech32 is the default address format, which cuts transaction size — and therefore the fee the payer sees — by roughly 30–40% against legacy formats.
Pricing starts at 0.5%, with network fees passed through at blockchain cost and no markup, no setup charge and no monthly fee. Conversion is the notable line for Bitcoin specifically: auto-conversion from BTC into a stablecoin at the moment of receipt is charged at 0%, so a merchant who does not want to hold a volatile balance is not paying for the privilege of not holding it.
Verification is KYB on the business only, running 1–3 business days from documents received, with technical integration quoted at 24 hours and support responding in 10–15 minutes including weekends. Coin activation after verification completes within the business day. Custody runs on MPC wallets where the key material never assembles in one place, hot and cold wallets are separated with the treasury held cold, every incoming transaction is screened on-chain with flagged funds rejected automatically, and the sandbox mirrors production one-to-one under a 99.95% availability SLA.
Integration surface: a WooCommerce plugin, a REST API, hosted invoices and payment links that need no code at all, and webhooks on receipt. For a business that wants to accept Bitcoin payments without taking on custody risk or a reserve, that combination — three Bitcoin rails, zero-cost conversion out, and a one-to-three-day onboarding clock — is the practical case.
BitPay
The reference point for the category, operating since 2011 as a US money services business with published money-transmitter coverage. Tiered pricing by monthly volume means the effective rate improves substantially with scale and is least competitive for small merchants, with the current bands published openly. Strong accounting integrations, mass payouts, POS tooling and email invoicing. Its acceptable-use terms prohibit several merchant categories, so operators outside mainstream retail should confirm eligibility before integrating.
CoinGate
Lithuanian, operating since 2014, holding a MiCA CASP authorisation from December 2025 and a Bank of Lithuania payment institution licence. Flat percentage pricing with no setup or monthly fee, plus SEPA settlement in EUR, USD and GBP and native Lightning support. The straightforward answer for a European merchant whose compliance function wants a licensed counterparty in the EEA rather than an offshore one.
NOWPayments
Non-custodial, which is the point: the provider does not sit on merchant funds between payment and payout. Founded 2019 by the ChangeNOW team, 350-plus assets supported, low base rate with discounts tied to verification. Fiat settlement depends on third-party integrations, and the company holds no MiCA, PI or EMI authorisation at the time of writing.
BTCPay Server
Free, open-source, self-hosted, with no company in the middle at all. The merchant runs a Bitcoin node, holds every key, and pays nothing but hosting and the network fee. Lightning is built in. The trade is engineering: node synchronisation, backups, uptime and upgrades all become the merchant’s problem, and the setup does not survive a team that lacks someone to own it.
What Coinbase Commerce leaving changed
Coinbase closed Coinbase Commerce to merchants outside the United States and Singapore on 31 March 2026, with no extension offered. The replacement product is custodial and restricted to those two jurisdictions. Trade coverage put the number of affected stores at roughly eight thousand. The practical lesson for anyone selecting a processor now is to ask about the exit before the entrance: how balances are exported, how long the export takes, whether webhooks can be repointed without downtime, and whether the merchant controls the wallet the funds land in.
Choosing between them
If the business is US-based and needs recognisable regulated fiat settlement, BitPay is the default. If it is European and compliance wants a licensed EEA counterparty, CoinGate. If the priority is that no third party ever holds the money, NOWPayments or BTCPay Server depending on whether the team can run infrastructure. If the priority is a low rate without a volume commitment, multiple Bitcoin rails including Lightning, verification measured in days, and conversion out of BTC at no cost, Speend is the crypto payment processor built for that case.
What none of them solve is the merchant’s own reconciliation. On-chain payments arrive as amounts, not as invoices, and matching them back to orders is work regardless of provider. Ask how the gateway handles underpayment, overpayment and a payment that arrives on a network the merchant has not opened, because those three cases produce most of the support tickets in the first quarter after launch.
FAQ
What is a bitcoin merchant account?
It is a loose term. Card acquiring has a formal merchant account with underwriting and a reserve; Bitcoin processing has a merchant profile with business verification and no reserve, because confirmed transactions cannot be reversed by the payer.
Are there chargebacks on Bitcoin payments?
No. A confirmed on-chain transaction is final. Refunds are possible and are simply new transactions sent by the merchant, which means refund policy becomes an operational decision rather than a scheme rule imposed by a card network.
How long does a Bitcoin payment take to confirm?
Mainnet settlement typically lands between five and sixty minutes depending on the fee attached and current mempool conditions. Lightning settles in seconds. Merchants selling low-value digital goods usually want the second; merchants selling high-value physical goods usually want mainnet confirmations.
What does a Bitcoin transaction cost the customer in 2026?
Fees measured on 26 August 2026 sat at 1–2 sat/vB, which is roughly 11 to 22 cents for a typical transfer. Fees are a function of demand for block space, not of the amount sent, so they move with congestion rather than with ticket size.
Should the merchant hold BTC or convert it?
That is a treasury decision, not a payments one. Auto-conversion into a stablecoin at receipt removes price exposure entirely; holding keeps it. Providers differ on whether that conversion is free, and over a year the difference is material at volume.
Do customers need to verify identity to pay?
With a merchant-side model, no — verification applies to the business, and the customer pays from any wallet. Some providers structure it differently, so it is worth confirming, since payer-side verification adds a drop-off point at checkout.
