One Stripe Dispute Covering Several Subscription Charges

A customer has paid you $50 a month through a Stripe subscription since the spring. In October their bank files a chargeback for $150. You open the dispute in the Stripe Dashboard and it points at the September 1 payment, which was $50. Your July and August invoices still show as paid. Stripe has taken three times the amount of the payment the dispute names, and nothing in your books says why.

That isn't a Stripe error. It's one of the cases Stripe documents: when a cardholder disputes several subscription payments, the bank can file one dispute for the total and attach it to just one of the charges. This post covers how to recognize one, what it costs, how to respond so every month is covered, and how to book it in QuickBooks so the loss lands on the right customer and the right periods. If you'd rather have Stripe's dispute activity reach QuickBooks through a mapping you set once, start a free trial.

What Stripe says happens

Stripe's guide to how disputes work has a table of reasons a disputed amount can differ from the original charge. One row is Recurring payments:

"Sometimes, when an account owner disputes multiple payments within a recurring subscription plan, their bank creates a single dispute for the total amount against one of the charges. This can also happen with non-recurring payments, but is rare."

Stripe's own example is the one above: "An account owner disputes three 50 USD recurring charges, but the bank issues a dispute of 150 USD against one of the three payments."

The Dispute object shows why this is confusing. A dispute has one charge field, the "ID of the charge that's disputed", and one amount, described as "Usually the amount of the charge, but it can differ." There is no field listing the other two payments. As far as Stripe's data model is concerned, one charge is disputed, for more than it was worth.

How to spot a bundled dispute

The signature is a dispute amount that is larger than the charge it references. Stripe's table lists the reasons an amount can differ, and only some of them push it up:

What you see	Likely reason
Dispute amount smaller than the charge	A partial dispute: the cardholder contests only part of the purchase, such as one damaged item
Dispute amount slightly different, in either direction	Currency conversion between the purchase and the dispute
Dispute amount an exact multiple of a subscription price, same currency	Several recurring payments bundled into one dispute

A same-currency dispute that is exactly two or three times the subscription price is almost always a bundle. To confirm, pull the customer's payments in Stripe and add up the most recent ones. If the last three charges total the dispute amount, you know which months the cardholder is contesting.

The dispute reason is usually a clue too. Stripe's dispute categories include Subscription canceled: "The customer claims that you continued to charge them after a subscription was canceled." A cardholder who believes they canceled in July and then saw charges in August and September has every reason to dispute all of them at once.

What it costs

Stripe debits the disputed amount, plus a dispute fee, from your balance when the dispute opens. The fees are per dispute, not per payment inside it. Stripe's June 2025 dispute fee update sets both US fees at $15:

• a dispute received fee, charged when the dispute arrives, which "is not returned if you win" (outside Mexico)
• a dispute countered fee, charged when you counter a dispute initiated after June 17, 2025, which "will be returned to you if you win"

Stripe says the received fee is "charged each time you receive a dispute", and the countered fee applies "when you counter a dispute". So one bundled $150 dispute costs $15 to receive and $15 to counter. Three separate $50 disputes would each carry their own fees.

Here is the example in numbers, using Stripe's standard US card rate of 2.9% + 30¢ on each $50 payment:

Date	What happened	Stripe balance
Jul 1	$50 subscription payment, less $1.75 fee	+48.25
Aug 1	$50 subscription payment, less $1.75 fee	+48.25
Sep 1	$50 subscription payment, less $1.75 fee	+48.25
Oct 14	Dispute of $150 against the Sep 1 charge, plus $15 received fee	-165.00
Oct 20	You counter with evidence: $15 countered fee	-15.00

Stripe says a countered dispute can take up to 3 months to decide. Then one of two things happens:

• You win. The issuer returns the $150 and Stripe returns the $15 countered fee: +$165.00. Your net cost is the $15 received fee.
• You lose. "No money moves from your perspective." You are out $150 plus $30 in fees, on top of the $5.25 in processing fees Stripe kept on the original payments.

Stripe's fee update also describes disputes that are partly won, where only part of the amount comes back and neither $15 fee is returned. That outcome is realistic with a bundle, because the issuer may agree about one month and not the others.

Responding when one dispute covers three months

The evidence has to cover the whole amount, not just the payment the dispute is attached to. A response that proves September was a valid charge still leaves $100 contested with nothing said about it.

For a Subscription canceled dispute, Stripe suggests showing that "The subscription was still active and that the customer was aware of, and did not follow, your cancellation procedure." Its evidence list for that category includes:

• your cancellation policy as shown to the customer, and how and when they saw it before paying
• "A justification for why the customer's subscription was not canceled, or if it was canceled, why this particular payment is still valid"
• renewal notices, or "an acknowledgement from the customer of their continued use of the product or service after the date they claim they canceled"
• "If the product was partially used, whether the dispute amount exceeds the value of the unused portion"

With a bundle, build that evidence per month. Show the renewal notice or the usage for July, then for August, then for September. If your records show the customer really did cancel before one of the charges, say so and argue the rest. Conceding the one month you'd have refunded anyway makes the case for the other two more credible, and a partly won dispute still returns the part you win.

Two practical checks while the dispute is open:

1. Don't refund the other two payments separately. Stripe says you "can't issue a refund outside the dispute process while the dispute is open", but that applies to the disputed charge. The July and August payments carry no dispute in Stripe, so a refund on either would go through, and you'd have returned that money twice if the dispute is lost.
2. Check the subscription status. If the customer believes they canceled, confirm whether the subscription is still billing. A fourth charge in November is the start of a second dispute.

The reverse also happens. Stripe notes that "In extremely rare cases, you might receive more than one dispute per payment", for example when a customer refiles with a different reason code. Its guidance there is to "Handle each dispute the same way as any other dispute" and to respond to each one individually. Book each one as its own event, too.

