Discover
Nearby merchants broadcast short-lived BLE handles—not account details.
Discover a shop over Bluetooth, verify the exact request, and approve payment inside the UPI app you already trust.
01 / THE IDEA
For a busy counter, opening a scanner, finding the code, framing it and waiting for recognition is small friction repeated all day. UPI Nearby explores a faster discovery layer while leaving the regulated payment rail untouched.
02 / PAYMENT FLOW
Nearby merchants broadcast short-lived BLE handles—not account details.
The payer reads a signed, expiring request containing the payee and amount.
Both parties are shown before handoff. Replays and altered requests are rejected.
The selected UPI app performs authentication and the bank transaction.
03 / TRY THE MODEL
Signal strength helps order the list. The customer still sees the merchant and amount and must explicitly continue.
This illustrates prioritization; BLE distance is an estimate, not a precise measurement.04 / TRUST BOUNDARIES
Authentication stays inside the payer’s installed UPI application.
BLE discovers requests. Server signatures establish integrity and expiry.
A production merchant confirms payment through its acquiring PSP—not a phone callback.
05 / BUILD STATUS
The discovery and signed-request loop works on Android. The remaining path to a pilot is merchant acquisition and authoritative settlement confirmation.
EARLY ACCESS
UPI Nearby is an upcoming experiment by Anant Goel. Follow the build, review the engineering, or get in touch about a controlled merchant pilot.