Merchant-Presented QR
Abbreviation: QR
Pronunciation: MUR-chuhnt pri-ZEN-tid kyoo-AR
Also known as: Merchant-Displayed QR, QR
Definition
Merchant-Presented QR is a QR code displayed by a merchant for a customer to scan and use to initiate or complete a payment. In merchant payment acceptance, it commonly covers merchant or invoice identity, amount, currency or asset, payment URI, expiration, reference, and status monitoring. It differs from customer-presented QR, where the customer displays a code for the merchant or terminal to scan. Operationally, teams should encode only necessary data, use standards where available, prevent tampering, handle expiration, verify payment server-side, and match the received payment to the correct order.
Overview
Merchant-Presented QR is a QR code displayed by a merchant for a customer to scan and use to initiate or complete a payment. For operational use in merchant account and operating management, teams should identify the object being described, the system of record, the event that creates it, and the outcome it is allowed to influence.
It differs from customer-presented QR, where the customer displays a code for the merchant or terminal to scan. Related operational concepts include Merchant POS Payment, Order Reference, and Checkout Session, each of which should retain a separate definition and system owner.
In merchant payment acceptance, it commonly covers merchant or invoice identity, amount, currency or asset, payment URI, expiration, reference, and status monitoring. The concept commonly includes merchant or invoice identity, amount, currency or asset, payment URI, expiration, reference, and status monitoring. It normally interacts with Merchant POS Payment and Order Reference, although the exact system boundaries vary by merchant and platform.
In merchant payment acceptance, it commonly covers merchant or invoice identity, amount, currency or asset, payment URI, expiration, reference, and status monitoring. The concept commonly includes merchant or invoice identity, amount, currency or asset, payment URI, expiration, reference, and status monitoring.
Controls for Merchant-Presented QR should use verified merchant mappings, least-privilege roles, approved settlement changes, configuration versioning, monitored production activity, reconciled statements and balances, and retained agreements. Reviews should confirm that customer-facing identity and support obligations match the responsible legal merchant. The audit scope should also preserve its distinguishing context: Merchant-Presented QR is a QR code displayed by a for.
In practice, a merchant reviewing Merchant-Presented QR should be able to trace the displayed value or status back to the applicable customer or account, commercial terms, source events, payment or order references, responsible system, and any later correction. That evidence determines whether the next action is customer communication, fulfillment, collection, refund, configuration change, or financial adjustment. The audit scope should also preserve its distinguishing context: Merchant-Presented QR is a QR code displayed by a for.
Key Takeaway
Merchant-Presented QR is a QR code displayed by a merchant for a customer to scan and use to initiate or complete a payment. Connect it to the correct legal merchant, configuration, responsibility, settlement, and reporting records.
Sources
- Build a Stripe-hosted checkout page — Stripe (2026-08-02)
- Accept a payment with the Express Checkout Element — Stripe (2026-08-02)