UPI changed how India pays, and design studios adopted it in the laziest possible way: the founder's personal QR code on WhatsApp. Client owes ₹80,000 for the drawing milestone? "Scan this, sir." The money arrives in the founder's personal account, mixed with dinner splits and cab fares, with a transaction note that says nothing, and three months later the accountant is playing detective across two bank statements and a UPI app's transaction history. UPI itself is brilliant for studio collections, instant, effectively free, and every client from a Gurgaon CEO to a Nashik homeowner knows how to use it. The problem is collecting it naked, disconnected from your invoices and your entity. Let me show you how studios should actually run UPI collection, including the limits that matter at interior-project ticket sizes.
Why UPI deserves to be your primary rail
Start with what UPI gets right for a studio. It's instant, the client pays in the meeting, not "by Friday." It's effectively free at the point of use for the payer, and for merchants, person-to-merchant UPI carries zero MDR on standard transactions under current policy, which matters enormously when your milestones are lakhs, because the roughly 2% that cards cost would be ₹8,000 on a ₹4 lakh milestone. And adoption friction is zero: you will never have to teach a client how to pay by UPI, which is not true of netbanking flows or card forms.
For the fee comparison across methods and the broader gateway landscape, I've written choosing a payment gateway for your studio as the companion piece; this post is about doing the UPI part properly.
The limits you'll actually hit
UPI has per-transaction and daily caps, and interior billing sizes hit them regularly, so plan around them instead of discovering them mid-collection:
| Limit type | Broad current shape | What it means for you |
|---|---|---|
| Standard per-transaction | ₹1 lakh for most P2P/P2M payments | A ₹3 lakh milestone won't go in one standard push |
| Enhanced categories | Up to ₹2 lakh, and ₹5 lakh for select categories | Select verified-merchant categories get higher caps |
| Per-bank daily caps | Banks set their own daily limits | The client's bank may cap below the UPI ceiling |
| App-level limits | Apps may add their own caps and counts | Same client, different app, different limit |
I'm keeping figures broad deliberately because NPCI revises limits by category over time, but the operational conclusions are stable. First, structure milestone requests knowing a standard UPI push caps around ₹1 lakh, so a ₹3 lakh milestone either goes as a gateway-backed UPI collect (merchant flows can access higher category limits) or as planned multiple payments, agreed upfront rather than improvised in an awkward chat. Second, the client's own bank and app limits are the real ceiling, so when a large payment fails, it's usually their daily cap, not your setup, and knowing that saves an embarrassed hour. Third, for genuinely large advances, NEFT/RTGS remains the right rail, and your collection system should present it as a clean option alongside UPI, not as a fallback scramble.
Personal QR versus proper collection: the real difference
Here's the heart of it. The personal QR habit has four costs that stay invisible until they bite:
Reconciliation blindness. A bare UPI credit says "received ₹80,000 from PRIYA S." Which project? Which invoice? Advance or milestone? Multiply by forty payments a quarter and you've built a puzzle nobody will solve correctly, and the bookkeeping routine that should take an hour takes a weekend.
Entity mess. Business income landing in a personal account undermines the clean separation your current account exists for, complicates GST reporting, and looks amateur to corporate clients whose finance teams need to pay "Studio Meraki Design LLP," not a personal handle.
No receipt trail. Clients paying lakhs deserve receipts issued against documents. Screenshots of UPI success pages are not receipts, and they don't adjust advances into invoices.
No leverage. A payment request tied to an approved document gets paid faster than a QR floating in a chat, because the client sees exactly what they're paying for and what happens next.
The fix is UPI through merchant collection tied to your billing: the client gets a payment link or UPI collect request generated from the invoice, pays with the same two taps they love, and the money lands in the studio's current account already matched to the document, with the receipt issued automatically.
The flow that makes "payment done?" extinct
Walk through what collection looks like when UPI is wired into the studio's workflow, because this is the version I built Designa around. The client approves the mood board and quote in their branded portal (unlimited free client logins, so the spouse who actually controls the budget sees everything too). The approved quote becomes a compliant GST invoice in one click. The invoice goes out carrying a Razorpay payment link where UPI is front and centre. The client pays from their phone in the time it takes you to sip your chai, and the payment reconciles against that invoice automatically, receipt issued, project money trail updated, org ledger updated. Month-end, it's all synced to Tally or Zoho Books, so your accountant sees clean, matched entries instead of a UPI archaeology assignment.
Notice what disappeared: the follow-up message, the screenshot, the manual receipt, the matching, the personal account. Not because anyone got more disciplined, but because the flow made the sloppy version impossible. That's the standard you should hold any studio tool to, and it's one of the criteria I'd push you to test in the studio software buyer's guide for India: don't ask whether a tool "supports UPI," ask whether a payment can arrive unmatched. If it can, you've just bought yourself a reconciliation hobby.
Moving your studio to proper UPI collection
- Stop sharing personal QR codes for business payments, from today
- Route UPI through merchant collection into the studio current account
- Generate payment requests from invoices, never as bare requests
- Present NEFT/RTGS cleanly for amounts above practical UPI limits
- Agree large-milestone payment structure upfront, knowing per-transaction caps
- Issue receipts automatically against documents, adjust advances into invoices
- Reconcile weekly, which takes minutes when every credit arrives pre-matched
Speed is a system property
One more reframe before you go change things. Studios talk about payment speed as a client-quality issue ("my clients always delay"), but across studios I've watched, collection speed tracks the studio's system more than the client's character. Invoices that arrive promptly after approved milestones, carrying working payment links, against documents the client already saw and approved in a portal, get paid in days. Invoices that arrive late, as PDFs, with bank details to type, get paid in "next week, boss." The client is the same person in both cases; the system is the variable, and the full set of levers is in how to collect payments faster in a studio.
So: merchant UPI, tied to invoices, into the current account, receipts automatic, books synced. If you'd rather switch that on than assemble it, Designa runs the whole loop inside one connected workspace, at one flat founding price for the whole studio, billed in rupees, and I've explained how the pricing works without per-seat surprises. Try the collection flow end to end at demo.designa.work, or see the founding offer at go.designa.work, and retire the personal QR with honours.
Frequently asked questions
Can interior design clients pay large amounts by UPI?
Yes, within limits. Standard UPI transactions cap around ₹1 lakh, with higher caps for select merchant categories, and the client's own bank and app daily limits also apply. For large milestones, use gateway-backed UPI collect or agree a structured set of payments, and keep NEFT/RTGS as the clean rail for very large amounts.
Are there charges on UPI payments for my studio?
Standard person-to-merchant UPI transactions carry zero MDR under current policy, which makes UPI dramatically cheaper than cards at interior-project ticket sizes. Check your gateway's plan for any platform fees.
What's wrong with using my personal UPI QR for client payments?
Four things: payments arrive unmatched to any invoice, business income mixes into your personal account, no proper receipt trail exists, and it reads as amateur to corporate clients. Merchant collection tied to invoices fixes all four.
How do I connect UPI payments to my GST invoices?
Generate payment links from the invoice itself through a gateway like Razorpay, so every payment carries the invoice reference and reconciles automatically. In Designa, the approved quote becomes the GST invoice and the link rides on it, with receipts issued and books synced to Tally or Zoho.
Why do clients pay some studios faster than others?
Collection speed mostly reflects the studio's system, not client character. Prompt invoices against portal-approved milestones, carrying working payment links, get paid in days; late PDFs with bank details to type get pushed to next week.