QR Codes & In-Person Crypto Payments for Business (2026 Guide)

39% of US merchants already accept crypto at checkout, according to the ++PayPal/National Cryptocurrency Association survey++ published in January 2026. Hospitality and travel lead adoption at 81%, with luxury and digital-goods retail close behind, and 88% of merchants report customers actively asking to pay with crypto.

There’s a caveat on that 39% figure: a meaningful share of "crypto acceptance" reported in industry surveys runs through wrapped checkout products, where a customer pays in crypto but it settles into the merchant's account as fiat through a custodial intermediary. That's a legitimate way to accept crypto, but it's a different flow from the direct, wallet-to-wallet QR payment this guide covers.

Most guides to accepting crypto in person are written for a coffee shop: high frequency, low ticket, same transaction repeated all day. That's not the problem a marine detailer, a boat dealer, or a luxury retailer actually has.

How the QR flow actually works

QR payments run on named technical standards. The current QR code format itself is ISO/IEC 18004:2024. Underneath most crypto QR payment flows sits either the EMVCo Merchant-Presented Mode, the same TLV-encoded standard behind national QR rails like PIX in Brazil and PromptPay in Thailand, or a chain-specific URI scheme like BIP21 for Bitcoin, still the dominant format in 2026 despite being formally superseded by BIP321.

The transaction itself runs in five steps:

The merchant enters the amount due on a device or terminal.
The system generates a QR code encoding that amount, in Merchant-Presented Mode, this is the standard direction. A second, less common flow, Consumer-Presented Mode, reverses it: the customer's own wallet displays the code and the merchant scans it instead.
The customer scans the code with their crypto wallet app.
The wallet displays the exact amount to send, locked at the current rate for a short window, typically 10 to 15 minutes.
Once the customer sends and the transaction confirms, the merchant sees payment confirmation immediately.

There’s no invoice step and no separate document to generate first. The QR code carries the payment request directly.

[Screenshot placeholder 1: QR code generation screen on the merchant device, showing the amount-entry step.]

[Screenshot placeholder 2: Customer-facing confirmation screen after a successful scan and payment.]

Why this fits on-site sales specifically

A coffee shop needs a QR flow that handles hundreds of small transactions a day without friction. A marine services business detailing a single boat, a dealer closing a luxury purchase, or an on-site contractor billing for a one-off job needs the opposite: one transaction, done right, with nothing left ambiguous.

Fee structure reinforces this. Crypto payment processing typically runs 0.5% to 1%, against 2% to 3% for card transactions industry-wide, a gap that matters more at high transaction values than at the size of a daily coffee order. Combined with no chargeback exposure once the transaction confirms, a topic covered in more depth in our chargebacks guide, the economics favor exactly the kind of infrequent, high-value sale this ICP handles.

Security considerations specific to in-person QR

Online checkout runs on a device the customer already controls, their own phone or laptop. In-person QR flips that. The payment request is displayed on a terminal or screen the merchant controls, and the customer's wallet has to trust that what's on that shared screen hasn't been tampered with before they scan it.

++WalletConnect's own documentation of the wallet-to-merchant connection++ notes this is exactly why encrypted, end-to-end communication between the wallet and the merchant's system matters more for in-person flows than for online checkout. A properly built in-person QR flow should generate a fresh, dynamic code per transaction rather than displaying a static, reusable one, precisely to close that gap.

What you actually need to set this up

A device or screen to display the QR code. A way to confirm the amount before generating it. And a workflow for what happens if a customer scans, then changes their mind before sending, since a generated QR code with a locked rate window will expire if unused.

This is a lighter setup than the invoicing flow, which is built for billing a customer who isn't standing in front of you. In-person QR skips that step entirely because the transaction is happening in real time.

Compliance basics for in-person crypto payments

Identity verification and Travel Rule data requirements apply here the same as any other crypto transfer, per ++FATF's Recommendation 16 guidance++. In practice, for a properly licensed payment gateway, this runs in the background but it's worth knowing it's there rather than assuming an in-person crypto transaction is unregulated because no card was swiped.

Frequently asked questions

How do I accept crypto payments in person?

Generate a QR code showing the amount due, using a merchant device or terminal connected to a payment gateway. The customer scans it with their crypto wallet, confirms the amount, and sends payment within the locked-rate window. No separate invoice is required.

Is a website required to accept crypto in person?

No. In-person QR payments run through a merchant device or app rather than an online checkout page, so a website isn't a prerequisite the way it typically is for e-commerce crypto acceptance.

How is in-person crypto payment different from an online crypto checkout?

The core mechanics are similar: generate a request, customer pays within a locked window, but the QR code is displayed on a shared terminal rather than the customer's own device, which is why dynamic, per-transaction codes and encrypted wallet communication matter more for the in-person flow specifically.

Do luxury and marine businesses actually accept crypto payments?

Yes. Luxury and digital-goods retail are among the highest-adoption merchant categories at around 76%, behind only hospitality and travel at 81%. Marine and high-ticket service businesses are a smaller but growing segment following the same pattern: one large, one-off transaction rather than daily volume.

What happens if a customer scans a QR code but doesn't complete the payment?

The rate lock and the QR code both expire after the set window, usually 10 to 15 minutes. The merchant can generate a new code if the customer is ready to try again.