Treating every dispute notice as a stolen-card problem is the wrong way to read chargeback reason codes. A better habit starts with a processor-to-network map, where each Stripe dispute value sits beside the Visa or Mastercard condition it most likely carries.
Our view is that a store should pair every code family with evidence it can honestly produce, a refund-or-fight call, and one fix that stops the dispute coming back. The Stripe values we map are fraudulent, product_not_received, product_unacceptable, subscription_canceled, duplicate and credit_not_processed.
At Peptide Marketing HQ we build this thinking into the stores, checkouts and payment setups of research-use-only suppliers, clinics and telehealth brands. Where we name specific reason codes below, we take them from Stripe's dispute reason code categories table, checked on November 17, 2026, which lists the Visa and Mastercard codes behind each Stripe category. Stripe's category names are its own wording, not the networks'.
Key takeaways
- A reason code is the issuer's label for what the cardholder said. It tells you which evidence the network will weigh, not what happened.
- The same real-world cause can arrive under different codes. Sort disputes by cause before you decide to fight.
- For a research-use-only store, the evidence file is the page snapshot, accepted terms, invoice, descriptor and fulfillment record. It also works as a compliance check.
- Refund early when a claim is clearly valid. Pre-dispute tools help, but they never replace honest product pages and accurate descriptors.
How Visa and Mastercard group chargeback reason codes
A reason code is the issuer's label for a dispute. The cardholder tells the issuer a story, the issuer files it under a code, and we answer the code. That is why the code points to the evidence the network will look at and says little about the truth.

Visa groups its codes into four numbered families:
- Fraud (10): includes 10.4, fraud in a card-absent environment, which is where most online orders land.
- Authorization (11): problems with how the transaction was approved.
- Processing errors (12): includes 12.6.1, duplicate processing, and 12.6.2, paid by other means.
- Consumer disputes (13): includes 13.1 (merchandise or services not received), 13.2 (canceled recurring), 13.3 (not as described or defective), 13.6 (credit not processed) and 13.7 (canceled merchandise or services).
Mastercard uses four-digit codes in the same spirit. Examples are 4837 for no cardholder authorization, 4834 for errors such as a cardholder debited more than once, 4855 for a transaction that did not complete, 4860 for credit not processed and 4853 for cardholder disputes. The two schemes do not map one to one. Mastercard's 4853 is a broad bucket that covers goods not as described, goods not provided, credit not processed and recurring-transaction disputes, while Visa splits that ground across several 13.x conditions.
Your dashboard adds a third layer. Stripe's dispute reasons are the processor's own wording on top of the network code. Stripe's category table pairs them like this:
- fraudulent: Visa 10.x fraud codes, including 10.4, and Mastercard 4837
- product_not_received: Visa 13.1 and Mastercard 4855
- product_unacceptable: Visa 13.3 and Mastercard 4853
- subscription_canceled: Visa 13.2
- duplicate: Visa 12.6.1 and 12.6.2, and Mastercard 4834
- credit_not_processed: Visa 13.6 and 13.7, and Mastercard 4860
Other processors use their own labels, and Stripe updates its table, so check the current version before you rely on a pairing. The network code itself is on each dispute record.
Which codes do ecommerce stores see most?
Card-not-present stores meet a short list again and again. Each one has a plain-English meaning:
- Visa 10.4 and Mastercard 4837: the cardholder says they did not authorize the charge.
- Visa 13.1: the cardholder says the order never arrived.
- Visa 13.3: the cardholder says the item was not as described or was defective.
- Visa 13.6: the cardholder says a promised refund or credit never showed up.
- Visa 13.2: the cardholder says they canceled a recurring charge and were billed anyway.
- Visa 13.7: the cardholder says they canceled an order or service and were charged anyway.
- Visa 12.6.1 and 12.6.2: the cardholder was charged twice, or paid another way too.
What 10.4 means when the customer really ordered
Most guides skip this. A 10.4 or 4837 dispute on an order the customer genuinely placed is common. The buyer may have forgotten the purchase, a family member may have used the card, or they did not recognize the charge on their statement. Calling that customer a thief wastes time. We call it first-party misuse or a recognition failure, and we answer it differently from true third-party fraud.
Why descriptors cause “fraud” on good orders
A billing descriptor that does not match your storefront name is a classic trigger. The customer scans their statement, sees a name they do not know, and files as unauthorized. The order was legitimate, but the dispute is real. We cover that fix in our post on the billing descriptor, so we will not repeat it here.
One caution applies to all of this. A code reflects what the cardholder told the issuer, so one cause can show up under several codes. A confusing cancellation flow can appear as 13.2 one week and as fraud the next.
Build the evidence file for each family
Most guides say "submit compelling evidence" and stop. We would rather build the file before any dispute exists, family by family.

