| App / channel | Axis Bank account UPI through open and supported third-party UPI apps; Axis also documents Lite, AutoPay, Credit on UPI and UPI Circle capabilities across its payment stack. | 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 | Link an eligible Axis account using the registered mobile/device flow in open or a participating UPI app. Axis migration material confirms active debit-card/account-holder requirements for migrated accounts; generic eligibility remains account/app dependent. | 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 | Ordinary account-funded UPI uses the UPI PIN and device/account security controls. UPI Lite transactions on an enabled app do not require the UPI PIN; RuPay credit-card UPI uses its own 6-digit UPI PIN rather than the 4-digit card PIN. | 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 | Current Axis UPI terms: up to ₹1,00,000 per transaction when funding from an Axis Bank account. Other-bank accounts may use different issuing-bank limits; the engine does not turn this per-transaction statement into an unsupported universal Axis daily ceiling. | 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 | Migration-specific evidence: newly re-registered migrated Citi accounts were limited to ₹5,000 in the first 24 hours on Android and ₹25,000 over the first 120 hours on iOS (₹5,000 per 24 hours). Because that source is migration-specific, generic Axis registrations follow live app/bank controls unless separately documented. | 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 | Axis terms explicitly recognize UPI Lite without UPI PIN but contain legacy ₹500 wording plus 'or as prescribed by NPCI'. Current RBI/NPCI controls are used: ₹1,000 per Lite transaction and ₹5,000 maximum stored balance, subject to any lower live app restriction. | 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 | Axis's current credit-card MITC requires the registered card mobile number and a separate 6-digit UPI PIN; only eligible RuPay P2M flows are allowed. P2P, P2PM, cash withdrawal, digital-account-opening, lending, eRUPI, IPO, foreign inward remittance and mutual-fund categories are excluded, and existing UPI plus card limits both apply. | 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 | Axis migration material confirms UPI AutoPay/recurring mandates. Mandates are stored separately from one-off transfers because authorization, recurrence, pause/revoke and merchant/use-case rules differ. | 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 | UPI/card-funded disputes can be raised with Axis or the UPI app used for the transaction. Device changes can require re-registration, and the prior device can be deregistered for linked card-on-UPI access. | 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. |
|---|