QR Code Payments: How They Work and How to Accept Them

QR code payments let a customer scan a code with a phone camera, confirm an amount and pay, with no card handed over and no cash counted. You can accept them at the counter, at the table, on an invoice or inside the software your business already runs.

This guide explains how the codes work, how to set them up, where text to pay fits, what it costs to accept them and how to keep customers safe. It also covers embedded payments, the model behind a payment integration we are building for HighLevel.

TL;DR

• A QR code payment starts when a customer scans a code. A static code points to a payment form. A dynamic code shows the exact amount for that sale.
• Start with the system you already use. Ask your POS or processor whether it can generate payment QR codes or payment links before you add a new tool.
• Text to pay sends a secure payment link by SMS. It suits phone orders, deposits, service calls and overdue invoices.
• Dynamic codes, daily checks of printed signage and PCI DSS compliant processing are the core safety habits.
• Embedded payments put checkout inside the software where the sale already happens, so you do not need to send customers elsewhere.

Table of Contents

• How QR code payments work
• Payment QR codes vs regular QR codes
• Where QR code checkout fits in your business
• Text to pay and pay by text
• How to set up QR code payments
• What does it cost to accept QR code payments?
• Keeping QR code payments safe
• QR codes vs tap to pay
• Embedded payments: QR and card-not-present checkout inside your software
• Our perspective
• Get QR, text and card payments on one account
• FAQ
• Sources

How QR code payments work

The flow is simple. The customer opens the phone camera or a banking or wallet app and scans a code. The phone opens a payment screen, the customer confirms and the money moves.

The U.S. Chamber of Commerce describes two types of code. A static code links to a web payment form where the customer enters the transaction details. A dynamic code shows the amount owed so the customer can confirm it.

The U.S. Payments Forum adds a practical detail. A static code is displayed by the merchant, for example on a decal at the payment counter. A dynamic code is generated for each transaction, usually on a screen, and can carry extra data such as the amount.

Static codes

A static code never changes. You print it once and place it where customers pay.

It is cheap and easy to roll out. The trade-off is that the customer usually types in the amount, so it fits fixed-price items, donations, tips and low-volume counters.

Dynamic codes

A dynamic code is created for one sale. The amount, order number and sometimes the tip are already filled in.

This cuts typing errors and makes reconciliation easier, because each payment ties back to a specific order. It is the better choice for restaurants, retail checkouts and anything with variable totals.

Payment QR codes vs regular QR codes

A regular QR code usually opens a web page, such as a menu. A payment QR code starts a transaction.

The Federal Reserve Financial Services explains the difference: payment codes are accessed through an authenticated app, such as a mobile banking app or digital wallet, which can add security. URL codes are typically opened through the phone camera to view menus or web pages.

The same source notes that the newly introduced X9.150 standard sets security, structure and content requirements for merchant-presented payment QR codes. The goal is interoperability across payment networks.

That standard is new. The U.S. Payments Forum has noted that QR implementations in the U.S. have lacked a single industry-wide standard, so the experience can differ by app or provider. Choose a provider whose checkout page is clear, branded and works on any smartphone.

Where QR code checkout fits in your business

The right setup depends on how and where customers pay.

QR codes also work as a doorway to other things. They can trigger loyalty rewards, open an online ordering page or lead to a tip screen. If you run online ordering, our guide on what online ordering means for businesses shows how the pieces connect.

For restaurants, a QR code sits best beside a full system. See our restaurant POS systems and payment processing page for what a complete setup looks like.

Text to pay and pay by text

Text to pay is the close cousin of QR checkout. Instead of the customer scanning a code, you send a payment link to their phone by SMS. They tap it, land on a secure payment page and pay with a card or wallet.

It works well when the customer is not standing at your counter. Think phone orders, deposits, appointment balances, repair estimates and past-due invoices.

Here is how it typically runs:

1. You enter the amount in your payment software or virtual terminal.
2. The system creates a secure payment link.
3. You text the link to the customer’s mobile number, with their permission.
4. The customer opens the link, reviews the amount and pays.
5. You receive confirmation and the payment is recorded against the invoice.

The backend work, including the SMS delivery, is usually handled by your processor or a messaging partner. You do not build it yourself.

Two habits keep text to pay professional. First, only text customers who have agreed to receive messages from you. Second, make the message recognizable: include your business name and the invoice or order reference, so the customer knows it is real.

The FTC warns about fake messages that pair a QR code with threats, for example texts demanding payment in cryptocurrency to avoid a utility shutoff. Customers are right to be cautious, so a clear, branded message with a familiar sender name builds trust.

