Payment solution

BTCPay Server: crypto payment solution

The verdict

Self-hosted acceptance platform Workable with effort Self-hosted infrastructure Suitable with operational tradeoffs

BTCPay Server is the reference self-custody answer: free, open-source software that takes Bitcoin and Lightning straight to your own wallet, in exchange for running and maintaining a server.

Who holds the funds
Merchant-controlled
Who holds the keys
Merchant
Self-hosting
Required
Lightning
Yes
Fiat settlement
No
Bank settlement
No

Best for: Technically capable or ecommerce merchants who want full self-custody, no fees, and no third party in the payment path.

Poor fit: Non-technical in-person merchants who want dollars in the bank and nothing to maintain.

Biggest tradeoff: You get complete independence and self-custody with no fees to any processor. You take on running the software: a server, a Bitcoin node, uptime, backups, and updates, plus no native fiat conversion or bank settlement.

Confidence: Medium Last reviewed 2026-07-11

What it is

BTCPay Server is free, open-source software you run yourself to accept Bitcoin and Lightning payments directly into a wallet you control. There is no company in the payment path, no processor taking a cut, and no third party holding your funds. It offers a point-of-sale app, online store plugins, invoicing, a payment button, and a full REST API.

What it is not

It is not a hosted service you simply sign up for, and it is not a way to get dollars in your bank. BTCPay does not convert crypto to fiat or settle to a bank account on its own. It is not zero-cost to operate just because the software is free: you run a server and a Bitcoin node, or you pay a third party to host it for you.

How the payment flow works

You deploy BTCPay Server (on your own server or through a third-party host), connect a wallet you control, and optionally run a Lightning node. Customers pay an on-chain or Lightning invoice, and the funds arrive directly in your wallet. Because you hold the keys, no one can freeze or withhold your money, and no one can convert it to dollars for you either.

Custody, keys, and settlement

The most important thing about any crypto payment solution is who controls the money and what happens if the provider goes away. Here is the structured answer, from primary sources.

Custody
Merchant-controlled
Key control
Merchant
Fiat settlement
No
Bank settlement
No
Settlement timing
Instant
Settles in
Cryptocurrency
Backup and recovery
Merchant

Conversion: BTCPay Server does not natively convert crypto to fiat. Some merchants pair it with a separate exchange or off-ramp; that is a separate service and a separate custody decision.

Getting your money: There is no withdrawal step: payments settle directly to the wallet you control, on-chain or over Lightning, with no provider holding funds in between.

If the provider or hosted service becomes unavailable

The self-hosted service keeps running if your infrastructure stays up.

Because BTCPay is self-hosted and non-custodial, there is no provider who can disappear with your money. Your funds are in a wallet you control, reachable with your keys and seed backup regardless of the software. If a third-party host you chose went away, you would migrate your instance, but your funds would remain yours the entire time. This is the strongest provider-independence posture of any solution we cover.

What you have to operate

A BTCPay Server instance (self-managed or via a third-party host), a Bitcoin full node, wallet key backups, and, if you use Lightning, a Lightning node with its channels and liquidity. You are responsible for uptime, security updates, and backups. This is real, ongoing operational work.

Ongoing maintenance: Substantial: server uptime, Bitcoin node, security updates, backups, and Lightning liquidity if used.

Support: Community support (docs, chat, GitHub). No commercial SLA from a vendor.

Who this is right for

A technically capable merchant, or an ecommerce seller with someone who can run software, who values full self-custody, wants to pay no processor fees, and is comfortable holding Bitcoin rather than dollars. It is the reference answer for merchants who want no third party in the payment path and are willing to run, back up, and maintain the software to get it.

Who should skip it

A non-technical in-person merchant who wants dollars deposited automatically and nothing to maintain. If you cannot run a server and a Bitcoin node, keep them updated and backed up, or pay a host to, and if you need automatic conversion to fiat and bank settlement, BTCPay by itself is not your answer. A custodial gateway will be far less work.

Our evaluation

Money and control

Who holds your money and keys, whether you get dollars, and what happens if the provider goes away.

What we evaluate Rating Why Confidence
Custody model Who holds your money between the sale and settlement, you or a third party. Excellent Fully non-custodial: funds go straight to a merchant-controlled wallet, keys never uploaded. High
Settlement Whether you get dollars, crypto, or a choice, and when. Fair Direct crypto settlement to your wallet is instant, but there is no native fiat or bank settlement. High
Fiat support Whether you can price and settle in dollars cleanly. Poor No native fiat conversion or bank settlement; pricing display aside, dollars require a separate service. Medium
Refunds Whether you can refund a payment, and how. Never inferred from an API. Good Refunds are supported via Pull Payments; specific rate options were not fully documented in retrieved pages. Medium
Security model What you are trusting and what your exposure is: keys, custody, attack surface. Good Self-custody removes third-party custody risk but makes key backup and server security your responsibility. Medium

Operations

What running this actually takes day to day, and whether it produces records your books can use.

