1. What is Razorpay?
Razorpay is India's leading payment gateway — and increasingly, its leading financial services platform for businesses. Founded in 2014 by Harshil Mathur and Shashvat Nakrani out of YCombinator, it started as a simple API to accept payments online. It's now a suite of products covering payments, banking, payroll, and lending.
The simplest version of the Razorpay story: they won the payment gateway market by being the product developers actually wanted to use, then used that distribution to expand into every financial product an SME needs.
Razorpay didn't win on price or feature count. They won because their API documentation was better than anyone else's — and in a developer-bought product, documentation is the product.
That insight — that the buyer persona in B2B fintech was changing from finance teams to developers — shaped every early product decision and is still the clearest lens for understanding what Razorpay is trying to build.
2. The User — And Why B2B User Complexity Matters Here
Razorpay has three distinct user types with very different needs, and getting this wrong is the fastest way to misunderstand their product decisions.
| User Type | Who They Are | What They Actually Want |
|---|---|---|
| Developer / Tech lead | Building the checkout or payment flow; evaluates APIs | Clean documentation, reliable uptime, instant sandbox, fast integration. Will advocate internally for whichever tool makes them look good. |
| Finance / Operations | Owns reconciliation, settlements, compliance | Accurate reporting, predictable settlement times, audit trail, GST handling. Will block adoption if reporting doesn't work. |
| Business owner / Founder | Cares about conversion, revenue, growth | Higher checkout success rate, lower payment failure rate, access to credit when needed. Buys on outcomes, not features. |
The product decision Razorpay made early — and most competitors missed — was to optimize first for the developer while making sure the finance team couldn't block it. The developer initiates adoption; the finance team has veto power. You need both.
The market segmentation by business size also matters: A startup wants a 15-minute integration. An enterprise wants SLAs, dedicated support, and custom settlement logic. Razorpay's product line has expanded to serve both — but the tension between these segments shapes every roadmap decision.
3. The Core Problem Being Solved
| Problem | How Bad It Was Before Razorpay |
|---|---|
| Payment gateway integration took weeks | Banks and traditional PGs (CCAvenue, PayU) required manual forms, verification, and enterprise sales cycles. A startup couldn't go live in a day. |
| API documentation was unusable | Competitors had PDFs, SOAP APIs, and integration guides written by lawyers. Developers were copying Stack Overflow answers to understand basic auth flows. |
| Payment failure rates were high | Industry average success rate ~65–70%. Lost transactions = lost revenue. Nobody was treating this as a PM metric. |
| SMEs had no banking product built for them | Traditional banks offered SME accounts that were designed for large enterprises, stripped down. No API access, no automation, no visibility. |
4. Product Evolution — The Platform Expansion Story
2014 — Launch └─ Payment gateway API for Indian businesses └─ Competitive moat: developer-first docs, fast onboarding 2015–17 — Distribution └─ PCI-DSS compliance, international card support └─ Razorpay Dashboard: finance team gets visibility └─ Growing SME merchant base 2018–19 — Product Depth └─ Payment Links: non-developer merchants can collect payments └─ Payment Pages: hosted checkout without engineering └─ Subscriptions: recurring billing for SaaS 2020 — Adjacency Expansion └─ Smart Collect (UPI QR, virtual accounts): B2B collections └─ Route: marketplace payment splitting └─ RazorpayX (banking): current accounts + API for businesses 2021 — Full Financial Stack └─ Razorpay Capital: instant credit based on transaction history └─ Opfin (payroll): acquired for ₹125 Cr — payroll for SMEs └─ Corporate cards via RazorpayX 2022–24 — Platform Maturity └─ International payments (outward remittances) └─ Embedded compliance (TDS, GST reconciliation) └─ AI-based fraud detection in payment flows └─ Razorpay for Enterprise: custom SLAs, dedicated infra
The sequencing logic worth studying: Razorpay expanded from payment collection → banking → payroll → lending. Each step used data from the previous one. Banking gave visibility into cash flow. Payroll gave data on employee count and burn rate. Both made underwriting for Razorpay Capital dramatically better than a traditional lender could achieve.
They didn't expand because they wanted to be a super-app. They expanded because each adjacency made the underwriting data better — which made the lending business viable.
5. Feature Analysis — What's Working and What's Not
Payment Gateway — Core Product
Industry-leading checkout success rate (reportedly 85%+ vs. industry ~70%). Best-in-class developer experience. SDKs for every major language and platform. Risk: This is increasingly table stakes — PhonePe for Business and PayU have closed the gap. The moat is defensibility of the installed base, not product differentiation.
RazorpayX — Business Banking
Current accounts with API access, automated payouts, vendor payments, corporate cards. Fills a genuine gap — traditional SME banking has no API layer. The PM bet: businesses that process payments with Razorpay and bank with RazorpayX give Razorpay a 360° view of their cash position — which is the real underwriting asset. Risk: RBI's banking regulations create a ceiling. Razorpay doesn't have a banking licence — it works through partner banks. Regulatory changes can move the ceiling unexpectedly.
Razorpay Capital — SME Lending
Instant credit lines and business loans underwritten using transaction history rather than traditional credit bureau data. This is the most strategically valuable product in the portfolio. SMEs that are creditworthy by cash flow but invisible to traditional lenders are the addressable market. The AI angle: Razorpay Capital is essentially a machine learning problem dressed as a fintech product — the model gets better with every loan cycle because more transaction data flows in.
Opfin (Payroll)
Acquiring Opfin was the right call — payroll data is the cleanest signal of a company's financial health. But payroll is a category where stickiness comes from compliance accuracy (PF, ESI, TDS), and that's a grueling product domain. The question isn't whether Razorpay should own payroll — it's whether they have the patience to build it with the depth that HR teams actually trust.
Payment Links & Pages
Democratized payment collection for non-technical merchants — freelancers, consultants, small retailers who don't have engineering resources. Smart move: extends Razorpay's addressable market without compromising the developer-first core product. Simple no-code interface. Opportunity: These users generate data about informal SME cash flows that Razorpay Capital could underwrite — but the data pipeline from no-code to lending isn't fully built yet.
International Payments
Outward remittances and international collections are real pain points for Indian exporters and SaaS companies with global customers. But this is a highly regulated, compliance-heavy space with established players (Wise, Payoneer, banks). Razorpay's advantage here is the existing merchant relationship — cross-sell, not a greenfield play. Too early to assess.
6. Business Model — The Three-Layer Stack
| Layer | Product | Revenue Mechanism | Margin Profile |
|---|---|---|---|
| Transactions | Payment gateway, Links, Pages | MDR (1.8–3% per transaction) | Low-medium — volume-dependent |
| Banking | RazorpayX, corporate cards, payroll | Interchange, float income, SaaS fees | Medium — improves with AUM |
| Lending | Razorpay Capital | Interest income, processing fees | High — if NPA is managed well |
The strategic logic: Transaction revenue is thin and commoditizing. Banking revenue scales with asset under management. Lending revenue is the highest-margin bet but carries credit risk. Razorpay is building toward a world where transactions are nearly free (a customer acquisition cost) and the real revenue comes from banking and credit.
This is the same playbook Stripe is running globally — but Razorpay is doing it in a market where 90% of SMEs are underserved by traditional finance, which makes the total addressable market much larger relative to the size of the company.
7. What's Working
Strengths
- Developer experience moat: Eight years of compound advantage in API quality, documentation, and developer community. Hard to replicate quickly.
- Data flywheel: More transactions → better fraud detection → higher success rates → more merchants → more transactions. Every new product adds a new data type to the flywheel.
- SME trust: 8M+ businesses rely on Razorpay for revenue collection. Switching cost is high once payroll, banking, and payments are all on one platform.
- Razorpay Capital's underwriting advantage: Transaction-history-based underwriting is structurally better than bureau-based underwriting for new-to-credit SMEs. No traditional lender has this data.
- Enterprise expansion: Moving upmarket to larger customers without losing the SME base — two customer segments, two revenue profiles, one platform.
8. What's Not Working
Risks and Weaknesses
- Regulatory ceiling on banking: Without a banking licence, RazorpayX is always one RBI circular away from a product constraint. The partner-bank model works until it doesn't.
- Commoditization in the gateway: The developer-first advantage is narrowing. Cashfree, PayU, and PhonePe Business have all improved their APIs significantly. Price pressure is real.
- B2B sales motion complexity: As Razorpay moves upmarket to enterprise, the sales cycle gets long, legal gets involved, and the developer-self-serve motion breaks down. Enterprise sales is a different muscle.
- Payroll execution risk: Opfin works, but compliance payroll is brutally hard. PF, ESI, TDS filings are highly sensitive — one systematic error at scale is a reputational crisis.
- Valuation overhang: The $7.5B Series F valuation was set at 2021 peak. A secondary market at this valuation is difficult. Pressure to reach profitability may constrain ambitious product bets.
9. Three Product Opportunities I'd Build Next
AI Cash Flow Intelligence — Razorpay Capital's Killer Feature
Razorpay Capital already uses transaction history for underwriting. The missing product: surface that intelligence back to the merchant as forward-looking cash flow forecasting. "You have 23 days of runway at current burn. Based on your seasonal pattern, you typically see a 40% revenue dip in August — here's a working capital offer sized for that dip."
This turns Razorpay Capital from a reactive lending product (apply when you need money) into a proactive financial advisor (we see the dip coming before you do). It also dramatically increases the relevance of credit offers — you're not cold-pitching, you're answering a question the business owner already has.
Razorpay for Bharat — Vernacular-First, Low-Bandwidth Payment Collection
The 8M businesses on Razorpay are not representative of India's ~64M SMEs. The remaining 56M are Tier 2/3 businesses — kirana stores, local service providers, small manufacturers — who operate on WhatsApp, in Hindi, Marathi, Tamil, or Telugu, and have unreliable internet connections.
The current Razorpay product assumes English, stable internet, and a smartphone with sufficient processing power to run a modern web app. None of these assumptions hold for Bharat. A simplified, vernacular-first, low-bandwidth payment collection product — built specifically for offline-first use cases — could double the addressable market. The challenge is product discipline: every feature that makes the premium product powerful makes the Bharat product harder to use.
Embedded Compliance — Automated Tax and Regulatory Filing at Point of Transaction
Every Indian business with GST registration has to file GSTR-1 and GSTR-3B monthly. Every business paying vendors above threshold has TDS obligations. Every payroll run has PF/ESI filing requirements. This compliance work is either done manually (error-prone, time-consuming) or outsourced to a CA (expensive).
Razorpay sees every transaction. The data to pre-populate 80% of a GST filing is already in the system. The product: as a merchant completes a transaction on Razorpay, the system automatically categorizes it for GST, flags TDS obligations, and pre-builds the filing. At month end, review and file with one click.
This makes switching from Razorpay almost impossible — your compliance history lives in the platform. And it's a feature that Stripe cannot replicate in India without years of regulatory relationship-building. It's a local moat.
10. The Comparative Lens — Razorpay vs. Stripe
The most common framing of Razorpay is "India's Stripe." It's useful shorthand, but it obscures the ways the products are fundamentally different — and why those differences matter for PM thinking.
| Dimension | Stripe | Razorpay |
|---|---|---|
| Core user | Global developer building internet businesses | Indian developer + Indian SME finance team |
| Market context | Card-first markets; established banking infrastructure | UPI-first; large unbanked SME segment; regulatory complexity |
| Revenue model emphasis | Transaction processing + Stripe Capital | Transaction + banking + lending (more balanced) |
| Data advantage | Global transaction patterns | Deep India-specific cash flow data on 8M SMEs |
| Regulatory posture | Works within established frameworks | Must navigate RBI, SEBI, IRDAI simultaneously |
| Competitive moat | Global developer network effects | India-specific data and compliance depth |
The key insight: Razorpay can build products Stripe cannot, because Razorpay has India-specific data advantages, regulatory relationships, and SME distribution that take years to build. The risk is that this moat only protects them in India — global expansion carries none of these advantages.