Guide

Chargeback reason codes: Visa, Mastercard, Amex and Discover

By · Updated

A reason code says what the customer told their bank: that they didn't make the purchase, it never arrived, it wasn't as described. Here are the 94 codes we cover (24 Visa, 16 Mastercard, 38 American Express, 16 Discover), with what each claims. Choose what you sell to see the evidence that answers each one for your business.

Draft my response free3 free drafts, no card. Nothing is sent without your approval.

How each network's process and time limits work: Visa chargebacks, Mastercard chargebacks, American Express chargebacks, and Discover chargebacks.

What you sell

Choose one to see the evidence for your kind of business, most important first.

94 codes.

Visa reason codes

Visa 10.1: EMV Liability Shift Counterfeit Fraud

The cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read (entry mode) and the authorizationThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 10.1 chargeback (EMV counterfeit card fraud)

Visa 10.2: EMV Liability Shift Non-Counterfeit Fraud

The cardholder says they didn't make an in-person purchase made with their card after it was lost, stolen, or never received.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read, the PIN verified, and the terminalThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 10.2 chargeback (lost or stolen card, chip and PIN)

Visa 10.3: Other Fraud — Card-Present Environment

The cardholder says they didn't make a purchase that was keyed in at the point of sale.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the swipe or chip read and the authorization, or the manual imprintThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 10.3 chargeback (card-present fraud, keyed sale)

Visa 10.4: Other Fraud — Card-Absent Environment

The cardholder says they didn't authorize an online or other card-not-present payment.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • 3D Secure authentication (Every seller)The cardholder completed their bank's identity check at checkout.For this code: If the payment was authenticatedState that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.
  • Earlier payments from the same customer (Every seller)The same customer paid before without disputing, linking this purchase to a known buyer.For this code: Showing the same customer paid before without disputingList each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer IP address and device (Every seller)The purchase came from an IP address or device linked to the cardholder's other activity.For this code: Showing the IP address or device matches earlier activityGive the purchase IP and show the same IP or device on logins or earlier orders.
  • Customer account history (Every seller)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.For this code: Showing the account is tied to the cardholder's emailAccount creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing messages from the cardholder's email about this orderThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Address and security-code checks (Every seller)The billing postcode and card security code entered matched the bank's records.For this code: Showing the address and security-code results, as supporting detail onlyReport the check results as Stripe recorded them. Supporting evidence only, never the main argument.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the billing address or an address used on earlier undisputed ordersThe carrier's delivery record showing date, address, and any signature or photo.
  • Billing and shipping addresses match (Physical goods)The order was sent to the cardholder's own billing address or a previously used address.Show both addresses side by side.
  • Access granted or digital product delivered (Digital products and subscriptions)The customer was given what they bought — an account, a login, a download link, a license key.For this code: Showing it was sent to the cardholder's emailThe delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing use from the same IP address or device as the purchaseDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the cardholder attended or received the workDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreement is in the cardholder's nameThe signed document with the signature and the relevant clauses marked.

Visa 10.4 chargeback (fraud, card not present)

Visa 10.5: Visa Monitoring Programs

A Visa monitoring program flagged this payment, and the issuer is disputing it under that program rather than on a specific claim.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing the refund's amount and dateRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the cardholder withdrew the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 10.5 chargeback (Visa monitoring programs)

Visa 11.1: Card Recovery Bulletin

The issuer says the payment was taken without an approval, on a card listed in Visa's Card Recovery Bulletin.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approvalThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: For an in-person sale at an EMV terminalThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 11.1 chargeback (Card Recovery Bulletin)

Visa 11.2: Declined Authorization

The issuer says the payment was processed after its approval request was declined or the card was to be picked up.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval and its codeThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: For a chip approval offlineThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Visa 11.2 chargeback (declined authorization)

Visa 11.3: No Authorization / Late Presentment

The issuer says the payment was taken without the approval it needed, or for more than was approved, or was sent for settlement too late.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, its amount, and when the payment was capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale dateThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Visa 11.3 chargeback (no authorization, late presentment)

Visa 12.1: Late Presentment

The issuer says the payment was sent for settlement after the time limit (for transactions up to 12 April 2024; later ones fall under 11.3).

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale dateThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing when the payment was approved and capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 12.1 chargeback (late presentment)

Visa 12.2: Incorrect Transaction Code

The issuer says the payment was processed with the wrong transaction type: a sale instead of a refund or the reverse, or a refund instead of a reversal.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the saleThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing it as a saleThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: For a refund that was a refundRefund date, amount, and reference.

Visa 12.2 chargeback (incorrect transaction code)

Visa 12.3: Incorrect Currency

The issuer says the payment was processed in the wrong currency, or converted to the cardholder's currency without their agreement.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the currencyThe receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the currency shown and chosen at checkoutA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 12.3 chargeback (incorrect currency)

Visa 12.4: Incorrect Account Number

The issuer says the payment was processed on the wrong card number.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the card endingThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approvalThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 12.4 chargeback (incorrect account number)

Visa 12.5: Incorrect Amount

The cardholder says the amount charged is wrong: miscalculated, keyed wrongly, or changed after the sale without their agreement.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the amount (an invoice also works), and for a tip, the receipt the cardholder signed with the tip they wrote in (it shows the final amount they agreed to)The receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing what the customer agreed to at checkoutA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the customer agreed to any changeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Visa 12.5 chargeback (incorrect amount)

Visa 12.6.1: Duplicate Processing

The cardholder says they were charged more than once for the same purchase.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Both charges side by side with what each paid forBoth charges side by side with what each one paid for.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what each charge paid forThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If one charge was refundedRefund date, amount, and reference.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing each order was deliveredThe carrier's delivery record showing date, address, and any signature or photo.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.For this code: Showing different billing periods, upgrades, or prorationsStart date, plan, each charge date and amount, status.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing each session or deliverable was providedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Visa 12.6.1 chargeback (duplicate processing)

Visa 12.6.2: Paid by Other Means

The cardholder says they paid for the purchase another way: cash, a check, another card, or another payment on the same card.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the purchase was paid only by this charge, or that the other payment was for something elseThe receipt or invoice sent to the customer.
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Showing the purchase was paid only by this charge, or that the other payment was for something elseBoth charges side by side with what each one paid for.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 12.6.2 chargeback (paid by other means)

