Cut the Middleman: Self-Hosted Bitcoin Payments with BTCPay Server

If you run a store and want to accept Bitcoin, your options usually boil down to handing a percentage of every sale to a payment processor and trusting them to hold your funds. What if you could skip the intermediary entirely—no fees, no third party sitting between you and your customers? That's the pitch behind BTCPay Server, a free and open-source, self-hosted Bitcoin payment processor that lets merchants accept Bitcoin directly.

What It Does

BTCPay Server is a payment processor you run yourself. Instead of routing transactions through a hosted service, you deploy the software and accept Bitcoin directly from your customers, without fees or intermediaries. That's the core idea, and it's spelled out plainly in the README.

The project is organized around distinct audiences, which tells you something about how it's meant to be used. There are entry points for users, operators (the people deploying and running a server), developers building integrations and plugins, and maintainers of the repository itself. Each has its own documentation path, and there's a documentation gateway that pulls the audience-specific resources together in one place.

For developers, the project exposes a Greenfield API, documented separately from the main docs. There's also a live demo on mainnet if you want to see the thing running before you commit to deploying anything. The codebase is MIT licensed, and the README keeps its project links close at hand: website, documentation, API reference, demo, issues, discussions, and a community chat.

Why It's Cool

No fees and no intermediaries is the whole point. Most payment processors charge per transaction and act as a custodian of your money along the way. BTCPay Server removes both of those things by design—you're accepting Bitcoin directly, so there's no processor taking a cut and no third party in the loop.

Self-hosting means you own the infrastructure. This isn't a hosted service with a free tier that disappears. You deploy it, you operate it, you control it. For merchants who care about that kind of independence (and plenty do), it's the main draw.

The audience-split documentation is a smart decision. Payment software sits at an awkward intersection: merchants need to use it, sysadmins need to run it, and developers need to integrate with it. Rather than cramming all of that into one README, the project routes each group to dedicated docs. That's a sign of a project that's been used by real people in all three roles.

The Greenfield API makes it a building block. If you're writing an integration, a plugin, or a custom checkout flow, the API is where you'll spend your time. Having it documented as a first-class part of the project (rather than an afterthought) is what you want from payment infrastructure.

Security is handled seriously. The README is explicit that vulnerabilities must be reported through the process in SECURITY.md, not as public issues. That's the right posture for software that handles money, and it's worth noting that the project states it clearly up front.

How to Try It

The README is a gateway rather than a tutorial, so the fastest path depends on who you are:

1. Just want to see it? Start with the demo at mainnet.demo.btcpayserver.org to get a feel for the interface before deploying anything.
2. Ready to deploy? Head to the operators documentation (docs/operators/README.md) for deployment and operation guidance.
3. Building an integration? Check the developers documentation (docs/developers/README.md) and the Greenfield API reference at docs.btcpayserver.org/API/Greenfield/v1/.
4. Merchant looking to accept payments? The users documentation (docs/users/README.md) is your starting point.
5. Want the full picture? The documentation gateway at docs/README.md links everything together.

The repository itself lives at github.com/btcpayserver/btcpayserver. If you hit a bug or have a question, issues and discussions are both linked from the README, and there's a community chat if you prefer a more conversational route.

Final Thoughts

BTCPay Server is best suited to merchants and developers who are comfortable running their own infrastructure and who specifically want to avoid payment processors—whether for cost reasons, philosophical ones, or both. If you're looking for a plug-and-play hosted solution with zero setup, this isn't that; self-hosting is the trade-off you're making for independence. But for the right audience, the value proposition is straightforward: your payments, your server, no fees, no middlemen. The MIT license and the clear separation of documentation for each audience make it easy to evaluate before you commit. Worth a look if the pitch resonates.

Follow @githubprojects for more developer tools and open source projects.