Skip to content
ln●cash
Menu

Guide

Lightning merchant setup checklist

Everything you need in place before taking your first customer payment over Lightning.

Published May 18, 2026 · Last updated May 18, 2026 · For merchant

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.

A practical checklist for getting from “we should probably accept Bitcoin” to “we’re taking Lightning payments today.” Tick through it in order.

1. Decide on custody

  • Self-hosted (BTCPay Server) — no platform fee, you own the keys, but you (or a consultant) run the server.
  • Hosted processor — OpenNode, Speed, Strike, or IBEX. Fee on transactions, KYC, custodial relationship, fastest setup.

Pick one. See BTCPay Server vs OpenNode for the decision in depth.

2. Decide on fiat settlement

  • Auto-convert to local currency — processor settles to your bank account in local currency on a schedule. Removes Bitcoin volatility from your books.
  • Hold sats — receive in Bitcoin, decide later when (and whether) to convert. Use country-specific holding-period exemptions where they apply.

Most hosted processors offer both. BTCPay can do both, but the conversion is on you.

3. Set up the payment infrastructure

If hosted:

  • Sign up for the processor.
  • Complete KYC.
  • Get API keys.
  • Add the processor’s plugin to your ecommerce platform, or integrate via API.

If self-hosted (BTCPay):

  • Provision a small server (~$8/month on Voltage, LunaNode, or a $5 VPS).
  • Run the BTCPay install script (Docker-based).
  • Wait for the Bitcoin node to sync (hours to a day or two).
  • Set up a Lightning implementation (LND or Core Lightning).
  • Fund the Lightning node with on-chain Bitcoin for channel opens.
  • Open at least one Lightning channel (or accept inbound liquidity from a partner).
  • Configure your BTCPay store.

If self-hosting feels too heavy, a managed BTCPay host (Voltage, LunaNode) gives you 90% of the benefit with 10% of the work.

4. Choose a customer-facing flow

  • Ecommerce checkout — Lightning shown as an option at checkout alongside card. Customer’s wallet scans the QR.
  • Counter / POS — tablet or phone showing a QR. Customer scans, pays. Staff confirms green checkmark.
  • Static QR poster — Lightning Address or LNURL-pay endpoint encoded once, printed, customers scan and choose the amount.
  • Payment link — emailed to customer or shared via chat. Customer clicks, pays.

You can offer multiple. Pick the one that fits your default sale shape.

5. Test end-to-end

  • Send a $1 test payment from a Lightning wallet you control to your own checkout.
  • Verify the payment shows as confirmed in your processor dashboard or BTCPay.
  • Verify the order is marked paid in your ecommerce platform (if applicable).
  • Verify the customer-facing confirmation screen looks right.

Five minutes of testing prevents a confusing first real sale.

6. Refund policy

Lightning payments are final once settled. Decide and document:

  • Refund mechanism. Standard: customer provides a Lightning invoice for the refund amount; you pay it. Some processors automate this.
  • Refund value. Same number of sats? Same fiat-equivalent value at refund time? Decide before you have to explain it.
  • Time limit. When does a refund stop being possible?

7. Accounting and tax

  • Record receipt-time fiat value of each payment. Most processors record this automatically. For BTCPay, verify your config logs it.
  • Plan for end-of-period reporting. Most jurisdictions tax received Bitcoin as income at receipt-time value, with separate gains/losses on later disposal.
  • Talk to an accountant who has handled crypto. Generalists frequently get this wrong.

See Lightning taxes for creators and your country guide for specifics.

8. Staff training

If you have staff at the counter:

  • Train the green-checkmark rule. Customer’s “sent” is not your “received.” Wait for the terminal to confirm before handing over goods.
  • Train the fallback. If Lightning isn’t working that day (network issue, payment doesn’t route), what does the staff do? Polite handoff to card payment is the right answer.
  • Train the refund flow. Most staff won’t process refunds, but at least one person should know.

9. Marketing

Once it works:

  • “Bitcoin accepted here” sticker at the door.
  • Menu / website note — “We accept Lightning payments.”
  • Local Bitcoin maps — BTCMap, Blink’s merchant directory, local meetup directories.
  • Social — one post when you launch is enough; don’t make it your whole identity.

In Bitcoin-active cities (Prague, Lugano, Bedford UK, parts of LATAM), being on the merchant map drives real inbound traffic.

10. Backup and recovery

If self-hosted:

  • Lightning node seed phrase backed up offline.
  • Channel state backups configured (most modern Lightning implementations do this automatically).
  • Server backups — at minimum, a snapshot of your BTCPay configuration.
  • Recovery test — at least once, on a non-production server, prove you can rebuild from backup.

If hosted, the processor handles infrastructure backup. You should still:

  • Withdrawal practice — actually withdraw sats from the processor at least once before relying on it for production volume.

What this checklist doesn’t cover

Next step

FAQ

How long does the whole setup take? +

Hosted processor (OpenNode, Speed, Strike): one afternoon. Self-hosted BTCPay Server: one weekend, or one to two days with a consultant.

Do I need to register as a crypto business? +

Almost certainly not. You're a normal business that accepts payment via Lightning — same as accepting card or cash. Your payment processor (if you use a custodial one) handles its own CASP compliance. Self-hosted setups (BTCPay) keep you out of CASP scope entirely.

Can I add Lightning to an existing ecommerce store? +

Yes. BTCPay Server has plugins for WooCommerce, Shopify V2, Magento, PrestaShop, Ghost, Cal.com, Zaprite, and 25+ others. Hosted processors have similar coverage.