Hosted BTCPay Server for Merchants: Costs and Key Custody

A person sealing a cardboard box at a packing table in a small stockroom, with a closed laptop and a face-down phone nearby.

A hosted BTCPay Server for merchants is a BTCPay instance someone else runs on your behalf: you get the checkout page, the invoice API and the wallet, and you skip the server maintenance. Custody is the difference. With hosting, the node and its database are managed for you, while the private keys and the bitcoin itself stay in a wallet only you control. That is different from a custodial processor, which holds your funds until you withdraw and takes a percentage of every sale.

TL;DR:

  • A hosted BTCPay Server runs the same open-source software you could run yourself. You pay for maintenance, not for software.
  • Your keys and your funds stay in your own wallet. The host takes no custody and no percentage.
  • Budget roughly 80 GB of disk for a pruned node, or about a terabyte for an archival full node, plus a day or more for the first sync.
  • Setup time is the trade: self-hosting costs an afternoon to a weekend, managed hosting is same-day.
  • FinCEN's 2019 guidance and the EU's MiCA both stop short of treating a merchant who accepts bitcoin for goods as a regulated money transmitter.

Table of Contents

What a Hosted BTCPay Server for Merchants Actually Means

BTCPay Server is open-source payment software that runs alongside a full Bitcoin node. It creates invoices, watches the blockchain for the matching payment, and tells your shop when the money lands. No company sits in the middle of that transaction, so there is no percentage to hand over. What remains is a server that needs maintenance.

Three ways to get one running in your store:

Self-hosted. You rent a VPS, install Docker, deploy the stack, point a domain at it, get a TLS certificate, and keep the node synced. The BTCPay Server deployment documentation covers all of it. Nothing here is unreasonable for someone who already administers Linux machines. It is a poor fit for someone who does not.

Managed hosting. You pay a company to run the same open-source stack on your behalf. Your wallet keys stay yours. The host handles updates, monitoring, backups, and the sync that dies at 3 a.m.

A custodial processor. You install a plugin and never think about a server again. The trade is custody: the processor holds your bitcoin until you withdraw, takes a cut of every sale, and applies its own KYC rules to your business. Our payment processor guide covers what that custody actually costs.

Self-hosted Hosted BTCPay Custodial processor
Who runs the server You The host The processor
Who controls the keys You You The processor
Cost per transaction 0% 0% Roughly 1% of volume
Time to first invoice An afternoon to a weekend Same day Under an hour
KYC on your business None None Yes
If the operator vanishes Your problem Your keys still spend Your balance may not

The Bill Nobody Quotes You: Server Costs Across Three Years

A VPS that runs BTCPay comfortably is nothing exotic: 2 vCPU, 4 GB of RAM, and as much fast disk as you can afford. Disk is the only number that moves the price.

A pruned node needs roughly 80 GB of storage. An archival full node wants close to a terabyte, and either one takes a day or more to sync from an empty disk.

Pruning lets the node validate every new block without keeping every block back to 2009. It saves money and it works fine for ordinary invoicing. Some plugins and historical lookups want the whole chain, which is why archival nodes cost more.

At common VPS prices, a 1 TB machine runs $20 to $40 a month. Over three years that is $720 to $1,440, before you count the hours. Budget two to four hours a month for updates, monitoring, and the occasional rebuild after a failed upgrade. At a $50 hourly rate, that is $3,600 of your own time across three years, which is usually the largest line item and the one that never makes it into the spreadsheet.

Now put that next to a processor fee. A store doing $20,000 a month in bitcoin pays roughly $2,400 a year in percentage charges. That is the number to hold up against any hosting fee.

What You Keep, and What You Give Up

Accepting bitcoin into your own wallet changes your failure modes more than it changes your revenue.

You keep custody. There is no account freeze, no rolling reserve, and no 180-day hold while a risk team reviews your order history. You can read the code that generates your addresses. If the host disappears tomorrow, your wallet seed still spends every satoshi the node ever received.

