Skip to main content

4.1 Counter-Fraud Solutions and Controls for Elevated Risk

No: 106897184 Date(g): 14/4/2025 | Date(h): 16/10/1446 Status: In-Force
Control IDControl requirement description

4.1.1

Member Organizations should implement real-time fraud detection and prevention solutions to identify anomalies in transactional and non-transactional data, and monitor systems and internal accounts for transactions or behaviours that may be indicative of fraud.
 

4.1.2

Fraud detection systems should operate 24/7 with appropriate resources in place to manage outputs on a timely basis.
 

4.1.3

Member Organizations should ensure that the solutions and rules are designed or can be customised to align to the products, services, and fraud risks of the organization.
 

4.1.4

Member Organizations should implement controls that allow real-time actions such as freezing of accounts and blocking of transactions in a timely manner if a customer or Member Organization suspects an account has been compromised.
 

4.1.5

Member Organizations should use data and intelligence to screen and block transactions or access from identified high risk accounts; GPS locations; IP addresses; email addresses; devices that are subject to jailbreaking or rooting; use of VPN services when accessing online or mobile services; and compromised devices or those that have previously been used for fraud.
 

4.1.6

Member Organizations should implement device registration controls which allow users to register trusted devices for access management.
 

4.1.7

Member Organizations should implement controls to protect customers from payments and product application fraud, including but not limited to:

a.Notification to the customer of new payees added (e.g., SMS, Mobile App notification).
b. Notification to the customer when: a. User submitted the product application request. b. When the product request is approved or denied.
c.Setting a default limit subject to periodic review for single and daily transactions. 

4.1.8

Member Organizations should conduct multi-factor authentication checks to verify:

a.Payments to newly added payees or beneficiaries
b.Unusual transactions (e.g., transactions after a period of account dormancy, changes to customer behaviours, payments to a high-risk foreign jurisdiction).
c.Unusual patterns of transactions (e.g., multiple payments to one or more beneficiaries in a short period, rapid inflow and outflow of funds).
d.Transactions exceeding a defined value threshold.
e.Requests to increase the single or daily transaction limit.
f.Initial transactions after registration for online or mobile services, or registration of a new device.

4.1.9

Multi-factor authentication conducted by Member Organizations for identification and transaction verification should not solely consist of One Time Passwords (OTPs) sent via SMS. Member Organizations should implement additional factors, e.g.,

a.Approval of transactions through Mobile App by a push notification on a trusted device;
b.Device characteristics; Precise Geolocation; Behavioural profile; or Biometric behaviours;
c.Call-backs.

4.1.10

Where a Member Organization sends an OTP via SMS, the purpose, amount and merchant name should be clearly defined and in line with SAMA approved notification templates. OTPs sent via SMS should be in the language selected by the customer on the account (e.g., Arabic, English).
 

4.1.11

Member Organizations should implement controls to detect mule accounts (e.g., accounts set-up to receive fraudulently obtained funds and launder the proceeds of crime) and take action to prevent the outward flow and recovery of funds. 
 

4.1.12

Member Organizations should update controls, rules and decision-making models in solutions to mitigate fraud risks resulting from new and emerging fraud typologies identified through intelligence monitoring or root cause analysis and take proactive action to prevent fraud. 
 

4.1.13

Where a customer relationship is initiated on a remote basis (e.g., online), Member Organizations should assess the risk of impersonation and the set-up of mule accounts, implementing appropriate controls to mitigate the risk, including but not limited to:
 

a.Ensuring a phone number and National ID/Iqama is linked to one customer application only. In the event an exception is identified (e.g., dependent family member), additional due diligence checks should be conducted to validate the authenticity of the application and monitoring use cases should be developed.
b.Verification that the ownership of the phone number is registered to the same user through a trusted party (i.e., the name of the account applicant and national ID match).
c. Authentication of the account registration request via the National Single Sign-On portal using Biometric based authentication (e.g., facial identification from national trusted party), including a one-time-password mechanism (OTP) explaining that a new account is being registered as a form of verification. The OTP must be sent to the verified phone number as per step (4.1.13-b).
d.Requiring the use of a registered National Address.
e.Notification of the completion of account registration should be sent to verified phone number that is registered for the account as well as to the phone number that is registered in the national single sign-on portal.
f.Following initial set up, account fraud risk scoring should be established with restrictions placed on the account where applicable (e.g., reduced transaction value limit) until such time as the Member Organization validates that the customer is genuine through a combination of activities (e.g., use of biometric authentication mechanism through facial identification from national trusted party periodically, physical presence in a branch, regular pattern of account activity over a period of time).
g.Member Organization should have process implemented to assure the recipient IBAN belongs to the loan requester.
h.Implementing a process to ensure the ability to identify the source of inbound customer transactions.
i.Implementing a process to allow accepting/rejecting inbound customer transactions that are not originating from the same customer for e-wallet card top-up and crowdfunding participation.