Visa 12.7: Invalid Data

The issuer says the approval request carried invalid or incorrect data: the date, merchant category, merchant name, country, or another required field.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale's detailsThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approvalThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 12.7 chargeback (invalid data)

Visa 13.1: Merchandise/Services Not Received

The cardholder says they didn't receive the goods or services they paid for.

In Stripe: The customer says they didn't receive what they paid for

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing what was promised and whenA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the customer acknowledged receipt or asked how to use itThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Shipping and tracking details (Physical goods)The goods were shipped, when, by which carrier.Carrier, tracking number, ship date.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the order address, with a signature for high-value ordersThe carrier's delivery record showing date, address, and any signature or photo.
  • Access granted or digital product delivered (Digital products and subscriptions)The customer was given what they bought — an account, a login, a download link, a license key.The delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing when the customer accessed or used what they bought, with datesDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreed scope and datesThe signed document with the signature and the relevant clauses marked.

Visa 13.1 chargeback (merchandise or services not received)

Visa 13.2: Canceled Recurring Transaction

The cardholder says they cancelled a recurring payment and were charged afterwards.

In Stripe: The customer says they cancelled but were still charged

Evidence that answers it
  • Recurring billing agreed at signup (Every seller)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.Quote the cancellation steps and notice period as shown at signup.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: Stating plainly if no request was receivedA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Subscription billing history (Every seller)When the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.
  • Renewal reminders sent (Every seller)The customer was told before the charge that the subscription would renew.The reminder email with its send date and recipient address.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the boxes shipped in the disputed period were deliveredThe carrier's delivery record showing date, address, and any signature or photo.
  • Use after the disputed charge (Digital products and subscriptions)The customer kept using the product or service after the charge they now dispute.For this code: Logins or use after the disputed chargeActivity dated after the charge date, with the charge date stated for comparison.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing work was delivered in the billed periodDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Visa 13.2 chargeback (cancelled recurring transaction)

Visa 13.3: Not as Described or Defective Merchandise/Services

The cardholder says what they received was defective, damaged, or not as described.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Captured as it was at the time of saleA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the seller's response and any offer to fix or replaceThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: No return received, or a return outside the policyState whether a return was received, when, and in what condition, with any return tracking.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.The carrier's delivery record showing date, address, and any signature or photo.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing substantial useDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing what was deliveredDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreed scopeThe signed document with the signature and the relevant clauses marked.

Visa 13.3 chargeback (not as described or defective)

Visa 13.4: Counterfeit Merchandise

The cardholder says the goods were counterfeit, and the claim is backed by the brand's owner, customs, law enforcement, another government agency, or a neutral expert.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Supplier invoice or certificate of authenticity (Every seller)Where the item came from: the seller bought it from the brand or an authorized supplier, or a certificate of authenticity covers it. It answers a claim that the goods were counterfeit (Visa 13.4).For this code: Showing the item is genuine: supplier invoices or certificates of authenticity for itThe supplier's invoice for the stock the item came from, or the certificate of authenticity for it, with the style code, model or SKU that matches the customer's receipt.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Visa 13.4 chargeback (counterfeit merchandise)

Visa 13.5: Misrepresentation

The cardholder says the terms of sale were misrepresented: for online sellers, most often an offer that suggested income, or a trial or one-off purchase that went on billing without clear notice.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing the terms as presentedA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the terms as presentedA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Recurring billing agreed at signup (Every seller)The customer agreed to be charged repeatedly, at a stated amount and interval.For this code: Showing the customer agreed to, and was told about, further charges after a trial or one-off purchaseThe signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Renewal reminders sent (Every seller)The customer was told before the charge that the subscription would renew.For this code: Showing the customer agreed to, and was told about, further charges after a trial or one-off purchaseThe reminder email with its send date and recipient address.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Visa 13.5 chargeback (misrepresentation)

Visa 13.6: Credit Not Processed

The cardholder says a refund or credit they were promised hasn't arrived.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing the credit or reversal, with its date, amount, method and referenceRefund date, amount, and reference.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing that credit is tied to the disputed paymentThe receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the credit confirmation the cardholder holds is for a different purchase, or, dated after the dispute opened, saying they no longer dispute itThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.For this code: Showing the cardholder didn't meet the policy's conditions, used only when the seller never confirmed a creditThe policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the cardholder didn't meet the policy's conditions, used only when the seller never confirmed a creditA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: When the promised credit depended on a return that never arrivedState whether a return was received, when, and in what condition, with any return tracking.

Visa 13.6 chargeback (credit not processed)

Visa 13.7: Cancelled Merchandise/Services

The cardholder says they cancelled an order or service, or returned goods, and are owed a credit that hasn't been issued.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.For this code: With terms accepted at checkout showing it was disclosed before final checkout with a click to acceptThe policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.For this code: With terms accepted at checkout showing it was disclosed before final checkout with a click to acceptQuote the cancellation steps and notice period as shown at signup.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: Showing the cardholder didn't cancel, or didn't cancel the way the policy saysA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a credit issued under the termsRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the cardholder withdrew the dispute, dated after it openedThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: Showing goods shipped before the cancellation weren't returned. A return also limits the dispute to the value of what came backState whether a return was received, when, and in what condition, with any return tracking.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing use before cancelling, which limits the dispute to the unused partDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.For this code: Showing which period the disputed charge covers compared with the cancellation dateStart date, plan, each charge date and amount, status.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing work done before the cancellationDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the cancellation terms the cardholder acceptedThe signed document with the signature and the relevant clauses marked.

Visa 13.7 chargeback (cancelled merchandise or services)

Visa 13.8: Original Credit Transaction Not Accepted

A payment sent to the card (an original credit, such as a payout) wasn't accepted by the cardholder or their bank.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing the credit was reversed (any record of the reversal works)Refund date, amount, and reference.

Visa 13.8 chargeback (original credit not accepted)

Mastercard reason codes

Mastercard 4807: Warning Bulletin File

The issuer says the payment was taken without approval on a card listed in Mastercard's warning bulletin.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, its code, and when the payment was capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4807 chargeback (warning bulletin file)

Mastercard 4808 (also 08): Authorization-Related

