Quick summary: LibrePay Node is a free, open-source, self-hosted Bitcoin payment gateway released under the AGPL-3.0 license. It charges zero fees, requires no accounts and no KYC, and — because it only ever holds watch-only wallet data — it is architecturally incapable of touching your money. You fork it, run one command, paste your wallet, and you are accepting Bitcoin both on-chain and over Lightning.
If you have ever lost a sale to a frozen PayPal account, waited weeks for a payment processor's "verification" team, or discovered that Stripe simply does not operate in your country, this project deserves your attention. And because it lives on GitHub, it also deserves something from all of us: a community. This review explains what the tool actually does, how it works under the hood, how it compares with traditional payment processors — and exactly how you can support the project, with or without money.
What Is LibrePay Node?
LibrePay Node is a payment gateway you own rather than rent. Technically, it is a single process with a single SQLite database that you run on your own server — a cheap VPS, a Raspberry Pi, or a Docker container. For every invoice it derives a fresh Bitcoin address and watches the public blockchain to confirm incoming payments. The money moves directly from your customer's wallet to yours; the software itself has no spending capability whatsoever.
The most important sentence on the project's website is this: it's software, not a service. There is no LibrePay company, no dashboard they control, and no server of theirs anywhere in the loop. You fork the repository and the entire gateway runs on your box. The project cannot shut you down — there is nothing of yours to shut down. That single design decision eliminates the biggest risk in online payments: trusting a third party with your revenue.
It is worth understanding why the developers built this. Half the world is effectively locked out of getting paid online: Stripe is unavailable in most countries, PayPal freezes accounts for months without explanation, and custodial crypto processors demand the same KYC paperwork as banks — then hold your coins the way a bank would. Bitcoin solved the money part; LibrePay Node solves the plumbing. It turns a wallet you already own into a complete checkout experience, with nothing in between you and your customer.
How It Works: From GitHub Fork to First Invoice
Getting live takes three steps, and the whole flow is demonstrated in a 90-second testnet4 demo on the project's landing page. Here is what it looks like in practice.
Step 1 — Fork it and run one command
Fork the librepay-node repository so your gateway lives in your own GitHub account, then run the installer on any Linux server. The installer detects your system (Debian/Ubuntu, Fedora/RHEL, Arch, openSUSE, Alpine, or Docker) and handles dependencies, systemd and optional HTTPS automatically:
curl -fsSL https://raw.githubusercontent.com/radhwendalyhamdouni/librepay-node/main/install.sh | bash
# with automatic HTTPS for a domain:
bash install.sh --domain pay.example.com
# or fully containerized:
bash install.sh --dockerThe installer prints your node URL and a one-time setup code, and that's the entire infrastructure story: no full node to sync, no external database, no platform to trust.
Step 2 — Answer five questions in the setup wizard
Open https://your-node/setup and the built-in wizard walks you through store identity, your receiving wallet (a watch-only zpub or a BIP47 payment code — the node derives a real address as proof it can see your wallet before accepting it), your confirmation policy, and encrypted backups. Press LAUNCH NODE and your API key is issued — shown exactly once — while the setup code self-destructs.
Step 3 — Get paid
Create invoices with a single API call, the WooCommerce or Shopify integration, or the embeddable widget. The buyer gets a six-language checkout (English, Arabic with full RTL support, French, Spanish, Portuguese and Filipino); the payment lands directly in your wallet; and your webhook receives an invoice.confirmed event:
curl -X POST https://your-node.example.com/api/v1/invoices \
-H "Authorization: Bearer lp_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"amountFiat": 25.00, "currency": "USD", "orderId": "order-42"}'
# → 201 {"invoice": {"id": "…", "status": "waiting"}, "checkoutUrl": "https://…/pay/…"}
Key Features at a Glance
The feature list reads like a checklist of everything merchants complain processors won't give them. Each item below is implemented in the open source code, not promised on a roadmap:
| Feature | What it means for you |
|---|---|
| Non-custodial by architecture | Watch-only zpub or BIP47 payment code — the node sees payments but mathematically cannot spend. Funds land directly in your wallet. |
| Stealth addresses | Every invoice derives a one-time on-chain address from your payment code. Payers never learn your wallet's history. |
| Instant Lightning | Bundled phoenixd sidecar (from ACINQ) with automatic channels and liquidity — mint bolt11 invoices, zero channel management. |
| Signed webhooks | HMAC-SHA256 over the raw body, timing-safe verification, SSRF-guarded, 8 retries over roughly 24 hours with dead-letter marking. |
| Six-language checkout | English, Arabic (RTL), French, Spanish, Portuguese and Filipino — detected automatically from the buyer's browser. |
| Encrypted backups | AES-256-GCM scheduled archives, local or pushed off-server over SSH, with one-command restore. |
| Merchant console | Password + TOTP two-factor, managed sessions, step-up auth, privacy modes and Prometheus metrics. |
| Self-monitoring | A fallen chain provider can never fail silently: signed esplora_down alarms and /metrics endpoint for your monitoring stack. |
The Watch-Only Architecture: Security You Can Verify
Most "secure payment gateway" claims boil down to "trust our security team." LibrePay Node makes a different claim: the most valuable feature is what it cannot do. The node holds only a public descriptor — never a private key. It can derive addresses and detect payments, but it cannot sign, spend, or freeze anything. Even a total compromise of the host leaks invoices, never funds. There is no hot wallet to drain and no withdrawal path to forge.
The same discipline runs through the payment lifecycle. One address per invoice follows BIP84 fresh-address derivation, or BIP47 stealth addresses when privacy matters more. Confirmations are reorg-safe: a payment must stay confirmed across watcher ticks before it settles. Underpayments never settle — beyond a small tolerance, an invoice stays marked as underpaid rather than being waved through. And the node can't even call phoenixd's pay-invoice endpoint, so it can't move your Lightning balance either.
For anyone who has watched a custodial processor collapse — taking users' coins with it — this "verify, don't believe" model is not a nice-to-have. It is the entire point.
LibrePay Node vs Traditional Payment Processors
How does this compare with the tools most online businesses currently depend on? The differences are structural, not cosmetic:
| Criteria | Stripe / PayPal / Custodial Processors | LibrePay Node |
|---|---|---|
| Fees | 2–3%+ per sale plus monthly costs | $0 — watching a public blockchain costs nothing |
| KYC / paperwork | ID, business documents, approval queues | None — fork and run |
| Custody of funds | They hold your balance until they release it | Never touches funds — watch-only by design |
| Country restrictions | Long exclusion lists | None — if you can fork a repo, you can accept payments |
| Chargebacks | Possible, often at merchant's loss | Cannot exist — Bitcoin payments are final |
| Account freezes | Possible, sometimes for months | Impossible — there is no account to freeze |
| Infrastructure | Their cloud, their rules | One process + SQLite on your server (VPS, Raspberry Pi, Docker) |
To be fair: mature platforms like BTCPay Server have paved the way for self-hosted Bitcoin payments, and they remain an excellent choice for merchants who want a full-node stack. LibrePay Node deliberately takes the lighter path — one process, one SQLite file, no full-node sync, and bundled zero-ops Lightning — which makes it especially attractive for solo founders, freelancers and small shops running on modest hardware.
Who Should Use LibrePay Node?
The project describes itself as "a tool, not a platform," and that shows in how broadly it fits. Freelancers and remote workers can invoice clients in Bitcoin from anywhere on Earth — no bank account, no processor approval, no "unsupported region" email. If you earn online, our guide on how to make money with AI in 2026 pairs naturally with borderless payments like these.
Developers and solo founders get two API endpoints, signed webhooks, ready-made PHP/Node/Python snippets and an embed widget — you can ship a paid product in an afternoon. If you are just starting your programming journey, choosing between Python and JavaScript is the first step; wiring up your first payment endpoint is the second. Merchants and online stores benefit from the included WooCommerce and Shopify integrations, 0% fees and final payments — chargebacks simply stop existing.
NGOs and global causes can accept borderless donations without a banking middleman deciding which causes are allowed to receive money, while creators and communities can collect tips and paid content straight from supporter to creator with no platform taking its cut. Finally, there is the group the current system fails hardest: the World Bank counts 1.4 billion unbanked adults — most of them have a phone, and a phone is all this needs. For developers exploring the tooling landscape, our roundup of the best AI tools for programmers is a good companion read.
How to Support the LibrePay Node Project
This is the part that matters most. LibrePay Node is free software — free as in freedom, and free as in "nobody is billing you" — but open-source projects do not survive on good intentions alone. They survive on community. Here is exactly how you can help, ranked from zero-cost to full support:
1. Star the repository (takes 5 seconds)
A GitHub star is the cheapest way to make a project visible. Stars push the repository up in GitHub search and trending, which is how new users discover it. Head to github.com/radhwendalyhamdouni/librepay-node and click ★ Star.
2. Fork it, break it, report bugs
The maintainer's own words: "Code is the loudest support." Fork the project, deploy it on your VPS or Raspberry Pi, hammer it with edge cases, and open issues for anything that misbehaves. Every bug report on GitHub makes the next merchant's deployment smoother — and AGPL-3.0 means you can study, modify and self-host it without asking anyone.
3. Contribute code, docs or translations
The checkout already speaks six languages and the landing page five — additional translations, documentation improvements and pull requests are the kind of contributions that compound over time. If you have PHP, Node or Python skills, the integration snippets are a friendly entry point.
4. Donate — with the same technology it ships
There is something refreshingly honest about the project's support page: donations run on LibrePay's own BIP47 stealth-invoice engine, so every donation gets a fresh one-time address and the maintainer's wallet is never even published. Lightning fans can zap small amounts to frostynight806114@getalby.com — coffee-size thanks are explicitly welcome. Suggested tiers are 2,100 / 21,000 / 210,000 sats, and a transparency note states that donations go straight to the maintainer's own wallet with nothing custodied or routed by any platform. Contributions fund hosting for the public testnet demo, a security audit on the road to the first recommended mainnet release, and hardware for long-term signing keys.
5. Share it with one merchant who still pays 3%
The single most valuable thing you can do costs nothing: send this article — or the project page — to one person who is still paying a 2–3% cut on every sale. That is how open-source payment infrastructure actually spreads.
Frequently Asked Questions
Is LibrePay Node really 100% free?
Yes. It is AGPL-3.0 licensed with zero fees, zero subscriptions and no hidden tiers. The $0 is not a promotion — it is a consequence of the design: there is nobody billing you because there is nobody in the middle.
Can LibrePay Node steal or freeze my money?
No. The node holds only watch-only public data (a zpub or BIP47 payment code) and mathematically cannot sign or spend. Even if the server is fully compromised, the attacker gets invoices — not funds. There is no account to freeze because there is no account.
Do I need to run a full Bitcoin node?
No. The embedded chain watcher uses a configurable Esplora API (mempool.space by default) so there is no blockchain to sync. You can point it at your own Esplora or Electrum-backed instance for full independence — a fully offline node still issues invoices at the last-known rate.
Does it support the Lightning Network?
Yes. A bundled phoenixd sidecar serves instant, low-fee Lightning invoices alongside on-chain payments, with automatic channels and liquidity via the ACINQ LSP — no channel management required. Large invoices can ride the slower on-chain rail.
How is it different from BTCPay Server?
Both are self-hosted and open-source. LibrePay Node takes a deliberately lighter path: one process and one SQLite file instead of a full-node stack, a bundled zero-ops Lightning sidecar, first-class BIP47 stealth addresses, and a five-question setup wizard. BTCPay remains a great fit for full-node purists; LibrePay targets solo founders and small merchants on modest hardware.
What do I need to get started?
A Linux server (or Docker), a Bitcoin wallet you control, and five minutes. Fork the repository, run the installer, answer the wizard's five questions, and create your first invoice.
Final Verdict
LibrePay Node is one of the most interesting open-source payment projects to appear this year: genuinely non-custodial, refreshingly permissionless, and honest about its own architecture. It will not replace enterprise processors for everyone — and it does not try to. What it does is guarantee that anyone, anywhere, with a wallet and a cheap server, can get paid in Bitcoin without asking permission, paying a percentage, or trusting a company that can disappear with their balance.
If that mission resonates with you, do the five-second thing right now: star the repository on GitHub, and share this review with one merchant who is still paying 3% per sale. Open-source payment freedom only wins if the community behind it grows — and every star, fork, bug report and satoshi counts.