What your customer sees at checkout

The whole flow, in 90 seconds

Most merchants overthink this part. They picture a complicated, technical interaction at the register: customers fumbling with wallet apps, staff explaining what Bitcoin is, a line forming behind them.

Almost none of that happens.

The actual flow is faster than a card transaction. Here's the entire customer experience, in the order it occurs.

At the point of sale (in-person):

1. Your staff rings up the order. Total is $42.
2. The customer says "I'll pay in Bitcoin" (or, more commonly, taps a "Pay with Lightning" button on the customer-facing screen).
3. Your POS displays a QR code with the $42 amount.
4. The customer opens their wallet app and scans the QR code with their phone camera.
5. The wallet shows the customer the amount and asks them to confirm.
6. They tap "Pay" or swipe right.
7. About 1-2 seconds later, your POS shows "paid."
8. You hand them their order.

That's it. Total time from QR appearing to "paid" confirmation: usually under 5 seconds. Often the customer hasn't even put their phone back in their pocket before the transaction is complete.

Online (e-commerce):

Same general flow, slightly different mechanics.

1. The customer fills their cart, $87 total.
2. At checkout, they select "Pay with Bitcoin" alongside other payment options.
3. The next screen shows a QR code (for mobile users) or a "Pay" button (for desktop users on the same device).
4. They scan the QR or click the button. Their wallet app opens with the amount pre-filled.
5. They confirm in the wallet.
6. Your checkout shows "paid," the order completes, and they get the confirmation email.

For desktop e-commerce, there's a small additional wrinkle: the customer might be on a laptop, with their wallet on a phone. In that case, they scan the on-screen QR with their phone, confirm in the wallet, and the laptop checkout updates automatically. This handoff is seamless — they don't have to do anything special.

What the customer is not doing

The merchant fears about Bitcoin checkout usually involve worst-case scenarios that don't actually happen. Worth naming them and dismissing them:

They're not typing a 64-character Bitcoin address. That was true in 2014. Lightning eliminated it. Modern checkout is QR-code-based or wallet-button-based; the customer never sees a Bitcoin address.

They're not calculating exchange rates. The QR code locks in the dollar amount at the moment of generation. When the customer scans, their wallet shows them exactly the equivalent in Bitcoin (or sats — the smaller denomination) at the current rate. They tap to confirm. No math.

They're not waiting for "confirmations." That's the slow-network experience. On Lightning, the moment they tap "confirm," you see "paid." There's no 10-minute confirmation window.

They're not getting confused by Bitcoin's volatility. If Bitcoin's price moves 2% in the 30 seconds between QR generation and payment, that's not the customer's problem and it's not your problem. The dollar amount you wanted is the dollar amount that gets paid; the Bitcoin amount in the customer's wallet adjusts to match.

They're not paying a fee on top of the amount. Lightning fees are typically pennies and are paid by the network routing the payment — not added to the customer's bill. The $42 they see is the $42 you receive (or, more precisely, the $42 minus your platform fee, same as any other payment method).

What the customer experience feels like

If you've never seen this in person, the closest comparison is Apple Pay or Google Pay. The customer holds their phone up, the screen does something for a second, and the transaction is done.

The major difference: there's no "tap your phone to the reader" gesture. The QR code on your screen is what does the work. The customer's phone is the wand, your POS screen is the target.

For first-time users (the curious customer category we talked about in Lesson 1), there's often a small moment of "wait, that worked?" — because they expected something more complicated. That moment is, frankly, a brand moment. They remember it. They tell their friends. "I paid in Bitcoin at [your business] and it was actually easy."

For experienced users (the Bitcoin-native and international segments), the experience is just normal payment. They don't think about it. They scan, tap, leave.

The "what if" scenarios

A few edge cases worth knowing about, even though they're rare:

What if the customer's wallet doesn't have enough Bitcoin? Same as if their card got declined. The wallet shows them the issue, they pay another way. Nothing happens on your end except "didn't complete."

What if the customer wants to pay over multiple wallets? Almost never asked, but technically possible — Lightning can route a payment from multiple sources. In practice, customers pay from one wallet.

What if the customer's phone has no signal? Lightning needs a brief connection to confirm the payment. If they're truly offline (rural location, bad coverage), the payment won't go through. You'd just take another payment method. This is rare in practice — most customer phones have at least some signal.

What if the QR code expires? QR codes are typically valid for 60 seconds to 5 minutes. If the customer takes longer than that, the POS generates a new one. No charge, no issue.

What if the customer wants a receipt? Standard. Lightning payments generate the same receipts your other payments do — printed, emailed, or both. Most POS integrations include the transaction ID, which can be used to verify the payment on the Bitcoin network if anyone ever questions it.

What's next

You now know:

• The exact step-by-step of a customer paying in Bitcoin (in-person and online)
• That the experience is faster than card and feels closer to Apple Pay
• What the customer is not doing (typing addresses, calculating rates, waiting for confirmations)
• What it feels like — both for first-timers and experienced users
• The "what if" edge cases worth knowing about

Next up: Lesson 4 — Wallets: the only thing your customer needs. We'll cover the four wallet apps your customers actually use, the differences between them, and how to handle the rare customer who shows up wanting to pay in Bitcoin but doesn't have a wallet yet.