Stripe Payment Link QR codes — card checkout on a poster

The mechanism

Stripe Payment Links are hosted checkout pages created from the Stripe dashboard without code: pick a product and price (or allow a customer-chosen amount), get a stable URL of the buy.stripe.com/... form. Stripe offers a QR download for each link, or you take the URL into the URL tool and control the output yourself — size, error correction, SVG for print. Either way the QR simply contains the URL; there is nothing payment-specific in the code, which you can confirm by decoding it with /validate.

The payer's flow: scan, land on the hosted checkout, pay by card or wallet (Apple Pay, Google Pay and local methods where enabled), done. No app requirement beyond a browser.

When this beats a payments-scheme QR

The schemes in this cluster — UPI, PIX, EPC, PayNow — are domestic bank rails. A Payment Link QR earns its place where those don't reach:

• Card-first markets. The US and UK have no national merchant-presented QR standard; a checkout URL is the practical "scan to pay" there, and unlike Venmo or Cash App codes it is not locked to one app's user base.
• International customers. A tourist cannot pay your PIX or EPC code, but their Visa works on a hosted checkout in their own currency.
• Card-native features — instalments, subscriptions, buyer-familiar checkout, receipts — none of which a bank-transfer QR provides.

And when it loses: fees. A bank-rail transfer costs the merchant nothing or nearly nothing; card processing takes a percentage plus a fixed fee of every transaction. On small-ticket domestic sales in a UPI/PIX/SEPA market, the local rail keeps the whole margin — use the scheme QR there and reserve the Payment Link for the customers the scheme cannot serve. Take current pricing from Stripe's published rates, not from anyone's summary.

The quasi-dynamic property — and the trap

A Payment Link QR has a property static scheme codes lack: the URL is stable while what sits behind it is editable. Change the price, swap the product, toggle quantities in the dashboard — every printed code now sells the new thing. That is most of what people want from a dynamic QR platform, without a QR subscription.

The same indirection is the trap. Deactivate the link and every printed code dead-ends on an error page — there is no redirect-to-somewhere-else, only off. A code on a thousand flyers is a commitment to keep that link live; treat deactivation as a decision about physical stock, not dashboard housekeeping. This is the general what-happens-when-the-service-stops problem in miniature: your code's meaning lives on infrastructure you rent.

Deployment notes

Standard print discipline applies: ≥ 4–5 cm at counter or poster-passing distance (check with the size calculator), quiet zone intact, and a short human-readable line under the code saying what it sells — a bare "scan to pay" QR invites justified suspicion. Test the full journey on a real phone — scan, checkout, confirmation — before printing, and once more after any dashboard edit, because the printed code will happily deliver whatever the link now points to.

FAQ

How do I turn a Stripe Payment Link into a QR code?

Create the link in the Stripe dashboard, then either use Stripe's QR download or generate a code from the URL with any QR tool. The code contains only the URL — print it at 4-5 cm or larger with a clear quiet zone.

Is a Payment Link QR better than a UPI or PIX code?

For domestic customers on a free instant rail, no — card fees take a cut the bank rail would not. It wins for card-first markets, international customers, and features like subscriptions that bank-transfer QRs lack.

Can I change what a printed Payment Link QR sells?

Yes — the URL stays constant while you edit price and product behind it, which is the main dynamic-like benefit. But deactivating the link kills every printed code outright, so deactivation is a physical-stock decision.

Does the customer need an app to pay?

No — the link opens a hosted checkout in the browser, taking cards and wallets like Apple Pay and Google Pay. That browser-only flow is exactly why it suits mixed and international audiences.