// Adds dimensions UUID, Author and Topic into GA4
Monday, December 15, 2025
25.2 C
Singapore

ICYMI: Netizen: ‘Might as well keep money in milo tin right?’ since analysts say “Customers shouldn’t expect banks to reimburse money lost in scams”

Singapore — Industry analysts have said that customers shouldn’t expect reimbursements from banks when they lose money due to scams, which is a view not many netizens share.

OCBC’s announcement that it would fully reimburse customers who lost their money due to a phishing scam was undoubtedly a welcomed one, but analysts say this move should not be seen as a precedent.

There are ramifications to this type of reimbursements, some analysts were quoted in a Jan 21 article in TODAY. It carries the risk of customers becoming complacent against such scams.

Moreover, it could also draw more cybercriminals to target banks in Singapore with their fraudulent schemes.

Analysts quoted in TODAY suggests that official guidelines be drawn for situations that qualify individuals to receive reimbursements when they’ve been scammed.

Having a reimbursement guarantee “might encourage cybercriminals to target Singapore banks’ customers more, since consumers are not so concerned about clicking on fraud SMS messages or emails, et cetera, knowing that they will get their money back regardless.

See also  About 10,000 HDB units set for former Keppel Club golf course site, with first BTO launch in October

This could lead to more careless behaviour from consumers with respect to a phishing email or SMS messages they receive,” Mr Lim Yihao, head of intelligence for Asia Pacific at cybersecurity firm Mandiant, is quoted in TODAY as saying.

The article also quotes Ms Emily Lai, the business risk partner at Grant Thornton Singapore, as saying, “When scams occur due to one’s ignorance, fraudulent or negligent actions, like sharing bank tokens, ATM cards, PIN and passwords knowingly to another person, then the onus should not be on the banks to reimburse the affected victims for the lost money.”

Last month, almost 470 OCBC customers were victims of a recent phishing scam that began with an SMS claiming to have been sent by the bank.

Loses from the scam have totalled at least $8.5 million, with some people having seen their entire life savings lost to the scam.

Commenting on the article in Today, some netizens disagreed with the analysts.

See also  Senior Parliamentary Secretary Amrin Amin exposes attempt to scam him on Facebook

Several wrote that the phishing scam may point to possible lapses in the bank’s security systems.

Screen Shot 2022 01 21 at 5.04.19 PM

Screen Shot 2022 01 21 at 4.55.15 PM

Screen Shot 2022 01 21 at 4.55.38 PM

Another said that if banks choose not to reimburse clients who lose money in a scam, this could result in a loss of trust.

Screen Shot 2022 01 21 at 4.47.39 PM

Some commenters believe that banks should have better protection to prevent scammers’ schemes.

Screen Shot 2022 01 21 at 4.48.45 PM

One netizen wrote that if analysts themselves get scammed, they may just end up with a different opinion.

Screen Shot 2022 01 21 at 4.50.13 PM

Another even posted a question in the comment section for Grant Thornton Singapore’s Ms Lai.

Screen Shot 2022 01 21 at 4.51.46 PM

One commenter wrote that if money is not safe in their banks, “then might as well i keep the money in the milo tin right?”

Screen Shot 2022 01 21 at 4.54.46 PM

/TISG

Read also: Public concerned how elderly can tell difference between genuine SMS and messages from scammers

Public concerned how elderly can tell difference between genuine SMS and messages from scammers

- Advertisement -

Hot this week

Popular Categories

document.addEventListener("DOMContentLoaded", () => { const trigger = document.getElementById("ads-trigger"); if ('IntersectionObserver' in window && trigger) { const observer = new IntersectionObserver((entries, observer) => { entries.forEach(entry => { if (entry.isIntersecting) { lazyLoader(); // You should define lazyLoader() elsewhere or inline here observer.unobserve(entry.target); // Run once } }); }, { rootMargin: '800px', threshold: 0.1 }); observer.observe(trigger); } else { // Fallback setTimeout(lazyLoader, 3000); } });
// //