You give up reversibility, and that changes how you handle mistakes.

Once a bitcoin payment confirms, there is no reversal. A customer who pays the wrong invoice, or a store that misconfigures an address, has a permanent problem that only the other party can fix.

Chargebacks are the single biggest reason merchants tolerate processor fees. Card networks can pull money back months after delivery. Bitcoin cannot, and that cuts both ways: you are protected from fraudulent chargebacks, and you are exposed to simple human error. Set a minimum order value for bitcoin, read the address back to the customer, and keep the largest orders on a rail where a mistake is recoverable.

You also give up the support phone number. A custodial processor has a desk you can call. A self-hosted node has you. A managed host sits between those two positions, which is the entire reason the category exists. For a longer look at the custody question, see what it takes to accept bitcoin directly to your wallet.

Confirmations, Lightning, and What Your Customer Actually Sees

The two payment rails create very different checkout experiences.

On-chain. The customer scans a QR code, their wallet broadcasts a transaction, and it lands in a block. Bitcoin targets one block every ten minutes, and difficulty retargets every 2,016 blocks to hold it there. One confirmation is the usual threshold for small orders. Above a few hundred dollars, waiting for two or three confirmations is a reasonable policy, which means up to 30 minutes of patience from your buyer.

Lightning. The invoice settles in under a second and the routing fee is a fraction of a cent. The catch is liquidity. Someone has to have inbound capacity for the payment to route, and if your node has no channel open in the right direction, the payment fails with an error the customer cannot interpret. A hosted setup usually has this configured already. A fresh self-hosted node does not, until you open channels and manage them.

Enable both and let the customer choose. If your average basket is $15, Lightning handles nearly all of it. If you sell $4,000 items, on-chain with confirmations is the calmer option for everyone involved.

Compliance: Who Has to Register, and Who Does Not

FinCEN's 2019 guidance on convertible virtual currency states that accepting virtual currency as payment for goods or services does not make the accepting merchant a money transmitter. You sold a product and received value for it. FinCEN treats that as the plain fact of the transaction.

The European Union's Markets in Crypto-Assets Regulation draws a similar boundary. It imposes licensing on crypto-asset service providers, which means exchanges, custodians and brokers. A shop that prices a jacket in bitcoin is not one of those. Hand that bitcoin to an exchange to convert it into euros, and you are dealing with a regulated firm that will run its own checks on you.

Tax is a separate question, and it is the one people ignore. The IRS treats virtual currency as property under Notice 2014-21. In the United States, spending bitcoin you have held at a gain is a taxable disposal, and you need a record of the fair market value at the moment of sale. Most BTCPay deployments can export that data, but you have to switch the export on before you need it.

None of this is legal advice. If your volume is meaningful, talk to an accountant who has handled crypto before, in your own jurisdiction.

Where Hosted Setups Fail, and the Maintenance Nobody Mentions

A person crouching beside a low shelf, plugging a network cable into the back of a small server.

Hosting removes sysadmin work, and it leaves every failure mode intact.

Disk exhaustion. A pruned node keeps growing, and a host that does not alert on disk pressure will go read-only at the worst possible moment. Ask any provider what their alerting threshold is.

Certificate renewal. BTCPay needs a public HTTPS endpoint so your shop can receive payment webhooks. Let's Encrypt certificates last 90 days and renew automatically on a healthy deployment. A broken renewal takes the checkout page down for every customer at once.

Webhook delivery into your shop. Your store's firewall or a security plugin can silently block callbacks from the node. The payment succeeds, the order stays pending, and the customer emails you an hour later. Test this with a $1 product before you go live.

Upgrades. BTCPay ships frequently. A major version can change plugin behavior, and a provider that pins an old release for stability is not doing you a favor if it means missing security patches.

