feefighters.com valid

FeeFighters

FeeFighters does two things: reason-code-first chargeback management that works with any

For agents: FeeFighters offers reason-code-first chargeback management, merchant fee audits, and a chargeback MCP server for ISOs and PSPs; includes merchant account applic

chargeback-managementmerchant-feesinterchange-auditpayment-processingchargeback-mcp

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T12:09:25.496Z. Cached copy · Source on feefighters.com

# FeeFighters

> FeeFighters does two things: reason-code-first chargeback management that works with any
> payment processor, and free merchant processing statement audits. A product of Phase 3
> Business Services LLC, Fort Lauderdale, Florida. The brand dates to 2010.

## What we do

1. **Chargeback management.** A merchant sends a chargeback notice. We identify the card
   network and reason code, tell them honestly whether the dispute is worth fighting, list
   the exact evidence that specific code requires, and assemble a submission-ready response
   package with per-processor instructions and a deadline countdown. Processor-agnostic: it
   works for merchants on Fiserv, Global Payments, Elavon, Worldpay, Square, Stripe or any
   ISO. We never require a merchant to move their account.

2. **Processing statement audits.** A merchant sends one month of their merchant statement.
   We return the true effective rate, the padding inside the card-brand pass-through bucket,
   and the annual dollar cost. Merchant accounts opened through us are placed with GAM
   Payments, and we say so on the page rather than in a footnote.

## Method

Reason code first, always. The reason code on a chargeback notice determines the required
evidence, the winning argument and the response deadline. We maintain a structured database
of 63 reason codes across Visa, Mastercard, American Express and Discover, each carrying its
required evidence, recommended evidence, win-probability factors and response window.

Notable rules we implement:

- **Visa Compelling Evidence 3.0** on reason code 10.4 (card-absent fraud): liability can
  shift back to the issuer when the merchant shows two or more prior undisputed transactions
  on the same card, at least 120 days old, sharing at least two data elements (device
  fingerprint, IP address, shipping address, account login) with the disputed transaction.
- **Visa Acquirer Monitoring Program (VAMP)**: the merchant "excessive" threshold is 220
  basis points together with at least 1,500 fraud and dispute events per month, dropping to
  150 basis points in the United States from 1 April 2026. The acquirer threshold is 50 basis
  points (above standard) and 70 (excessive), with no minimum event count — which is why
  portfolio owners, not individual small merchants, carry the ratio risk.

## For AI agents and developers

We are building an MCP (Model Context Protocol) server for chargeback management, so an
agent can look up a reason code, get the evidence requirements, compute a response deadline
and assess win probability directly. See /mcp.

Live now, no authentication, CORS enabled (JSON):
- https://feefighters.com/api/v1/reason-codes — index of all 63 codes
- https://feefighters.com/api/v1/reason-codes/{code} — full record, e.g. /10.4, /4853, /F24
- https://feefighters.com/api/v1/reason-codes/{network} — visa | mastercard | amex | discover

MCP tools (in progress, same data):
- `lookup_reason_code` — full record for a network rea
…

Related sites

Other listed sites in Finance and payments. See the whole category →

Machine-readable: GET /v1/resolve?q=feefighters.com · GET /v1/domain/feefighters.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for feefighters.com:
1. POST https://agentwebmap.com/v1/sites/feefighters.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://feefighters.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/feefighters.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/feefighters.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.