Guide
How to accept Lightning payments
Practical setup paths for creators, merchants, and developers — without becoming a Bitcoin expert first.
Affiliate disclosure. Some links on this page are partner links. LN Cash may earn a commission if you sign up. This does not change which tools we recommend — see our methodology and the full disclosure.
There’s no single right way to accept Lightning payments. There are three reasonable paths, depending on what you’re trying to do.
This guide walks through each one and tells you which to skip.
Path 1: Creators (tips, donations, paid newsletters)
Use case: newsletter writer, podcaster, open-source maintainer, artist, indie educator. You want a public place to share that says “send me sats here,” and you don’t want to think about servers.
Recommended setup:
- Pick a Lightning wallet that ships a Lightning Address.
- Easiest path: Wallet of Satoshi — custodial, you’re done in 60 seconds. Not available to US customers since November 2023.
- Self-custodial mobile: Phoenix — slightly more setup, but you control the keys.
- Self-custodial with creator tooling: Alby — Alby Hub (self-hosted) or Alby Cloud (hosted, keys still yours, ~$10/month). Strong Nostr Wallet Connect integration.
- Copy the Lightning Address from the wallet’s “receive” screen.
- Add it to your bio, newsletter footer, Nostr profile, GitHub
funding.yml.
What to skip: you do not need a payment processor for this. Processors are for merchants taking many payments per day with accounting requirements.
One thing to plan for: wallet availability changes by region. Wallet of Satoshi has been unavailable in the US since November 2023 (a self-custodial Spark-based version is in beta as the pathway back). Whatever you choose, write down the backup phrase (if non-custodial) or note the support contact (if custodial) before you have a problem.
Path 2: Small merchants (café, market stall, pop-up, in-person sales)
Use case: physical business taking Lightning payments at a counter. Customer scans a QR, pays, you confirm, hand over the croissant.
Two reasonable setups:
Hosted processor (fastest)
- Sign up for a hosted processor: OpenNode, Speed (BTC + USDT + USDC, scaled to ~$1.5B annual volume), or Strike (US, EU since April 2024, UK).
- Generate per-transaction invoices from their dashboard, mobile app, or POS integration.
- Settle to fiat daily or weekly.
Trade-off: KYC, fee, custodial relationship.
Self-hosted BTCPay Server
- Stand up a BTCPay Server on a $5/month VPS or via a managed host like Voltage.
- Use the BTCPay POS app or pair with Zeus running in POS mode.
- Zero platform fees. You own everything.
Trade-off: you (or a consultant) need to maintain the server. Slower to start, far cheaper long term.
For most cafés the practical answer is: start hosted, switch to BTCPay once volume justifies it.
Things merchants forget:
- Refund policy. Lightning payments are final once settled. Decide in advance how you’ll handle refunds (typically: pay back in sats, after the customer provides a Lightning invoice).
- Accounting. Even if your processor settles in fiat, your local tax authority may still treat each sat received as a taxable event. Confirm locally.
- Staff training. Anyone running the till needs to know the difference between “invoice generated” and “payment received.” Verify on screen before handing over goods.
Path 3: Digital products and websites
Use case: you sell courses, downloads, SaaS subscriptions, or services online and want to add a Lightning payment option.
Recommended setup:
- Pick a processor based on your ecommerce platform:
- WooCommerce / WordPress → BTCPay Server (free plugin) or OpenNode.
- Shopify → BTCPay Server V2 plugin, OpenNode, Strike, or Speed.
- Custom site → API integration with any hosted processor.
- Ghost / Cal.com / Zaprite → BTCPay Server integrates with all three out of the box.
- Add the Lightning checkout option alongside fiat, not as a replacement.
- Decide whether to settle in fiat (removes volatility) or sats (keeps the Bitcoin exposure).
One opinionated note: if you’d otherwise need to add a percentage-fee payment processor to your stack just to support Lightning, the cost-benefit math may not work for low volumes. Start with a Lightning Address tip jar, prove demand, then add proper checkout.
Path 4: Developers (API, plugin, app integration)
Use case: you’re building a product that needs to receive Lightning payments programmatically.
Decision matrix:
| Need | Recommended |
|---|---|
| Fastest hello-world, willing to pay a fee | OpenNode REST API |
| Maximum control, willing to run infrastructure | BTCPay Server with Greenfield API (LND or CLN backend) |
| Embedded in mobile app, self-custodial | Breez SDK — Greenlight (CLN cloud node) or Nodeless (Liquid) variants |
| Embedded in web app, browser-native | Alby wallet SDK + Nostr Wallet Connect |
| Stablecoin alongside Bitcoin | Speed (BTC, USDT, USDC) |
| Enterprise volume, LATAM coverage | IBEX |
General advice:
- Test on Lightning testnet first. Real sats arrive instantly and irreversibly.
- Build payment-confirmation logic against the processor’s webhook or polling endpoint, not on the assumption that an invoice scan means payment received.
- Plan for chain reorgs (on-chain fallback) and HTLC timeouts (Lightning settlement). Both are uncommon at small amounts but real.
What this site does not do
LN Cash compares tools and explains the protocol. It does not custody funds, does not route payments, does not provide financial advice. Every recommendation here is editorial — the right choice depends on your country, volume, and risk tolerance. Always verify pricing and country availability with the provider directly before signing up.
Next step
- Pick a Lightning wallet for personal use.
- Pick a payment processor for merchant or developer use.
- Read BTCPay Server vs OpenNode for the most common decision point.
FAQ
Do I need to run a Lightning node? +
No. For most use cases — creator tips, small-merchant payments, ecommerce — you can use a wallet or hosted processor that runs the node for you. Running your own node is only necessary if you want full sovereignty, high volume, or specific routing behavior.
Do I need to verify my identity (KYC)? +
For self-custodial wallets (Phoenix, Breez, Zeus, BTCPay Server) — no. For hosted processors (OpenNode, Speed, Strike Pay) — usually yes, because they touch fiat settlement and are regulated.
Can my customers pay if they don't have a Lightning wallet yet? +
Most payment processors also accept on-chain Bitcoin as a fallback. Some hosted processors also support payments from custodial apps like Cash App or Strike, which use Lightning under the hood without exposing the user to it.