Why payment gateway applications get rejected in India, and how to pass the audit in 2026
I once had a merchant apply for the UroPay API with a website that looked ready to go live: clean design, working checkout flow, a product catalogue that made sense. The application still stalled for four extra days because the refund policy page was a placeholder that said "coming soon," and the bank account was registered under a slightly different business name than the PAN card. Neither problem was really about the website's design. Both were the kind of thing an audit exists to catch.
That's the part of getting a payment gateway that nobody enjoys talking about: before you ever move money, someone reviews your business. In 2026, that review got a lot more formal across the whole industry, not just at UroPay. The Reserve Bank of India's new rules for payment aggregators pushed merchant due diligence requirements into force on January 1, 2026, and the compliance window for merchants who were already live before that date closes soon. If you're applying for a UPI payment gateway API this year, or you're an existing merchant whose paperwork is still catching up, here's what the audit actually checks, why it got stricter, and how to get through it on the first try with the UroPay API.
What actually happens during a payment gateway audit
A payment gateway audit is not a background check on your credit score. It's a review of what your business sells and whether your website or app can back that up in writing. Every payment aggregator runs some version of the same checklist: does the site have a visible refund policy, a privacy policy, and terms of service; does it list real contact details; do the product pages match what's actually for sale; does the pricing show up before checkout instead of after.
On the UroPay API, this is the second of five onboarding steps and it happens for every merchant, KYC or not. The product page describes it plainly: the review covers "what you sell, your policies, your pages" against a published list of restricted categories. That's a narrower scope than a full compliance audit at a bank, but it's still a real review, not a formality. A site with no refund policy, or one where the product description doesn't match what a customer would actually receive, gets flagged the same way it would at any other aggregator.
Razorpay and Cashfree publish similar document checklists on their own blogs, which tells you this isn't a UroPay-specific hurdle. What differs between providers is what happens after the audit flags a problem. Some aggregators park the application in a review queue for weeks. UroPay's onboarding runs on a five-working-day target, and a flagged website usually just means fixing the specific page and reapplying rather than waiting out a queue. Worth being clear about the trade-off here too: a five-day audit is still five days you're not collecting payments, so it pays to get your site ready before you apply rather than after. The step-by-step checklist further down in this post covers exactly what to check first.
RBI's 2025 rules made audits stricter, and the deadline lands this year
The reason audits across the industry feel more thorough in 2026 traces back to a specific regulatory change. On September 15, 2025, the RBI issued the Master Direction on Regulation of Payment Aggregators, 2025, replacing a patchwork of earlier circulars with a single rulebook covering authorisation, merchant due diligence, escrow handling, and reporting for every payment aggregator operating in India.
The merchant due diligence requirements in that direction entered into force on January 1, 2026. Aggregators now have to run Contact Point Verification, background checks, and a "fit and proper" assessment on merchants before onboarding them, on top of the usual KYC documents. For merchants who signed up after January 1, 2026, there's no grace period; the new checks apply immediately. For merchants who were already live before December 31, 2025, RBI gave payment aggregators until September 15, 2026 to bring that older merchant base into compliance, a deadline that's a couple of weeks out from today.
What that means in practice: if your business went live on any payment aggregator before this year and your paperwork was thin, you may get a request to complete additional verification before that September deadline, even if nothing about your account has changed. And if you're applying fresh in 2026, expect the audit to look at more than it would have two years ago, PAN-to-bank-account name matching in particular, since document mismatches were flagged as the single biggest cause of onboarding delays in the older, looser system. None of this is specific to UroPay; it's the baseline every aggregator in India is now working against.
Five things that get website-based applications rejected
Most rejections aren't about the business itself being ineligible. They're about the website not backing up what the application claims. In order of how often they come up:
A mismatched name across PAN, GST, and bank account is the top one. Even a missing middle initial or an "and" swapped for an ampersand between your PAN card and your bank account can stall an application, since one industry estimate puts name mismatches behind close to 40% of gateway onboarding delays in India. Get this aligned before you apply, not after.
A missing or vague refund policy is second. "Refunds at our discretion" isn't a policy, it's a placeholder, and reviewers treat it that way. Spell out the timeframe, the conditions, and how a customer actually requests one.
Third, a privacy policy that doesn't say what happens to payment data specifically. Generic legal boilerplate copied from a template site is easy to spot and easy to reject.
Fourth, no visible way to contact the business, no support email, no phone number, no physical address anywhere on the site. This is one reviewers check first because it's the fastest signal of whether a business is real.
Fifth, and the one that ends applications instead of just delaying them: selling something on the prohibited list. That list is long and specific. Check it before you build a checkout page around a product line that was never going to clear review.
KYC vs non-KYC on the UroPay API: what actually changes
The UroPay API runs two pricing tiers, and I want to be precise about what the KYC decision actually skips. Complete KYC and you pay 5% + ₹5 per transaction, with settlement on T+3 working days. Skip it and you pay 10% + ₹5, settled on T+5. What KYC buys you is a lower rate and faster money, not a lighter audit.
The website or app review happens either way. So does the merchant contract. What non-KYC skips is the identity paperwork specifically: PAN of the business or proprietor, ID and address proof of the signatory, business registration or GST certificate. If you're not ready to hand those over yet, or your business is simply too new to have them, the non-KYC tier still gets you live in the same five working days, just at a higher rate. You can complete KYC later and drop to the lower rate whenever you're ready. That's a real, if costlier, path around the identity-document bottleneck that stalls so many applications at larger aggregators. It is not a way to skip the review of your website itself.
If your business needs the lighter-touch, no-audit route entirely, that's really what UroRelay is for, since it relays payments through your own UPI account with no onboarding review at all. It's built for freelancers and solo sellers who don't need their own checkout page. The trade-off is that you're sharing a payment button or link instead of owning the checkout experience, which is exactly the gap the API closes once you're ready to build your own.
The 44-category prohibited list, and where UroPay is more accommodating
The UroPay API publishes a list of 44 prohibited categories. Read it before you apply, not after. It covers the obvious ones: weapons, drugs, counterfeit goods, gambling, adult content, chit funds. It also covers less obvious entries like drop-shipped merchandise, mailing lists sold for tele-calling, and multi-level marketing collection fees. Nothing on that list is negotiable regardless of KYC status; the audit checks against it specifically, and a business built around one of these categories will get declined at the review stage rather than approved with conditions.
Outside that list, though, UroPay's actual pattern is closer to accommodating than restrictive, and this is the part that's easy to miss when you're only looking at the fee. Categories that bigger, stricter aggregators place on indefinite review, or decline outright because they're not worth the compliance overhead at scale, sole proprietorships without a formal company structure, early-stage businesses with thin operating history, niche or nonstandard product lines, get a real audit instead of an automatic hold. That's the actual reason some merchants pick the higher commission over a cheaper mainstream aggregator. Not price. A real shot at getting approved at all. Check the full list against your business before applying; if you're unsure whether a category qualifies, the audit step will tell you, but it costs nothing to check first.
UroPay API vs traditional payment gateway APIs
| UroPay API | Typical mainstream aggregator API (Razorpay/Cashfree/PayU/CCAvenue) | |
|---|---|---|
| Commission | 5% + ₹5 with KYC, 10% + ₹5 without | Typically around 2% + GST |
| KYC requirement | Optional, sets your rate | Mandatory before going live |
| Settlement | T+3 (KYC) or T+5 (non-KYC) | Often T+1 to T+2 once approved |
| Onboarding | About 5 working days, audit + contract | Varies widely, can run longer for edge-case categories |
| Who owns the checkout | You, on your own domain | You, on your own domain (with full API integration) |
| Support model | Direct email to the founder, gaurav@uropay.me | Tiered, often ticket-based below enterprise volume |
| Restricted categories | Reviewed case by case within the 44-category list | Often declined or held indefinitely at application |
The commission gap is real, and I'm not going to pretend otherwise. What you get on the other side of it is in the next section.
What it actually costs: KYC, non-KYC, and a mainstream aggregator side by side
Take a ₹2,499 order, a realistic mid-range ticket size for an online course, a subscription box, or a service invoice. On the UroPay API's KYC tier, that's 5% (₹124.95) plus the flat ₹5 fee, so ₹129.95 comes off before settlement, leaving about ₹2,369 in your account on T+3. On the non-KYC tier, it's 10% (₹249.90) plus ₹5, so ₹254.90 comes off, leaving about ₹2,244 on T+5. A mainstream aggregator charging roughly 2% + GST on the same order would take somewhere around ₹59, leaving close to ₹2,440, usually a day or two faster.
Run that at volume and the gap compounds fast. On 100 orders a month at this ticket size, the KYC tier costs roughly ₹5,000 more than a 2% aggregator; the non-KYC tier costs closer to ₹19,500 more. That's not a rounding error, and I'd rather a merchant see the real number before signing than discover it in their first settlement report.
What buys back some of that gap is what a mainstream aggregator usually doesn't offer below enterprise volume: a direct line to the person running the platform instead of a support ticket queue, a non-KYC path that actually skips identity documents rather than just gesturing at simplicity, and a real audit instead of an automatic decline for a business that doesn't fit a standard template. For a merchant in a restricted or edge-case category who's been declined elsewhere, or one who values being able to email gaurav@uropay.me directly when something breaks, that combination can be worth more than the commission difference. For a straightforward business with clean documents chasing the lowest possible fee, a 2% aggregator is honestly the better math. Both are legitimate answers depending on what you're optimizing for.
How to prepare your site before you apply
Most of the delay in a payment gateway audit is avoidable, and it's cheaper to fix these before applying than after a review flags them.
Start with your policy pages. Publish a real refund policy with a specific timeframe and process, and a privacy policy that names what payment data you collect and how it's handled. Put both behind a visible link in your site footer, not buried three clicks deep.
Check your name consistency next. Pull up your PAN card, your GST certificate if you have one, and your bank account details, and confirm the legal name matches exactly across all three, spacing, punctuation, and all. That one check alone reportedly heads off the single most common cause of onboarding delay in India.
Add contact information reviewers can actually verify: a support email, ideally on your own domain, and a physical address if you have one. A contact form alone tends to read as thin.
Make sure your product or service pages describe what you're actually selling, with pricing visible before checkout, not hidden behind a "contact us for pricing" wall. Reviewers can't approve what they can't see.
Then check your business against the prohibited category list before you apply, not after. If you're clearly outside it, the review should move fast. If you're close to a line, better to know that going in.
Once the site is ready, the actual flow through dashboard.uropai.in is short: apply and describe your business, go through the website audit, decide whether to complete KYC now for the lower rate or skip it and go live at the higher one, sign the merchant contract, and get live keys. From there it's two REST endpoints, documented at api.uropai.in/documentation: one to create an order, one to check its status, plus a signed webhook for order confirmation.
Quick takeaways
- Every UroPay API merchant goes through a website and business audit, whether or not they complete KYC.
- RBI's Master Direction on Payment Aggregators, in force since January 1, 2026, made merchant due diligence stricter across the whole industry, not just at UroPay.
- Merchants onboarded before December 31, 2025 have until September 15, 2026 to meet the new requirements, a deadline that's close as of this post.
- The top cause of onboarding delay industry-wide is a mismatched name across PAN, GST, and bank account, so check that first.
- Non-KYC on the UroPay API skips identity documents and lowers your settlement speed and rate; it does not skip the audit or the contract.
- The UroPay API's commission, 5% + ₹5 with KYC or 10% + ₹5 without, runs well above a typical 2% mainstream aggregator fee.
- What that premium buys is direct founder-level support, a meaningfully more lenient KYC path, and a real shot at approval for restricted or edge-case categories other aggregators decline outright.
Getting started
An audit is a one-time cost for getting a payment gateway that's actually yours: your own checkout, your own domain, your own order data, on rails run by a licensed aggregator instead of a redirect to somebody else's hosted page. The businesses that clear it fastest are the ones that treat the policy pages, the name-matching, and the product descriptions as part of building the site, not as paperwork to handle after the fact.
If you're weighing whether the UroPay API is the right fit given the commission difference laid out above, the honest answer depends on whether your business is straightforward and well-documented, in which case a 2% mainstream aggregator probably serves you better, or whether you're in a category that keeps stalling elsewhere and you'd rather pay more for a real review and a person to email when something goes wrong. I built the non-KYC tier and the 44-category review specifically for the second group.
Start by checking your site against the checklist above, then apply through dashboard.uropai.in. If you have questions about whether your business fits before you apply, email me directly at gaurav@uropay.me. You can also read more about how the three UroPay products compare on the UroPay API page or check the FAQ.
Frequently asked questions
Does the UroPay API audit happen even if I skip KYC?Yes. The website and business audit is step two of onboarding for every merchant, regardless of whether you complete KYC. Skipping KYC changes your commission rate and settlement time; it doesn't remove the audit or the merchant contract.
What documents does the UroPay API actually require for KYC?PAN of the business or proprietor, identity and address proof of the signatory, business registration or GST certificate where applicable, and bank account proof for settlement. The exact list is confirmed during onboarding since it can vary by business type.
Why did payment gateway audits get stricter in 2026?RBI's Master Direction on Regulation of Payment Aggregators, 2025 brought merchant due diligence requirements, including Contact Point Verification and stricter identity checks, into force on January 1, 2026, replacing older, looser rules that applied across the industry.
What's the single biggest reason a payment gateway application gets rejected?A mismatch between the name on your PAN card, GST registration, and bank account. Industry estimates put this behind close to 40% of onboarding delays in India, ahead of missing policy pages or unclear product listings.
Can a business get approved on the UroPay API if bigger aggregators have declined it?Sometimes. Categories outside the published 44-category prohibited list get a real audit rather than an automatic hold, which is different from how larger aggregators often treat nonstandard or early-stage businesses. Categories on the prohibited list are declined regardless of prior history elsewhere.
Before you go
Have you been through a payment gateway audit that got stuck on something you didn't expect? I'd like to hear what it was, since it helps me keep this checklist accurate for the next founder reading it. Email me at gaurav@uropay.me, or share this post with someone who's mid-application right now.
References
- RBI Master Direction on Regulation of Payment Aggregators, 2025 (official PDF)
- RBI (Regulation of Payment Aggregators) Directions, 2025 — summary
- Payment Gateway KYC Onboarding Guide India (2026) — Razorpay
- Documents Required for Payment Gateway in India — Cashfree
- UroPay API — pricing, onboarding, and prohibited categories






