MyPursu API Integration & UPI OpenData Solutions

1. Session Authentication

// Step 1: Obtain access token via device + user credentials
POST https://do.api.mypursu.com/login
Content-Type: application/json

{
  "mobile": "+1-555-0100",       // intl. number
  "password": "<USER_PASS>",
  "device_id": "<DEVICE_FINGERPRINT>",
  "platform": "android"
}

// Response:
{
  "access_token": "<JWT>",
  "refresh_token": "<REFRESH>",
  "expires_in": 3600,
  "kyc_status": "verified",
  "wallet_id": "WLT_XXXXXXXXXX"
}

2. UPI Transaction History Query

// Fetch paginated UPI transaction history
GET https://do.api.mypursu.com/v1/transactions
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

// Query params:
?from_date=2025-01-01
&to_date=2025-03-31
&type=UPI_QR,UPI_ID
&status=SUCCESS
&page=1&page_size=50

// Response item:
{
  "txn_id": "TXN_20250312_001",
  "upi_id": "merchant@upi",
  "amount_inr": 850.00,
  "source_currency": "USD",
  "fx_rate": 83.45,
  "rrn": "123456789012",
  "status": "SUCCESS",
  "timestamp": "2025-03-12T09:14:22Z",
  "merchant_name": "Spice Route Restaurant",
  "qr_type": "STATIC"
}

3. Wallet Balance & Fund-Load Records

// Query wallet balance snapshot
GET https://do.api.mypursu.com/v1/wallet/balance
Authorization: Bearer <ACCESS_TOKEN>

// Response:
{
  "wallet_id": "WLT_XXXXXXXXXX",
  "balance_inr": 14250.00,
  "ppi_limit_inr": 200000.00,
  "kyc_tier": "full_kyc",
  "updated_at": "2026-04-23T08:00:00Z"
}

// Fund-load history endpoint:
GET https://do.api.mypursu.com/v1/wallet/loads
?from_date=2025-01-01&page=1

// Response item:
{
  "load_id": "LOAD_20250210_007",
  "source_currency": "USD",
  "source_amount": 200.00,
  "fx_rate": 83.20,
  "inr_credited": 16640.00,
  "card_last4": "4242",
  "status": "COMPLETED",
  "timestamp": "2025-02-10T14:32:11Z"
}

Regulatory framework

MyPursu operates under the Reserve Bank of India's Prepaid Payment Instrument (PPI) framework — specifically the RBI Master Direction on PPIs (2021, updated 2024). International travelers using the platform are subject to KYC requirements mandated by FEMA (Foreign Exchange Management Act) and PMLA (Prevention of Money Laundering Act). Outstanding balances on Traveller PPIs are capped at INR 2,00,000 at any given time.

The UPI One World wallet framework — launched by NPCI on 22 July 2024 — provides the regulatory foundation for foreign visitors to access UPI without an Indian bank account, through authorized PPI issuers at airports, hotels, and money-exchange outlets. MyPursu aligns directly with this framework.

• RBI PPI Master Direction — governs wallet issuance, KYC tiers, and transaction limits
• NPCI UPI One World (July 2024) — defines cross-border UPI PPI rules for travelers
• FEMA — regulates foreign exchange aspects of INR prepaid instruments
• PMLA / AML/CFT — KYC and transaction monitoring obligations
• IT Act 2000 / DPDP Act 2023 — India's data protection law governing personal data handling

Our compliance approach

All integrations we deliver are structured around customer authorization and documented access patterns. We do not use or distribute user credentials; sessions are managed via tokenized access with defined TTLs and explicit refresh boundaries. Data minimization is built into every module — we extract only the fields required for the specified integration use case.

• Consent-gated data access — user authorization required for each data type
• Read-only by default — no write or payment-initiation without explicit scope
• Token TTL management and automatic refresh without credential storage
• NDA available upon request for sensitive integration projects
• Compliance review included for RBI PPI and FEMA-adjacent data flows

About Our Studio

We are an independent technical services studio specializing in app interface integration and authorized API integration. Our team brings years of hands-on experience in mobile fintech, cross-border payments, and open-data protocol analysis — with particular depth in UPI, NPCI infrastructure, and the RBI-regulated PPI ecosystem that underpins apps like MyPursu.

We work with clients globally — from corporate travel desks needing automated India expense exports, to NRI fintech startups building consolidated financial dashboards, to enterprise HR platforms automating trip reconciliation. Our delivery model is simple: you name the app and the data you need; we deliver working, documented API source code.

• UPI, NPCI, RBI PPI, and FEMA-aligned integration expertise
• Android and iOS protocol analysis for fintech and travel apps
• Custom Python / Node.js SDKs with automated test harnesses
• Full pipeline: protocol analysis → build → validation → compliance review
• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API endpoint and pay only per call; no upfront cost, ideal for usage-based teams

Contact Us

To request a quote or submit your target app and integration requirements, visit our contact page. We respond within one business day with a scoping assessment and timeline estimate.

Open Contact Page

Engagement Workflow

1. Scope confirmation — define integration scenarios: which data types (UPI transactions, wallet balance, KYC, concierge bookings) and delivery target (ERP webhook, REST API, database sink).
2. Protocol analysis & API design — 2–4 business days; we map MyPursu's backend endpoints, auth flow (token lifecycle, device binding), and data schema.
3. Build & internal validation — 3–7 business days; runnable modules with error handling, retry logic, and pagination built in.
4. Documentation & test cases — 1–2 business days; OpenAPI spec, integration guide, and automated test suite included.
5. Delivery & review — you run the code against your environment; we address feedback. Typical end-to-end: 7–14 business days.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Does this work for both Android and iOS?