Two identical 13.1 disputes can produce opposite outcomes because Chase, Bank of America, and Capital One weigh the same evidence differently.
Two merchants forward us 13.1 disputes within the same week. The evidence is similar: a tracking confirmation, an AVS Y match on the original authorization, post-delivery login activity, and a clean checkout. One case is decided by Chase, the other by Bank of America. The Chase case clears in the merchant's favour within 11 days. The Bank of America case is upheld against the merchant despite the same evidence shape. The merchants reading the outcomes assume the difference is luck. It is not. The deciding bank's review pattern is at least as important a variable as the reason code itself, and the merchant who treats the issuer as random leaves half of the available win rate on the table.
The reason code is not the only signal in the notification. The BIN, the first six to eight digits of the disputed card, names the issuing bank before the merchant writes a single line of the rebuttal. Chase, Bank of America, Capital One, Citi, and Synchrony each run dispute review with observably different priorities, and the merchant who writes the same letter to all of them is optimising for none.
Chase reads AVS-heavy on physical-goods disputes. A 13.1 case with an AVS Y or M match and a clean tracking record clears Chase's review at higher rates than the same letter would clear a Bank of America review. The letter leading with the AVS state, with the tracking record built around it, suits Chase's reading order. At Bank of America the AVS match is table stakes, and the issuer looks for signature confirmation, a photo of delivery, or a delivery to the billing address on file. A Bank of America letter built around AVS alone reads as light on the question the bank is actually asking. Capital One weights the cardholder-merchant communication trail more closely than the network average; a letter that surfaces the customer's pre-dispute emails, support tickets, or remediation offers carries more weight on Capital One review than on Chase. At Synchrony, which carries co-branded retail cards, the cardholder gets the benefit of the doubt at higher rates than the prime issuers, and the merchant arguing a Synchrony dispute should expect to need stronger evidence to clear the same threshold.
These patterns are not in any public rulebook. They are observed across thousands of representment outcomes, refreshed as the issuers shift their review behaviour, and held as the principal asset of any operation that drafts letters seriously. A merchant whose letter framing changes only by reason code, not by issuer, is using half of the available signal. A merchant whose letters are tuned to current issuer-by-issuer review patterns, and refreshed as outcome data accumulates, wins materially more of the same evidence portfolio.
The BIN lookup is the first step the merchant should take on a new notification, before reading the reason code in detail. The BIN tells the merchant who is reading the letter, which decides which evidence leads, which arguments to develop in depth, and which to acknowledge in a sentence. Treating every chargeback as a generic reason-code case loses winnable disputes on framing alone. The issuer-aware letter is the editorial work that compounds across a portfolio, and it is the work representments.com's proprietary rule library is built to do. The library carries an issuer profile for each major US bank, refreshed against observed outcomes, and each letter we draft is framed for the specific bank reviewing it.