UPI QR Code Generator

Q: Does this work with GPay, PhonePe and Paytm?

Yes, all of them. The code uses the upi:// scheme from the NPCI specification rather than any single provider's proprietary format, and every UPI-compatible app in India registers to handle that scheme. Whichever app the payer has set as default will open.

Q: Is it safe to print my UPI ID on a public code?

Yes. A UPI ID is a receiving address, like a bank account number on an invoice — knowing it lets someone send you money, not take it. What it does expose you to is spam collect-requests, so keep collect requests disabled in your UPI app, and never approve a request that arrives claiming you need to 'accept' a payment. Money you receive never requires you to approve anything.

Q: Should I set a fixed amount?

Only when the price genuinely cannot vary. Fixed amounts are right for event tickets, a set-price workshop or a specific invoice. For a shop counter, a donation box or anything where the total changes, leave it blank so the payer types the real figure — a pre-filled wrong amount causes more problems than an empty field.

Q: Can I track who paid me through this code?

Not from the code itself. A static UPI QR is the same for everyone who scans it, so your bank statement shows the payer's name and the amount, with no order or invoice reference attached. The transaction note field is fixed at print time and cannot identify individual payers. For per-order reconciliation you need dynamic QR codes from a payment gateway.

Create a UPI payment QR code that opens GPay, PhonePe or Paytm with your details already filled in.

UPI ID (VPA)

The address money is sent to, in the form name@bank.

Payee name

Amount (₹, optional)

Note (optional)

Logo (optional)

Or upload your own

Logo size 18%

PNG, JPG or WebP. SVG is not accepted, since SVG files can carry scripts. Your image is never uploaded — it is composited in your browser.

Appearance

Error correction

Quiet zone 4 modules

Foreground #000000

Background #ffffff

Format

Image size

What It Does

This tool builds a UPI deep link following the NPCI UPI Linking Specification — the same upi://pay format the apps themselves generate. Because it is the open spec rather than any one company's format, the resulting code opens in whichever UPI app the payer has installed: GPay, PhonePe, Paytm, BHIM, or their bank's own app. You choose whether the amount is fixed or left for the payer to type.

When to Use It

You run a stall or small shop and want one printed code at the counter instead of reading out your UPI ID all day.
You are selling a fixed-price item — a ticket, a workshop seat, a set menu — and want the amount locked so nobody underpays by mistake.
You are collecting money for something informal, like a group gift or a society subscription, and want a code to drop into a WhatsApp group.
You invoice clients and want a payment code on the PDF that saves them copying an ID across apps.

Worked Examples

Shop counter — payer enters the amount

No amount set, which is right for a till where the total changes with every customer. The analysis confirms the payer will type their own figure.

Fixed-price ticket — ₹499

The amount is locked, so nobody underpays. The analysis states this explicitly, because a locked amount on the wrong code is the mistake that costs money.

Malformed UPI ID

Missing the @ that separates the name from the bank handle. A wrong VPA fails silently at the payer's end, so the format check exists to catch it before the code is printed and mounted.

Common Mistakes

Locking the amount on a shop counter code. A fixed amount is right for a ticket and wrong for a till: every customer then has to notice the pre-filled figure is wrong and edit it, and the ones who do not will underpay or overpay. Leave the amount blank for anything where the total varies.
Leaving the payee name empty. The payer sees your raw UPI ID on the confirmation screen instead of a business name, which looks like a scam at a counter and gets payments abandoned.
Typing the UPI ID from memory. A wrong-but-valid VPA does not error — it either fails at the payer's end or, worse, pays someone else. Copy it from your UPI app and test the printed code with a one-rupee transfer before it goes up.
Expecting a payment confirmation from the code. A static UPI QR carries no order reference, so nothing links a payment back to a specific customer or invoice. If you need reconciliation, you need a payment gateway with dynamic codes, not a printed one.

Features

Follows the NPCI UPI Linking Specification

Works with GPay

PhonePe

Paytm

BHIM and bank apps

Optional fixed amount or payer-entered amount

Optional transaction note

VPA format check before you print

Download as PNG

SVG

PDF or JPEG

Nothing sent to any server

How to Use

1. Enter your UPI ID exactly as your app shows it, in the form name@bank. 2. Add the payee name that should appear on the payer's confirmation screen. 3. Leave the amount blank for a counter code, or set it for a fixed-price item. 4. Read the analysis, download, and test the printed code with a small real payment before using it.

Frequently Asked Questions

Does this work with GPay, PhonePe and Paytm?

Is it safe to print my UPI ID on a public code?

Should I set a fixed amount?

Can I track who paid me through this code?

Embed this UPI QR Code Generator

Paste this snippet into your site to embed the tool.

<iframe src="https://webtoolworld.com/embed/upi-qr-code-generator" style="width:100%;min-height:560px;border:0" loading="lazy" title="UPI QR Code Generator"></iframe>
<p style="font-size:12px;margin-top:6px"><a href="https://webtoolworld.com/upi-qr-code-generator">UPI QR Code Generator</a> by WebToolWorld</p>

Everything runs in your browser. Nothing you type here is uploaded to our servers, and no code you make is stored or tracked. Brand marks in the logo library identify third-party platforms and remain the trademarks of their respective owners; you are responsible for having permission to use them. Always test a printed code with a real phone, at the distance people will actually stand, before committing to a print run.