Shield

How we check what we publish about broker fraud and chargeback routes

Every claim on this site is tied to a source, a payment method, or a documented procedure. Here is the standard we hold ourselves to when writing about scam patterns, dispute windows, and the evidence a bank or card issuer will actually accept.

Who we work alongside, and what that actually means

Partnerships on this page are listed for one reason: they describe a working relationship that helps a reader check a broker, a payment route, or a document trail. We name the type of cooperation, the field it covers, and the limits of what a partner does and does not do. No logos are borrowed to imply endorsement, and no partner is presented as a regulator, a bank, or a recovery service.

Most of the cooperation behind this site is unglamorous. It is data sharing with consumer advisory desks, editorial review by people who handle dispute paperwork daily, and cross-checks with anti-fraud researchers who track cloned broker domains. Each relationship below is scoped: a partner contributes a specific kind of input, and that input is labelled as such.

If a partner's role changes or a cooperation ends, the entry is removed rather than left standing as a stale trust signal. That is the whole point of keeping this list short.

Shield quality

Consumer advisory desks

Independent advice services that handle card and transfer complaints. They share anonymised case patterns with us, and we publish the recurring warning signs that come out of those patterns. They do not review our articles, and we do not route readers to them as a service.

Anti-fraud research groups

Small research teams tracking cloned broker domains, reused registration numbers, and recycled account-manager scripts. We cite their domain lists when explaining how a fake platform is assembled. Their findings are treated as leads, not verdicts.

Dispute documentation reviewers

Practitioners who read chargeback files for a living and review our checklists for accuracy: what a card issuer expects, which timestamps matter, how a chat log should be exported. They flag wording that could be read as a promise of outcome.

Financial literacy publishers

Editors and trainers who reuse our plain-language explanations of chargebacks, recalls, and payment routes in workshops. The material is shared under the same neutral framing: describe the process, name the deadlines, avoid guarantees.

Payment-route specialists

People who work with card scheme rules and bank recall procedures and check that our comparison of dispute routes stays current. Their input is limited to process accuracy, not to case handling or advice on individual claims.

A listed cooperation is not a certification, an approval, or a statement about any specific claim. If you are checking whether a platform is legitimate, start with the warning signs and the evidence checklist, then speak to your own bank or card issuer about the route that applies to your payment.

How we judge quality before we publish anything

Quality here is not a slogan. It is a set of checks we run on every page, every comparison, and every explanation of how a dispute route works. Below are the standards we hold ourselves to, and the reasons they matter when someone is trying to work out what happened to their money.

We separate what is documented from what is assumed Payment dispute rules, card scheme timeframes, and bank recall practices

When we describe a chargeback window or a recall request, we say where the rule comes from and what it does not cover. If a detail depends on the card network, the issuing bank, or the country, we say so instead of flattening it into one universal answer. Readers who act on a deadline need the boundary conditions, not a confident summary.

No invented statistics, no borrowed authority We do not present ourselves as a regulator, bank, or recovery service

You will not find recovery rates, success percentages, or case counts on this site, because we cannot verify them and they would mislead. We are an information resource. We explain how fraudulent broker platforms operate and what a victim can consider, but we do not file claims, hold funds, or act on anyone's behalf.

Every claim is traceable to a process, not a promise Reason codes, evidence requirements, escalation paths

If we say a card dispute may be available, we follow it with what the issuer typically asks for: transaction records, correspondence with the merchant, screenshots of the platform dashboard, and a written timeline. That is the part a reader can actually use. The rest is noise.

Language checked for false impressions Wording reviewed so nothing reads as official endorsement

Fraud awareness material fails when it sounds like it comes from an authority it does not represent. We review headings, calls to action, and contact blocks so a visitor never mistakes this site for a government body, a financial regulator, or a law firm. Where a step requires a licensed professional, we say that plainly.

Updated when the underlying procedures change Card scheme rules, bank recall practice, and platform tactics shift

Dispute windows get revised. Scam operators change their onboarding scripts. When a described procedure no longer matches how banks or card issuers handle a case, the page is rewritten rather than left standing. Outdated guidance is worse than no guidance when someone is deciding whether to file.

If you want to see how these standards shape the material itself, start with the plans overview or read the solutions breakdown.