Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Authorised Push Payment Fraud
Threats, Abuse & Incident Response

Authorised Push Payment Fraud

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Threats, Abuse & Incident Response

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.

What authorised push payment fraud actually exploits

Authorised push payment fraud works because the payment rail is being used as intended, but the human decision to approve the transfer has been manipulated. That makes it different from unauthorised card or account theft, and it is why controls must address both payment execution and the credibility of the instruction itself.

In practice, the scam often blends social engineering, impersonation, urgency and trust abuse. The victim may believe they are paying a supplier, resolving an emergency, protecting an account, or helping a trusted contact, so the transfer is “authorised” in form even though the intent was engineered by deception.

Why APP fraud is difficult to separate from normal payment control

APP fraud sits in the gap between fraud prevention and payment authorisation. Standard controls such as beneficiary setup, dual approval, or transaction limits can reduce risk, but they do not fully solve the problem when the user has already been convinced that the payment is legitimate.

That is why APP fraud is often assessed through the lens of behavioural verification, payee intelligence, and friction at the point of high-risk transfer. A control can be technically working and still fail to stop the scam if the false narrative is convincing enough to override the user’s judgment.

Resources that help explain the broader fraud patterns include Top 10 Online Fraud Attacks and Payment Fraud Guide, which place APP scams alongside related payment abuse and control failures.

Common attack patterns and why they succeed

APP fraud commonly uses business email compromise, bank impersonation, invoice redirection, romance scams, investment scams, and deepfake-enabled executive impersonation. The technique matters less than the social outcome: the victim is pushed into a payment decision under time pressure, authority pressure, or emotional pressure.

These scams succeed because they exploit normal organisational and personal habits, such as trusting familiar names, relying on email alone, or treating a prompt payment request as routine. Once the victim authorises the transfer, recovery becomes harder because the payment often looks valid from the banking system’s perspective.

The danger is especially clear in cases like deepfake-led impersonation, where the fraudster uses synthetic voice or video to strengthen the illusion of legitimacy. That kind of manipulation is a strong reason to treat “authorised” as a legal and procedural state, not as proof that the instruction was sound.

Prevention, detection and response after a suspected scam

Effective prevention focuses on verification paths that do not depend on the same channel used to deliver the payment instruction. Callback checks, out-of-band confirmation, payee name matching, and elevated scrutiny for urgent or unusual transfers all help reduce exposure, especially when supplier details or account information change unexpectedly.

Detection is usually strongest when organisations look for abnormal payment timing, first-time beneficiaries, pressure language, changes to bank details, or repeated failed verification attempts. After suspected APP fraud, speed matters because recall options, bank reports, and internal escalation may improve recovery chances if action is taken quickly.

For readers looking for practical sector guidance, the Authorised Push Payment (APP) Fraud Guide, Deepfake CEO Fraud Response Playbook, and Invoice Redirection and Supplier Bank Detail Fraud Guide map directly to the most common scenarios.

Liability, evidence and the identity impact of compromise

APP fraud creates awkward questions about liability because the payment was authorised, but the authorisation was induced by deception. That makes evidence collection important: the bank trail, message history, call recordings, change requests, and verification logs can all matter when assessing what happened and whether controls were followed.

Where the scam involved impersonation, account compromise, or supplier detail tampering, the identity impact may extend beyond the payment itself. Teams may need to review inbox access, payment approver accounts, supplier master data, and any credentials or sessions that enabled the fraudulent instruction or concealment.

Related references such as Top 10 Email Security Threats and Business Email Compromise and Fraud Statistics Guide are useful when the scam is delivered through compromised messaging or executive impersonation.

Risk and Threat Considerations

APP fraud is risky because it turns trusted payment workflows into an attack surface. The core exposure is not a broken transfer system, but a broken decision, so prevention is hard when fraudsters can convincingly fake authority, urgency or legitimacy.

Failure mechanism: The attacker manipulates the victim into authorising a transfer to the wrong beneficiary, often by impersonation, social pressure or a false business narrative, and the bank processes a payment that appears legitimate on its face.

Impact: Funds can leave the organisation or individual quickly, recovery becomes time-sensitive, and the resulting dispute may hinge on evidence quality, verification discipline and whether compensating controls were actually used.

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 SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementAPP fraud often requires account and approval governance around payment access.
IA-5 — Authenticator ManagementFraudulent instructions may rely on compromised mail or payment credentials.
Recommendation — Review payment approver accounts and remove unnecessary approval paths. Rotate and protect credentials used in payment and supplier-change workflows.
CIS Controls v8CIS-5 — Account ManagementAPP fraud prevention depends on controlling who can approve and change payees.
Recommendation — Restrict and periodically review access to payment approval and beneficiary change functions.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication, and Access ControlThe term involves authorised actions that need stronger access and verification controls.
Recommendation — Apply stricter authentication and approval checks for high-risk payment actions.
OWASP API Security Top 10API5 — Broken Function Level AuthorizationPayment-authorisation abuse maps to ensuring only approved functions can execute payments.
Recommendation — Enforce function-level restrictions on payment initiation and payee changes.

Practitioner Guidance

Why practitioners should care: APP fraud is one of the few payment fraud types where the control failure can occur even when the transaction workflow itself is functioning correctly. That means finance, banking, and security teams need shared ownership of verification behaviour, not just payment-system configuration.

Governance implication: Set clear rules for callback verification, beneficiary change approval, high-risk payment review, and escalation when urgency or impersonation appears. The most effective programmes treat payment approval as a governed human process, not only a system control.

Practitioner takeaway: If the payment request arrived through the same channel that is asking for the money, assume the instruction itself needs independent verification.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org