Best Payment Gateway for a Small Indian Online Store: The Cart-Conversion, COD, and Cross-Border Playbook

Cart-conversion reality — why the 'best payment gateway' question is really a checkout-optimisation question

The single most impactful metric for a small Indian online store is completed-checkout rate: the percentage of customers who click 'Buy' and actually complete payment. Every published study of Indian D2C checkout drop-off puts the figure well below what merchants assume — a large share of would-be customers who reach checkout do not complete the transaction. The payment gateway choice materially affects this rate through several mechanisms.

One-tap UPI Intent vs multi-step UPI Collect. UPI Intent (which opens the customer's chosen UPI app directly from the merchant checkout with pre-populated amount and merchant ID) has meaningfully higher completion rates than UPI Collect (which pushes a pull request to the customer's UPI app requiring the customer to open it separately and approve). Both Razorpay and PayU support both flows; the checkout UX difference between which flow is default-presented to mobile users materially moves conversion.

Checkout-flow length. Every additional field, screen, or click reduces completion by a measurable percentage. Razorpay Standard Checkout is widely regarded as the most polished among Indian PA-licensed gateways for compressing the flow while maintaining PCI DSS + RBI tokenisation compliance. PayU Bolt SDK is competitive but the differential is real. Cashfree Pay is comparable to Razorpay on mobile-optimised checkout polish.

Failed-transaction retry. When a card transaction fails at the issuer (insufficient funds, OTP timeout, network drop), a well-designed gateway offers automatic retry with an alternative method suggested (retry as UPI, retry as netbanking). Both Razorpay and PayU offer smart-routing/optimizer features; the recovery percentage varies by merchant category and volume tier.

Mobile-first vs desktop-first UI. Indian D2C traffic is materially mobile-heavy across most categories. Checkout UX optimised primarily for mobile (thumb-reachable buttons, compressed form fields, native-app-like input handling) converts better than desktop-first UX squeezed onto mobile.

Guest checkout vs account creation gate. Requiring account creation before payment reduces completion. Guest checkout with post-purchase account creation offer is the modern D2C default.

Trust signals at checkout. RBI PA-licensed indicator, PCI DSS badge, network logos (Visa, Mastercard, RuPay, UPI ecosystem badges) collectively reduce abandonment among cautious buyers. Both Razorpay and PayU checkout include these signals; embedded checkout in the merchant's own UI must reproduce them explicitly.

The right gateway for a specific small online store is the one whose checkout UX, retry logic, and mobile ergonomics deliver the highest completion rate for that store's specific cart mix — not the one with the lowest sticker MDR. For the regulatory framework that determines which gateways can even legally hold your funds, see the companion guide on PayU vs Razorpay under the RBI PA license and UPI Zero-MDR mandate. For deep fee arithmetic across MDR + GST + hidden charges, see the fee-math playbook.

The Shopify + WooCommerce + Wix + Zoho Commerce + Dukaan + Mydukaan integration landscape

Most small Indian online stores run on one of half a dozen commerce platforms. The gateway-integration story differs materially across them.

Shopify India. Shopify supports Razorpay, PayU, Cashfree, PayTM, PayU BizGrid, and Stripe India via native and third-party gateway apps. Native integration setup is generally straightforward through the Shopify admin — the merchant provides API key and secret from the gateway dashboard, tests transactions in the gateway sandbox, and enables the gateway for live checkout. Shopify also charges its own transaction fee (variable by Shopify plan) on top of the gateway MDR unless the merchant uses Shop Pay + Shopify Payments in supported markets — Shopify Payments is not currently launched in India, so Indian Shopify merchants always pay the Shopify transaction fee plus gateway MDR. Practical implication: Shopify India MSMEs should model total gateway cost as Shopify transaction fee + gateway MDR + 18% GST on both.

WooCommerce. WordPress + WooCommerce is a very large share of the Indian D2C long-tail. Razorpay, PayU, Cashfree, Instamojo, Bharatpe, and Paytm all offer official WooCommerce plugins. Setup requires plugin install, API key configuration, and webhook URL registration. No platform transaction fee (WooCommerce is free to use beyond hosting), so gateway MDR is the primary payment cost. The WooCommerce ecosystem is generally the most gateway-flexible of any commerce platform in India — most merchants can trial two or three gateways in parallel on a WooCommerce store to compare completion rates before consolidating.

