EST · MMXXVI
Home/Insights/Guides/Complaint, Incident and Breach Notification Duties
Compliance, AML & Travel Rule

Complaint, Incident and Breach Notification Duties

Complaint, Incident and Breach Notification Duties. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagements. T

A cryptocurrency exchange discovers that a former employee accessed customer wallet data without authorization. The firm's regulator demands to know why it heard about the breach from a competitor's tip-off, not from the licensee. The data-protection authority issues a fine for late notification. The bank closes the account. The cost is immediate – frozen rails, reputational damage, and a compliance audit that halts operations for weeks.

Licensed digital-asset businesses carry overlapping notification duties to multiple audiences: the licensing regulator, data-protection authorities where applicable, affected customers, and in some cases banking counterparties and law enforcement. The triggers differ – a customer complaint, a suspicious transaction, a data breach, a system outage that delays settlement – but the common thread is the same: each duty runs on its own clock, and missing a deadline converts what would have been a managed disclosure into an enforcement event.

This guide maps the notification landscape a VASP, exchange, custodian or token issuer faces across the major licensing hubs, with the practical mechanics of who reports, when and to whom. The framework below assumes the business already holds the relevant licence and operates under the applicable AML compliance, KYC framework and transaction monitoring obligations. The question is what happens when something goes wrong – or when a user alleges that it did.

Which events trigger a notification duty

A notification obligation arises when a specified event occurs and a rule or licence condition requires the firm to inform a named authority or affected party. The event categories are broadly consistent across the flagship jurisdictions, though the precise definition and the timeline vary. The five common triggers are a customer complaint above a materiality threshold, a suspicious transaction meeting the jurisdiction's reporting standard, a data breach affecting personal information or wallet access, an operational incident that impairs service delivery, and a breach of a licence condition or regulatory requirement.

Customer complaints typically trigger an internal escalation duty first – the firm's complaint-handling procedure, documented in its operations manual, must log the matter and respond within a stated window. Where the complaint alleges fraud, unauthorized access or a disputed transaction, and the firm cannot resolve it to the customer's satisfaction within that window, the regulator expects notification. MiCA-compliant CASPs must maintain a complaints register and report unresolved matters to the national competent authority; VARA requires a complaints officer and mandates disclosure of complaint volumes in the annual audit. The substance of the complaint determines whether it also becomes a suspicious activity report or a data-breach notification.

Suspicious transactions are the domain of the money-laundering reporting officer (MLRO). Under the FATF baseline and its local implementations, a VASP files a suspicious activity report (SAR) or suspicious transaction report (STR) when it knows, suspects or has reasonable grounds to suspect that funds are the proceeds of crime or relate to terrorist financing. The obligation is activity-based, not volume-based: a single transaction can trigger the duty. In most jurisdictions the MLRO files to the financial intelligence unit (FIU); the timeline ranges from immediate (where there is an imminent risk) to a matter of days. Tipping-off prohibitions mean the customer is not told, and the transaction may be delayed or blocked while the report is assessed.

Data breach notification – overlapping regimes

A data breach affecting personal information or private keys sits at the intersection of data-protection law and financial-services regulation. Where the business operates under the EU General Data Protection Regulation (GDPR), a breach that poses a risk to individuals' rights must be notified to the relevant supervisory authority within 72 hours of the firm becoming aware of it. If the breach is likely to result in a high risk to individuals, the affected persons must be informed without undue delay. The clock starts when the firm has a reasonable degree of certainty that a breach has occurred, not when the forensic investigation concludes.

The licensing regulator typically expects its own notification in parallel. VARA's operational-resilience rules require immediate notification of any cybersecurity incident affecting customer assets or data. The MiCA framework mandates disclosure of significant ICT incidents to the national competent authority, with severity thresholds set at the member-state level. Where the breach involves customer funds or wallet access, the duty often extends to banking counterparties under the account terms, and to insurance providers where the firm holds crime or cyber cover.

The practical challenge is that the 72-hour GDPR window often expires before the forensics team can quantify the exposure. The initial notification to the supervisory authority states what is known at that time – the nature of the breach, the categories of data affected, the approximate number of individuals and the measures taken to mitigate harm – with a commitment to provide further detail as the investigation progresses. Under-reporting in the initial notice is safer than delay; the authority can be updated as facts emerge.

Operational incidents and service disruptions

