If you're building a product in India in 2026, the best payment infrastructure depends on what you're building. For most businesses, the stack below is a strong default: | Use case | Recommended infrastructure | |---|---| | Consumer payments | **UPI** (primary) | | Recurring payments | UPI AutoPay + eMandates | | Bill payments | Bharat Connect (formerly BBPS) | | Card payments | RuPay, Visa, Mastercard via a payment gateway | | Business bank transfers | NEFT/RTGS/IMPS | | Financial data sharing | Account Aggregator framework | | Lending | OCEN (where supported by ecosystem partners) | | Commerce | ONDC integration (if you're building a marketplace) | ### For most startups A practical architecture is: - **UPI** for 90%+ of customer payments. - A payment gateway (such as Razorpay, Cashfree, PhonePe PG, or PayU) for cards, net banking, and UPI. - **Bharat Connect** for utility bills, subscriptions, and institutional collections. - **Account Aggregator** if your app needs user-consented financial data for lending or personal finance. - **ONDC** only if you want interoperable commerce rather than payments alone. ### If you're building fintech The current India Stack is roughly: - Identity: Aadhaar - Payments: UPI - Bill payments: Bharat Connect (BBPS) - Financial data: Account Aggregator - Lending: OCEN - Commerce: ONDC - Documents: DigiLocker These layers are increasingly designed to work together rather than as isolated services. ### Why UPI remains the default UPI continues to dominate India's retail digital payments. Government data from early 2026 reported over **21.7 billion monthly transactions** in January 2026, with **691 banks** live on the network, making it the foundational payment rail for most consumer and merchant use cases. If you can share **what you're building** (for example, SaaS, marketplace, lending, B2B, e-commerce, or subscription business), I can recommend the most suitable payment architecture and providers for that specific use case.
Brands named