RapiPay Agent API integration (AEPS, BBPS, DMT)

Deliverables checklist

• OpenAPI 3.1 specification covering every endpoint we wire
• Protocol report: TLS pinning, header signing, OTP/MPIN flow, biometric PID block envelope
• Runnable Python (FastAPI) and Node.js (Express) reference clients for AEPS, DMT and BBPS
• Postman collection and an integration test harness with replayable transaction fixtures
• Compliance handover: KYC retention plan, Aadhaar masking helper, RBI audit-log template

Why RapiPay Agent data is worth integrating

Assisted-payment apps are the only structured digital trail for cash-economy customers in semi-urban and rural India. A RapiPay Agent ledger is, in effect, a high-frequency record of last-mile cash-in / cash-out flows that no card network or pure UPI app captures. Pulling it into your warehouse unlocks credit underwriting for retailers, anti-money-laundering surveillance over agent terminals, and unit-economics reporting for distributors who run hundreds of DBOs.

RapiPay's 2024 push into a digital-banking super app (NYE) following a USD 15 million funding round reported by Trade Brains adds another layer: agents are now a distribution channel for savings, insurance, and lending products, all of which generate downstream events worth syncing to a CRM.

1. Daily AEPS reconciliation for a multi-DBO distributor

A super-distributor running several hundred Direct Business Outlets pulls the AEPS transaction list every morning, joins it against bank-side settlement files received through SFTP, and flags mismatches by RRN. Mapping to OpenFinance: this is a classic statement-export pattern used in PSD2 AISP setups, only the data source is an assisted-payments app rather than a retail bank.

2. Underwriting credit lines for retail agents

An NBFC partner uses 90 days of agent throughput — AEPS volume, BBPS count, DMT remit value, commission earned — to size a working-capital float. The integration exposes a single /agent/{id}/throughput rollup so the credit model does not have to call seven different endpoints. Mapping to OpenFinance: cash-flow underwriting using transaction data instead of bureau scores.

3. BBPS biller analytics for a state utility

A discom integrates the BBPS receipt feed to track collection share by district, channel and time-of-day. The webhook fires on bill_payment_success and pushes an event with biller_id, consumer_id_hash, amount, payment_mode and receipt_url to the discom's data lake. Mapping to OpenFinance: open BBPS data feeding regulated utility reporting.

4. Compliance & AML surveillance over agent terminals

A bank running RapiPay as an outsourced channel needs to watch for structuring (multiple sub-threshold remits) across the same beneficiary IFSC. The integration ships a daily denormalised parquet file of DMT events, plus a same-day webhook for any remit above the PMLA monitoring threshold. Mapping to OpenFinance: regulatory data sharing under RBI outsourcing master direction.

5. ERP / Tally export for retailer accounting

Retailers want their RapiPay earnings to land directly in Tally or Zoho Books with the correct GST head. The integration pulls the commission ledger nightly, splits CGST/SGST/IGST/TDS, generates an XML voucher per day, and posts to the accounting API. Mapping to OpenData: structured financial export from a fintech super-app into a third-party accounting tool.

Agent login & session refresh

// Agent login (pseudocode, OAuth2-style)
POST /api/v1/rapipay/agent/login
Content-Type: application/json

{
  "agent_id": "RP123456",
  "mpin": "<ENCRYPTED_MPIN>",
  "device_id": "android-3f9c-...",
  "app_version": "8.x"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_9c1d...",
  "expires_in": 1800,
  "agent": { "id": "RP123456", "dbo_code": "DBO-451", "limits": { ... } }
}

AEPS cash-withdrawal request

// AEPS withdrawal (PID block stays opaque)
POST /api/v1/rapipay/aeps/withdraw
Authorization: Bearer <ACCESS_TOKEN>
Content-Type: application/json

{
  "txn_ref": "TX-20260503-0001",
  "bank_iin": "508534",
  "aadhaar": "XXXX-XXXX-1234",
  "amount": 2000,
  "pid_block": "<UIDAI_PID_BLOCK_BASE64>",
  "geo": { "lat": 28.61, "lng": 77.20 }
}

200 OK
{ "status": "SUCCESS", "rrn": "612300456789",
  "balance_after": 1450.00, "settlement_date": "2026-05-04" }

BBPS statement export

// Pull BBPS bill receipts for a date range
GET /api/v1/rapipay/bbps/payments?from=2026-04-01&to=2026-04-30&page=1
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "page": 1, "page_size": 50, "total": 1284,
  "items": [
    { "txn_id": "BB-998123", "biller_category": "Electricity",
      "biller_id": "BSES-RAJ", "consumer_no": "1100xxxx345",
      "amount": 1240.00, "status": "SUCCESS",
      "receipt_url": "https://.../receipt/BB-998123.pdf",
      "paid_at": "2026-04-12T11:14:22+05:30" }
  ]
}

Commission webhook (server → your endpoint)

// Webhook delivered to your URL after end-of-day settlement
POST https://your-domain/webhooks/rapipay/commission
X-RapiPay-Signature: t=1714723200,v1=<HMAC_SHA256>
Content-Type: application/json

