API Integration
Overview
Unified cross-GTM integration reference — understand how each partner type integrates with the M2P UPI Platform.
This guide provides a unified, cross-GTM comparison of how each type of M2P UPI partner integrates. Choose your integration model below.
GTM Integration Models
Integration Model Summary
| GTM | Who Builds the App | Integration Mode | Partner Calls APIs | M2P Handles NPCI | Needs SDK |
|---|---|---|---|---|---|
| Bank PSP | Partner (bank's own app) | SDK + API | ✅ All UPI APIs | ✅ Full switch | ✅ Required |
| TPAP | Partner (existing app) | SDK + API | ✅ All UPI APIs | ✅ Full switch (via sponsor) | ✅ Required |
| PPI | Partner (wallet app) | SDK + API | ✅ UPI + Wallet APIs | ✅ Full switch | ✅ Required |
| Issuer Host | No customer app | CBS Adapter (M2P → Bank CBS) | ❌ Bank exposes CBS APIs | ✅ Issuer switch | ❌ N/A |
| Acquirer Host | Partner (merchant portal) | MMS API | ✅ Merchant/MMS APIs | ✅ Acquirer switch | Optional |
Integration Direction
Understanding who calls whom is critical:
In Issuer Host, the direction is reversed — M2P calls the partner, not the other way around.
Integration Channels by GTM
| Channel | Bank PSP | TPAP | PPI | Issuer Host | Acquirer |
|---|---|---|---|---|---|
| Android SDK (Headless) | ✅ Primary | ✅ Primary | ✅ Primary | ❌ N/A | ⚠️ Merchant SDK |
| iOS SDK | ✅ Primary | ✅ Primary | ✅ Primary | ❌ N/A | ⚠️ Merchant SDK |
| Direct REST API | ✅ Available | ✅ Available | ✅ Available | ❌ N/A | ✅ Primary |
| CBS Adapter | ❌ N/A | ❌ N/A | ❌ N/A | ✅ Primary | ❌ N/A |
| Webhook Callbacks | ✅ Required | ✅ Required | ✅ Required | ✅ Notifications | ✅ Required |
| Admin Portal | ✅ Included | ✅ Included | ✅ Included | ✅ Included | ✅ Included |
| UAM Portal | ✅ Separate | ✅ Separate | ✅ Separate | ✅ Separate | ✅ Separate |
SDK vs Direct API
| Factor | Use SDK | Use Direct API |
|---|---|---|
| Mobile app | ✅ Recommended | ⚠️ Possible but harder |
| Device binding & SIM auth | ✅ Required (SDK handles it) | ❌ Not possible |
| Encryption/key exchange | ✅ SDK handles ECDH + AES | ⚠️ Partner must implement |
| Server-to-server | ❌ N/A | ✅ Required |
| Web application | ❌ No web SDK | ✅ Use APIs |
| Merchant portal / MMS | ❌ N/A | ✅ Use APIs |
API Applicability by GTM
| API Category | Bank PSP | TPAP | PPI | Issuer Host | Acquirer |
|---|---|---|---|---|---|
| Profile / Onboarding | ✅ | ✅ | ✅ | ❌ | ❌ |
| VPA Management | ✅ | ✅ | ✅ | ❌ | ❌ |
| Account Linking | ✅ | ✅ | ❌ (wallet) | ❌ | ❌ |
| Send Money (P2P) | ✅ | ✅ | ✅ | ❌ | ❌ |
| Pay Merchant (P2M) | ✅ | ✅ | ✅ | ❌ | ❌ |
| QR Scan & Pay | ✅ | ✅ | ✅ | ❌ | ❌ |
| QR Generation | ❌ | ❌ | ❌ | ❌ | ✅ |
| Mandate / AutoPay | ✅ | ✅ | ✅ | ❌ | ✅ |
| Delegate Payment | ✅ | ✅ | ❌ | ❌ | ❌ |
| Dispute / Complaint | ✅ | ✅ | ✅ | ✅ | ✅ |
| CBS Adapter Ops | ❌ | ❌ | ❌ | ✅ | ❌ |
| Merchant Mgmt (MMS) | ❌ | ❌ | ❌ | ❌ | ✅ |
NPCI Collect Deprecation
NPCI has sunset P2P collect requests on Android devices effective February 28, 2026. New integrations should use intent-based payments.
Choose Your Integration Guide
Bank PSP Integration
Full PSP integration for banks with own UPI app
TPAP Integration
Third-party app integration via sponsor PSP
PPI Integration
Wallet / prepaid instrument UPI integration
Issuer Host Integration
Bank-side CBS adapter integration
Acquirer Host Integration
Merchant management and acquiring integration
Sequence Diagrams
Visual API and webhook flows per use case