An operational incident is any event that impairs the firm's ability to deliver the service its licence authorizes. The category includes system outages, trading-platform downtime, delayed settlement of withdrawals, loss of access to cold-storage keys, and third-party vendor failures where the vendor provides a critical service. The notification duty exists because the regulator needs to assess whether the incident threatens the firm's solvency, exposes customer assets to loss or indicates a control failure that requires supervisory intervention.

Most regimes set a materiality threshold. MiCA requires notification of "significant" ICT incidents; what qualifies as significant depends on the duration of the outage, the number of affected clients and whether customer assets are at risk. VARA expects notification where an incident affects more than a stated percentage of users or where service is interrupted for longer than a specified period. The Singapore MAS framework uses a hybrid test: impact on service availability, loss or compromise of data, and financial loss above a threshold all trigger the duty independently.

The timeline for operational-incident notification is typically shorter than for complaints – often within hours of detection, with a follow-up report once the root cause is established. The regulator expects the initial notice to state what happened, the scope of the impact, what the firm is doing to contain it and an estimate of when normal service will resume. The follow-up addresses root cause, lessons learned and whether the incident revealed a gap in the firm's operational-resilience plan that requires remediation.

Suspicious activity reporting – mechanics

The MLRO is the statutory owner of the SAR process. Every transaction that meets the suspicion threshold must be evaluated and, if the suspicion is substantiated, reported to the jurisdiction's FIU. The threshold is not certainty – it is reasonable grounds to suspect. In practice, this means the firm's transaction monitoring system flags patterns consistent with money laundering or terrorist financing (rapid turnover, structuring to avoid thresholds, geographic risk, counterparty on a sanctions list), and the MLRO reviews the alert against the customer's profile and stated business purpose.

Where a SAR is filed, the transaction may be subject to a temporary hold under the jurisdiction's consent regime. In the United Kingdom, the firm may need consent from the National Crime Agency (NCA) before proceeding; the NCA has a statutory period to respond, and silence is deemed consent after that window. Proceeding without consent where consent is required is a criminal offense. Other jurisdictions allow the firm to proceed but require disclosure of the suspicion; the FIU may then initiate its own investigation or request further information from the firm.

The tipping-off prohibition means the customer cannot be told why a transaction is delayed or why an account is under review. Telling the customer – or anyone else outside the firm's compliance team – that a SAR has been filed, or is being considered, is itself an offense in most jurisdictions. The practical consequence is that customer communication during a SAR review must be carefully scripted: "further verification is required" or "the transaction is subject to enhanced review" are permissible; any reference to law enforcement or money-laundering suspicion is not.

Licence-condition breaches

A breach of a licence condition occurs when the firm fails to meet a requirement set out in the licence itself, the regulator's rulebook or an undertaking given during the application process. Common examples include operating outside the permitted scope (offering a service the licence does not cover), failing to maintain the required capital or liquid-asset buffer, appointing a key person (director, MLRO, compliance officer) who does not meet the fit-and-proper standard, and breaching the AML compliance, KYC framework or transaction monitoring standards the licence requires.

The duty to notify the regulator of a breach is often immediate – "as soon as the firm becomes aware" is the standard formulation. Waiting to assess the breach or attempting to remedy it before disclosure extends the period of non-compliance and is treated as an aggravating factor. The regulator expects to hear about the breach from the firm, not from an audit finding or a whistleblower complaint. Where the breach is material – it affects customer assets, creates a solvency risk or indicates a systemic control failure – the regulator may place the firm under enhanced supervision, require an independent review or impose conditions on the licence while the firm remediates.

The notification must state what the breach is, how it occurred, what risk it created and what the firm has done to contain it. Where the breach resulted from a lapse by a key person, the regulator will want to know whether that person remains in post and what steps have been taken to prevent recurrence. A pattern of breaches – even if each is individually minor – signals a weak compliance culture and typically results in a more intrusive supervisory response than a single well-managed incident would attract.

Who reports – internal ownership

The notification duty falls on the firm, but internal accountability varies by event type. For customer complaints, the first point of contact is the complaints handler or customer-support lead; unresolved matters escalate to the compliance officer or the designated complaints officer where the licence requires one. For suspicious transactions, the MLRO is the statutory owner – no one else in the firm can file a SAR on behalf of the entity. For data breaches, the data-protection officer (DPO) where one is appointed, or the compliance officer in smaller firms, coordinates the GDPR notification; the same person or the chief information security officer typically notifies the licensing regulator. For operational incidents, the chief operating officer or head of technology initiates the report, with compliance confirming that the regulator's materiality threshold is met.

