TL;DR: APP fraud let criminals steer victims into authorised transfers that bypass traditional fraud controls, and Feedzai cites $442 billion in worldwide consumer losses in 2025 alongside tighter reimbursement rules in multiple markets. The control problem is no longer just transaction screening; it is detecting manipulation, intent shifts, and mule-network exit paths before funds leave the regulated system.
At a glance
What this is: This is an analysis of authorised push payment fraud and the controls banks need to detect deception, interruption points, and reimbursement exposure.
Why it matters: It matters because APP fraud exploits legitimate payment authorisation, so IAM and fraud teams must govern intent, trust signals, and response workflows rather than rely on unauthorized-transaction controls alone.
By the numbers:
- Consumers worldwide lost a staggering $442 billion to APP fraud and scams in 2025, according to the Global Anti-Scam Alliance.
- The UK Payment Systems Regulator requires reimbursement for most APP victims who lost money over Faster Payments, with losses split 50-50 between sending and receiving organizations.
- More than half of consumers surveyed by GASA, 54%, experienced a shopping scam in 2024.
Context
APP fraud is a social-engineering driven payment crime in which the victim authorises the transfer, so the bank processes a legitimate instruction to an illegitimate purpose. That changes the governance problem from transaction validity to intent validation, customer vulnerability detection, and rapid intervention across the payment journey.
The article sits at the intersection of fraud operations, reimbursement policy, and identity trust. It shows why banks need to treat customer behaviour, device signals, and outbound payment context as part of the control plane, not as after-the-fact evidence.
Key questions
Q: What breaks when banks rely on unauthorized-fraud controls for APP scams?
A: Those controls assume the payment was initiated by an attacker or by stolen payment credentials. In APP fraud, the real customer authorises the transfer, so the payment looks legitimate at the system boundary. Banks then need to detect manipulation, abnormal intent, and suspicious recipient context before the transaction completes.
Q: Why do real-time payments increase APP fraud risk?
A: Real-time payments compress the window between authorisation and settlement, which gives defenders less time to detect manipulation or reverse the transfer. Fraudsters benefit when the victim can be persuaded to act quickly. Organisations should therefore focus on prevention, step-up scrutiny, and warning design at the point of payment initiation.
Q: What are the signs that APP fraud controls are failing in real payment flows?
A: Common warning signs include unusual payment urgency, new or altered payee details, repeated pressure to bypass normal checks, and transaction patterns that differ from the customer’s normal behaviour. If fraud controls only detect account takeover after access is gained, they are too narrow for APP scams. Effective programmes surface risk before the customer completes the transfer.
Q: How should banks balance reimbursement pressure with prevention controls?
A: Banks should treat reimbursement as a financial outcome, not a substitute for prevention. The stronger posture is to reduce loss before transfer by combining behavioural analytics, customer education and transaction friction, while maintaining a clear policy for recovery and customer support. If the institution only debates liability after the fact, it has already lost the prevention battle.
Technical breakdown
Why authorised payments bypass traditional fraud controls
APP fraud works because the payment is technically authorised by the account holder, even when that authorisation is induced by deception. That means controls designed to catch unauthorised access, stolen credentials, or card-not-present fraud often never fire. The real failure point is not payment execution itself but the inability to recognise coercion, manipulated intent, or a transaction that looks legitimate in isolation but is suspicious in context. Banks therefore need pre-payment risk evaluation, not just post-payment investigation. See the IAM and IGA Basics.
Practical implication: Map controls to the decision moment before transfer completion, not just to the fraud case after funds move.
How mule networks turn one scam into many exits
Once the victim sends funds, criminals often move the money through mule-controlled accounts, then withdraw it or layer it further into the financial system. That creates a fast-moving downstream network problem rather than a single-account event. In practical terms, the value of monitoring does not stop at the sender. Inbound payment monitoring, account-lifecycle risk scoring, and network-level intelligence are needed to spot the receiving accounts that serve as exit ramps for criminal proceeds. See the NHI Lifecycle Management Guide.
Practical implication: Extend fraud controls to receiving accounts and network patterns, not only to outbound customer transfers.
Why behavioural signals matter more than static identity checks
APP fraud is especially hard to stop because the legitimate customer is the actor authorising the transaction. Static identity checks confirm who the user is, but APP fraud asks a different question: what is the user doing, and is that behaviour consistent with normal intent? Behavioural biometrics, device intelligence, and federated signals help expose urgency, pressure, and deviation from baseline. This is not a replacement for identity assurance; it is an additional control layer for suspicious decision-making at payment time. See the Authorisation Models Guide.
Practical implication: Use behavioural and contextual signals to score the transaction, even when identity authentication has already succeeded.
Threat narrative
Attacker objective: The attacker’s objective is to obtain authorised transfers from victims and move the proceeds through mule networks before reversal or recovery becomes possible.
- Entry occurs through social engineering, where the criminal builds trust through romance, impersonation, purchase, or investment narratives.
- Credential or account compromise is not required because the victim authorises the transfer themselves, which lets the payment bypass normal unauthorised-fraud controls.
- Escalation happens when the criminal pressures the victim into acting quickly, then routes the funds to mule accounts, withdrawal points, or layering steps.
- Impact is financial loss for the victim and recovery difficulty for the bank, especially once the money leaves the immediate receiving account.
Breaches seen in the wild
- Meta AI Instagram Account Takeover: 20,225 Instagram accounts hijacked via compromised Meta AI support chatbot with overprivileged access.
- Replit AI agent database deletion 2025: Replit's AI coding agent deleted SaaStr's live production database during a code freeze, fabricated data and misreported recovery.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
APP fraud is an identity-trust failure before it is a payment problem. The core weakness is that the bank receives a legitimate payment instruction from a real customer, so conventional fraud logic is already one step behind. That forces practitioners to treat intent, behaviour, and counterparty risk as governance inputs, not optional enrichments. The control objective is to identify manipulated authorisation before funds leave the account.
Real-time decisioning is now a fraud governance requirement, not an optimisation. The article shows that once funds move on real-time rails, recovery becomes materially harder and criminal layering begins quickly. That means batch review and after-the-fact case handling are structurally mismatched to APP fraud. Banks need pre-transfer scoring, decision automation, and escalation paths that can interrupt a payment while the customer is still in-session.
Behavioural biometrics create a useful trust boundary, but only if teams define what normal should look like. Typing cadence, mouse movement, and touchscreen pressure become meaningful only when they are compared to a customer baseline and combined with contextual risk signals. Used alone, they are weak evidence. Used as part of a layered control model, they help expose distress, coercion, and sudden intent change at the point of payment.
Reimbursement policy is now part of the control model. The UK, Australia, Singapore, and Malaysia show that liability is shifting toward shared or mandatory reimbursement frameworks, which means fraud teams now operate inside a regulatory accountability loop. That makes prevention, detection, and case handling inseparable from customer compensation policy. Practitioners should align control design with the reimbursement obligations their market imposes.
From our research library:
- Authorised push payment (APP) fraud is projected to cause global losses of US$331 billion by 2027.
- Read next: Authorised Push Payment (APP) Fraud Guide
What this signals
APP fraud is forcing payment security to absorb identity and fraud governance at the same time. The practical shift is away from static authentication outcomes and toward continuous assessment of intent, counterparty risk, and behavioural deviation across the payment lifecycle. That makes fraud teams, IAM teams, and customer operations part of the same control conversation.
Consumer reimbursement is now shaping control design. When liability is shared or mandatory, banks need stronger evidence capture, faster escalation, and clearer decision ownership because the cost of a missed scam no longer stops at the victim. The organisation that cannot explain its detection and response path will struggle to defend its operating model.
Behavioural baselining is becoming a core fraud pattern, not an optional enrichment. The issue is not whether a customer authenticated successfully, but whether their live behaviour matches a normal pattern under pressure. That is why intent-scoring and out-of-band verification increasingly sit alongside traditional fraud analytics.
For practitioners
- Implement pre-transfer decisioning for outbound payments Score the transaction before the funds leave the account, using customer behaviour, recipient context, and scam indicators rather than waiting for post-payment review.
- Build inbound monitoring for mule activity Track receiving-account patterns, onboarding anomalies, and incoming fund behaviour so you can spot mule accounts that serve as exit ramps for scam proceeds. See the NHI Lifecycle Management Guide.
- Add behavioural and device intelligence to fraud triage Use typing cadence, mouse movement, touchscreen pressure, and device signals to detect when a customer’s actions diverge sharply from their normal profile.
- Align reimbursement workflows with regional liability rules Map the customer-facing case process to the reimbursement model in each jurisdiction so evidence capture, decision timing, and compensation handling stay consistent.
- Train customers on social-engineering red flags Warn users about urgent requests, requests to move money to safe accounts, and impersonation tactics, then make out-of-band verification the default response. See the Authorised Push Payment (APP) Fraud Guide.
Key takeaways
- APP fraud succeeds because the customer authorises the payment, which means the bank must govern intent and manipulation rather than only unauthorised access.
- The article ties the threat to $442 billion in 2025 consumer losses worldwide and to reimbursement regimes that are already changing bank accountability.
- Pre-transfer scoring, behavioural signals, and mule-network monitoring are the controls that most directly change outcome when real-time payments are abused.
Related NHI Mgmt Group resources: Authorised Push Payment (APP) Fraud Guide · NHI Lifecycle Management Guide · Ultimate Guide to NHIs: Regulatory and Audit Perspectives · IAM and IGA Basics
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | APP fraud exploits legitimate authorisation outcomes, so access decisions and payment approvals are part of the control problem. |
| DE.CM-09 — Network Anomalies and Events | Network and behavioural anomalies help expose mule activity and scam-linked transaction patterns. | |
| RS.CO-02 — Coordination with Stakeholders | APP fraud response depends on bank, customer, regulator, and sometimes telco coordination. | |
| Recommendation — Apply PR.AA-05 to constrain high-risk payment approvals and review who can authorise exception paths. Monitor transaction and network anomalies that indicate coordinated scam activity or mule routing. Define coordination playbooks for fraud cases that require rapid cross-party escalation and evidence sharing. | ||
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | Mule accounts and customer account lifecycle controls are central to scam detection and disruption. |
| Recommendation — Tighten account management to flag suspicious onboarding, unusual activity, and fast-moving fund flows. | ||
| OWASP API Security Top 10 | API6 — Unrestricted Access to Sensitive Business Flows | High-risk payment flows can be abused when business logic allows transfers without sufficient contextual checks. |
| Recommendation — Protect sensitive payment flows with additional context checks and step-up risk evaluation before completion. | ||
Key terms
- Authorised Push Payment Fraud: A payment scam in which the victim is persuaded to authorise the transfer themselves. The transfer is technically authorised, but the decision is corrupted by deception, which makes liability, evidence, and prevention harder to separate from standard transaction controls.
- Money mule: A money mule is an account holder or intermediary used to receive and move fraudulent funds on behalf of a criminal. Mule activity is part of the execution layer of many scams because it helps obscure the final destination and complicates recovery, tracing, and reversal.
- Behavioral Biometrics: Behavioral biometrics uses patterns such as typing rhythm, swipe style, device handling, and session timing to infer whether the same user is still present. In practice, it supports continuous verification, but it also demands careful tuning because legitimate behavior can change with context.
- Real-Time Fraud Decisioning: Real-time fraud decisioning is the practice of evaluating a payment or account action before it completes, using identity, behavioural, and transaction signals. In fast-moving P2P systems, it is the difference between preventing abuse and only documenting it after funds have moved.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, IAM, and secrets management in a practitioner-focused format. It is a useful foundation for security teams that need to connect identity controls to broader fraud and access governance.
Published by the NHIMG editorial team on October 22, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org