Tool 26 · Fraud & Risk
Interactive reference for Authorised Push Payment fraud typologies, regulatory obligations, and control frameworks across UK, EU, US, and AU. Filter by jurisdiction and fraud type.
What this tool simulates: This tool models the liability allocation process for Authorised Push Payment (APP) fraud and Unauthorised Account Takeover (ATO) fraud claims under three regulatory regimes. It maps user inputs — jurisdiction, fraud type, vulnerability, and bank interventions — to simulated liability splits using transparent JavaScript conditionals. All output is illustrative and uses mock regulatory frameworks based on publicly available guidance.
Target audience: Payments operations teams, compliance officers, fintech product managers, and fraud analysts learning how liability rules apply across jurisdictions. This tool is designed for training, planning, and internal reference — not for determining liability in live fraud cases.
UK PSR 2026 simulation basis: The UK Payment Systems Regulator's APP fraud reimbursement rules (effective October 2024, updated 2025–2026) require mandatory reimbursement up to £85,000 for most APP scams. Liability is split 50/50 between sending and receiving PSPs as a default, adjusted by whether Confirmation of Payee was implemented, whether the customer is vulnerable, and whether the customer ignored explicit warnings. The tool models these adjustments using hardcoded conditional rules.
US Reg E simulation basis: Regulation E (12 CFR Part 1005) covers unauthorised electronic fund transfers. For authorised push payment scams, Reg E protection is limited — the customer authorised the payment, so the sending bank typically bears minimal liability unless there was clear negligence. Error resolution deadlines: customer must report within 60 days of statement; bank must investigate within 10 business days.
EU PSD2 simulation basis: PSD2 Article 73 requires PSPs to refund unauthorised payment transactions "immediately." For authorised transactions (APP scams), PSD2 provides less protection — liability follows whether strong customer authentication (SCA) was applied. The EU is implementing additional APP fraud protections under the Instant Payments Regulation (2024) with verification of payee obligations.
Decision logic: All liability splits are computed using transparent if/else conditionals in JavaScript — no machine learning, no external API. The "Logic Trace" section in the output documents every conditional branch taken for a given input set.
Data privacy: This tool simulates liability decisions using mock scenarios. No real fraud claims, customer data, account information, or PII is processed or transmitted. All processing happens locally in your browser.
Source: Built by AINumbers.co · Tool 26 · MIT License.