The issuer says the payment wasn't approved, was approved after a decline, was settled after its approval expired, or was one of several clearings made on one approval.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, its code, and when the payment was capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4808 chargeback (authorization-related)

Mastercard 4831: Transaction Amount Differs

The cardholder says the amount charged differs from the amount they agreed to.

Not in Mastercard's current Chargeback Guide; Stripe still lists it. Mastercard now handles this claim as 4834.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the amount (an invoice also works)The receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the customer agreed to any changeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Mastercard 4831 chargeback (transaction amount differs)

Mastercard 4834 (also 34): Point-of-Interaction Error

Usually that the cardholder was charged more than once for the same purchase, but this code covers several processing errors.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Showing the charges side by side as two valid, separate transactions (Mastercard requires an explanation when the documents don't show it on their own)Both charges side by side with what each one paid for.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what each charge was for, its amount and its currencyThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a refund made before the disputeRefund date, amount, and reference.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the amount and currency the customer agreed to at checkoutA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the other payment the cardholder names paid for something elseThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing each order was delivered, as documentation of separate transactionsThe carrier's delivery record showing date, address, and any signature or photo.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.For this code: Showing different billing periods, upgrades or prorationsStart date, plan, each charge date and amount, status.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing each session or deliverable was providedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: In the EEA and the UK, with a price list or a maximum per payment that the charge stayed withinThe signed document with the signature and the relevant clauses marked.
  • Recurring billing agreed at signup (Services)The customer agreed to be charged repeatedly, at a stated amount and interval.For this code: In the EEA and the UK, with a price list or a maximum per payment that the charge stayed withinThe signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.

Mastercard 4834 chargeback (point-of-interaction error)

Mastercard 4837 (also 37): No Cardholder Authorization

The cardholder says they didn't authorize the payment.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the cardholder took part in the purchase (Mastercard names letters, emails, texts and chat messages)The relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • 3D Secure authentication (Every seller)The cardholder completed their bank's identity check at checkout.For this code: If the payment was authenticated with Mastercard Identity CheckState that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.
  • Address and security-code checks (Every seller)The billing postcode and card security code entered matched the bank's records.For this code: When the address check answered X or Y and the goods went to that confirmed addressReport the check results as Stripe recorded them. Supporting evidence only, never the main argument.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery signed for by the cardholder, or to the address the address check confirmedThe carrier's delivery record showing date, address, and any signature or photo.
  • Billing and shipping addresses match (Physical goods)The order was sent to the cardholder's own billing address or a previously used address.Show both addresses side by side.
  • Access granted or digital product delivered (Digital products and subscriptions)The customer was given what they bought — an account, a login, a download link, a license key.For this code: Showing the goods were delivered electronically, with the cardholder's written confirmation that they registered to receive electronic delivery. Only when buyers must register with a password or other authentication before buying (never a guest checkout): customer account history showing the registration, earlier payments from the same customer before or after the disputed one, customer ip address and device from a registered device and IP address, and access and usage log showing the goods or services were used. For a recurring charge: recurring billing agreed at signup showing the cardholder clicked to accept the recurring terms, and subscription billing history with the start dateThe delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Customer account history (Digital products and subscriptions)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Earlier payments from the same customer (Digital products and subscriptions)The same customer paid before without disputing, linking this purchase to a known buyer.List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer IP address and device (Digital products and subscriptions)The purchase came from an IP address or device linked to the cardholder's other activity.Give the purchase IP and show the same IP or device on logins or earlier orders.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Recurring billing agreed at signup (Digital products and subscriptions)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: A work order or other document signed by the cardholder showing they received the serviceThe signed document with the signature and the relevant clauses marked.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Mastercard 4837 chargeback (no cardholder authorization)

Mastercard 4841: Cancelled Recurring or Digital Goods Transaction

The cardholder says they cancelled a recurring payment and were charged afterwards, or disputes a small digital-goods purchase.

Not in Mastercard's current Chargeback Guide; Stripe still lists it. Mastercard now handles this claim as 4853.

In Stripe: The customer says they cancelled but were still charged

Evidence that answers it
  • Recurring billing agreed at signup (Every seller)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.Quote the cancellation steps and notice period as shown at signup.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: Stating plainly if no request was receivedA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Subscription billing history (Every seller)When the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.
  • Renewal reminders sent (Every seller)The customer was told before the charge that the subscription would renew.The reminder email with its send date and recipient address.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the boxes shipped in the disputed period were deliveredThe carrier's delivery record showing date, address, and any signature or photo.
  • Use after the disputed charge (Digital products and subscriptions)The customer kept using the product or service after the charge they now dispute.For this code: Logins or use after the disputed chargeActivity dated after the charge date, with the charge date stated for comparison.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing work was delivered in the billed periodDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Mastercard 4841: cancelled recurring or digital goods

Mastercard 4842: Late Presentment

The issuer says the payment was sent for settlement after the time limit.

Not in Mastercard's current Chargeback Guide; Stripe lists it as deprecated.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale dateThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing when it was approved and capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4842 chargeback (late presentment)

Mastercard 4846: Correct Transaction Currency Code Not Provided

The issuer says the payment was processed in the wrong currency, or converted without the cardholder's agreement.

Not in Mastercard's current Chargeback Guide; Stripe lists it as deprecated. Mastercard now handles this claim as 4834.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the currencyThe receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the currency shown and chosenA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4846 chargeback (wrong currency code)

Mastercard 4849 (also 49): Questionable Merchant Activity

Mastercard listed the seller's business under its Questionable Merchant Audit Program or its Coercion Program, and the issuer is disputing the payment under that program.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4849 chargeback (questionable merchant activity)

Mastercard 4853 (also 53): Cardholder Dispute

A broad code covering several cardholder claims. Most often: the goods or services were defective or not as described.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing the listing as it read at the time of sale, and that what was delivered matched itA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the seller offered a repair, replacement or price adjustment, or the customer confirmed it arrived in good conditionThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a refund made before the disputeRefund date, amount, and reference.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the condition was disclosed at sale (as is, refurbished), or that the seller kept the guarantee or return policy the customer citesA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.For this code: Showing the condition was disclosed at sale (as is, refurbished), or that the seller kept the guarantee or return policy the customer citesThe policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the goods arrived and were signed forThe carrier's delivery record showing date, address, and any signature or photo.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: When the customer never said the goods were available for pickup or returnState whether a return was received, when, and in what condition, with any return tracking.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing the product was delivered and worked as described. For digital goods of USD 25 or less: terms accepted at checkout and customer account history as dated screenshots of the purchase controls in place at the time (purchases off by default, a sign-in window of no more than 15 minutes, and confirm or cancel with the total shown)Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Terms accepted at checkout (Digital products and subscriptions)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Customer account history (Digital products and subscriptions)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the service was provided as the invoice or contract describedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreed scopeThe signed document with the signature and the relevant clauses marked.

Mastercard 4853 chargeback (cardholder dispute)

Mastercard 4854: Cardholder Dispute, Not Elsewhere Classified (US)

A US cardholder has a complaint about a purchase that no other Mastercard code covers, tried to resolve it with the seller, and the seller refused to adjust the price, repair or replace the goods, or give a credit.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the complaint and what the seller offeredThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing what was agreedA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what was agreedThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a refund or partial credit was givenRefund date, amount, and reference.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.The carrier's delivery record showing date, address, and any signature or photo.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: If the goods came backState whether a return was received, when, and in what condition, with any return tracking.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing useDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing what was agreedThe signed document with the signature and the relevant clauses marked.

Mastercard 4854 chargeback (US cardholder dispute)

Mastercard 4855: Goods or Services Not Provided

The cardholder says the goods or services weren't provided.

Not in Mastercard's current Chargeback Guide; Stripe still lists it. Mastercard now handles this claim as 4853.

In Stripe: The customer says they didn't receive what they paid for

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing what was promised and whenA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the customer acknowledged receipt or asked how to use itThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Shipping and tracking details (Physical goods)The goods were shipped, when, by which carrier.Carrier, tracking number, ship date.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the order address, with a signature for high-value ordersThe carrier's delivery record showing date, address, and any signature or photo.
  • Access granted or digital product delivered (Digital products and subscriptions)The customer was given what they bought — an account, a login, a download link, a license key.The delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing when the customer accessed or used what they bought, with datesDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreed scope and datesThe signed document with the signature and the relevant clauses marked.

Mastercard 4855 chargeback (goods or services not provided)

Mastercard 4860: Credit Not Processed

The cardholder says a refund for a return, cancellation, or promised credit wasn't processed.

Not in Mastercard's current Chargeback Guide; Stripe still lists it. Mastercard now handles this claim as 4853.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a refund or credit was already issuedRefund date, amount, and reference.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing what was and wasn't promisedThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: No return received, or a return outside the policyState whether a return was received, when, and in what condition, with any return tracking.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing use before the refund requestDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the work was delivered before cancellationDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the cancellation termsThe signed document with the signature and the relevant clauses marked.

Mastercard 4860 chargeback (credit not processed)

Mastercard 4863: Cardholder Does Not Recognize — Potential Fraud

The cardholder doesn't recognize the transaction on their statement. It can be a real purchase under a name they don't know.

Not in Mastercard's current Chargeback Guide; Stripe still lists it.

In Stripe: The customer doesn't recognize the charge

Evidence that answers it
  • How the statement name links to the seller (Every seller)The name on the customer's statement belongs to the business they bought from.For this code: The statement name, the brand the customer bought from, and the websiteThe descriptor as it appears on statements, the business and brand name, and the website.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing it was sent to the cardholder's emailThe receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing messages with the cardholder about this orderThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Earlier payments from the same customer (Every seller)The same customer paid before without disputing, linking this purchase to a known buyer.For this code: Showing the same customer paid before without disputingList each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer account history (Every seller)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the cardholder's addressThe carrier's delivery record showing date, address, and any signature or photo.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing activity on the cardholder's own accountDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Mastercard 4863 chargeback (doesn't recognize the charge)

