| 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. | IDFC FIRST Bank Mobile Banking/UPI channel for eligible account-funded UPI, plus supported third-party UPI apps and separate bank merchant/QR services. |
|---|
| 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. | Register/link eligible bank account(s) in the bank's UPI/mobile channel using the registered mobile and app/device flow. The bank's UPI app can also link existing eligible accounts for send/collect usage. |
|---|
| 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 authorization. UPI Lite is enabled separately for PIN-less eligible small-value transactions; RuPay credit-card UPI requires its own UPI PIN and the card-registered mobile number. |
|---|
| 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. | Current bank UPI page: ₹1 lakh/day fungible for P2P and non-verified-merchant payments, ₹2 lakh/day for verified merchants, and up to ₹1 lakh per P2P transaction from IDFC FIRST savings accounts. |
|---|
| Security cooling | Current Kotak help: transactions are restricted to ₹5,000 during the first 24 hours after UPI registration. | No current first-party bank-account UPI post-registration cooling figure is hard-coded from this evidence set. The profile leaves that state to the live app/bank control instead of borrowing the credit-card linking rule. |
|---|
| 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. | IDFC FIRST's current first-party Lite guidance states ₹1,000 per UPI Lite transaction and ₹5,000 aggregate wallet balance, with single activation through mobile banking and no 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. | FIRST Digital RuPay credit-card UPI uses the same registered mobile number, card details/OTP and UPI PIN. For the first 24 hours after UPI PIN generation, card-funded UPI is limited to ₹5,000; afterward the bank states ₹1 lakh/day under the current card guidance, subject to issuer/card/app controls and eligible merchants. |
|---|
| 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. | UPI mandates remain a separate recurring-authorization layer. IDFC FIRST merchant UPI infrastructure supports payment/collection workflows; no bank-specific mandate ceiling is invented where current consumer evidence is not explicit. |
|---|
| 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. | Collect requests can expire; failed/disputed transactions should be handled through the bank/app support and merchant/UPI dispute channel relevant to the transaction. Card-funded issues remain tied to the linked card as well as the UPI app. |
|---|