Payment QR Code Generator for Scan-to-Pay Checkouts

How a payment QR code actually works

A payment QR code does not move money by itself. What it stores is a pointer — usually a URL to a hosted checkout page, or a payment URI such as a UPI string that a banking app knows how to open. The scan takes the customer to a page or app screen where the real payment happens, secured by the payment provider rather than by the code.

That distinction matters when you are choosing what to encode. A link to a Stripe payment link or a PayPal.Me address with an amount appended (for example a URL ending in /25) opens a checkout with the amount already set, so the customer only confirms. A bare profile link opens an empty form and asks them to type the amount themselves, which is where most abandoned scan-to-pay attempts happen.

Because the code is static, whatever you encode is fixed once printed. The reliable pattern is to encode a URL you control the destination of — your own checkout page or a provider link you can edit — so you can change the price, currency or provider later without reprinting anything.

What to encode for each payment provider

PayPal: use a PayPal.Me link, optionally with the amount and currency in the path so the checkout opens pre-filled. Stripe: create a Payment Link in the Stripe dashboard and encode that URL — it supports fixed or customer-chosen amounts and works on any phone browser without an app.

UPI (India): encode the full UPI URI rather than a web address. It begins with upi://pay? and carries the payee address, payee name and, optionally, the amount and a transaction note. Banking apps recognise the scheme directly, which is why a UPI code opens the payment sheet instead of a browser.

Venmo and Cash App: both expose a shareable profile URL that opens the app on a phone. These generally cannot carry a fixed amount reliably across platforms, so pair the code with a printed amount next to it. Wise, Revolut and most invoicing tools (Xero, QuickBooks, Zoho) generate a per-invoice payment URL — that is the string to encode, one code per invoice.

Creating your payment QR code step by step

1. Generate the payment link first, in your provider's dashboard, and open it on a phone to confirm it loads the checkout you expect. 2. Paste that exact string into QRPixel — including https:// for web links or the upi:// prefix for UPI. 3. Check the live preview renders and is not unusually dense; if it is, shorten the link. 4. Style the code with your brand colours, keeping strong contrast between the pattern and the background.

5. Add your logo or your payment provider's mark to the centre if you want the code to read as legitimate at a glance — this measurably reduces hesitation on printed material. 6. Export SVG for anything going to a printer and PNG for invoices sent as email attachments. 7. Before it goes out, scan the real printed or on-screen output with two different phones and complete a small test payment to yourself.

Where businesses put payment QR codes

Market stalls and pop-ups use a laminated A5 counter card with the code and the trading name, so customers can pay without the stall holder carrying a card terminal. Tradespeople print the code directly on the paper invoice, which shortens the gap between handing over the job and being paid.

Freelancers add the code to the footer of PDF invoices, alongside bank details, for clients who prefer card payment. Restaurants and cafes place it on the bill wallet for tips or the full check. Charities and buskers print a large code on a sign, where scan distance rather than density is the main design constraint.

Subscription and course businesses use one code per plan, each pointing at a different pre-priced Stripe link, so the printed material itself acts as the plan selector.

Security: the part most guides skip

Payment QR codes are a known target for tampering. The attack is physically simple: someone sticks their own printed code over yours, and payments quietly go elsewhere. Codes on outdoor signage, parking meters and unattended counters are the usual victims.

Defend against it with the boring measures. Laminate or seal the code so a sticker cannot sit flat over it, place it inside a frame or under acrylic, check unattended codes daily as part of opening routine, and scan your own code regularly — if the destination is not your own checkout, replace the sign immediately.

Print the destination domain in readable text next to the code as well. A customer who sees the URL before scanning is far more likely to notice that the page they land on does not match. Never ask customers to enter card details on a page reached through a code that does not show a padlock and your own domain.

Common mistakes with payment QR codes

Encoding a bare provider profile with no amount, then wondering why customers pay the wrong figure. Encoding a link that only works inside a specific app, so desktop and unsupported phones hit a dead end. Printing at 1.5 cm on a receipt, where the density of a long checkout URL pushes the modules below what a camera can resolve.

Using low-contrast brand colours on a payment code is a particularly expensive mistake — a failed scan at the moment of payment is a lost sale, not just an inconvenience. Keep the pattern dark on a light background, or fully inverted with equally strong contrast, and never place the code over a photograph or gradient.

Finally, do not reuse an invoice-specific code across multiple invoices. If the URL carries an invoice ID or amount, generate a fresh code per invoice; batch tools make this practical for dozens at a time.

Pro tips for higher scan-to-pay conversion

Add a short instruction line under the code — 'Scan to pay by card' — rather than leaving it unlabeled. Ambiguity is the single biggest reason a payment code goes unscanned. Include the amount in large type next to the code even when the checkout is pre-filled; customers verify against it.

For anything sent digitally, put the payment link as tappable text next to the code as well. A customer reading the invoice on the same phone cannot scan their own screen, and a tappable fallback captures that payment instead of losing it.