Fraud and unrecognized charges
- AVS and CVV results from the original authorization
- IP address and device records tied to the order
- Prior order history on the same account or card
- The invoice and a clean copy of the billing descriptor
Not received and processing errors
For non-receipt, we want the shipment record, the delivery confirmation and a destination that matches the order. For processing errors, we want proof of one charge, or a refund log showing the second was returned. Delivery proof shows the parcel arrived, not that the buyer was happy. Do not stretch it further than that.
Not as described
For a research-use-only store, the file holds a snapshot of the exact product page shown at purchase. It also holds the research-use-only terms the buyer accepted at checkout, the invoice and any batch documentation. It makes no claim about what the product does.
Wording matters here. Product copy that implies human use, diagnosis or outcomes makes a 13.3-style dispute much harder to defend. The same copy is an underwriting problem. So the evidence file doubles as a compliance check: if you would be embarrassed to show the snapshot to a processor, fix the page first.
Keep one exportable record
In WooCommerce, keep order notes, status history, refund entries, subscription cancellations and customer emails together. Export them into one record per order, not a folder of screenshots. A screenshot is easy to challenge, while a timestamped export is easier to trust.
Should you refund, accept the loss or fight?
We sort every dispute by cause first, then decide. Our rough path looks like this:
- Third-party fraud: usually worth representing if AVS, CVV and device data line up. If they do not, accept the loss and tighten screening.
- First-party misuse: represent only if prior orders and the descriptor are clean. Otherwise a quick refund is cheaper than a long fight.
- Genuine non-receipt: refund or reship. Fight only when delivery proof matches the destination.
- Product-description dispute: fight only if the page snapshot and accepted terms are clean and claim-free. If the copy overreaches, refund and fix the page.
- Our own processing error: refund at once and log the root cause.
Refund early when a claim is clearly valid. Dispute fees and ratio monitoring mean a lost fight can cost more than the order. We keep the ratio side in our Visa VAMP post, so we will not restate thresholds here.
Friendly fraud is a real part of the problem for many stores. We are not quoting a share here, because the figures that circulate come from vendor surveys rather than Visa or Mastercard data, so check your own dispute records instead. Friendly fraud is a reason to keep good records, not a reason to assume every customer is lying.
Recurring billing changes the weighting. For clinics and telehealth brands, cancellation records, consent and renewal reminders matter more than shipping proof. We run a compliance review before payment onboarding, because a billing model that cannot show consent will lose these disputes however good the evidence file is.
Where RDR and alerts fit before representment
Rapid Dispute Resolution (RDR), from Visa's Verifi, and chargeback alerts are pre-dispute tools. RDR refunds a disputed Visa transaction automatically under rules the merchant sets in advance, such as "refund anything under this amount" or "refund when the order is already canceled", so no chargeback is created. Visa's VAMP fact sheet (2025) excludes disputes resolved this way from the VAMP ratio. Ethoca Alerts do a similar early-warning job on the Mastercard side.
The practical question for a founder is simple. Which cases would you auto-refund anyway? Duplicate charges, canceled orders and clearly valid non-receipt claims are the usual candidates. Using these tools well needs a processor that supports them, and vendor prices change, so check their pages directly.
One line stays firm. These tools deal with disputes after the sale. They never replace honest product pages, accurate descriptors and clean order records.
Fix the cause behind each code
Each family has a control that prevents it:
- Unrecognized charges and fraud: a descriptor that matches your storefront and checkout language that tells the buyer what will appear on their statement.
- Not received: a clear shipping and tracking process, with confirmation emails that include the destination.
- Not as described: product copy with no claims about human use, diagnosis or outcomes, plus accepted research-use-only terms.
- Credit not processed: a visible refund path and a refund log your team actually updates.
- Canceled: a cancellation flow that is easy to find, with confirmation emails you can export.
Our peptide chargeback prevention post covers the tactics in more detail. Our peptide payment processing page covers backup routing and payment orchestration. A second route helps resilience when one processor pauses you. It never hides product type, and we will not advise anyone to disguise the product or the descriptor. We also make no claim that any certification covers research-use-only sellers.
A code is usually a symptom of the whole system: site copy, descriptors, fulfillment, support, compliance and payments. That is why we work as one accountable team for the whole chain a peptide store needs to stay live: a compliant site built for underwriting review, high-risk payment processing with a backup route, SEO, email, labels and packaging.
If your last batch of chargeback reason codes looked like a mixed bag, our free store audit is a low-pressure way to see which family is driving it.
Frequently asked questions
What are chargeback reason codes?
They are labels the issuer attaches to a dispute. They tell the card network which rules and evidence apply. They reflect what the cardholder said, not necessarily what happened.
Is a Stripe dispute reason the same as the Visa or Mastercard code?
No. Values like fraudulent or product_not_received are Stripe's own wording layered on the network condition. They usually sit near a specific Visa or Mastercard code, but check Stripe's current documentation for the exact values.
What does Visa 10.4 mean when the customer placed the order?
It means the cardholder told the issuer they did not authorize the charge. On a real order, the cause is often a forgotten purchase, a family member or an unrecognized descriptor. Check the descriptor and prior order history before you decide whether to fight.
Should I fight every chargeback?
No. Refund clear valid claims early, and represent only when your evidence answers the specific code. A weak file, or product copy that overreaches, can make the loss and the processor risk worse.
Do RDR and chargeback alerts replace good evidence?
No. As Visa and vendors describe them, they resolve some cases before a formal chargeback. Honest product pages, accurate descriptors and clean order records still decide the cases that remain.

