$129.1B
India's inbound remittances in 2024 — the highest single-year inflow ever recorded for any country
World Bank Migration & Development Brief, December 2024
14.3%
Of global remittances flowed to India in 2024 — highest share for any country since 2000
World Bank, December 2024
$179T
Global cross-border payments value in 2024. India is among the most active corridors on SWIFT.
McKinsey Global Payments Map, 2024
INDIA'S BANKING FOOTPRINT
12
Public sector banks
21
Private sector banks
44
Foreign banks operating in India
223
SBI's correspondent banks across 55 countries
RBI compilation, August 2025; SBI Annual Report FY24-25
Every cross-border payment carries an address.
Every address must clear SWIFT validation by November 2026.
Every address must clear SWIFT validation by November 2026.
A REAL INDIAN ADDRESS
"Flat 302, Sai Krupa CHS, Near Hanuman Mandir, opposite petrol pump, behind SBI ATM, Malad East, Mumbai 400097"
No street name. No building number. Landmarks instead.
SWIFT CBPR+ REQUIRES (NOV 2026)
✗ REJECTED
<PstlAdr>
<AdrLine>Flat 302, Sai Krupa CHS...</AdrLine>
</PstlAdr>
<AdrLine>Flat 302, Sai Krupa CHS...</AdrLine>
</PstlAdr>
✓ ACCEPTED
<PstlAdr>
<PstCd>400097</PstCd>
<TwnNm>Mumbai</TwnNm>
<CtrySubDvsn>Maharashtra</CtrySubDvsn>
<Ctry>IN</Ctry>
</PstlAdr>
<PstCd>400097</PstCd>
<TwnNm>Mumbai</TwnNm>
<CtrySubDvsn>Maharashtra</CtrySubDvsn>
<Ctry>IN</Ctry>
</PstlAdr>
WHEN PAYMENTS FAIL — VERIFIED COSTS
2-5%
Of cross-border payments result in exceptions on any given day
80%
Of bank back-office expenditure consumed by exception handling
$20M+
Annual cost for largest banks in slow, fragmented investigations
5-10
Days typical resolution time per investigation
SWIFT 2025 reports; SunGard/Sibos research; Pega/SWIFT analysis
The address SWIFT requires does not exist in Indian addresses.
It must be inferred, resolved, and structured — for millions of addresses, in seven months. Every Indian bank faces the same problem at the same time.
Tap an address. Watch the engine resolve it.
DIGIPIN · LAUNCHED MAY 27, 2025
A 10-character geo-coded digital address for every 4×4 metre of India.
Built by India Post with IIT Hyderabad and ISRO's NRSC, under the DHRUVA framework. Open-source. Already published. Ready for integration.
Press Information Bureau, May 2025; India Post DIGIPIN page
THE UPI PARALLEL
UPI did not become national infrastructure when NPCI announced it. It became infrastructure when it was integrated into every bank's app, when RBI mandated interchange, when daily volumes crossed a threshold.
DIGIPIN is at UPI's pre-2017 stage today. Launched. Policy backed. Not yet locked into national financial infrastructure.
The November 2026 SWIFT deadline is the use case that locks it in.
UPI WENT GLOBAL — DIGIPIN CAN TOO
UPI is now operational or piloted in:
Singapore
UAE
France
Mauritius
Sri Lanka
Bhutan
Nepal
Project Nexus (4 ASEAN)
SWIFT, BIS Project Nexus documentation, 2024-2026
INDIA POST BRINGS WHAT WE CANNOT BUILD ALONE
→
Delivery beat data — the rural addresses no commercial geocoder has, accumulated over 154,000 post offices
→
DHRUVA framework — operationalises AVA registration as live infrastructure
→
DIGIPIN integration — threaded into every cross-border payment leaving India
→
Bank CEO relationships — institutional gravitas that compresses 6-month sales into a phone call
WHAT WE ARE BUILDING
India's address resolution layer for cross-border banking compliance.
A production-grade engine that converts unstructured Indian addresses into ISO 20022 PostalAddress24 — the format SWIFT will require from November 2026. Built on five independent resolution paths, deterministic where SWIFT's own AI is probabilistic, and designed from day one to integrate with India Post's DIGIPIN as the geocoding standard.
CURRENT STATE OF THE ENGINE
4,050
Lines of Python
production code
production code
94
Tests passing
zero failures
zero failures
< 5ms
Per address
cached resolution
cached resolution
5
Independent
resolution paths
resolution paths
WHY THIS IS THE MOMENT FOR INDIA POST
The November 2026 SWIFT deadline is the largest commercial use case DIGIPIN will see in its first decade. Every Indian bank will need a CBPR+ compliance solution. The resolution layer they choose becomes embedded in their core banking systems for years.
An Indian solution with India Post at the centre — or a foreign vendor by default. The window to choose is approximately seven months.
A GOLDEN OPPORTUNITY — STARTING WITH MAHARASHTRA CIRCLE
Mumbai is India's financial capital. Every major Indian bank, every foreign bank operating in India, has its cross-border payment operations centred here. Maharashtra Circle is uniquely positioned to lead this initiative — not as a regional pilot, but as the operational anchor for a national rollout.
Starting in Maharashtra means starting where the volume is, where the banks are headquartered, and where the impact compounds fastest into national infrastructure.
A PROPOSED PATH FORWARD
1.A first conversation — we bring the working demo to your office
2.Working session with Maharashtra Circle technical and policy teams
3.Joint identification of two or three pilot Mumbai-headquartered banks
4.MoU expansion building on the existing Dak-Vani relationship
5.DIGIPIN integration threaded through every CBPR+ compliant message
A national infrastructure moment,
starting in Maharashtra.
starting in Maharashtra.