{
  "event": "commission.settled",
  "agent_id": "RP123456",
  "for_date": "2026-05-02",
  "gross": 412.50, "gst": 74.25, "tds": 4.13,
  "net_payable": 334.12,
  "lines": [
    { "service": "AEPS_WITHDRAW", "count": 27, "amount": 178.00 },
    { "service": "BBPS_BILLPAY", "count": 14, "amount": 112.50 },
    { "service": "DMT",          "count":  9, "amount": 122.00 }
  ]
}

Compliance & privacy

All RapiPay Agent integrations we deliver run under written agent authorisation or documented public/partner APIs. Biometric AEPS payloads conform to UIDAI PID-block specifications and travel only to NPCI-certified endpoints — they are never written to disk on our side. Settlement and remittance data is handled in line with the Reserve Bank of India's master directions on Prepaid Payment Instruments and on outsourcing of payment operations, alongside the NPCI AEPS product specification.

We also align with the Digital Personal Data Protection Act 2023 for retention, consent capture, and data-subject access requests, and we provide a ready-to-use Aadhaar masking helper so PII never leaks into application logs.

Data flow / architecture

A typical pipeline looks like this:

1. Client app (RapiPay Agent on Android/iOS) — original event source.
2. Ingestion / API gateway — our adapter normalises payloads, signs requests, refreshes tokens.
3. Storage — partitioned by date / agent_id in Postgres or your warehouse (BigQuery, Snowflake, Redshift).
4. Output — REST APIs, webhooks, SFTP CSV drops, or Kafka topics depending on consumer.

Each stage carries an audit trace tying every record back to the originating txn_ref, which simplifies RBI inspections and internal reconciliation.

Spice Money

One of the largest BC networks in India. Holds AEPS, DMT, BBPS, and mini-ATM transaction data for millions of adhikaris (agents). Integrators often need a unified statement export across Spice Money and RapiPay for retailers operating both apps.

Paynearby

A retail BC platform with deep AEPS volumes and a rich commission ledger. Common ask: reconcile Paynearby AEPS RRNs against bank settlements alongside RapiPay's own.

Paytm AEPS

Paytm's assisted-payments stack inside the One97 ecosystem. Holds bill payment, recharge and AEPS data; useful for cross-app commission roll-ups when an agent is registered on more than one platform.

Bankit

Provides a similar AEPS, DMT and BBPS suite to retailers. The data shape is comparable, which makes a single OpenFinance schema across Bankit and RapiPay realistic.

Ezulix

White-label fintech platform powering many regional brands; integration consumers often want to bridge Ezulix's API output into the same warehouse used for RapiPay records.

Ezeepay

Multi-service BBPS and AEPS portal. Frequently appears in "apps like RapiPay Agent" searches and shares a similar agent-centric ledger model.

Biznext

Strong AEPS commission portal that publishes detailed slab tables. Integrating Biznext data with RapiPay helps distributors compare margin per RRN across providers.

Fino Payments Bank

An RBI-licensed payments bank with its own merchant app. Holds agent-banking transactions plus a savings layer; pairing it with RapiPay enables a fuller picture of an agent's business volume.

Fingpay

Tone Tag's biometric payments product. Often referenced alongside RapiPay in AEPS comparisons; sharing data flows can simplify multi-vendor reconciliation.

MobiKwik

Wallet, BBPS and recharge platform with retailer-side flows. Useful when a retailer's customer mix spans both digital wallet top-ups and AEPS cash-out.

About us

OpenFinance Lab is an independent technical-services studio focused on mobile-app protocol analysis and OpenData / OpenFinance / OpenBanking integration. Our team blends payments engineering (former engineers from Indian payment gateways and acquiring banks), Android / iOS reverse-engineering, and cloud platform work (Kubernetes, queue-driven ETL, warehouse-side modelling). For Indian fintech work we maintain working knowledge of NPCI specifications (UPI, AEPS, BBPS), RBI digital-payment master directions, and UIDAI Aadhaar-handling rules.

• Coverage: payments, digital banking, insurtech, and assisted-payments BC stacks
• Engineering: Python, Node.js, Go, plus Android/iOS analysis tooling
• Operations: enterprise API gateways, security review, and SOC-friendly logging
• Pipeline: protocol analysis → API design → build → validation → compliance handover
• Source-code delivery from $300 — runnable APIs and full docs; pay after acceptance
• Pay-per-call hosted APIs — usage-based pricing, no upfront commitment, ideal for pilots

Contact

For quotes or to send the target app and a brief, open our contact page. We will reply with a scope outline within one business day:

Contact page

We sign NDAs on request and can work either in your environment or under our own ISMS controls.

Engagement workflow

1. Scope confirmation: list which RapiPay flows you need (AEPS, Micro ATM, DMT, BBPS, recharge, CMS, commission ledger).
2. Protocol analysis and API design — typically 2–5 business days, depending on biometric and webhook coverage.
3. Build and internal validation against fixture data — 3–8 business days.
4. Documentation pack: OpenAPI 3.1, Postman collection, runnable sample, and compliance notes — 1–2 business days.
5. First delivery commonly lands in 5–15 business days; partner / regulator approvals can extend this.

FAQ

What do you need from me to start a RapiPay Agent integration?

How long does a typical RapiPay Agent API drop take?

How do you handle compliance for AEPS and biometric data?

Can I get pay-per-call hosted APIs instead of source code?