logo

DBS adds mobeil wallet security feature

Finextra12-05-2025
In an effort to combat the rise of mobile wallet phishing, DBS Bank will launch a new 'Mobile wallets' feature within DBS/POSB digibank app's Payment Controls, preventing scammers from adding phished card details to their mobile wallets.
0
This content is provided by an external author without editing by Finextra. It expresses the views and opinions of the author.
Payment Controls – located within the DBS/POSB digibank app – allows customers to self-manage their card transaction limits in real-time. Customers can use these controls to protect themselves from unauthorised transactions when their card is misplaced, stolen or misused. This includes disabling e-commerce or cash advance transactions, locking the card, among others.
From mid-May 2025, customers will not be able to add DBS/POSB cards to their mobile wallets until they turn on the new 'Mobile wallets' toggle in Payment Controls. The 'Mobile wallets' feature is turned off by default and customers will need to first turn on the 'Mobile wallets' toggle before adding their cards. Using the 'Mobile wallets' in-app control introduces a deliberate pause in the transaction process, allowing users to verify their intention to add their card to a mobile wallet.
The new 'Mobile wallets' feature is the latest addition to the bank's suite of self-managed security control features in the DBS/POSB digibank app. DBS was the first bank in Singapore to introduce the most comprehensive set of payment controls and has continued to maintain that leading position since 2021. To date, over 1.5 million users have adopted DBS' self-managed security tools that also include DBS' money lock feature (digiVault) and security checkup.
Calvin Ong, DBS Head of Consumer Banking Singapore said, 'Along with the Singapore Police Force (SPF), the Cyber Security Agency of Singapore (CSA) and the Monetary Authority of Singapore (MAS), DBS has also observed a rise in mobile wallet phishing incidents, where scammers target customers' cards to add to their mobile wallet for subsequent unauthorised transactions. As part of the industry's initiative to address this issue, DBS has introduced a new 'Mobile wallets' feature to verify our customers' intention to add their card to a mobile wallet. By introducing the deliberate pause, we enable customers to be alert when performing transactions.'
Customers should add only their own cards to their mobile wallets. If they are unfamiliar with mobile wallets, they should consult their family or call the ScamShield Helpline (1799) for assistance.
'Joint vigilance with our customers is essential to combating scams and we will continue to expand our suite of self-managed security features, as well as anti-scam educational resources and community events, to empower our customers to take control of their security,' added Ong.
SPF, CSA and MAS have been working with banks, mobile wallet providers, and card service providers to combat this trend. According to the Singapore Police Force, there were over 650 reports of phished card credentials being added to mobile wallets in the last three months of 2024, resulting in at least SGD 1.2 million in losses from transactions made on scammers' mobile wallets.
How DBS/POSB's Mobile wallets security feature works
The 'Mobile wallets' feature in Payment Controls is turned off by default to ensure customers' cards cannot be added to mobile wallets. Customers who wish to add their DBS/POSB card must first turn on the 'Mobile wallets' toggle in Payment Controls within the DBS/POSB digibank app. To further protect users, this 'Mobile wallets' feature will be automatically turned off if the card is not added to any mobile wallet within 10 minutes.
DBS enhances the anti-scam security features of its digibank app
Greater convenience for DBS digiVault: Since October last year, customers can instantly lock funds and prevent digital transfers from their accounts via the DBS/POSB digibank app, or digibot on the DBS/POSB website. The funds can then be unlocked at over 1,200 ATMs island-wide in addition to the bank's branches. Customers will continue to earn the same interest on their locked savings and fixed deposits.
More capabilities for DBS anti-malware tool for Android devices: The digibank app's anti-malware tool for Android devices will alert users when the app is being remotely controlled by another device or when the Android device's USB/wireless debugging setting is enabled. When the USB/wireless debugging setting in the Developer Options is turned on, scammers can remotely control a user's Android device without their knowledge, steal sensitive information such as passwords and access the user's digibank app. Users will also be cautioned by the anti-malware tool when screen-sharing or mirroring is enabled on their Android device.
Creating a robust anti-scam ecosystem with partners and customers
DBS works closely with key partners including the SPF, Infocomm Media Development Authority (IMDA) and the CSA to co-create educational anti-scam content (e.g an anti-scam quiz) and extend its reach to a wider audience through digital literacy roadshows and street performances ('getais') in the heartlands. In 2024, DBS conducted over 300 anti-scam and digital literacy workshops, reaching 90,000 Singaporeans and residents. The bank also launched its new Bank Safely Hub last year to help the public stay informed about scams by featuring essential scam alerts, educational materials and resources.
Since January 2025, DBS has held POSB neighbourhood getai events and POSB SG60 neighbourhood carnivals in Bedok, Eunos, Tiong Bahru and Punggol, where residents were trained to use DBS security tools including Payment Controls, digiVault and security checkup. DBS has plans to continue to roll out these activities this year.
DBS has a multi-layered defence against scams which combines real-time fraud surveillance, advanced security infrastructure and customer education. Furthermore, DBS continues to deploy dedicated personnel who are embedded within the SPF's Anti-Scam Centre, performing real-time transaction monitoring and immediate intervention against suspicious activities.
Orange background

