How to Fix “Don’t Submit UTR Too Frequently. Please Try Again Later” Error

Person holding a smartphone looking at a failed online payment transaction screen
Resolving Digital Payment UTR Errors

💡 Quick Answer: What Should You Do?

If you are seeing the “don’t submit UTR too frequently. pls try again later” error, the payment gateway’s security system has temporarily blocked your account for spamming the 12-digit reference number.

The Fix: Stop trying immediately. You must wait a minimum of 2 to 4 hours (sometimes up to 24 hours depending on the platform) before attempting to submit the UTR again. Your money is safe in the banking network.

You just transferred money to a trading app, wallet, or gaming platform using UPI or IMPS. The money left your bank account, but when you entered the 12-digit UTR (Unique Transaction Reference) to claim your funds, the system rejected it. In a panic, you clicked “Submit” a few more times, and now you are hit with the dreaded rate-limit error.

First: take a deep breath. This is a standard anti-fraud measure, not a sign that your money is gone forever. Here is exactly why this happens and the step-by-step E-E-A-T backed process to resolve it.

Why Does the System Block Your UTR Submission?

When you make a payment in India via the National Payments Corporation of India (NPCI) network, a unique 12-digit UTR is generated. Payment gateways use this number to match your bank deposit to your app wallet.

When you click “Submit” multiple times within a few seconds or minutes, the system’s firewall flags your IP address or user ID. It assumes a bot is trying to brute-force or guess UTR numbers to steal funds. This triggers a temporary cooldown period to protect both the merchant and your account.

The Wait-Time Matrix

Depending on how many times you spammed the submit button, your cooldown period varies. Use this table as a general guideline:

Submission Attempts System Response Required Cooldown Time
1 to 3 times Soft Warning 15 to 30 Minutes
4 to 10 times Hard Rate-Limit Block 2 to 4 Hours
10+ times Temporary Account Freeze 24 Hours (Requires Support)

Actionable Steps to Resolve the Issue

Do not keep trying to push the transaction through. Follow these exact steps to ensure your funds are credited properly:

  • 1.Close the App Immediately: Force close the browser tab or mobile application. Continuing to keep the session open might trigger background API calls that reset your cooldown timer.
  • 2.Verify Your UTR Number: Open your banking app (SBI, HDFC, PhonePe, GPay, etc.) and check the history. Ensure the 12-digit number you are copying is the UTR (or UPI Ref No), not the transaction ID or order ID.
  • 3.Wait the Full Cooldown Period: If you received the “don’t submit too frequently” message, set an alarm for 3 hours. Do not attempt a “test submission” during this window.
  • 4.Clear Cache Before Retrying: If you are on a web browser, clear your site cookies and cache. If on mobile, toggle Airplane mode on and off to reset your network IP, preventing lingering IP bans.

What If the Money Was Deducted But Still Fails?

If you wait the requisite time, enter the correct UTR, and it still fails, the issue is likely a bank-side node failure. The receiving bank’s server hasn’t communicated the receipt of funds to the merchant yet. In this scenario, RBI guidelines dictate that failed transactions must be automatically refunded to your source account within T+3 to T+5 business days.

⚠️ Important Safety Warning: Never share your UTR number, OTP, or UPI PIN on public forums, Twitter (X), or Telegram groups while asking for help. Scammers monitor these tags to steal transaction details. Always use the official support portal within your app.

If your problem persists beyond 24 hours, you may need to escalate the issue. Read our comprehensive guide on how to handle stuck UPI transactions and contact the correct banking ombudsman.


Disclaimer: This article provides general troubleshooting for common payment gateway errors. Always consult your bank or the official merchant support team for account-specific transaction inquiries.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply