Glitch in OnlineSBI (State Bank of India’s online banking system)
What do you think about this video on online banking?
A glitch in OnlineSBI, State Bank of India’s online banking system that doesn’t disable ‘high security transaction’ settings(an SMS containing a transaction code is sent to your cellphone, which has to be entered to complete a transaction) when you disable it from the website. Since SMSes are banned in J&K, this is a big conundrum. Obviously, there’s a simple workaround. WORKAROUND – If you have a relative outside J&K, tell them that they’ll get an SMS containing a 4 digit number which they should tell you. Now change the mobile number in your OnlineSBI’s profile to your relative’s. SBI is an obdurate, it has messed up a lot. Many of it’s ‘Yuva card’ users face a lot of problems, which the banking giant doesn’t resolve even after 6 months of consistent complaining. Now the slapdash system of it’s website corroborates to the fact that things need to be changed….
Tagged with: bank • banking • Glitch • India's • online • OnlineSBI • state • system
Filed under: Online Banking
Like this post? Subscribe to my RSS feed and get loads more!
@ hotchat321 : Thanks 4 ur comment but it doesn’t work that way. Check it out urself if u hav an OnlineSBI account.
I complained but the problem still persists. However, I’m using a workaround, I’ve changed my phone no. 2 my brother’s no. in Punjab, so I do not face transaction problems now.
But this problem speaks volume about the fecklessness of SBI & the company that makes it’s software. I’d hav had them all(software team) fired.
Is your problem solved or not still ..did you complain to sbi???
I think to disable the high security you will need the otp password in your mobile.For example what is the use of high security password if somebody steals your login password they will not be able to transact unless they know otp password.so to disable high security first the otp password should be entered.
The glitch is still there & SBI officials don’t give a damn
OnlineSBI had a maintenance downtime on 4th September, so maybe the glitch has been removed. Or maybe itz still dere…..
Read the above description