What we evaluate Rating Why Confidence
Hosting requirements Whether you have to run a server or a node. The biggest burden divider. Poor You must run a server and a Bitcoin node yourself, or pay a third-party host; the biggest burden here. High
Ease of setup Honest effort to go live, not marketing easy. Fair A managed host lowers the barrier, but self-managed deployment is a real technical project. Medium
Accounting and records Whether it produces records your books and CPA can use. Good CSV reporting and exports exist; deeper accounting-software integrations were not documentation-confirmed. Medium
Employee workflow What your staff actually have to do, and whether multiple users are supported. Not confirmed A store user-role hierarchy was not documented in retrieved pages; only API permission scopes were. Low
Merchant support Who helps when it breaks, and how good that help is. Fair Active community support and thorough docs, but no vendor SLA; a third-party host may add support. Medium
Offline capability Whether it works when the internet or a node is down. Not confirmed No offline or no-internet acceptance mode was documented for any BTCPay app. Low

Technical capability

What the solution can actually do: Lightning, on-chain, stablecoins, and how extensible it is.

What we evaluate Rating Why Confidence
Lightning support Whether you can take Lightning, and what that requires operationally. Good First-class Lightning support, but running a node adds channel and liquidity management to your load. Medium
On-chain support Whether you can take on-chain, with what confirmation and fee reality. Excellent Full native on-chain Bitcoin acceptance directly to your wallet. High
Open source Whether you can inspect and self-host it, and whether it is actively maintained. Excellent MIT-licensed, actively maintained (v2.4.0, June 2026), large public repository. High
Operational maturity Whether this is a stable product or an early project. Good Established since 2017, actively released, widely deployed; a mature open-source project. High
Developer ecosystem Whether you can extend it if you need to. Mostly for infrastructure and API-first tools. Excellent Greenfield REST API, plugins, and an active developer community make it highly extensible. High

Cost, clarity, and privacy

What it really costs all in, how clearly that is disclosed, and what using it reveals.

What we evaluate Rating Why Confidence
Fees What it really costs, all in, and how transparent that cost is. Excellent No processor fees at all; your only costs are hosting and Bitcoin/Lightning network fees. Medium
Documentation quality Whether a merchant can actually learn to run this. Good Extensive, current documentation, though a few specific pages (roles, refund options) are thin. High
Privacy What using this reveals, and to whom: address reuse, KYC, on-chain linkage. Good Self-hosting and no KYC keep data with you, though on-chain payments remain publicly visible. Medium

We rate each area on its own. There is no overall score, because averaging areas this different, a self-hosted server's independence against a gateway's convenience, would hide the tradeoff you need to see. How we rate.

Pricing

Setup
$0 software (the software is free; deployment costs time or a host fee)
Subscription
$0 to the project (third-party hosts charge their own fee)
Transaction fee
0% to any processor (no processor takes a cut)
Conversion fee
Not applicable (no native conversion)
Network fee
Bitcoin / Lightning network fees (paid to the network, not to BTCPay)
Settlement fee
Not applicable (no provider settlement)
Hosting cost
Roughly free to about $70/month (self-managed VPS or a third-party host; varies widely)

BTCPay Server is free and open-source. The real cost is operational: hosting and your time, or a third-party hosting fee. Confirm current host pricing before you rely on it. Last verified 2026-07-11.

Limitations

  • No native conversion to fiat and no bank settlement; dollars require a separate service.
  • Running a server and a Bitcoin node is a real operational burden, not a one-time setup.
  • Lightning adds channel and liquidity management on top of node uptime.
  • Offline acceptance behavior is not documented; treat it as unconfirmed.
  • Support is community-based; there is no vendor SLA unless a third-party host provides one.

What we are still verifying

We publish what our documentation review supports and mark the rest as unverified. These questions are open. We will answer them with hands-on testing before we treat them as fact.

Open questionCurrent confidence
How much real effort is a self-managed deployment versus a third-party host? Low
What are the exact refund rate options (current rate, rate-at-invoice, custom, fiat)? Low
Does BTCPay have a store user-role hierarchy for employees? Low
Can the point-of-sale app take a payment offline or in low connectivity? Low
How clean are the accounting exports for a CPA and reconciliation? Low

How much real effort is a self-managed deployment versus a third-party host?

Why it matters: Setup effort is the single biggest factor in whether a merchant can actually adopt BTCPay, and it varies enormously.

Planned lab validation: Deploy BTCPay both self-managed and via a third-party host, and document real setup time and steps.

What are the exact refund rate options (current rate, rate-at-invoice, custom, fiat)?

Why it matters: Refund behavior is a top merchant concern and the retrieved refund page did not document the specific rate options.

Planned lab validation: Issue refunds via Pull Payments and document each available rate option.

Does BTCPay have a store user-role hierarchy for employees?

Why it matters: Multi-user and employee permissions matter for any business with staff; only API permission scopes were documented.

Planned lab validation: Add store collaborators in a live instance and document the available roles and permissions.

Can the point-of-sale app take a payment offline or in low connectivity?

