QR code payment
A camera, barcode reader, or supported payment application reads a QR code. The code communicates information used to start or conduct the payment flow.
Mobile payments and contactless FAQ
QR code payments are often described as contactless or touchless because the customer and merchant can complete checkout without handing over a card or making physical contact with a payment terminal. However, a QR payment is not the same technology as an NFC tap transaction. A QR flow uses a camera or optical scanner to read a two-dimensional code, while EMV contactless chip payments use a contactless chip card or an NFC-enabled mobile device near a compatible reader.
That distinction matters when a merchant evaluates equipment, customer instructions, reporting, and provider support. The word contactless may describe the customer experience broadly, but the technical payment flow still needs to be identified accurately.
A customer can scan or present a QR code without touching merchant equipment, so QR checkout fits the everyday idea of a touchless payment. In technical payment documentation, though, EMV Contactless Chip refers to transactions made with contactless chip cards and NFC-enabled mobile devices. EMV QR Code is a separate technology with its own specifications and operating patterns.
A camera, barcode reader, or supported payment application reads a QR code. The code communicates information used to start or conduct the payment flow.
A contactless chip card, phone, or other NFC-enabled device communicates at close range with a supported payment reader.
Merchants can call QR checkout touchless while explaining separately whether their checkout accepts QR codes, tap payments, or both.
EMVCo describes two primary QR payment modes. In merchant-presented mode, the business displays the QR code and the customer scans it with a supported mobile application. In consumer-presented mode, the customer displays a QR code on a mobile device and the merchant scans it with an optical scanner or mobile device.
The code is only one part of the workflow. EMVCo notes that its QR specifications standardize the QR data format, while messaging after the code is read and processed is left to payment providers. The underlying payment can also vary: EMV QR formats can support card-based and account-based payment options. A merchant should therefore avoid assuming that every QR code uses the same payment rail, customer application, confirmation flow, or operating rules.
A QR code printed near a register does not establish that the existing terminal can accept QR payments, and an NFC symbol does not establish QR acceptance. Each option may require a different application, scanner, display, staff step, or confirmation screen. Support depends on the merchant's payment provider, software, equipment, transaction type, and enabled services.
Use precise language on signs and checkout screens. If customers scan a merchant-displayed code, tell them which approved application or checkout path to use. If staff scan a customer-presented code, document where employees should confirm the result. A merchant-facing payment status should be the operational source of truth; staff should not rely only on a customer's screen or verbal confirmation.
Merchants comparing broader options can review mobile payments and contactless guidance and the overview of digital wallets and alternative payments.
Ask whether the merchant presents the code or scans the customer's code, which application is required, how amounts are entered, and how completed or canceled attempts appear.
Confirm support for the merchant's current POS, payment service, devices, connectivity, receipt process, and sales channels. Do not infer compatibility from a QR label alone.
Make the accepted flow clear at checkout. Train staff to recognize pending, completed, failed, and canceled states in the merchant's own system.
Determine how QR payments are labeled in transaction records, daily reports, refunds, and reconciliation so the business can trace a payment from checkout to its records.
For a related in-person workflow, see how merchants accept digital wallets in person. If an existing tap option is failing, use the separate contactless payment troubleshooting guide.
No universal assumption should be made. NFC tap acceptance and QR acceptance are different capabilities. Verify the terminal, POS, scanner, application, and payment provider for the specific merchant setup.
No. QR codes are general-purpose data carriers, and not every QR code is a payment code. Even within payment flows, the data and processing path depend on the implementation and provider.
A merchant may be able to offer both, but support is setup-specific. Confirm each payment method separately and give customers clear instructions for the option they select.
Start by documenting whether customers will scan a merchant code, present a customer code, tap an NFC device, or choose among several methods. Then verify the required payment service, equipment, customer steps, merchant confirmation, and reporting before enabling the option.
When requesting guidance, describe the current POS or checkout environment and the desired customer flow. Do not submit cardholder data, passwords, bank credentials, complete account numbers, or secret API keys through a general contact form.
Explore mobile payment guidanceTo learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US