QR Code for Payment Links (Stripe/PayPal)

Pay-by-QR removes the friction of typing a URL or hunting for a payment button. A customer points a camera at a printed square, a branded checkout opens, and money moves. The catch is that people are rightly cautious about scanning to pay, so the way you build and place the code matters as much as the code itself.

Why a payment link is the safest thing to encode

A QR code is just a container for text, so you never encode raw card data or account numbers. Instead you encode a hosted payment link that your processor creates and controls. Stripe Payment Links, PayPal.Me, and Square checkout links all produce a public URL that opens a real, secured checkout page. That page handles the card entry, receipts, and fraud checks, while the QR only carries the address.

This separation is what makes the workflow safe. If you need to change the price or disable the link, you edit the destination in your dashboard. Encode the checkout, not the payment.

Create the link in your processor first

Build the hosted link before you touch any QR tool:

• In Stripe, open Payment Links, set the product and price, and copy the generated buy.stripe.com URL.
• For PayPal, use PayPal.Me with a fixed amount appended, or a hosted invoice link.
• In Square, create a checkout link or an online payment page for the item.

Open that link on your own phone once. Confirm it shows your business name, the correct currency, and a mobile-friendly checkout. If the page looks bare or generic, add your logo and business name in the processor settings so the customer recognizes who they are paying.

Turn the link into a scannable code

Paste the copied checkout URL into the URL QR code generator and generate the image. Download the SVG version for anything that will be printed, because SVG stays crisp at any size, from a table tent to a large market banner. Keep a PNG on hand only for quick digital sharing, such as a slide or a chat message.

Give the code room to breathe. Leave a clear quiet zone on all four sides, keep strong dark-on-light contrast, and size it for the scan distance. A table sign can be small, but a banner read across a market stall needs to be much larger.

Label the code so people trust it

Trust is the whole game with payments. A bare square with no context looks exactly like a scam, so surround the code with the facts a cautious customer wants:

• The business name, matching the name on the checkout page.
• The exact amount, or a clear note that the total is confirmed on the next screen.
• A specific instruction such as “Scan to pay Rosa’s Bakery” rather than “Scan me.”

When the label, the checkout domain, and the branded page all agree, the customer relaxes and completes the payment. Any mismatch makes them stop.

Where pay-by-QR earns its keep

The format shines wherever a customer is ready to pay but a card reader is awkward or absent:

• Market stalls and pop-up booths, where a printed code beats juggling a terminal.
• Invoices, where a Stripe link and its QR let a client pay from the paper without typing.
• Service businesses taking deposits, so a client scans a card and pays before the appointment.
• In-person counters and “pay by QR” table signs at cafes and food trucks.
• Event merch tables, where each item can carry its own fixed-amount code.

For fixed prices, one link per product or amount keeps the counter fast and error-free. For variable totals, prefer a checkout that asks the customer to confirm the amount, so a single sign stays accurate all day.

The sticker-overlay scam and how to block it

The most common real-world attack on payment QR codes is physical. A scammer prints their own code and pastes it directly over a legitimate one on a parking meter, a market sign, or a restaurant table. Customers scan the overlay and pay the wrong person.

Defend against it on your side:

• Use tamper-evident labels so a peeled or covered code leaves an obvious mark.
• Inspect public codes on a schedule and feel for a second sticker layered on top.
• Print the destination context and business name, so a swapped code that opens a different name gets caught.
• Never obscure who is being paid; transparency is your best fraud alarm.

Because scan-to-pay sits squarely in fraud territory, it is worth reading the deeper walkthrough in Are QR Codes Safe? before you print anything for a public space.

Handling receipts and follow-up

Payments generate paperwork, and QR codes can smooth that too. If clients regularly need an invoice or a receipt sent to your inbox, add a second code built with the Email QR code generator. It opens a pre-addressed draft so a customer can request a receipt without hunting for your address. Keep this code visually separate and clearly labeled so no one confuses it with the payment code.

Test before you print

A payment code that fails in the field costs you a sale and some trust, so test the final artwork, not a draft:

• Scan the exported SVG or a printed proof, not just the on-screen preview.
• Test on both an iPhone and an Android device, since default cameras behave differently.
• Try it over mobile data with Wi-Fi off, because that is how most customers will scan.
• Recheck contrast and size after any resize, recolor, or compression.

If a code passes on paper, on two phones, and on cellular, it is ready for the counter. For a related trust-first playbook, compare your setup against QR Code for Nonprofit Donations, and if this is part of a wider campaign see QR Code for Small Business Marketing.

FAQ

Do I need special software to turn a Stripe or PayPal link into a QR code?

No. Create the hosted payment link inside your processor, copy the full URL, and paste it into a URL QR generator. The QR image simply encodes that link, so anything that opens a checkout page also works as a QR code.

How do customers know the payment QR is really mine and not a scammer’s sticker?

Print your business name and the amount right next to the code, keep the destination on your own or the processor’s known domain, and use tamper-evident labels on public signs so a covered code is obvious at a glance.

Should I make one QR per amount or one generic payment code?

For fixed prices, a link per product or amount removes typing errors at the counter. For variable totals, use a checkout where the customer confirms the amount before paying, which keeps a single code accurate.