When UX Becomes Fraud: A Personal Case Study in Dark Patterns

And when that power is misused, it can cross a line from persuasion into extraction, and from design into fraud.

I want to share a recent experience that made this painfully clear.

I paid for a subscription on @upwork, a global freelancing marketplace. The payment went through without issue.

Immediately after paying, my account was blocked due to a supposed “verification issue.”

I appealed.
All the information I had provided was accurate.
The response I received was brief and final: permanent suspension, no explanation, no refund.

At that point, the product I paid for was entirely unusable.

This wasn’t a bug.
It wasn’t a misunderstanding.
It was a designed flow.

Let’s look at it structurally:

• The platform accepts payment before verification is fully resolved

• Access to the service is then revoked after payment

• The user is given no meaningful explanation

• Refunds are categorically refused

• The burden of recovery is shifted entirely onto the user

Whether intentional or not, this is a dark pattern.

The user is placed in a lose–lose position:

• You can’t access the service

• You can’t get your money back

• You’re told the decision is final

• You’re offered no path to resolution

That’s not customer support failure — that’s risk externalisation by design.

Fraud doesn’t always look like stolen credit cards or fake invoices.

Sometimes it looks like:

• Monetising access before eligibility is confirmed

• Using vague “trust & safety” language to shut down dialogue

• Hiding behind terms like “no refunds” even when nothing was delivered

• Relying on the fact that most users won’t escalate legally or financially

This is what I mean by fraudulent UX:
designing systems that systematically extract value while denying delivery, knowing that friction, opacity, and fatigue will stop most users from fighting back.

In the EU, consumer law is explicit: if a digital service is not provided, the consumer is entitled to a refund. Contract terms don’t override that. But many platforms rely on the assumption that users don’t know their rights — or won’t exercise them.

That assumption is part of the design.

This isn’t just about one company.

It’s about a wider industry pattern where:

• Trust & Safety decisions are opaque and unchallengeable

• Payments are decoupled from actual service delivery

• UX is optimized for conversion, not fairness

• “No refund” policies are used as a shield against accountability

As designers, product managers, and founders, we should be asking harder questions:

• What happens to users after they pay?

• Where does verification actually belong in the flow?

• Who carries the risk when something goes wrong?

• Are we designing for safety — or for plausible deniability?

I’m pursuing a chargeback and escalating through formal consumer-protection channels. I’ll likely get my money back.

But that’s not the point.

The point is that most users won’t. And systems that rely on that fact are not neutral — they are exploitative.

UX ethics isn’t about nicer buttons or clearer copy.
It’s about power, accountability, and who pays the price when systems fail.

If we don’t call these patterns what they are, they’ll keep spreading — quietly, legally, and at scale.

If you’ve experienced something similar, I’d love to hear from you.
And if you design systems like this: it’s worth asking whether “allowed by policy” is the same thing as right.

UX is never neutral.