Why this question matters more than it used to

A few years ago, merchants asking about Bitcoin payments were largely dealing with a single option:

• Send Bitcoin

• Wait for confirmation

• Receive funds

That model worked for some use cases and failed visibly in others. Coffee shops tried it and watched checkout lines stall. Online stores added it and found customers abandoning carts when fees exceeded the item value.

The Lightning Network changed what “accepting Bitcoin” actually means. It introduces a second layer built on top of Bitcoin that routes payments off-chain, settles them in milliseconds, and charges a fraction of a cent per transaction.

Merchants who route everyday purchases on-chain pay unnecessary fees and introduce checkout delays that hurt conversion. Merchants who dismiss on-chain entirely miss the settlement model it was designed for. 

This guide covers both layers in enough detail to make the right call for your business.

The problem on-chain Bitcoin creates for merchants

On-chain Bitcoin is the base layer. Every transaction settles directly on the Bitcoin blockchain, recorded permanently and verified by thousands of nodes. 

That architecture gives it extraordinary security properties, immutability, global verifiability, and cryptographic finality. For transferring significant value, it is one of the most reliable payment systems ever built.

For retail commerce, those same properties create friction.

The Bitcoin blockchain processes around 7 transactions per second. Each transaction waits in a queue called the mempool before miners include it in a block. A new block appears roughly every 10 minutes, but most merchants and exchanges require 3 to 6 confirmations before treating a payment as final.

Which means waiting anywhere from 30 minutes to over an hour in normal conditions. During periods of high network congestion, which will extend further, fees spike as users compete for block space.

On-chain transaction fees are not fixed. They are determined by how much block space your transaction needs and how busy the network is at the moment. During peak demand periods, market volatility, major events, and inscription waves. Fees have historically spiked from a few dollars to $50 or more per transaction.

For a merchant processing a $15 lunch order or a $30 online sale, a $10 fee is not a cost of doing business. It is a structural problem that makes the payment model unworkable. Zero-confirmation acceptance is one way merchants try to work around this, treating an unconfirmed transaction as good immediately.

The risk is double-spending. With Replace-by-Fee now standard on the Bitcoin network, an unconfirmed transaction can be replaced by a higher-fee version that sends the funds elsewhere. Merchants accepting zero-conf transactions carry that exposure on every sale.

None of this means that on-chain Bitcoin is a failed system. It means it was not designed for what retail merchants need from a payment rail. Understanding on-chain and Lightning as separate tools for separate jobs is the starting point for building a payment stack that actually works.

What does lightning solve? And how does it work?

The Lightning Network is a second-layer protocol that sits on top of Bitcoin. It was introduced by Joseph Poon and Thaddeus Dryja in 2015 and launched on the Bitcoin mainnet in 2018. The design premise is straightforward: 

If two parties are going to transact repeatedly, they don’t need to recover every transaction on the blockchain. They can open a shared payment channel, move funds between them off-chain as many times as needed, and settle the final balance on-chain when they're done.

The practical result for merchants is that payments clear in under a second without touching the Bitcoin blockchain. Fees on Lightning are typically composed of a small base fee (around 1 satoshi) plus a percentage of the payment amount, usually less than 0.1%. 

For a $50 transaction, that comes to a few cents at most. For a $5 transaction, it costs almost nothing. This is what makes Lightning viable for micropayments that would be economically impossible on-chain.

Lightning also scales in a way that on-chain cannot. The Bitcoin blockchain handles around 7 transactions per second. The Lightning Network has no theoretical throughput limit; capacity is bounded by the number of channels and available liquidity, not by block size.

In April 2026, BTC Inc. processed 4,187 Lightning payments in a single eight-hour window at a Las Vegas event, covering tickets, merchandise, vendor settlements, and staff payouts through one payment stack. That kind of volume at that kind of speed is not achievable on-chain.

For merchants, the operational difference comes down to four things:

Settlement speed

Lightning payments are final the moment they are completed. There is no confirmation queue, no mempool wait, and no need for the customer to stand at the counter while blocks are mined. The transaction either succeeds or fails within milliseconds, and when it succeeds, it is done.

Fee predictability

On-chain fees depend on network congestion and cannot be predicted reliably. Lightning fees are stable and minimal regardless of Bitcoin network activity. A merchant accepting 500 Lightning transactions in a day pays predictable, negligible fees on every one of them.

Chargeback elimination