Booking it in QuickBooks

The mistake to avoid is booking the chargeback at the amount of the charge instead of the amount of the dispute. If your process reverses the September payment and stops there, QuickBooks records a $50 loss while Stripe took $150. The $100 difference sits in your Stripe clearing account as an unexplained gap between QuickBooks and Stripe's balance.

The rule: chargebacks booked must equal the dispute amounts, not the amounts of the charges the disputes name.

On October 14, when Stripe debits the balance, a journal entry for the example looks like this:

Account	Name	Debit	Credit	Memo
Chargebacks	Customer	50.00		du_... covers Jul 1 charge (inv. #1041)
Chargebacks	Customer	50.00		du_... covers Aug 1 charge (inv. #1077)
Chargebacks	Customer	50.00		du_... filed against Sep 1 charge (inv. #1112)
Dispute fees		15.00		Dispute received fee
Stripe Clearing			165.00	Stripe dispute du_...

Book the countered fee on October 20 the same way: debit Dispute fees, credit Stripe Clearing.

Split the $150 into one line per payment. A single $150 line is arithmetically fine, but it tells the next reader that September's $50 payment produced a $150 loss. Three lines, each naming the customer and the invoice it relates to, keep customer-level and period-level reports honest. When someone asks "which months did we lose?", the memo answers it.

Date the entry in October, when the money moved. The July and August sales were correct when you booked them, and those months may already be closed. Reversing them in place would change reported revenue for closed periods and cross your QuickBooks closing date. The chargeback is an October event that relates to earlier sales. That's what the memo is for.

Leave the July and August invoices as they are. They were paid, and the money reached your bank. The loss is the chargeback, not an unpaid invoice. Reopening those invoices would put $100 back into Accounts Receivable that the customer will never pay.

If the case straddles a close. Some businesses book an open dispute to an asset such as "Disputed funds receivable" until the outcome is known, then move it to Chargebacks on a loss or clear it on a win. That works here as well. Just carry the full $150, not $50.

When the outcome arrives:

Outcome	Entry
Won	Debit Stripe Clearing 165.00. Credit Chargebacks 150.00 (the three lines reversed). Credit Dispute fees 15.00
Lost	No entry. The October entry already carries the loss
Partly won	Debit Stripe Clearing for the amount returned. Credit Chargebacks for the months the issuer found in your favor

For more on ordinary wins and losses, see our chargeback accounting guide. If a lost dispute comes back months later, late wins and late withdrawals have their own treatment. If the charges were in a foreign currency, add the exchange difference covered in disputes on converted charges.

Reconcile against Stripe, not against the charge

The fastest way to catch a bundled dispute you missed is to compare your Stripe clearing account with Stripe's ending balance. Stripe's Balance summary report "works like a bank statement", and its itemized export lists every dispute row with the charge_id it relates to and, for Stripe Billing, the invoice_id and subscription_id as well.

Filter the month's rows for disputes and compare each dispute's amount with the amount of the charge it names. Any dispute row larger than its charge, in the same currency, is a bundle. If your QuickBooks chargebacks for the month are short by exactly the difference, you've found your variance.

Where Acodei fits

What Acodei's documentation supports, and where it stops:

• Dispute activity is mapped once. Disputes and other adjustments are among the uncommon Stripe balance transaction types that Acodei handles through Balance Transaction Mapping on the Account Mapping page. You assign a product once, and on a daily balance summary or payout the dispute is included as a line using that product. In real-time mode, Acodei's documentation describes reversing the original record instead, for example removing the payment on an invoice so the invoice reopens.
• A won dispute is not re-posted as a new payment. When Stripe returns disputed funds, Acodei doesn't recreate the customer's original payment. If a disputed invoice shows as open in QuickBooks after a chargeback, that's expected, and you can record a payment against it if the money comes back.
• What the documentation doesn't cover. Neither source describes what happens when a dispute is larger than the payment it references. So after a bundled dispute syncs, run the checks above: confirm that the total reaching QuickBooks equals the dispute amount, then decide whether to split it across the months it covers.

A bundled dispute is rare, and it's easy to misread because Stripe's data points at one payment. An integration can get Stripe's activity into QuickBooks without retyping it. Deciding which months the loss belongs to, and what to argue in the response, stays with you. To get your Stripe dispute activity into QuickBooks through a mapping you set once, start a free trial.

Frequently asked questions

Why is my Stripe dispute bigger than the payment?

Stripe lists several reasons. The one that makes a dispute larger in the same currency is a bundle: "when an account owner disputes multiple payments within a recurring subscription plan, their bank creates a single dispute for the total amount against one of the charges." Currency conversion can also move the amount up or down slightly.

Do I pay the Stripe dispute fee once or for each payment in the dispute?

Once per dispute. Stripe says the received fee is "charged each time you receive a dispute", and the countered fee applies when you counter one, so in the US a single bundled dispute carries one $15 received fee, plus one $15 countered fee if you respond. The countered fee is returned if you win.

Should I reverse the July and August invoices in QuickBooks?

Usually not. Those payments were real and the months may be closed. Book the full dispute amount as a chargeback in the period Stripe debited it, with one line per payment it covers, and put the invoice numbers in the memos. Confirm the treatment with your accountant.

Can I refund the other payments while the dispute is open?

Not while the outcome is open. Stripe's rule that you can't refund outside the dispute process applies to the disputed charge. The other payments carry no dispute in Stripe, so a refund on them would go through, and if you then lose the dispute you've returned the same money twice.

What if I win only part of a bundled dispute?

Stripe's fee update describes partly won disputes: part of the amount is returned, and neither $15 fee is. Book the returned amount against the months the issuer decided in your favor, and leave the rest as a chargeback.