Wix and Squarespace India. Wix supports Razorpay, PayU, and PayPal for Indian storefronts; Squarespace's India payment integrations are more limited (Stripe is the primary Squarespace integration globally but Stripe India availability for Squarespace merchants is variable). Merchants on Wix or Squarespace with material Indian payment volume increasingly migrate to Shopify or WooCommerce for wider gateway choice.

Zoho Commerce. Deep native integration with Zoho's own payment stack + Razorpay + PayU + Instamojo + Stripe. Zoho Commerce ties into Zoho Books for GST-compliant invoicing and Zoho Inventory for stock — attractive for Indian MSMEs already using the Zoho suite.

Dukaan and Mydukaan. Indian-origin no-code online-store builders targeting the same audience as Shopify for smaller merchants. Native integrations with Razorpay, PayU, Cashfree, and payment link workflows. Streamlined for merchants who don't want the full Shopify complexity.

Custom-built stores. For merchants with in-house developer capability, direct API integration with Razorpay, PayU, or Cashfree is the norm. Razorpay's API documentation is widely regarded as the smoothest developer experience among Indian PA-licensed gateways. PayU's API is comprehensive but less polished. Custom integration allows the finest control over checkout UX, retry logic, and analytics but requires ongoing engineering maintenance as gateway APIs and RBI tokenisation requirements evolve.

UPI Intent, UPI Collect, and UPI AutoPay — the checkout that actually converts on Indian mobile

UPI carries the largest share of Indian D2C order count on almost every category. The specific UPI flavour presented at checkout materially affects completion.

UPI Intent. The customer clicks a UPI Intent button on the merchant checkout, their default UPI app (PhonePe, Google Pay, Paytm, BHIM, or their bank UPI app) opens directly with the merchant details and amount pre-populated, and the customer approves with UPI PIN. This is the highest-completion UPI flow because it collapses the entire authentication into one app-switch. All PA-licensed gateways (Razorpay, PayU, Cashfree, Paytm) support UPI Intent, with slight variations in how discoverable the flow is in the checkout UI.

UPI Collect. The customer enters their VPA (Virtual Payment Address) on the merchant checkout, the gateway pushes a Collect request to the customer's UPI app, and the customer must open the app separately to see and approve the pending request. This flow is materially less converting than UPI Intent because it requires the customer to switch apps voluntarily rather than being pushed directly. Merchants who default their checkout to UPI Collect (a common misconfiguration on older gateway integrations) leave conversion on the table.

UPI QR (in-app or in-checkout). The gateway displays a UPI QR code on the checkout page; the customer scans with their UPI app camera and completes payment. Historically important for desktop-to-mobile bridging, still relevant for BharatPe merchants and for merchants who want a fallback for customers whose UPI Intent handler is broken. Both Razorpay and PayU support this pattern.

UPI AutoPay (e-mandate). NPCI's UPI AutoPay framework allows customers to authorise recurring debits (subscription payments, EMI-like periodic charges) from their UPI-linked account without repeated OTP or PIN entry for each debit. This was a genuine breakthrough for Indian subscription businesses — before UPI AutoPay, subscription recurring failed frequently due to card OTP expiry and issuer authentication friction. Razorpay Subscriptions has deep UPI AutoPay integration; PayU supports it; Cashfree supports it. For a subscription-box, streaming, SaaS, or membership business, UPI AutoPay support is non-negotiable — a subscription business without it loses material recurring revenue to failed renewals.

UPI transaction limits. Standard per-transaction UPI limit historically ₹1 lakh (with sector-specific higher limits for capital markets, insurance, government payments, and merchant categories being raised progressively). For D2C stores with average order value under ₹10,000, UPI limit is not a constraint. For higher-ticket verticals (large-appliance, jewellery, furniture) approaching or exceeding ₹1 lakh average order value, the merchant must plan for card or netbanking fallback beyond the UPI limit.

