An Ahmedabad businessman lost ₹85,000 from his Bank of Baroda account after his phone appeared to undergo a software update and later showed signs of unauthorised activity, according to a report by Nav Gujarat Samay. The case, reported from the Airport police station area, illustrates how a routine smartphone function can become the entry point for a digital-payment fraud when a device suddenly stops responding and the user cannot immediately verify what is happening.
The 71-year-old businessman, Hemvani Hiranand Topandas, lives in Sardarnagar’s Ambawadi Bhilwas and operates a textile-printing shop called Bombay Sticker in Kubernagar. He told the police that the incident began on the evening of October 5, when his phone displayed a software-update notification at around 6 pm. The phone did not remain normally operational for some time. He tried to switch it off, but it did not shut down as expected and later restarted automatically.
The account debit was discovered only the following afternoon. On October 6, while attempting to make a ₹5,000 business payment from his shop, Topandas found that the transaction could not be completed because the account did not have sufficient balance. When he checked his Bank of Baroda account, he found that ₹85,000 had been debited at about 6:15 pm on October 5 through a UPI transfer to a PhonePe identity named “AKASH BATHAM”. The report states that he had not authorised the payment.
The sequence is important because the loss was not identified when the transfer occurred. It was detected when a later, legitimate business payment failed. For a small business owner, the bank balance is part of daily operating capacity: it determines whether suppliers, workers or routine expenses can be paid. In this case, the unauthorised transaction was discovered only when the victim tried to use the account for another purpose.
The report does not establish precisely how the unauthorised UPI transfer was executed. It records the victim’s account that the phone was affected during the software-update episode and that the debit occurred within minutes of the device problem. That distinction matters. A suspicious update notification, a compromised device, stolen credentials and an unauthorised UPI transaction are connected in the reported chronology, but the technical mechanism will need to be determined through the police investigation, bank records and device-level evidence.
This is the institutional challenge in smartphone-based banking: the customer experiences one continuous incident, while responsibility for understanding it is divided among several systems. The phone may involve the device manufacturer or operating-system provider. The payment may involve a bank, a UPI application and the receiving account. The complaint is handled by the police, while the first reporting channel for suspected cyber fraud is the national helpline 1930. The victim therefore has to move quickly across multiple institutions even when the original event has left the device inaccessible or confusing to operate.
Topandas contacted the cybercrime helpline 1930 immediately after discovering the debit and subsequently filed a complaint at the Airport police station, according to the report. The supplied account does not state whether the funds were frozen or recovered, whether the receiving account was placed under restriction, or whether investigators identified the person associated with the PhonePe UPI identity. Those outcomes remain material to the case because the time between an unauthorised transfer and its reporting can affect the possibility of tracing or stopping the funds.
The episode also shows why digital-payment safety cannot be treated only as an individual awareness issue. A user may be told not to share a one-time password, PIN or screen access, but a fraudulent software-update prompt can create a different form of risk: the user may believe the device is performing a normal maintenance task and may not realise that the phone’s behaviour has changed. In the reported case, the phone’s failure to switch off normally and its later automatic restart were warning signs, but they were not necessarily easy for a user to interpret in real time.
The transaction details provide a narrow but significant picture of the exposure. The disputed payment was made through UPI, an account was debited by ₹85,000, and the transfer was directed to a PhonePe identity recorded as “AKASH BATHAM”. The amount was large enough to prevent a subsequent ₹5,000 business payment, turning a cyber incident into an immediate operational problem for the victim’s shop. The report does not provide information about the victim’s usual account balance, transaction limits, device model, update source or authentication method, so no broader conclusion about the prevalence or technical pattern of similar incidents can be drawn from this case alone.
What the case does establish is the importance of a rapid reporting chain. The victim used 1930 after checking the account and then approached the police. That response created an official record and placed the matter within the cyber-fraud reporting system. For investigators, the relevant evidence may include the bank’s transaction logs, the UPI transfer trail, the receiving account details, device activity around the update notification and any available application or network records. The supplied report does not say which of these records have been collected or what the investigation has found.
The city-level significance lies in the increasing dependence of ordinary urban livelihoods on connected devices and instant payment systems. Topandas runs a local printing business, and the disputed transaction affected a payment made for business purposes rather than a purely personal expense. Small shops often rely on one phone for banking, customer communication, payment applications and business coordination. When that device becomes unavailable or unreliable, the disruption can extend beyond a single fraudulent debit.
The case also exposes a gap between the speed of digital transactions and the slower process of establishing what happened. The transfer was recorded at 6:15 pm, shortly after the reported phone disruption, but the victim identified it only when he attempted another payment the next day. The account illustrates why transaction alerts, immediate account checks and fast access to formal reporting channels matter, although the report does not say whether an alert was received or whether one was enabled.
For authorities, the next stage is to determine whether the reported software-update notification was genuine, deceptive or unrelated to the payment, and how the UPI transaction was authorised. Those questions cannot be answered from the available report. The confirmed facts are that the phone displayed an update notification, behaved abnormally, ₹85,000 was debited through UPI without the victim’s stated authorisation, and a complaint was made to the cyber helpline and Airport police station. The investigation’s findings, including whether the money can be recovered and whether the recipient can be identified, will determine what this Ahmedabad cyber fraud case ultimately reveals about the methods used and the effectiveness of the response system.
