| App / channel | UPI through YONO SBI, BHIM SBI Pay and other supported UPI-compatible channels linked to an eligible SBI account. | YES Pay Next UPI/payment app with transaction history, support/complaint and merchant-payment functions. |
|---|
| Registration | Register the eligible account on the supported UPI channel using the bank-registered mobile/device process and establish the UPI PIN required for ordinary debit-account transactions. | Register the app/UPI relationship on the supported device and verify the eligible linked bank account/mobile setup. |
|---|
| Authentication | Ordinary UPI uses UPI PIN/UPI security controls. Current SBI guidance states UPI Lite can make eligible small-value payments up to ₹1,000 without entering the UPI PIN. | Ordinary UPI uses the UPI security/PIN layer; device changes create a bank-defined cooling state before full value access returns. |
|---|
| Standard limits | After cooling, current SBI material states ₹1 lakh per transaction and ₹1 lakh per day for ordinary P2P/P2M, with a maximum 20 P2P transactions per 24 hours per account; P2M transaction count is governed by the value cap rather than the same 20-count rule. | Current YES Pay Next FAQ states a maximum 20 UPI transactions aggregating to ₹1 lakh in a day for its ordinary UPI flow. |
|---|
| Security cooling | After setting/resetting UPI PIN: Android first 24 hours ₹5,000 maximum transaction/cumulative day; iOS ₹5,000 per day for the first five days. SBI says these controls can change under NPCI/bank discretion. | New registration or device switch: current YES Pay Next FAQ states a maximum ₹5,000 during the first 24 hours. iOS has additional early-use restrictions in YES BANK material, so the live app/current FAQ controls the exact post-24-hour progression. |
|---|
| UPI Lite | Current SBI page: up to ₹1,000 per UPI Lite payment without UPI PIN and ₹5,000 maximum Lite balance, consistent with the current RBI/NPCI framework. | UPI Lite is supported in YES BANK’s current payment stack; current RBI/NPCI limits are ₹1,000 per eligible payment and ₹5,000 maximum stored balance. Bank/app implementation controls such as auto top-up are kept separate. |
|---|
| RuPay credit-card UPI | Keep RuPay credit-card-on-UPI separate from SBI deposit-account UPI. NPCI restricts linked RuPay credit-card UPI primarily to eligible merchant flows and sets the usable amount to the lowest applicable issuer risk/card/customer limit rather than a guaranteed bank-account UPI ceiling. | Eligible RuPay credit-card-on-UPI is merchant-oriented and subject to card/issuer/customer limits under NPCI rules; this profile does not treat the bank account’s ₹1 lakh/day statement as a guaranteed card-funded allowance. |
|---|
| AutoPay / mandates | UPI AutoPay/e-mandates are a separate recurring-payment authorization layer. NPCI supports pause, unpause, modify and revoke controls and generally sends a pre-debit notification before execution. | YES BANK supports recurring/AutoPay payment capability; UPI AutoPay is modeled with its own mandate lifecycle rather than as a normal send-money transaction. |
|---|
| Failure / recovery | SBI advises using official channels for UPI support and safety; PIN reset/re-registration can itself trigger the documented cooling state, so restored access does not imply immediate steady-state limits. | The current YES Pay Next FAQ documents complaint raising from the app and security cooling after a device switch; live app/support controls remain authoritative for re-registration/recovery. |
|---|