UPI payment link generator for Indian businesses.

A UPI payment link is not a webpage. It is a upi://pay deep link — a short instruction that tells whichever UPI app the customer has installed to open a payment screen pre-filled with your details. Nothing is hosted, nothing is stored, and no payment gateway sits in the middle.

The parameters that matter:

• pa — your payee address, meaning your UPI ID such as yourname@okhdfcbank. This is the only genuinely required field.
• pn — payee name, shown to the customer on the confirmation screen. Use your business name exactly as customers know it, because an unfamiliar name is the most common reason a payment gets abandoned at the last step.
• am — the amount. Leave it out and the customer types their own, which is right for donations and wrong for deposits.
• tn — transaction note. Put the booking reference or the service name here so the payment is identifiable in your statement later.
• cu — currency, always INR for UPI.

Because it is a deep link rather than a hosted page, it works from a WhatsApp message, an SMS, a QR code, or a button on your site, and it costs nothing per transaction. The trade-off is that there is no gateway doing reconciliation for you — see the limits section below.

For most Indian service businesses, the highest-value use of a UPI link is not collecting the full bill. It is collecting a small deposit at the moment the booking is made.

No-shows are rarely malicious. Someone books, something else comes up, and there is no cost to simply not turning up. A deposit changes that arithmetic — and the amount matters far less than its existence. ₹100 against a ₹800 haircut is enough to make someone either arrive or call to reschedule, which is the outcome you actually want. You can see the size of that leak in your own numbers with the missed call and no-show calculator.

Practical rules that come up repeatedly:

• Send it inside the same conversation. A deposit link that arrives an hour after the call gets ignored. Sent while the customer is still on WhatsApp, it usually gets paid within a minute.
• Say what it is for and whether it is adjustable against the bill. Ambiguity here causes disputes at the counter.
• Put the booking reference in the note field. Otherwise you will be matching ₹100 credits to names by memory at the end of the week.
• Do not ask for a deposit on a first enquiry call. Ask once the slot and service are agreed, not while the person is still deciding whether to come at all.
• Have a stated refund rule and follow it. One publicised refusal costs more than every deposit you collected that month.

This tool is free and so is the link it makes, but a direct UPI link is genuinely worse than a payment gateway at several things. It is worth knowing which before you build a workflow on it.

There is no automatic confirmation. Nothing tells your system the payment happened. You find out by looking at your bank app or waiting for the customer to send a screenshot. At a handful of deposits a day that is fine; at fifty it is somebody’s job.

Reconciliation is manual. Without the transaction note filled in properly, matching credits to bookings is guesswork. A gateway does this for you and gives you a dashboard.

Refunds are manual too. You send the money back yourself, and there is no linked record tying the refund to the original payment.

Desktop is awkward. A upi:// link needs a UPI app on the same device. On a laptop it typically needs to become a QR code the customer scans with their phone.

App behaviour varies. Different UPI apps handle a pre-filled amount slightly differently, and some intent flows have changed over time. Always test your own link on your own phone before you send it to a customer.

If you need automatic confirmation, reconciliation and refunds, a gateway is the right tool and its fee buys something real. If you need a deposit collected in a WhatsApp conversation at zero cost, a direct link is hard to beat. Most small businesses end up using both. The comparison in detail is in Razorpay Route and our UPI deep linking guide.

We are deliberately not printing a table of transaction limits here, because they differ by bank, by app, by account type and by category, and they change. What we can tell you is which limits exist, so you know what to ask your bank about rather than discovering it at the counter.

• A per-transaction cap. Every UPI account has one, and it is usually the binding constraint for a business collecting a large payment in one go. Deposits are almost never affected; full invoices for high-value services sometimes are.
• A daily cumulative cap. Separate from the per-transaction cap, and separate again from the number of transactions allowed per day. A busy Saturday at a salon collecting fifty deposits can hit a count limit long before a value limit.
• New-account cooling periods. Freshly linked accounts and newly added payees are often restricted for the first day. Worth knowing before you switch your UPI ID the week of a festival.
• Personal versus business accounts. Collecting business receipts into a personal UPI ID works technically and creates problems later — for your accountant, for your GST position, and for anything you might want to reconcile. Ask your bank about a current account and a business VPA before volume grows.
• App-level differences. Some UPI apps present a pre-filled amount as editable, some do not, and behaviour has changed across versions. This is the single most common reason a link behaves differently for a customer than it did in your test.

The practical advice is unglamorous: test your link on your own phone, collect a small deposit rather than a large balance wherever you can, and confirm your caps with your bank before you build a busy day around them.

A payment link is only as good as its timing. The generator above solves the easy half — making a correct link. The half that decides whether you get paid is when it goes out and what happens afterwards.

The sequence that works is short: confirm the service and slot, state the deposit and what it is for, send the link in the same thread, watch for payment, then send a confirmation that names the service, the time and the amount received. If payment has not arrived within a few minutes, one polite nudge — then release the slot rather than holding it indefinitely on an unpaid promise.

Doing that reliably by hand is easy at five bookings a day and impossible at fifty, which is where it stops being a payments problem and becomes a staffing one. Our Payments agent runs that sequence inside the same conversation the booking happened in — the link goes out mid-conversation, the confirmation follows payment, and the slot is released automatically if nothing arrives. There is no commission on what you collect; the money goes to your UPI ID, not through us.

That is the honest boundary of this free tool. It makes a correct link. It cannot send it at the right moment, notice the payment, or chase the ones that do not arrive.