Mastercard 4870 (also 70): Chip Liability Shift

The cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read (entry mode) and the authorizationThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4870 chargeback (chip liability shift)

Mastercard 4871 (also 48): Chip/PIN Liability Shift: Lost, Stolen, or Never-Received

The cardholder says someone else used their card for an in-person purchase after it was lost, stolen, or never received.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read, the PIN verified, and the terminalThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Mastercard 4871 chargeback (chip and PIN, lost or stolen)

American Express reason codes

American Express A01: Charge Amount Exceeds Authorization Amount

The issuer says the amount charged is more than the amount approved.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approved amountThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex A01 chargeback (amount exceeds authorization)

American Express A02: No Valid Authorization

The issuer says the payment had no valid approval.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, its code, and when the payment was capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a credit that offsets the charge was already processedRefund date, amount, and reference.

Amex A02 chargeback (no valid authorization)

American Express A08: Authorization Approval Expired

The issuer says the payment was settled after its approval expired.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, its code, and when the payment was capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex A08 chargeback (authorization approval expired)

American Express C02: Credit Not Processed

The cardholder says a refund or credit they were promised hasn't arrived.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a refund or credit was already issuedRefund date, amount, and reference.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing what was and wasn't promisedThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: No return received, or a return outside the policyState whether a return was received, when, and in what condition, with any return tracking.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing use before the refund requestDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the work was delivered before cancellationDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the cancellation termsThe signed document with the signature and the relevant clauses marked.

Amex C02 chargeback (credit not processed)

American Express C04: Goods or Services Returned or Refused

The cardholder says they returned the goods or refused delivery, and weren't refunded.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Return status (Every seller)Whether the goods were returned, and whether the return followed the policy.For this code: Showing whether a return arrivedState whether a return was received, when, and in what condition, with any return tracking.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing any refund already madeRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex C04 chargeback (goods returned or refused)

American Express C05: Goods or Services Cancelled

The cardholder says they cancelled the order and were charged anyway.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.Quote the cancellation steps and notice period as shown at signup.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: Showing when the cancellation cameA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing any refund already madeRefund date, amount, and reference.

Amex C05 chargeback (goods or services cancelled)

American Express C08: Goods/Services Not Received or Only Partially Received

The cardholder says the goods or services weren't received, or only part of the order was.

