Engineering
Your Website Should Take the Payment, Not Just Collect a Phone Number
If people still pay you with a UPI QR and a screenshot, payments will slip. Here is what Arterns builds so a Dehradun or Uttarakhand business can take UPI and card payments on its own website, tied to a booking, order or bill.
Arterns TechnologiesUpdated 6 min read

A lot of websites we are sent in Dehradun look finished, until you ask a simple question: how does someone actually pay?
The answer is often "they call us," or "we send a UPI QR on WhatsApp," or "they screenshot the payment and we tick them off in a diary." That works when you have five payments a week and you are always on your phone. It starts to fail when two screenshots look the same, a payment sits unnoticed in a chat, a parent is trying to pay fees after hours, or a guest wants to hold a room and you are out of network in the hills.
At Arterns we build websites that take the payment, not just the enquiry. This post explains what that looks like for a local business or small brand, what we actually set up, and when it is worth adding payments to a site you already have.
What "taking payments on your website" means, in plain words?
It means a customer can pay you, on a page you control, with UPI or a card, and you both get a clear record of it, without a screenshot passing through a chat.
That might be:
- A deposit to hold a booking, for a clinic appointment, a salon slot, a workshop, a photoshoot or a homestay stay.
- A full payment for a product or a service, from an order on your online store, a course fee, a repair visit, or an invoice you have already raised.
- A simple pay-a-bill page, where a parent, a patient or a retailer opens a link, sees what they owe, and pays it.
The common idea is the same. The website does the taking, confirming and recording. Your team does not have to chase.
Why the "just send a QR" habit starts to cost you
There is nothing wrong with UPI. The problem is the way it is often stitched together by hand.
- You cannot always tell who paid for what. A name in a UPI note is not the same as an order number, a booking or an invoice, and two payments of the same amount on the same day are a headache.
- The slot or the order is not linked to the money. Someone says they have paid, you hold the time, and later you cannot find the payment. Or they do pay, and nobody notices until they follow up.
- People give up after hours. If your only method needs you to send a QR, a late-night customer waits, and sometimes they do not come back.
- Your records are a chat history. That is hard for you, harder for your accountant, and no comfort for a customer who wants a proper receipt.
A website payment does not replace UPI. It uses UPI and cards, but it ties each payment to a person, a booking or an order, and writes it down in one place.
Four examples of what we would build
A clinic, salon or studio. The booking is confirmed only when a deposit (or the full amount) is paid. The customer gets a confirmation at once, and you see the payment next to the appointment, not in a separate chat. This sits naturally with a booking system if you already need one.
A coaching centre or school office. Parents open a fees page, see what is pending, and pay from their phone. Reminders can go out with a link, instead of the office asking each family to "pay on this number and send the screenshot." If you later want parents to also see attendance or reports, that can grow into a customer portal.
A homestay or small hotel in Mussoorie, Rishikesh or elsewhere in Uttarakhand. A guest can pay a booking deposit on your site when they request dates, rather than waiting for you to send a QR after a long WhatsApp exchange. We cover the wider site picture in our homestay website guide; payments are the part that turns an enquiry into a held room.
A shop or D2C brand. The customer adds items, sees delivery charges, and pays before you pack. You get an order with a payment attached, which is a different thing from a voice note that says "send two jars." That checkout is part of the online stores we build.
What we actually set up
We keep this as simple as the rest of the site. A typical project includes:
- A payment page that matches your brand, not a generic third-party look that makes people hesitate.
- UPI and cards, through a trusted Indian payment service, so the money comes into your account with a proper reference.
- A clear yes or no. The customer sees a success page and a receipt. You see the payment against the booking, order or invoice. Failed or dropped payments do not get marked as paid.
- A record you can export. Your team and your accountant can see what came in, without scrolling through WhatsApp.
- The rules you already use. Deposits versus full payment, refunds you approve by hand, or a link that expires if a pending booking is not paid in time.
This is part of our web development work, and of our ecommerce development when the site is a store. We can add it to a site we are building, or, in many cases, to a site you already have, as long as that site is in a state where a payment page can sit safely.
We will not invent a complicated setup you do not need. If all you require is a single "pay this amount" link that you can send to a customer, we can start there, and only go further when you have bookings or a catalogue that needs it.
What we need from you, and what we are careful about
To go live you will need a business bank account and the usual checks the payment service asks for. We guide you through that, but the account and the documents have to be yours. We also keep the wording on the page honest: the amount, what it is for, and what happens if someone cancels, so customers are not surprised.
We do not treat payments as a place to be clever. The page should be short, clear and mobile-friendly, and it should work on a mid-range phone over an ordinary connection. If a payment fails, the person should know what to do next without calling you in a panic.
When it may be too early
If you only take a rare, large payment and you are happy to handle each one in person, a payment page can wait. If your website itself is badly out of date or does not work well on a phone, we would usually fix that first, then add payments, so people are not asked to pay on a page they do not trust.
Thinking about it?
You can keep UPI and still stop running the business from a camera roll of screenshots. A website that takes the payment gives you a cleaner record, fewer missed deposits, and a better experience for the person trying to pay you after hours.
See what we build on our web development and ecommerce development pages, or book a free 30-minute call. Bring an example of how you take payment today, even if it is a QR and a chat thread, and we will tell you what is worth putting on the site first.
Frequently asked questions
Which payment methods can customers use?
On most of the sites we build, customers can pay with UPI and with cards, through a trusted Indian payment service. We set up the methods that make sense for your customers, and we keep the page short and clear on a phone.
Do you hold our customers' money?
No. Payments go to your own account through the payment service, with a proper reference against the booking, order or invoice. We build and look after the website; the money does not pass through Arterns.
Can I add payments to the website I already have?
Often yes, if the current site is in a state where a payment page can sit safely. If the site is badly out of date or awkward on a phone, we may recommend fixing that first, so people are not asked to pay on a page they do not trust.
Is a UPI QR on the website enough?
A QR on the page is still a manual payment. It does not reliably tie the money to a booking, order or bill, and two similar amounts on the same day are easy to mix up. A proper payment page uses UPI, but it confirms and records each payment against the right person and the right item.




