A reason code is the start of an investigation. It helps you identify the kind of claim being made, but it does not replace the cardholder’s explanation or the transaction record. The most useful response plan connects the category, the allegation and the evidence your business can actually provide.
Read the code and the complaint together
Capture the network, raw reason code, processor category and any available claim details. Keep the original labels even if you use a simpler internal category for reporting. That preserves the route back to the authoritative case record.
Stripe groups network reason codes into broader categories and provides category-specific evidence guidance. Use the guidance for the actual payment method and case. Similar-looking labels across providers do not necessarily mean identical response requirements.
Write the question the evidence must answer
Before requesting documents, turn the allegation into a plain-language question. This step keeps the team focused and makes missing evidence easier to spot. The working question can change when the claim details reveal more context.
- Product not received: What do the records show about the promised and actual delivery?
- Subscription canceled: What was requested, when did it take effect and how did billing proceed?
- Duplicate payment: Do the charges represent separate purchases, an error or a later correction?
- Credit not processed: What refund or credit was promised, and what is its recorded status?
- Unauthorized payment: Which available records address authorization rather than merely successful processing?
These questions organize your review; they are not a universal evidence checklist. Follow the current processor instructions and include the additional details needed for the particular allegation.
Request records with a purpose
Send each evidence owner a specific request. State the case reference, the fact being investigated, the record needed and your internal due date. A fulfillment team can respond more effectively to “find the delivery event associated with this tracking number” than to “prove the customer is wrong.”
Record where each item came from. If a screenshot relies on information that changes over time, preserve the relevant date and context. Avoid changing a source record merely to make the response look more persuasive.
Distinguish relevance from volume
Review every proposed attachment against the working question. A large collection of unrelated records can obscure the strongest facts. Use the minimum context needed to explain each event accurately, and keep the full internal source available according to your retention policy.
A general policy page may explain the business’s normal process, but it might not establish what happened to this customer. A current account screenshot may need a dated activity record. Ask what the document proves and what it leaves unresolved before adding it to the packet.
Example: the delivery record does not answer the claim
Consider a case labeled “product unacceptable.” The warehouse provides a delivery scan and the team begins drafting a non-delivery response. Reading the available complaint shows that the customer acknowledges receipt but says the product differs from its description.
The evidence plan now needs the purchase description, relevant product records, the complaint and the resolution history. The delivery scan may establish chronology, but it does not answer the central allegation. This fictional example shows why a code should be read alongside the underlying claim.
Use reason codes to improve the business
After cases close, review recurring categories with the teams that own the customer experience. Keep raw codes and plain-language causes separate. Several cancellation disputes may come from one missed support handoff, while similar-looking complaints in another brand may have a different cause.
Record one action, an owner and a review date for each confirmed pattern. Consistent categorization helps reporting, but the operating improvement comes from understanding the events behind the label.