m2pfintech
API Integration

Integration Flows

Visual API and webhook flow diagrams for all major UPI operations — onboarding, payments, mandates, disputes.

Visual flows for all major UPI operations showing synchronous API calls and asynchronous webhook notifications.

Solid arrows (──▶) = synchronous API call. Dashed arrows (--▶) = asynchronous webhook/callback. All webhooks use the NotificationRequestDtoV2 format.

User Onboarding

Goal: Register a new user, bind device, create UPI ID, link bank account, set UPI PIN.

No webhooks during onboarding — all steps are synchronous request-response. VPA creation happens before bank account linking.

P2P — Send Money

Goal: User sends money to another UPI ID with debit-credit cycle and webhook notifications.

Key points:

  • API response is synchronous — returns SUCCESS or PENDING (code UPI_007)
  • If UPI_007: final result arrives via webhook; can also poll checkTxnReq
  • rrn is the primary reconciliation key across both webhooks
  • PIN is RSA-2048 encrypted in the request (SDK handles encryption)

P2M — Pay Merchant

Mandate — Create AutoPay

Mandate — Pre-Debit & Execution

Delegate Payment (UPI Circle)

Dispute — Raise & Track

PPI Onboarding (M2P as PPI Provider)

Issuer Host — Incoming Payment (Credit)

Issuer Host — Auto-Reversal

Encryption & Key Exchange

AES-256 payload encryption and RSA-2048 session key exchange for secure API communication.

Bank PSP Integration

Step-by-step integration guide for banks building their own UPI app as a Payment Service Provider.

On this page

User Onboarding
P2P — Send Money
P2M — Pay Merchant
Mandate — Create AutoPay
Mandate — Pre-Debit & Execution
Delegate Payment (UPI Circle)
Dispute — Raise & Track
PPI Onboarding (M2P as PPI Provider)
Issuer Host — Incoming Payment (Credit)
Issuer Host — Auto-Reversal