On this page

What the common code forms tell you

These are safe starting points for the search terms appearing in this site's data. They are not a substitute for the live case instructions.
Label in the noticeWhat can be said safelyWhat to check next
Visa 10.1, 10.3, or 10.4Current Visa fraud conditions. The environment and condition name matter: EMV counterfeit, card-present, and card-absent fraud are different cases.Confirm the condition, transaction environment, claim text, and evidence fields on the acquirer notice.
Visa 11.3, 12.3, 12.6, or 13.4Current Visa conditions for no authorization/late presentment, incorrect currency, duplicate or alternate-tender claims, and counterfeit merchandise.Open the Visa reference, then match the condition to authorization, currency, payment, product, and fulfillment records.
Visa 30, 53, 72, 80, or 83Historical Visa numbers still found in older documents or exports; they should not be presented as the current universal names for a dispute.Use the Visa page for historical context, then confirm the current condition and claim on the live notice.
Mastercard 4808, 4812, 4849, or 4853Mastercard message reason forms. Their meaning depends on the message system, transaction type, geography, and dispute stage; MATCH is a separate merchant-screening system.Preserve the full code and stage, then use the Mastercard reference and the processor's requested evidence fields.
Mastercard 53, 55, 4855, 4859, or 4860Alternate, limited, or transitional forms documented for particular debit, single-message, ATM, addendum, non-receipt, or credit contexts—not one general chargeback family.Check the product, message system, geography, and claim before choosing evidence; do not turn a historical form into a current universal label.
104, 1040, 412, C08, C18, AW, CD, IC, NA, P01, RG, RM, R03, 0053, or paid by other meansNot safely mappable from the code or phrase alone in this reference. These may be provider, acquirer, regional, rail-specific, shortened, zero-padded, or alternate-tender labels.Keep the exact export and surrounding description, identify the provider and payment rail, and reconcile any other tender before asking the processor which current category applies.

Use the claim to choose the evidence guide

These are merchant-facing orientation examples from Stripe and network guidance, not a complete code list or a filing code you should guess.
Processor categoryTypical Visa examplesTypical Mastercard examples
Product not received13.1 Merchandise/Services Not Received4855 Goods or Services Not Provided (transitional in some flows)
Product unacceptable / not as described13.3 Not as Described or Defective; 13.4 Counterfeit; 13.5 Misrepresentation4853 Defective / not as described
Fraudulent / unauthorized10.4 Other Fraud — Card Absent; 10.1–10.3 EMV and card-present fraud4837 No Cardholder Authorization; 4870/4871 chip liability
Credit not processed13.6 Credit not processed; 13.7 Cancelled merchandise/services4860 Credit Not Processed (legacy in some flows)
Duplicate12.6.1 Duplicate processing; 12.6.2 Paid by other means4834 amount/duplicate family
Subscription cancelled13.2 Cancelled Recurring4841 cancelled recurring / digital goods

Codes that are easy to misread

  • Mastercard 4853 is a broad consumer-dispute family. Stripe maps pieces of it to not-as-described, not-received, credit, and even recurring. Do not pick evidence from the code number alone if Stripe already categorized the case.
  • Visa 10.4 is the common card-absent fraud code. Visa Compelling Evidence 3.0, when Stripe flags it, is about prior non-fraud history with that cardholder — not a new kind of delivery proof.
  • Visa 10.5 (Fraud Monitoring Program) is described by Stripe as generally not contestable with evidence.
  • Unrecognized charges are sometimes their own issuer story. See unrecognized charges.