Learning · 2026-09-20 · 5 min read
Offline-first payments: what Nepal needs when the internet drops
How digital payments could keep working without conventional internet — device-to-device links, local processing, and syncing later. Notes from NexPay concept research.
In much of Nepal, internet connectivity is not something you can assume. It drops in remote areas, slows during monsoon disruptions, and vanishes entirely in emergencies. Yet almost every digital payment system is designed as if the network never fails. That mismatch is what my NexPay concept research is about.
The core idea: transact now, sync later
An offline-first payment flow has three phases. First, two devices agree on a transaction directly — over QR codes, for example — with no server in the loop. Second, each device stores a signed local record. Third, when connectivity returns, both records sync against each other and reconcile.
None of this is a finished product. It is a research concept I am exploring honestly, one question at a time.
Why QR codes fit
QR codes need nothing but a screen and a camera — no pairing, no accounts on the same network, no special hardware. For a student-built prototype, that makes them the natural carrier for small offline transaction payloads.
The hard part is trust, not transport
Moving bits offline is easy. Knowing the money is real is hard. Double-spending, forged records, and replayed QR codes are the first threats any offline design must answer — with cryptographic verification ideas, spending limits, and secure reconciliation rules.
An offline payment system that cannot prove what happened is just two people disagreeing with extra steps.
What I am deliberately not claiming
This is not a wallet you can download, not a licensed payment system, and not handling anyone's real money. It is a learning project: Android and Kotlin concepts, Jetpack Compose sketches, local storage experiments, and lots of reading.
Why this matters for Nepal
Markets, buses, rural shops, disaster relief — these are exactly the places where connectivity fails and where being able to transact anyway would matter most. Designing for the worst network, not the best, is the whole point.
Follow the work
The concept lives at /nexpay with its features, roadmap, and documentation notes. Questions welcome through /contact.
Jitesh Prakash — teen tech creator writing about coding, AI, and cybersecurity.