Wallet backups. The node is not the wallet. Lose your seed phrase and the server's disk at the same time and the funds are gone. Keep the seed on paper, in two places, offline.

Pro Tip: Import an extended public key (xpub) from a hardware wallet instead of letting BTCPay generate a hot wallet. BTCPay will derive addresses and watch for incoming payments, while the keys that can actually spend sit on a device that never touches the internet. A compromised server can then annoy you, not bankrupt you. It takes about 20 minutes to configure and it is the highest-value thing you will do all year.

Three Questions That Settle Self-Hosted vs Hosted

Work through these in order and you will have your answer before the third one.

  • Do you already run Linux servers? If yes, self-hosting is cheaper across three years and you will enjoy the control. If no, the arithmetic almost always favors paying someone. Our BTCPay Server installation service comparison walks through where the hours actually go.
  • What is your monthly bitcoin volume? Below roughly $10,000, a $29 hosting fee is a smaller number than the time you would spend. Above $100,000, that fee is noise and the better question is whether you want a dedicated node for privacy and reliability.
  • Do you need Lightning? On-chain only is simple to run. Lightning adds channel management, liquidity monitoring, and a new class of "why did this payment fail" tickets. Hosts absorb most of that. Self-hosters learn it the hard way.

If you are starting from zero and want the shortest route, read how to accept bitcoin without a processor before you commit to a stack.

Get a Hosted BTCPay Server for Merchants Without the Terminal

Myntli runs the stack described above and hands you a working checkout. For $29 a month you get a BTCPay store on their node, monitored and updated, with every payment landing straight in a wallet you control. The host takes no percentage and does not custody your funds, and there is no KYC check on your store. If you would rather own the machine, they will install a full BTCPay Server node on your own server for a one-time $449. Both options include shop setup for WooCommerce, Shopify, Ghost, Magento, PrestaShop, Drupal Commerce, Invoice Ninja and ReplaPay, plus API access for custom work. Creators on membership platforms should read the Ghost membership site walkthrough before picking a tier.

One limit worth stating plainly: hosting does not take the wallet off your hands. You still generate a seed, back it up offline, and keep it. Myntli does not hold your keys and cannot recover funds for you. Before you pay, check the spec sheet, including theirs, for disk size, node type, and whether Lightning is included in the plan you chose.

Frequently Asked Questions

Is a hosted BTCPay Server custodial?

It should not be, if the host sets it up correctly. You provide or generate your own wallet, and the node's job is to watch for incoming payments and match them to invoices. The keys that can spend stay with you. Ask any provider directly which wallet model they use before you pay them.

How much does it cost to run a hosted BTCPay Server for a small store?

Managed plans generally run $20 to $50 a month depending on whether Lightning and dedicated resources are included. Self-hosting on a VPS costs roughly $10 to $40 a month in server fees, plus several hours a month of your own upkeep time.

Do I need KYC to accept bitcoin with BTCPay Server?

BTCPay itself has no account and no KYC process. FinCEN's 2019 guidance says accepting virtual currency as payment for goods and services is not money transmission. You will encounter KYC the moment you send bitcoin to an exchange to convert it into local currency.

Can I use a hosted BTCPay Server with Shopify or WooCommerce?

Yes. BTCPay has plugins for WooCommerce, Magento, PrestaShop and Drupal Commerce, and a Shopify integration that connects through an app. The node needs a public HTTPS address so the plugin can receive payment webhooks.

What happens if my hosting provider goes offline?

Your checkout page stops working, but your funds do not. Payments that already confirmed sit in your wallet, and you can restore access to that same wallet with your seed phrase on another BTCPay instance or a standard Bitcoin wallet. Keep the seed offline and separate from the server.

Pruned node or full node for a merchant store?

A pruned node validates every new block and handles invoicing without trouble, and it needs far less disk space. An archival full node keeps the entire chain, which some reporting and analytics tools use. If your only need is accepting payments, pruned is the cheaper choice.

Sources