For years, the SMS OTP has been an almost invisible part of banking in Singapore. Log in, wait for the code, enter the numbers and continue.
That familiar experience is now changing.
Major retail banks in Singapore have been progressively moving away from SMS OTPs for bank account logins for customers who use digital tokens, following measures announced by MAS and ABS in 2024.
Instead of asking customers to receive and manually enter a code, banks are increasingly using digital tokens and other authentication methods that can provide stronger protection against phishing and other account takeover risks.
This reflects a broader shift in how banks approach login security: from codes that customers manually enter towards authentication methods tied more closely to a trusted device, banking app or biometric factor.
For banks and fintechs, the question is no longer simply how to deliver an SMS OTP reliably. It is how to choose authentication methods that strengthen security without adding unnecessary friction to the customer experience.
Why is Singapore Banking Moving Away From SMS OTP?

SMS OTP has long been used as a second authentication factor in banking because it is familiar, widely supported and relatively easy for customers to use. MAS has also recognised SMS-delivered OTPs as one possible authentication factor within an MFA setup.
The challenge is what happens if a customer is tricked into handing over the code.
A customer may receive a genuine OTP by SMS, then enter it into a phishing website believing they are logging into their bank. Scammers can also use social engineering to persuade customers to disclose an OTP over the phone or through messaging platforms.
As phishing tactics become more sophisticated, bank login security in Singapore is shifting towards authentication methods that are harder for customers to accidentally expose.
This was one of the concerns highlighted by MAS and ABS when they announced measures to move away from OTP-based bank-account login. With digital-token authentication, customers can approve a login directly through their mobile device instead of manually entering an OTP that could be intercepted, copied or disclosed to a scammer.
That does not mean SMS OTP is inherently insecure or that SMS no longer has a role in banking. The broader shift is about matching the authentication method to the risk of the action being performed, and finding ways to make stronger security a natural part of the customer experience.
What Did MAS and ABS Announce About SMS OTP Guidelines in 2024?
On 9 July 2024, MAS and ABS announced that major retail banks in Singapore would progressively phase out SMS OTPs for bank-account login for customers who had activated digital tokens. The transition was expected to take place within three months of the announcement.
For these customers, logging in through a browser or mobile banking app would instead require authentication through their digital token, removing the need to manually enter an SMS OTP.
Importantly, the announcement was not a blanket ban on SMS OTPs across all banking activities. The measure specifically targeted bank-account login for customers using digital tokens, where digital-token authentication could offer stronger protection against phishing.
The change was also part of a wider set of anti-scam measures introduced by MAS and ABS. In September 2024, they announced that major retail banks would progressively introduce Singpass Face Verification for higher-risk digital-token setup scenarios. The additional verification was intended to make it harder for scammers to use phished credentials to activate a digital token on their own device.
Together, these measures point to a broader shift in Singapore bank login security: authentication is moving beyond codes that customers can be tricked into sharing, towards methods that provide stronger links between the customer, their trusted device and the authentication process.
For banks and fintechs, the takeaway is not simply to replace SMS OTP with the latest technology. It is to consider how each authentication method performs against the risks of the specific action, while keeping the experience straightforward for customers.
What Does This Mean for Singapore Banks?
The direction is clear: bank authentication is becoming more device-bound, risk-based and layered.
Instead of relying on customers to receive a code and manually enter it, banks can use authentication factors that are more closely tied to a trusted device, app or verified identity.
Depending on the customer journey and level of risk, these may include:
- Digital tokens
- Device-bound authentication
- Biometrics
- Face verification
- Passwordless authentication
- Step-up authentication for higher-risk actions
- Transaction signing
There is no single authentication method that fits every banking scenario. The right combination depends on the bank’s risk model, customer journey and regulatory obligations.
This is also where passwordless authentication in Singapore fits into the broader shift. By reducing reliance on passwords and manually entered OTPs, passwordless approaches can give customers a simpler way to prove their identity while enabling banks to use stronger, device- or identity-based authentication behind the scenes.
The goal is not simply to remove the OTP. It is to make authentication harder for scammers to compromise without making it harder for customers to use their bank.
Is SMS OTP Being Phased Out Completely in Singapore Banking?
The 2024 MAS and ABS announcement specifically addressed OTP-based bank-account login for customers who use digital tokens. It did not mean that SMS OTPs would immediately disappear from every banking or financial-services use case.
SMS OTPs can still be relevant in certain verification and authentication journeys, particularly where customers need a broadly accessible authentication method or have not activated another option.
At the same time, Singapore’s major card-issuing banks have been implementing additional measures such as in-app controls and digital-token authentication to strengthen protection against scams.
A more useful way to think about the change is that SMS OTP is moving away from being the default authentication mechanism towards being one component within a broader, risk-based authentication strategy.
The wider shift also comes as Singapore continues to strengthen its anti-scam measures. According to the Mid-Year Scam and Cybercrime Brief 2025, scam cases and losses fell by 26% and 13%, respectively, in the first half of 2025. While this cannot be attributed to the move away from SMS OTP alone, the figures reflect the broader effort to strengthen safeguards around digital banking and reduce customers’ exposure to scams.
What Authentication Methods are Replacing SMS OTP in Singapore Banking?
There is no single replacement for SMS OTP across every banking journey. Instead, banks can combine several authentication factors depending on the level of risk.
| Authentication method | How it works | Potential role in banking |
| SMS OTP | Sends a one-time code to a registered mobile number | Verification, fallback authentication and selected transactions |
| Digital token | Authenticates through a trusted mobile device or banking app | Bank-account login and transaction authentication |
| Biometrics | Uses characteristics such as a fingerprint or face to verify the user | Convenient device or app authentication |
| Face verification | Compares a customer’s face against an identity record | Higher-risk identity verification and digital-token setup |
| Silent Mobile Authentication | Uses mobile-network information to verify a user’s mobile identity without requiring manual OTP entry | Frictionless mobile-number verification and authentication |
| Transaction signing | Customer explicitly authenticates a specific transaction | Higher-risk transactions and payment authorisation |
The important distinction is that these methods are not interchangeable. A bank choosing an authentication method needs to consider the authentication factor, the risk of compromise, the customer journey and the specific action being authorised.
For financial institutions looking to reduce reliance on manually entered OTPs, Silent Mobile Authentication offers another approach to verifying mobile users. 8×8 CPaaS Silent Mobile Authentication can verify a user’s mobile number without requiring them to manually enter an OTP, helping reduce friction while adding another layer to the authentication journey.
How Does Silent Mobile Authentication Work?

