The Profitability Moat: Architecting the Sustainable Digital Bank
The Most Interesting Number in Indian Fintech Isn’t 139%
Everyone will quote the headline: net profit up 139%. I want to talk about the ₹124.5 crore sitting quietly in the middle of that release.
A 9% Revenue Year and a 139% Profit Year
Airtel Payments Bank closed Q2 FY27 with ₹28.2 crore net profit against ₹11.8 crore a year earlier, on revenue of ₹875.5 crore – up just 8.9%. EBITDA rose 39.4% to ₹124.5 crore, with 3.1 crore monthly transacting users, ₹4,385 crore in customer balances, a 5-lakh merchant network and 70 lakh NCMC cards issued. It was the only profitable payments bank in the quarter, as a rival slipped into the red under identical regulations.
That Gap Is the Architecture, Not the Marketing
A 9% revenue line producing a 139% profit line is textbook operating leverage – and operating leverage is an engineering outcome, not a finance one. Once the ledger, KYC, onboarding, settlement and reconciliation layers are built, the marginal cost of serving transaction number ten crore is close to zero. The strategic question every CTO should ask is uncomfortably simple: does adding your next thousand customers add headcount, or does it add load on a system you already amortised?
Percentage growth off a small base is easy. Sustaining absolute profitability inside a regulatorily squeezed margin is the real achievement, and it’s the one worth studying.
The Balance Sheet Is the Product
Here’s the constraint most people skip: a payments bank cannot lend. Revenue therefore has to come from fee income plus float income on customer deposits. That means ₹4,385 crore of customer balances is not a vanity metric – it is the business model. And a stored-value ledger carries a non-negotiable architectural covenant: availability and integrity are the same thing. A thirty-minute settlement outage doesn’t cost a sale; it costs the presumption of correctness.
That’s the argument for deliberately unglamorous design – active-active multi-region settlement, idempotent APIs, immutable append-only ledgers, and continuous reconciliation at scale. Boring, expensive, invisible. Also the only thing standing between you and a trust event.
Where Cost-Per-Transaction Goes to Die
Look at where the volume actually happens: transit tap-ins, AePS withdrawals, small remittances. Highest frequency, lowest ticket size, worst possible environments – patchy connectivity, feature phones, semiliterate users. You cannot brute-force this with infrastructure spend; you have to design it down to fractions of a rupee per transaction. That frugal muscle, once built, subsidises everything else you attempt. And note the competitive signal: when two players run the same rails, the same KYC rules and the same caps, the differentiator is operational discipline. Not product.
The Northeast Needs Endpoints, Not New Rails
I have argued this repeatedly in state technology forums: Assam and the hill states don’t need a separate financial infrastructure. AePS, UPI and NCMC already reach here. What’s thin is the last endpoint – merchant acceptance in district towns, local-language UX, and assisted-digital models that work when confidence in a screen is low. Inflow remittances into the Northeast are substantial; capture is weak because the acceptance layer is weak. That is an integration and design problem, squarely in our industry’s hands.
What I’d Tell a CTO
- Measure cost-to-serve per transaction. If you can’t, you don’t yet know your business model.
- Treat availability as a financial line item, not an SLO in a dashboard.
- Assume your hardest users are your best architects – design for the weakest device and connection first.
- Optimise the operating leverage curve deliberately; scale without it is just expensive growth.
- In regulated, commoditised markets, operations is the moat.
A closing thought: the flashy numbers tell you how fast a business is running. The dull ones – margins, float, cost per transaction – tell you whether the machine underneath can carry it further. Build accordingly.
About the Author: Sanjeev Sarma is the Founder Director and Chief Software Architect at Webx Technologies. With a core focus on Generative AI integration, Cloud-Native Scalability, and Enterprise Software Architecture, he has spent over two decades driving digital transformation across Northeast India and beyond. Beyond his corporate leadership, Sanjeev is deeply invested in shaping the future of the IT industry. He serves as an Industry Expert on the Board of Studies for Assam Don Bosco University’s School of Technology, advises state technology committees, and actively mentors emerging tech startups at STPI. He brings a unique, dual perspective of high-level enterprise execution and future-ready academic curriculum development.