UPI mandate for subscriptions post-CoFT. Card recurring subscriptions post-RBI Card-on-File Tokenisation mandate operate through network tokens with periodic re-authentication events. UPI AutoPay mandates operate through the UPI PIN + mandate framework without card involvement. For merchants where card recurring reliability has degraded post-tokenisation, migrating subscription customers from card recurring to UPI AutoPay materially improves renewal reliability.

Cash on Delivery (COD) and Return-to-Origin (RTO) — the elephant in every Indian online-store payment discussion

Cash on Delivery remains a material share of Indian e-commerce order value — industry estimates place COD at 30-60% depending on category, geography (higher in tier-2/3/4 cities), and merchant maturity (smaller D2C stores skew higher COD than large marketplaces that push prepaid). The payment gateway choice interacts with COD strategy in several meaningful ways.

RTO (Return-to-Origin) economics. COD orders have materially higher RTO rates than prepaid orders — the customer refuses delivery, the courier returns the parcel to the merchant, the merchant pays outbound + return shipping, restocking, and lost working capital on the tied-up SKU. RTO can turn a positive-margin COD order into a net-loss order once shipping, packaging, and handling costs are included. RTO reduction is arguably the highest-ROI operational focus for a small Indian D2C store.

COD-to-prepaid conversion nudges. Payment gateways that support sending a payment link (via WhatsApp, SMS, or email) after order placement but before dispatch enable a specific RTO-reduction pattern: the merchant places the order as COD, immediately sends the customer a payment link with a small incentive (₹50-₹100 off, free shipping upgrade, small freebie), and if the customer prepays via the link the order is converted to prepaid and the RTO risk drops to near zero. Razorpay Payment Links, PayU Payment Links, Cashfree Links, and Instamojo Payment Links all support this pattern; the winning implementation is the WhatsApp Business Platform-based flow where the payment link comes through the same channel the customer already uses.

COD verification via OTP. Merchants can integrate a phone-number OTP verification step for COD orders — the customer receives an SMS or WhatsApp OTP that must be entered before the order is confirmed. This step reduces prank orders and fraudulent COD attempts, both meaningful in tier-2/3 city acquisition. Delhivery, Shiprocket, and other Indian shipping aggregators integrate this at the shipping-label generation step.

COD pincode gating. RTO rates vary materially by pincode. Mature D2C stores maintain a pincode blacklist (where COD is not offered) based on historical RTO data — high-RTO pincodes get prepaid-only checkout, low-RTO pincodes get COD offered. Shopify apps and WooCommerce plugins support this; direct implementations require pincode-lookup logic at checkout.

Payment gateway support for COD reconciliation. Some gateways offer COD reconciliation dashboards that ingest shipping-aggregator COD-remit data and reconcile against orders. Razorpay Route + Payouts and Cashfree Payouts both offer relevant tooling. PayU offers reconciliation but the integration depth with Shiprocket, Delhivery, and other Indian shipping aggregators varies.

