About ShantiPe

Banking reaches further when it already has a shop on the corner

ShantiPe is a retail fintech portal built for the people who already serve their neighbourhood — the mobile shop, the kirana, the travel agent — and gives them what they need to serve it as a banking point too.

Why we built it

A branch is far. The shop is not.

For a large part of India, the nearest bank branch is a bus ride and half a day’s wages away, while the nearest shop is a two-minute walk. The technology to close that gap already exists — Aadhaar authentication, UPI, IMPS, BBPS. What was missing was a counter-grade way to put all of it in one place, on one wallet, for a shopkeeper who is not a banker.

That is what ShantiPe is. Not a wallet app and not a bank — the operating layer a small retailer runs their counter on, and the distribution network that supports, funds and supervises them.

What the counter replaces

Per visit
Trip to the branchTravel, queue, half a day
Removed
ATM cardFingerprint instead
Not needed
Smartphone & dataThe retailer’s device serves
Not needed
Banking hoursShop hours, six days
Extended
How we build

Six things we refuse to get wrong

Money moves through this portal in both directions, in cash, in front of a customer. That constrains almost every decision in it.

Never show money that isn’t there

A transaction is called successful only when the bank confirms it, never when it was merely sent. Pending stays visibly pending — so you know when not to hand over cash.

Fewest fields that still make it safe

Someone is standing at the counter waiting. Every field on the screen has to earn its place against the time it costs.

Real locks, not hidden buttons

Leaving something off a menu is not security. Service approvals, KYC and tier rules are enforced for real, so what you have not been cleared for simply does not open.

Every rupee has a row

Every transaction keeps the bank’s own reference number. A dispute three weeks later is settled with a record, not somebody’s memory.

A double-tap is not a double payout

Patchy connectivity is the normal case here, not the rare one. The portal is built assuming the line will drop mid-transaction, and works hard to make sure that does not turn into a second payment.

Support in the retailer’s language

The person at the counter is accountable to their customer. When something breaks, they need a human who can explain it, not a ticket number.

How the network runs

Four tiers, each with a job

A retailer cannot be left to fund themselves and troubleshoot alone, and head office cannot know ten thousand counters personally. The tiers exist so that float, onboarding and support all have a nearby owner.

Tier 1

State Head

Owns a state. Appoints master distributors, allocates float into the region and answers for its performance.

Tier 2

Master Distributor

Runs a cluster of distributors. Pushes float down and settles commission up.

Tier 3

Distributor

Onboards retailers, approves their fund requests and is the first call when a counter has a problem.

Tier 4

Retailer

The counter itself, and the only tier that transacts with the public.

0Services at the counter
0Network tiers
0Certified devices
6Days a week support
Join the network

Run a counter, or build a region

Retailers, distributors, master distributors and state heads all start the same way — a conversation about the territory you cover.