UPI QR Code Generator

UPI QR Code Generator is for static payment workflows where a customer should be able to scan and open a UPI-compatible app with payee details already filled in. It is commonly used for counters, invoices, donation sheets, and small printed payment displays. The page is helpful for generating the payload quickly, but the trust step happens afterward: you still need to test the QR code in real payment apps, confirm the payee details, and remember that a static QR does not adapt automatically if account details or app behavior change later.

Last updated: May 26, 2026

Tool Interface

Generate a static UPI payment QR code for Indian payments.

UPI IDPayee nameAmount

Preview

Enter content to generate a code.

How this tool works

Enter the UPI ID, payee name, and optional amount exactly as they should appear in the payment app.

Generate the QR and copy the payload if you want to verify the final UPI string before download.

Test the code with a real UPI app so the payee name, handle, and optional amount appear correctly before using it for live collection.

Examples

Counter payment card

Print a QR code for a reception desk or market stall so walk-in customers can pay without asking for the UPI handle verbally.

Invoice fallback

Add a static UPI QR to a PDF invoice when you want clients to scan and pay quickly from a phone app.

Visual walkthrough

Preview checkpoint

Payee verification

Before sharing the QR, compare the preview workflow against the exact payee name and UPI ID you expect the payment app to show to the sender.

Preview checkpoint

Live scan check

A complete test should open a real UPI app and show the correct merchant handle, optional amount, and payee confirmation screen before any payment is attempted.

What to verify before using the result

OKVerify the UPI ID and payee name carefully before download because a wrong payment destination is a serious real-world error.

OKScan the QR code in at least one common UPI app to confirm the payment flow opens with the expected details.

OKTreat any amount field cautiously and confirm whether your use case should keep the amount fixed or let the payer enter it manually.

OKReview the printed output before publishing so the code has enough size and margin to scan reliably at a counter or on paper.

Limitations

!This is a static QR workflow, so it does not confirm settlement, expiry, inventory, or order reconciliation on its own.

!Optional fixed amounts are convenient for standard fees, but they are less flexible when the amount changes often.

!A typo in the UPI ID or payee name can send users to the wrong payee or cause payment-app warnings.

Methodology and scope

iBuilds a standard UPI payment payload from the entered payee details and optional amount.

iBest for fixed or semi-fixed payment collection points where users already trust the surrounding context.

FAQ

Is this a static QR code?

Yes. The generated image stores the payload directly, so changing the destination later means generating a new QR image.

What payload does this page encode?

It stores a static UPI payment payload with payee details that a compatible payment app can interpret after scanning.

Why should I test the QR code on a phone first?

Different camera apps and scanner apps can handle payloads differently, so one scan test before printing or publishing catches avoidable mistakes.

What is the biggest real-world failure point?

Assuming all UPI apps will display the exact same payment screen or handle optional fields identically without testing the result first.