Transaction Wise Transfer Limits for Bank Remittances
Most people learn their bank’s transfer limit the day it stops them from sending money. A wire that should be routine gets kicked back at the branch counter, a UPI push declines with a cap message, or an app quietly refuses to raise the daily total. None of these are random. They are all pieces of the same layered limit structure that Indian banks apply to bank remittances.
This piece walks through the limits transaction by transaction: how much you can move in a single push, how much across a day, how those numbers change based on whether you are at a branch, on net banking, or in the mobile app, and what actually needs to happen to push the ceiling higher.
Why Banks Set Per Transaction Caps
Per transaction limits are not just a business policy. They are shaped by three overlapping forces.
The first is regulation. The Reserve Bank of India sets outer boundaries for retail payment channels such as UPI, IMPS, and NEFT. A bank cannot let a UPI push exceed the network cap even if it wanted to.
The second is risk. Each channel and each customer tier carries a different risk profile. A branch officer authorising a wire with wet signature and physical KYC is a lower risk transaction than a login pin approving the same amount through an app. Banks price the risk with a lower cap on the higher risk channel.
The third is fraud containment. If a customer’s credentials are compromised, a per transaction cap is the first line of defence. A daily aggregate cap is the second. Together they contain the maximum loss the bank absorbs before the fraud is caught.
Per Transaction Caps by Channel
The current per transaction caps for bank remittances in India sit roughly in these bands:
- UPI allows up to INR 100,000 per transaction for most everyday uses, up to INR 200,000 for select categories such as education fees and hospital payments, and up to INR 500,000 for capital market payments to registered brokers.
- IMPS through mobile banking or net banking allows up to INR 500,000 per transaction. Some banks offer a lower default that customers can raise.
- NEFT has no upper cap at the network level. Banks set their own maximums, which usually range from INR 500,000 to INR 2,500,000 online and higher at branches.
- RTGS has a minimum of INR 200,000 per transaction. There is no upper cap at the network level, so RTGS is the standard rail for high value bank remittances.
- Wire transfers to foreign accounts are treated as separate LRS transactions. The individual annual ceiling is USD 250,000, split across as many transactions as the customer chooses.
These numbers are the network side. What actually gets processed depends on the customer’s specific product tier and the channel they are using.
Daily Aggregate Limits
A single transaction cap is only half the picture. Banks also apply daily aggregate limits across channels.
A typical current account holder using a private bank’s mobile app might see a daily aggregate of INR 1,000,000 across IMPS, NEFT, and UPI combined. A savings account holder on the same app might see INR 500,000. Premium banking tiers push the aggregate to INR 2,500,000 or higher.
The daily aggregate cap resets at midnight, but the reset time follows the bank’s clock, not the user’s. That distinction matters for anyone trying to time a large payment across the day boundary.
Some banks let customers raise the daily aggregate temporarily by adjusting a slider in the app. Others require a request through customer service. The channel matters as much as the amount.
Branch vs Online Limits
This is where the layers get most confusing.
At a branch, per transaction limits are usually higher because the officer processing the payment has verified the customer’s identity in person. A branch wire of INR 5,000,000 is routine at most banks; the same wire attempted online might require a special approval flow.
Online, the caps are lower by default because the bank is relying on multifactor authentication rather than physical presence. Net banking is usually the highest online tier, with mobile app coming in below net banking, and third party apps like UPI intermediaries coming in lowest.
The gap between branch and online limits is closing but not gone. If you are moving a large sum and the online cap gets in the way, the branch remains the fastest path in most cases.
Reality Check: Limits Live in a Grid, Not a Line
The mistake most remitters make is thinking of transfer limits as a single number. In practice, every payment sits inside a grid of caps.
The channel determines the maximum. The customer segment sets the default within that channel. The daily aggregate cuts across all channels. The bank’s fraud engine can drop the effective cap for any specific transaction if it flags an anomaly. And the regulator’s cap sits on top of the whole grid.
Any of these can bind first. The reason a UPI push fails is often not the UPI cap but the daily aggregate, and the reason an IMPS push fails is often the fraud engine flagging the beneficiary as new. Understanding the layers is more useful than memorising a single number.
How Banks Handle Exceptions
When a customer needs to move more than their standing limit, banks have three ways to accommodate:
- Standing instructions, where the customer submits paperwork to raise the online cap permanently. This usually needs branch KYC refresh, income proof, and sometimes a purpose justification.
- Ad hoc branch clearance, where the customer visits the branch on the day of the transfer and requests a one time exception. This is faster than paperwork but requires physical presence.
- Escalation through relationship managers, available to priority and premium tier customers. The RM raises the cap through a back office queue that usually clears in a few hours.
Which path is available depends on how the customer is segmented. First time and low tier customers are usually pushed toward the standing instructions route. Priority customers get the RM path.
Comparison: Bank Remittance Channels at a Glance
| Channel | Typical Per Transaction Cap | Speed | Best Fit |
|---|---|---|---|
| UPI | INR 100,000 to 500,000 by use case | Instant | Everyday payments, small transfers |
| IMPS | INR 500,000 | Instant | Medium bank to bank transfers |
| NEFT | INR 500,000 to 2,500,000 online | Half hourly batches | Salary, vendor, EMI payments |
| RTGS | No upper cap, minimum INR 200,000 | Near real time | High value bank remittances |
| SWIFT wire | Bank set, often USD 250,000 online for LRS | 1 to 3 business days | Foreign currency wires |
What NRIs and Overseas Remitters Should Know
For NRIs sending money into India through a US or other overseas bank, the domestic Indian transfer limits are not the binding constraint. What binds is the funding channel on the sender side, the compliance flow on the beneficiary bank, and any RBI reporting on the inbound remittance.
The inbound side of India is uncapped by the RBI for individual remittances, but the recipient bank still enforces its own daily aggregate on how much can be credited to a beneficiary account in one day. If a large inbound wire lands, it may be held for a compliance review even though it is well within the annual LRS window on the outbound side.
Cross border rails that work directly into UPI or IMPS get around some of this. A tool like Sliq Pay routes USD from a US bank into an Indian bank account, UPI ID, phone number, or email address, with settlement in seconds up to INR 200,000 on UPI and INR 500,000 on IMPS. Above the instant rail caps, the transfer settles within hours through the alternative rails.
Practical Tips
Check your current daily aggregate before you attempt a large payment. Most bank apps show it under settings or profile. If the aggregate is lower than the transfer you need, raise it before you initiate.
Split a large transfer across days rather than fighting the cap. Two IMPS pushes of INR 400,000 on two days beat one RTGS at INR 800,000 for most cost sensitive users, because the fees stack differently.
If you are moving inbound money from overseas to a large Indian bank account, warn the beneficiary bank in advance. Most banks have a treasury desk that can pre approve an inbound wire so it is not held on arrival.
For recurring high value bank remittances, invest in a one time standing instruction rather than fighting the daily cap every month. The paperwork takes an hour and saves years of friction.
FAQs
Why is my UPI transaction failing at INR 100,000? UPI has a standard per transaction cap of INR 100,000 for most everyday uses. Categories like education fees, hospital payments, and capital market pushes allow up to INR 200,000 or INR 500,000, but you have to select the right merchant category for the higher cap to apply.
Can I raise my daily transfer limit online? Most banks allow a temporary raise through the app or net banking, up to a hard ceiling set by product tier. Beyond that, the change requires branch paperwork or a relationship manager request.
Is there a difference between branch and app transfer limits? Yes. Branch limits are usually much higher because in person KYC is stronger evidence for the bank. App limits are lower by default and are raised through customer initiated adjustments.
Does RTGS have a maximum? No network cap. Banks set their own maximums, which can go into crores for corporate customers. RTGS has a minimum of INR 200,000 per transaction.
How does an NRI send more than the per transaction cap through IMPS? IMPS caps out at INR 500,000. Above that, the bank routes to RTGS or holds the transfer for hourly settlement. Cross border payments apps like Sliq Pay handle the amount split automatically so the sender does not have to plan around the rail cap.
Why did my transfer get held even though I was within the cap? The bank’s fraud engine can hold any specific transfer if it triggers an anomaly signal. Common triggers are a new beneficiary, an unusually large first payment, or a payment initiated from a new device.
Is there a way around the daily aggregate limit for a one time large transfer? Yes. Branch clearance the same day, or a relationship manager escalation, or a scheduled standing instruction submitted in advance.
Before You Send
Bank remittances in India work well when the sender knows which cap will bind first and plans around it. Fighting the app cap while the branch has a higher one is wasted effort. Fighting the daily aggregate when the transfer could have been split across two days is a fee sink.
If you are handling regular cross border inflows into India, tools like Sliq Pay carry the last mile onto the domestic rails without adding another cap layer, so the only limits you have to think about are the ones already sitting on the receiving side.
Disclaimer
The information provided on this blog is for general informational purposes only and does not constitute legal, financial, tax, or professional advice. Product features, pricing, eligibility, and availability may vary by country, user type, regulatory requirements, and are subject to change.
Please refer to Sliq Pay’s Terms of Use and official product pages for the most accurate and up-to-date information. Sliq Pay makes no representations or warranties regarding the completeness, accuracy, or reliability of the content.
