QR code payments at the counter: what to know

QR codes are everywhere now, from restaurant menus to parking meters. QR code payments use a scannable square barcode to start or complete a payment on a phone. At a store counter, that can mean a customer scanning your code to pay, or you scanning a code on their phone. It's a different path from tapping a card, and it brings its own setup questions and scam risks.

It's worth understanding before a customer asks whether you take it.

How do QR code payments work?

A QR code is a two-dimensional barcode that stores information, often a web address. Phones can read them with the camera.

There are two main styles at the counter.

Store-presented codes. You display a code, printed or on a screen. The customer scans it with their phone, which opens a payment page or app. They confirm the amount and pay. Some codes are static, meaning the customer types in the amount. Others are dynamic, generated for each sale with the amount already filled in.

Customer-presented codes. The customer opens an app that shows a code on their screen. You scan it with a scanner or device, and the payment runs.

Behind the scenes, the payment might run on a card, a bank account, or a digital wallet balance, depending on the service.

How is this different from tapping a phone?

When a customer taps a phone wallet on your card reader, it works like a contactless card. It runs on the card networks, follows the chip and contactless standards, and settles with your regular card sales.

QR payments often run through a separate service or app. They may have their own fees, their own settlement schedule, and their own rules for refunds and disputes. They may not show up in your POS the same way as card sales.

So "we take phone payments" can mean two very different things. Tap-to-pay on your reader is one. QR payments through an app is another.

What are the risks?

A few worth knowing.

Fake codes. Scammers sometimes stick their own QR code over a legitimate one. Customers scan it and pay the scammer instead of you. If you display a printed code, check it every day, the same way you'd check your card reader for skimmers.

Wrong amounts. With static codes, customers type in the amount. Mistakes happen, and some are on purpose. Always confirm the payment amount on your end before handing over goods.

Unconfirmed payments. A customer might show you a screen that looks like a completed payment. Confirm the payment arrived in your system, not just on their phone.

Record gaps. If QR payments don't connect to your POS, your sales reports and drawer counts may not line up. Plan how you'll record them.

Should you offer QR payments?

It depends on your customers and your setup. Ask a few questions first.

Do your regulars actually ask for it, or do they already tap cards and phones?

What service would you use, and what are its fees and settlement terms?

How do refunds and disputes work?

Does it connect to your POS so sales are recorded properly?

For many neighborhood stores, contactless card and phone taps at the reader already cover what customers want. Ask the NRS Pay team what your setup supports; don't assume QR payments are available on your account until they confirm. For readers that handle tap-to-pay, see NRS Pay equipment. The FTC's small business guidance also covers common scams, including fake payment requests.