Why it matters: Offline behavior determines fitness for markets and food trucks with poor internet; it was not documented.

Planned lab validation: Run the POS app in a degraded-connectivity setting and observe behavior.

How clean are the accounting exports for a CPA and reconciliation?

Why it matters: Determines the real bookkeeping burden and how it bridges to the Accounting Toolkit.

Planned lab validation: Export reporting data and evaluate whether it reconciles cleanly and imports into common accounting tools.

CryptoLic Lab

CryptoLic does not stop at reading documentation. We independently validate what vendors claim by setting things up and running them ourselves, then we publish what we actually observed. For this solution, that hands-on validation is in progress. Nothing below is marked verified until we have tested it, so you can trust a "verified" label when you eventually see one.

What we will verifyStatus
Self-hosting setup effort (self-managed vs third-party host) Pending verification
On-chain acceptance end to end Pending verification
Lightning acceptance and node operations Pending verification
Refund via Pull Payments and rate options Pending verification
Store user roles and permissions Pending verification
Accounting export quality Pending verification
Offline / low-connectivity POS behavior Pending verification
Backup and recovery workflow Pending verification
Holding your own keys?

If you control the keys, you own the security. The The Merchant Security Playbook covers backups, recovery, and keeping funds safe.

Keeping the books straight?

Whichever solution you choose, the crypto has to reconcile against your books. The The Merchant Accounting & Bookkeeping Toolkit gives you a routine and a clean year-end package for your CPA.

Sources and verification

Last content review 2026-07-11 Documentation verified

Custody
2026-07-11
Settlement
2026-07-11
Pricing
2026-07-11
Availability
2026-07-11
Kyc
2026-07-11
Supported assets
2026-07-11
Integrations
2026-07-11
Refunds
2026-07-11
Open source
2026-07-11
Content reviewed
2026-07-11
Editorial update
2026-07-11

How we verify and date facts.

Change log

  1. 2026-07-11 Initial publication. Documentation review complete; hands-on lab validation in progress.

Spotted something out of date? Send a correction. We verify every submission against primary sources; vendor contact never changes a rating.

Questions

Is BTCPay Server really free?

The software is free and open-source (MIT license), and it charges no processor fees. But running it is not free: you pay for a server and your own time to maintain it, or you pay a third-party host. Budget for real operating cost even though the software costs nothing.

Do I hold my own money with BTCPay?

Yes. BTCPay is non-custodial: payments go straight to a wallet you control, and in the recommended setup your keys are never uploaded to the server. No third party holds or can freeze your funds.

Can BTCPay deposit dollars in my bank?

Not on its own. BTCPay does not convert crypto to fiat or settle to a bank. If you need dollars, you pair it with a separate exchange or off-ramp, which is its own service and its own custody decision. Many merchants who choose BTCPay are choosing to hold Bitcoin.

Do I have to run a server myself?

You run it yourself or you use a third-party host. Self-managing gives you the most control and requires the most work: a server, a Bitcoin node, updates, and backups. A third-party host trades some of that independence for convenience and a fee.

Does BTCPay support Lightning?

Yes, Lightning is first-class. Be aware that running Lightning means managing a node, channels, and liquidity, which is additional operational work on top of the base server. We will document the real burden when our lab testing is complete.

How this compares

Every solution we cover is evaluated the same way. Here is where the others land.

SolutionCategoryReadinessThe short version
OpenNode Custodial gateway R4 Merchant-ready OpenNode is a finished, hosted Bitcoin and Lightning gateway that can auto-convert to dollars and settle to a US bank, in exchange for the provider holding your funds and gating bank payout behind approval.
Strike Lightning infrastructure or provider R2 Early or narrow Strike is a powerful custodial Lightning and fiat rail, but for merchants it is mostly an API plus a consumer app, and bank payout is gated behind partner onboarding, so it is not yet a turnkey way to accept payments.

Using this beside your POS

This solution runs beside your point-of-sale system, not inside it. See how crypto acceptance works with the registers we have reviewed:

What "beside the register" (parallel acceptance) means.

Related reading

Not sure this is the right one?

Compare it against the others in the Payment Solutions Decision Center, or start from what you actually need.

Learn the fundamentals

New to accepting crypto?

Learn

How to choose a crypto payment solution

A short decision path through the real choices: custody, settlement, rail, and support. How to narrow the field to the one that fits your business.

Learn

Custody explained: who holds your crypto, and why it matters

The difference between holding your own keys and letting a processor hold them is the most important choice you will make. Here it is in plain terms.

Learn

Pricing in dollars and converting crypto payments

You keep pricing in dollars. The tool handles the crypto. Here is how quotes, conversion, and settlement actually work at the moment of sale.
Something went wrong. Please try again in a moment. If the problem continues, contact us.
Thanks! Check your inbox to confirm your subscription.

Join the CryptoLic Insider

Practical cryptocurrency payment guidance for small businesses. Get occasional security tips, implementation guides, product updates, and launch announcements. No spam