How a Debt Purchaser PRA Group Tried to Convert a Regulatory Complaint Into an Easy Win Vulnerability Case

Debt purchasers like PRA and others have a playbook. It’s subtle, psychological, and designed to protect their revenue not the customer.

And one of the most common tactics is what I call the Complaint Conversion Trick:

Take a regulatory complaint… and quietly convert it into a “vulnerability support case”… so they never have to answer the real questions.

This week, PRA Group demonstrated this tactic perfectly.

Let’s break down exactly what happened — and why every debtor needs to understand this manoeuvre.

1. The PRA Complaint Was About Regulation — Not Vulnerability.

My complaint to PRA Group was clear:

protected‑income misuse
suitability failures
oversight failures
jurisdiction errors
SFS transmission failures
Consumer Duty breaches
CONC 7 & 8 compliance
data‑accuracy failures

These are regulatory issues, not emotional ones.

They require:

evidence,
audit trails,
transmission logs,
policy documents,
and a formal final response under DISP.

Instead of answering any of these points, PRA attempted something else entirely.

2. PRA Unilaterally “Withdrew” the Complaint — Which Is Not Allowed.

Their letter stated:

“I have withdrawn your complaint.”

Under DISP 1.4.1R, a firm cannot withdraw a complaint unless:

the customer withdraws it, or
the firm issues a valid final response.

I did not withdraw it. They did not issue a final response.

This means PRA breached FCA complaint‑handling rules.

This alone is grounds for escalation.

3. PRA Tried to Reframe the Complaint as a “Support Needs” Case.

Instead of addressing the regulatory issues, PRA attempted to convert the complaint into a vulnerability interview.

They asked for:

medical evidence
therapist letters
DMHEF forms
bank statements
mortgage statements
tenancy agreements
benefit award letters
asset details
income details
expense details
priority debt lists
other debt lists

This is not complaint handling.

This is data harvesting.

It shifts the burden of proof onto the debtor — a direct breach of Consumer Duty.

4. PRA Invented a “Write‑Off Request” That I Never Made.

Their letter stated:

“I have advised CST that you are looking for your account to be written off due to exceptional circumstances.”

I never asked for this.

Why did they invent it?

Because if they write off the account due to “exceptional circumstances”, they avoid:

admitting protected‑income misuse
admitting oversight failure
admitting suitability failure
admitting jurisdiction failure
admitting Consumer Duty failure
admitting SFS transmission failure
admitting data‑accuracy failure

A write‑off becomes their escape hatch.

It’s cheaper to write off a debt than to admit a regulatory breach.

5. PRA Ignored the PayPlan SAR Evidence!

My PayPlan SAR proves:

every annual SFS was sent
every vulnerability marker was sent
every dependant was sent
every income source was sent
every update was sent
every address was sent

PRA were fully informed every year.

Their claim that PayPlan “did not make them aware” is contradicted by the SAR.

This is a serious oversight failure.

6. PRA Tried to Stall the Process With a 30‑Day Hold.

They placed the account on hold for 30 days.

This is not kindness. It’s a delay tactic.

They know:

the complaint is valid
the SAR evidence is damning
the protected‑income argument is correct
the jurisdiction argument is correct
the oversight argument is correct
the suitability argument is correct

They are stalling for time.

7. Why Debt Purchasers Use This Tactic.

Because it works — on most people.

The Complaint Conversion Trick:

avoids answering regulatory questions
avoids admitting breaches
avoids providing evidence
avoids transmission logs
avoids oversight documentation
avoids Consumer Duty analysis
avoids suitability checks
avoids jurisdiction errors
avoids protected‑income misuse
avoids refund liability

Instead, they push the debtor into:

emotional disclosure
medical disclosure
financial disclosure
vulnerability pipelines
“support needs” conversations

This turns a regulatory breach into a soft‑touch welfare case.

It’s easier for them. It’s cheaper for them. It protects their inflow of cash.

8. How to Defeat This Dirty DMP Tactic.

You defeat it by doing exactly what I did:

Step 1 — Reject the conversion

Tell them the complaint remains active.

Step 2 — Reject the vulnerability diversion

Tell them you will not provide medical evidence during an active complaint.

Step 3 — Reject the write‑off framing

Tell them you did not request a write‑off.

Step 4 — Reassert the regulatory questions

Send the full 11‑question strikeout.

Step 5 — Remind them of DISP 1.4.1R

They cannot withdraw a complaint.

Step 6 — Keep everything in writing

Never allow them to move the conversation to phone calls.

Step 7 — Escalate to FOS if they fail again

Procedural breaches are automatic wins.

9. Final Message to Debtors.

If a debt purchaser tries to:

withdraw your complaint,
reframe it as vulnerability,
ask for medical evidence,
ask for bank statements,
ask for award letters,
ask for mortgage documents,
ask for tenancy agreements,
ask for asset lists,
or push you into a “support needs” team…

…it means your complaint is valid and they are trying to avoid answering it.

You are not powerless. You are not at the mercy of scripts. You are not a passive debtor.

You are the auditor. And the system has to answer.

Debt purchasers have a playbook. It’s subtle, psychological, and designed to protect their revenue — not the customer.

And one of the most common tactics is what I call the Complaint Conversion Trick:

Take a regulatory complaint… and quietly convert it into a “vulnerability support case”… so they never have to answer the real questions.

This week, PRA Group demonstrated this tactic perfectly.

Let’s break down exactly what happened — and why every debtor needs to understand this manoeuvre.

You are not at the mercy of scripts. You are not a passive debtor.

You are the auditor. And the system has to answer.