Why we started

Ecom Fraud Guide began in 2019 as a shared spreadsheet. Two of us—a former chargeback analyst and a payments engineer—were trading notes on fraud patterns we saw across US merchants. The spreadsheet grew into a blog, then into a small team that now writes full-time about chargeback risk and fraud operations. We exist because most guidance for online merchants is either too generic or locked behind a sales call. We wanted something practical, specific, and free to read.

What we do

We publish research, explainers, and checklists for merchants who handle their own fraud and chargeback processes. Our work covers the full dispute lifecycle: how to read a chargeback reason code, how to build evidence packets that hold up, how to spot friendly fraud without alienating good customers, and how to set thresholds that don’t block revenue. We don’t sell a fraud tool or take affiliate commissions from gateway providers. Our only product is the guide itself.

How we work

Every article starts with a real merchant problem—usually one we’ve seen in support tickets, forum threads, or conversations with ops teams. We test claims against public card network rules and, where possible, against anonymized data from merchants who share their numbers with us. When we’re unsure, we say so. We update posts when rules change (the 2024 Visa compelling evidence updates, for example) and note the revision date at the top.

Who we are

The editorial team is small: three writers and two part-time reviewers. Our lead writer spent six years in chargeback operations at a mid-size apparel retailer, handling everything from first-party misuse to post-dispute recovery. Our technical reviewer worked on payment gateways and has a habit of reading card network rulebooks for fun. Between us we’ve filed thousands of representments and sat through enough risk reviews to know which advice actually gets used.

We also rely on a group of outside contributors—merchant consultants, fraud analysts, and one very patient chargeback lawyer—who review drafts for accuracy. They’re not paid; they contribute because they’re tired of seeing the same bad advice circulate.

What we value

• Specificity over generality. A reason code is not a strategy. We aim for numbers, examples, and decision trees you can apply today.
• Transparency about limits. We don’t have a silver bullet. Some fraud you can’t prevent, only manage. We’d rather tell you that than sell you a false sense of control.
• No hidden agenda. We don’t accept sponsored posts, and we don’t rank tools for pay. If we mention a vendor, it’s because we’ve used it or a merchant we trust has.
• Plain language. Chargeback rules are dense enough. We write in plain English and avoid jargon where we can.

How we’re funded

We cover our costs through a single, clearly labeled sponsor slot in our newsletter and through occasional paid workshops for merchant teams. That’s it. No pay-to-play coverage, no lead-gen forms. If that changes, we’ll say so here first.

Corrections

We get things wrong. When we do, we correct the article and add a note at the bottom. If you spot an error, email corrections@ecomfraudguide.com. We read every message.

Where to start

If you’re new to chargebacks, begin with our guide to the dispute lifecycle. If you’re drowning in reason code 10.4, start with the Visa compliance series. And if you just want to talk through a messy case, our forum is open—no account required.

We’re not the biggest name in payments, and we’re fine with that. We’re the guide we wished we’d had when we were the ones on the phone with the processor at 11 p.m.