In Stripe: The customer says they didn't receive what they paid for

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a credit already processed that directly offsets the disputed chargeRefund date, amount, and reference.
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Showing what was ordered and the agreed delivery dateA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what was ordered and the agreed delivery dateThe receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Refuting a claimed cancellation or return, or linking the person who received the order to the card memberThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the delivery date and the full shipping addressThe carrier's delivery record showing date, address, and any signature or photo.
  • Billing and shipping addresses match (Physical goods)The order was sent to the cardholder's own billing address or a previously used address.For this code: Showing the order went to the address the card member gaveShow both addresses side by side.
  • Shipping and tracking details (Physical goods)The goods were shipped, when, by which carrier.For this code: Showing the shipment's tracking, together with the delivery recordCarrier, tracking number, ship date.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: When the card member says the goods were returned and they weren'tState whether a return was received, when, and in what condition, with any return tracking.
  • Customer IP address and device (Digital products and subscriptions)The purchase came from an IP address or device linked to the cardholder's other activity.For this code: Showing the IP address at purchase matches the one that downloadedGive the purchase IP and show the same IP or device on logins or earlier orders.
  • Access granted or digital product delivered (Digital products and subscriptions)The customer was given what they bought — an account, a login, a download link, a license key.For this code: Showing delivery to the email given at purchaseThe delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing the card member used the site after the purchase date, with the date and timeDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the dates the services were providedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the card member signed for the work, such as a completed work orderThe signed document with the signature and the relevant clauses marked.
  • Cancellation history (Services)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: When the card member says they cancelled and didn'tA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.

Amex C08 chargeback (goods or services not received)

American Express C14: Paid by Other Means

The cardholder says they paid for the purchase another way.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing this charge was the only payment, or that the other payment was for something elseThe receipt or invoice sent to the customer.
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Showing this charge was the only payment, or that the other payment was for something elseBoth charges side by side with what each one paid for.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a credit that offsets the card charge was already processedRefund date, amount, and reference.

Amex C14 chargeback (paid by other means)

American Express C18: "No Show" or CARDeposit Cancelled

The cardholder says a reservation or deposit was cancelled, or they were charged for not showing up.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Signed contract or agreement (Every seller)The customer agreed in writing to the scope, price, and terms.For this code: Showing the cancellation and no-show terms the cardmember acceptedThe signed document with the signature and the relevant clauses marked.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the cancellation and no-show terms the cardmember acceptedA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.A dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex C18 chargeback (no-show or deposit cancelled)

American Express C28: Canceled Recurring Billing

The cardholder says they cancelled recurring billing and were charged afterwards.

In Stripe: The customer says they cancelled but were still charged

Evidence that answers it
  • Recurring billing agreed at signup (Every seller)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.Quote the cancellation steps and notice period as shown at signup.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.For this code: Stating plainly if no request was receivedA dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Subscription billing history (Every seller)When the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.
  • Renewal reminders sent (Every seller)The customer was told before the charge that the subscription would renew.The reminder email with its send date and recipient address.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the boxes shipped in the disputed period were deliveredThe carrier's delivery record showing date, address, and any signature or photo.
  • Use after the disputed charge (Digital products and subscriptions)The customer kept using the product or service after the charge they now dispute.For this code: Logins or use after the disputed chargeActivity dated after the charge date, with the charge date stated for comparison.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing work was delivered in the billed periodDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Amex C28 chargeback (canceled recurring billing)

American Express C31: Goods/Services Not as Described

The cardholder says the goods or services weren't as described.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.For this code: Captured as it was at the time of saleA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing the seller's response and any offer to fix or replaceThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Return status (Physical goods)Whether the goods were returned, and whether the return followed the policy.For this code: No return received, or a return outside the policyState whether a return was received, when, and in what condition, with any return tracking.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.The carrier's delivery record showing date, address, and any signature or photo.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing substantial useDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing what was deliveredDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreed scopeThe signed document with the signature and the relevant clauses marked.

Amex C31 chargeback (goods or services not as described)

American Express C32: Goods or Services Damaged or Defective

The cardholder says the goods or services were damaged or defective.

In Stripe: The customer says it wasn't as described or was defective

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.A capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Proof of delivery (Every seller)The goods arrived at the customer's address.For this code: Showing the condition it shipped in, with photosThe carrier's delivery record showing date, address, and any signature or photo.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing an offered fix, replacement, or returnThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.

Amex C32 chargeback (damaged or defective goods)

American Express F10: Missing Imprint

The cardmember says they didn't take part in the charge, and the seller hasn't provided an imprint of the card.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a credit, processed before the dispute, that directly offsets the disputed chargeRefund date, amount, and reference.
  • Receipt or invoice (Physical goods)What was bought, the amount, and the date.For this code: Showing how it was ordered: for an order placed online, by phone or by mail, the order confirmationThe receipt or invoice sent to the customer.
  • Customer IP address and device (Physical goods)The purchase came from an IP address or device linked to the cardholder's other activity.For this code: Showing the order was placed online through the checkout, not in personGive the purchase IP and show the same IP or device on logins or earlier orders.
  • Terms accepted at checkout (Digital products and subscriptions)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the order came through the online checkout and the card wasn't presented in personA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Customer IP address and device (Digital products and subscriptions)The purchase came from an IP address or device linked to the cardholder's other activity.For this code: Showing where and on what device the order was placed at the online checkoutGive the purchase IP and show the same IP or device on logins or earlier orders.
  • Receipt or invoice (Services)What was bought, the amount, and the date.For this code: Showing when and how it was paid: for a service booked and paid online, by phone or by mail, the invoice, or, for a phone or mail order keyed into a card reader, the reader's record that the card was keyed with no card read, alongside the booking that shows the order wasn't taken in personThe receipt or invoice sent to the customer.
  • Messages with the customer (Services)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing, from the time of the order, that it was booked and paid by phone, online or by mailThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Terms accepted at checkout (Services)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the order came through an online checkout and wasn't taken in personA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.

Amex F10 chargeback (missing imprint)

American Express F24: No Cardmember Authorization

