The Four Verdict Problem
A difficult claim rarely produces one verdict. It produces four. Collapse them together and reimbursement pressure starts rewriting the facts.
Fraud
Did an APP scam actually occur? This is a classification question.
Scheme
Does the customer and payment fall within the mandatory reimbursement regime?
Consumer conduct
Can the Consumer Standard of Caution exception lawfully be established?
Defensibility
Would the complete handling remain defensible if independently reviewed?
Never use the answer to one verdict as a shortcut to another.
A genuine scam can involve a payment outside the mandatory rules. An in-scope victim can act carelessly without the firm proving gross negligence. A correct calculation can coexist with a complaint about prevention or warning quality. Some genuine commercial activity does not automatically make a claim a civil dispute.
Six gates, in order
Do not start with “should we refund?” Start with “what event are we dealing with?” The sequence prevents a desired payment outcome from contaminating classification.
Classify the event
Separate APP scam, unauthorised fraud, civil dispute and other payment problems. Record the basis, not merely the label.
Establish scheme scope
Test customer, account, payment system, geography, payment date and reporting date. Faster Payments and retail CHAPS rules have applied since 7 October 2024. The FPS definition covers individuals, qualifying microenterprises and charities below the stated income threshold. [1] [8]
Establish deception and purpose
Test whether fraudulent or dishonest conduct manipulated, deceived or persuaded the customer to pay an unintended recipient or for an unintended purpose. The formal definition requires more than a disappointing outcome. [1]
Test the civil dispute boundary
Consider communications, trading status, capability, deception about payment purpose and receiving PSP information. The factors are independent, non-exhaustive and must be weighed in the round. [4]
Test the Consumer Standard of Caution
Identify the relevant standard, the firm’s evidence of non-compliance and whether that non-compliance resulted from gross negligence. The burden is on the sending PSP and the threshold is higher than ordinary negligence. [3]
Scope is a gate, not a fraud verdict
For Faster Payments, a claim reported more than 13 months after the final scam payment is outside mandatory reimbursement. A reimbursable claim is ordinarily paid within five business days. The clock may be paused only while specified information is awaited, and the claim must close by the end of the 35th business day. [1]
The current FPS ceiling is £85,000 per claim. A sending PSP may apply an excess of up to £100, but neither the Consumer Standard exception nor the excess applies where relevant vulnerability materially affected the victim’s ability to protect themselves. [5] [6]
These limits decide what the mandatory scheme requires. They do not decide whether fraud occurred, whether separate financial crime action is needed, or whether the wider complaint is defensible.
The contractor who actually started work
Does partial performance make this a civil dispute?
- The customer found a renovation business through social media.
- The company exists on Companies House and a representative visited.
- An initial deposit was followed by some genuine work.
- A much larger second payment was then requested and paid.
- The contractor stopped responding soon afterwards.
- The receiving account has suspicious characteristics.
- Related victim reports emerged after the payment.
- The business shows no credible supplier spend or operating capacity matching the funds received.
The Nominal Performance Trap
Interpretation A: genuine failure
The business intended to complete the work but failed through poor management, cash-flow pressure or a supplier problem. Attendance, work quality, purchasing evidence and credible contemporaneous records may support this.
Interpretation B: fraudulent inducement
Limited work established credibility and induced the larger payment. A sudden payment escalation, absence of capacity, diversion of funds and connected victim reports may support this.
The PSR expressly warns that earlier returns or services can be used to build confidence, and that a nominal service may be started to make an offer appear legitimate. It also says non-delivery alone does not establish an APP scam. [4] Performance is evidence. It is not the conclusion.
Source
The sending PSP should consider the five civil-dispute factor areas, each claim on its merits and all available information in the round. If it classifies a claim as a civil dispute, the onus is on the PSP to demonstrate and communicate why. [4]
Application
Attendance and some work support a genuine relationship, but registration alone proves little about actual trading. The timing of the larger request, account behaviour, later reports and lack of operational capability support planned inducement. The present record is not strong enough for a categorical conclusion solely from performance or non-performance.
Action
Keep the case classified as potential APP scam while targeted evidence is gathered. Ask the receiving PSP for relevant account-opening, usage, marker and prior-claim information. Test supplier spend, workforce, communications and use of the second payment. Then record which interpretation the evidence better supports.
What Would Change My Decision?
Towards genuine commercial failure: independently verified supplier purchases, credible payroll and subcontractor records, work across other customers, contemporaneous evidence of an unforeseen failure, and funds applied consistently with the quoted project.
Towards fraudulent inducement: immediate dissipation unrelated to the work, fabricated supplier documents, repeated near-identical victim journeys, false claims about capacity, scripted reasons for the second payment, or receiving-PSP evidence of prior fraud concerns.
Decision Record
- Facts
- Two payments were made. A representative attended. Some work occurred. Work then stopped. Related reports and suspicious receiving-account features exist.
- Assumptions
- The limited work may have been intended to induce the second payment. That inference is not yet an established fact.
- Indicators
- Larger follow-on request, lack of matching operating capacity, receiving-account concerns and connected reports materially support fraudulent inducement.
- Mitigants
- A real company, property visit and genuine performance support a plausible commercial relationship.
- Decision
- Potential APP scam requiring targeted evidence before final classification. Do not reject solely as a civil dispute.
- Rationale
- The evidence supports two live competing explanations. The missing evidence concerns intent and capability at the point of the larger payment, so the next action is evidential rather than outcome-led.
The warning the customer ignored
Does ignoring both automated and human warnings automatically establish the Consumer Standard of Caution exception?
- A recently bereaved customer developed an emotionally intense online relationship.
- The supposed partner requested a large payment for an urgent problem.
- The PSP displayed an APP warning and the customer continued.
- A fraud analyst then called and identified scam indicators.
- The customer gave a false explanation about the beneficiary.
- The customer insisted the payment was genuine and it proceeded.
- The relationship was later shown to be fabricated.
- The file records the interventions, but not what the customer understood or why the deception persisted.
Source
A refusal based on an intervention requires the PSP to demonstrate gross negligence. The intervention should be specific, directed and clear about the probability of an APP scam. Proceeding after a warning does not automatically satisfy the exception. Relevant vulnerability removes the exception where it materially affected the ability to self-protect. [2] [3]
Application
The click-through, false explanation and insistence are important conduct evidence. They are not self-proving. Bereavement is also not self-proving. The analyst must establish what each intervention communicated, what the customer understood, why emotional manipulation displaced it, whether coaching was operating and whether those circumstances materially reduced independent judgement.
Action
Reconstruct the warning and call from the evidence available at the time. Assess the customer’s conduct against the specific caution requirement. Complete the causal vulnerability assessment before deciding whether the PSP has discharged the gross-negligence burden. Preserve a separate complaint review of whether the payment should have been paused or refused.
What Would Change My Decision?
Towards the exception: a scam-specific intervention clearly communicated a high probability of fraud; reliable records show the customer understood the real risk and could act independently; no material vulnerability affected that ability; and the PSP can show a significant degree of carelessness caused the failure to have regard.
Away from the exception: generic or mismatched warning content, no reliable record of the call, active coaching, emotional dependence, impaired comprehension, a reasonable belief that disclosure would endanger the supposed partner, or evidence that bereavement materially reduced the ability to resist the manipulation.
Decision Record
- Facts
- The customer continued after an automated warning and an analyst call, gave a false explanation about the beneficiary, and later established that the relationship was fabricated. The customer was recently bereaved. The file does not establish the exact warning content, what the customer understood, or the effect of bereavement on self-protection.
- Assumptions
- It would be an assumption that the warnings were adequate, that the customer understood and could act independently, that deception proves gross negligence, or that bereavement materially affected the ability to self-protect.
- Indicators
- Proceeding after two interventions and providing a false explanation may support failure to have regard to a warning, if the interventions were specific, directed and understood. The intense relationship and fabricated urgency support sustained scam manipulation.
- Mitigants
- Possible coaching, emotional dependence, recent bereavement and missing evidence about warning quality or comprehension may weaken a gross-negligence inference. None of those factors determines vulnerability or reimbursement by itself.
- Decision
- Do not apply or reject the Consumer Standard of Caution exception on the current record. Reconstruct the interventions and complete the causal vulnerability assessment before deciding whether the sending PSP can demonstrate gross negligence.
- Rationale
- The customer conduct is material but not conclusive. The exception depends on the quality and understanding of the intervention, the degree of carelessness, and whether relevant vulnerability materially affected the ability to self-protect. Reimbursement follows the resulting scheme analysis, not a warning acknowledgement or vulnerability label alone.
The Defensibility Layer
The mandatory result is one answer. Complaint defensibility is another.
Scheme compliant
The classification, scope, exception, timing, ceiling and excess follow the applicable reimbursement rules.
Defensible
The wider handling survives scrutiny of warning quality, prevention conduct, evidence, customer communication and complaint fairness.
The Financial Ombudsman says it will look at the complaint and how the firm handled it regardless of which rules apply. It may still consider whether a firm could and should have prevented the loss where the mandatory rules do not apply, or where an excess or the £85,000 ceiling limits the scheme payment. [9]
- Can an independent reviewer reconstruct the exact warning or call?
- Did the intervention address the actual scam mechanism?
- What did the firm know at the time and what could it reasonably have done?
- Does the calculation leave loss above the ceiling or within an applied excess?
- Does the customer letter explain the four verdicts without internal jargon?
- Do fraud intelligence, receiving-account action and suspicious-activity consideration remain separate from reimbursement?
Mandatory scheme compliance does not automatically end the firm’s exposure.
Practitioner Lens
The facts stay fixed. The operational question changes by role.
Fraud Analyst
Separate facts, customer statements, third-party evidence, assumptions and gaps. Sympathy, scepticism and reimbursement cost are not classification evidence.
Fraud Manager
Test analyst variance. If materially similar evidence produces different gate outcomes, inspect the decision standard, assurance sample and coaching, not just individual accuracy.
Complaints
Run the Defensibility Layer after the scheme decision. Examine prevention, warning quality, fairness, communication and any residual loss rather than treating the reimbursement calculation as final.
Product and Fraud Strategy
Treat warning quality as evidence. A warning later relied on to establish conduct must be reproducible, specific to the payment and intelligible to an independent reviewer.
MLRO and Financial Crime
Do not allow a reimbursement result to decide separate suspicious-activity consideration, receiving-account risk or wider network investigation.
Five reasoning traps
These are not five fraud typologies. They are five ways a sound process produces an indefensible decision.
1. The Backwards Verdict
- Risk
- An out-of-scope payment is recorded as not fraudulent.
- Signal
- The rationale starts with policy eligibility rather than what happened.
- Response
- Complete fraud classification before the scheme-scope gate.
2. The Stage-Set Business
- Risk
- Nominal performance conceals planned fraudulent inducement.
- Signal
- “Some work was done” is treated as the end of the analysis.
- Response
- Test intent, capability and use of funds in the round.
3. The Click-Through Conviction
- Risk
- Weak intervention evidence is used to refuse reimbursement.
- Signal
- The file records continuation but not warning quality or understanding.
- Response
- Reconstruct the intervention and prove the gross-negligence threshold.
4. The Label Without a Mechanism
- Risk
- Vulnerability is either assumed or dismissed without scam-specific analysis.
- Signal
- The record names a circumstance but not its effect on self-protection.
- Response
- Document how the circumstance affected detection, resistance or escape.
5. The Ceiling Becomes a Wall
- Risk
- Preventability and complaint fairness are left unexamined.
- Signal
- The complaint closes when the mandatory calculation is complete.
- Response
- Run the Defensibility Layer against the complete handling.
One Screen Operational Summary
- TriggerCustomer reports an authorised payment induced by suspected fraud.
- ClassifyDetermine whether it is APP scam, unauthorised fraud, civil dispute or another payment problem.
- ScopeEstablish whether the payment and customer fall within the mandatory regime.
- EvidenceSeparate established facts, customer statements, third-party evidence, receiving-PSP intelligence, assumptions and gaps.
- Scam testDetermine whether fraud or dishonesty manipulated recipient identity or payment purpose.
- Civil disputeAssess intent using the available evidence in the round.
- VulnerabilityDetermine whether vulnerability materially affected the ability to protect against this scam.
- Consumer cautionOnly then assess whether the PSP can demonstrate gross negligence.
- ReimburseApply the relevant timing, excess and reimbursement ceiling.
- DefensibilitySeparately assess warning quality, prevention conduct and complaint fairness.
- DocumentRecord facts, assumptions, competing evidence, outcome and rationale.
Red Team Questions
- Are we treating absence of evidence as evidence that fraud did not occur?
- Have we confused commercial failure with fraudulent intent?
- Have we confused some genuine performance with genuine overall intent?
- Are we using customer deception as evidence of scam sophistication and then using the same deception against the customer?
- If relying on a warning, could an independent reviewer understand exactly what the customer saw or heard?
- Have we established why the customer proceeded, or merely recorded that they proceeded?
- Have we assessed vulnerability before applying the Consumer Standard of Caution exception?
- Would another competent analyst reach the same conclusion from the Decision Record?
- Could the decision be explained clearly to the customer without internal jargon?
- Would the rationale remain understandable twelve months later?
Knowledge check
Choose one answer for each question. The score is an aid to review, not a credential or case decision.
The Radar View
Signal
Across closed Faster Payments claims in the first 18 months, the PSR dashboard reports that 88% of reimbursable APP scam losses by value were returned. A separate July 2026 evaluation estimated that the policy reduced APP fraud losses by £73 million a year. [11] [13]
Exposure
The PSR also says implementation remains inconsistent and outcomes can still vary according to the customer’s provider. That is a judgement-control problem, not merely a processing problem. [13]
Control
Test scam versus civil-dispute reasoning, vulnerability, Consumer Standard decisions, warning quality, receiving-PSP evidence, Decision Records, complaint outcomes and analyst variance.
Watch
The PSR plans a December 2026 consultation covering further clarity on consumer caution, civil disputes, me-to-me transactions and other policy parameters, with a decision and revised directions planned for May 2027. [12]
Risk, Signal, Response
1. The Backwards Verdict
- Risk
- An out-of-scope payment is recorded as not fraudulent.
- Signal
- The rationale starts with policy eligibility rather than what happened.
- Response
- Complete fraud classification before the scheme-scope gate.
2. The Stage-Set Business
- Risk
- Nominal performance conceals planned fraudulent inducement.
- Signal
- “Some work was done” is treated as the end of the analysis.
- Response
- Test intent, capability and use of funds in the round.
3. The Click-Through Conviction
- Risk
- Weak intervention evidence is used to refuse reimbursement.
- Signal
- The file records continuation but not warning quality or understanding.
- Response
- Reconstruct the intervention and prove the gross-negligence threshold.
4. The Label Without a Mechanism
- Risk
- Vulnerability is either assumed or dismissed without scam-specific analysis.
- Signal
- The record names a circumstance but not its effect on self-protection.
- Response
- Document how the circumstance affected detection, resistance or escape.
5. The Ceiling Becomes a Wall
- Risk
- Preventability and complaint fairness are left unexamined.
- Signal
- The complaint closes when the mandatory calculation is complete.
- Response
- Run the Defensibility Layer against the complete handling.
FAQ
Does a genuine APP scam always fall within mandatory reimbursement?
No. Fraud classification and scheme scope are separate verdicts. Payment system, account control, geography, customer type, date and reporting time can affect scheme scope without changing what happened.
Does partial performance prove a civil dispute?
No. It supports one interpretation, but the PSR’s guidance expressly recognises that a nominal service can be used to induce confidence. Test intent, capability, payment purpose and all available information in the round.
Does proceeding after a warning prove gross negligence?
No. The firm must demonstrate gross negligence in failing to meet a specified caution standard. Warning specificity, clarity, the scam’s complexity, the customer’s understanding and relevant vulnerability all matter.
Does bereavement automatically establish vulnerability for the exception?
No. It is a potential vulnerability characteristic. The scheme question is whether the circumstances materially affected the customer’s ability to protect themselves from the particular scam.
Does the £85,000 ceiling end the complaint?
No. It limits the mandatory scheme amount. The Ombudsman may still consider whether the firm could and should have prevented loss above the ceiling or within an applied excess.
Sources and methodology
Scope: UK Faster Payments and retail CHAPS APP scam reimbursement judgements under the rules in force from 7 October 2024. This is decision support for practitioners, not legal advice.
Method: Operative directions, scheme rules and official guidance were reviewed against current PSR, Pay.UK, Bank of England, Financial Ombudsman Service and FCA materials. The scenarios are composites designed to test borderline reasoning. They do not describe real customers or predetermine an outcome.
Evidence separation: Source blocks state what an authority establishes. Application blocks are FinCrimeRadar analysis of the composite facts. Action blocks are operational recommendations. Illustrative facts are not represented as external evidence.
- Payment Systems Regulator, Specific Requirement 1, Faster Payments APP scam reimbursement rules, amended July 2024.
- Payment Systems Regulator, The Consumer Standard of Caution Exception, December 2023.
- Payment Systems Regulator, Consumer Standard of Caution Exception Guidance, December 2023.
- Payment Systems Regulator, Supporting the identification of APP scams and civil disputes, September 2024.
- Payment Systems Regulator, Notice of maximum reimbursement level value, September 2024.
- Payment Systems Regulator, Notice of maximum excess value, December 2023.
- Pay.UK, FPS Reimbursement Rules, Schedule 4, version 3.5.
- Bank of England, CHAPS reimbursement rules, August 2024.
- Financial Ombudsman Service, APP fraud and other scams involving authorised payments or withdrawals, accessed 8 September 2026.
- Financial Conduct Authority, FG21/1: Guidance for firms on the fair treatment of vulnerable customers, updated 22 July 2026.
- Payment Systems Regulator, APP scams reimbursement dashboard for Q1 2026, updated 30 July 2026.
- Payment Systems Regulator, APP scams policy roadmap, July 2026.
- Payment Systems Regulator, Payment fraud falls by £73m following PSR reimbursement scheme, July 2026.
Last reviewed: 8 September 2026. Recheck the PSR roadmap and any revised directions after the planned December 2026 consultation.