In multi-jurisdiction operations, the question of who reports becomes more complex. A VASP licensed in Malta under MiCA serves customers across the EU; a data breach in its Dublin data center affects users in France, Germany and Italy. The firm must notify the lead supervisory authority (the Maltese regulator in this case) and may need to notify other member-state authorities where users are resident. The GDPR one-stop-shop mechanism means a single notification to the lead authority is usually sufficient, but the national implementing rules for financial services may add requirements. Allied counsel in each relevant jurisdiction can confirm the local position before the 72-hour window closes.

The board retains oversight responsibility. Every material notification – a data breach, a significant operational incident, a pattern of SARs indicating a control gap – should be logged with the board, with a note of when the regulator was informed and what remediation the firm is undertaking. The regulator will ask for board minutes in an audit or investigation, and a gap between the date of the event and the date the board was told is a red flag.

Timelines by notification type

Customer complaints follow the longest timeline – the firm's internal procedure typically allows several business days or weeks to resolve the matter before escalation to the regulator is required. The MiCA framework sets outer limits at the member-state level; VARA requires a response to the customer within a stated period and disclosure to the regulator if the matter remains unresolved after that window.

Suspicious activity reports are filed as soon as the MLRO has reasonable grounds to suspect, with "as soon as practicable" being the common standard. In high-risk cases – where there is an imminent threat of terrorist financing or where the transaction involves a sanctioned counterparty – the timeline compresses to hours. The consent regime jurisdictions add a procedural step: the firm requests consent, waits for the FIU to respond within the statutory period, and only then proceeds (or declines) the transaction.

Data breaches under GDPR carry the 72-hour rule from the point the firm becomes aware. High-risk breaches require notification to affected individuals without undue delay, typically interpreted as within days once the firm has enough information to communicate meaningfully. The licensing regulator's timeline often mirrors the GDPR standard – immediate for critical incidents, within 72 hours for material breaches, and in all cases a follow-up report once the investigation is complete.

Operational incidents are notified within hours where the incident is ongoing and affects customer access to funds or data. Once the incident is contained, a root-cause report follows within a matter of days or weeks, depending on the jurisdiction. Licence-condition breaches are reported as soon as the firm identifies them – there is no grace period for internal assessment.

What the regulator expects in the notification

The content of a notification is prescribed by the jurisdiction's rules or guidance, but the core elements are consistent. The regulator needs to know what happened, when it happened, who is affected, what risk the event created and what the firm has done about it. A notification that omits any of these elements will result in follow-up questions and may be treated as inadequate.

For data breaches, the regulator expects the nature of the breach (unauthorized access, accidental disclosure, ransomware attack), the categories of data affected (names, email addresses, transaction history, private keys), the number of individuals affected (or an estimate if exact numbers are not yet available), the likely consequences for those individuals, and the measures taken to mitigate harm (password resets, user alerts, enhanced monitoring, forensic investigation). Where private keys or seed phrases were exposed, the firm must state whether any funds have been moved and what it is doing to secure affected wallets.

For operational incidents, the regulator wants to see the timeline (when the incident began, when it was detected, when normal service resumed), the root cause if known, the number of customers affected, any financial loss, and the steps taken to prevent recurrence. If the incident was caused by a vendor failure, the regulator will ask what due diligence the firm conducted on that vendor and whether the vendor's performance is subject to a service-level agreement with penalties for downtime.

Cross-border notification – who gets told

A business operating under multiple licences faces parallel duties. A CASP passporting into Germany, France and the Netherlands from a Lithuanian base must notify the Bank of Lithuania as lead supervisor; depending on the nature of the incident, it may also need to inform the national authorities in each host state. The MiCA passporting framework centralizes prudential supervision with the home regulator, but conduct and consumer-protection issues may still require local notification.

A VASP licensed in Dubai under VARA and separately in Abu Dhabi under the ADGM regime reports to both authorities – there is no mutual recognition between the two UAE regulators. A firm holding a Payment Services Act licence in Singapore and a VASP registration in Hong Kong notifies both MAS and the SFC independently; the timelines and materiality thresholds differ.

Where the business banks in a jurisdiction where it does not hold a digital-asset licence – for example, a Malta CASP with a bank account in Switzerland – the bank's terms typically require notification of any regulatory action, licence suspension or material compliance breach. Failing to notify the bank under those terms gives the bank contractual grounds to close the account, even if the underlying incident would not have triggered that result on its own. The cross-border reality for digital-asset firms is that every material event must be assessed against multiple notification regimes simultaneously.

