The fear is sized to your exposure, not to the person — so shrink the exposure and the fear becomes proportionate. Four moves reduce the worst realistic outcome to a modest amount and a few weeks, which is a risk you can take without needing to be certain about anyone.
The fear, stated plainly
You’re about to send money to someone you met three days ago, for something that doesn’t exist yet, with no refund policy and nothing you could enforce.
That’s an accurate description of the transaction. The discomfort isn’t irrational — it’s a correct reading of an arrangement where all the risk sits on one side at the moment of payment.
Complaint records confirm the pattern you’re afraid of exists: advance paid, work begins or doesn’t, replies slow, then stop. What they also show is that recovery is much harder when the payment went to a personal account with no invoice — which tells you exactly where to intervene.
Move 1: Register the domain yourself, first
Before you hire anyone. About ₹700–1,200 a year, ten minutes, any registrar, using your own email.
This is the single most effective thing on this page, and it’s the one most people skip because it doesn’t feel like a payment safeguard. It is. Here’s what it changes:
Without it, a vendor going quiet can mean losing your business name, your email, and every link and card pointing at you. That loss has no ceiling.
With it, the same event costs you an advance. Recoverable, annoying, survivable.
You don’t need to trust anyone for this to work. Do it today, whether or not you’ve chosen a vendor.
Move 2: Keep the advance at 20–30%
Not half. A vendor confident of being paid on delivery doesn’t need half.
This is also standard enough that asking for it isn’t awkward. If someone insists on more, that’s a conversation worth having before paying rather than a term to accept quietly — and their reaction tells you something.
| Advance | If they vanish on a ₹25,000 project |
|---|---|
| 50% | ₹12,500 gone |
| 30% | ₹7,500 gone |
| 20% | ₹5,000 gone |
Same vendor, same risk, very different exposure. The only variable you controlled was one sentence.
Move 3: Tie the rest to stages you can open
Not to dates and not to descriptions. To things you can see on your own phone:
- 30% on confirmation — with written scope and an invoice
- 30% on design approval — a home page you’ve said yes to
- 30% when all pages are viewable on a staging link
- 10% on go-live — after you’ve tested the contact form and received the logins
Two effects. Your exposure at any moment is one stage, not the whole project. And the final instalment is small enough that nobody deadlocks over it at the end — which is a genuine failure mode when the last payment is large.
Move 4: Pay a named firm, against an invoice
Check the account holder name your UPI app displays before you confirm. It takes four seconds and it’s the detail every later claim turns on.
The firm’s name appears — good. A person’s name you’ve been dealing with — common with freelancers; get a written bill and scope. A name you don’t recognise — ask before sending.
Screenshot the confirmation showing that name and keep it with the invoice and the scope message in one folder.
What this adds up to
With all four in place, the worst realistic outcome on a ₹25,000 project is losing ₹7,500 and three weeks, with your domain intact and a documented claim if you want to pursue it.
That’s an ordinary business risk. It’s a completely different object from the open-ended one you were afraid of — and the difference cost you ₹1,000 and four sentences.
What doesn’t help
Paying more for a “safer” vendor. Price is largely uncorrelated with delivery. A higher quote buys presentation, not protection.
Refusing any advance. It filters out vendors with steady work and creates a deadlock at the end. There’s a separate piece on why.
Waiting until you feel confident. You won’t. Projects die in that pause more often than in the build, and the delay costs more than the advance you were protecting.
What to do this week
- Register the domain in your own account today.
- Offer 30%, not more.
- Split the balance across the four stages above.
- Check the account holder name before confirming payment.
- Keep invoice, scope message and payment screenshot in one folder.
If you want it done the certain way
30% advance, stage-linked balance, a small final instalment after you’ve tested the forms, GST invoice, and the domain in your name from day one — all in writing before you pay anything. We’d also tell you to register the domain yourself first, with us or anyone. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- How much advance is safe to pay?
- The moment before you hit “pay”
- Is your website advance “gone money”?
- Personal UPI or company account — does it matter?
FAQ
How do I pay a web developer without risking my money?
Register the domain in your own account first, keep the advance to 20–30%, tie the balance to stages you can open on your phone, and pay a named firm against an invoice. Together those cap the worst outcome at a modest amount.
What’s the safest advance amount for a website?
Twenty to thirty percent. It’s enough to be a serious commitment while limiting your exposure, and it’s standard enough that asking for it isn’t unusual.
Should I check who receives my payment?
Yes — your UPI app shows the account holder name. Confirm it matches the firm you contracted with, and screenshot the confirmation. That name is the detail any later claim depends on.