The cardholder denies making or knowing about the charge.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing a credit already processed, the only response Amex listsRefund date, amount, and reference.
  • 3D Secure authentication (Every seller)The cardholder completed their bank's identity check at checkout.For this code: Showing a SafeKey authentication of this payment, used only to contest outside Amex's listState that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.
  • Earlier payments from the same customer (Every seller)The same customer paid before without disputing, linking this purchase to a known buyer.List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer IP address and device (Every seller)The purchase came from an IP address or device linked to the cardholder's other activity.Give the purchase IP and show the same IP or device on logins or earlier orders.
  • Customer account history (Every seller)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing the goods were sent to the cardmember's address, with the order confirmationThe carrier's delivery record showing date, address, and any signature or photo.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: For use by the cardmember's own login after the charge, with the checkout and terms recordsDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing service was given to the cardmember after the charge, with the invoiceDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Amex F24 chargeback (no cardmember authorization)

American Express F29: Card Not Present

The cardholder says they didn't authorize a card-not-present payment.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Earlier payments from the same customer (Every seller)The same customer paid before without disputing, linking this purchase to a known buyer.For this code: Showing payments at your business on the same card in the 12 months before the chargebackList each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer account history (Every seller)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.For this code: Showing the card member's name and loginAccount creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Customer IP address and device (Every seller)The purchase came from an IP address or device linked to the cardholder's other activity.For this code: Showing at least two of the device ID, full IP address and confirmation email matching those earlier paymentsGive the purchase IP and show the same IP or device on logins or earlier orders.
  • Address and security-code checks (Every seller)The billing postcode and card security code entered matched the bank's records.For this code: When the address check or the card security code check answered YReport the check results as Stripe recorded them. Supporting evidence only, never the main argument.
  • 3D Secure authentication (Every seller)The cardholder completed their bank's identity check at checkout.For this code: If the payment was authenticated with Amex SafeKeyState that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the card member's billing addressThe carrier's delivery record showing date, address, and any signature or photo.
  • Billing and shipping addresses match (Physical goods)The order was sent to the cardholder's own billing address or a previously used address.For this code: Or a shipping address used on an earlier undisputed orderShow both addresses side by side.
  • Product or service as described at sale (Digital products and subscriptions)What the customer was told they were buying.For this code: Amex asks for all of these together: product or service as described at sale describing what was bought, access and usage log with the date and time the card member downloaded or accessed it, and the earlier undisputed purchase with the login and matching details above. For recurring billing started online: recurring billing agreed at signup with the card member's written agreement to periodic billing, subscription billing history with an earlier undisputed charge for the same goods, and renewal reminders sent showing how you told them about the chargeA capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.Dated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Recurring billing agreed at signup (Digital products and subscriptions)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.Start date, plan, each charge date and amount, status.
  • Renewal reminders sent (Digital products and subscriptions)The customer was told before the charge that the subscription would renew.The reminder email with its send date and recipient address.
  • Signed contract or agreement (Services)The customer agreed in writing to the scope, price, and terms.For this code: Showing the agreement is in the card member's nameThe signed document with the signature and the relevant clauses marked.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the date the service was providedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Amex F29 chargeback (card not present)

American Express F30: EMV Counterfeit

The cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read (entry mode) and the authorizationThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a credit that offsets the charge was already processedRefund date, amount, and reference.

Amex F30 chargeback (EMV counterfeit, card present)

American Express F31: EMV Lost, Stolen, or Non-Received

The cardholder says they didn't make an in-person purchase made with their card after it was lost, stolen, or never received.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read, the PIN verified, and the terminalThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If a credit that offsets the charge was already processedRefund date, amount, and reference.

Amex F31 chargeback (lost or stolen card, chip and PIN)

American Express FR2: Fraud Full Recourse Program

The cardmember denies authorizing the charge, but there is no claim for the seller to answer: the seller's account is in American Express's Fraud Full Recourse Program, which lets American Express charge back fraud disputes without the usual response.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refunded before the chargebackRefund date, amount, and reference.

Amex FR2 chargeback (Fraud Full Recourse Program)

American Express FR4: Immediate Chargeback Program

The cardmember has disputed the charge, but there is no claim for the seller to answer: the seller's account is in American Express's Immediate Chargeback Program, which charges back without a cardmember dispute being answered first.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refunded before the chargebackRefund date, amount, and reference.

Amex FR4 chargeback (Immediate Chargeback Program)

American Express FR6: Partial Immediate Chargeback Program

The cardmember has disputed the charge, but there is no claim for the seller to answer: the account is in American Express's Partial Immediate Chargeback Program, which charges back disputes up to a set amount at once.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refunded before the chargebackRefund date, amount, and reference.

Amex FR6 chargeback (Partial Immediate Chargeback)

American Express M01: Chargeback Authorization

Not a cardmember claim: the seller (or someone for them) authorized American Express to charge back, often in reply to an inquiry.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex M01 chargeback (chargeback authorization)

American Express M11: Reversal Due to Credit

Not a cardmember claim: the seller issued a credit, and American Express is reversing the original charge to match it.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex M11 chargeback (reversal due to credit)

American Express M36: See Notes

A catch-all code: the notice's own notes explain the issue.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Amex M36 chargeback (see notes): how to answer it

American Express M38: Reversal

Not a cardmember claim: American Express is reversing an earlier charge for a reason no specific code covers.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex M38 chargeback (reversal)

American Express M42: Reversal Request Too Late

Not a cardmember claim: the seller's request to reverse or refund the charge came too late to be processed normally.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex M42 chargeback (reversal request too late)

American Express OP1: General

A general code for a dispute that fits no specific one; the notice explains it.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Amex OP1 chargeback (general dispute code)

American Express P01: Unassigned Card Number

The issuer says the card number charged isn't a valid account.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the card endingThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approvalThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the card read electronically by a terminal, or an imprint confirming the card numberThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex P01 chargeback (unassigned card number)

American Express P03: Credit Processed as Charge

The cardholder says a refund owed to them was processed as a charge.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the saleThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing it as a saleThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing any refund already madeRefund date, amount, and reference.

Amex P03 chargeback (credit processed as charge)

American Express P04: Charge Processed as Credit

The issuer says a charge was processed as a refund.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: For a refund that was a refundRefund date, amount, and reference.

Amex P04 chargeback (charge processed as credit)

American Express P05: Incorrect Charge Amount

The cardholder says the amount charged is wrong.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the amount (an invoice also works)The receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Agreeing to any changeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Amex P05 chargeback (incorrect charge amount)

American Express P07: Late Submission

The issuer says the payment was submitted for settlement late.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale dateThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing when it was approved and capturedThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex P07 chargeback (late submission)

