Android prototype · Active development

Nearby checkout,
without the camera.

Discover a shop over Bluetooth, verify the exact request, and approve payment inside the UPI app you already trust.

Signed requestsUPI-native approvalNo PIN collection
01 · DISCOVER

The nearest verified shops rise to the top.

Short-lived BLE signals help the app order nearby requests without broadcasting a customer’s payment details.

02 · VERIFY

A signed request proves what you are about to pay.

The merchant identity, amount, expiry and integrity checks are shown before the payment app opens.

03 · REVIEW

Both sides see who is paying whom.

The payer and merchant UPI IDs remain visible, with the exact amount fixed into the request.

04 · APPROVE

Your trusted UPI app completes the transaction.

UPI Nearby never collects a PIN or claims settlement from a phone callback.

11:24◉ 5G ▰
UPI NearbySecure

NEARBY NOW

Pay the place
in front of you.

CT
Corner Tea8 m · Verified request
₹48
FB
Fresh Basket21 m · Open shop
₹—
Scanning nearby
NearbyActivityProfile
LIVEClosest request foundscroll to explore the flow

01 / THE IDEA

QR made UPI visible.
Bluetooth can make it ambient.

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.

03 / TRY THE MODEL

The closest request earns attention—not automatic payment.

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.
1
Corner TeaVerified · Open shop
8 m
2
Fresh BasketVerified · Exact request
21 m
3
Metro PharmacyVerified · Open shop
38 m

04 / TRUST BOUNDARIES

Designed around what the app should never do.

01

Never collect a UPI PIN

Authentication stays inside the payer’s installed UPI application.

02

Never trust proximity alone

BLE discovers requests. Server signatures establish integrity and expiry.

03

Never infer settlement

A production merchant confirms payment through its acquiring PSP—not a phone callback.

05 / BUILD STATUS

Working prototype.
Honest next steps.

The discovery and signed-request loop works on Android. The remaining path to a pilot is merchant acquisition and authoritative settlement confirmation.

  1. BLE discovery and closest-shop priorityWorking on physical Android devices
  2. Signed amount-bound invoicesLive managed backend and replay protection
  3. Merchant pilot experienceUI refinement, diagnostics and QR fallback
  4. PSP / acquiring-bank integrationVerified merchant VPA, MCC and settlement webhooks

EARLY ACCESS

Building for the counter, one verified step at a time.

UPI Nearby is an upcoming experiment by Anant Goel. Follow the build, review the engineering, or get in touch about a controlled merchant pilot.