| Channels | INDIE/IndusMobile for retail mobile transfers; IndusNet for retail Internet Banking; IndusDirect for corporate Internet Banking; RTGS is also available at branch. | Canara ai1 Mobile Banking, Internet Banking and branch. The detailed cooling/₹7.5 lakh interbank figures in this profile are explicitly mobile-channel rules. |
|---|
| Authentication | 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. | Canara ai1 beneficiary transfer uses MPIN plus OTP for IMPS/NEFT/RTGS (UPI uses UPI PIN and is modeled separately). |
|---|
| NEFT | 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. | RBI NEFT has no system floor/ceiling and settles 24x7 in 48 half-hourly batches. Canara ai1 applies the mobile interbank daily ceiling up to ₹7.5 lakh; savings-bank online NEFT is nil-charge under the current service schedule. |
|---|
| RTGS | 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. | RBI minimum ₹2 lakh, 24x7 real-time and no RBI upper ceiling. Canara ai1's mobile interbank daily cap can still constrain the transfer; the current Canara schedule lists outward RTGS ₹24.50/₹49.50 + GST by slab. |
|---|
| IMPS | 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. | Instant 24x7 with NPCI ₹5 lakh per-transaction ceiling. Canara ai1 remains subject to the ₹7.5 lakh/day mobile interbank aggregate; Direct Pay without beneficiary is separately ₹25,000/day. |
|---|
| Beneficiary controls | 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. | New Canara ai1 beneficiary: no transfer for first 1 hour; after 1 hour and up to 12 hours, up to ₹50,000; after 12 hours, full permitted daily limit. Night-time additions use the bank's 6 AM timing rule. |
|---|
| Security cooling | 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. | New Mobile Banking registration: first 24h cumulative ₹15,000, split ₹5,000 Quick Pay + ₹10,000 to a new beneficiary after one hour. Standing instruction to a newly added beneficiary is enabled after 24h. |
|---|
| Charges | 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. | Current schedule: online NEFT nil for SB customers; RTGS outward ₹24.50 (₹2–5L) / ₹49.50 (>₹5L) + GST; IMPS Internet/Mobile below ₹1k nil, then ₹3/₹5/₹8/₹15/₹20 + GST by slab up to ₹5L, with stated exempt account classes. |
|---|
| Failure / reversal | 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. | Canara's RTGS/NEFT FAQ provides return/escalation routes for non-credit/delay. Pending/failed IMPS should be handled through the bank's transaction-status/support process rather than retried blindly. |
|---|