Lightning Network in November 2025 processed $1.17 billion in monthly volume. The network has 18,000 active nodes, 5,400 BTC of total capacity, and 12 million monthly transactions. Public Lightning volume grew 266 percent year-over-year. By the end of 2026, Lightning is on track to handle 30 percent of all Bitcoin transfers for payments and remittances.
These are real numbers. Lightning is no longer the speculative scaling layer that crypto-twitter argued about in 2018. It is a working payment rail with measurable adoption. Here is the 2026 reality check on Lightning for merchants, what it is good at, where it falls short, and whether it should be in your checkout stack.
The adoption curve finally bent
For most of Lightning's existence, the merchant adoption number was a rounding error. Most Bitcoin payments settled on the base layer. Lightning was for tipping, micropayments, and crypto-native experiments.
That changed materially in 2024 and 2025. CoinLaw's 2026 Lightning Network statistics report: "The Lightning Network processes over 12 million transactions monthly across 18,000+ active nodes, with total network capacity exceeding 5,400 BTC. The Bitcoin Lightning Network has crossed a significant milestone in 2025, surpassing $1 billion in monthly transaction volume, with monthly volume exceeding $1.17 billion in November 2025."
The driver is integrations. Block (formerly Square) is rolling Bitcoin via Lightning to its full merchant base of roughly 4 million US POS hardware customers, "with full availability expected by 2026." That single rollout 5x's the merchant-side acceptance footprint of Lightning in the US.
Strike, CashApp, Kraken, Bitget, and Coinbase have integrated Lightning deposits and withdrawals. Strike and CashApp facilitate merchant adoption across 85 countries. The infrastructure exists. The user-side wallets work. The merchant-side hardware is shipping.
What Lightning is good at
Micropayments. A 50-cent transaction on Bitcoin mainnet costs $0.50 to $3 in fees. The same transaction on Lightning costs fractions of a penny. For any business model that depends on small-ticket sales (in-game purchases, streaming subscriptions, pay-per-article, tipping), Lightning is the only Bitcoin rail that makes economic sense.
Same-second settlement. Lightning transactions are routed through payment channels and settle in seconds, not 10 minutes (Bitcoin mainnet 1 confirmation) or 60 minutes (6 confirmations for finality). The customer pays, the merchant sees the payment land before the customer has put their phone away.
Cross-border without correspondent banks. Bitnob facilitates Lightning-based salary payments for remote workers across 23 African countries with transaction volumes growing 340 percent year-over-year. The lack of correspondent banking infrastructure in many African countries makes Lightning a structurally better rail than SWIFT for that geography.
El Salvador-style government adoption. Chivo, El Salvador's government-backed wallet, processed 4.2 million Lightning transactions in 2025, primarily for remittances and retail purchases. The wallet is mandated as legal tender. The volume is real.
Where Lightning still falls short for merchants
Liquidity management overhead. Running a Lightning node as a merchant means thinking about inbound and outbound channel liquidity. If your channels are imbalanced, you cannot receive (or cannot send change) until you rebalance. This is a real operational task that SaaS gateways abstract away but pure self-host does not.
Not stablecoin-denominated. Lightning settles in Bitcoin. The merchant's revenue is denominated in BTC unless they immediately swap to stable. For merchants who price in USD and want to receive USD, the swap step adds latency, slippage, and complexity. Stablecoin rails on Solana, Base, and Tron skip this entirely.
Limited beyond Bitcoin. Lightning is a Bitcoin protocol. It does not transport USDC, USDT, or ETH-denominated value. If your customers want to pay in stables (and most do, per industry data), Lightning is not the rail.
Mobile-first by design. Lightning works beautifully on phones. It works less well in card-terminal contexts where the customer expects a tap or chip transaction. Merchant adoption beyond mobile point-of-sale is still early.
Should it be in your checkout?
Three signals to add Lightning to your stack:
- 1.Your customers are crypto-native AND prefer BTC. A non-trivial share of Bitcoin holders prefer to spend BTC directly rather than swap to stables first. If you serve that segment, Lightning is the cheap rail to settle their preference.
- 1.Your average ticket is under $20. Sub-$20 transactions have terrible unit economics on cards (the $0.30 flat fee is a 1.5 percent rate alone) and on Bitcoin mainnet (gas eats the margin). Lightning is the only rail where small-ticket crypto works.
- 1.You sell to remittance or cross-border use cases. Africa, Latin America, and Southeast Asia have meaningful Lightning footprints. If your customer base lives there, Lightning is a competitive rail.
Three signals to skip Lightning for now:
- 1.Your customers prefer stablecoins. The majority of crypto-paying customers in 2026 prefer USDC or USDT. Lightning does not carry those assets. Adding Lightning to serve a smaller segment is added complexity without proportional return.
- 1.You operate primarily on Shopify or WooCommerce. The mature Lightning plugins for those platforms exist but lag the stablecoin-rail plugins in feature parity and reliability.
- 1.You do not have an engineer comfortable with channel liquidity. Lightning operations is a real skill set. If you do not have someone to own it, the SaaS abstraction is worth the percentage fee until you do.
How Plaitr handles the Lightning question
Plaitr's default rail is stablecoin-denominated (USDC, USDT) on every major L1 and L2. The merchant accepts the customer's preferred token, Plaitr routes the value, settlement is same-day on-chain to the merchant's wallet. Lightning is on the roadmap but not yet a default checkout option, because the merchant volume in 2026 still skews heavily toward stablecoin acceptance over BTC.
For merchants who specifically need Lightning, the right tool today is Strike for international flow, Block's Square POS rollout for US in-person, or BTCPay Server with Lightning enabled for self-hosted full-stack control. These are mature, working, in-production rails. Lightning is not a future bet anymore. It is a tool with specific best uses.
What to do this week
Check your sales data. What percent of your customers paid in BTC over the last 12 months (versus stablecoins, versus cards)? If the BTC share is below 10 percent, Lightning is a "not yet" decision. If it is above 30 percent, the case for adding Lightning is strong, and the simplest path is a Lightning-enabled BTCPay Server alongside your existing stablecoin rail.
Lightning is not the future of crypto payments. It is one rail among several, with a specific best-fit profile. The 2026 reality is that the profile is real, the adoption is measurable, and the cases where Lightning wins are no longer hypothetical. The cases where stablecoin rails win are equally real and equally measurable. The merchant who picks correctly per use case is paying less than the merchant who tries to be neutral.