Company
Product Requirements
Defines what Auron is building, for whom, and the technical requirements that are non-negotiable. Phase 1 scope only.
Problem
India has 350M+ UPI users and one of the most active real-time payment networks on earth. Crypto holders in India — freelancers paid in USDC, developers earning in stablecoins, Web3 users — cannot spend their assets in the real economy without going through centralized exchanges, 2–5 day settlement delays, and high withdrawal fees.
On the other side: merchants cannot accept crypto even if they wanted to. They have no wallet, no node, no tolerance for volatility. UPI is their entire payment reality.
The gap: no programmable, developer-accessible layer that connects stablecoin holders to the UPI economy — with proper verification, state tracking, and failure recovery.
Target users
Crypto-native consumers
Hold USDC/SOL from freelancing, DeFi, or airdrops. Want to spend it without cashing out to a bank first. Have Phantom installed.
Web3 developers
Building payment flows on Solana. Need a settlement API they don't have to build from scratch. Want TypeScript SDK + webhooks.
AI agent builders
Building autonomous agents that need to initiate real-world financial transactions. Need machine-readable APIs with spend limits and idempotency.
Indian merchants
Already on UPI. Don't know or care about crypto. Just want to get paid. Auron is invisible to them.
Phase 1 features
Must have
✓AI natural language intent parsing (Claude Sonnet)
✓QR scanner — decode UPI QR, extract merchant details
✓Live FX quote with 60-second TTL and price guard
✓USDC transfer via Phantom (desktop + mobile deep link)
✓7-step on-chain transaction verification
✓INR settlement via OnMeta (primary) + Razorpay X (fallback)
✓14-state payment lifecycle with immutable audit trail
✓Failure classification + auto-refund engine
✓Replayable SHA-256 receipts at /api/receipt/:id
✓6-layer security: risk scoring, spend ceiling, scam detection, argon2id PIN
✓Idempotency — safe retries, no double settlements
✓Solana Blinks — composable pay links
Out of scope for Phase 1
—Multi-currency support (USDT, EURC) — Phase 2
—Batch payouts / scheduled transfers — Phase 2
—Cross-chain abstraction (Ethereum, Base) — Phase 3
—AI-managed autonomous treasury — Phase 3
—RWA yield products — Phase 4
Technical requirements
Settlement atomicity
Both ledger record and settlement row must update together — no partial state
Idempotency
Every payment endpoint must accept idempotency keys and return cached results on replay
No fund loss on failure
Any terminal failure triggers automatic USDC return to user's on-chain wallet
Audit completeness
Every state transition must be recorded in status_history with timestamp and reason
Server-side secrets
No private keys, API keys, or treasury credentials may appear in client bundles
Quote integrity
Server rejects settlements where live FX rate has moved >150 bps from quoted rate
Replay protection
A settled transaction signature must never trigger a second settlement
NOTEThese requirements are non-negotiable and enforced in code — not just documented. Each one has a corresponding test path in the settlement worker or verification layer.