UAE banks have been moving authentication off SMS and email one-time codes since 25 July 2025, as reported. One dated rule is mapped here, with its status and public source, to the controls it calls for and the DeepID modules that support them. DeepID supports compliance and never guarantees it.
Named for orientation. Which routes are live with which operator is confirmed with you before a pilot.
Phone numbers, payees and amounts are the illustrative values this site uses for the UAE.
Each rule with its date, its status, what it asks of a bank and the controls it calls for. A proposal is listed for what it would touch, and never marks the map.
Banks move authentication for transactions and enrolment off SMS and email one-time codes and into their own apps, from 25 July 2025, with a full phase-out reported for March 2026.
Calls for: Beyond SMS OTP.
Source: Gulf News (New rule: UAE banks to stop sending OTPs via SMS and email from July 25, opens in a new tab), 2025, press report
Each control the rule map tracks, whether a rule in the UAE calls for it, and the DeepID modules that support it.
| Control | In the UAE | DeepID modules and how they support it |
|---|---|---|
| Bind the customer to the phone | Not mapped yet | SIM and device binding, Device intelligenceSIM and device binding at onboarding and re-binding on change, with the number confirmed by the network and device integrity read every session. |
| Move beyond SMS OTP | Rule mapped | Silent network verification, Liveness and face matchOne-tap login that tries the network check and the SIM check before any one-time code, and face checks with injection defence where identity is in doubt. |
| Check risk at every key event | Not mapped yet | Device intelligence, Behavioural biometrics, Scam signals, Payee and mule graph, One decision, with reasonsDevice, behaviour, scam and payee signals read at login, new payee and payment, returned as one decision with its reasons. |
| Cool off and hold | Not mapped yet | SIM and device binding, One decision, with reasonsCool-off and hold decisions after a new device, SIM or payee, or when a payment looks coerced, set per market and journey. |
| Find and stop mule accounts | Not mapped yet | Payee and mule graphA payee and mule graph across accounts and devices, with recipient risk scored before the payment is sent. |
| The bank pays when controls fail | Not mapped yet | One decision, with reasonsDecision logs with their reasons and the message shown to the customer, and versioned policies, as evidence of what the bank did. |
Not mapped yet means no rule is mapped to that control here, not that no rule exists. DeepID supports compliance and never guarantees it, and it claims no regulator approval.
No loss-sharing rule is mapped for the UAE yet. The complaint and the case review still land with the bank.
The attacks whose pages name a rule or advisory in the UAE, each told step by step.
By industry: Banks, Digital banks, Lenders, Payments, Insurance, Capital markets.
We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.