The gap nobody is building for

340 Million People.
Zero Tooling.

India has the world's best payment network. And the world's biggest gap between who can receive money and who can do anything useful with it.


Last year, UPI processed 131 billion transactions. One hundred and thirty-one billion. A number so large it's almost decorative, until you look at who is behind it.

NPCI's merchant ecosystem has roughly 350 million registered UPI receivers. Payment aggregators - Razorpay, Cashfree, PayU, all of them combined - serve somewhere between 10 and 12 million registered merchants.

340MUPI receivers transacting every day
with no tooling, no records, no automation around their payments.

That is not a rounding error. That is the entire point.

Why does this gap exist?

This is the question worth asking before building anything. Because a gap this large, sitting on top of infrastructure this good, doesn't persist by accident. There's a concrete reason for it.

Every payment solution ever built in India has assumed one thing at the merchant end: a registered business. GST number. Current account. Minimum transaction volume to justify onboarding. A technical team to integrate an API.

Those aren't arbitrary product decisions. They're legal requirements for licensed Payment Aggregators under RBI's guidelines. KYC is mandated under PMLA. Settlement floats exist for fraud protection. The fees charged by aggregators aren't greed - UPI MDR was set to zero in 2020. What they charge is for the value-added layer on top: reconciliation, fraud scoring, checkouts, refunds.

"The system works exactly as designed. It just wasn't designed for everyone."

Below the formal threshold, outside the registered business layer, there is nothing. Not bad products. Nothing.

Three problems nobody is solving

Apps like AutoAlert proved merchants want this - a million downloads just for a voice alert when payment arrives. Nobody built what comes next.

The Digital Delivery Problem

India has an explosion of solo digital sellers - coaching notes, astrology reports, PDFs, resume templates, local recipe books. They sell via WhatsApp and Instagram. Payment happens on UPI. Delivery is manual, delayed, and entirely dependent on the seller being online. There is no automated digital fulfillment layer that doesn't require a payment gateway. For every sale, someone is waiting.

The Reconciliation Problem

A temple receiving 200 UPI donations on a Saturday is manually checking a phone screen. No receipts. No donor records. No 80G certificate generation. No goal tracking. This affects every religious institution, NGO, community fund, and local charity in India, which is an enormous number. The money arrives. The paper trail doesn't.

The Friction Cost Problem

You can register for GST voluntarily, even below the INR 40 lakh threshold. But voluntary registration means mandatory monthly return filing, compliance overhead, and ongoing accounting costs that make no economic sense for a home baker, a solo creator, or a community fund with irregular income. The formal system doesn't lock them out. It just asks too much in return for too little.

The insight behind SeedhaPe

Going back to first principles: what does every UPI receiver already have that no gateway can improve on?

A notification.

When money arrives on any UPI ID - personal, merchant, anything - the app sends a push notification. That notification contains everything: amount, sender VPA, transaction reference ID, timestamp. A licensed Payment Aggregator isn't giving you any information that notification doesn't already contain.

The key insight: If you're not aggregating funds - if the merchant's own UPI ID receives the money directly - you don't need a PA license. You're not in the payment flow. You're just the intelligence layer sitting on top of a notification.

SeedhaPe listens to those notifications using Android's NotificationListenerService, matches incoming payments to pending orders, and auto-fulfills them. No gateway. No API integration. No regulatory surface area beyond what the merchant already has.

How it works

01
Merchant creates an orderA digital product, a donation link, a service booking, anything with a price attached.
02
Customer pays on any UPI appTo the merchant's own UPI ID. No redirect. No checkout page required.
03
Notification firesSeedhaPe reads the incoming payment notification in real time.
04
Auto-fulfillment triggersProduct delivered. Receipt sent. Record created. In seconds, automatically.

What this actually unlocks

SeedhaPe is the first proof of concept. The bigger vision is a full financial operating system for India's pre-formal economy - reconciliation, receipts, digital delivery, donor management, basic analytics - all triggered by a notification, not a license.

Starting exactly where every existing solution stops.

The 340 million aren't underserved because the problem is technically hard. They're underserved because every product was built looking up, toward enterprise, toward scale, toward the registered merchant with a current account and a dev team. Nobody built looking sideways at the person transacting right now, rationally outside the formal system, with nothing around it.

That's the gap. And it's the most interesting gap in Indian fintech right now.

Built for the 340 million.

SeedhaPe is in early access. If you're a solo creator, a small community, an NGO, or anyone receiving UPI payments with no tooling around it, we're building for you.

Join the waitlist