Lightning for Business: Instant Settlement, Near-Zero Fees
The Lightning Network turns bitcoin into a practical payment rail for business: settlement in about a second, fees of a small fraction of a percent, no chargebacks, and global reach without intermediaries. Here is what it enables and how to integrate it.
Bitcoin's base layer settles transactions with final, global, trustless certainty — but in minutes, not seconds, and at a fee that varies with network demand. That is the right design for large settlements and for holding reserves. It is the wrong design for selling a coffee. The Lightning Network is the layer that fixes this, and for a business it is what makes bitcoin a practical payment rail rather than only a reserve asset.
Film · Lightning Integration · 1:36
Block ———A short film in the language of this site's homepage: the base layer for settlement and Lightning for payments; three levels of integration, described by kind and never by brand (a self-hosted, open-source payment server, a Lightning address at your own domain, and your own software on a Lightning node's API); inbound capacity and how to get it; a hosted node or your own; a working float on the node and savings in multisig, with its own risks; and the contrast between renting the card rails and running your own. It loops while on screen; use Pause to stop it. Turn on Narration to hear it explained aloud. A transcript follows.
Read the film, with its sources
- Module 3 of 4Lightning integration. Not how Lightning works inside, and not how to pay with it, but the owner’s and the developer’s view: how a business plugs Lightning into its tills, checkouts and invoices, from the simple to the advanced, and how it manages its channels.
- Two layersBitcoin’s base layer is for settlement: treasury, large transfers, savings. Lightning is the payment layer on top, for the point of sale, the online checkout, the subscription and the invoice.
- Level 1The simplest start for most businesses: an open-source payment server that you host yourself, with a Lightning node built in alongside on-chain payments. Your store offers both; the customer chooses. It needs no custom development, gives you accounting exports, and holds no one’s keys but yours: it is non-custodial. We describe the kind, not the product.
- Level 2A Lightning address is written like an email address (name@domain, at your own domain), and anyone can pay it at any time. The payer need not ask you for an invoice first: their wallet asks your domain’s server, which makes a fresh one for each payment. It suits tips, donations and informal payments, as a second way to be paid: printed on a business card, or as a tip jar on your website.LUD-16: Paying to static internet identifiers (LNURL specification)
- Level 3With developers of your own, you can build Lightning straight into your systems through a Lightning node’s API. Your software asks the node for an invoice (an amount, a description, and an expiry: one hour by default), shows it to the customer, and watches for it to be paid. When it is, the node holds the proof: in the specification’s words, the payment hash’s “Preimage of this provides proof of payment”.BOLT #11: Invoice Protocol for Lightning Payments (Lightning specification)
- Level 3That suits checkouts in online shops, subscriptions (a fresh invoice for each billing period), and software that pays out. A newer part of the specification, offers, lets a merchant publish one reusable payment request on a web page or a code, and also covers payments the other way, such as refunds. Custom work makes most sense for high volumes, subscription models, or payments inside a software product; for most small and medium businesses a self-hosted payment server does the job without it.BOLT #12: Negotiation Protocol for Lightning Payments (Lightning specification)
- ChannelsA channel’s capacity is the bitcoin locked into it, split between the two sides. You can send only what is on your side, and receive only as much as there is on the far side: that room is your inbound capacity, and liquidity is having enough of it, on each side, where you need it. When a channel opens, the specification counts the funding as “the amount the sender is putting into the channel”, so a channel you open and fund yourself starts with everything on your side: you can pay out, but not yet be paid. For a business that mostly receives, inbound capacity is the main concern.BOLT #2: Peer Protocol for Channel Management (Lightning specification)
- LiquidityThere are three common ways to get it: another node opens a channel to you; you buy inbound liquidity from a marketplace that sells it; or you spend over Lightning (paying suppliers, refunds or payouts), which moves balance to the far side of your channels. A self-hosted payment server can help with the basics; as volumes grow, it needs watching.
- The nodeSomeone has to run the Lightning node. A hosted node is run for you by a provider, which handles uptime, backups and often channels: less effort, but you trust the provider with your infrastructure, so read exactly what it controls. Your own node gives you full control, and full responsibility: it must stay online, keep backups of its channels, and watch the chain, because, in the specification’s words, once a node has funds at stake “monitoring the blockchain is required” to stop the other side closing a channel on its own terms.BOLT #5: Recommendations for On-chain Transaction Handling (Lightning specification)
- The nodeSome services go further and take the payments for you, holding them or converting them: the simplest integration of all, but then your takings are a claim on that company, not bitcoin you hold.
- TreasuryA Lightning node has to sign every payment, so its keys are online: hot. Keep only a working float there, and sweep the rest of the takings to cold storage, which on this site means multisig: three keys held by different people in different places, any two of which can spend. Multisig takes care and has risks of its own: lose the wallet descriptor, the record of how the keys fit together, and the keys alone will not recover the funds; when a key-holder leaves, the keys must be changed; and the business needs a plan for succession, so that the right people can still reach the funds. Practise a recovery with a small amount first.
- Fiat or bitcoinTake fiat currency by card, and a payment involves at least four parties besides the customer: the business itself, the card scheme, the acquirer that handles the business’s card payments, and the customer’s card issuer. The business pays its acquirer a merchant service charge, which includes fees passed on to the issuer and the scheme: it rents the rails. With Lightning, the business can run the payment server itself, and be paid straight into its own node.Payment Systems Regulator, Market review into card-acquiring services: final report (MR18/1.8, November 2021)
- The Bitcoin TransitionIn fiat, you rent the rails. On Lightning, you can run them.
We explain the technology in general terms in Lightning, Explained Without the Jargon. This article is about what it means for a business specifically. It is part of the Should Your Business Hold Bitcoin? cluster.
What Lightning Gives a Business
- Instant settlement — payments confirm in about a second, regardless of geographic distance. Faster than a card terminal.
- Near-zero fees — routing fees are typically a small fraction of a percent, against the 2–3% of card networks.
- Finality — once a Lightning payment completes, it is settled. No chargebacks, no reversals, no intermediary that can claw it back.
- Global reach — a payment from another continent is identical to one from across the counter. No foreign-exchange markup, no international wire machinery, no requirement that the customer have a bank.
- Micropayments — it is practical to charge a cent or less, which opens business models that card fees make impossible: per-article content, per-API-call billing, streaming payments.
Integration Options
There are three levels of Lightning integration, matched to three levels of need.
Level 1: BTCPay Server
The simplest path, and the right start for most businesses. BTCPay Server includes a built-in Lightning node. Deploy it, enable Lightning alongside on-chain, and your invoices and point-of-sale generate Lightning payment requests automatically. No custom development. Non-custodial — you hold the keys.
Level 2: A Lightning address or managed wallet
For businesses that want a simple receive endpoint — a tip jar, a donation link, informal payments — a Lightning address (which looks like an email address) lets anyone pay you without generating an invoice first. Services like Alby provide these. Some businesses run a managed Lightning wallet for convenience, accepting a degree of custodial trust in exchange for not running infrastructure.
Level 3: Custom API integration
For businesses with development resources and high volume — subscription products, software with embedded payments, platforms — Lightning integrates directly via APIs. LND and Core Lightning expose full programmatic control; managed providers like Voltage handle the node infrastructure so you interact only with an API. This is the path for embedding Lightning into a product rather than bolting it onto a checkout.
Liquidity, in Plain Terms
The one Lightning concept a business should understand is liquidity. A Lightning channel needs capacity on the receiving side to accept payments. For a business primarily receiving — which most are — this means ensuring your channels have enough inbound capacity for the payment volume you expect. BTCPay handles basic liquidity automatically, and for higher volumes there are marketplaces (Lightning Pool, Magma) to acquire inbound capacity. At typical small-business volumes this is a solved problem you rarely need to think about; at scale it becomes an operational consideration worth planning for.
Why It Matters Strategically
Lightning is what lets a business operate on bitcoin rather than merely hold it. A business that accepts Lightning, pays suppliers over Lightning, and settles with workers over Lightning is participating in a circular economy — value moving between parties without returning to the fiat banking system. That is the end state the whole project points toward: not bitcoin as an asset on a balance sheet, but bitcoin as the rail the business actually runs on.
It also provides resilience. A business with Lightning payment infrastructure has a payment rail that no card network, bank, or processor can switch off. For businesses in politically sensitive sectors or jurisdictions with weak rule-of-law protections, that is not a convenience — it is a continuity safeguard. The Bitcoin for Business course covers Lightning integration module by module.
Holding bitcoin makes a business resilient to monetary debasement. Running on Lightning makes it resilient to everything that can switch off a payment rail.
Written by
The Bitcoin Transition
The Bitcoin Transition is a free, non-commercial educational project. We publish from first principles, in the voice of the protocol itself: direct, technically precise, and free from fiat-denominated framing.
Related reading
Should Your Business Hold Bitcoin? The Complete Guide
Every business with reserves already holds a position in a depreciating asset: cash. This guide walks through the four decisions a business faces with bitcoin — treasury, payments, tax, and structure — and how to think about each from first principles.
How to Accept Bitcoin Payments: A Business Guide
Accepting bitcoin is simpler, cheaper, and more final than card payments. This guide covers the full setup — BTCPay Server, Lightning, point-of-sale, online checkout — and the one decision that actually matters: convert or hold.
The Lightning Network, Explained Without the Jargon
The Lightning Network is a payment network built on bitcoin. Two parties lock bitcoin into a shared channel and can then pay each other instantly, as often as they like, for tiny fees, settling on the bitcoin blockchain only when they close it. Payments route across channels, so you can pay people you have no channel with.