
A fraud prevention policy (also called an anti-fraud policy) describes a firm’s fraud risks and the measures that protect against them. It names who is responsible for suspicious transactions and customer complaints. For electronic money institutions (EMIs) and payment institutions (PIs), the policy reflects their services, authentication controls and refund obligations under PSD2. For crypto-asset service providers (CASPs), it reflects the services authorised under MiCA, especially custody and the handling of orders. A regulator reads the policy together with the business plan, risk assessment and IT documents, and looks for inconsistencies.
This article covers what EU law requires, what we recommend adding and how to check your own policy. It is useful if you are preparing an application for an EMI or PI licence or a CASP licence, or updating an existing policy.
What is fraud prevention and why you need a policy
Fraud prevention covers the measures a firm uses to prevent, detect and respond to fraud. A fraud prevention system is software with rules, risk scores and alerts. An anti-fraud policy explains who runs the system, who investigates fraud cases and who reports to the regulator. The regulator checks how the firm organises fraud prevention: who is responsible, how staff investigate suspicious transactions and which reports the firm files.
Is a fraud prevention policy mandatory?
No. EU law does not require a document with this exact title. It does require firms to apply specific measures, procedures and reporting.
That is why firms often bring all these requirements together in one fraud prevention policy, sometimes called a fraud risk management policy. This makes it easier to check duties and the records that support them.
| Requirement | EMI and PI | CASP under MiCA |
|---|---|---|
| Licence application | Procedures for security incidents and sensitive payment data; principles for fraud statistics; a security policy with a risk assessment (PSD2, Art. 5(1)). The European Banking Authority (EBA) requires a detailed risk and fraud assessment (EBA/GL/2017/09) | Internal control and risk management; where relevant, a custody policy or, for a trading platform, a system to detect market abuse (MiCA, Art. 62(2)) |
| Transaction controls | Monitoring that detects unauthorised or fraudulent payments (RTS 2018/389, Art. 2) | Control of client assets and instructions; detection of market abuse when arranging or executing transactions (MiCA, Art. 92) |
| Reports and incidents | Fraud statistics under PSD2 and EBA guidelines; major ICT-related incidents under DORA | STORs where MiCA Art. 92 applies; major ICT-related incidents under DORA |
| Client assets | Safeguarding of client funds; refunds and liability for unauthorised payments | Segregation and protection of client assets; duties of custodians (MiCA, Arts. 70 and 75) |
| Whistleblowing | An internal channel for staff reports, whatever the headcount (Directive (EU) 2019/1937, Art. 8(4)) | The same rule |
For EMIs, the PSD2 application requirements apply through Article 3(1) of the E-Money Directive. If a firm provides several licensed services, it checks the obligations for each one separately.
Which fraud risks should the policy cover?
Separate internal fraud from attacks on customers and their transactions. Include only the scenarios that can occur in your business model.
| Risk | EMI or PI example | CASP example |
|---|---|---|
| Internal fraud | Diversion of safeguarded client funds, falsified reconciliations, unauthorised refunds | Misuse of private-key access, unauthorised transfers of client assets |
| Account takeover | Stolen credentials, session hijacking, SIM swap | Compromised exchange account, wallet or withdrawal approvals |
| Social engineering (deceiving the customer) | A payer is tricked into confirming a transfer | A customer is tricked into withdrawing assets to a scam address |
| Use of third parties | Money mules (intermediary accounts for stolen money) receive the proceeds | Accounts are used to exchange or move stolen crypto-assets |
| Market abuse | — | Spoofing, wash trading, insider dealing |
Each risk has its own rules. An unauthorised payment (a payment the customer did not confirm) differs from a transfer the customer made after being deceived. A suspicious crypto trade does not always mean money laundering. The policy sets a separate path for investigating, escalating and reporting each case.
What a fraud policy must contain: 8 sections
AMS recommends eight connected sections. EU law does not prescribe this structure, but it helps firms address the applicable requirements and common supervisory questions.
- Scope and governance. Legal entities, products and countries; management responsibility, the policy owner, decision rights and escalation.
- Fraud risk assessment. Internal and external scenarios, inherent risk, controls, residual risk and triggers for review.
- Prevention. Customer verification, payment authentication, staff access, segregation of duties, limits and protection of client assets.
- Detection and monitoring. Data sources, rules, alert thresholds, who reviews alerts and how rules are tested.
- Response and customer protection. Triage, evidence preservation, disputed payments, refund decisions, recovery attempts and complaints.
- Reporting and escalation. Which cases go to management, the payment or market regulator, the financial intelligence unit and the ICT incident channel.
- Training and records. Role-based training, the staff whistleblowing channel, audit trail, access restrictions and retention periods.
- Review and assurance. Management metrics, control testing, independent review, owners of fixes and triggers for updates.
The policy does not need to repeat every work instruction. It is enough to name the procedure, the owner and the records that show staff follow it. The regulator also compares the document with the risk management policy, AML procedures, safeguarding of client funds and ICT controls.
What does a regulator check beyond the policy?
The policy must match how the firm actually works. Before filing, check five connections.
| Document or system | Question the policy must answer |
|---|---|
| Business plan and payment flows | Which transactions can be stopped, additionally confirmed or reviewed, and at what stage? |
| IT architecture and external providers | Where does monitoring run, who receives alerts and what happens if a provider fails? |
| Risk assessment | Which scenarios matter for the firm’s customers, products and countries, and why? |
| Staff and governance | Who reviews alerts, approves exceptions, decides payment disputes and reports failures? |
| Records and management reports | Can the firm show a case history, tests, losses, recoveries and fixes? |
This cross-check reveals a common mistake: a policy that promises controls the firm cannot deliver.
Who is responsible for fraud prevention?
The management body (board of directors) is responsible for the internal control system. Day-to-day work needs a specific owner, with access to all data and the right to report problems to management at once. We recommend giving this role to a fraud prevention officer. A separate position is not required: in a small firm, the role can be combined with risk management or compliance. The key point is that this person does not check their own decisions, such as payments they approved.
The policy should give the owner:
- Full access. To all relevant data, systems and customer complaints about fraud.
- Links to other functions. Regular contact with compliance, risk management and internal audit.
- A say on resources. Management consults the owner before reducing fraud staffing or tools and explains the reasons in writing.
- Written reporting. Reports to management on a schedule, and immediate escalation of material issues.
- Capacity checks. At least once a year, management reviews the workload, headcount and skills of the fraud team.
The policy should name who updates fraud scenarios, approves changes to monitoring settings and decides on refunds. The policy should also name a deputy to cover the owner’s absence. An organisational chart alone cannot show who was responsible for a missed alert.
Supervisors find the same gap between approved rules and practice. In June 2026, the Dutch central bank (DNB) reviewed how seven banks, PIs and EMIs fight fraud. The fraud teams were active, but key risk indicators (KRIs) were “not always substantiated or adhered to in practice” (DNB review). In some cases, monitoring was constrained by the team’s capacity to investigate alerts. More alerts do not improve protection if the firm has no resources to review them.
Transaction monitoring: what is required
For EMIs and PIs, transaction monitoring is a direct legal requirement. The EU regulation on strong customer authentication (2018/389) requires firms to detect unauthorised and fraudulent payments. The monitoring system must consider at least five risk factors:
- compromised or stolen login credentials;
- the amount of each payment;
- known fraud scenarios;
- signs of malware when the customer logs in;
- unusual use of the device or app provided by the firm.
The firm documents these measures, tests them regularly and has them reviewed. The policy states which systems run the checks, what counts as an alert and how staff and automated tools respond.
We recommend scoring the risk of each payment and setting an action for each risk level in advance. Possible actions: contact the customer, hold the payment, require strong customer authentication (SCA) or refer the case to the police.
When SCA can be skipped
Strong customer authentication (SCA) requires two or more independent authentication factors, such as a password and a one-time code.
For some low-risk payments, the law allows firms not to apply SCA. This exemption is called transaction risk analysis (TRA). It can be used only if set conditions are met, including the payment amount and the permitted fraud rate.
Maximum fraud rate for the TRA exemption
| Payment amount up to | Online card payments | Online transfers |
|---|---|---|
| €500 | 0.01% | 0.005% |
| €250 | 0.06% | 0.01% |
| €100 | 0.13% | 0.015% |
The policy names the person who tracks this rate every quarter, reports any excess to the regulator and decides when to stop or resume the exemption.
Fraud monitoring and AML monitoring can use shared data and one system, but their rules and decisions differ. A fraud alert does not by itself mean that the firm must file a suspicious transaction report.
Refunds to customers: PSD2 rules
If the customer did not confirm a payment (an unauthorised payment), PSD2 sets the refund procedure and the split of liability directly. For consumers, these rules cannot be overridden by contract, so the policy must reflect them accurately.
- Contact at any time. The customer must be able to report the loss, theft or misuse of a card, app or other payment instrument around the clock.
- The firm proves, not the customer. The firm must show that the payment was authenticated and correctly recorded. Use of the payment instrument alone does not prove the customer’s consent or gross negligence.
- Refund by the end of the next business day. The firm refunds immediately, no later than the end of the business day after it learned of the payment.
- Exception: suspected fraud by the customer. The provider may delay the refund if it has reasonable grounds for suspicion and has reported them in writing to the national competent authority.
- Customer liability is limited. If a payment instrument is lost or stolen, the customer bears losses of up to €50. The customer bears all losses only if they acted fraudulently, intentionally or with gross negligence.
- No strong authentication, no loss for the customer. If the firm did not ask the customer to confirm in two ways (SCA), the customer bears no loss unless they acted fraudulently.
A real case: refund first, argue later
On 15 October 2026, the Court of Justice of the EU ruled on a fraudulent transfer (Case C-70/25). A customer was selling an item online and followed a fake link from a “buyer”. She entered her online banking credentials on a fake website, after which a fraudster transferred about €700 from her account. The bank refused a refund, citing her gross negligence.
The Court held that suspected gross negligence “does not entitle the payment service provider to refuse to refund immediately”. The provider must refund first. It may then seek to recover the funds, but only if it proves the customer’s intent or gross negligence itself.
The case involved a bank, but the rule applies to all payment service providers, including EMIs and PIs. For the policy, this means two separate processes: an immediate refund decision, and a later recovery decision based on the evidence collected.
The ruling covers only unauthorised payments. If the customer authorised the transfer after being deceived, different rules apply. So the first step in handling a complaint is to decide which type it is.
What we recommend beyond the law
In addition to the mandatory PSD2 requirements, we recommend that the policy provides for:
- A separate channel for fraud reports. Available in the app and on the website, with the option to reach the firm outside business hours.
- Fast review of reports. Start examining a disputed payment at once and record every step.
- Written reasons for refusals. If a refund is refused, explain why, show the evidence and state how to complain.
- Contact with the payee’s provider. Reach out at once to try to stop the transfer or recover the money.
- Customer information. Warn about new fraud schemes, never send links that ask for passwords and test new authentication methods before launch.
Fraud reporting and management metrics
Management should see how many fraudulent transactions occur, how much money the firm and its customers lose and how quickly staff react to suspicious payments.
For EMIs and PIs, part of this data goes into mandatory fraud reporting to the regulator. The EBA guidelines (EBA/GL/2018/05) define which statistics to collect:
- Number and value of fraudulent payments. By transaction type, compared with total payment volume.
- Fraud methods. Who initiated or changed the payment, and whether the customer was deceived. For card payments, stolen, lost and counterfeit cards, cards not received and stolen card details are counted separately.
- How payments were made. Whether strong customer authentication (SCA) or an exemption was used, whether the payment was remote and between which territories it went.
- Who bore the losses. The firm, the customer or other parties to the payment.
Separately, the firm tracks its own fraud rate. If it uses the TRA exemption, it compares this rate with the thresholds set by law (Art. 19 of Regulation 2018/389).
For internal control, we also recommend tracking:
- how long it takes to start reviewing a suspicious payment;
- how many high-risk alerts remain unreviewed;
- the proportion of flagged transactions confirmed as fraud;
- how much stolen money was recovered;
- which control weaknesses remain unresolved past their deadlines.
These indicators help management see whether the team can handle the workload and whether fraud prevention measures work.
CASPs covered by MiCA Art. 92 need separate indicators for possible market abuse: suspicious orders and transactions, review outcomes, STOR filing times and the completeness of investigation records.
What CASPs need under MiCA
Fraud prevention requirements for CASPs depend on the firm’s services. MiCA sets rules on protecting client assets, custody of crypto-assets and detecting market abuse. However, MiCA has no refund rules like those in PSD2.
Custody: access to client assets
A CASP that holds clients’ crypto-assets must have a custody policy (MiCA, Art. 75(3)). It must reduce the risk of losing assets through fraud, cyber attacks or staff errors.
The fraud prevention policy should define:
- who has access to client assets and who approves their transfer;
- how the firm reconciles balances and detects unauthorised transactions;
- what to do after an account takeover or a suspicious transfer;
- how to record incidents and preserve evidence.
These rules must match the custody policy and the DLT policy for a CASP. MiCA Art. 75 also sets requirements for segregating client assets and for liability for their loss.
Trading: detect market abuse
Not every CASP must monitor for market abuse. Under MiCA Art. 92, this applies to firms that professionally arrange or execute crypto-asset transactions.
Such firms must detect suspicious orders and transactions. Where there is reasonable suspicion of market abuse, the firm files a STOR (suspicious transaction and order report) with the regulator without delay.
EU Regulation 2025/885 sets out how to organise this control. It provides for ongoing monitoring of orders, transactions and distributed ledger data, review of alerts by staff and staff training.
The firm must keep its review records for five years, including documented reasons for deciding not to submit a STOR (Art. 3).
All CASPs: protection against internal misuse
MiCA Art. 70 requires firms to protect clients’ crypto-assets and funds. The firm may not use them for its own account.
So the policy should cover staff access control, segregation of client assets and regular reconciliations.
It is also important to separate three types of reports to authorities:
- STOR — on suspected market abuse.
- AML report — on a suspicious transaction linked to money laundering.
- DORA notification — on a major ICT incident.
For each case, the policy sets out the procedure and the person responsible.
Need a fraud prevention policy for your licence?
AMS develops fraud prevention policies for EMIs, PIs and CASPs, as part of a licence project or as a separate service. Send us your business model, list of services and any documents you have. The first introductory call is free. We work in English, Russian and Ukrainian.
What will PSR and PSD3 change?
The new PSR and PSD3 rules will strengthen protection against payment fraud. They provide for sharing data on fraudulent transactions, additional measures to prevent deception and refunds in some cases where fraudsters pose as staff of a bank or payment provider.
As at 22 October 2026, PSR and PSD3 have not yet been adopted. The agreed draft is going through the legislative procedure. Until the new rules apply, PSD2 remains in force.
Verification of the payee is already required by current law. EU Regulation 2024/886 requires checking the payee’s name against their account number (IBAN) before a transfer. The deadlines for mandatory implementation depend on where the provider is located.
The policy should reflect the requirements already in force and, once PSR and PSD3 are adopted, update its procedures to the new rules.
Check your policy
Download our checklist and compare your policy with it. It lists the sections a policy needs for each licence type, the reporting deadlines and a short self-assessment. Each “No” answer marks a gap worth closing before you apply.
Fraud prevention policy checklist (PDF)
Check your policy against EU requirements before you file it or update it.
- Required sections and EU rules
- Extra sections for EMIs and PIs, and for CASPs
- Reports to file and their deadlines
- 24-point self-assessment
Preparing a licence application?
We will help prepare or review the fraud prevention policy for your EMI, PI or CASP and make sure it fits your business model and the other documents in your application.
Regulatory note: this article describes EU rules as at October 2026. National rules, exemptions and supervisory practice may change specific requirements. It does not replace legal advice on a firm’s activities.
FAQ: fraud prevention policy
Does an EMI or PI need a fraud prevention policy?
Not necessarily under that name. PSD2 requires information on security, incidents, risks and fraud in the licence application. The authentication rules also require transaction monitoring.
A separate fraud prevention policy helps bring these duties together. But the procedures it describes must work in practice and match the firm’s other documents.
Must every CASP monitor market abuse and file STORs?
No. MiCA Art. 92 applies to firms that professionally arrange or execute crypto-asset transactions. The duty depends on the firm’s services.
CASPs that hold clients’ crypto-assets have separate duties under MiCA Art. 75. Before drafting the policy, define the requirements for each authorised service.
How often should fraud risks be reviewed?
PSD2 requires payment service providers to give the regulator an updated assessment of operational and security risks every year. The regulator may ask for it more often (PSD2, Art. 95(2)).
We recommend reviewing fraud risks at least once a year, and after material changes or incidents. For CASPs, an annual review of fraud risks is also a recommendation, not a general deadline set by MiCA.
How often must EMIs and PIs report fraud statistics?
Under PSD2 Art. 96(6), firms submit fraud statistics at least once a year. The EBA guidelines (EBA/GL/2018/05) provide for six-monthly reporting for most payment service providers.
Some small PIs and EMIs operating under special exemptions report once a year. The national regulator sets the exact deadlines.
The policy names who is responsible for reporting, the submission calendar and how the firm checks the data.
Does a small fintech need a whistleblowing channel?
Yes. For EMIs, PIs and other firms subject to the relevant financial and AML rules, headcount does not matter. They must have an internal channel for reporting breaches (Directive (EU) 2019/1937, Art. 8(4)).
Whether anonymous reports must be accepted depends on national law.
How is a fraud prevention policy different from an AML policy?
A fraud prevention policy covers fraud prevention, investigations, customer protection and financial losses. An AML policy covers the risks of money laundering and terrorist financing and how suspicious transactions are reported.
Both can use shared data. But their criteria for detecting breaches, investigation procedures and reporting differ.
Can a policy template be used for a licence application?
A template can serve as a starting point. But before filing, the firm must adapt it to its business model: its real risks, monitoring system, responsible staff and review procedures.
If the firm cannot carry out the procedures it describes, the regulator will have questions about the application.