| Channels | Kotak Bank App, Kotak Net Banking and branch for NEFT/RTGS; IMPS through digital banking. One-time transfers without beneficiary use their own combined limit. | INDIE/IndusMobile for retail mobile transfers; IndusNet for retail Internet Banking; IndusDirect for corporate Internet Banking; RTGS is also available at branch. |
|---|
| Authentication | Authenticated Net/Mobile banking and the account's signing/transaction authority apply. Kotak's one-time transfer flow uses channel authentication, while saved-beneficiary transfers remain subject to beneficiary activation and CRN limits. | 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 | Digital NEFT is available 24x7 except Kotak's published 11:30 PM–12:30 AM no-initiation window. Existing/customer-set limits apply through 9:30 PM; up to ₹10 lakh is shown for 9:30–11:30 PM, and the bank publishes a maximum permissible ₹50 lakh per transaction from 12:30–7:30 AM, still subject to the overall daily limit. | 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 | Minimum ₹2 lakh. Kotak lists RTGS 24x7 except 11:30 PM–12:30 AM and a maximum permissible ₹5 crore per transaction between 12:30–7:30 AM; the customer/CRN daily limit can be lower. | 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 | Instant 24x7 through Net/Mobile. Current default CRN limits apply across IMPS with the customer's overall controls; Kotak's separate beneficiary article states up to ₹5 lakh daily IMPS after its stated first-day beneficiary restriction, so this is kept as source-scoped rather than used to overwrite the newer segment table. | 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 | Main current limit page: add up to 10 beneficiaries/day for Privy/Wealth/Solitaire/Non-Resident or 5/day for Regular/811; newly added beneficiary caps are ₹3 lakh, ₹50,000 and ₹25,000 by segment, after a 30-minute no-transfer cooling period. | 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 | A separate current Kotak help article says the limit is ₹25,000 for the first 24 hours after a beneficiary is added or edited. Because this conflicts with the segment-based 30-minute/cap table, both are retained and the live channel screen should control at transfer time. | 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 | Account/channel specific. Reviewed Kotak savings schedule: Net/Mobile NEFT/RTGS nil; branch NEFT ₹2/₹4/₹14/₹24 by amount slab and branch RTGS ₹20/₹40 by slab. IMPS pricing can differ by account proposition, so no universal charge is inferred. | 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 | Kotak exposes transaction status, service-request and dispute/support routes. For NEFT credit timing, the bank notes beneficiary-bank processing can affect receipt; pending transfers should be checked before retrying. | 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. |
|---|