Consider the position of a fintech or software business that loses access to important systems and receives a cryptocurrency demand. Its insurer proposes an incident-response firm and a payment intermediary. The company can make no contact, refuse payment, defer a proposal while facts are checked, or consider a defined payment once the applicable conditions are satisfied. Paying through the insurer or its provider adds actors and legal connections. The recipient, indirect benefit and victim's own duties still require assessment. The ransomware advisory of the US Office of Foreign Assets Control (OFAC), the ransomware guidance of the UK Office of Financial Sanctions Implementation (OFSI) and Australia's express on-behalf reporting rule make that point particularly important.
The law and regulatory status are stated as at 19 November 2026. This comparison covers the United States and Canada; the UK, France, Germany and the EU level; Singapore and India; the United Arab Emirates (UAE) and Saudi Arabia; South Africa and Nigeria; Brazil and Mexico; and Australia and New Zealand. The countries were selected for differences that change this decision, including specific payment reports, insurance conditions, provider rules and distinct reporting triggers. EU rules are addressed once, with national differences set out separately.
English explanations of non-English laws are unofficial paraphrases; the original legal text controls.
Establish who is acting and which laws follow the transaction
Begin with an entity and transaction map. Identify the affected company, the owner of the funds, the person authorising expenditure, the insurer, the negotiator, the exchange or custodian and the entity that would make each transfer. Record where decisions and services occur, the parties' incorporation and relevant nationality or residence, financial licences, critical-infrastructure status, affected data and customers, and the banks or exchanges in the route.
The victim's location and lack of designation answer only part of the question. A recipient may act through another person, control an unlisted entity or receive an indirect benefit. Currency denomination alone is an incomplete jurisdictional test: identify the actual bank, clearing, provider and personnel connections. A foreign payment company can bring its own restrictions even where the victim's domestic law has no dedicated ransomware payment ban. US cyber-sanctions regulations, Articles 3 and 18 of the EU cyber-sanctions Regulation, Canada's sanctions framework and New Zealand's sanctions legislation each require their own nexus assessment.
The business description also needs legal classification. Establish whether the software supplier is also a bank, payment institution or another regulated entity. Its actual classification determines whether the EU Digital Operational Resilience Act (DORA), Australian Prudential Regulation Authority (APRA), Monetary Authority of Singapore (MAS), Saudi Central Bank (SAMA) or other sector duties apply. A company can be both a victim and a data processor, or both a product manufacturer and a regulated financial entity. Contracts can allocate assistance and filing work while the statutory duty remains with the designated entity. DORA expressly preserves the financial entity's responsibility when reporting is outsourced. The entity must notify its competent authority of the arrangement as soon as it is concluded and before the first notification or report. Implementing Regulation 2025/302, Article 6; DORA, Articles 2 and 19
- Victim company. What it must establish for the proposed route: Its applicable restrictions, reports, authority, customer obligations and recovery options. Documents and records to obtain: Entity and licence records, incident chronology, demand and attribution evidence, policy, reporting register and decision record.
- Directors or delegated officers. What it must establish for the proposed route: Actual powers, conflicts, relevant care duties and an informed decision about a defined act. Documents and records to obtain: Constitution/bylaws, resolutions and delegations, spending limit, alternatives, reasons and approval conditions.
- Insurer. What it must establish for the proposed route: Coverage and consent scope, its own payment/reimbursement restrictions and any applicable reporting role. Documents and records to obtain: Full policy and endorsements, written vendor and payment consents, reservation of rights, payer identity and reimbursement conditions.
- Negotiator or incident responder. What it must establish for the proposed route: Its mandate and whether it merely advises or also arranges, controls, converts or transfers value. Documents and records to obtain: Engagement, authority to communicate, service description, subcontractors, complete communications and escalation rules.
- Payment provider. What it must establish for the proposed route: Activity-specific permissions, customer and beneficial-owner checks, sanctions controls, transfer information, reporting and any transaction hold. Documents and records to obtain: Exact legal entity, licence/registration or valid transition evidence, custody and funds path, compliance determination and records accessible to the victim.
This is a recommended allocation of the decision file. The binding duties differ by role and jurisdiction. The insurer's panel appointment should never substitute for checking what the appointed firm will actually do.
Decide whether the payment route is prohibited, restricted or still unresolved
Sanctions and terrorist financing require separate findings
A search for a dedicated ransomware ban is insufficient. Asset-freezing measures can prohibit making funds or economic resources available directly or indirectly to designated persons and controlled entities. Terrorist-financing law can apply without a designation or an executed terrorist act, depending on the jurisdiction's intention, knowledge, reasonable-ground or recklessness tests. Ordinary AML offences have their own proceeds and conduct requirements. Establish the required proceeds element before characterising treasury funds as laundered proceeds. Apply terrorist-financing and sanctions tests separately to the recipient, intended use and benefit.
In the United States, OFAC's advisory expressly addresses insurers, digital-forensics and incident-response firms, banks and money-services businesses that facilitate ransomware payments. Civil sanctions exposure can arise without knowledge that the transaction was prohibited. Cooperation and a sanctions compliance programme can affect enforcement assessment. Payment still requires a lawful route under each applicable restriction. Any licence must actually cover the proposed conduct. OFAC advisory, pages 3–6
In the UK, apply the relevant sanctions instrument and OFSI guidance to the payer and facilitator. Civil monetary penalties can arise without satisfying the sanctions provision's knowledge, suspicion or belief requirement. Policing and Crime Act 2017, section 146(1A). Obtain any required OFSI licence separately from a defence or consent under another financial-crime process. The National Crime Agency's (NCA) guidance expressly distinguishes the AML/terrorist-financing defence process from sanctions authorisation. The UK also has a specific offence covering an insurer's payment under, or purportedly under, an insurance contract concerning property already handed over or to be handed over in response to a demand made wholly or partly for terrorism, where the insurer or payment authoriser has the specified knowledge or reasonable cause to suspect. Apply this test to advance funding as well as later reimbursement. Cyber Sanctions Regulations; UKFIU guidance; Terrorism Act, section 17A
EU asset-freezing rules likewise require assessment of indirect availability, ownership/control and the actual exception or authorisation. France adds its own terrorism-financing offence and covered-professional suspicious-reporting procedures. In Germany, a reportable suspicious transaction can engage the separate standstill under section 46 of the Money Laundering Act (GwG): execution ordinarily requires consent or the prescribed period to expire without prohibition, subject to the actual statutory exception. Neither filing a suspicious transaction report (STR) nor an attacker's deadline supplies general clearance. EU Regulation 2019/796; French Penal Code 421-2-2; CMF L561-15–18 and L561-24; German GwG 43 and 46
Singapore's Terrorism (Suppression of Financing) Act (TSFA) addresses terrorist purposes, property, services and facilitation, including specified reasonable-ground tests. India's Unlawful Activities (Prevention) Act (UAPA) and section 51A freezing procedures also require a recipient, purpose and conduct assessment. The Supreme Court's 2021 Sudesh Kedia bail decision is a useful caution against assuming every extorted payment proves terrorist-financing participation: its findings concerned particular facts and were expressly confined to bail. Each payment requires its own application of the offences, sanctions and freezing rules. Singapore TSFA, sections 3–8; India UAPA; section 51A procedure; Sudesh Kedia, paragraphs 11(A)–12
As at 19 November 2026, the UAE's federal AML framework is the 2025 law and implementing regulation, including virtual assets and attempted transactions. Its designated-asset rules apply alongside the distinct local service permissions. Saudi Arabia’s December 2025 targeted-financial-sanctions rules for SAMA-supervised financial institutions expressly include ransom payments to designated persons within the relevant funds definition, regardless of payment method or payer. Apply that designated-recipient rule within its institutional scope, alongside the general criminal financing provisions. UAE Decree-Law 10/2025; Cabinet Resolution 134/2025; Cabinet Resolution 74/2020; Saudi TFS rules
South Africa combines the Financial Intelligence Centre Act's designated-property and suspicious-transaction rules with separate terrorism-financing provisions. Nigeria requires particular care: the enacted Terrorism (Prevention and Prohibition) Act's section 21 financing rules and section 24 references to detained property or facilities require a reasoned assessment of the demand and intended benefit. Classify the conduct under those enacted provisions, including the detention/property and financing elements, even where the recipient is unlisted. Any proposed ban requires its own enactment and commencement. South African FIC Act; POCDATARA; 2022 amendment; Nigeria TPPA, sections 21, 24 and 54
Brazil's United Nations sanctions implementation and terrorism-financing law, and Mexico's criminal financing and regulated-bank blocking rules, also constrain a route even where no dedicated payment-reporting law applies. Mexico's statutory blocked-list framework in force and the Supreme Court's 6 April 2026 decisions must be considered before relying on older summaries about the limited grounds for bank freezing. Australia and New Zealand similarly require separate sanctions and terrorist-financing conclusions; a permit or exemption under one provision cannot be assumed to override another offence. Brazil Law 13.810; Law 13.260, Article 6; Mexico CPF; LIC blocked-list provisions; Australia sanctions regulations; NZ Terrorism Suppression Act
Public-sector bans and proposals have different consequences
North Carolina's covered state and local government entities may neither pay nor otherwise communicate with the entity that encrypted their systems and demanded ransom. A private supplier should establish whether the particular restriction or a relevant contract reaches its role. New Zealand's government-agency non-payment policy is distinct from its strong advice to private businesses not to pay. North Carolina section 143-800; NZ DPMC cyber-ransom advice
Do not turn a proposed regime into an operative ban or reporting duty. As at 19 November 2026, the final rule under the US Cyber Incident Reporting for Critical Infrastructure Act (CIRCIA) remained pending, Canada's Critical Cyber Systems Protection Act (CCSPA) had been enacted but was not in force, and the UK's ransomware legislative proposals remained distinct from existing law. France's bill on resilience and on the second Network and Information Security Directive (NIS2) had passed an amended first reading in the National Assembly on 17 November 2026; that was not promulgated replacement legislation. Existing applicable incident, privacy and financial-crime rules continue to matter. CISA; OIRA; CCSPA; UK proposals; French Assembly record
Start each reporting clock from the event the rule specifies
For the lists below, CASP/VASP means a crypto-asset or virtual-asset service provider; CDD is customer due diligence; STR/SAR is a suspicious transaction/activity report. Financial-sector abbreviations identify specific regulated classes: FRFI (Canadian federally regulated financial institution), PSP/PSO (payment service provider/system operator), and IFPE (Mexican electronic-payment-funds institution). CII means designated critical information infrastructure; OES/RDSP identifies the UK essential-service and relevant digital-service categories. Establish the local definition before applying an entry.
The incident team should record discovery, awareness, classification, payment and awareness of another actor's payment separately. It should also distinguish regulator notice, affected-person notice, a police complaint, suspicious-transaction reporting and an insurer claim. One can be due while another is not triggered.
The list compares decision-changing routes. Apply each entry only after establishing its entity, event and territorial scope. “Immediately,” “without undue delay” and similar wording still matters where an outer limit is also given. Business days, working days, calendar days and elapsed hours must be calculated under the applicable rule.
- Australia: reporting business entity. Trigger, recipient and initial timing: Qualifying cyber-extortion payment: report to the designated Commonwealth body within 72 hours after paying, or after becoming aware that another entity paid on its behalf. Further facts, updates or scope qualification: Report required incident, demand, payment, payer and communications information known or discoverable by reasonable search/enquiry. Ordinary business turnover must exceed the statutory threshold; covered critical infrastructure has a separate route. Act 26–27; Rules 6–7.
- New York Department of Financial Services (DFS) covered entity. Trigger, recipient and initial timing: Cybersecurity incident: as promptly as possible, within 72 hours after determination. Extortion payment connected with an event involving the entity: within 24 hours after payment to DFS. Further facts, updates or scope qualification: Within 30 days after payment, give reasons, alternatives considered and diligence concerning legality and alternatives. These payment stages are separate from the incident report. 500.17.
- US domestic reporting issuer. Trigger, recipient and initial timing: Form 8-K Item 1.05: four business days after determining materiality. Further facts, updates or scope qualification: Determine materiality without unreasonable delay after discovery; use the form's actual disclosure and permitted-delay rules. The materiality determination starts this issuer-specific clock. Form 8-K.
- US banking organisation / covered bank service provider. Trigger, recipient and initial timing: Bank: as soon as possible, within 36 hours after determining a notification incident. Provider: affected-bank notice as soon as possible on the specified disruption test. Further facts, updates or scope qualification: The provider's four-hour actual/likely disruption condition defines the reportable event; notice is due as soon as possible once the test is met. Federal Reserve rule guidance.
- Canada: Personal Information Protection and Electronic Documents Act (PIPEDA) organisation. Trigger, recipient and initial timing: Office of the Privacy Commissioner of Canada and affected people: as soon as feasible after determining a breach creates a real risk of significant harm. Further facts, updates or scope qualification: Keep prescribed records of all breaches for 24 months; provincial routes need their own assessment. No general federal 72-hour clock applies. PIPEDA 10.1–10.3; Breach Regulations.
- Canada: FRFI / retail PSP. Trigger, recipient and initial timing: Office of the Superintendent of Financial Institutions (OSFI): within 24 hours, or sooner if possible, for an incident within the scope of OSFI's reporting advisory. Retail Payment Activities Act (RPAA) section 18: notify the Bank of Canada and materially affected parties without delay. Further facts, updates or scope qualification: Bank of Canada guidance expects no later than 48 hours after materiality determination. Apply the statutory without-delay duty alongside that supervisory expectation. OSFI; RPAA; Bank guidance.
- UK: OES / relevant digital service provider. Trigger, recipient and initial timing: Scoped significant/substantial incident: relevant authority, without undue delay and no later than 72 hours after the rule's awareness event. Further facts, updates or scope qualification: OES and RDSP tests differ. RDSP reporting goes to the Information Commission and requires access to information enabling substantial-impact assessment. Give entity/service, time, duration, nature/impact and cross-border information. NIS regulations 11–12.
- UK: controller / FCA firm. Trigger, recipient and initial timing: UK GDPR controller: notify the Information Commission without undue delay and, where feasible, within 72 hours after awareness, unless rights/freedoms risk is unlikely. FCA SUP 15.3.1: immediate notice on its specified serious-regulatory-impact grounds. Further facts, updates or scope qualification: Processor-to-controller and high-risk affected-person notices are separate. Assess the firm's reputation, adequate customer service/serious detriment and wider financial consequences under the actual FCA rule. The FCA's general incident-reporting framework applies from 18 March 2027. UK GDPR 33–34; FCA SUP 15.3.1; FCA reporting guidance.
- EU: GDPR controller / processor. Trigger, recipient and initial timing: Controller to supervisory authority: without undue delay and, where feasible, 72 hours after awareness, unless risk is unlikely. Processor to controller: without undue delay. Further facts, updates or scope qualification: Phase missing information without undue further delay; document facts, effects and remedial action. High-risk affected-person notice has a separate Article 34 test. GDPR 33–34.
- EU: DORA financial entity. Trigger, recipient and initial timing: Initial notice as early as possible, within four hours of major classification and ordinarily 24 hours of awareness. Further facts, updates or scope qualification: If classified more than 24 hours after awareness, report within four hours of classification. Intermediate: 72 hours after initial notice; final: one month after the latest intermediate report. Weekend relief has entity/report exclusions; updates and affected-client duties remain. DORA 19; 2025/301, Article 5.
- France: covered essential / digital services. Trigger, recipient and initial timing: As at 19 November 2026, a qualifying incident under the first Network and Information Security Directive (NIS1) regime goes to the National Cybersecurity Agency of France (ANSSI) without delay after awareness. Further facts, updates or scope qualification: Apply national entity and impact scope. Digital-service coverage has establishment/representative and conjunctive small-business conditions. DORA and privacy are separate assessments. Law 2018-133, Articles 7, 11, 13.
- Germany: entity covered by the Act on the Federal Office for Information Security (BSIG). Trigger, recipient and initial timing: Significant incident: immediate/max 24-hour early warning, immediate/max 72-hour incident report. Further facts, updates or scope qualification: Requested interim updates; final report normally one month after the 72-hour report. An ongoing incident needs a progress report, followed by a final report after handling. Check the section 28 DORA exclusion first. BSIG 28, 32.
- Singapore: Personal Data Protection Act (PDPA) organisation / data intermediary. Trigger, recipient and initial timing: Assess reasonably and expeditiously. Notice to the Personal Data Protection Commission (PDPC) is due as soon as practicable and no later than three calendar days after the day of the notifiability assessment. Further facts, updates or scope qualification: The three-calendar-day period starts after the day of the notifiability assessment. Harm and significant scale are distinct gates; data intermediaries notify the organisation without undue delay. Individual notice has its own conditions. PDPA 26C–26D.
- Singapore: specified MAS entity. Trigger, recipient and initial timing: FSM-N13 relevant incident: as soon as possible, within one hour of discovery. Further facts, updates or scope qualification: MAS’s reporting-process guidance adds an initial report as soon as possible, within 24 hours of incident discovery, subject to an earlier MAS request, and a final report within 14 days of discovery. The underlying notification remains due. FSM-N13; MAS circular.
- Singapore: designated CII actor / temporary-concern system. Trigger, recipient and initial timing: Main prescribed incident branch: two hours from awareness, supplementary report within 72 hours from awareness. Further facts, updates or scope qualification: Final report: 30 days after the supplementary report. Under the third-party CII rules effective 13 July 2026, the specified non-disrupting provider-controlled-system branch has quarterly reporting, subject to escalation. Verify designation, system relationship and incident category. CII regulations; third-party CII regulations; temporary-concern regulations.
- Singapore: entity of special cybersecurity interest. Trigger, recipient and initial timing: Prescribed incident on the designated system: 24 hours from awareness, supplementary report within 72 hours from awareness. Further facts, updates or scope qualification: Final report: 30 days after the supplementary report. The regulations for entities of special cybersecurity interest took effect 30 October 2026; the entity’s designation must be established. ESCI regulations.
- India: entity covered by the directions of the Indian Computer Emergency Response Team (CERT-In) / phased non-bank PSO. Trigger, recipient and initial timing: Annex I incident to CERT-In within six hours of noticing or being brought to notice. Covered Reserve Bank of India (RBI) non-bank PSO: RBI within six hours of detection, plus CERT-In. Further facts, updates or scope qualification: Ransomware is listed. Available facts can be followed by reasonable-time supplementation. The 5 November 2026 PSO directions apply to large and medium PSOs from website publication; the small-PSO implementation date is 1 April 2028; as at 19 November 2026, the relevant general breach provisions of the Digital Personal Data Protection (DPDP) Act were not yet operative. CERT-In directions/FAQs; RBI directions; DPDP commencement.
- UAE: Virtual Assets Regulatory Authority (VARA) VASP. Trigger, recipient and initial timing: Material cyber/qualifying business continuity and disaster recovery (BCDR) event: as soon as reasonably practicable, within 72 hours of detection. Further facts, updates or scope qualification: Separate data rule: notify VARA as soon as possible and within 24 hours after notifying the data regulator or an affected person. Include nature, scope, impact, mitigation and other notices. Technology Rulebook I.K.1 / II.C.2.
- UAE: Dubai Financial Services Authority (DFSA) / Financial Services Regulatory Authority (FSRA) authorised firm. Trigger, recipient and initial timing: DFSA material cyber incident: as soon as reasonably practicable, within 72 hours of awareness/reasonably suggestive information. FSRA material cyber incident: 24 hours after awareness or information reasonably suggesting occurrence, under GEN 3.5.18. Further facts, updates or scope qualification: FSRA's separate GEN 8.10.6 operational notice can be immediate. Use prescribed initial/progressive reports and the correct entity's regulator. DFSA; FSRA.
- UAE: Dubai International Financial Centre (DIFC) / Abu Dhabi Global Market (ADGM) data controller. Trigger, recipient and initial timing: DIFC Article 41: as soon as practicable for the specified compromise. ADGM section 32: without undue delay and, where feasible, 72 hours after awareness, unless risk is unlikely. Further facts, updates or scope qualification: Separate processor and high-risk individual notices, records and phased information. Do not import either rule into the federal Personal Data Protection Law. DIFC; ADGM; federal PDPL.
- Saudi Arabia: scoped financial entity / data controller. Trigger, recipient and initial timing: SAMA medium/high cyber or covered operational incident: immediate notice under applicable rules. Personal Data Protection Law (PDPL) implementing regulation, Article 24: 72 hours after awareness when its harm/rights condition is met. Further facts, updates or scope qualification: These are separate scope and risk gates. Provide missing data-breach information as soon as possible with reasons; assess subject notice. SAMA also requires its specified post-restoration report. SAMA 121; CSF 3.3.15; PDPL regulation.
- South Africa: responsible party / financial institution. Trigger, recipient and initial timing: Protection of Personal Information Act (POPIA) unauthorised access/acquisition: regulator and identifiable subjects as soon as reasonably possible; operator tells responsible party immediately. Further facts, updates or scope qualification: Scoped financial-sector template, effective September 2026: 24 hours after material classification, impact update 14 calendar days after notice, final timing agreed with authority. As at 19 November 2026, Cybercrimes section 54's enacted 72-hour rule had not commenced. POPIA; Joint Notice; Annexure A cover; commencement.
- Nigeria: public/private system or network operator. Trigger, recipient and initial timing: Cybercrimes Act section 21: inform the national computer emergency response team immediately of a qualifying attack, intrusion or disruption liable to hinder another computer system or network. Further facts, updates or scope qualification: Open this reporting route independently of privacy and financial-sector reports, and use the applicable sectoral reporting channel. Cybercrimes Act 21.
- Nigeria: data controller / regulated financial actor. Trigger, recipient and initial timing: Nigeria Data Protection Commission (NDPC) within 72 hours of awareness where the rights/freedoms risk gate is met; high-risk subject notice immediately. Separate Central Bank of Nigeria (CBN) bank and virtual-asset (VA) incident rules apply. Further facts, updates or scope qualification: Deposit money bank and payment service bank detection report: 24 hours. Scoped VA report: 24 hours of awareness, immediate for specified serious/imminent threats, detailed follow-up 72 hours after initial notice. Do not treat routine reporting transitions as a general delay of incident duties. NDPA 40; CBN banking framework; CBN 2026.
- Brazil: General Data Protection Law (LGPD) controller. Trigger, recipient and initial timing: Relevant-risk personal-data incident: National Data Protection Authority (ANPD) and affected people generally three business days from knowledge that personal data were affected. Further facts, updates or scope qualification: Apply Article 5's risk criteria; justified supplemental ANPD information within 20 business days after initial notice; records for five years. Qualified small-agent treatment needs its own eligibility assessment. ANPD Resolution 15.
- Brazil: regulated financial / payment / VA institution. Trigger, recipient and initial timing: Timely Central Bank of Brazil (BCB) communication when a relevant incident or relevant outsourced-service interruption constitutes a crisis. Further facts, updates or scope qualification: Apply the institutional scope and documented crisis criteria. BCB 85 expressly includes authorised virtual-asset service companies (SPSAVs) from March 2026. For institutions authorised for foreign exchange (FX) and qualifying Article 29 §5 transition SPSAVs, the separate return covers their VA-service operations within BCB 277 from 3 November 2026, due by the fifth day of the month following the operation. This transaction return is separate from the incident report. CMN 4.893, Articles 1 and 20; BCB 85, Articles 1 and 20; BCB 552; BCB 277, Article 82-A.
- Mexico: private controller / IFPE. Trigger, recipient and initial timing: Significant patrimonial/moral-rights data harm: affected-person notice immediately. IFPE cyber notice to Banxico/the National Banking and Securities Commission (CNBV): immediately. Further facts, updates or scope qualification: IFPE follow-up five business days after identification; remediation plan 15 business days after the incident ends; specified affected-customer data notice 24 hours. Article 43 separately requires interruptions lasting at least 30 minutes to be reported within 60 minutes from occurrence and imposes customer-notice duties. Private-data Act 19; IFPE Articles 42–43.
- Australia: other incident routes. Trigger, recipient and initial timing: Security of Critical Infrastructure Act (SOCI) covered entity: as soon as practicable, within 12 hours for specified significant availability impact, otherwise within 72 hours for the qualifying relevant-impact branch. Further facts, updates or scope qualification: Oral reports have separate written follow-ups. APRA has scoped 72-hour incident duties and a 24-hour duty for a critical-operation disruption outside tolerance. Notify a known eligible privacy breach as soon as practicable; the 30-day provision governs assessment of a suspected breach. SOCI; CPS 234; CPS 230; Privacy Act.
- New Zealand: agency / prudential entity. Trigger, recipient and initial timing: Notifiable privacy breach: Privacy Commissioner and affected people as soon as practicable. Reserve Bank of New Zealand (RBNZ) material cyber incident: as soon as possible, within 72 hours after materiality is established. Further facts, updates or scope qualification: The privacy statute requires notice as soon as practicable; the Privacy Commissioner's 72-hour guidance informs that process. RBNZ scope is banks, non-bank deposit takers and insurers; as at 19 November 2026, the periodic all-incident survey was paused. Privacy Act; OPC explanation; RBNZ; FAQ question 2.
Australia's payment report follows the payer and the victim's awareness
Australia provides the clearest contrast between incident discovery and a completed payment. Under the ordinary-business branch, the prior financial year's turnover must exceed A$3 million. The ransomware payment reporting rules proportionately adjust that threshold for a business carried on for only part of the year. The branch excludes Commonwealth and State bodies and responsible entities for critical-infrastructure assets; a separate branch covers the responsible entity for an asset to which SOCI Part 2B applies. Applying only a simple revenue test can therefore produce the wrong answer. Cyber Security Act 26; Rules 6
If the covered company pays, its 72-hour clock runs from payment. If it becomes aware that the insurer or another actor paid on its behalf, the clock runs from that awareness. The file should establish who paid, when the company learned of it and how the act relates to the demand. A contract saying the intermediary will handle reporting should be tested against the statutory duty. No payment means this particular payment trigger does not arise, but privacy, infrastructure, sector and financial-crime reports may already be due.
The Cyber Security Act's information-use, privilege and admissibility protections apply within their statutory limits. Payment prohibitions and independently obtained evidence remain relevant. Cyber Security Act 28–32
Financial-crime reports can arise before any payment
An attempted, rejected or abandoned transaction can still be reportable. A covered US money transmitter's qualifying suspicious activity report generally has a US$2,000 threshold and a 30-calendar-day clock from initial detection of facts that may form a reporting basis. OFAC blocking and sanctions-rejection reports have a separate 10-business-day clock; commercial refusal alone does not trigger that sanctions report. Canadian reporting entities must submit a qualifying suspicious transaction report as soon as practicable after completing measures that establish reasonable grounds for suspicion, including sanctions-evasion suspicion. These duties can continue when a proposed payment is abandoned. US money-services rule; OFAC blocking reports; OFAC rejection reports; Canadian reporting rule. Apply each duty to its covered actor and suspicion threshold. In Singapore, the Payment Services Act (PSA) provider's prompt STR, the TSFA disclosure, the five-working-day PSN03 material suspicious-activity/fraud report and the technical incident report are separate routes. As at 19 November 2026, India's Prevention of Money-laundering (Maintenance of Records) Rules (PML Rules) require the principal officer to report promptly once satisfied the transaction is suspicious; the older seven-working-day formulation should not be used as a grace period. Singapore PSN02; PSN03; India PML Rules 8(2)
Nigeria adds a payment-adjacent condition with wider relevance: section 3 of the Money Laundering (Prevention and Prohibition) Act (MLPPA) requires a written report to the Nigerian Financial Intelligence Unit (NFIU), the CBN and Nigeria's Securities and Exchange Commission within one day for the specified international transfer exceeding US$10,000 equivalent. Funds include virtual assets. Establish the amount and international character from the actual parties and transfer route. The MLPPA's suspicious-transaction reports and the CBN's VASP suspicion clock are additional. MLPPA 3, 7, 30; CBN 26.9
Sanctions and terrorist-property information can require a separate report: EU Regulation 2019/796 Article 8 requires immediate compliance information to the designated national authority and transmission to the European Commission; Canada's Criminal Code section 83.1 requires qualifying property/transaction disclosure without delay to the Commissioner of the Royal Canadian Mounted Police or the Director of the Canadian Security Intelligence Service. In the UK, regulation 23 of the Cyber Sanctions Regulations requires a relevant firm's qualifying business-derived report to the Treasury as soon as practicable, and separately imposes the specified annual frozen-asset report on holders. EU Article 8; Canadian section 83.1; UK regulations 23–24
In the UAE, report designated assets within five working days from freezing under Article 15, and apply covered institutions' separate immediate supervisory duty under Article 21. SAMA-supervised financial institutions must provide the required sanctions-system feedback immediately and within 24 hours of receiving the relevant official notification, including a negative response. Australia and New Zealand distinguish ordinary suspicious reporting from particular terrorism/property routes. Keep protected STR information out of routine customer or attacker communications and follow the actual tipping-off rules. UAE Resolution 74, Articles 15 and 21; Saudi October 2026 circular; Australian AML Act 41; NZ AML Act 39A–41
Obtain the policy and distinguish consent from legal permission
The insurer should identify precisely what it is approving: the responder, negotiator, communications, cryptocurrency acquisition, payment, associated costs or later reimbursement. A panel appointment can cover only one of those acts. Obtain the full policy and endorsements, the insured entity and interests, governing law, extortion wording, notification/cooperation terms, emergency expense authority, limits, retention and relevant sanctions, illegality, war or terrorism exclusions.
Paying before required approval can create a coverage dispute. The consequence depends on the actual wording and applicable law. Several jurisdictions expressly qualify the effect of particular notice or conduct breaches; none of those provisions creates ransomware cover where the policy does not grant it.
- France. Insurance condition that can change the immediate response: Code des assurances L12-10-1 conditions indemnity for qualifying cyber-offence losses of legal persons and professional natural persons on a complaint to competent authorities within 72 hours after the victim learns of the attack. The condition covers qualifying cyber-loss indemnity generally; the complaint period runs from knowledge of the attack, independently of the payment decision. L12-10-1.
- Germany. Insurance condition that can change the immediate response: The Federal Financial Supervisory Authority's (BaFin) 01/2026 (VA) circular, effective 1 April 2026, addresses acceptable operation of direct ransom insurance, including cyber cover. Its conditions include immediate police reporting by the insured, trusted persons and insurer, confidentiality and central insurer handling. These are scoped insurance supervisory conditions; the actual policy and payment legality remain separate. BaFin circular.
- Australia. Insurance condition that can change the immediate response: Insurance Contracts Act section 54 can limit refusal based solely on a post-contract act/omission, subject to prejudice, causation and statutory qualifications. Assess the particular consent breach, resulting prejudice and causation against the actual cover. Section 54.
- New Zealand. Insurance condition that can change the immediate response: The 1977 Act, section 9, qualifies manner/time notice clauses by prejudice and inequity. The 2024 contract regime was not yet operative as at 19 November 2026. Analyse the separate payment-consent condition under the actual policy and its governing law. 1977 Act; reform status.
- South Africa. Insurance condition that can change the immediate response: Claim-handling protections under the Policyholder Protection Rules (PPR) have a defined policy scope, including a corporate size threshold. Where applicable, preserve proof of notice to the insurer or qualifying mandated handler, obtain the claim decision and reasons, and protect representation and litigation deadlines. These protections do not create ransom cover or dispense with required prior consent. PPR, Chapter 1 and Rule 17; 2018 amendment; threshold determination.
- Nigeria. Insurance condition that can change the immediate response: Use the Nigerian Insurance Industry Reform Act 2025 (NIIRA), including section 65's differentiated consequences of policy-condition/warranty breaches. Actual cover remains necessary. NIIRA.
- Brazil. Insurance condition that can change the immediate response: Law 15.040, operative from December 2025, requires prompt notice, useful/necessary mitigation and information. Articles 66–68 distinguish deliberate and negligent failures and protect incident evidence. Classify any proposed ransom expense under the policy and the applicable mitigation/expense provisions. Insurance Law.
- Mexico. Insurance condition that can change the immediate response: Insurance-contract Articles 66–69 provide the notice framework, generally a five-day outer period, differentiated consequences and relevant information rights. Apply the relevant consequence to the actual delay, prejudice and conduct. Insurance Act.
For the US, Canada, UK, Singapore, India, UAE, Saudi Arabia and South Africa, the actual policy, governing law and applicable local restrictions remain necessary to determine consent, exclusions and reimbursement. If the proposed insured route remains unresolved, a different proposal to use company funds without expected reimbursement requires an explicit, informed assessment of its authority, legality and commercial consequences.
Verify the intermediary's permitted service
Ask the proposed firm to describe each act it will perform. Negotiating a demand, arranging a transfer, buying tokens, taking custody, controlling keys and transmitting value can attract different rules. Classify those actual services under each relevant jurisdiction's licensing perimeter, including where the firm is a consultant, law firm or insurer-appointed vendor.
- US / Canada. What to establish before funding the provider: Analyse money transmission or virtual-currency business under the actual activity and nexus. The US Financial Crimes Enforcement Network (FinCEN) expressly addresses ransomware intermediaries; Canadian foreign money services business coverage can turn on directed Canadian business. Required registrations, local permissions and financial-crime controls are distinct. FinCEN; US definition; PCMLTFA.
- EU / UK. What to establish before funding the provider: MiCA authorisation or the limited Article 60 institution/service route must fit the service. The maximum legacy-provider transition ended 1 July 2026. An EU originator's crypto-asset service provider must also satisfy the Transfer of Funds Regulation's (TFR) applicable transfer-information and verification requirements before initiating or executing the transfer. TFR Article 14. UK AML registration has its own business-in-the-UK test. Establish that connection and apply the permission route in force before relying on a later broader crypto regime. MiCA 59–60, 143; FCA guidance.
- Singapore. What to establish before funding the provider: PSA licensing can reach arranging digital payment token (DPT) transmission without receiving the tokens. PSN02 restricts proceeding where required CDD or transfer information cannot be satisfied, subject to its actual provisions. Pure negotiation and regulated arranging must be distinguished on the facts. Section 137 of the Financial Services and Markets Act (FSMA) also requires licensing for covered digital-token-service business outside Singapore: individuals and partnerships operating from a Singapore place of business, and Singapore corporations (including limited liability partnerships) operating from Singapore or elsewhere, subject to its exclusions. PSA 5 and First Schedule; PSN02 6, 13, 16; FSMA 137.
- India. What to establish before funding the provider: Notified virtual digital asset (VDA) activities for another person can require Financial Intelligence Unit (FIU) reporting-entity registration and controls. Separately classify each Indian outward-payment leg under the Foreign Exchange Management Act (FEMA) and establish the applicable authorised-dealer route and any specifically required permission. The resident-individual US$250,000 Liberalised Remittance Scheme (LRS) allowance is unavailable to a corporate payer. The FIU's January 2026 guidelines require the specified transfer information before or with the transfer and reject post-facto completion. FIU VDA guidance; FEMA; RBI LRS eligibility.
- UAE. What to establish before funding the provider: Separate federal AML/targeted financial sanctions (TFS), VARA, DIFC/DFSA, ADGM/FSRA and onshore Central Bank of the UAE (CBUAE) permissions. CBUAE Article 2 restricts permitted token-service transfers and expressly operates despite a Securities and Commodities Authority (SCA) or local VA licence. Its financial-free-zone exclusion and the genuine technical-service exclusions require their actual facts. Establish the onshore CBUAE permission independently of any VARA licence. CBUAE Article 2 and definitions; VARA.
- Saudi Arabia. What to establish before funding the provider: Establish the actual payment-service permission and applicable SAMA framework. AML Article 10 prevents the wire transfer where the required originator/beneficiary information cannot be obtained. No generic lawful Saudi VASP route should be inferred from a provider's willingness to act. Payment framework; AML law.
- South Africa / Nigeria. What to establish before funding the provider: South African CASP accountable-institution duties and Financial Advisory and Intermediary Services (FAIS) permissions follow the service. Nigeria's November 2026 non-security VA regime has specific licences, cross-border permissions and conditional existing-operator transitions; securities require their own classification. FIC/FSCA; CBN 2026.
- Brazil. What to establish before funding the provider: BCB 520/589 distinguishes authorisation, an existing provider's permitted continuation and what regulated counterparties may facilitate. The operative Article 91 restriction applies from 6 November 2026 and has express-exception wording. Verify whether the actual provider and counterparty fall within a permitted continuation or an express exception. BCB 520; 589. Also classify the actual service under the FX rules: Article 76-A restricts moving funds for a third party through covered VA services, with a specified exception for service to an FX-authorised institution acting for clients. Provider-class limits, residency, self-custody identification and purpose information also matter. An insurer-funded route needs this separate assessment. BCB 277, Articles 29 and 76-A–C.
- Mexico. What to establish before funding the provider: Professional client exchange, custody and transfer can enter the vulnerable-activity regime of the federal anti-money laundering law (LFPIORPI); bank and financial technology institution (ITF) crypto permissions have separate limits. AML registration does not itself create a financial-service licence. Apply the 2025 amendments and their actual transition conditions. An IFPE must also check the regulator authorisation/advance-notice requirements for a responder with specified data or system access. IFPE Articles 44–45; LFPIORPI; Banxico Circular 4/2019.
- Australia / New Zealand. What to establish before funding the provider: Apply Australia's expanded service perimeter and required VASP/remittance registration, including any proven transition. New Zealand service/product permissions and AML classification depend on activity; the Department of Internal Affairs (DIA) became the sole AML and counter-terrorist-financing supervisor on 1 July 2026. Apply the continuing obligations under the correct supervisor. Australian AML Act; FMA guidance.
The engagement should identify the actual paying entity, who owns or controls assets at each stage, all subcontractors, required records and the process for notifying the victim of an on-behalf payment. It should also identify circumstances requiring a stop: a prohibition or freeze, missing required permission, failed mandatory CDD or transfer information, or a material change in recipient or route. After a rejected transaction, reassess the legal restriction, missing information and proposed route before issuing further instructions.
Make the board decision specific and preserve the evidence
Corporate authority comes from the applicable company law, constitutional documents and valid delegations. Identify the distinct powers of the chief executive, insurer and incident commander. The board or authorised officer should receive a concise record of the lawful options, technical recovery evidence, safety/service/customer consequences, costs and uncertainties, insurance position, recipient assessment, provider permissions and reporting status.
The governing-law examples differ: Delaware's management provisions, the Canada Business Corporations Act (CBCA), Germany's GmbH rules, South Africa's Companies Act, Nigeria's Companies and Allied Matters Act (CAMA), Brazil's corporation statute, Mexico's General Law of Commercial Companies (LGSM) and Australian and New Zealand company laws have their own entity and authority conditions. DORA and Germany's BSIG also impose scoped management oversight obligations. The decision remains subject to the applicable payment prohibitions. DGCL; CBCA; GmbHG; South Africa Companies Act; CAMA; Brazil Law 6.404; LGSM; Australian Corporations Act; NZ Companies Act
Privilege requires a separate, local assessment. Define counsel's client, legal purpose, any genuinely anticipated proceedings and necessary recipients. Preserve ordinary factual evidence even if the resulting legal advice is protected. Assess each report's purpose, author, client and recipients under the applicable privilege rule, including documents commissioned through an insurer.
India's Supreme Court addressed the limits of in-house counsel protection in 2025 INSC 1275, paragraph 67(4)–(4.1). France's November 2026 decree starts the substantive in-house consultation confidentiality regime on 1 January 2027, despite earlier commencement of specified ethics/training provisions. Germany's criminal-procedure protection has an express Syndikus qualification. Those differences prevent a worldwide assumption about in-house incident files. Indian judgment; French decree, Article 12; German StPO 53 and 97
Keep original threat messages and headers, native logs, lawfully acquired forensic images, access and custody records, wallet and transaction evidence, notices and approvals. Record the source and limits of attribution and distinguish observation from inference. If urgent remediation changes or destroys evidence, record why, what was preserved first and who acted. Brazil's insurance law and Mexico's criminal-procedure custody rules illustrate how preservation can affect more than a later technical investigation. Brazil Article 68; Mexico CNPP 227–228
Pre-decision legal file
Before a payment proposal reaches an approver, assemble:
- Entities and legal connections: exact victim, fund owner, insurer and providers; location, licences, infrastructure/data roles and transaction path.
- Incident chronology and reports: separate awareness/classification/payment clocks, legal thresholds, recipients, filed facts, unknowns, updates and receipts.
- Recipient assessment: available identities, wallets, ownership/control and terrorist-purpose evidence, screening results and limitations, contradictory facts and any required permission.
- Policy and consents: full wording, exclusions, insured interests, panel scope, written vendor/negotiation/payment approvals and reimbursement conditions.
- Provider permissions and mandate: exact services, licence/registration or valid transition, CDD/transfer controls, custody, subcontractors and on-behalf reporting arrangements.
- Recovery alternatives: validated backups, restoration tests, lawful decryption options, continuity/customer measures and residual data-disclosure risk.
- Authority and reasons: constitutional/delegated powers, conflicts, financial limit, alternatives, grounds for the choice and conditions that require renewed approval.
- Evidence and confidentiality: originals, collection and custody record, legal mandate, access restrictions, disclosure decisions and applicable retention periods.
Use an approve, defer or prohibited decision tree
The following is a proposed governance workflow. Each legal test must be answered under the applicable jurisdiction and facts.
- Preserve evidence and start reports. Next: contact or payment being considered?
- Contact or payment being considered? No: no contact or refuse; execute recovery plan. Yes: does a prohibition or binding hold bar the act?
- Does a prohibition or binding hold bar the act? Yes: valid permission covers every relevant restriction? No: material facts and legal conditions established?
- Valid permission covers every relevant restriction? No: PROHIBITED route; do not perform the act. Yes: material facts and legal conditions established?
- Material facts and legal conditions established? No: DEFER; name missing evidence and owner. Yes: provider, corporate and required contract approvals complete?
- Provider, corporate and required contract approvals complete? No: DEFER; name missing evidence and owner. Yes: informed decision supports the defined act?
- Informed decision supports the defined act? No: no contact or refuse; execute recovery plan. Yes: APPROVE defined act with limits and rechecks.
- PROHIBITED route; do not perform the act. Next: continue reporting, recovery and customer protection.
- DEFER; name missing evidence and owner. Next: continue reporting, recovery and customer protection.
- No contact or refuse; execute recovery plan. Next: continue reporting, recovery and customer protection.
- APPROVE defined act with limits and rechecks. Next: continue reporting, recovery and customer protection.
Prohibited means the proposed route is barred and no valid applicable permission covers it. An application for a licence, regulator silence or insurer consent is not the permission. A different proposal must be assessed afresh; it cannot be used to evade the restriction.
Defer means a material recipient/control issue, legal connection, required permission, provider condition or authority remains unresolved. Identify the exact missing item and who will obtain it. A pending insurance decision can defer the proposed insured route. A proposal using company funds requires a separate legal, contractual and authority assessment. Reports and recovery continue during the deferral.
Approve means the authorised decision maker approves a precisely defined act after the applicable legal and contractual conditions have been addressed and the recovery/insurance consequences understood. Record the entity, mandate, limit, conditions and expiry. Recheck a changed wallet, beneficiary, intermediary or instruction before acting. Record the remaining uncertainty about restoration, disclosure and reimbursement in the decision.
Make refusal and no contact workable outcomes
A no-payment decision should activate a practical restoration and customer-protection plan, with owners and milestones. Preserve incoming demands without responding where no contact is chosen. Validate clean backups and any available lawful decryption assistance, maintain critical services safely, assess affected-person communications, and keep each report and update on its own clock. Treat deletion claims as unproven and validate restored systems before returning them to service. FBI ransomware guidance; Canadian Cyber Centre playbook; NZ cyber-ransom advice
If tracing identifies assets and an effective legal forum, counsel can assess lawful preservation, disclosure and recovery. The claimant, property interest, cause of action, evidence and jurisdiction must support the remedy. Licentium's analysis of crypto-asset recovery after a Nigerian company's treasury theft addresses that separate recovery decision. Where the incident also affects a distributed software product, the Cyber Resilience Act reporting analysis for AI SDKs in EU fintech apps explains the product-role assessment alongside financial-sector and privacy reporting.
Review the payment route and controls
For a scoped review of the financial-crime controls around a proposed payment arrangement, provide the entity and service map, policy and consent records, incident chronology, recipient evidence and provider mandate. Licentium's AML / KYC & Financial-Crime Programs describes its work on sanctions controls, customer due diligence, transaction monitoring and governance. The review should produce a documented lawful route or a clear reason the proposed act cannot proceed.