Live · 2026
qrbaton
Your agent shops on a desktop. You pay with one tap.
Problem
AI agents can browse and fill a cart, but a UPI QR on a desktop is a dead end: the agent can't pay it, so you end up screenshotting and relaying it to your phone by hand.
Build
A tiny Next.js service with an MCP tool and a plain HTTP endpoint. It decodes the QR server-side, wraps the cart and bill in a review page, and deep-links into GPay, PhonePe or Paytm pre-filled. Status is polled live and reported back to the agent through signed webhooks.
Result
One tap from agent to payment, with no accounts or keys. Links expire on their own and the app never touches money; the UPI app shows the real payee before the PIN.
Highlights
- Reads any UPI QR — screenshots, phone photos or crops — decoded on the server
- Closes the loop with live status, an “I've paid” button and signed webhooks
- On a laptop, the pay page shows a fresh QR to scan with your phone
- No keys, no accounts: one HTTP call or MCP tool, and links expire on their own
Stack
- Next.js
- TypeScript
- MCP
- UPI