If your firm has experienced an incident and the notification clock is running, immediate legal input can clarify which authorities must be told, in what sequence and within what window. Parallel filings across jurisdictions are coordinated to avoid inconsistency; allied counsel in the relevant jurisdiction confirms the local position. Map your obligations now.

Common mistakes in the notification process

The most frequent error is delay. Firms wait to investigate before notifying, reasoning that a complete picture is better than a preliminary report. The regulator sees it differently: delay signals that the firm does not understand its duties or, worse, that it attempted to assess the breach internally before deciding whether to disclose. Most regimes allow – and expect – an initial notification based on incomplete information, with updates as the investigation progresses. Waiting for certainty before notifying usually means the deadline has passed.

A related mistake is under-classification. The firm treats a data breach as an IT issue, not a regulatory event, and notifies the technology team but not the regulator. A customer complaint about a disputed transaction is logged in the support system but not escalated to compliance. An operational incident is resolved internally without checking whether it met the materiality threshold for regulatory disclosure. The regulator discovers the gap during an audit and treats the non-disclosure as a separate breach.

Inconsistent narratives across filings create enforcement risk. The firm notifies the data-protection authority that a breach affected 5,000 users but tells the licensing regulator the number was 3,000. The root-cause report to the regulator states the incident lasted four hours; the customer communication said two hours. The regulator will ask why the numbers differ, and any answer that implies the firm tailored the disclosure to minimize the perceived severity is treated as a lack of candor.

Tipping-off violations occur when a firm, in an effort to be transparent, tells a customer that a SAR has been filed or that the account is under review at the request of law enforcement. The customer moves the funds to another platform or jurisdiction, frustrating the investigation. The firm faces prosecution for the tipping-off offense, which is often treated more seriously than the underlying money-laundering suspicion.

Remediation and follow-up

A notification is not the end of the process. The regulator will expect evidence that the firm has identified the root cause and taken steps to prevent recurrence. For a data breach, that may mean enhanced access controls, staff training on phishing, engagement of a third-party security auditor, or a switch to a more secure hosting provider. For an operational incident, it may mean system redundancy, a tested disaster-recovery plan, or contractual changes with the vendor whose failure caused the outage.

Where the breach indicates a systemic issue – the MLRO was under-resourced, the transaction-monitoring system was misconfigured, the complaints log was not reviewed by senior management – the regulator may require an independent skilled-person review. The firm pays for the review, and the report goes to the regulator, not to the firm's board. The skilled person will identify control gaps and recommend remediation; the regulator then monitors implementation, often through quarterly progress reports.

In severe cases the regulator imposes interim restrictions: a cap on new customer onboarding, enhanced reporting requirements, a requirement that certain decisions be approved by the regulator before implementation, or appointment of an independent compliance monitor. These restrictions remain in place until the regulator is satisfied that the root cause has been addressed and that the firm's culture has shifted to prioritize compliance. For a growth-stage crypto business, a period of restricted operations can be fatal – the regulatory signal deters banking partners, investors and customers alike.

Building a notification protocol

A notification protocol is a written procedure that states which events trigger a duty, who owns the assessment, what the timeline is and where the template notification lives. The protocol should be part of the firm's compliance manual and reviewed by the board at least annually. Every key person – directors, MLRO, compliance officer, DPO, COO, head of customer support – must know what their role is when an incident occurs.

The protocol begins with a decision tree. Is the event a customer complaint? Route to the complaints handler; if unresolved within the internal timeline, escalate to compliance, who notifies the regulator. Is it a suspicious transaction? Route to the MLRO, who files a SAR if the threshold is met. Is it a data breach? Route to the DPO (or compliance if there is no DPO); notify the supervisory authority within 72 hours and the licensing regulator under its incident-notification rule. Is it an operational incident? Route to the COO; assess against the materiality threshold; if met, notify the regulator within the required window.

The protocol includes template notifications for each event type, pre-approved by external counsel. The template states what information must be included, where to find that information (the transaction-monitoring log, the complaints register, the incident log, the audit trail), and who signs off before the notification is sent. For time-sensitive reports – data breaches, SARs in high-risk cases – the template includes a pre-drafted holding message that can be sent within the deadline, with a commitment to follow up with detail as soon as it is available.

