A UPI “limit exceeded” message can refer to the amount of one payment, a running total, the number of payments or a temporary account restriction. Identify which limit you reached before changing apps or attempting the same payment again.
Four questions before a large payment
- Is the recipient a person or a verified merchant in a special category?
- Which bank account, card or other instrument will fund the payment?
- What per-payment, total-value and count limits apply to that source?
- Has registration, a PIN reset, device change or another security event imposed a temporary restriction?
The lowest applicable restriction can determine the outcome. A higher product ceiling does not override a lower bank control or unavailable funds.
Why a single bank-by-bank table can mislead
An account’s limit can depend on transaction type, security state and the provider’s current rules. Instead of treating an approximate list as a promise, use the bank’s published help and the limits shown for your account. Ask support to identify the rule if the message is unclear.
| Official example | What the documentation says | What it does not establish |
|---|---|---|
| SBI UPI customer-care page | Describes a ₹1 lakh P2P total and 20 transactions over 24 hours, with separate restrictions after PIN setup or reset | A universal new-payee limit for every bank or a promise that all merchant categories have the same cap |
| Google Pay limits guide | Separates ordinary P2P limits from selected verified-merchant categories and device-registration restrictions | A limit that overrides the issuing bank’s lower controls |
These are examples of how rules are scoped, not an exhaustive account entitlement table. Check the linked source and your bank before depending on a particular amount.
Higher merchant limits are category-specific
The NPCI higher-limit circular distinguishes per-transaction and 24-hour caps for selected categories. For example, capital-market and insurance merchant payments are listed at ₹5 lakh per transaction and ₹10 lakh over 24 hours. Merchant verification and the correct category matter.
You cannot give a personal transfer a higher ceiling by writing “hospital bill” in its note. If a merchant expects a large payment, ask it to confirm the supported payment method and correct merchant account.
Registration restrictions are not all “new-payee rules”
A restriction triggered by setting or resetting your own PIN is different from a rule triggered by adding a beneficiary. SBI’s help page explicitly ties one temporary ₹5,000 restriction to PIN setup/reset and distinguishes Android and iOS periods. Do not assume a ₹1 test payment to a new contact starts or bypasses every bank’s waiting period.
A genuine small test can help confirm a recipient, but it should not be described as a guaranteed way to raise a limit. Follow the bank’s instructions and plan ahead for time-sensitive bills.
What to do when you reach a limit
- Read and save the exact error message.
- Check recent payments and the bank’s counting window. Do not assume every limit resets at midnight.
- If the payment can wait, use the provider’s stated reset time.
- If it is urgent, ask the bank and recipient about another appropriate transfer method and its own limits, beneficiary setup and fees.
- Check whether any previous attempt debited the account before trying another route.
Do not open or switch accounts solely to evade a security restriction. A second account is not a universal promise of double capacity, and UPI Lite has its own rules rather than unlimited extra allowance.
A useful message to bank support
“I am trying to pay [amount] to [person or merchant category] from [account ending]. The error says [exact text]. Please confirm the applicable per-payment and rolling-total limit, any temporary restriction, and when it ends.” Provide identifying details only in the bank’s secure channel.
For a debit without confirmation, use the failed-payment process instead of assuming the limit message means no funds moved.
Reviewed on 27 October 2026. Bank and app controls can change; published examples do not replace account-specific confirmation.