How to set up QR code payments

The U.S. Chamber of Commerce outlines a simple path: confirm your POS or processor supports QR payments, then open the provider’s dashboard to generate and display a code for customers.

Here is the same path in practical steps.

1. Check what you already have. Ask your processor or POS provider whether it supports payment QR codes, payment links and text to pay. Many modern systems do, and embedded payment collection shows how payments can sit inside the tools you already use.
2. Pick static or dynamic. Use dynamic codes for variable totals. Use static codes for fixed prices or tips.
3. Generate the code in your dashboard. Create it inside the provider’s system so it ties to your merchant account. A code made in a free generator that points to a random page will not move money to you.
4. Test it yourself. Scan it from an iPhone and an Android phone, then run a small live payment to confirm funds reach your account.
5. Place it with care. Put it at eye level in a spot staff can see. Add your business name and a short line such as “Scan to pay.”
6. Train your team. Staff should know how to help a customer who cannot scan, and what to do if a code looks damaged.
7. Reconcile daily. Match payments in your dashboard to your sales report.

If you are choosing hardware too, our POS systems overview lists the terminals and platforms we support, including Clover and Square.

What does it cost to accept QR code payments?

Most QR payment setups do not charge a separate monthly fee for the code itself. You pay the cost of processing the card or wallet payment behind it.

That means the real question is your processing structure, not the QR code. Your total cost depends on your pricing model, your card mix, your average ticket and any gateway or software fees.

Three common pricing models apply:

• Flat rate. One percentage plus a fixed fee per transaction. Easy to predict.
• Interchange-plus. The card networks’ wholesale cost plus a stated markup. Often more efficient at higher volume.
• Dual pricing or cash discount. Customers see a cash price and a card price, which offsets processing fees. Our dual pricing program explains how it works.

Before you sign anything, ask for every line item in writing: the processing rate, gateway fees, monthly minimums, statement fees and equipment terms. We promise transparent pricing with no hidden surcharges, and we publish fees where we can. For example, our gateway with eCheck plan is listed at $25 per month. ACH returns and rejects carry flat fees, listed on that page.

For card processing and POS pricing, we quote by business type and volume. Our merchant services page outlines the Clover Flat Rate and interchange-plus options.

Keeping QR code payments safe

QR code payments are generally safe when you use a trusted processor and follow good practice. The risk is mostly about tampering. The U.S. Chamber notes that fake or altered codes can send customers to malicious websites.

The common trick is a sticker placed over your real code. A customer scans it, lands on a lookalike page and pays a stranger. This is sometimes called quishing.

The FTC has also warned that a QR code on an unexpected package can lead to a phishing site that steals personal information or installs malware.

What you can do

• Use dynamic codes wherever you can, so each code is tied to one sale.
• Inspect printed codes daily. Run a finger over each one to check for stickers, and replace damaged signage.
• Keep codes behind the counter or on a screen your staff controls when possible.
• Use a PCI DSS compliant platform. The U.S. Payments Forum says processing platforms should meet PCI DSS requirements to encrypt financial data in transit and at rest.
• Show your brand on the payment page so customers recognize where they land.
• Tell customers what to expect, such as the name that will appear on the payment screen.

The same Payments Forum paper cautions that open-standard QR implementations can be more exposed if strong validation controls are missing. That is a reason to choose a provider that validates codes and transactions, not a reason to avoid QR.

For a deeper look at how the pieces of the payment chain differ, see our explainer on payment gateway vs processor. Cafes that use QR for menus and payments can also look at QR codes in cafe settings for ideas on keeping customer-facing codes tidy.

QR codes vs tap to pay

QR checkout and tap to pay solve different problems. The U.S. Payments Forum notes that QR codes work across smartphones without needing NFC hardware, though they lack the one-tap feel of NFC payments and often take more steps.

In practice, you do not have to choose one.

• Use tap and chip at the counter, where speed matters most.
• Use QR at the table, on the invoice or at a pop-up, where you want no extra hardware.
• Use text to pay when the customer is remote.
• Use embedded checkout online, where the buyer is already on your page.

A good setup lets all four write to the same merchant account and the same reports. That is the point of a unified platform.

Embedded payments: QR and card-not-present checkout inside your software

Embedded payments mean checkout happens inside the software where the sale begins. A customer books, orders or receives an invoice and pays on the same page or message. No redirect, no separate payment tool.

This matters for QR and text to pay because both are card-not-present flows. The payment link or code leads to a hosted page that connects to a gateway. If your software connects through open APIs, any tool can generate that link or code.

Merchant Solutions Corp has open APIs, so we can connect to a wide range of software and process card-not-present transactions.

MSC Payments for HighLevel

We are building MSC Payments as a payment integration for eCommerce and the HighLevel CRM. It is designed to give agencies and their clients another way to accept payments directly inside the HighLevel ecosystem.

Instead of putting every merchant on the same default processor, MSC Payments is designed to connect HighLevel to a broader merchant-services infrastructure.

The intended workflow is short:

1. An agency installs Merchant Solutions Payments in a HighLevel sub-account.
2. The agency connects the merchant’s payment account.
3. The merchant processes payments through invoices, order forms and payment links, with the option to refer other businesses to MSC Payments.

For agencies, this means more flexibility and more control. It also lets you turn payment processing into another service you offer clients.

Because MSC Payments is still being built, contact us for current availability before you promise it to a client. Our eCommerce payments page covers the online side today.

Why a choice of processor matters

A merchant account is not one-size-fits-all. A restaurant, a dental office, a smoke shop and a peptide clinic each have different risk profiles, volumes and ticket sizes.

When the payment layer connects to many merchant accounts, the merchant gets pricing and underwriting that fit the business. That includes specialty and high-risk industries, which we support.

Our perspective

We see the same pattern with business owners every week. They add a QR code or a text link because customers ask for it, and they discover the code is the easy part.

The harder part is what sits behind it: the merchant account, the pricing model, the gateway and the reports. If those pieces do not connect, the owner ends up reconciling three dashboards.

That is why we start with the merchant account and build outward. Our open APIs let software connect to a single payment setup. Our hardware programs, including $0 upfront options, mean you can add terminals without a large first bill. Dual pricing helps offset processing fees, and our onboarding is designed to be fast.

For agencies, the same thinking applies. A client should not have to change their whole business to fit one processor. With MSC Payments, we are building a way to bring a broader merchant-services setup into the HighLevel workflow your clients already use.

If you take only one thing from this guide, make it this: choose the payment partner first, then the QR code. The code is only as strong as the account behind it.

Jonathan

Get QR, text and card payments on one account

Merchant Solutions Corp is a nationwide payment processing and POS provider serving restaurants, retail and service businesses across the US and Canada. We offer credit card and ACH processing, POS systems including Clover and Square, mobile terminals, online ordering, kiosks and dual pricing.

If you want one setup for in-person, online and remote payments, start with our payment processing services and tell us how your customers pay today. We will help you match the right terminal, gateway and pricing model to your business.

FAQ

How do I make a QR code for payments?

Generate it from your payment provider’s dashboard or POS, not from a general-purpose code generator. That keeps the code tied to your merchant account. Choose a dynamic code for variable totals or a static code for fixed prices, then test a small live payment before you display it.

What is the difference between a merchant QR code and a regular QR code?

A merchant QR code starts a payment. A regular code usually opens a web page such as a menu. Payment codes are often opened in an authenticated banking or wallet app, which can add security.

Is QR payment safe?

It is generally safe with a trusted, PCI DSS compliant processor. The main risk is a fake sticker placed over a real code. Use dynamic codes, check printed signage daily and keep codes where staff can see them.

Do I have to pay a monthly fee for a QR code?

Often the code itself has no separate fee. You pay the processing costs on each payment, and some providers add gateway or software fees. Ask for every fee in writing before you sign.

How does pay by text work?

You send a secure payment link to the customer’s phone by SMS, with their permission. They tap it, review the amount and pay on a hosted page. The payment is recorded against the invoice or order in your system.

Sources

• A Guide To QR Code Payments, U.S. Chamber of Commerce
• New X9 Standard for Payment QR Codes and Instant Payments, Federal Reserve Financial Services
• FAQ: QR Codes, U.S. Payments Forum
• Mobile and Digital Wallets: U.S. Landscape and Strategic Considerations, U.S. Payments Forum
• Mobile and Digital Wallets: U.S. Landscape, 2025 update, U.S. Payments Forum
• Only scammers demand utility payments in cryptocurrency, FTC
• Scam alert: QR code on an unexpected package, FTC

Recommended

• Retail Payment Processing Guide
• CBD Payment Processing Guide 2026

This article provides general educational information and does not constitute legal or regulatory advice. Laws, card-network rules, and processor requirements may change. Businesses should verify the requirements that apply to their location, industry, processor, and payment program before implementing any payment or pricing practice.