Card Dispute Outcome Table

What it does

Card Dispute Outcome Table takes the card dispute cases you handled, one row each: the network (Visa, Mastercard, American Express, Discover or other), the reason code as printed, the outcome (won, lost, withdrawn or open), the days it took to close, and, if you like, your own label for the merchant. It gives back a table by network reason code, by reason-code family across networks and by merchant label: how many cases, how many won, lost, withdrawn and open, the win rate among decided cases with a 95 percent range, and the days to close (median, 90th percentile, mean, longest). A group with too few decided cases is marked too few to rely on. Each Visa, Mastercard and American Express code comes with its plain meaning. Every answer states the federal clocks for a consumer's own dispute with a bank or card issuer (Regulation E section 1005.11 for debit, Regulation Z section 1026.13 for credit) with the date each rule was last amended; ask for check_sources and it asks the eCFR, the official online CFR, whether either rule was amended since. The answer is dated and signed with our key. It is arithmetic, a code list and a lookup: no model, nothing stored, nothing sent.

Who it is for

Agents that help card acceptors, payment facilitators, community banks and credit unions, and the chargeback analysts and bookkeepers around them, see which dispute reasons are won, how long they take, and how far a small sample can be trusted.

Price

Free, no sign-up: 120 tables an hour per address. Paid calls are planned and not charging.

Limits

Up to 500 cases and 60,000 bytes per call, 50 merchant labels; larger requests are refused, never cut. There is no pooled data in this version: every number comes from the rows you send, and the tool does not know whether your rows are complete or typical. A win rate is won out of won plus lost; withdrawn and open cases are counted but left out of the rate. The 95 percent range is a Wilson interval and assumes the cases are independent. It does not tell you whether to contest a dispute or what evidence a network will accept, and it does not know the networks' own time limits, which are in private rule books. The code meanings are our copy of the networks' public rule summaries and may be out of date: check the network's own document. Discover and other networks are accepted, but there is no code list for them. The Regulation E and Z clocks are for a consumer's own dispute with their bank or card issuer, not network chargeback deadlines. Use merchant labels (letters, digits, . _ -), never card numbers, names or emails; a label with 6 or more digits is refused, but the tool cannot spot every identifier. Nothing you send is stored; only a count of requests per address is kept in memory for an hour. The source check reads two fixed eCFR pages, cached 10 minutes for everyone, 20 source checks an hour per address; you cannot send an address. It reads amendment dates only, not the rules' text. Not legal, banking or compliance advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"card_dispute_outcome_table_win","arguments":{"outcomes":[{"network":"visa","reason_code":"13.1","outcome":"won","days_to_close":18,"merchant":"shop-a"},{"network":"visa","reason_code":"13.1","outcome":"lost","days_to_close":41,"merchant":"shop-a"},{"network":"mastercard","reason_code":"4837","outcome":"won","days_to_close":9},{"network":"visa","reason_code":"10.4","outcome":"open"}],"min_cases":20,"check_sources":true}}}
-> by reason code: cases, won, lost, win rate with a 95% range, days to close, a too-few flag, the meaning of each code; by family and by merchant; the Regulation E and Z clocks with dates; signed record

For agents

Tool card_dispute_outcome_table_win on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:ttfnk55xma3tcrikd43einvejm): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): 7oC5B6ncaHxUdCFDogDtlKqmhyhhmjaIqvAbgELihtI=

This tool exists to be found by agents that search MCP registries for card dispute, chargeback and reason-code tools (road: MCP registries, through the Campus gateway: MCP, Agent2Agent and REST). It makes one signed, checkable answer per call; keep the signed record with your work so a person can see which rows the table was built from and when, and send new cases next time to see how the rates move.

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card