API Integration Integration Types TPAP Integration Integration guide for third-party application providers connecting via sponsor PSP bank.
Aspect Detail Partner Type Fintech or app company using an existing bank's PSP infrastructure App Ownership Partner builds UPI feature within their existing app Integration Mode M2P Android/iOS Headless SDK + optional Direct API M2P Role UPI Switch (via sponsor bank), Profile, Transaction processing Partner Role App UI/UX, UPI feature integration, user engagement
Aspect Bank PSP TPAP NPCI License Bank's own PSP license Operates under sponsor PSP VPA Handle Own handle (@bankname) Sponsor's handle or co-branded CBS Connection Bank's own CBS Sponsor bank's CBS via M2P Settlement Direct NPCI settlement Settlement via sponsor bank Regulatory Bank is directly regulated TPAP regulated via sponsor agreement
TPAP uses the same API set as Bank PSP with these differences:
Phase Difference Auth Setup Same — TPAP gets own credentials Onboarding Same APIs — VPA handle is sponsor's handle Transactions Same APIs — channelCode identifies TPAP tenant VPA/Account Same APIs Mandate Same APIs Disputes Same APIs
Refer to the Bank PSP Integration for the complete API integration order. All endpoints are identical — only the channelCode parameter differentiates the TPAP tenant.
Step Action Details 1 Sponsor bank agreement Sign agreement with existing PSP bank on M2P 2 NPCI TPAP registration Register with NPCI as TPAP, referencing sponsor PSP 3 Credential issuance M2P issues separate credentials under sponsor's tenant 4 SDK integration Same SDK — channelCode differentiates TPAP 5 Onboarding flow Same APIs — VPA created as user@sponsorhandle 6 Testing NPCI UAT with TPAP-specific test cases 7 Go-live Independent of sponsor bank's go-live
# Action Description 1 Sponsor PSP mapping Map TPAP to sponsor bank's PSP configuration 2 TPAP tenant isolation Ensure data isolation between TPAP and sponsor 3 Co-branded handle setup Register TPAP sub-handle with NPCI (if applicable)
