The Ultimate Payment Gateway Integration Checklist for Indian Businesses
Pre-Integration: Choosing the Right Gateway and Understanding Fee Structures (TDR vs. MDR)
Embarking on online sales in India requires a robust, reliable payment gateway. Your first step in this crucial payment gateway integration checklist india is selecting the right partner. The Indian market is dominated by players like Razorpay, PayU, Cashfree, and Stripe, each offering a unique blend of features, support, and pricing. Your choice should hinge on factors like your business scale, transaction volume, required payment methods (e.g., UPI, cards, net banking, wallets, EMI, PayLater), and the quality of their developer support. Before you commit, it's vital to understand the fee structures, primarily the Transaction Discount Rate (TDR). Often used interchangeably with Merchant Discount Rate (MDR), TDR is the fee you pay on each transaction.
Most gateways have moved away from setup fees and annual maintenance charges (AMCs), but the TDR is non-negotiable. It's typically a percentage of the transaction value plus a fixed fee. For instance, a common TDR might be 1.9% + ₹0 for UPI and 2% + ₹0 for other instruments. This means a ₹5,000 sale via a credit card could cost you ₹100 in fees. Understanding these nuances is critical for financial planning and pricing strategy. Don't just look at the headline rate; investigate fees for international cards, chargebacks, and refund processing, as these can significantly impact your bottom line.
A lower TDR isn't always better. Prioritize reliability, transaction success rates, and customer support. A gateway that saves you 0.2% on fees is no good if it fails 5% more often during peak sales events.
Here's a simplified breakdown of common pricing components:
| Fee Component | Description | Typical Cost (for Indian businesses) |
|---|---|---|
| Transaction Discount Rate (TDR) | A percentage fee per transaction. Varies by payment mode (UPI, Debit/Credit Card, Net Banking, Wallet). | 0% for UPI up to ₹2,000. 1.8% - 3.0% for other domestic methods. |
| Setup Fee | A one-time fee for account creation. | Usually ₹0 for most standard plans. |
| Annual Maintenance Charge (AMC) | A yearly fee to keep the account active. | Largely waived by major players, but check the fine print. |
| Refund Processing Fee | A fee charged to process a customer refund. | Can be a fixed fee (e.g., ₹5-₹10) or just the non-return of the original TDR. |
| Chargeback Fee | A penalty fee when a customer disputes a transaction with their bank. | Can be a significant fixed fee (e.g., ₹500 per dispute), often non-refundable even if you win. |
Assembling the Essentials: A Checklist of KYC and Business Registration Documents
Once you've shortlisted a gateway, the next step is account activation, which requires a thorough KYC (Know Your Customer) process. Payment gateways are regulated financial intermediaries, and they are legally obligated to verify the identity and legitimacy of the merchants they serve. Delaying this step is a common pitfall. To ensure a smooth and swift onboarding, you must have all your business registration and identity documents scanned and ready for upload. The required documents vary based on your business constitution—a sole proprietorship has different requirements than a private limited company.
Being prepared is half the battle won. We recommend creating a dedicated folder on your computer with high-quality scans or digital copies of all relevant documents before you even start the application process. This simple act of organization can cut your onboarding time from weeks to just a few days. Gateways use this information to verify your business's existence, assess risk, and activate your account for live transactions.
Do not use personal bank accounts for your business. Payment gateways require a business bank account (a current account is ideal) in the name of the business or the proprietor. A personal savings account will almost always lead to rejection.
Here is a detailed checklist of the documents you will likely need:
- For Sole Proprietorships:
- Identity Proof: PAN Card of the proprietor.
- Address Proof: Aadhaar Card, Passport, or Voter ID of the proprietor.
- Business Registration Proof (any one): GST Certificate, Shop and Establishment Act License, FSSAI License, or other government-issued registration.
- Financial Proof: A cancelled cheque with the business name/proprietor's name printed on it, or a recent bank statement (first page).
- For Private Limited / LLP / Partnership Firms:
- Company/Firm PAN Card.
- Business Registration Proof: Certificate of Incorporation (for companies), Partnership Deed (for partnerships), LLP Agreement.
- Constitutional Documents: Memorandum of Association (MoA) and Articles of Association (AoA) for companies.
- Director/Partner Documents: PAN and Address Proof for all authorized signatories and directors/partners.
- Financial Proof: A cancelled cheque or bank statement for the company's current account.
- Board Resolution / Partner Consent: A formal document authorizing the opening of a payment gateway account. Most gateways provide a template for this.
The Technical Phase: A payment gateway integration checklist india for Sandbox Setup, API Key Generation, and Website/App Integration
With documentation out of the way, you enter the technical integration phase. This is where you connect your website or application to the payment gateway's system. Modern gateways make this incredibly accessible through a sandbox environment. This is a secure, isolated testing world that perfectly mimics the live payment environment. It allows your developers to build, test, and break things without touching real money or exposing your live site to bugs. The first step here is to create a developer account on your chosen gateway's platform and access this sandbox.
Inside the sandbox dashboard, you will find your first critical assets: your sandbox API keys. These usually come in a pair: a public 'Key ID' and a private 'Secret Key'. Think of the Key ID as your username and the Secret Key as your password for the gateway's API. These keys authenticate your application, proving that it has the right to request payments on your behalf. Guard your Secret Key carefully; it should never be exposed in your website's front-end code (like HTML or JavaScript). The actual integration method depends on your platform:
- Plugin/Extension Integration: If you use a popular CMS like WordPress (with WooCommerce), Shopify, or Magento, this is the easiest path. The gateway provides a pre-built plugin that you install, configure with your API keys, and you're almost done.
- SDK Integration: For mobile apps, gateways offer Software Development Kits (SDKs) for iOS and Android. These toolkits provide ready-made UI components and functions to handle payments natively within your app.
- Direct API Integration: For custom-built applications, you'll use the gateway's REST APIs. This offers the most flexibility and control over the user experience but requires significant development effort to build the checkout flow, handle responses, and secure the server-side communication.
Critical Testing: Simulating Successful Transactions, Payment Failures, and Refunds
Integration isn't complete when the checkout page loads. It's complete when it's been battle-tested. The sandbox environment is your battlefield. Rushing this stage is a recipe for disaster—leading to lost sales, frustrated customers, and a support nightmare on your first day of business. Your goal is to simulate every possible scenario, not just the happy path of a successful transaction. Gateways provide a suite of test card numbers, UPI IDs, and net banking credentials that can be used to trigger specific outcomes.
Your testing checklist should be exhaustive. You need to verify that your system correctly handles not just payments, but the entire lifecycle of a transaction. This includes processing refunds correctly and, most importantly, listening for webhooks. A webhook is a notification that the gateway sends to your server whenever a transaction's status changes (e.g., from 'pending' to 'captured' or 'failed'). Relying only on the front-end response is unreliable; the webhook is your single source of truth for order confirmation.
"If you don't test for failures, your first failure will be with a real customer." This is a core tenet of e-commerce development. A robust system gracefully handles errors, provides clear feedback to the user, and never leaves an order in an ambiguous state.
Here are the minimum test cases you must run:
- Successful Transactions: Process a successful payment with every payment method you plan to offer (Credit Card, Debit Card, UPI, a few Net Banking options, wallets).
- Failed Transactions:
- Simulate a failure due to an incorrect card number, expiry date, or CVV.
- Simulate a failure due to insufficient funds.
- Trigger an authentication failure (e.g., incorrect 3D-Secure PIN or OTP).
- Refund Simulation:
- Initiate a full refund from your admin panel and verify it reflects in the gateway's dashboard.
- Initiate a partial refund and verify the amount.
- Webhook Verification: Confirm that your server receives and correctly processes webhook notifications for payment success, failure, and refund events. Disconnect your internet and see if the order is still processed correctly once the webhook is received later.
Go-Live Day: Switching to Production Keys and Final Security & PCI Compliance Checks
After rigorous testing and a fully verified KYC, you're ready for the final step in your payment gateway integration checklist india: going live. This process is conceptually simple but must be done with extreme care. The core task is to switch from the sandbox environment to the live, real-money production environment. This involves generating a new set of API keys. Log in to your now-activated live gateway dashboard and navigate to the developer or API settings section. Here, you will generate your production API keys. These are the keys to your kingdom; they authorize real charges to customer accounts.
The transition plan is straightforward:
- Locate the configuration file or settings panel in your website/app's backend where you stored the sandbox API keys.
- Carefully replace the sandbox 'Key ID' and 'Secret Key' with their new production counterparts.
- Deploy the changes to your live server.
- Crucially, perform one final end-to-end test transaction with a small amount using a real credit card or UPI. This confirms that the production keys are working and that your system is correctly processing live payments.
A word on security: this is also the time for a final check on PCI DSS (Payment Card Industry Data Security Standard) compliance. The good news is that if you've used a standard integration method (like a redirect, iframe, or the gateway's pre-built checkout library), most of the heavy lifting for PCI compliance is handled by the gateway. They isolate the sensitive card data entry on their own secure domain. This drastically reduces your compliance scope. You must ensure you are not capturing, transmitting, or storing raw card numbers on your server at any point. Using a reputable gateway's standard checkout is the most secure and efficient path for most Indian businesses.
Beyond Integration: How to Streamline Your Payment Operations with an Expert Partner
Successfully integrating a payment gateway is a major milestone, but it's the beginning, not the end, of your financial operations journey. As your business grows, you'll face new challenges: managing thousands of transactions, reconciling payments with your accounting software, handling customer disputes (chargebacks), and optimizing your checkout flow to minimize drop-offs. The raw data from your payment gateway is a goldmine, but turning it into actionable intelligence requires expertise.
This is where a strategic digital partner can transform your business. You need a team that understands the full picture—not just the payment integration, but how it plugs into your entire operational ecosystem. For example, manually reconciling transactions from your gateway report with sales entries in your ERP (like ERPNext) or accounting software (like Tally) is a time-consuming and error-prone process. This can become a major bottleneck, preventing you from having a real-time view of your cash flow.
Your payment gateway shouldn't be a separate silo. It should be the engine of a fully integrated financial system that automates data flow from checkout to your final balance sheet. This is the key to scaling efficiently.
At WovLab, we specialize in bridging this gap. Our expertise goes beyond a simple setup. We build automated workflows and AI-driven solutions to streamline your entire commerce operation. We can help you:
- Automate Reconciliation: Build custom bridges that post payment data directly into your ERP or accounting software, eliminating manual entry.
- Enhance Reporting: Create custom dashboards that merge data from your payment gateway, website analytics, and marketing campaigns to give you a holistic view of your customer acquisition cost and lifetime value.
- Optimize Success Rates: Analyze failed transaction data to identify patterns and implement strategies (like smart routing or UI improvements) to improve payment success.
- Manage Disputes: Implement systems to help you efficiently manage and respond to chargebacks, protecting your revenue.
By partnering with WovLab, you gain a team that leverages development, AI, and operations expertise to turn your payment system from a simple utility into a strategic asset for growth.
Ready to Get Started?
Let WovLab handle it for you — zero hassle, expert execution.
💬 Chat on WhatsApp