| 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. | bob e-Pay, Bank of Baroda's UPI app, can link eligible accounts from UPI-live banks and supports QR, Send/Collect, account+IFSC, Global UPI, Tap & Pay, Lite, AutoPay, RuPay credit cards and UPI Circle. |
|---|
| 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 with the same mobile number used by the linked bank account, complete app SMS/mobile verification, create VPA/login PIN, add the eligible account and set UPI PIN using the linked debit-card/issuer authentication flow. |
|---|
| 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. | Two-factor/device-binding controls apply. bob e-Pay supports UPI PIN for ordinary transactions and current features include biometric/face-authentication paths for selected UPI PIN/transaction journeys; Lite has its own PIN-less small-value state. |
|---|
| 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. | P2P/P2PM and ordinary P2M: ₹1 lakh per transaction and ₹1 lakh/day, 20 transactions/day/account. Specified-MCC P2M: ₹2 lakh per transaction/day. IPO and RBI Retail Direct collect: ₹5 lakh per transaction and ₹15 lakh/day. USSD (*99#): ₹5,000 per transaction/day. |
|---|
| 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. | Current table: after setting/resetting UPI PIN and fresh registration/re-verification of device, fund transfer is limited to ₹5,000. The security section describes ₹5,000 for the new user's first transaction; the live app remains controlling if additional risk restrictions apply. |
|---|
| 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. | bob e-Pay offers UPI Lite, but the bank page still displays legacy ₹500/₹2,000/₹4,000 numbers in its FAQ. Current RBI/NPCI limits are therefore used for current system context—₹1,000 per transaction and ₹5,000 stored balance—while the stale bank copy is surfaced as an evidence conflict rather than silently overwritten. |
|---|
| 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. | bob e-Pay can link eligible RuPay credit cards from participating issuers. Bank FAQ states credit-card UPI is only for P2M and carries no linking/transaction fee from bob e-Pay; available credit and issuer/UPI restrictions still apply. |
|---|
| 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 AutoPay is supported and mandates can be managed in-app. Recurring instructions remain a separate authorization lifecycle from one-off P2P/P2M limits. |
|---|
| 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. | bob e-Pay provides dispute management/history, real-time/settlement reversals and complaint paths. More than three wrong UPI PIN attempts can cause temporary blocking and repeat failures can require UPI PIN regeneration; device/SIM changes require re-registration. |
|---|