Silent Mobile Authentication verifies a user’s mobile number through the mobile network without requiring them to manually enter an OTP.
In a typical journey, a customer starts a login, registration or verification process on their mobile device. Instead of receiving a code and typing it into a form, the authentication flow can use network-based verification to confirm that the mobile number is associated with the device being used.
This can remove a familiar point of friction:
Enter mobile number → wait for SMS → retrieve OTP → enter OTP → continue
With silent authentication, eligible users can move through the verification process with fewer manual steps, without having to retrieve and enter a one-time code.
For banks and fintechs, this can be useful for mobile onboarding, account access and step-up authentication, particularly in journeys where verifying possession of the customer’s mobile number is an important part of the authentication process.
Silent Mobile Authentication should not, however, be treated as a universal replacement for every authentication factor. Financial institutions still need to assess how it fits into their broader authentication architecture, risk model and applicable security requirements.
Is Silent Mobile Authentication more secure than SMS OTP?
Not necessarily in every situation. Silent Mobile Authentication and SMS OTP use different approaches to authentication, so their security should be assessed based on the specific implementation, risk level and authentication factors involved.
With SMS OTP, the point of weakness lies in a scammer’s ability to potentially trick the customer into entering or disclosing the code through a phishing site, phone call or messaging platform.
Silent Mobile Authentication can remove that manual code-entry step. By verifying the mobile number through the mobile network, it can reduce exposure to phishing attacks that rely on persuading customers to reveal an OTP.
That does not make Silent Mobile Authentication a complete security solution on its own. Singapore banks should assess it as part of a broader, layered authentication architecture, taking into account the risk of the action, the factors being used and the applicable security requirements.
This is consistent with the broader principle behind multi-factor authentication (MFA). MAS guidance has emphasised the use of two or more unique and independent authentication factors where MFA is required, with examples including OTPs, biometrics, device identity and digital certificates.
The key takeaway is therefore not that one technology is universally “more secure” than another. It is about choosing authentication factors that address the relevant risks while making the customer journey as secure and seamless as possible.
How Should Singapore Banks Approach Authentication After the SMS OTP Shift?
The shift away from SMS OTP for bank-account login does not mean banks need to replace it with a single new technology. A stronger approach is to match authentication to the risk, customer journey and action being protected.
A bank could use different authentication layers for different scenarios:
Low-friction account access
For routine login, a trusted digital token or device-bound authentication can reduce reliance on manually entered OTPs while keeping the customer journey straightforward.
New-device registration
Activating a digital token on a new device presents a different level of risk and may require stronger identity verification.
Singapore’s introduction of Singpass Face Verification for higher-risk digital-token setup is an example of this layered approach. The additional verification helps strengthen protection against scammers attempting to activate a digital token using phished credentials.
High-risk transactions
Actions such as large-value transactions, adding new payees or unusual account activity may warrant additional verification. Step-up authentication or transaction-specific approval can add another layer when the risk is higher.
Mobile onboarding
For registration or account setup on a mobile device, Silent Mobile Authentication can provide a lower-friction way to verify a customer’s mobile number without requiring them to manually enter an OTP, subject to the bank’s authentication architecture and risk requirements.
Fallback scenarios
SMS OTP can still play a role in cases where customers cannot access their primary authentication method or where a particular workflow requires an alternative verification channel.
The result is a more risk-based authentication strategy: stronger controls where the risk is higher, and fewer unnecessary steps where it is not.
When evaluating an authentication solution, banks should therefore consider more than the technology itself. How does it fit into the wider authentication architecture? What risks does it address? And how does it align with applicable MAS requirements and cybersecurity controls?
What Should Banks Consider When Choosing an Authentication Solution?
Moving beyond SMS OTP in Singapore banking is not simply a technology replacement exercise. Banks should evaluate how an authentication solution fits into their existing identity, security and customer-experience architecture.
Key considerations include:
- Security: Does the method reduce exposure to phishing, credential theft and social engineering?
- Authentication factors: Can it work alongside other independent factors where MFA is required?
- Customer experience: How many steps does the customer need to complete, and how much manual input is involved?
- Device coverage: Does it work reliably across the devices and mobile networks used by the bank’s customers?
- Integration: Can it connect with existing CIAM, identity, fraud and banking systems?
- Risk-based authentication: Can stronger authentication methods be triggered when a login, transaction or other action presents higher risk?
- Fallback: What happens if the customer’s primary authentication method is unavailable?
- Monitoring: Can the bank monitor authentication attempts, failures and suspicious activity?
The goal is not to eliminate SMS overnight, but to build an authentication architecture in which the most appropriate method is used for each customer and risk scenario.
A layered approach can combine different authentication methods based on the risk and customer journey. 8×8 CPaaS and Descope CIAM, for example, can support mobile authentication, passwordless login and risk-based multi-factor authentication as part of a broader customer identity strategy.
How Can 8×8 CPaaS Support Stronger Authentication for Financial Services in Singapore?
For banks, insurers and fintechs, authentication needs to balance security with a customer experience that feels fast and intuitive. 8×8 CPaaS brings together mobile authentication and identity capabilities that can help financial institutions reduce reliance on manual verification while building more flexible authentication journeys.
-
Silent Mobile Authentication
8×8 CPaaS Silent Mobile Authentication verifies a customer’s mobile number through the mobile network without requiring them to manually enter an SMS OTP.
For journeys where every additional step can create friction, silent authentication can make mobile verification faster and less visible to the customer, without requiring them to retrieve and enter a one-time code.
-
Descope CIAM