COD as a growth choice, not a permanent commitment. Small D2C stores often launch with COD to reduce customer trust friction (customer doesn't pay until they can see and touch the product), then progressively push prepaid as brand trust builds. Payment gateway choice interacts with this journey — gateways that support the COD-to-prepaid conversion pattern well accelerate the transition.

Cross-border D2C — international card acceptance, FEMA compliance, AD Category-I bank, and the RBI foreign inward remittance workflow

Indian D2C stores selling internationally (US, UK, EU, UAE, Australia, Singapore) — increasingly common in fashion, beauty, jewellery, home decor, wellness, and food/spice categories — enter an additional regulatory frame that shapes gateway choice.

FEMA (Foreign Exchange Management Act 1999). All foreign exchange transactions by Indian residents are governed by FEMA and RBI regulations. Foreign inward remittance to an Indian D2C store for international online sales must comply with FEMA procedures: correct purpose code assignment for the transaction (relevant codes for merchandise export, service export, and similar), documentation of the underlying trade, and reconciliation for RBI reporting via the merchant's bank.

AD Category-I bank relationship. Foreign inward remittance is handled through an Authorised Dealer Category-I bank — most scheduled commercial banks in India (SBI, HDFC, ICICI, Axis, Kotak, and others) hold AD-I status. The merchant maintains a current account with the AD-I bank; the payment gateway settles international-card receipts into that account with the appropriate FEMA-compliant documentation attached (Bank Realisation Certificate / e-BRC generation via the bank's export documentation flow).

International card acceptance — payment gateway options. Razorpay, PayU, and Cashfree all support international card acceptance (Visa, Mastercard, Amex, Discover, JCB) for Indian merchants, but with different depth and pricing:
- Razorpay: standard international MDR typically 3-3.5%+ plus 18% GST; integrated FEMA reconciliation workflow via the merchant's AD-I bank; strong documentation and settlement clarity.
- PayU: comparable international MDR structure; enterprise-oriented settlement workflow; deeper for larger cross-border merchants.
- Cashfree: competitive on international acceptance with a focus on payout products for cross-border merchants; integrated with cross-border settlement partners.
- Stripe India: Stripe operates in India through a partnership structure with local acquirers; international card acceptance is smooth; the developer experience is strong; suited to merchants building product for both Indian and international customers on the same technical stack.
- PayGlocal: specialist Indian gateway focused on cross-border commerce, worth evaluating for higher-volume cross-border D2C.

Alternative rails for cross-border D2C. Beyond direct card acceptance, Indian D2C stores selling internationally sometimes route through international platforms (Shopify + Shopify Payments in a target market where the merchant has a local entity, Etsy for handmade categories, Amazon Global Selling programs) rather than accepting card payments through an Indian PA gateway. The trade-off is platform commission vs FEMA/settlement complexity — merchants scaling cross-border should evaluate both paths.

Settlement currency. Indian PA gateways typically settle to the merchant in INR after conversion from the payment currency at a rate defined by the gateway (with transparent or embedded FX margin, varying by provider). Merchants with significant USD, EUR, or GBP receipts may prefer to hold in the payment currency where regulation permits — the RBI framework for Exchange Earners Foreign Currency (EEFC) accounts allows Indian exporters to hold a defined percentage of foreign exchange receipts in the foreign currency, useful for merchants with foreign-currency-denominated costs (international ads, SaaS tools).

Practical stack for a small Indian D2C store selling both domestically and internationally: primary domestic gateway (Razorpay or PayU or Cashfree) for INR transactions from Indian customers; international-card-enabled second rail (same gateway with international acceptance enabled, or Stripe India, or PayGlocal) for foreign-currency transactions; AD Category-I bank relationship with the merchant's chosen scheduled commercial bank; consistent FEMA documentation discipline via the bank's export documentation platform.

WhatsApp catalog + Instagram Shopping — the social commerce payment loop for small Indian online stores

For small Indian D2C stores, social commerce channels (WhatsApp Business Platform, Instagram Shopping, Facebook Shops) increasingly generate the majority of new-customer conversations. Payment gateway integration with these social channels is where a materially different set of workflow patterns emerges.

WhatsApp Business Platform (Cloud API) catalog. Meta's WhatsApp Business Platform supports product catalog integration — the merchant uploads product SKUs (name, description, price, image, availability) to the catalog, and messages exchanged with customers can reference specific catalog items with rich-media presentation. The payment loop: customer browses catalog in WhatsApp, expresses purchase intent in conversation, merchant confirms details and sends a payment link (Razorpay, PayU, Cashfree, Instamojo, or Bharatpe payment link), customer completes payment via the linked gateway flow, order enters merchant fulfilment pipeline. This flow is particularly strong for small D2C stores where consultative sales (jewellery, custom apparel, home decor with size and colour selection, wellness products with usage questions) benefit from human conversation before purchase.

Instagram Shopping. Instagram supports product tagging in posts, Reels, Stories, and Shopping tabs. The payment flow varies by market — in India, Instagram Checkout (in-app checkout without leaving Instagram) is not universally available; the more common pattern is tag-to-website: customer taps product tag, jumps to merchant Shopify/WooCommerce/WordPress storefront, completes checkout there with the merchant's chosen payment gateway. Merchants running Instagram Shopping should ensure their storefront checkout is genuinely mobile-optimised — Instagram traffic is essentially 100% mobile.

Facebook Shops. Similar pattern to Instagram Shopping — product tagging, jump-to-website checkout. Facebook Shops integration with Shopify and WooCommerce is standardised.

WhatsApp catalog + payment link integration architecture. The typical implementation stack for a small Indian D2C store combining these channels: WhatsApp Business Platform (Cloud API) via a Meta-approved BSP (Business Solution Provider) that handles catalog sync from the Shopify/WooCommerce product database; payment gateway integration via the BSP or via a middleware that generates payment links on demand; CRM to log customer conversations and order status. BSP options include Interakt, AiSensy, Wati, Zoko, and others operating in the Indian market — each with varying depth of Razorpay/PayU/Cashfree native integration.

Conversion economics of the WhatsApp payment loop. Small D2C stores frequently report materially higher completion rates on WhatsApp-conversation-plus-payment-link orders than on cold website-only checkout — the pre-purchase conversation resolves ambiguity, builds trust, and answers objections that would otherwise cause cart abandonment. The gateway MDR paid on these WhatsApp-loop conversions is often more than offset by the completion-rate lift.

Regulatory note for WhatsApp-loop payments. The RBI PA framework, tokenisation mandate, and DPDP Act 2023 all apply to WhatsApp-initiated payments the same as to website-checkout payments. The BSP intermediary does not change the compliance obligation — the merchant remains the Data Fiduciary under DPDP for customer data captured in the WhatsApp flow, and the PA-licensed gateway remains the escrow-holder for funds between customer payment and merchant credit.

Subscription boxes and recurring D2C — UPI AutoPay, card mandates post-CoFT, and the RBI e-mandate framework

Indian subscription-box businesses (curated beauty, fitness supplements, coffee, snacks, pet food, curated books, kids activities) and recurring D2C (replenishment models for staples like coffee pods, razor blades, contact lenses) depend on reliable recurring billing. The RBI Card-on-File Tokenisation mandate and the shift from card-based recurring to UPI AutoPay have materially reshaped the recurring-billing landscape in India.

Card-based recurring post-CoFT. Before the October 2022 tokenisation mandate, card recurring subscriptions worked through merchant-stored card details with periodic MDR debits authenticated behind the scenes. Post-mandate, all card-on-file operations must use network tokens (Visa, Mastercard, RuPay, Amex tokens), and RBI's additional-factor-authentication requirements for recurring payments have added friction at specific transaction amounts and periodic re-authentication events. Card-recurring failure rates for many merchants increased during the transition; well-implemented gateway integrations have largely recovered, but the underlying framework is materially more complex than pre-CoFT.

UPI AutoPay as the modern alternative. NPCI's UPI AutoPay (e-mandate) framework allows recurring debits from a customer's UPI-linked bank account without repeated OTP or PIN entry for each debit within the mandate limits. The customer sets up an e-mandate once at subscription start, approves it in their UPI app, and subsequent debits execute automatically until the mandate expires or the customer cancels. UPI AutoPay has better renewal-reliability characteristics than post-CoFT card recurring for many merchant categories. Razorpay Subscriptions has deep UPI AutoPay integration; PayU supports it; Cashfree supports it.

Mandate limits and terms. NPCI defines maximum per-debit amounts and mandate duration parameters. Mandates for regulated categories (mutual funds, insurance) have specific frameworks. Subscription-box merchants typically operate within standard mandate limits which cover the vast majority of consumer subscription price points.

Failed-payment retry strategy. Even the best gateway integration will see some subscription-billing failures — insufficient balance, mandate expiry, customer bank change. A well-designed subscription business layers automated retry (2-3 automated retry attempts over 3-7 days), followed by dunning (email/SMS/WhatsApp notification to customer with alternative payment option), followed by pause (subscription paused until customer resolves), followed by cancellation (subscription ended after defined period without resolution). Razorpay Subscriptions and Cashfree Subscriptions both support this cadence out of the box; PayU supports it but the configuration depth varies.

Subscription-specific gateway comparison. Razorpay Subscriptions is widely regarded as the most mature Indian PA-licensed subscription product with deep UPI AutoPay integration, dashboard analytics, and dunning tooling. Cashfree Subscriptions is competitive with focus on developer-first API. PayU offers subscription but the product is more oriented toward enterprise custom implementation than self-service SaaS. For a small Indian subscription-box business, Razorpay Subscriptions is typically the starting point unless specific developer-experience or pricing considerations point elsewhere.

International subscription customers. For an Indian D2C brand with international subscription customers (diaspora buyers, international audience), the FEMA and AD Category-I bank considerations from the cross-border section apply. Cross-border recurring is materially more complex than domestic recurring — many Indian subscription-box businesses either restrict subscriptions to domestic customers or operate a separate international entity for cross-border subscription operations.

Beyond PayU and Razorpay — Cashfree, Instamojo, Bharatpe, Paytm for Business, and Stripe India for small online stores

The 'best payment gateway' question expands beyond the PayU vs Razorpay binary for small Indian online stores. Several specialist and adjacent players fit specific merchant profiles.

Cashfree Payments. RBI PA-licensed, Bengaluru-based (verify current PA licence status on the RBI website). Product suite: Cashfree Payments (gateway), Cashfree Payouts (mass disbursement to vendors, freelancers, refunds), Cashfree Subscriptions, Cashfree UPI, Cashfree Split Payments. Cashfree Payouts is particularly strong — for D2C stores that pay influencers, affiliate marketers, refunds at scale, or drop-shipping partners, the payouts side of Cashfree is a genuine feature-set advantage over pure payment gateways. Developer experience and dashboard are competitive with Razorpay. Pricing is broadly comparable with PayU and Razorpay for standard MDR tiers.

Instamojo. Indian-origin, oriented toward the very-small-merchant segment — solopreneurs, home bakers, artisans, tutors, small D2C sellers with monthly GMV below what makes full PA gateway onboarding worthwhile. Strong on payment links and lightweight storefronts (Instamojo Store). MDR structure oriented toward pay-per-transaction with minimal fixed costs. Best fit for merchants below the practical break-even for a Razorpay/PayU/Cashfree onboarding.

Bharatpe. Started as a QR-code first payment infrastructure for merchants (offline + O2O), expanded into online payment aggregation. Best fit for merchants with mixed offline (physical shop) + online (small online store) revenue where consolidating on Bharatpe for both simplifies reconciliation. Merchant lending products layered on top.

Paytm for Business. Payment aggregator arm of Paytm (One97 Communications). Strong for merchants whose customer base skews toward Paytm wallet users. Integrated with Paytm's broader ecosystem (Paytm Mall visibility, Paytm Ads, Paytm Postpaid BNPL). RBI regulatory situation for Paytm's payment aggregator subsidiary has evolved through 2024-2025 — merchants should verify current PA licence status before making Paytm their primary rail.

Stripe India. Stripe operates in India through a partnership structure with local acquirers. Best fit for developer-first merchants building modern tech stacks and for merchants needing consistent Stripe integration across India + international. Native support for the same Stripe APIs used globally is attractive for cross-border D2C. Standard Stripe pricing (published on the Stripe India site) is competitive.

Juspay. Payment orchestration layer rather than a PA itself — sits above one or more PA-licensed gateways and provides intelligent routing (send this transaction to the gateway with best expected success rate), retry logic, and analytics. Best fit for larger merchants (₹5 crore+ monthly GMV) where the orchestration lift materially improves completion rates and where the merchant wants to hedge dependency on any single PA. Overkill for small D2C stores.

Decision pattern for small Indian online store. Start with primary PA-licensed gateway matching commerce platform (Razorpay for Shopify + WooCommerce depth of integration; PayU for larger enterprise heritage; Cashfree if Payouts side matters). Layer in Instamojo if merchant is very small. Add Bharatpe if offline QR volume warrants. Consider Stripe India specifically for cross-border developer stacks. Reconsider the stack quarterly as GMV grows and requirements shift.