Try Our AI Features

Explore what Daily8 AI can do for you:

Comments

No comments yet...

Related Articles

Rethinking AI in enterprise, blockchain development
Rethinking AI in enterprise, blockchain development

Coin Geek

time27 minutes ago

  • Coin Geek

Rethinking AI in enterprise, blockchain development

Getting your Trinity Audio player ready... A recent Model Evaluation & Threat Research (METR) study found artificial intelligence (AI) coding assistants slowed experienced developers by 19% on familiar codebases, underscoring the cognitive friction of tool-context shifts. Conscious Stack Design™ (CSD) calls for intentional, context-aware integration of AI, reserving assistants for scaffold tasks while preserving flow on legacy work. In blockchain domains like BSV, the precision demands and security stakes amplify this effect, suggesting teams calibrate AI for documentation and test scaffolding rather than core consensus logic. What drives the slowdown among veteran developers? Experienced software engineers build rich mental models of their projects over time. These internal frameworks let them navigate complex code with minimal cognitive overhead. Introducing an AI assistant such as Cursor interrupts that fluency in two main ways: Context switching and evaluation overhead. Every AI suggestion must be read, interpreted, and validated against the developer's intent. Even when suggestions are directionally correct, developers spend precious seconds confirming variable names, API contracts, and edge cases. Over dozens of small interactions, these validation steps accumulate, eroding any raw time saved by auto-completion. Perception versus reality disconnect. In the METR trial, participants believed they worked 24% faster with AI—but objective measures showed a 19% slowdown. This gap arises because AI makes code authoring feel easier—akin to editing a draft rather than writing from scratch—even though each edit requires scrutiny. Seasoned developers' self-assessment skews toward perceived ease, masking the hidden review costs. By contrast, less experienced coders often lack deep familiarity and lean on AI for boilerplate or syntax. Their cognitive load falls more steeply, so they register net gains even if they invest similar time in validation. How does Conscious Stack Design inform AI adoption? Conscious Stack Design™ emphasizes harmony between tools, workflows, and human cognition. It recognizes that adding a new layer—no matter how powerful—can fragment a mature stack if not introduced with intention. Three CSD tenets guide AI integration: Align tools with task context: Not all tasks benefit equally from AI. Use assistants for greenfield development—scaffolding new modules, generating test harnesses, or spinning up documentation templates. For maintenance on established code, default to native IDE features and keyboard-driven workflows. Not all tasks benefit equally from AI. Use assistants for greenfield development—scaffolding new modules, generating test harnesses, or spinning up documentation templates. For maintenance on established code, default to native IDE features and keyboard-driven workflows. Establish clear 'AI boundaries': Define rules such as 'AI for initial drafts only' or 'Disable AI in production branches.' Embedding these policies into version-control hooks or team guidelines prevents ad hoc toggling that disrupts flow. Define rules such as 'AI for initial drafts only' or 'Disable AI in production branches.' Embedding these policies into version-control hooks or team guidelines prevents ad hoc toggling that disrupts flow. Monitor and iterate on AI resonance: Track lead metrics like code-review time, bug-fix rates, and developer satisfaction. If AI assistance correlates with longer reviews or higher defect density in certain contexts, adjust usage rules. This iterative feedback loop preserves resonance—maximizing benefit while minimizing noise. In practice, a CSD-aligned team might enable AI suggestions only when creating unit tests or prototyping a novel service, then turn it off when working on critical legacy functions. This selective approach prevents cognitive tax while still capturing AI's generative power. What does this mean for blockchain developers on BSV? Blockchain engineering combines high-stakes correctness, domain-specific protocols, and often tight coupling between smart contracts and consensus rules. For BSV developers, the METR findings carry particular weight: Security and auditability demands. Smart-contract errors can lead to on-chain losses or protocol vulnerabilities. AI-generated code must undergo rigorous formal verification and peer review. Each AI suggestion introduces an audit checkpoint, compounding time spent on validation and diminishing the allure of instant snippets. Protocol evolution and unfamiliarity. When BSV protocols evolve, even veteran blockchain engineers face new interfaces. In these scenarios—akin to 'greenfield' work—AI can excel at generating boilerplate for transaction parsing or RPC wrappers. Here, novices and experts alike may gain from AI scaffolding, aligning with CSD's recommendation to use AI in unfamiliar territories. Test and documentation acceleration. Rather than embedding AI in core contract code, blockchain teams can leverage assistants to auto-generate comprehensive test suites, API documentation, or example integrations. These peripheral artifacts accelerate onboarding and reduce manual drudgery, while keeping the critical path free from AI-induced friction. Ecosystem collaboration. In BSV's open-source environment, community contributions often come from varied experience levels. AI-driven style guides or linting suggestions can help standardize code quality across contributors. However, project maintainers should gate AI-assisted pull requests behind stricter review rules to safeguard protocol integrity. By mapping AI use cases to the stages of blockchain development—innovation, deployment, maintenance—teams can apply CSD principles to optimize where AI amplifies productivity and where it introduces undue overhead. Toward a balanced AI-augmented developer stack As AI tools mature, their integration into enterprise workflows demands more than flip-of-a-switch adoption. The METR study serves as a cautionary tale: even promising technologies can backfire when they collide with entrenched expertise. Conscious Stack Design™ offers a roadmap: Audit current workflows Document where context-switching costs are highest. Are developers spending excessive time reviewing pull requests? Which tasks feel most tedious? Pilot targeted AI interventions Roll out AI in narrow, well-defined contexts—new component creation, test writing, API client generation. Measure impact on cycle time and code quality. Codify AI usage policies Establish team standards: when to enable AI, how to label AI-generated code, and what review thresholds apply. Embed checks into CI/CD pipelines. Iterate with feedback loops Use metrics (e.g., mean time to repair, review durations) and qualitative surveys to refine AI boundaries. Continuously adjust to preserve developer flow. Educate and enable all skill levels Offer training on effective prompt crafting and AI-tool configurations. Equip junior engineers to leverage AI safely, while showing seniors how to integrate suggestions without undue scrutiny. In conclusion, AI coding assistants hold transformative potential—but only when woven into a stack with conscious intent. For enterprise teams and blockchain specialists alike, the road to AI-augmented productivity lies in respecting human cognition, aligning tool use with task context, and iterating based on real-world feedback. Explore Conscious Stack Design™ frameworks and pilot targeted AI interventions in your next sprint. You might discover that the smartest way to speed up development is knowing when to hit 'disable.' In order for artificial intelligence (AI) to work right within the law and thrive in the face of growing challenges, it needs to integrate an enterprise blockchain system that ensures data input quality and ownership—allowing it to keep data safe while also guaranteeing the immutability of data. Check out CoinGeek's coverage on this emerging tech to learn more why Enterprise blockchain will be the backbone of AI . Watch: Demonstrating the potential of blockchain's fusion with AI title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen="">

