Collections Infrastructure for Microfinance Institutions.

UPI Autopay & eNACH mandate-based loan collections — higher collection efficiency, go live in 48 hours, with a dedicated account manager.

RocketPay UPI Autopay and eNACH loan collections dashboard for MFIs

Who We Serve

Built for every microfinance model.

From NBFC-MFIs to group lending models — one collections stack, built for high-frequency field operations.

Book Demo
NBFC-MFIs

NBFC-MFIs

High-frequency mandate collections with intelligent retry — built for weekly and bi-weekly EMI cycles at scale.

Microfinance Institutions

Microfinance Institutions

Purpose-built collections infrastructure that supports your field operations — not a generic payments tool.

Group Lending Models

Group Lending Models

Mandate-based collections aligned to group lending timelines and field collection workflows.

Problems Faced

What microfinance collections look like without the right infrastructure.

Low repayment recovery at high frequency

Low repayment recovery at high frequency

Weekly and bi-weekly cycles demand precision. Without intelligent retry, missed EMIs compound faster than field teams can recover them.

Platforms built for lenders, not for MFIs

Platforms built for lenders, not for MFIs

Most collections platforms are not built for MFI timelines or group lending models. Integration drags while field operations run manually.

Field operations managed through a ticket queue

Field operations managed through a ticket queue

MFI collections are operationally dense. When something breaks, the team needs a person on the phone — not a support queue.

Collections infrastructure that does not go deep enough

Collections infrastructure that does not go deep enough

Most platforms handle the basic mandate setup and stop there. When your borrower base has varied repayment patterns and high-frequency collection needs, your field team ends up filling the gaps manually.

Collections support limited to business hours

Collections support limited to business hours

Field collections run early mornings and weekends. When something breaks outside office hours, MFIs cannot wait until Monday.

Settlements delayed

Settlements delayed

For MFIs managing tight working capital, delayed settlements create a ripple — impacting field payouts, disbursements, and operational continuity.

Why RocketPay

How RocketPay's collections stack is built differently for MFIs.

RocketPay brings structure to high-frequency collections — with mandate management and dedicated support built for MFI field operations.

  • Higher collection efficiency
  • Go live in 48 hours
  • Dedicated Account Manager
  • Custom coverage for MFI collection scenarios
  • 24x7 Support
  • On-time settlements

Our Impact

Microfinance lenders across India trust RocketPay to collect.

25+
Lenders served
₹300 Cr+
Worth of loan collection mandates created
2 lakh+
Transactions created

How to Deploy

Deploy RocketPay your way.

Two ways to get started — pick what fits your technical setup.

API and SDK integration for MFI collections
For technical teams

API & SDK

Integrate mandate-based collections directly into your LMS. Full control over mandate creation, debit scheduling and retry logic.

  • For LMS integrations
  • Webhooks and mandate status APIs
  • Non-cancellable and variable mandates
  • Works with your existing PSP
  • Go live in 48 hours
View API Documentation
RocketPay Android app for MFI collections
For field teams and smaller MFIs

Android App

Quick onboarding for field teams. Create mandates and track collections from mobile — no API integration needed.

  • No API integration needed
  • Mandate creation from mobile
  • Real-time collection status
  • Built for field operations
  • Go live in 48 hours
Download Android App

Get started

Let's automate your loan collections.

Higher field collection efficiency, faster go-live, and a dedicated account manager from day one.

FAQs

Frequently asked questions

Once a mandate is registered, RocketPay handles the full collection lifecycle automatically. On the due date, a debit instruction is triggered via UPI Autopay or eNACH. If the debit fails, AA-based partial recovery fetches available balance and recovers what is present. Non-cancellable mandates and intelligent retry ensure maximum credit recovery. Every attempt, status change, and settlement is logged in real time — accessible via dashboard or API webhook.

Any NPCI-registered UPI app and bank supports UPI AutoPay mandate registration — including PhonePe, Google Pay, Paytm, BHIM, WhatsApp Pay, Amazon Pay, and all major bank-native apps. The mandate is registered against the customer's VPA handle. For the complete and updated list of supported banks and PSP apps, visit the official NPCI page.

The three most common eNACH mandate authentication methods are — Net Banking, Debit Card, and Aadhaar OTP. Some banks additionally support PAN-based authentication, and a few offer Customer ID-based authentication via their own portal. Available methods vary by bank. For the complete list of supported banks and their authentication options, visit the official NPCI page.

These limits apply per debit — not per mandate. UPI Autopay supports collections up to ₹15,000 per transaction. eNACH supports up to ₹1 crore per transaction. The mandate itself carries no amount cap — it simply authorises future debits on the schedule you set. For portfolios where each collection exceeds ₹15,000, eNACH is the appropriate instrument.

Pending — The mandate link has been sent to your customer, but it is not approved yet. No collections will happen until your customer authorises the mandate.

Active — Your customer has approved the mandate. Collections will run automatically on the scheduled dates.

Paused — The mandate is active but temporarily paused. No future debits will be attempted until the mandate is unpaused or resumed.

Finished — The mandate has completed its full tenure. No further debits will occur.

Cancelled — The mandate has been cancelled. No further debits will occur.

Expired — The mandate link was not approved within the validity window and has lapsed. You will need to send a new mandate request to the customer.

No. Once a mandate is finished or cancelled, no further debits are possible against it. The mandate is permanently closed. If you need to start collections again, a new mandate must be created and approved by the customer.

No. A mandate requires only one-time authorisation. Once approved, all subsequent collections within the mandate happen automatically on the scheduled dates — no OTP, no PIN, no action required from either party.

Yes — your business will need to complete a one-time KYC verification as part of onboarding. This is a standard regulatory requirement for all businesses using payment infrastructure in India. No KYC is required from your end customers — they simply authenticate the mandate, and collections run from there.

Settlement happens on T+1 — funds are credited to your account on the next business day after a successful collection. This applies to both UPI Autopay and eNACH. Settlement timing starts from when the debit is confirmed on the customer's account. You can track exact collection and settlement timestamps in real time from your RocketPay dashboard.