%201.svg)
Recurring Billing Chargebacks: Reason Codes, Evidence, and When to Fight
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
600+ reviews
TL;DR:
- Match the reason code to the claim first: 13.2 and 4841 are cancellation disputes, 10.4, 4837 and 4863 deny the charge, and 12.6.1 and 4834 are duplicates or wrong amounts.
- Cancellation disputes turn on your cancellation log and use after the cancellation date, so accept them when a request was received and not processed.
- “I never subscribed” disputes are won with signup consent, login or device records and, on Visa 10.4, prior undisputed transactions under Compelling Evidence 3.0.
- Your response deadline comes from your processor, Stripe documents 7 to 21 days, and you usually get one submission.
- Disputes resolved through pre-dispute programs such as Visa RDR stay out of the VAMP count, so decide fight or refund on evidence and fees.
A recurring billing chargeback is a dispute a cardholder files against one charge in a subscription, membership or other repeating payment, and the reason code on the case tells you which evidence can win it. Seven codes cover the claims below: Visa 13.2 (Cancelled Recurring), 10.4 (Other Fraud: Card-Absent Environment) and 12.6.1 (Duplicate Processing), and Mastercard 4841, 4837, 4863 and 4834.
This page is the response playbook: what the cardholder is claiming, the evidence that answers each code, and whether to fight or refund. For the market drivers behind these disputes, read why subscription chargebacks keep rising.
$42B forecast global cost of chargebacks to merchants by 2028, with nearly half reported as fraudulent | 120 to 365 days age of the two prior undisputed transactions that can qualify a Visa 10.4 dispute for Compelling Evidence 3.0 | 1.5% Visa VAMP merchant Excessive ratio in the US, Canada, EU and Asia Pacific since 1 April 2026, at 1,500 or more counted events a month |
Sources: Mastercard 2025 State of Chargebacks, Visa Merchants Dispute Management Guidelines (June 2024) and the Visa Acquirer Monitoring Program fact sheet.
How Chargebacks Affect Subscription Businesses
Each disputed renewal costs the payment, a dispute fee and a count toward the monitoring ratios covered below, and the customer usually leaves. Because subscriptions repeat, one unfixed cause such as an unprocessed cancellation can produce a dispute every billing cycle, so the subscription chargeback prevention and recovery program is where you fix the cause while this page covers answering the claim.
Unlike a one-time dispute, the issuer is judging an ongoing agreement and its state on the charge date, not delivery of a single order. For the process itself, see what a chargeback is and the difference between a dispute, a chargeback, a refund and representment.
Which Claim Maps to Which Reason Code
Read the reason code on the notice first, because it sets the evidence you can use. The table maps what the cardholder says to the Visa and Mastercard codes and to the category Stripe assigns in its current dispute documentation.
| What the cardholder says | Visa code | Mastercard code | Stripe category |
|---|---|---|---|
| “I canceled, and you charged me anyway” | Visa 13.2 Cancelled Recurring | Mastercard 4841 Canceled Recurring or Digital Goods Transactions | Subscription canceled |
| “I don’t recognize this renewal” or “I never subscribed” | Visa 10.4 Other Fraud: Card-Absent Environment | 4837 No Cardholder Authorization and 4863 Cardholder Does Not Recognize - Potential Fraud | Fraudulent (10.4 and 4837); Unrecognized (4863) |
| “You charged me twice” | Visa 12.6.1 Duplicate Processing | Mastercard 4834 Point of Interaction Error, which covers a cardholder debited more than once for the same goods or services | Duplicate |
| “The amount is wrong” or “the price changed” | Visa 12.5 Incorrect Amount | 4834 Transaction Amount Differs | General (Visa 12.5); Duplicate (Mastercard 4834) |
| “I did not get the service” or “it was not as described” | Visa 13.1 and 13.3 | Mastercard 4853 Cardholder Dispute | Product not received; Product unacceptable |
Mastercard issuers still use 4841 for canceled recurring and digital goods, and Stripe’s mapping also lists recurring-transaction disputes under 4853, so work from the code printed on your case. The full lists are in the Visa chargeback reason codes and Mastercard chargeback reason codes guides, and how to tailor evidence to each reason code covers the general method.
Canceled Recurring Disputes: Visa 13.2 and Mastercard 4841
The cardholder says they canceled, withdrew permission or closed the account before this charge, and you billed anyway. Answer it with your cancellation log, not with your terms alone.
Visa’s listed remedies for 13.2 are narrow: proof the cardholder used the service after withdrawing permission, documentation of a credit or reversal already processed with its amount and date, or the cardholder’s statement that they no longer dispute the charge. If a cancellation was received and no credit was issued, Visa’s merchant guidelines point to accepting the dispute.
| Evidence | What it proves | Stripe evidence field |
|---|---|---|
| Cancellation log with timestamps for every request channel | Whether a cancellation was received before the billing date | cancellation_rebuttal |
| Signup record showing the renewal schedule and cancellation terms the customer accepted | The customer agreed to the renewal and knew the cancellation route | cancellation_policy and cancellation_policy_disclosure |
| Login and usage logs after the claimed cancellation date | The service was used after the customer says they stopped | uncategorized_text or uncategorized_file |
| Refund or credit record with amount and date | The customer was already made whole | uncategorized_text or uncategorized_file |
| Customer messages sent before the dispute | Whether the customer tried to cancel or resolve it with you first | customer_communication |
Trial conversions belong here too. Stripe’s description of 4841 includes a cardholder who forgot to cancel a free trial and disputes the first paid charge, so keep the trial terms, the reminder you sent and the date the trial ended. If the dispute came through PayPal, the steps differ, so see how to win a canceled recurring billing PayPal dispute.
Unrecognized Renewal and “I Never Subscribed” Disputes: Visa 10.4, Mastercard 4837 and 4863
The cardholder says they did not authorize the charge or do not recognize it. Stripe notes that an unrecognized claim is effectively indistinguishable from a fraud claim, so answer with proof that the cardholder, or someone they authorized, opened the account and used it.
| Evidence | What it proves | Where to find it |
|---|---|---|
| Signup record with timestamp, IP address, device ID and accepted terms | A real person with this card opened the account | Checkout or signup logs from the first, customer-initiated payment |
| Login and usage history, including activity after the disputed charge | The cardholder or an authorized person used the service | Product analytics and access logs; the proof of access evidence guide shows how to package them |
| AVS and CVV results from the first payment | Billing details matched the cardholder | Processor authorization response; see how AVS results should drive decisions |
| 3D Secure result on the first payment | Authentication that can shift liability on fraud claims | Authentication record; 3D Secure 2 explains the liability effect |
| Prior undisputed transactions with matching identifiers | The pattern Visa Compelling Evidence 3.0 accepts on 10.4 | Your transaction history, matched on device, IP address, login ID or delivery address |
Visa Compelling Evidence 3.0 applies only to 10.4. It needs two or more undisputed prior transactions dated 120 to 365 days before the disputed charge that share identifiers with it, so a customer who joined less than 120 days earlier cannot qualify on your own history. Stripe checks eligibility automatically on 10.4 disputes and says eligibility typically translates to a significantly higher likelihood of overturning the dispute.
From 24 October 2026, Visa’s rules also let CE 3.0 draw on multi-merchant transaction history for 10.4, so ask your acquirer how it applies to your account. The full requirements are in Visa Compelling Evidence 3.0 explained. For Mastercard 4837 and 4863 the same signup, login and 3D Secure evidence applies.
Many of these claims come from customers who forgot the subscription rather than from fraudsters, and the friendly fraud guide covers telling the two apart. For a billing-platform example, see how to beat an “I never subscribed” dispute with Chargebee and Chargeflow.
Duplicate Charge Disputes: Visa 12.6.1 and Mastercard 4834
The cardholder says one charge was processed more than once. Visa 12.6.1 requires the same payment credential, the same transaction date and the same amount, so two renewals on different dates are not duplicates under this code.
| Situation | Response | Evidence or fix |
|---|---|---|
| Two settled charges from a retry or system error, same credential, date and amount | Accept and refund the extra charge | Fix idempotency keys so the same payment cannot settle twice |
| Two separate renewals or add-ons on the same day | Fight | Separate invoices showing different products or periods; Stripe’s duplicate_charge_id, duplicate_charge_explanation and duplicate_charge_documentation fields |
| A pending authorization the cardholder reads as a second charge | Fight | Authorization and settlement records showing one charge cleared and the hold dropped |
| A failed payment retried automatically, then paid again by the customer | Refund one charge if both succeeded | Review retry rules in smart dunning management so a retry cannot run after the customer pays manually |
| A void or refund already issued | Respond with the record | Void or refund confirmation with amount and date |
Mastercard 4834 is broader than duplicates, because it also covers a transaction amount that differs from what the cardholder agreed. Read the case detail before choosing a response.
Fight or Refund: A Decision Rule by Claim
Fight when your records contradict the claim, and refund when they confirm it. Whether you can show the claim is wrong matters more than any fixed dollar threshold.
| Situation | Decision | Reason |
|---|---|---|
| Cancellation received before the charge and not processed | Accept, then fix the cancellation flow | Visa’s 13.2 guidance points to accepting when permission was withdrawn and no credit was issued |
| Refund or credit issued before the dispute posted | Respond with the refund record | Documenting the credit, amount and date is a listed Visa remedy for 13.2 and 12.6.1 |
| No cancellation on record, signup consent on file and use after the billing date | Fight | Your records contradict the claim |
| Unrecognized renewal on Visa 10.4 that Stripe flags as CE 3.0 eligible | Fight | Eligibility typically raises the likelihood of overturning the dispute |
| Unrecognized renewal where the descriptor does not name your brand and no login history links the cardholder | Accept and change the descriptor | Nothing ties the cardholder to the account, and the descriptor problem will repeat |
| Low-value dispute on a processor that keeps the dispute received fee | Refund before it posts where an alert allows | Stripe does not return the dispute received fee even when you win, unless your contract says otherwise |
Refunding early also helps your monitoring ratio, because Visa’s VAMP count excludes disputes resolved through pre-dispute solutions. Chargeback alerts and Visa Rapid Dispute Resolution are the routes to refund before a dispute posts, and Stripe dispute fees shows what each outcome costs there. For the policy question, see whether you should fight every chargeback.
Representment Timing for Recurring Billing Disputes
Your deadline comes from your processor, not from the network maximum, and you usually get one submission. Build the full packet before you submit it as chargeback representment.
| Step | Clock or limit | What to do |
|---|---|---|
| Cardholder files | Visa conditions commonly run 120 days from a start event; Mastercard commonly allows 120 days, and some codes run longer | Check the start event for the code in the guide to chargeback time limits |
| You respond | Set by your processor; Stripe documents 7 to 21 days depending on the network | Work to the due date on the case, because a missed deadline is an automatic loss |
| You submit | One response on Stripe, with a combined 4.5 MB evidence limit and 19 pages for Mastercard | Merge files by evidence type and leave out links, audio and video, which banks do not review |
| Issuer decides | Up to 3 months after you counter, per Stripe | Track the case and keep records for escalation |
| Escalation | Pre-arbitration and arbitration clocks start from specific case events | See what pre-arbitration involves, the Visa dispute rules, fees and time limits and the Mastercard chargeback guide |
If the case arrives as an inquiry instead of a chargeback, answer it with the same evidence, because a resolved inquiry never becomes a dispute. If it escalates, Stripe requires a second response.
How Recurring Billing Disputes Count Toward Monitoring Programs
Recurring disputes feed card network monitoring ratios, so a cancellation problem that repeats every cycle moves your ratio quickly.
| Program | What counts | Level that matters | Recurring billing note |
|---|---|---|---|
| Visa VAMP | Fraud reports (TC40) plus disputes (TC15), divided by settled transactions | Merchant Excessive at 1.5% in the US, Canada, EU, Asia Pacific and Latin America and the Caribbean (2.2% in CEMEA), with 1,500 or more counted events a month outside CEMEA | 13.2, 10.4 and 12.6.1 disputes all count; disputes resolved through pre-dispute solutions and TC40 fraud qualified for CE 3.0 are excluded |
| Mastercard ECM | First-presentment chargebacks on any reason code | 100 to 299 chargebacks and a 1.5% to 2.99% ratio (HECM at 300 chargebacks and 3%) | 4841, 4834 and fraud codes all count toward the same ratio |
| Mastercard EFM | Fraud-coded chargebacks on card-not-present sales, limited to 4837 and 4863 | All four criteria in a month, including 1,000 or more ecommerce transactions, $50,000 or more in fraud chargebacks and low 3D Secure use | Unauthorized-renewal claims feed this program, and 3D Secure on the first payment is one of its criteria |
The Visa VAMP guide covers the ratio and exclusions, chargeback thresholds compares VAMP and ECM side by side, and the Mastercard Excessive Chargeback Program guide covers ECM and EFM fines.
Tools and Platforms That Prevent Recurring Billing Disputes
No single platform prevents recurring billing disputes. Prevention works in layers, and each layer reduces a different claim.
| Layer | What it does | Claims it reduces |
|---|---|---|
| Billing platform with self-serve cancellation and renewal notices, such as Stripe recurring payments or Shopify recurring payments | Keeps subscription, invoice and access states aligned and sends notices before each charge | 13.2, 4841 and 12.6.1 |
| Recognizable billing descriptor and a receipt for each cycle | Lets the cardholder match the charge to your brand | 10.4 and 4863 |
| Automatic credential updates through account updater and network tokens, covered in the card-on-file guide | Replaces expired or reissued card details before the renewal runs | Fewer failed renewals and retries that can turn into 12.6.1 claims |
| Pre-dispute alerts, such as Chargeflow Alerts | Connects Verifi RDR, Ethoca and CDRN alerts and refunds alerted charges within 24 hours of receipt | Any claim where a refund is the right outcome |
| Evidence automation, such as Chargeflow Automation | Collects evidence and submits it for supported disputes within the processor deadline | Claims you choose to fight |
Keep failed payments and disputes in separate queues, because involuntary churn and chargebacks need different fixes. The recurring payments guide covers consent and rules, a recurring payment service provider comparison covers platform choice, and the ecommerce fraud prevention guide covers screening for the 10.4 claims that remain.
Frequently Asked Questions
What is Visa reason code 13.2?
Visa reason code 13.2 is Cancelled Recurring Transaction: the cardholder says they canceled, withdrew permission or closed the account before a recurring charge was processed. Contest it with proof the service was used after cancellation, a record of a credit already issued, or the cardholder’s withdrawal statement, and accept it when a cancellation was received and no credit was issued.
What is Mastercard reason code 4841?
Mastercard 4841 is Canceled Recurring or Digital Goods Transactions: the cardholder says they canceled a subscription or digital purchase, or never authorized it, and Stripe’s description includes forgotten free trials. Answer it with the signup agreement, cancellation terms, proof that no cancellation was received and usage logs, and check the case code because issuers also use 4853 for recurring disputes.
Can a customer dispute a recurring charge after canceling?
Yes. A charge that posts after a cancellation is disputed as 13.2 or 4841, and you should accept it if you received the cancellation and did not process it. Charges from before the cancellation can still be disputed as unrecognized or unauthorized, commonly within 120 days of a start event set by the dispute condition.
What evidence beats an “I never subscribed” dispute?
Submit the signup record with timestamp, IP address, device ID and accepted terms, plus login history, AVS and CVV results and the 3D Secure outcome. On Visa 10.4, add two or more undisputed prior transactions dated 120 to 365 days earlier that share identifiers with the disputed charge, which is the Compelling Evidence 3.0 pattern.
What is the difference between Mastercard 4837 and 4863?
4837 is No Cardholder Authorization, where the cardholder says they did not authorize or take part in the charge. 4863 is Cardholder Does Not Recognize - Potential Fraud, where a card-not-present charge is unfamiliar to them. The same signup, login and 3D Secure evidence answers both, and both count toward Mastercard’s Excessive Fraud Merchant program.
Should I fight or refund a disputed subscription charge?
Fight when your records contradict the claim, such as consent plus login history or usage after the claimed cancellation, and refund when they confirm it, such as a cancellation you received and did not process. Also weigh the amount against your processor’s dispute fees, because Stripe does not return the dispute received fee even when you win unless your contract says otherwise.
Does a chargeback cancel future billing?
Not always. Billing behavior depends on your platform and configuration, so verify the subscription status, collection settings, access and any remaining invoices after the dispute is resolved.
What platforms and tools prevent recurring billing disputes?
No single tool does. A billing platform with self-serve cancellation and renewal notices reduces 13.2 and 4841 claims, a recognizable descriptor reduces unrecognized-charge claims, and pre-dispute alerts plus evidence automation handle the disputes that still arrive.
Explore Chargeflow’s automated chargeback recovery to organize evidence and manage supported dispute responses.
Chargebacks?
No longer your problem.
Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000 merchants.
.png)
.webp)
.webp)