Lightning payments are cryptographically final. Once the payment settles, it cannot be reversed. This removes the chargeback risk that costs card-accepting merchants billions annually, not just in reversed charges, but in dispute fees, processor penalties, and fraud management overhead.

Global reach

Lightning payments work across borders at the same fee and speed as domestic transactions. A customer in Singapore paying a merchant in Brazil through Lightning pays the same fraction of a cent as a local transaction, with no correspondent banking delays and no currency conversion at the payment layer.

On-chain vs Lightning for merchants (Compared)

The comparison makes the use-case split clear. On-chain belongs in high-value, non-time-sensitive transfers where cryptographic finality and blockchain immutability matter more than speed. Lightning belongs at the checkout, whether that checkout is a physical POS terminal, an eCommerce cart, or a subscription billing system.

Where stablecoins fit into this?

Bitcoin’s volatility is a real concern for merchants who want to hold what they receive. A business that accepts Bitcoin at $95,000 and watches it drop to $82,000 over the next week has absorbed a meaningful loss on its revenue. That exposure is manageable with the right settlement tools, but it is a legitimate operational consideration.

USDT on the Lightning Network addresses this directly. Tether announced native USDT integration on Lightning in January 2025 using the Taproot Assets protocol. The result is a payment that moves at Lightning speed and cost, settled in under a second, with fees well under a cent, but denominates the value in US dollars rather than Bitcoin.

Merchants can accept USDT on Lightning and receive dollar-stable funds without any conversion step or fiat off-ramp delay. The future of global payments matters for two categories of merchants. 

The first is businesses in markets with a strong USD preference or cross-border supplier relationships, where invoicing in Bitcoin introduces accounting complexity. The second is a merchant who wants to accept crypto from customers who hold it but don’t want to manage Bitcoin price exposure on the settlement side.

Speed supports USDT and USDC on Lightning alongside Bitcoin, which means a merchant can accept payments in any of those assets and settle in whichever form their business prefers. 

Real-world use cases: Where each layer belongs

Retail and quick-service restaurants

On-chain Bitcoin at a fast-food counter is not viable. A customer ordering a $12 meal cannot wait 30 minutes for block confirmations. Zero-conf acceptance introduces fraud exposure. And when on-chain fees spike above a dollar, the payment math breaks down entirely on a sub-$20 transaction.

Lightning handles this without friction.

• The customer scans a QR code. 

• Payment clears.

• The receipt prints.

Total elapsed time: Under a second. This is exactly how Steak ‘n Shake deployed Bitcoin payments across all 393 U.S. locations through Speed’s infrastructure. 

Lightning QR codes at retail stores, at the kiosk, and drive-throughs allowed customers to pay with Bitcoin in the same time it takes to tap a card, with lower fees for the merchant and no chargeback exposure.

eCommerce and digital goods

Online merchants benefit from Lightning’s instant settlement and global reach. A customer in Germany buying a digital product from a US-based store pays in Lightning-native Bitcoin or USDT, the merchant receives settlement within seconds, and there is no currency conversion step, no chargeback window, and no payment processor taking 2–3% of the sale. 

On-chain Bitcoin still works for online purchases if the transaction value is large enough to absorb fees and the customer experience allows for confirmation delays. A $500 electronics purchase from a Bitcoin-native customer could reasonably happen on-chain if the buyer can wait and the merchant accepts the transaction after sufficient confirmations.

For anything below that threshold, and especially for high-volume, smaller-ticket stores, Lightning is the appropriate rail. Speed’s eCommerce & Marketplaces infrastructure supports both layers with checkout integrations and API-level access for custom implementations.

Gaming and entertainment

In-game purchases, virtual item transactions, and platform tipping operate at amounts where on-chain fees make the payment model unprofitable. A player buying a $0.50 in-game item cannot pay $3 in mining fees to do it. Lightning makes those transactions practical, and fees stay well under a cent regardless of the transaction amount.

Platforms handling high volumes of small-value transactions also benefit from Lightning's throughput. Subscription and pay-per-use billing models that require recurring micro-charges every few minutes or hours function on Lightning in a way they never could on-chain.

Speed's Gaming & Entertainment infrastructure is built for this volume.

Cross-border B2B payments and payouts

Large B2B transfers, supplier payments, contractor payroll, and international settlements are better suited to on-chain Bitcoin in some cases. A $50,000 supplier payment benefits from on-chain finality and the permanent blockchain record. 

