DEV Community

Akhil Baraik for Crework Tech

Posted on

Adding Online Payments to Your Business Website: What to Sort Out Before a Developer Plugs In the Gateway

"Can you just add a pay button?" is one of the most common requests I hear from business owners. The button itself is the easy part. What usually slows things down, or causes trouble a few weeks after launch, is everything around it: the paperwork, the website pages a payment provider expects to see, what happens when a payment fails, and who handles refunds.

If you are planning to take payments on your website, whether for orders, bookings, fees or deposits, here is what I'd suggest sorting out first.

Be clear about what you are actually collecting

Start by writing down, in one or two lines, what a customer pays for and when. For example:

  • full payment for a product before it ships
  • an advance or deposit to confirm a booking, with the balance paid later
  • fixed fees, such as a course or a consultation
  • a monthly or yearly subscription

Each of these needs slightly different handling. A deposit needs a way to record the balance due. A subscription needs recurring billing and a way to cancel. A one-off product payment needs stock and shipping to update once the payment succeeds. Telling your developer this up front saves rework later.

Get the business paperwork ready

Payment gateways in India have to verify the business before they let you accept live payments. The exact list varies by provider and by business type, but expect to be asked for things like your PAN, bank account details in the business's name, address proof and some proof that the business is registered. Have these ready, in the business's name, before the build starts.

Two practical points:

  • Open the gateway account in the business's name, not your developer's. The money, the dashboard and the customer data should belong to you. Your developer only needs API keys, ideally test keys first.
  • Keep the login with someone in the business. If the person who set it up leaves, you should still be able to see payments, issue refunds and download reports.

Put the right pages on your website

Payment providers often review your website before approving a live account. They want to see that it is a real business that tells customers what they are buying and what happens if something goes wrong. At a minimum, make sure your site clearly shows:

  • what you sell, with prices or a clear way to get a price
  • your contact details: phone, email and address
  • terms and conditions
  • a privacy policy
  • a refund and cancellation policy
  • shipping or delivery details, if you deliver anything

These pages should describe how your business actually works, not a copied template. If your refund policy says "refunds within 7 days" but nobody in the business knows that, it will cause problems the first time a customer asks.

Decide what happens after someone pays

This is the part most often left vague. A payment is not finished when the money moves. Decide:

  • What the customer sees. A clear confirmation page with an order or booking number, and an email or SMS receipt.
  • Who in your team gets notified. An email, a WhatsApp alert or a dashboard entry, so someone can act on it.
  • What updates automatically. Stock levels, a booking calendar or an order status.
  • Where the record lives. Payment ID, amount, date and customer details should be stored in your own system, not only in the gateway dashboard.

A good developer will confirm payments on the server side using the gateway's verification or webhook, rather than trusting whatever the customer's browser reports. You don't need to know how that works, but it is worth asking, "How do we confirm a payment really succeeded?"

Plan for failed and pending payments

Not every payment goes through cleanly. A UPI app may time out, a bank may decline a card, or the customer may close the window halfway. Sometimes a payment shows as pending and only succeeds a little later.

Ask your developer how the site handles each case:

  • If a payment fails, can the customer simply try again without filling everything in a second time?
  • If money is deducted but the site shows an error, how will you find and match that payment?
  • If a payment is pending, does the order wait, or is it cancelled?

Agree on a simple daily or weekly habit of matching gateway payments against orders, at least for the first few months.

Make refunds a process, not a scramble

Refunds will happen. Decide in advance who can approve one, whether it is issued from the gateway dashboard or from your own admin panel, and how the customer is told. Keep a note of every refund with the reason. It helps with accounts and shows you if one product or service keeps causing problems.

Test everything before going live

Every major gateway offers a test mode. Before switching to live keys, run through at least these:

  1. a successful payment by UPI and by card
  2. a failed payment
  3. a customer closing the window mid-payment
  4. a refund, full and partial if you offer partial refunds
  5. the confirmation email or SMS, checked on a phone
  6. the notification your team receives

Then make one small real payment yourself after going live, and refund it. It is the simplest way to be sure the whole chain works.

Keep it simple at the start

You don't need every payment option on day one. Most small businesses do well starting with one reliable gateway that supports UPI, cards and net banking, a clear checkout, and a solid confirmation and refund process. Instalments, wallets and international cards can come later if customers ask for them.

If you are planning a new website, or adding payments to the one you have, and want help with the build and the gateway setup, you can read about our approach to website development in Ranchi. Either way, sort out the points above before anyone writes code. They decide whether online payments make your life easier or give you a new set of problems.


Akhil Baraik is the founder of Crework Tech, an IT and digital marketing agency in Ranchi, India, that has been building websites, apps and software for businesses for 7+ years.

Top comments (1)

Collapse
 
alexshev profile image
Alex Shev •

The handoff before the gateway integration is often the real project. I’d include a plain-language payment state diagram—authorized, captured, failed, refunded, disputed—and decide which system owns each transition. It prevents the website, gateway, and accounting tool from quietly disagreeing later.