How do we get a FOSS UPI mobile app
summary
Argues that a usable FOSS UPI app is practical by building a clean‑room common library specification that reproduces NPCI device registration and PIN flows, and a separate bank‑backend adapter so one working bank implementation unlocks interoperability across 150+ banks. Demonstrates an Android USSD wrapper for star 99# with limitations (iOS blocks programmatic USSD), publishes specs and a GitHub reference (captn3m0/tabcoin) and says prototypes work but full apps need community implementation and security review.
AI-written summary · about
chapters (16)
- 0:00FOSS UPI app vision
- 1:52Open versus closed UPI
- 3:37Why FOSS UPI for India
- 4:58Challenges in FOSS UPI
- 8:23UPI with banks and NPCI
- 10:49Bank interaction vs third-party
- 11:30USSD and feature phone limits
- 14:16Roadmap to FOSS UPI
- 16:21Starline and hash proposal
- 17:22Library spec for interoperability
- 19:29Current FOSS UPI and next steps
- 20:53Security and regulatory for FOSS banking
- 23:41Patent and legal risks
- 24:43Developer responsibility in FOSS
- 27:08Legal clarity for personal use
- 29:14Audience reactions and future models
related talks
21mHow I Hacked Your Bank Account: A Detailed Look At UPI Security
40mState of UPI - Observations from reluctant observer
14mSecurity and Privacy Advice for UPI Users in India
23mHow UPI and Banking APIs Are Changing the Brokerage Industry
32mEnhancing Security, Reliability, and Global Scalability in FinTech
37mTechnical overview of recurring payments using e-NACH and UPI v2
26mReimagining the Banking Core: APIs as the Digital Fabric of Transformation
25mBuilding an Open Source Payment System