Logo
Banking & Fintech
Card Solution
ERP Products
API Services
Custom Dev
Other

Refresh Mandate API for Real-Time eMandate Status Updates

The Refresh Mandate API allows businesses to instantly fetch, update, and sync the latest status of customer mandates across banking networks like NACH, UPI AutoPay, and eMandate systems.

AUTOFLOW

E-Mandate API

Maximum Limit

₹ 25,000/cycle

Consumer Bank Merchant Node

Frequency

MONTHLY

Start Date

17 APR 2026

Status

ACTIVE

🏦

HDFC Bank Ltd.

XXXX XXXX 8821

REQUEST_METADATA

{

"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

QR
⭐ 4.9/5 Rating | Synchronizing 5M+ Mandate Statuses for Real-Time Payment Tracking Monthly

Refresh Mandate Status API

Get the latest status of your recurring payment instructions. Sync mandate approvals and registration states across all banking partners instantly.

1. Status Inquiry

Trigger a refresh call using the unique Mandate ID to fetch the most current registration status from the bank.

2. Bank Sync

Our API communicates with NPCI and the destination bank to verify if the mandate is Active, Pending, or Rejected.

3. Ledger Update

Receive the final payload to automatically update your database and proceed with the next scheduled collection.

Precision Data Tracking

Maintain a source of truth for every recurring instruction. The Refresh API ensures your system never falls out of sync with bank records.

Real-Time Verification

Instantly verify if a customer has successfully completed the bank-side authorization flow.

Resolve 'Pending' States

Don't wait for webhooks; actively pull the latest status to clear stuck or ambiguous mandate registrations.

Detailed Error Codes

Identify exactly why a mandate was rejected with granular bank response codes for better troubleshooting.

NPCI Reconciliation

Stay compliant with automated reconciliation against NPCI’s central mandate management system.

Optimized Collection Planning

Only attempt debits on 'Active' mandates, significantly reducing bank penalty charges for failed requests.

Post-Migration Sync

Perfect for verifying the status of legacy mandates migrated from older systems or different providers.

Audit-Ready Logs

Maintain a timestamped history of every status change for compliance and dispute management.

Zero Latency Tracking

High-availability endpoints ensure you get status updates in milliseconds, not minutes.

Dynamic State Logic

Handle complex mandate transitions like suspension, cancellation, or expiry with ease.

Smart Sync Tools

Our Refresh Mandate API provides the intelligence needed to manage the entire lifecycle of recurring payments.

Automated Polling

Configure smart polling intervals to auto-refresh mandates that have been in 'Pending' state for over 24 hours.

UMRN Tracking

Fetch the Unique Mandate Reference Number (UMRN) as soon as it is generated by the bank for official records.

Callback Sync

Use the Refresh API as a fallback to verify webhook data, ensuring 100% data integrity for your financial ledger.

Why Use Refresh Mandate API?

Ensuring your database matches the bank's records is critical for automated billing. Use the Refresh API to synchronize mandate statuses across diverse financial sectors instantly.

Status Verification
Success Confirmation
Failure Analysis
Billing Sync
Compliance Audit
Revocation Tracking
Ledger Accuracy
Grace Period Management

Sync Mandate Status in Real-Time

Update your mandate records with a single API call. Fetch current registration states, UMRN details, and bank approval timestamps effortlessly.

cURL Node.js PHP
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",
                "request_type": "STATUS_CHECK"
            }'
Response 200 OK
{
    "status": "SUCCESS",
    "data": {
    "mandate_id": "MND_987654321",
    "current_status": "ACTIVE",
    "umrn": "HSBC0000000000123456",
    "bank_ref_no": "REF77889900",
    "last_updated": "2024-05-20 14:30:05",
    "reason": null
    }
}

🔍 Efficiency of Refresh Mandate API

Optimize your collection logic with real-time status polling. Eliminate uncertainty in your payment cycles with direct banking synchronization.

Instant Sync

Pull the latest mandate status directly from the NPCI/Bank gateway without delay.

UMRN Retrieval

Automatically fetch and store the UMRN required for initiating subsequent debit requests.

Error Debugging

Receive clear bank-end rejection reasons to help customers correct mandate issues.

Polling Automation

System-driven polling logic to resolve mandates stuck in 'Pending' or 'In-Process' states.

Data Integrity

Ensure 100% parity between your merchant dashboard and the actual banking status.

Webhook Fallback

A robust fallback mechanism in case of missed webhooks or network delivery failures.

High Throughput

Capable of processing bulk status refresh requests for thousands of mandates simultaneously.

Unified Response

Standardized JSON responses across 50+ major banks for simplified backend processing.

How Refresh Mandate API Works

Maintain a real-time connection with banking networks to track, verify, and synchronize the latest status of every digital instruction.

Identify Mandate

Pass the unique Mandate ID or Customer reference to our refresh endpoint to begin the synchronization.

Network Query

Our system instantly queries NPCI and destination banks to retrieve the absolute latest state of the mandate.

Status Sync

Verify transitions from 'Pending' to 'Active' or identify revocations and expirations with 100% accuracy.

Update Records

Update your local database with the fresh response to ensure collection schedules are perfectly aligned.

Lifecycle Verification

Maintain Absolute Ledger Parity with Refresh Mandate API

Our Refresh Mandate API is built to solve the challenge of asynchronous payment states by providing on-demand status synchronization. We eliminate the gap between customer authorization and your internal database.

To ensure zero collection failures, businesses need a verification layer that bypasses delayed webhooks. Our solution provides direct banking queries and UMRN retrieval for mission-critical subscription platforms.

Whether you are verifying new registrations, tracking UMRN generation, or handling complex revocation flows, this Verification Engine delivers the data integrity required for high-volume recurring collections.

status: SYNCED

Status Sync Accuracy

100.0% ▲ Real-time Pull

Sync Speed

< 150ms

Verification

Bank-Grade
Test Refresh API

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 API and synchronization flows.

1. What is the Refresh Mandate API?

The Refresh Mandate API is a specialized endpoint that allows you to fetch the current, real-time status of a mandate from the NPCI/Bank systems. It is used to synchronize your local database with the actual state of the mandate.

2. When should I call the Refresh API?

You should call this API when a mandate remains in a "Pending" state for too long, if you suspect a missed webhook, or as a final check before initiating a high-value recurring debit request.

3. Does it provide the UMRN?

Yes. Once a mandate is successfully registered by the bank, the Refresh API response will include the Unique Mandate Reference Number (UMRN), which is essential for scheduling automated payments.

4. Can I use this for bulk status updates?

While the Refresh API is optimized for high performance, we recommend individual calls for real-time needs. For bulk synchronization, you can implement a worker script that iterates through mandates requiring status updates.

5. What statuses can I expect in the response?

Common statuses include: PENDING (Awaiting user/bank action), ACTIVE (Ready for debit), FAILED (Authorization rejected), and REVOKED (Cancelled by user/bank).

6. Is there a rate limit for Refresh calls?

To ensure system stability and comply with banking partner guidelines, we implement fair-usage rate limits. Please refer to your account tier documentation for specific transaction-per-second (TPS) limits.

7. Why does the status still show 'Pending' after authorization?

Mandate registration involves coordination between the Sponsor Bank, NPCI, and the Destination Bank. This process can take anywhere from a few minutes to T+2 days. The Refresh API helps you track this journey.

8. Can this API detect if a user cancelled a mandate at their bank?

Yes. If a customer revokes the standing instruction directly through their banking app or branch, the Refresh API will return a REVOKED or CANCELLED status, allowing you to stop billing immediately.

9. Is the refresh response different for different banks?

No. Our API normalizes the responses from all 40+ supported banks into a consistent JSON format, making it easy for your developers to handle data regardless of the customer's bank.

10. How do I test the Refresh flow in Sandbox?

In the Sandbox environment, you can use specific test Mandate IDs provided in the documentation to simulate various states (Success, Pending, Rejected) when calling the Refresh endpoint.