BP-chartered tanker leaves port of sanctioned-Nayara without loading, sources say
BP-chartered tanker leaves port of sanctioned-Nayara without loading, sources say

Reuters

timean hour ago

  • Reuters

BP-chartered tanker leaves port of sanctioned-Nayara without loading, sources say

SINGAPORE/NEW DELHI, July 22 (Reuters) - A tanker chartered by energy major BP left a port run by newly sanctioned Indian refiner Nayara Energy without loading, according to five industry sources and LSEG shipping data, a sign fresh European Union curbs on Russia are beginning to bite. The vessel Talara was supposed to load 60,000 metric tons (447,000 barrels) of ultra-low sulphur diesel on July 21 at Nayara's Vadinar port in western India, with the cargo bound for Africa, LSEG data showed. Nayara, partly-owned by Russia's largest oil producer Rosneft ( opens new tab, and BP (BP.L), opens new tab did not immediately respond to requests for comment. The sources declined to be named as they were not authorised to speak to the media. The change in loading plan suggests that EU sanctions imposed on Nayara on Friday are disrupting refined products exports from the Russia-backed refiner, one of the two private fuel exporters in India. The Talara did not load the cargo after the EU imposed the sanctions, one of the sources said. The sanctions package against Russia over its war in Ukraine is aimed at dealing further blows to Russia's oil and energy industry. BP subsequently released the ship, making it available for charter within India or the Middle East region, two of the sources said. On Monday, Nayara said in a statement that it condemned the EU's "unjust and unilateral" decision to impose sanctions on the company, while India said on Friday it did not support the EU's "unilateral sanctions". Following the EU sanctions, Nayara Energy amended the terms of a naphtha tender issued on Monday to obtain payment in advance, a tender document seen by Reuters showed. Another vessel, Panamax-sized tanker Pacific Martina, chartered by Shell (SHEL.L), opens new tab, arrived at Vadinar on July 18 to load jet fuel, LSEG and Kpler data showed. After loading jet fuel from Nayara, the partially loaded Pacific Martina has been anchored off the port next to Talara, LSEG data showed on Tuesday. PetroChina has also provisionally chartered medium-ranged tanker Chang Hang Xing Yun to load 35,000 tons of gasoil on July 29-31 from Vadinar port with the option to discharge the cargo at Singapore or Chittagong, Bangladesh, shipping fixtures from shipbrokers showed. Shell and PetroChina did not immediately respond to a request for comment.

DOWNLOAD THE APP

Get Started Now: Download the App

Ready to dive into a world of global content with local flavor? Download Daily8 app today from your preferred app store and start exploring.
app-storeplay-store