American Express P08: Duplicate Charge

The cardholder says they were charged more than once for the same purchase.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Both charges side by side with what each paid forBoth charges side by side with what each one paid for.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what each charge paid forThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If one charge was refundedRefund date, amount, and reference.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing each order was deliveredThe carrier's delivery record showing date, address, and any signature or photo.
  • Subscription billing history (Digital products and subscriptions)When the subscription started, each renewal, and that earlier renewals weren't disputed.For this code: Showing different billing periods, upgrades, or prorationsStart date, plan, each charge date and amount, status.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing each session or deliverable was providedDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Amex P08 chargeback (duplicate charge)

American Express P22: Non-Matching Card Number

The issuer says the card number charged doesn't match the card used.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the card read electronically by the terminal, or an imprint confirming the card numberThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the card ending, which isn't one of Amex's listed responsesThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval, which isn't one of Amex's listed responsesThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex P22 chargeback (non-matching card number)

American Express P23: Currency Discrepancy

The issuer says the payment was processed in the wrong currency.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refunded (Amex's only listed response)Refund date, amount, and reference.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the currency, which answers the issuer's question but isn't on Amex's listThe receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.For this code: Showing the currency shown and chosen, which answers the issuer's question but isn't on Amex's listA screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex P23 chargeback (currency discrepancy)

American Express R03: Insufficient Reply

American Express asked the seller for information (an inquiry) and says the reply didn't answer it.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refunded (Amex's only listed response)Refund date, amount, and reference.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex R03 chargeback (insufficient reply to inquiry)

American Express R13: No Reply

American Express asked the seller for information (an inquiry) and says no reply came.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Record of the reply to the original inquiry (Every seller)That the seller answered the card network's inquiry, and when: the reply as sent, with its date, before the inquiry's deadline. It answers a chargeback raised because no reply came (Amex R13).For this code: Showing the seller's dated reply to the original inquiry (Amex's first listed response)The reply as it was sent to the inquiry, with the date it went and the inquiry it answered, from the processor's dashboard or the seller's own records.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Amex R13 chargeback (no reply to inquiry)

American Express S01: Reversal Request Denied

Not a cardmember claim: a status notice: the seller's request to reverse a chargeback was denied.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex S01 notice (reversal request denied)

American Express S04: Reversal Request Under Review

Not a cardmember claim: a status notice: the seller's request to reverse a chargeback is being reviewed.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: With the seller's own record of the credit or requestRefund date, amount, and reference.

Amex S04 notice (reversal request under review)

Discover reason codes

Discover AA: Cardholder Does Not Recognize

The cardholder doesn't recognize the charge on their statement.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • How the statement name links to the seller (Every seller)The name on the customer's statement belongs to the business they bought from.For this code: Linking the statement name to the sellerThe descriptor as it appears on statements, the business and brand name, and the website.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover AA chargeback: unrecognized charge on a statement

Discover AP: Cancelled Recurring Transaction

The cardholder says they cancelled a subscription and were charged again.

In Stripe: The customer says they cancelled but were still charged

Evidence that answers it
  • Recurring billing agreed at signup (Every seller)The customer agreed to be charged repeatedly, at a stated amount and interval.The signup page or email showing price, interval, renewal, and how to cancel, with the date the customer signed up.
  • Cancellation policy (Every seller)How and when a subscription or booking could be cancelled.Quote the cancellation steps and notice period as shown at signup.
  • Cancellation history (Every seller)Whether, when, and how the customer asked to cancel, compared with the charge date.A dated timeline: signup, renewals, any cancellation request and its channel, the disputed charge. State plainly if no request was received.
  • Use after the disputed charge (Every seller)The customer kept using the product or service after the charge they now dispute.Activity dated after the charge date, with the charge date stated for comparison.
  • Renewal reminders sent (Every seller)The customer was told before the charge that the subscription would renew.The reminder email with its send date and recipient address.

Discover AP chargeback: charged after cancelling

Discover AT: Authorization Noncompliance

The issuer says the payment wasn't properly approved.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval and its codeThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover AT chargeback: payment not properly approved

Discover AW: Altered Amount

The cardholder says the amount charged was changed from what they agreed.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the amount (an invoice also works)The receipt or invoice sent to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Agreeing to any changeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.

Discover AW chargeback: amount changed from what was agreed

Discover CD: Credit Posted as Card Sale

The cardholder says a refund owed to them was posted as a charge.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.The approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: Showing any refund already madeRefund date, amount, and reference.

Discover CD chargeback: refund posted as a sale

Discover DP: Duplicate Processing

The cardholder says they were charged twice for one purchase.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Showing what each charge paid forBoth charges side by side with what each one paid for.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing what each charge paid forThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If one was refundedRefund date, amount, and reference.

Discover DP chargeback: charged twice for one purchase

Discover IN: Invalid Card Number

The issuer says the card number charged isn't valid.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the card endingThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approvalThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover IN chargeback: invalid card number

Discover LP: Late Presentment

The issuer says the payment was sent for settlement too late.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the day of the saleThe receipt or invoice sent to the customer.
  • Payment approval record (Every seller)The card issuer approved the payment when it was made: the network's approval, the approval code, the amount and date approved, and when the payment was captured.For this code: Showing the approval date and the capture date, to set beside the day of the saleThe approval as the payment processor recorded it: approved by the card network, the approval code, and the amount and date. For a payment taken outside Stripe or Square, the processor's transaction record.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was refunded before the disputeRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has written to withdraw the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover LP chargeback: payment settled too late

Discover PM: Paid by Other Means

The cardholder says they paid for the purchase another way.

In Stripe: The customer says they were charged twice

Evidence that answers it
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing this charge was the only paymentThe receipt or invoice sent to the customer.
  • Why the charges are separate (Every seller)Each charge is for a different order, item, or billing period.For this code: Showing this charge was the only paymentBoth charges side by side with what each one paid for.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover PM chargeback: customer says they paid another way

Discover RG: Non-Receipt of Goods, Services, or Cash

The cardholder says what they paid for never arrived.

In Stripe: The customer says they didn't receive what they paid for

