| Channels | FedNet Internet Banking and FedMobile; branch/corporate service contexts can have different charge and limit treatment. | INDIE/IndusMobile for retail mobile transfers; IndusNet for retail Internet Banking; IndusDirect for corporate Internet Banking; RTGS is also available at branch. |
|---|
| Authentication | FedNet requires 2FA for transactions of any amount. Current FAQ lists mobile-based OTP/FedSecure, SMS OTP and a hardware-token option for corporates; the selected form factor also affects new-beneficiary activation. | Current INDIE limit increases require OTP and then a four-hour security cooling period. Mobile/Internet transfers otherwise use the channel's authenticated transaction controls. |
|---|
| NEFT | FedNet documents NEFT up to ₹10 lakh as available 24x7 subject to the client's set transaction limit. Enhanced limits beyond ₹10 lakh are available Monday–Friday and eligible Saturdays from 8:45 AM–6:30 PM. | INDIE supports NEFT within the current ₹10 lakh cumulative daily mobile fund-transfer limit. The reviewed mobile page says method-specific limits can vary; v1.39 does not invent a separate NEFT ceiling where current first-party evidence is not explicit. |
|---|
| RTGS | RTGS uses the applicable ₹2 lakh system minimum. FedNet documents transfers up to ₹10 lakh 24x7 subject to the client-set limit, with enhanced limits beyond ₹10 lakh during the published working-day window. | Minimum ₹2 lakh. IndusNet publishes ₹10 lakh for individual customers and ₹25 lakh for non-individual customers; IndusDirect standard permitted cumulative/per-transaction limit is ₹25 lakh. INDIE remains subject to its separate mobile cumulative limit. |
|---|
| IMPS | IMPS is an instant digital rail; the reviewed Federal sources do not provide one clean universal Federal customer maximum, so v1.39 preserves the customer/channel limit model rather than inventing a daily cap. | INDIE supports instant IMPS within the app's cumulative daily transfer control and applicable IMPS rail limit. The current mobile page says method-specific limits can vary rather than publishing one stable universal bank maximum. |
|---|
| Beneficiary controls | Newly added FedNet beneficiaries are activated instantly for most 2FA arrangements, but customers who selected SMS OTP as 2FA have a 24-hour beneficiary activation wait. | IndusMobile FAQ permits up to 5 beneficiary additions/day for Current Accounts and 3/day for Savings Accounts across IndusNet/IndusMobile. The reviewed retail sources do not establish one universal new-beneficiary cooling duration. |
|---|
| Security cooling | Beneficiary cooling is authentication-form-factor dependent, not a universal Federal number. FedNet also allows customer transaction limits to be changed through its limit-management service. | Current INDIE: first registration/device re-registration sets ₹2 lakh for 24h; limit increase uses OTP + 4h cooling with old limit active. Separate IndusMobile FAQ instead states ₹10,000 for 24h after new-user/device/phone registration; conflict retained. |
|---|
| Charges | Current 1 June 2025 schedule: FedNet/FedMobile interbank NEFT/RTGS free; IMPS ₹2.50 up to ₹1,000, ₹5 above ₹1,000–₹25,000, ₹7 above ₹25,000–₹1 lakh and ₹15 above ₹1 lakh. Other transaction contexts can have their own tariffs. | Account-specific. Reviewed Indus Online Savings schedules state no charge on NEFT/RTGS across channels for those variants and show product-level fee treatment; other account propositions can differ. |
|---|
| Failure / reversal | FedNet lets customers track Pending Payments and Payments Made. Its RTGS FAQ states that where the beneficiary bank cannot credit the account, the beneficiary bank returns the funds to the remitting bank within two hours. | IndusMobile says transfer failure can result from beneficiary details or receiving-bank availability; its terms state rejected payments are processed for re-credit within five working days. Check status/support before retrying. |
|---|