Before a payment provider switches on live payments for your business, someone on their side usually looks at your website. If the site is a half-finished template with no business details, no refund terms and no clear description of what you sell, approval often stalls, and the delay lands on you. For a Pune small business, the fastest route to a live checkout is a website that already shows who you are, what you sell, what it costs, how to reach you and what happens if something goes wrong. This guide, rewritten in 2026 from an earlier version that focused on payment regulation, covers the website side only: the pages to build, the wording that helps, the checkout behaviour to test and the mistakes that cause rejections. It does not give tax, banking or legal advice; the account, KYC and fee questions are for your provider and your accountant.
What Changed in This Guide
An earlier edition of this article tried to explain payment rules and fees. That material goes stale quickly and belongs with your provider and professional advisers, so we have removed it. What stays useful, and what a web developer actually controls, is the website a provider reviews and the checkout a customer uses. Everything below is about building and testing those, and each provider publishes its own current requirements, so always check theirs before you start.
What Providers Typically Look For on Your Website
Requirements differ between providers and change over time, so treat this as a checklist of what is commonly asked, not as any one provider's rules. Before applying, read your chosen provider's current documentation and note what they say about website review.
In general, a reviewer wants to see that:
- The business is real and identifiable. A legal or trading name, address, phone number and email that match what you submit in your application.
- The offering is clear. What you sell, in plain words, with prices or a way to get a quote.
- Customers know the terms. Delivery or service timelines, cancellation and refund terms, and a privacy policy.
- The site works. No dead links, no "coming soon" pages, no broken checkout.
- Nothing prohibited is for sale. Providers publish lists of restricted categories; check yours.
A website that shows these things clearly is easier for a reviewer, and also easier for a first-time customer deciding whether to trust you with their money.
The Pages to Build
Home page
State what you do and where you operate in the first screen. A visitor, or a reviewer, should know within seconds whether this is a bakery in Kothrud, a coaching centre in Kharadi or an online store shipping across India. Link clearly to products or services.
Products or services pages
Give each item a name, a description, a price (or a "from" price with an explanation) and what is included. If prices vary, say how. Avoid vague pages that say "contact us for everything"; a reviewer cannot judge what you are selling and a customer cannot judge the price.
About page
Say who runs the business, how long you have operated, and where you are based. Use real names and real photographs where you can. Do not invent awards, certifications or client names; fabricated claims create more trouble than they solve.
Contact page
Include a working phone number, an email address on your own domain if possible, your postal address and business hours. Add a simple enquiry form, and make sure you actually answer it. Reviewers sometimes test contact details, and customers certainly do. Our guide to enquiry form design covers the details.
Privacy policy
Explain what personal data you collect (name, phone, address, order details), why, who you share it with (your payment provider, courier, email tool), how long you keep it and how a person can ask about it. India's Digital Personal Data Protection Act, 2023 sets rules for processing personal data, so have the policy reviewed by a qualified adviser rather than copying another site's text. Our guide to cookie banners and consent explains the technical side.
Terms and conditions
Cover how orders and bookings work, what you promise, what you do not, and how disputes are handled. Again, take professional advice for your category.
Refund, cancellation and delivery policy
State clearly:
- Whether refunds are offered, in what situations and within how many days.
- How a customer requests one (a form, an email, a phone number).
- How and roughly when a refund reaches them.
- For physical goods, your dispatch time and delivery area; for services, how and when they are delivered.
Write only what you will honour. If you do not offer refunds on a category, say so plainly. Our guide to refund and cancellation policy pages shows the structure for donations, and the same layout works for businesses.
Link all policy pages from the footer of every page, so a reviewer and a customer can find them in one click.
Checkout Behaviour That Customers and Reviewers Notice
Show the total before the last step
No surprises: item prices, shipping, any fees and the final amount, in rupees, visible before payment. Charge exactly what the page showed.
Keep card and bank details off your own pages
Use the provider's hosted checkout or embedded fields so that sensitive payment details go to them, not through your server. Your developer should confirm which integration style is used and what it means for your security responsibilities; see our guide to PCI DSS for Indian ecommerce sites for the concept.
Use HTTPS everywhere
Every page, not just checkout, should load over HTTPS with a valid certificate. Check that renewals are automated, since an expired certificate shows a browser warning. See domain, DNS and SSL renewal.
Handle failed and pending payments gracefully
A payment can succeed, fail or remain pending. Your site should:
- Show a clear message for each state.
- Not mark an order as paid until your system receives confirmation from the provider (a server-to-server notification, often called a webhook), not merely because the customer returned to your site.
- Let the customer retry without re-entering everything.
- Tell customers what to do if money is deducted but the order shows unpaid.
Our guide to UPI and COD checkout design and the order confirmation page cover the screens involved.
Send a confirmation
After payment, show a confirmation page and send an email or message with the order number, items, amount and your contact details.
A Test Plan Before You Apply and Before You Go Live
Most providers give you a test mode. Use it fully before touching real money.
- Run a successful test payment and check that the order appears as paid in your system and in the confirmation email.
- Run a failed payment and check the message and the order state.
- Close the browser mid-payment and see what your site shows when the customer returns.
- Place two orders in quick succession to check for duplicate handling.
- Check the site on a mid-range Android phone on mobile data, since that is how many customers will pay.
- Confirm that the confirmation email arrives in the inbox, not spam. See email authentication with SPF, DKIM and DMARC.
- When you go live, make one small real purchase yourself and confirm it flows through, then refund it through your normal process.
Keep notes on the date, test and result, as you would for any pre-launch testing checklist.
Common Reasons Websites Get Held Up
- Mismatched details. Business name or address on the website differs from your application.
- Missing policy pages or ones that are obviously copied with another company's name left in.
- Placeholder content. Lorem ipsum, stock text and dead pages.
- No prices or vague offers.
- Broken checkout links or a test page that errors.
- A site that is not live yet or sits behind a password.
- Selling something outside the provider's allowed categories.
Allow time in your launch plan for questions from the provider; a review can need several rounds. Do not plan a promotional campaign to start the same day you expect approval.
Costs and Timelines: What to Ask
Fees, settlement timelines and charges change and differ between providers, so we do not quote them here. Ask each provider for their current fee schedule in writing and compare like with like. For your own website budget, our guides on ecommerce website development cost and timeline in Pune and custom ecommerce payment flows cover the build side.
Who Does What
| Task | Usually owned by |
|---|---|
| Business registration, KYC documents, bank account | You, with your accountant |
| Choosing a provider and reading its terms | You |
| Building pages, policy layout and checkout flow | Your web developer |
| Writing policy wording, tax treatment | You, with a qualified adviser |
| Testing in test mode and going live | Developer and you, together |
| Ongoing monitoring of failed payments | You, with developer support |
Agree these roles in writing at the start so nothing falls between them.
Frequently Asked Questions
What does a payment provider check on my website?
Commonly: that your business is identifiable, that your offering and prices are clear, that policy pages exist and that the site works. Requirements vary, so read your provider's current guidance before applying.
Which policy pages does my small-business website need?
At minimum a privacy policy, terms and conditions, and a refund, cancellation and delivery policy, plus a contact page with working details. Have the wording reviewed by a qualified adviser for your type of business.
Can I apply before my website is finished?
You can often start, but a half-built site tends to delay approval. Have the main pages, prices, policies and a working test checkout in place first.
Should my website store card details?
No. Use the provider's hosted or embedded payment fields so that sensitive details go to them directly, and confirm the integration style with your developer.
Getting Your Site Ready to Take Payments
Govindani Infotech, a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, builds business websites and checkout flows for Pune businesses. If you want the pages, policies and checkout built and tested before you apply, see our website creation services and checkout systems, then contact us or call 092019 58274.
Sources:
- Digital Personal Data Protection Act, 2023 (Government of India)
- PCI Security Standards Council: Document Library
About the author: written by the Govindani Infotech ecommerce development team in Pune.