← India FS Pulse

Memo

Underwrite distribution economics, not transaction economics

Generated 2026-08-22 by analysis/03_pe_diligence.py. Every figure below is interpolated from a computed value, so the prose cannot drift from the data.

The recommendation

Conditional no on a payments-fee thesis; conditional yes on a merchant-financing thesis. The merchant payments market is enormous and still compounding, but at 0bps MDR the payment itself is not a revenue event. An investment here has to be underwritten as distribution economics: the right to lend to, and sell software to, a merchant base, not as transaction economics. If the sponsor’s model depends on MDR returning, the answer is no, because that is a policy bet, not a business plan.

What the numbers say

Metric (2026Q2)Value
Registered merchants50,705,249
Transactions per merchant per quarter487
GMV per merchant per quarterRs 206,685
Merchant GMV10.48 lakh crore
Average merchant ticketRs 425
Payment revenue at today’s 0bps MDRRs 0

Annualised revenue per merchant, if an MDR existed:

MDRRevenue per merchant per yearTotal
10bpsRs 827Rs 4,192 crore
30bpsRs 2,480Rs 12,576 crore
50bpsRs 4,134Rs 20,960 crore

Three supporting arguments

1. Market attractiveness is not the constraint; price is. 50,705,249 merchants each running 487 transactions a quarter is a distribution asset most lenders would pay a great deal to rent. The constraint is that the transaction carries no price.

2. The unit economics only work at the merchant level, and only with a second product. At 30bps: a rate that does not exist: a merchant is worth Rs 2,480 a year. Any working-capital product priced off the same relationship dwarfs that. The payment is the acquisition channel; the loan is the P&L.

3. The only listed pure-play has not solved it yet. One97 Communications (Paytm) reported Rs 8,437 crore of revenue in FY2026 at a 7% net margin. A sponsor cannot underwrite this deal on a ‘payments scale economics’ thesis when the largest listed comparable, with a decade of scale, still earns a thin return on the payments business itself.

Red flags

Upside register

Ambiguity register

The JD asks for the ability to deal with ambiguity and to develop approaches to tackle diligence questions. Stated explicitly, here is what this analysis does not know, and how a real diligence would resolve it:

UnknownWhy it is unresolved hereHow to resolve it
True market-wide merchant countPulse discloses one operator’s registered merchants; merchants multi-home across appsAcquirer-level data room; NPCI acquirer reporting under NDA
Actual blended take rateNot disclosed at instrument level in any open sourceManagement take-rate bridge; sample settlement files
CAC and payback by merchant segmentNot observable externally at allCohort files from the target; channel-level spend
Credit loss on UPI-originated lendingVintages too short and not publicStatic-pool loss curves by vintage from the lending partner
Whether the 30% share cap bindsThe enforcement date has moved beforeRegulatory counsel; model the cap as a step function

How this changes the recommendation. The conditional no is robust to all five: none of them makes a 0bps payment fee-bearing. The conditional yes is fragile to the credit-loss question specifically: if UPI-originated loss rates run materially above unsecured norms, the merchant-financing thesis fails and there is no third leg to fall back on. That single unknown is where diligence spend should concentrate.

Scope note

This is a simulation built entirely on public data, to demonstrate diligence structure. It is not investment advice and not a recommendation on any security. One97 Communications appears only as the listed comparable, using its filed figures.