The Shizz!Book a Growth Audit
← THE JOURNAL
Operations8 MIN READ

Razorpay vs PayU vs Cashfree: the gateway decision is a conversion decision

Founders compare gateways on the quoted MDR. The money actually lives in success rates, settlement speed and what the checkout does to your funnel.

By The Shizz · Published 4 Aug 2026

Reframe: you are buying conversion, not processing

All serious Indian gateways quote similar headline pricing — typically zero or near-zero MDR on UPI (where most D2C volume now lives), and roughly 1.7–2 percent on cards and netbanking, with premium instruments higher. At those spreads, the fee comparison is the least important part of the decision. The variables that actually move your P&L: payment success rate on your specific mix (a point of failed payments is lost orders you already paid to acquire), settlement speed (T+1 versus T+2 versus instant — working capital for an inventory business), checkout UX (saved instruments, UPI intent flow that opens the right app, retries that rescue failures), and operational quality — refund speed, dispute handling, downtime behaviour during sale events.

Razorpay: the D2C default, for good reasons

Razorpay became the reflex choice for Indian startups on developer experience: clean APIs and plugins for every stack, Magic Checkout with saved addresses and one-click flows, subscriptions, payment links and a polished dashboard. Success-rate performance on UPI and cards is consistently competitive, and features land here first more often than not. The trade-offs founders report: onboarding and risk reviews have tightened (food and wellness categories sail through; anything claim-heavy gets scrutiny), support quality scales with your volume tier, and pricing negotiability starts only when your volumes justify a conversation. If you are on Shopify or WooCommerce and want the least-friction competent default, this is it.

A one percent difference in payment success rate is worth more than a half percent difference in fees — every single month.

PayU and Cashfree: where each one earns its seat

PayU carries enterprise DNA — deep card-network relationships, strong EMI and affordability stack (relevant the moment your AOV crosses ₹3,000), international payment support, and success-rate muscle on card-heavy mixes. It tends to win older, larger, card-skewed businesses and brands selling abroad. Cashfree competes on payouts and money movement as much as collections: instant refunds, vendor splits, payout APIs (useful for COD refund flows and marketplace-style operations), aggressive UPI economics and generally sharp pricing for growing volumes. Practical pattern across our client base: Razorpay or Cashfree as primary for UPI-heavy D2C mixes, PayU entering the frame with EMI-heavy or international requirements.

The two-gateway architecture (what mature brands actually run)

Past a few thousand orders a month, single-gateway dependence is an availability and negotiation risk. The standard play: primary gateway for 80–90 percent of volume, a second live for failover and leverage, ideally behind an orchestration layer or your platform's native routing. What this buys: automatic rerouting when a gateway has a bad UPI hour (they all do), instrument-level routing (send EMI to PayU, UPI to the cheapest reliable rail), real success-rate data to negotiate with, and zero-downtime sale events. The cost is one extra integration and reconciliation stream — trivial against a Diwali evening of failed payments (the festive playbook assumes checkout survives the traffic you paid for).

UPI mechanics: where Indian checkouts are won and lost

With UPI at the heart of D2C payments, the details compound: intent flow beats collect flow on mobile (tapping into the UPI app directly converts far better than typing a VPA and waiting for a request); failed-payment retry UX — instant retry with an alternate method on the same screen rescues a meaningful slice of failures; saved-card tokenisation plus UPI Autopay unlock one-tap repeats and subscriptions (the retention engine in the WhatsApp playbook converts better when the payment is one tap); and COD-to-prepaid nudges at checkout — a visible prepaid discount funded by your RTO savings — shift payment mix more cheaply than any gateway fee negotiation. Measure success rate by instrument and by hour; averages hide the failures that cluster.

The selection checklist, in order of impact

  1. Run a two-week parallel test if you can: same traffic, measure success rate by instrument. This one number usually decides.
  2. Settlement: T+1 standard? Instant settlement pricing? Refund speed (instant refunds visibly reduce support tickets and repeat-purchase hesitation)?
  3. Checkout: UPI intent, saved instruments, native retries, address intelligence — demo them on a ₹12,000 Android phone on 4G, not your office Wi-Fi.
  4. Ops: reconciliation exports your accountant can live with, dispute SLAs, downtime history during major sales.
  5. Then, and only then, negotiate rates — with your real volumes and your measured success-rate data as leverage.

Frequently asked questions

Which payment gateway has the best success rate for D2C in India?

It depends on your instrument mix and traffic profile more than the brand name — all three majors are competitive. The honest answer is to run a parallel test on your own traffic for two weeks and measure success rate by instrument; a one-point success-rate difference outweighs any headline fee difference.

Should a D2C brand use two payment gateways?

Past a few thousand orders a month, yes: a primary handling 80–90 percent of volume and a second for failover, instrument-level routing and negotiation leverage. Single-gateway dependence turns any bad UPI hour — and they all have them — into lost orders you already paid to acquire.

What matters more: gateway fees or settlement speed?

For most growing D2C brands, settlement speed and success rate both beat fees. T+1 versus T+2 settlement is real working capital for an inventory business, and failed payments are lost acquisition spend. Negotiate fees last, armed with your measured volumes and success-rate data.

How do I reduce failed UPI payments at checkout?

Use intent flow (tap into the UPI app) rather than collect requests on mobile, offer instant same-screen retry with an alternate method, keep the gateway SDK current, and monitor success rate by hour and instrument to catch clustering failures early. Checkout UX rescues more revenue than rate negotiations save.

Leaking orders at the last step?

The free audit includes a checkout teardown — success rates, UPI flow and the retries you are not running.

Book a Growth Audit →