A visual flow from Sign In to Magic Link Sent to Successful Authentication, built without writing identity infrastructure from scratch – with Descope. Descope CIAM is a no-code customer authentication and identity management platform that helps financial institutions secure customer-facing applications and journeys.
With Descope CIAM, banks, insurers and fintechs can:
- Secure customer authentication: Manage login, access control and identity across customer-facing applications.
- Simplify onboarding: Create smoother registration and account setup journeys while supporting identity verification.
- Enable passwordless authentication: Support methods such as magic links, social logins and OTPs to reduce reliance on passwords.
- Strengthen multi-factor authentication: Configure risk-based MFA, bot protection and step-up controls for higher-risk journeys.
- Manage authentication centrally: Integrate authentication and authorisation into existing customer journeys without building identity infrastructure from scratch.
Together, 8×8 CPaaS Silent Mobile Authentication and Descope CIAM can support a broader approach to customer authentication, combining low-friction mobile verification with configurable identity, MFA and access controls. That combination matters because it runs on the same 8×8 CPaaS infrastructure a bank may already use for SMS OTP, voice and other customer communications, with Omni Shield’s fraud monitoring covering the verification traffic underneath it. Rather than adding a separate identity vendor on top of an existing messaging stack, a bank can extend the same platform relationship to cover mobile authentication and CIAM.
Talk to our experts to find out how banks, insurers and fintechs in Singapore can create authentication journeys that are secure, adaptable, and easier for customers to navigate, while fitting into the institution’s wider security and compliance framework.
Frequently Asked Questions
- Is SMS OTP being phased out for Singapore banks? SMS OTP has been phased out for bank-account login for customers using digital tokens at major retail banks, following the MAS and ABS announcement in July 2024. This does not mean SMS OTP has been eliminated from every banking or financial-service use case.
- What is replacing SMS OTP for bank login? For customers with digital tokens, the digital token on their mobile device is used to authenticate bank-account login instead of requiring a customer to enter an SMS OTP. Other authentication technologies, including biometrics and face verification, can provide additional layers for particular journeys and risk scenarios.
- Is Silent Mobile Authentication the same as a digital token? No. Silent Mobile Authentication and digital tokens use different approaches. Silent Mobile Authentication verifies a user’s mobile identity through the mobile network without requiring manual OTP entry, while a digital token is an authentication mechanism associated with a customer’s trusted device and banking application.
- Can banks still use SMS OTP? Yes. The MAS and ABS measure did not ban SMS OTP across all banking use cases. SMS OTP can still be used for selected verification or authentication journeys, including some card-related processes, although banks are introducing additional controls for higher-risk scenarios.
