APP Fraud and How Confirmation of Payee Helps
Most fraud controls are designed to stop payments the customer never made. Authorised push payment fraud is different and harder, because the customer did make the payment. They were deceived into sending money to a criminal, believing they were paying someone legitimate. Because the payment is genuinely authorised, many traditional defences do not trigger. This post explains what APP fraud is, why it is so difficult to prevent, and how Confirmation of Payee, a name-checking control, meaningfully reduces one of its most common forms.
What APP fraud is
In an authorised push payment, the account holder instructs their bank to push money to another account. APP fraud is when that instruction is the product of deception. The victim is manipulated into authorising a transfer to an account controlled by, or feeding, a criminal. Because the customer entered their own credentials and approved the payment, the transaction looks legitimate to authentication systems.
Common variants include:
- Impersonation scams, where the fraudster poses as a bank, a government body, or a trusted company and pressures the victim to move money to a supposedly safe account.
- Invoice and mandate scams, where a genuine payment is redirected by altering the payee details, often after a business email is compromised.
- Purchase scams, where the victim pays for goods or services that never arrive.
- Romance and investment scams, which build trust over time before extracting payments.
What unites them is that the fraud targets the human, not the technology. The payment rail works exactly as intended.
Why APP fraud is hard to stop
Conventional fraud detection leans heavily on signals that a payment is unauthorised: an unrecognised device, a login from an unusual location, credentials that do not match. In APP fraud, none of those help, because the legitimate customer is the one authorising the payment from their own device. The intent is manipulated, but the mechanics are clean.
Two structural features make it worse. First, instant-payment rails settle quickly and often irrevocably, so there is little time to intervene and little chance of recovery once the money moves. Second, criminals rapidly move funds through mule accounts, layering the transfer so that tracing and recovery become difficult. The combination means prevention is far more valuable than after-the-fact recovery.
How Confirmation of Payee helps
One of the most effective interventions attacks a specific weakness in the payment process: the fact that, historically, payments were routed on account number and sort code alone, and the payee name was never actually checked. A fraudster could tell a victim to pay an account under any name they liked, and the system would not notice the mismatch.
Confirmation of Payee (CoP) closes that gap. Before a payment is sent, the payer's bank checks the name the payer entered against the name registered on the destination account, and returns one of a few outcomes:
- Match: the name matches the account, giving the payer reassurance.
- Close match: the name is similar but not exact, prompting the payer to check details.
- No match: the name does not match, a clear warning sign that the payer should stop and verify.
This directly disrupts impersonation and invoice-redirection scams, because the account the fraudster wants the money sent to is almost never registered in the name the victim expects. A stark no-match warning at the moment of payment gives the victim a concrete reason to pause.
What CoP does and does not do
Confirmation of Payee is a strong control, but it is not a complete answer, and it is important to be clear about its limits.
| CoP helps with | CoP does not solve |
|---|---|
| Misdirected payments to the wrong account | Scams where the victim knowingly pays the criminal's own named account |
| Impersonation and invoice-redirection fraud | Social engineering that persuades a victim to ignore a warning |
| Simple payee-name mismatches | Purchase scams where goods simply never arrive |
A determined fraudster can coach a victim to disregard a no-match result, and some scams do not depend on name mismatch at all. CoP raises friction at the right moment, but it works best as one layer among several.
Layering CoP with monitoring
Because CoP is a point-of-payment check, it complements rather than replaces real-time transaction monitoring. Monitoring looks at behaviour and context: is this payment unusual for this customer, is the destination account showing mule-like patterns, is the velocity abnormal? A modern anti-fraud posture combines both, a name check at the moment of payment and continuous behavioural monitoring across the rail.
Open, real-time monitoring platforms make this practical. Tazama, for instance, is an open-source real-time fraud and AML monitoring platform designed for high volumes, and it can evaluate typologies that flag mule-like receiving accounts and abnormal flows. At KibiPay we run Tazama across our rails so that behavioural signals sit alongside point-of-payment controls like payee verification. Neither layer alone is sufficient; together they are far stronger.
The most reliable time to stop APP fraud is before the payment leaves, which is exactly where a payee-name check and real-time monitoring both operate.
Building for prevention
For builders, the design implication is to intervene early and clearly. Surface name-check results prominently, use plain-language warnings, and make it easy for a hesitant payer to stop. Pair that with monitoring that can identify suspicious receiving accounts and unusual flows. And design for the reality of instant settlement, where the window to act is small and recovery is unlikely.
Takeaway: APP fraud is hard precisely because the victim authorises the payment, which neutralises many traditional defences. Confirmation of Payee is one of the strongest available countermeasures because it checks the payee name at the decisive moment, but it works best layered with real-time behavioural monitoring and clear, well-timed warnings.