Evidence that answers it
  • Shipping and tracking details (Every seller)The goods were shipped, when, by which carrier.Carrier, tracking number, ship date.
  • Proof of delivery (Every seller)The goods arrived at the customer's address.The carrier's delivery record showing date, address, and any signature or photo.
  • Access granted or digital product delivered (Every seller)The customer was given what they bought — an account, a login, a download link, a license key.The delivery or welcome email, or the platform record showing when access was granted and to which email.
  • Service delivered (Every seller)The service took place — a session was attended, work was delivered, an event happened.Dates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover RG chargeback: customer says it never arrived

Discover RM: Cardholder Disputes the Quality of Goods or Services

The cardholder says the goods or services weren't as described or were of poor quality.

In Stripe: General dispute (no specific reason given)

Evidence that answers it
  • Product or service as described at sale (Every seller)What the customer was told they were buying.A capture of the sales page, listing, or proposal as it was at the time of purchase, plus a one-paragraph plain description.
  • Proof of delivery (Every seller)The goods arrived at the customer's address.The carrier's delivery record showing date, address, and any signature or photo.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: Showing an offered fix or returnThe relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.

Discover RM chargeback: customer disputes the quality

Discover RN2: Credit Not Processed

The cardholder says a refund they were owed never came.

In Stripe: The customer says a refund was promised but not given

Evidence that answers it
  • Refund or return policy (Every seller)What the customer was entitled to, and that this situation falls outside it.The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer.
  • Terms accepted at checkout (Every seller)The customer saw and agreed to the terms (refund, cancellation, recurring billing) when they paid.A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded.
  • Return status (Every seller)Whether the goods were returned, and whether the return followed the policy.State whether a return was received, when, and in what condition, with any return tracking.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.Refund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover RN2 chargeback (credit not processed)

Discover UA01: Fraud: Card-Present Transaction

The cardholder denies an in-person purchase.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read and the verificationThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.The receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover UA01 chargeback (card-present fraud)

Discover UA02: Fraud: Card-Not-Present Transaction

The cardholder denies an online or other card-not-present purchase.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • 3D Secure authentication (Every seller)The cardholder completed their bank's identity check at checkout.State that the payment was authenticated with 3D Secure and the result. For fraud disputes this usually moves liability to the bank.
  • Earlier payments from the same customer (Every seller)The same customer paid before without disputing, linking this purchase to a known buyer.List each earlier payment with date and amount, and which identifiers match the disputed one (email, IP, device, shipping address, account).
  • Customer IP address and device (Every seller)The purchase came from an IP address or device linked to the cardholder's other activity.Give the purchase IP and show the same IP or device on logins or earlier orders.
  • Customer account history (Every seller)The buyer has an account with the seller — created on a known date, used repeatedly, tied to the cardholder's email.Account creation date, email, login count and dates, earlier orders. A screenshot or export from the seller's platform.
  • Address and security-code checks (Every seller)The billing postcode and card security code entered matched the bank's records.For this code: As supporting evidence onlyReport the check results as Stripe recorded them. Supporting evidence only, never the main argument.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.The relevant messages only, dated, with the key lines highlighted or quoted in the response.
  • Proof of delivery (Physical goods)The goods arrived at the customer's address.For this code: Showing delivery to the billing address or an address used on the cardholder's earlier undisputed orders, with the order confirmationThe carrier's delivery record showing date, address, and any signature or photo.
  • Access and usage log (Digital products and subscriptions)The customer actually used what they bought — logins, lessons viewed, files downloaded, features used.For this code: Showing the cardholder used what was bought after the charge, with the checkout and terms recordsDated list of activity tied to the customer's account: first and last login, count of sessions, what was viewed or downloaded. A short summary first, then the export.
  • Service delivered (Services)The service took place — a session was attended, work was delivered, an event happened.For this code: Showing the service was delivered after the charge, with the invoiceDates of service with proof: calendar invites and attendance, call records, delivered files, project sign-off.

Discover UA02 chargeback (card-not-present purchase denied)

Discover UA05: Fraud: Chip Counterfeit Transaction

The cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read (entry mode) and the authorizationThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover UA05 chargeback (chip counterfeit)

Discover UA06: Fraud: Chip and PIN Transaction

The cardholder says their card was lost, stolen, or never received, and that someone else used it for an in-person purchase.

In Stripe: The customer says they didn't make this purchase

Evidence that answers it
  • Card reader or processor record (chip, PIN, imprint) (Every seller)For an in-person sale: how the card was read (chip, contactless, swipe, or keyed), how the cardholder was verified (PIN, signature), and that the terminal could read chips and take a PIN. A manual imprint of the card shows the card itself was there for a keyed sale.For this code: Showing the chip read, the PIN verified, and the terminalThe terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified.
  • Receipt or invoice (Every seller)What was bought, the amount, and the date.For this code: Showing the sale: what was bought and the amountThe receipt or invoice sent to the customer.
  • Refund or credit already issued (Every seller)The customer was already refunded or credited, in full or in part.For this code: If the payment was already refundedRefund date, amount, and reference.
  • Messages with the customer (Every seller)Depending on content: the customer acknowledged receipt, was satisfied, never asked for a refund or cancellation, or was offered a fix.For this code: If the cardholder has withdrawn the disputeThe relevant messages only, dated, with the key lines highlighted or quoted in the response.

Discover UA06 chargeback (chip and PIN)

Questions people ask

What is a chargeback reason code?

The code the customer's bank gives a dispute to say what the customer claims: that they didn't make the purchase, it never arrived, it wasn't as described, and so on. It decides what the bank checks, so it decides what evidence answers the dispute.

Is Mastercard 37 the same as 4837?

Yes. Mastercard's Chargeback Guide writes some codes both ways, such as 4837/37 and 4853/53, so a notice can show either.

Why do Visa's codes look different from Mastercard's?

Each network numbers its own. Visa groups its codes by kind: 10 for fraud, 11 for authorization, 12 for processing errors and 13 for consumer disputes. Mastercard uses four-digit codes, American Express a letter and two digits, and Discover letters, numbers or both.

Why does Stripe show a different reason?

Stripe sorts every network's codes into a few plain reasons, such as fraudulent or product not received, and shows the network's code alongside. Each code above says which Stripe reason it falls under.

Have a notice in front of you? The notice decoder finds the code, the amount and the deadline in it.

Got a dispute?

Answer a few questions about it and get a response built for its reason code, only from your answers, with the evidence to attach.