u/0xViking

Hey Guys!

I have been building door@ since last week. Trying to solve last mile addressing, It is a human layer for address sharing.

You can choose you doora handle(eg: praneeth@home, praneeth@gym, praneeth@office, etc.,) and share it with any friend, delivery guys, etc.,

It will remain free for users.

It solves the the issue what Dr.Santanu B written in the "Automated Systems to Solve India’s $10B+ Addressing Problem" article.

It sits on top of DIGIPIN which is developed by India Post in collaboration with IIT Hyd.

We start in India — where the address problem is sharpest — but the primitive works anywhere addresses are unstructured in the world. DIGIPIN does support geo coding worldwide.

Really need honest opinion from you guys on this!!

Please check it out.

Ever stood at a checkout counter opening 3 different UPI apps just to see which one has a grocery cashback today? Yeah, me too.

So, I built ORBIT UPI 🪐

It’s a lightning-fast, zero-backend UPI payment router designed to eliminate friction and maximize your rewards.

What it does today:
📱 Scan & Select: Scan any UPI QR code right from your browser and jump instantly into your app of choice.
🔒 100% Local & Private: No backend. No servers. No tracking. Every transaction log is stored entirely on your local device browser.

The Future Vision (Smart Routing):
🧠 Cashback Optimization: ORBIT will read the Merchant Category (MCC) and auto-suggest the app with the best active cashback.
⚡ Downtime Bypassing: If a bank network is down, ORBIT will hide the failing apps and route you to the most stable one.
But I’ve hit a massive technical roadblock, and I need the fintech ecosystem's help.

While ORBIT’s deep-linking works perfectly with apps like CRED, I am being completely blocked by the heuristic engines of other major players.

🛑 The Issue: When ORBIT passes a standard, strictly formatted P2P intent, apps are throwing "Security Risk" errors simply because the intent originates from a web browser.
🚧 The Barrier: I understand the need to prevent phishing, but the only official "fix" right now is to register as a corporate merchant and integrate a heavy Payment Aggregator SDK just to generate a signed intent.

Question for the engineering/product teams at Phonepe, Gpay, CRED, PAYtm:
How can independent developers build legitimate, secure web-to-app routing utilities without being forced into an enterprise merchant flow?
Is there a modern standard or an intent structure for local-only tools to trigger user-initiated payments without hitting security blockades?
Would love any technical suggestions, intent string workarounds, or feedback from the community!

#UPI #FINTECH