The protocol is tested. At least once a year, the firm runs a tabletop exercise: a hypothetical incident is introduced (a ransomware attack, a rogue employee accessing wallets, a system outage during a market event), and the team walks through the notification process in real time. Who would be notified? In what order? Using which template? Who signs off? What information would the regulator need, and where would it come from? The exercise surfaces gaps – missing contact details for the regulator's incident desk, uncertainty about whether a given scenario meets the materiality threshold – that can be fixed before a real incident occurs.

How OBOLUS supports notification compliance

OBOLUS designs notification protocols that map the firm's licensing stack – operating jurisdiction, host jurisdictions, banking jurisdiction, data-hosting jurisdiction – to the overlapping duties each imposes. We draft the decision trees, the escalation paths and the template notifications, and we test them against real scenarios drawn from enforcement files and audit findings across the flagship hubs. For firms operating under MiCA, VARA, MAS or the SFC regime, we align the protocol to the local rules and confirm the regulator's expectations through direct engagement where needed.

Where an incident has occurred and the notification deadline is approaching, we coordinate the filings. That means assessing which authorities must be told, drafting the initial notification to meet the timeline, preparing the follow-up root-cause report, and liaising with the regulator if questions arise. For cross-border incidents – a data breach affecting users in multiple member states, an operational failure that impacts customers in several licensing jurisdictions – we work with allied counsel in the relevant jurisdiction to ensure each filing is consistent and complete.

For firms facing an audit or a skilled-person review triggered by a notification, we manage the response. That includes gathering the evidence the regulator requests, preparing the remediation plan, coordinating with the skilled person, and negotiating the scope and timeline of any interim restrictions the regulator proposes. The goal is to demonstrate that the firm has addressed the root cause and that the control environment is now fit for purpose, so that restrictions can be lifted and normal operations can resume.

To implement a notification protocol before an incident occurs, or to manage a live notification where the clock is already running, contact OBOLUS at info@oboluslaw.com. We scope the engagement as a fixed package: protocol design or incident response, with the timeline and deliverables stated at the outset. For a firm operating under multiple licences, we map the full set of duties so that nothing is missed.

Related at OBOLUS

FAQ

What does this regime require from a VASP?

A VASP operating under any of the flagship regimes – MiCA, VARA, MAS, SFC, FINMA – must maintain systems to detect, log and report the five core event types: customer complaints, suspicious transactions, data breaches, operational incidents and licence-condition breaches. Each event type carries its own timeline and materiality threshold. The systems must be documented in the compliance manual, assigned to named individuals, and tested at least annually. Notification is not discretionary; where the threshold is met, the duty is mandatory and the clock starts immediately.

Who must act as MLRO for a crypto firm?

The MLRO must be an individual (not a committee) who holds sufficient seniority to access transaction data, customer files and the board, and who has the authority to halt a transaction or block a customer where a money-laundering suspicion arises. Most licensing regimes require the MLRO to be approved by the regulator as a key person and to hold a recognized AML qualification or equivalent experience. The MLRO cannot be the same person as the chief executive or the chief financial officer in jurisdictions that require functional separation of compliance. Where the firm is part of a group, the group MLRO may oversee the subsidiary's AML program, but a local MLRO is usually required for the licensed entity.

How do regulators audit crypto AML programs?

A regulator's AML audit begins with a document request: the transaction-monitoring policy, the SAR log, the customer risk-rating methodology, evidence of staff training, and the most recent independent AML review. The regulator then samples transactions – typically high-value transfers, transfers involving high-risk jurisdictions, and rapid on-and-off-ramps – and asks why each was or was not flagged. The regulator interviews the MLRO, reviews the complaints log for patterns, and checks whether SARs were filed within the required timeline. Where gaps are found, the regulator may require an independent skilled-person review, impose a fine, or restrict the licence until remediation is complete. The audit cycle varies but is typically annual for licensed VASPs and more frequent for firms under enhanced supervision.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. In our cross-border work, we routinely coordinate notification filings for firms operating under multiple licences, drafting the protocol in advance and managing the response when an incident occurs. We map the licence stack across operating, custody and payment layers before you commit, so that notification duties are identified and assigned before the business goes live. To discuss your situation, contact info@obolus.com.

By Victor Olsen, Regulatory & Compliance Analyst – Victor specializes in AML compliance frameworks, transaction monitoring systems and notification-protocol design for licensed VASPs across the MiCA, VARA and MAS regimes.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours