Somebody signs up for Razorpay, discovers payment links, and asks the obvious question: “I can just create a link in the dashboard and WhatsApp it to my customer. Why would I ever pay a developer to ‘integrate’ anything?”
It’s a fair question, and most developers answer it badly, because the honest answer costs them work: for a lot of businesses, payment links are genuinely enough. But there’s a line, and businesses cross it later than they should — usually after months of manual work that software should have been doing. This post is about where that line is.
What payment links actually are
A payment link is a checkout page Razorpay hosts for you. You create it in the dashboard (or their app), set an amount and description, and share the URL — WhatsApp, SMS, email, anywhere. The customer taps it, pays by UPI or card, you get notified. Fees are the standard gateway charges (typically around 2% + GST; UPI can be lower depending on your plan).
No website needed. No developer needed. Working in five minutes.
For a tutor collecting monthly fees, a boutique taking orders on Instagram DMs, a consultant invoicing a handful of clients — this is the right tool, full stop. If someone quotes you ₹50,000 to “integrate payments” for that use case, walk away.
Where links quietly start costing you
The problem isn’t the links. It’s everything around them that stays manual. Three signs you’ve crossed the line:
1. You’ve become the software. Someone pays → you check the dashboard → you match the payment to an order in your head or a notebook → you confirm on WhatsApp → you update an Excel sheet. That’s a payment workflow, and you’re executing it by hand, per payment, forever. At five payments a day it’s fine. At fifty it’s a part-time job you didn’t hire for.
2. You can’t answer “what is this payment for?” Links capture an amount, not context. Which order? Which size, which delivery slot, which of the three customers named Priya? When the payment arrives detached from its details, reconciliation becomes detective work. (This gets worse when money arrives from multiple sources — I wrote about solving exactly that with webhook-based source attribution.)
3. Anything needs to happen automatically after payment. A ticket that must be issued, stock that must decrease, a receipt that must be emailed, an account that must be activated. The moment “payment received” needs to trigger something, a hosted link can’t help you — there’s no system on your side listening.
What integration actually gets you
A full integration means checkout happens on your website or app, and — the part that matters — your system hears about every payment the instant it happens, through webhooks, and acts on it:
- Customer picks a product/seat/date on your site, price computed live — no “please don’t use this link twice” instructions
- Payment verified server-side (not “customer sent a screenshot”)
- Receipt/confirmation sent automatically, always identical, in seconds
- Your records update themselves — no Excel, no evening reconciliation
- Every payment carries its full context: what it’s for, who from, which campaign
On the SikhAid NGO platform, this is the difference between “donations arrive in the account” and “every donation is verified, receipted, recorded, and attributed to its campaign — with no human in the loop.”
Cost-wise, payments integration lands in my Tier 2 bracket (₹20,000–₹40,000 as part of a build, one-time), and the gateway’s per-transaction fees are the same as with links. You’re not paying for the payments — you’re paying to delete the manual workflow around them.
The decision, as a rule of thumb
| Your situation | Use |
|---|---|
| Few payments a week, each personally discussed | Links — you’re done, enjoy |
| Fixed catalogue, growing volume, WhatsApp-driven sales | Links now, plan the build for when volume hurts |
| Anything must happen automatically after payment | Integration |
| Payments from multiple campaigns/sources into one account | Integration with source tracking |
| Selling inventory that can clash (seats, slots, stock) | Integration — links can oversell; your system must be the referee |
One more honest note: this isn’t either/or forever. Plenty of my clients keep using payment links for edge cases — a custom order, an old customer who just wants a link — alongside an integrated flow that handles the regular volume. The gateway is the same; only the plumbing differs.
Frequently asked questions
Are Razorpay payment links free?
Creating and sharing links is free; you pay the standard transaction fee on each payment (typically ~2% + GST, less for UPI on some plans). A custom integration pays the same per-transaction fees — the difference is what happens around the payment.
Can payment links work without a website?
Yes — that’s their main superpower. Dashboard → create link → share on WhatsApp. For very small volumes this is the correct, zero-cost answer.
What does a payment gateway integration cost in India?
As part of a custom build, payment integration with verification, automatic receipts, and record-keeping typically falls in the ₹20,000–₹40,000 one-time range depending on what happens after payment. No monthly fees to the developer; you own the code.
Can a payment link trigger automatic actions, like sending a ticket?
Not by itself. Automation needs a system on your side listening for payment events (webhooks) — which is exactly what an integration is. If “payment received” must cause anything to happen automatically, you need the integration.
We already take payments through links — can the manual work be automated later?
Yes, and it’s a common path: keep your Razorpay account, add a proper integration on top. Your payment history, settlements, and account stay exactly as they are.
Drowning in dashboard-checking and Excel reconciliation? Describe your payment flow and I’ll tell you honestly whether links are still enough — and a fixed quote if they’re not. Get in touch →
