Refresh Mandate Installment Debit API – Auto Refresh Failed EMI & Subscription Payments | UPI eMandate API India
The Refresh Mandate Installment Debit API enables businesses to automatically Refresh failed debit transactions for recurring payments such as EMIs, loan repayments, subscriptions, and utility bills. Built for high success rates, this API intelligently retries failed mandates due to insufficient balance, network issues, or bank downtime—ensuring maximum payment recovery with minimal manual effort.
AUTOFLOW
E-Mandate APIMaximum Limit
₹ 25,000/cycle
Frequency
MONTHLY
Start Date
17 APR 2026
Status
ACTIVE
HDFC Bank Ltd.
XXXX XXXX 8821
{
"mandate_id": "EM_4409X",
"type": "ON_DEVICE_AUTH",
"config": {
"max_amount": 25000.00,
"recurrence": "MNTH",
"secure_hash": "AES_GCM_256"
}
}
NPCI_ONBOARDED
Digital India Stack 2026
Refresh Mandate Installment API
Recover failed recurring payments by re-triggering installment debits. Automate the collection of missed payments with intelligent Refresh logic and real-time bank status updates.
1. Trigger Refresh
Initiate a Refresh request using the original Mandate ID and Transaction reference to re-attempt a failed debit installment.
2. Bank Processing
Our API routes the request through NPCI to the destination bank, ensuring the Refresh complies with authorized mandate limits.
3. Recovery Status
Receive an instant notification of the Refresh outcome, providing clear success confirmation or detailed failure reason codes.
Maximize Collection Success
Protect your revenue stream by minimizing payment defaults. The Refresh Mandate Installment API offers a robust mechanism to recover funds without customer intervention.
Automated Recovery
Systematically re-attempt failed debits due to insufficient funds or temporary technical issues at the bank's end.
Smart Scheduling
Optimize Refresh timing based on previous success patterns to increase the likelihood of successful fund capture.
Compliance Adherence
Operate strictly within NPCI guidelines for Refresh attempts, ensuring your collection process remains within regulatory limits.
Reduced Churn
Prevent subscription cancellations by fixing payment gaps automatically before the service is interrupted.
Transaction Linking
Maintain a clear link between original failed attempts and successful retries for seamless ledger reconciliation.
Reason Analysis
Utilize detailed decline codes to decide whether to Refresh or move the installment to a manual recovery bucket.
Zero Friction
Collect payments silently in the background without requiring the customer to perform another e-Mandate authorization.
Lower Admin Costs
Reduce the overhead of manual outreach and follow-ups by automating the recovery of delinquent installments.
Scalable Architecture
Handle thousands of Refresh requests simultaneously during peak billing cycles without performance degradation.
Advanced Refresh Logic
Our Refresh Mandate API provides the technical precision needed to recover revenue efficiently while maintaining customer trust.
Dynamic Re-trigger
Execute Refresh attempts based on customizable rules, ensuring you never miss a collection window.
Authorized Limits
Every Refresh is validated against the original mandate amount and frequency limits to ensure 100% security.
Success Analytics
Track the recovery rate of retried installments to fine-tune your billing and collection strategies.
Why Use Refresh Debit API?
Recovering failed installments shouldn't be manual. Use the Refresh API to programmatically re-attempt collections, reduce involuntary churn, and maintain a healthy cash flow without bothering your customers.
Trigger Refresh Installments Instantly
Initiate a recovery debit with a single POST request. Programmatically re-process failed transactions using original mandate parameters.
curl --request POST
--url https://api.idspay.in/v3/mandate/Refresh
--header 'Authorization: Bearer YOUR_API_KEY'
--header 'Content-Type: application/json'
--data '{
"mandate_id": "MND_987654321",
"original_txn_id": "TXN_123456789",
"amount": "5000.00"
}'{
"status": "Refresh_INITIATED",
"data": {
"Refresh_id": "RTY_887766554",
"mandate_id": "MND_987654321",
"original_txn_id": "TXN_123456789",
"amount": "5000.00",
"Refresh_count": "1",
"initiated_at": "2026-04-17 16:40:00"
}
}🔍 Precision of Refresh Mandate API
Transform failed installments into successful collections. Our API handles the complexities of bank-level retries while ensuring full compliance with NPCI mandates.
Smart Retries
Automatically re-trigger debits for specific failure codes like insufficient funds or gateway timeouts.
TXN Correlation
Map every Refresh attempt back to the original billing cycle for perfect accounting and reconciliation.
Policy Guardrails
Built-in checks to ensure Refresh frequency and counts never exceed bank or regulatory limits.
Fast Recovery
Minimize the time gap between a payment failure and a successful recovery attempt.
Recovery Rates
Analyze the success probability of retries across different banks and failure reasons.
Instant Webhooks
Get notified immediately when a Refresh succeeds so you can restore customer services instantly.
Flexible Retries
Option to Refresh the full installment amount or a partial balance where permitted.
Seamless UX
Recover payments without asking customers to re-authenticate or visit a checkout page.
How Refresh Debit API Works
Automate the recovery of missed payments by re-triggering installment debits through our secure banking gateway with intelligent Refresh logic.
Initiate Refresh
Submit the original transaction reference and mandate ID to the Refresh endpoint to start the recovery process.
Limit Validation
The API automatically verifies the Refresh request against the customer's authorized mandate limits and bank policy.
Bank Processing
The debit request is routed to the customer's bank via NPCI to capture the funds from the linked account.
Fund Recovery
Upon success, the installment is recovered, and webhooks are triggered to update your internal ledger in real-time.
Stop Losing Revenue to Failed Debits with Refresh Mandate API
Our Refresh Mandate Installment API is engineered to recover missed payments by providing automated re-attempt logic. We ensure you can capture failed installments without customer intervention.
To ensure maximum recovery rates, businesses need a robust Refresh layer that handles technical and fund-related failures gracefully. Our solution provides a secure bridge to re-process installments instantly.
Whether you are fixing a missed loan EMI, a subscription renewal, or a utility bill payment, this Recovery Engine delivers the automation required for maintaining a healthy and predictable recurring revenue pipeline.
Installment Recovery Success Rate
Automation
Compliance
Why IDSPay is Better than Other Mandate APIs?
See how we outperform the industry standards.
Faster Response
Lower latency and faster data retrieval than competitors.
Superior Uptime
More reliable service stability than Eko & API Mall.
Cleaner Docs
Easier to read and implement compared to Digitap.
Affordable Pricing
Cost-effective plans tailored for growing startups.
Dedicated Support
Real human experts ready to help you with any integration hurdles 24/7.
Why We Are The Better Choice
Compare our performance and see why top fintechs trust our infrastructure.
| Feature | 🚀 Our API | Other Providers |
|---|---|---|
| Accuracy |
99.9% (Govt. Direct)
|
~85-90% (Scraped)
|
| Speed |
< 500ms
|
2 - 5 Seconds
|
| Pricing |
Pay-per-use (No Fixed Fee)
|
High Monthly Commitment
|
| Support |
24/7 Priority Support
|
Email-only (48hr TAT)
|
* Based on internal benchmark tests and competitor analysis (April 2026).
Frequently Asked Questions
Common developer queries about the Refresh Mandate Installment API and automated recovery workflows.
What is the Refresh Mandate Installment API?
The Refresh Mandate Installment API is an automation endpoint designed to re-initiate failed recurring payment collections. It allows merchants to trigger a fresh debit attempt against an existing mandate after an initial installment failure.
2. When should I trigger a Refresh attempt?
You should trigger a Refresh when an installment fails due to soft declines such as 'Insufficient Funds' or temporary technical errors. It is best used within the grace period allowed by your service agreement and NPCI guidelines.
3. Is a new customer authorization required for retries?
No. The Refresh API utilizes the original mandate authorization (E-Mandate/NACH). As long as the mandate remains 'Active' and the Refresh amount is within the authorized limit, no further customer intervention is needed.
4. How many times can I Refresh a failed installment?
While our API supports multiple attempts, NPCI and banking regulations typically limit the number of Refresh attempts per installment cycle. We recommend following a T+2 or T+5 Refresh schedule to maximize success.
5. What happens if a Refresh fails again?
If a Refresh fails, the API returns a detailed decline code. Depending on the reason (e.g., 'Account Closed'), you may choose to halt further retries and move the account to a manual collection or suspension workflow.
6. Can I Refresh a partial amount of the installment?
Yes, the API allows you to specify the amount for the Refresh attempt, provided it does not exceed the maximum authorized limit defined in the original mandate registration.
7. Are there additional charges for using the Refresh API?
Refresh attempts are treated as standard transaction requests. However, frequent failures might incur bank-level bounce charges for the customer. It is advisable to use Refresh logic judiciously.
8. How do I reconcile a successful Refresh?
Each Refresh request generates a unique 'Refresh_id' which is linked to the 'original_txn_id'. You can use our webhooks or reconciliation reports to match these IDs and update your billing records.
9. Does the API support bulk Refresh requests?
Yes, for large-scale recovery operations, the API can process batch Refresh instructions. This is ideal for managing thousands of subscription renewals or loan repayments simultaneously.
10. How soon after a failure can I initiate a Refresh?
Technically, a Refresh can be initiated as soon as you receive the failure notification. However, for fund-related failures, waiting 24-48 hours often yields higher success rates as it aligns with typical customer salary cycles.