Why Does Your YES Bank Mobile Banking Login Keep Failing — and Which Fix Should You Try First?
Digital Banking · Security · India
Why Does Your YES Bank Mobile Banking Login Keep Failing — and Which Fix Should You Try First?
The screen says the same thing every time. You tap in your PIN, the loader spins, and back comes a message about being unable to perform the action. You clear the cache. You reinstall. Nothing. Then you notice the app works on mobile data but not on Wi-Fi, or that it stopped the day you moved your SIM to a new phone. YES Bank mobile banking login failures almost never have one universal cause, but they do fall into a small set of patterns, and those patterns have a strict order in which they should be tried. Getting the order wrong is what turns a five-minute fix into a two-day one, because three wrong attempts will lock you out entirely.
Four causes, one order, and a clock that decides your liability
Most IRIS login failures are one of four things: an outdated app, a network path the app rejects, SIM binding breaking after a device or SIM change, or a forgotten PIN. Try them in that order, because three wrong PIN attempts lock the app for 24 hours. Never call a customer care number you found through a search engine. If money has actually moved, the clock that matters is the RBI one: report within 3 working days for zero liability.
The platform you are logging into
Scale matters here because it explains both the reliability and the occasional wobble. YES BANK reported over 1,300 branches, more than 200 Business Correspondent Banking Outlets and over 1,350 ATMs across more than 300 districts as of its Q4 FY26 results. On the digital side the bank has described itself as processing roughly one in three digital payment transactions in India, with a UPI market share reported at 56.4 per cent and around 90 per cent of its transactions running through digital channels. The app you are logging into is not a side channel; for most customers it is the bank.
The current app is IRIS by YES BANK, which replaced the older YES Mobile experience. Its store listing highlights biometric login, two-factor authentication on payments, and SIM binding, which ties your credentials to one trusted device. That last feature is genuinely good security and also the single most common reason a login that worked yesterday stops working today.
Four credentials, and why people mix them up
A large share of failed logins are not failures at all. They are the right PIN typed into the wrong box. IRIS uses separate credentials for separate jobs, and they are not interchangeable with your net banking password.
| Credential | What it does | Typical length | How to reset |
|---|---|---|---|
| APIN | Opens the app at the login screen | 6 digits | Forgot APIN on the login screen, then card or account validation |
| MPIN | Authorises transactions inside the app | Set at registration | Forgot MPIN, then validate via debit card, credit card, net banking or loan account |
| UPI PIN | Authorises UPI payments only | 4 or 6 digits | Reset inside the UPI section using debit card details |
| Net banking password | Website login only | Alphanumeric | Reset on the net banking site |
| Biometric | Shortcut for APIN after enrolment | Device-held | Re-enable under More, then Settings |
Guidance published on the IRIS app notes that existing net banking credentials can be used to register on the app, and that a customer who has never used net banking can still register using credit card, debit card or loan account details. Registration and login are different things, though. Once you are registered, the website password will not open the app.
First-time registration, stage by stage
If you are setting up rather than recovering, the sequence below is what to expect. The whole process usually takes under ten minutes provided your mobile number at the bank is current, which is the one thing you cannot fix from your sofa.
Why the login fails, ranked by how long the fix takes
Work down this list rather than across it. The cheap fixes sit at the top for a reason, and every wasted PIN attempt pushes you closer to a lockout you cannot undo yourself.
The Wi-Fi quirk that looks like an outage
Users have publicly reported the app failing on Wi-Fi while working normally on mobile data, with other banking apps unaffected on the same network. If the app throws a generic inability-to-perform-the-action message, switch off Wi-Fi and retry on mobile data before you conclude anything is wrong with your account. Corporate networks, public hotspots and some home routers with DNS filtering are the usual culprits, and this single test resolves a surprising share of reported outages.
SIM binding, and why a working phone suddenly stops working
The IRIS app store listing describes SIM binding as tying login credentials to a single trusted device to protect against fraud. In practice the app checks that the mobile number registered with the bank is present and active in the handset it is running on, usually by sending a silent SMS that never appears in your inbox. If that check fails, registration and login fail with it, and the message you see rarely explains why.
This is why the failure so often coincides with something that had nothing to do with banking. Moving to a new phone breaks it. Swapping a physical SIM for an eSIM breaks it. Putting the registered SIM in slot two of a dual-SIM phone while slot one holds a different number frequently breaks it. So does a SIM that is technically active but has no outgoing SMS balance on a prepaid plan, because the silent message never leaves the device. None of these are account problems, and none of them are fixed by reinstalling.
The fix in every case is the same: put the registered SIM into the device you want to bank on, confirm it can send an ordinary SMS to any number, and re-register. The binding to your old handset is released in the process, which is also why you should block mobile banking access through customer care before disposing of an old phone rather than after.
What the error actually means
| What you see | Likely cause | What to do |
|---|---|---|
| Unable to perform the required action | Network path, server load, or an outdated build | Switch to mobile data, then update the app, then retry |
| Invalid APIN | Wrong credential, or caps from a password manager | Stop after two tries and use Forgot APIN |
| Account locked | Three consecutive wrong entries | Wait 24 hours or call phone banking to unlock |
| SIM verification failed | New device, new SIM, eSIM swap, or dual SIM in the wrong slot | Ensure the registered SIM is active in the phone, then re-register |
| Registered number mismatch | Bank holds an old mobile number | Update it at a branch or through a verified request |
| Device not trusted | SIM binding still points at the old handset | Re-register on the new device; the old binding is released |
| UPI PIN incorrect | UPI PIN confused with MPIN | Reset the UPI PIN separately using debit card details |
| Session expired repeatedly | Battery optimisation killing the app in background | Exclude the app from battery optimisation in phone settings |
The lockout, and how to get out of it
Published guidance on YES Bank mobile banking indicates that entering the wrong credentials three times locks the app, after which you either wait at least 24 hours, contact customer support, or reset through the recovery route. The reset itself is straightforward once you know which door to use.
- Stop after the second failed attempt. The third one costs you a day. There is no counter on screen telling you where you stand, so treat two as the ceiling.
- Use Forgot MPIN on the login screen. Guidance on the IRIS app describes resetting through product validation using credit card, debit card, net banking or loan account details.
- Have the validation instrument physically present. Debit card number, expiry and ATM PIN are typically needed. Fumbling here burns attempts on a second counter.
- Set a new PIN that is not a variant of the old one. Incrementing the last digit is the most commonly guessed pattern in the country.
- Re-enable biometrics afterwards under More, then Settings, so daily logins stop touching the PIN at all.
- If the handset is lost, do not attempt any of this. Guidance for IRIS users is to request a call back from customer care or visit a branch to block mobile banking access.
Never search for a bank helpline number
Fake customer care numbers planted in search results, map listings and social replies are one of the most reliable fraud vectors in India. The person who answers will sound professional, will know your bank, and will ask you to install a screen-sharing app or read out an OTP. YES BANK publishes contact numbers including 1800 1200 for phone banking, 1800 103 1212 and 1800 103 6000 for card queries, 1860 210 1200, and WhatsApp banking on +91 82912 01200, with international support on +91 22 5079 5101. Timings vary by line and some lines are card-specific. Verify any number against yes.bank.in or the contact section inside the app before dialling it, and remember that no bank employee will ever ask for your APIN, MPIN, UPI PIN, OTP or card PIN.
When the login works but the payment does not
A different complaint often gets reported as a login problem: you are inside the app, but a transfer keeps bouncing. That is usually a limit, not a fault. NPCI sets the ceilings and your bank sets its own cap underneath them.
So a payment that fails at 8 pm after a busy day is far more likely to be the twentieth transaction than a broken login. Switching to IMPS or NEFT inside the same app, or waiting for the rolling 24-hour window to reset, resolves it without any support call.
If money has actually moved, this is the only clock that matters
Suppose the login failure was not a glitch. Suppose someone else got in. At that point the technical questions stop mattering and a legal one takes over, because the RBI circular of 6 July 2017 on limiting customer liability in unauthorised electronic banking transactions fixes your exposure by how fast you report, not by how much was taken.
Call 1930
Zero liability
Capped liability
Bank policy decides
Bank must resolve
The three working days are counted from the date you received the bank’s communication about the transaction, not from the date you noticed it. If an SMS alert landed at 2 am and you saw it at breakfast, the clock started at 2 am. That is why alerts should never be muted, and why the registered mobile number being current is a security control rather than an administrative detail.
| Account or instrument | Within 3 working days | 4 to 7 working days | Beyond 7 days |
|---|---|---|---|
| Basic savings (BSBD) | Zero | Up to ₹5,000 | Bank’s board policy |
| Other savings accounts | Zero | Up to ₹10,000 | Bank’s board policy |
| Prepaid and gift instruments | Zero | Up to ₹10,000 | Bank’s board policy |
| Credit cards, limit up to ₹5 lakh | Zero | Up to ₹10,000 | Bank’s board policy |
| Credit cards, limit above ₹5 lakh | Zero | Up to ₹25,000 | Bank’s board policy |
The caps apply where the deficiency lies neither with the bank nor with you. Where the bank was negligent, liability is zero regardless of when you report. Where you voluntarily shared credentials without any manipulation, you bear the loss until you report. Once notified, the bank is required to credit the disputed amount as a shadow reversal within 10 working days and to resolve the complaint within 90 days.
Worked example of the liability clock
An alert lands at 2.10 am on a Friday for a debit of ₹48,000 from a regular savings account. Rakesh sees it at 8 am, calls 1930 by 8.20 am and reports to the bank the same morning. The clock started at 2.10 am on Friday, so he is comfortably inside 3 working days and his liability in a third-party breach is zero. Had he assumed it was a mistake and waited until the following Thursday, he would have crossed 7 working days, and the outcome would rest on the bank’s board-approved policy rather than on a fixed cap. The same facts, the same amount, a completely different result, decided by nothing but elapsed time.
Escalating when nothing works
Escalate in order and keep every reference number, because each tier will ask for the one before it. The important judgement is knowing which ladder you are on. A login that will not open is a service problem and belongs on rungs one to three. An unauthorised debit is a fraud problem and jumps straight to rung four while the service ladder continues in parallel. Confusing the two costs time you do not have.
Six habits that prevent most of this
Frequently asked questions
Why does my YES Bank mobile banking login keep failing?
Most commonly one of four things: the app build is outdated, the network path is being blocked, SIM binding has broken after a device or SIM change, or the wrong credential is being entered. Try them in that order. Switching from Wi-Fi to mobile data is the single fastest test and resolves a meaningful share of generic error messages.
How many wrong attempts before the app locks?
Three consecutive wrong entries lock mobile banking access. After that you generally wait at least 24 hours, contact customer support to unlock, or reset through the Forgot MPIN route. Because there is no on-screen counter, stop after two failed attempts and go straight to the reset.
What is the difference between APIN, MPIN and UPI PIN?
The APIN opens the app, the MPIN authorises transactions inside it, and the UPI PIN authorises UPI payments specifically. They are separate, they reset through separate routes, and none of them is your net banking password. Typing the right PIN into the wrong box is one of the most common causes of an apparent login failure.
Can I use my net banking password to log into the app?
Not for daily login. Net banking credentials can be used during registration to validate your identity, and customers who have never used net banking can register using credit card, debit card or loan account details instead. Once registered, the app opens with the APIN or biometrics.
The app works on mobile data but not Wi-Fi. Is my account blocked?
Almost certainly not. Users have publicly reported exactly this pattern, with other banking apps working normally on the same network. It points to the network path rather than your account, and is usually a router, DNS filter or corporate firewall issue. Test on mobile data before assuming anything is wrong.
I changed my phone and now the app will not verify me.
That is SIM binding doing its job. The app ties credentials to one trusted device, so a new handset, a new SIM, an eSIM migration or the registered SIM sitting in the wrong dual-SIM slot all break verification. Put the registered SIM in the new phone, confirm it can send an SMS, and re-register.
What if I have lost the phone with the app installed?
Do not try to troubleshoot. Guidance for IRIS users is to request a call back from customer care or visit the nearest branch to block mobile banking access. Blocking access is the priority; re-registering on a new device can wait until the old one is locked out.
Someone accessed my account. How fast must I report it?
Within 3 working days of the bank’s communication for zero liability in a third-party breach. Between 4 and 7 working days your liability is capped at the transaction value or a ceiling of ₹5,000 to ₹25,000 depending on the account or card type. Beyond 7 working days the bank’s own board-approved policy applies. Call 1930 first, because it can freeze funds in transit.
How long must the bank take to refund an unauthorised debit?
On being notified, the bank must credit the disputed amount as a shadow reversal within 10 working days, value dated to the date of the unauthorised transaction, without waiting for any insurance settlement. The complaint itself must be resolved and liability established within 90 days.
My login works but payments keep failing. Why?
Usually a limit rather than a fault. The standard UPI daily ceiling is ₹1 lakh, most banks allow roughly 20 person-to-person transactions in 24 hours, and new UPI registrations are capped at ₹5,000 in the first 24 hours. Switch to IMPS or NEFT, or wait for the rolling window to reset.
What to do, in one paragraph
Treat login attempts as a scarce resource and spend them last, not first. Update the app, switch off Wi-Fi, check that the registered SIM is in the phone, and only then touch the PIN. Keep the mobile number at the bank current, because it silently controls registration, alerts and your legal protection. Save a verified helpline number now so you never have to search for one under pressure. And if money has moved rather than merely a screen misbehaving, stop reading, call 1930, and report to the bank the same day, because the three working days that decide your liability start from the bank’s alert and not from the moment you noticed.
