November 04, 2026
A UPI TPAP (Third-Party Application Provider) is a non-bank company that offers UPI payments through its own customer-facing app, using a partner PSP bank to connect to NPCI's UPI network. PhonePe, Google Pay and Paytm are the best-known examples. For any fintech or NBFC thinking about launching its own UPI app, 2026 is an unusually relevant year to study how the TPAP model works.
The reason is a deadline. NPCI's rule that no single TPAP should handle more than 30% of UPI transaction volume is currently scheduled to apply to existing providers from 31 December 2026, and the two largest apps are still well above that level on monthly data. This article explains what a TPAP is, where the market stands today, what the cap does and does not change, and how to think about building, white-labelling or integrating UPI.
A TPAP is the app layer of UPI. It designs the user experience, such as scan-and-pay, collect requests, mandates and bill payments, while a PSP bank handles the bank-side connection, and NPCI operates the switch that routes every transaction. Only a bank can act as a PSP, so a fintech company becomes a TPAP by partnering with one and obtaining NPCI's approval.
| Participant | Role in UPI | Examples |
| NPCI | Operates the UPI network, sets the rules, certifies participants and monitors compliance | National Payments Corporation of India |
| PSP bank | Provides the connection to UPI, and handles settlement, authentication and compliance for the apps it sponsors | UPI member banks |
| TPAP | Builds and runs the customer-facing UPI app and the user experience | PhonePe, Google Pay, Paytm |
This is different from a payment aggregator. A TPAP works only on UPI, while a payment aggregator accepts several payment modes such as cards, net banking and wallets on behalf of merchants. Teams weighing the two options may also find LetsFin's guide to choosing a payment aggregator useful.
UPI processed 24.07 billion transactions in September 2026, according to NPCI data reported by MediaNama, after a record 24.51 billion in August. Concentration is still high, but it is easing slowly.
| App | Transactions, Sept 2026 | Share of listed-app volume |
| PhonePe | 10.91 billion | 45.57% |
| Google Pay | 7.71 billion | 32.23% |
| Paytm | 1.94 billion | 8.1% |
PhonePe and Google Pay together held 77.8% of listed-app volume in September 2026, down from 81.9% a year earlier. Navi (1.14 billion transactions) and super.money (405.1 million) were among the newer apps gaining ground. These shares are calculated on the roughly 23.93 billion transactions across NPCI-listed apps, not on the 24.07 billion total across UPI.
NPCI introduced the cap in November 2020 to reduce concentration risk. It limits any single TPAP to 30% of total UPI volume, measured on a rolling three-month basis. Compliance for existing providers that exceed the cap has been pushed back more than once, and the current deadline is 31 December 2026.
Two points are easy to get wrong:
• Monthly share is not the compliance test. The rule measures an app's share of overall UPI volume across the preceding three months. As MediaNama noted, a single month's share of listed-app volume cannot show whether an app has breached the cap.
• The deadline is not guaranteed. It has been extended before, and NPCI has not published an enforcement mechanism that observers can rely on beyond the circular itself. Anyone planning around the cap should track NPCI announcements rather than assume a fixed outcome.
Under NPCI's framework, an existing provider above the cap faces restrictions such as stopping new customer onboarding. What actually happens after 31 December will depend on how NPCI chooses to implement the rule.
The cap is designed to open room for smaller apps, but a rule alone does not move users. For a fintech or NBFC, the more practical question is whether owning the UPI layer makes business sense.
• Lenders are already doing it. ZET, a fintech company built around a fixed-deposit-backed credit card, received its TPAP licence in December 2025 and reported that 75% of its card customers linked their cards to its UPI within 20 days. LIGHT announced NPCI TPAP approval for an app focused on credit for UPI.
• UPI becomes a distribution channel. An app that already holds a customer's attention for credit, savings or bills can add everyday payments and keep that customer engaged.
• Recurring payments sit on the same rail. For lenders, UPI mandates are central to EMI collection, a topic LetsFin has covered in its piece on how UPI AutoPay can fail a borrower at the wrong moment.
None of this means every lender should become a TPAP. Smaller apps start with a very small share of UPI volume, and winning daily payment habits from PhonePe and Google Pay is difficult.
The exact process depends on the PSP bank and on NPCI's current requirements, but vendor guides generally describe a sequence like this:
1. Choose a PSP bank and sign an agreement. NPCI approval flows through this sponsor relationship.
2. Submit the proposal and documents for NPCI's review, including company and financial details and a description of the app.
3. Build or integrate the app against the bank's test (UAT) environment.
4. Complete security audits, typically by auditors empanelled with CERT-In, and fix any findings.
5. Clear NPCI's testing, move through pre-production, and receive go-live permission.
6. Integrate the production setup and launch, then maintain ongoing compliance.
Several vendor guides estimate that approval takes a few months from a complete application, but timelines vary widely with the PSP bank, the audit cycle and how ready the app is. NPCI has also issued a multi-bank framework that lets large tech players connect to UPI through more than one PSP bank, which is relevant for apps expecting meaningful scale.
Not every business that wants UPI needs its own TPAP. The right model depends on how central UPI is to your product.
| Option | Best when | Trade-off |
| Build your own TPAP | UPI is core to your product and you have a long-term volume plan | Highest control, but the longest timeline, audit burden and ongoing compliance cost |
| White-label TPAP technology | You want your own branded UPI app without building the stack from scratch | Faster launch; you depend on the technology partner's roadmap and PSP bank relationships |
| Integrate UPI through an existing provider | You mainly need to collect or pay, not run a consumer UPI app | Lowest effort; limited branding and less control over the UPI experience |
• Which PSP banks they work with, and whether a multi-bank setup is supported as you scale
• Support for the UPI features your product needs, such as collect, mandates and recurring payments
• How they handle security audits, NPCI certification and data-localisation requirements
• Uptime, failover design and incident handling, since UPI users notice failures immediately
• Visibility into your own volume trends, so you can plan against NPCI's share thresholds as you grow
• A clear commercial model, covering integration fees, per-transaction charges and exit terms
LetsFin's UPI TPAP listing lets you compare technology partners for this layer side by side instead of negotiating with each one separately. If you are also weighing card and net-banking acceptance alongside UPI, LetsFin's payment aggregator guide covers how to evaluate that decision, and the UPI AutoPay article covers the recurring-collections side.
What does TPAP stand for in UPI?
TPAP stands for Third-Party Application Provider. It is a non-bank company that offers UPI payments through its own app by partnering with a PSP bank and obtaining NPCI's approval.
Can fintech be a PSP?
No. Only a bank can be a PSP. A fintech company participates in UPI as a TPAP, working through a PSP bank.
What is the 30% UPI market share cap?
It is an NPCI rule that limits any single third-party app to 30% of total UPI transaction volume, measured on a rolling three-month basis. The deadline for existing providers above the cap is currently 31 December 2026.
Will PhonePe and Google Pay be affected on 31 December 2026?
Both had monthly shares above 30% of listed-app volume in September 2026, but the rule is measured differently, and the deadline has been extended before. The practical outcome depends on NPCI's enforcement, which has not been fully spelled out publicly.
How is a TPAP different from a payment aggregator?
A TPAP operates only within UPI and runs the consumer app. A payment aggregator accepts multiple payment modes, such as cards, net banking and wallets, on behalf of merchants.
How long does it take to launch a UPI app?
It varies. Vendor guides commonly cite a few months from a complete application, but the PSP bank, security audits and NPCI's testing all affect the timeline.
The TPAP model is how non-bank companies reach UPI, and the 30% cap is NPCI's attempt to keep that layer from concentrating further. Whether the rule reshapes the market after 31 December 2026 is still an open question, but the decision for lenders and fintechs does not have to wait for it: work out how central UPI is to your product, then choose between building, white-labelling or integrating. Compare UPI TPAP technology partners on LetsFin to see your options in one place.