| App / channel | UPI through Kotak Mobile Banking/BHIM UPI and supported UPI apps linked to an eligible Kotak account; eligible Kotak RuPay credit cards can be separately linked for merchant UPI. | Canara ai1Pe is a multi-bank UPI app supporting Canara and other UPI-enabled bank accounts, with UPI Circle, AutoPay, UPI Lite, merchant payments, analytics and QR flows. |
|---|
| Registration | Create/link the UPI ID/VPA against the eligible Kotak account using the registered mobile/device journey and set the UPI PIN. Newly linked RuPay credit cards follow a separate card-linking and UPI-PIN flow. | Download ai1Pe, verify mobile number by SMS, set app passcode, link the eligible bank account and activate using debit card or Aadhaar OTP before setting the UPI PIN. |
|---|
| Authentication | Account-funded UPI uses the UPI PIN. Kotak states that card-funded UPI uses a UPI PIN distinct from the credit-card PIN; the current RuPay FAQ says UPI PIN change for the linked card is not presently available through that flow. | Ordinary UPI uses UPI PIN plus device/account controls. Canara UPI Lite permits eligible payments up to ₹1,000 without UPI PIN after Lite enablement; delegated/card-funded flows use their own authorization rules. |
|---|
| Standard limits | ₹1 lakh maximum daily UPI transfer is consistently stated, but current bank pages differ on transaction count: Scan & Pay says 10 transactions/day while the BHIM UPI FAQ says up to 20/day. Gallery-uploaded QR is limited to ₹2,000 per transaction on the reviewed Scan & Pay page. | P2P: ₹1 lakh per transaction and ₹1 lakh/day, max 20/24h. Verified/special merchant P2M: ₹2 lakh per transaction/day. IPO/Retail Direct: ₹5 lakh per transaction and ₹10 lakh/day. Hospitals/education and tax: ₹5 lakh per transaction/day. QR from gallery: ₹2,000 per transaction / ₹10,000 daily, max 5/day. |
|---|
| Security cooling | Current Kotak help: transactions are restricted to ₹5,000 during the first 24 hours after UPI registration. | New UPI user on any enabled app with Canara remitter: Android first 24 hours up to ₹5,000; iOS first 72 hours up to ₹15,000 total, limited to ₹5,000 in each 24-hour cycle. |
|---|
| UPI Lite | Kotak's April 2026 first-party educational guidance reflects the current system framework—₹1,000 per Lite transaction and ₹5,000 wallet balance with Auto Top-Up. Because that is educational rather than a channel entitlement page, the profile does not claim every Kotak UPI app/version exposes Lite. | Current Canara terms: ₹1,000 per UPI Lite transaction, ₹5,000 maximum Lite balance and ₹10,000 cumulative daily spend. Lite is an on-device balance enabled from one eligible linked account and does not require UPI PIN for eligible Lite payments. |
|---|
| RuPay credit-card UPI | Kotak RuPay credit-card UPI permits merchant P2M, not person transfers/receipts. Current bank FAQ states ₹1 lakh/day per card, ₹2 lakh/day for specified special cases, subject to available credit; first 24 hours after linking are capped at ₹5,000. P2P/P2PM, cash withdrawal, digital account opening, lending, eRUPI, IPO, foreign inward remittance and mutual funds are restricted. | Canara's current UPI debit table separately lists RuPay credit-card-on-UPI merchant/special-category P2M at ₹2 lakh per transaction and ₹3 lakh/day. Linking uses eligible RuPay card details/OTP and a 6-digit UPI PIN; this card-funded ceiling does not alter P2P account limits. |
|---|
| AutoPay / mandates | Kotak exposes UPI AutoPay management and merchant UPI mandate create/modify/revoke/execute/notification/history capabilities. A mandate's own recurring authorization is not treated as the ordinary P2P transfer limit. | Canara explicitly supports UPI Mandate/AutoPay for recurring/future payments and separately documents higher no-additional-factor e-mandate processing for specified merchant categories under current rules. |
|---|
| Failure / recovery | Kotak provides in-app transaction history/dispute support and UPI block/unblock help. Re-registration after mobile changes and linked-card issues should follow the current bank/app flow rather than assuming prior device credentials persist. | Device change/Lite disablement has a defined balance-return process in Canara's Lite terms. Account/app support and UPI dispute/reversal processes apply for failed transactions, while re-registration can trigger the documented cooling state. |
|---|