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 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.

RocketPay’s device locking lets lenders remotely lock or unlock an Android smartphone when a customer misses a payment — no physical access required. DLC-based locking is supported on Motorola, Xiaomi, Nothing, iQOO, Google Pixel, Tecno, Itel, Infinix, and Honor. Native OEM locking is supported on Samsung, Oppo, and Realme. Between the two methods, all major Android brands are covered. The solution integrates via API into your lending platform, or can be accessed directly through the RocketPay app. Device locking is not available on iOS.

Device locking is the most effective NPA control tool available for consumer mobile financing. When a customer knows their device can be remotely locked on a missed payment, the incentive to pay on time is immediate and personal. RocketPay’s device locking reduces NPAs for consumer financing lenders to less than 1% — without physical recovery, field agents, or legal escalation. Remote lock and unlock is handled instantly from your dashboard or via API.

No. There are three methods a borrower might attempt — none result in a usable unlocked device. Factory reset from settings — this option is permitted on DLC-locked devices. But the moment the device connects to the internet after the reset, the locking app is automatically downloaded and reinstalled. Hard reset — available on certain brands. Same outcome: as soon as the device connects to the internet, the locking app reinstalls automatically. Software flashing via PC — USB debugging and developer mode are disabled at the Android framework level. When the device is connected to a computer, no commands can be executed and the locking app cannot be deleted. The device will only charge. In every case, the lock returns the moment the device goes online.

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.

RocketPay automatically retries failed settlements until they go through — no action is needed from your end. The collected amount remains secure and is not affected by the delay. Once the retry succeeds, funds are credited to your account. You can monitor settlement status in real time from your dashboard. You can always reach out to our 24x7 support for assistance.

Yes. If a collection attempt fails, you can schedule a retry for any future date of your choice — directly from the dashboard or via API. There is no fixed retry schedule; the business decides when to retry till the mandate remains active — no changes needed.

Yes. You can skip any collection as long as its collection attempt has not been initiated. The mandate stays active and all future collections run as scheduled. Only that one instalment is skipped.

Yes — customers receive two automatic notifications before each scheduled collection. The destination bank sends a pre-debit notification at least 24 hours in advance, and RocketPay sends one as well. The business does not need to trigger or configure either. The customer is informed of the amount and date before the debit goes through.

Yes. Different installments within the same mandate can have different amounts — the schedule does not need to be fixed. This allows lenders to structure progressive EMIs, declining balance schedules, or any custom repayment plan where each installment differs. The full collection schedule and amounts must be defined before the customer authorises the mandate.

For eNACH mandates, the customer’s bank charges a penalty of ₹550 + GST for the failed debit. For UPI Autopay mandates, no such penalty applies. In both cases, you can schedule a retry for any future date directly from your dashboard.

Upcoming — The due date has not arrived yet. No collection attempt has been initiated. Payment collection initiated — The debit request has been sent to the end-customer’s bank. It will be attempted within 24 hours. Payment collected, processing — The amount has been successfully debited. Settlement to your account is in progress. Payment failed — The collection attempt failed. You can schedule a retry for any future date from your dashboard. Settlement initiated — Settlement to your bank account has been initiated. Payment deposited to you — The collected amount has been credited to your linked bank account. Settlement failed — Settlement to your account failed. RocketPay automatically retries. You can also reach out to our 24x7 support. Skipped — This installment was intentionally skipped. No debit was attempted. Manually collected — You have marked this installment as collected outside of RocketPay.

If the collection did not happen on the due date, you can schedule a retry directly from your dashboard. Retries are possible as long as the mandate is active. RocketPay keeps the mandate active for 90 days after the last installment’s scheduled collection date, giving you a sufficient window to retry any missed installment.

Create mandate → Enter customer details and set the collection schedule → Share the mandate link with your customer → Customer authorises once via UPI Autopay or eNACH → Collections run automatically on the scheduled dates

Via mandate link — The customer receives the link, opens it, confirms the payment details, enters their UPI ID or selects a UPI app, a request appears on their UPI app, they accept and enter their UPI PIN, and the mandate becomes active. Via QR code — The business presents a QR code, the customer opens their UPI app and scans it, they are taken directly to the AutoPay setup page, they accept and enter their UPI PIN, and the mandate becomes active.

The customer receives the mandate link, opens it and confirms the payment details, enters their bank account details, selects their authentication method (Net Banking, Debit Card, or Aadhaar OTP), completes verification on their bank’s page, and the mandate becomes active.

A mandate bounce due to insufficient funds is a criminal offence under Section 25 of the Payment and Settlement Systems (PSS) Act, 2007 — carrying the same legal weight as a cheque dishonour under Section 138 of the NI Act. Both UPI AutoPay and eNACH/NACH mandates qualify as electronic funds transfers under Section 2(1)(c) of the PSS Act and are explicitly covered. The NPCI’s November 2021 circular further confirmed this for UPI AutoPay. To initiate proceedings: issue a written demand notice to the borrower within 30 days of the bounce. The borrower has 15 days to make the payment. If they do not, you can initiate criminal prosecution. Under Section 25(3), the borrower cannot use ignorance of their account balance as a defence. The penalty can be imprisonment up to 2 years, a fine up to twice the defaulted amount, or both.