Shield

Who we are, and why this project exists

Shield is an independent information project. We write about fraudulent brokers, investment scams, and the payment-dispute routes people actually have after money has already left their account. No regulator status, no recovery promises, no sales calls.

Why this project exists, and what it refuses to be

Shield is an information resource, not a recovery service. We explain how fraudulent brokers and investment schemes work, what a chargeback actually is, and which documents matter if someone needs to dispute a payment. Nothing here is legal or financial advice, and we do not act on anyone's behalf.

The problem we keep running into

Most people who lose money to a fake broker do not lose it in one dramatic moment. They lose it across weeks: a small test deposit that works, a friendly account manager who answers quickly, a dashboard that shows gains, and then a withdrawal request that triggers a tax, a compliance fee, or a liquidity top-up. By the time the pattern becomes obvious, the money is gone and the platform's support chat has gone quiet. The information that could have helped earlier is scattered across forums, bank help pages, and card scheme rules that are written for institutions, not for individuals.

How we work

We write in plain language and we stay inside what we can verify. When we describe a chargeback, we describe the card scheme process and its typical timeframes, not a guaranteed outcome. When we describe a bank transfer recall, we say clearly that it depends on the receiving bank and often fails. We do not promise recovery, we do not collect case details, and we do not present ourselves as a regulator, a bank, a payment provider, or a law firm. Where a topic needs a professional, we say so and point to the right kind of institution rather than to ourselves.

What a reader should leave with

The realistic goal is a clearer next step. Someone who arrives after a suspicious withdrawal request should be able to identify which payment route they used, find the deadline that applies to it, and assemble the evidence a bank or card issuer will actually ask for: transaction references, chat logs, the platform's terms, screenshots of the account, and the dates of every request for additional funds. That is a modest outcome compared with a promise of recovery, and it is the one we can honestly deliver.

How our understanding of fraud took shape

The Values page is also a record. Below are the moments that changed how we write, what we warn about, and which questions we stopped treating as settled.

2019 — Reading the same script twice

Two people sent us screenshots from different platforms with identical wording: the same account manager tone, the same "compliance deposit" phrasing. That overlap became the first thing we started cataloguing instead of treating each case as isolated.

2020 — Separating card disputes from transfers

We kept seeing the word chargeback used for money that never touched a card. Rewriting our material around payment method first, and dispute route second, removed a lot of confusion for readers who had already been told the wrong thing by someone else.

2022 — Evidence before urgency

Victims often arrive after weeks of pressure and very little saved. We shifted our guidance to start with what to preserve: chat logs, withdrawal screens, bank statements, the exact dates of each request. Documentation outlasts memory, and it outlasts the platform's website.

2024 — Writing for the person, not the case

Our pages stopped reading like intake forms. We describe how fraudulent brokers build trust, why extra fees appear after a withdrawal request, and what a person can realistically expect from a bank, without implying we are a regulator, a law firm, or a recovery service.

How This Project Took Shape

Shield started as a shared notes file between three people who kept answering the same questions from friends and relatives. The milestones below are the decisions that turned those notes into a public reference on fraudulent brokers and payment disputes.

Shield values
  1. 01

    From private answers to a written record

    At first we replied one-to-one: how a fake broker platform opens an account, why a "test withdrawal" clears, what a card issuer actually needs to see. The same explanations kept repeating, so we wrote them down properly and started checking each claim against bank dispute rules and card scheme documentation.

  2. 02

    Separating education from advice

    An early draft read like a service page. We cut it back. The site explains how chargebacks, bank transfer recalls, and card disputes differ, and what evidence to keep, but it does not act on anyone's behalf and does not present itself as a regulator, bank, or law firm. That boundary shaped every page after it.

  3. 03

    Building the case library

    We collected anonymised patterns from reader emails: the fee escalation after a withdrawal request, the cloned dashboard, the account manager who switches tone once a second deposit is refused. Those patterns became the backbone of the blog and the use-case pages, written in plain language rather than compliance jargon.

  4. 04

    Reviewing the wording with people who handle claims

    Payment dispute staff and consumer advisers read the drafts and flagged where our language was too loose. We tightened the definitions, added timeframes where they are genuinely fixed, and removed anything that sounded like a promise of recovery. The result is slower to read and more useful.

  5. 05

    Keeping it current

    Scam scripts change faster than the pages describing them. We revisit the guides when readers report a new tactic, when dispute windows shift, or when a payment route stops being reversible in practice. The timeline on this site tracks those revisions rather than marketing announcements.

If a pattern on this site does not match what happened to you, that is worth knowing too. Write to [email protected] and describe it in your own words.