Bitcoin Lightning vs on-chain payments: which rail should you use?

If someone is about to pay you in bitcoin, you need to decide which way to receive it before you give them an address or invoice. The two main options, on-chain and Lightning, work very differently and suit different situations. This guide breaks down both so you can pick the right one for your context.

What "on-chain" actually means

Every bitcoin transaction that gets broadcast to the main blockchain is called on-chain. The sender creates a transaction, signs it, and broadcasts it to the peer-to-peer network. Miners bundle it into a block, and once enough blocks pile on top (typically six, though many merchants accept one), the payment is considered final.

A few things follow from this:

• Settlement is slow by design. Blocks come every ~10 minutes on average. Six confirmations takes roughly an hour.
• Fees vary with demand. When block space is congested, fees can spike to several dollars or more per transaction, paid in satoshis. When the network is quiet, fees are low.
• There is no practical size limit on a single payment. Sending $50 CAD or $5 million CAD costs roughly the same fee.

On-chain is the base layer. It is what most people picture when they think of bitcoin. If you want to understand how a transaction actually moves through the network before diving into payment rails, the guide on how bitcoin payments work step by step covers the mechanics in plain language.

What Lightning is

Lightning is a second layer that runs on top of bitcoin. Instead of recording every payment on the blockchain, two parties open a payment channel by making one on-chain transaction. After that, they can send payments back and forth between themselves (or route through other connected nodes) without touching the blockchain again. When they want to close out, they settle the final balance on-chain.

The result is payments that confirm in seconds and cost a fraction of a cent. A Lightning invoice typically expires in minutes or hours, and the payment either succeeds immediately or fails cleanly. There is no waiting.

Lightning does come with tradeoffs. The receiving side needs a node or wallet with inbound liquidity: funds already committed to that channel from the other direction. Setting up a proper Lightning node takes some effort. Custodial Lightning wallets (where a third party manages the node) are simpler but mean you do not hold your own keys.

Comparing the two rails

Here is a side-by-side look at how on-chain and Lightning differ on the factors that matter most for Canadian merchants and individuals:

Factor	On-chain	Lightning
Confirmation time	~10 min per block; full settlement ~1 hr	Seconds
Transaction fee	Variable; can be $0.50-$10+ CAD in busy periods	Fractions of a cent
Minimum practical amount	No hard floor, but fees make micro-amounts wasteful	Works well for any amount, even a few cents
Maximum amount	No ceiling	Depends on channel capacity (can be large with proper setup)
Privacy	Pseudonymous; all transactions public on-chain	Slightly better; intermediate hops see less data
Setup complexity	Low; any wallet can receive on-chain	Moderate; need a node or custodial service
Reversal risk	Zero after confirmations	Zero if properly implemented
Best suited for	Large or infrequent payments	Small, frequent, or speed-sensitive payments

When on-chain makes more sense

On-chain is the better fit when:

• The payment amount is large enough that the fee is a small percentage. Sending or receiving $500+ CAD on-chain is usually sensible even when fees are elevated.
• Speed is not critical. Real estate deposits, invoice payments between businesses, or peer-to-peer transfers between individuals can wait an hour.
• You want maximum simplicity. Any bitcoin wallet can send and receive on-chain. There is nothing to configure beyond a standard address.
• You prefer to avoid custodial risk. On-chain receipt goes straight to your wallet with no intermediary node involved.

For Canadian businesses that invoice clients monthly or accept deposits on big-ticket items, on-chain is the practical default. The beginner's guide to accepting bitcoin payments in Canada walks through how to set up on-chain receipt from scratch.

When Lightning makes more sense

Lightning is a better fit when:

• The payment is small. A $5 CAD coffee or a $2 tip does not make sense on-chain when the fee might match or exceed the amount.
• You need instant confirmation. Retail point-of-sale, vending machines, or any situation where the customer is standing in front of you.
• You are handling high transaction volume. A busy online shop accepting small purchases would find on-chain fees and wait times impractical.
• You want to experiment with streaming payments or pay-per-use models. Lightning supports this in ways on-chain cannot.

One thing worth knowing: some Lightning wallets for Canadian users settle to on-chain bitcoin periodically. So even if your customer pays via Lightning, you may ultimately hold on-chain funds. The distinction matters operationally, but the end asset is the same.

Tax and compliance notes for Canadians

The Canada Revenue Agency treats bitcoin as a commodity. Whether you receive payment on-chain or via Lightning does not change your tax position. Both create a transaction that may trigger income or capital gains obligations, depending on your situation. You should record the CAD value at the time of receipt for each payment, regardless of which rail it came in on.

FINTRAC rules around money services businesses may also apply if you are operating as an exchange or processor rather than simply accepting bitcoin for goods or services. The regulatory line depends on your business model, not on which payment rail you use.

This is an educational overview, not tax or legal advice. CRA guidance and FINTRAC registration requirements change, so confirm current rules before setting up any payment system. A tax professional familiar with crypto is worth the consultation fee.

Practical decision guide

If you are unsure which rail to set up first:

1. If your average transaction is above ~$100 CAD and speed is not a concern, start with on-chain. It is simpler and works with any bitcoin wallet.
2. If you are in retail, hospitality, or any context where customers pay at the point of sale, add Lightning from the start. Waiting for blockchain confirmations while a customer stands at the counter is not practical.
3. If you want to understand what you are actually agreeing to when you accept bitcoin either way, read what it really means to accept bitcoin as payment before choosing a processor.

Many businesses end up supporting both rails. Most modern bitcoin payment processors handle both and present a single QR code that the sender's wallet resolves to the right option automatically (this is called a unified QR or BIP-21 URI). You do not necessarily have to pick one and stick with it.

---

FAQ

Can I accept Lightning payments without running my own node?

Yes. Custodial Lightning wallets like Wallet of Satoshi or Blink let you receive Lightning payments without running any infrastructure. The tradeoff is that those providers hold your funds until you withdraw. Non-custodial Lightning wallets exist too but require more setup. Which approach fits depends on how much you want to control your own keys.

What happens if a Lightning payment fails partway through?

Lightning payments either complete or they do not. There is no stuck-in-the-middle state from the receiver's perspective. If the payment fails, the sender gets their funds back automatically. You do not need to issue a refund; nothing was deducted from the sender in a failed route.

Do on-chain and Lightning fees show up differently for CRA purposes?

The CRA has not issued specific guidance distinguishing on-chain fees from Lightning routing fees as of this writing, but both are generally deductible as business expenses when incurred in the course of business. Keep records of amounts paid in fees, including the CAD equivalent at the time. Confirm current CRA positions with a tax advisor.

Is one rail more private than the other?

On-chain transactions are publicly recorded on the blockchain forever, though addresses are pseudonymous rather than directly tied to identities. Lightning routing reveals less information to third parties because intermediate nodes only see adjacent hops, not the full path. Neither rail provides complete anonymity.

Can Canadian merchants accept both on-chain and Lightning with one QR code?

Many payment processors and some self-hosted setups support unified QR codes (BIP-21) that encode both an on-chain address and a Lightning invoice. The sender's wallet picks the appropriate rail. If you are using a processor, check whether they support unified QR, as most major ones do.