The 30-minute confirmation window is acceptable for a payment of that size. On-chain fees at that value represent a fraction of a percent rather than a structural problem. 

For smaller recurring cross-border payments, Lightning wins again. Sending contractor payments of $ 200-$2,000 weekly or monthly via Lightning is faster and cheaper than wire transfers, with no correspondent banking overhead and no SWIFT delays.

How does Speed handle both layers?

Speed was built as Lightning-first infrastructure, but it supports both on-chain and Lightning within a single merchant account. Merchants don't have to choose one and exclude the other; the platform routes payments appropriately and gives merchants control over how they settle.

Payments cover inbound transactions from customers. Speed generates Lightning invoices and QR codes that work with any Lightning-compatible wallet, processes payments in under a second, and provides real-time confirmation via webhook. On-chain payments are also supported for merchants or customers who prefer that layer.

Payouts handles outbound transfers. Whether sending contractor payments, processing refunds, or distributing affiliate earnings, Speed supports both Lightning and on-chain destinations in the same payout job. Batch payouts allow merchants to send to hundreds of recipients in a single operation.

Terminals are browser-based point-of-sale tools for in-person transactions. No proprietary hardware is required. Staff can accept Lightning payments from a tablet, phone, or desktop, generating QR codes, adding service charges, and tracking transactions in real time. This is the same infrastructure deployed at Steak ‘n Shake.

On-ramp & Off-ramp allow merchants to move between fiat and crypto in either direction. A merchant who accepts Bitcoin but wants to settle in USD can convert automatically. A merchant who wants to hold Bitcoin as a treasury asset can do that too. The settlement preference is configurable per merchant account.

Connect is the white-label infrastructure layer for platforms and PSPs that want to offer Bitcoin and stablecoin payments to their own merchant base. It exposes the full Speed stack through a Lightning Network API without requiring each sub-merchant to integrate separately.

How does Lightning payment actually work: A step-by-step flow?

Understanding the payment lifecycle helps merchants integrate correctly and set accurate expectations for their customers and finance teams. 

Step 1: Invoice generation

When a customer initiates checkout, the merchant system calls Speed’s API to generate a Lightning invoice. The invoice specifies the amount and sets an expiry window (typically 10 mins, which is configurable). The merchant frontend displays this as a QR code or a payment button.

Step 2: Customer payment

The customer scans the QR code with a Lightning-compatible wallet such as Speed wallet or any other compatible application. The wallet reads the invoice, finds the best payment route through the Lightning network, and submits the payment.

Step 3: Network routing

The Lightning Network routes the payment from the customer’s node through payment channels to Speed’s node. This happens automatically and typically completes within milliseconds. The routing algorithm selects the path with the best combination of liquidity and fee.

Step 4: Settlement and confirmation

Once the payment reaches the destination, the cryptographic proof of payment is released, and the transaction settles. Speed triggers a webhook to the merchant system, confirming the payment, updating the order status, and recording the transaction.

Step 5: Reconciliation and settlement

Speed records the transaction with a timestamp, the exchange rate at the time of payment, and the settlement amount. Merchants can export transaction data via CSV or API for accounting. Settlement to fiat or stablecoin happens based on the merchant’s configured preference.

From checkout to settlement, this covers the full merchant-side payment lifecycle, including how to handle partial payments, invoice expiry, and reconciliation.

Which layer should your business use?

The short answer: Lightning for almost everything at the checkout; on-chain when transaction value and confirmation security matter more than speed.

A more specific breakdown:

Use lightning when the transaction is under a few thousand dollars in value, the customer expects a fast checkout experience, you are processing high volume or high frequency payments, the transaction is cross-border, and you want to avoid banking delays, or you are handling micropayments where on-chain fees would consume the value.

Use on-chain Bitcoin when the transaction is a large treasury transfer or institutional settlement, when the receiving party specifically requires on-chain confirmation, or when you are sending funds to cold storage or long-term custody. For these cases, the 30-to-60- minutes window is acceptable and the security guarantees are worth it.

The practical answer for most merchants is that they need both, with Lightning as the default for customer-facing transactions and on-chain available for settlements, large B2B transfers, and specific customer requests. Speed's infrastructure handles that without requiring separate accounts or separate integrations.

If you are in the process of evaluating payment infrastructure providers, then follow the criteria in detail, including routing success rates, liquidity coverage, and developer experience.

FAQs