When a customer forgets about a renewal and calls their bank, you see two debits in your balance. One reverses the sale, and the other charges you for the dispute itself.
Subscription operators on Hacker News describe the same surprise. In one thread, a SaaS seller said a $10 payment ended up costing $43.95, and another said the dispute fee stays charged whether or not the claim holds up.
Most chargeback cost breakdowns count lost merchandise and shipping, neither of which applies to a software seller. They leave out the costs you do carry, including compute already used, hours spent gathering evidence and a dispute ratio the card networks watch.
On a small renewal, one dispute can cost more than the sale itself. Winning does not always get you the fee back.
This guide breaks down the fee, what each outcome costs and the full cost of a dispute, then looks at who carries it when you use a processor or a merchant of record.
What is a chargeback fee?
A chargeback fee is a separate charge that your processor, or the acquiring bank that settles card sales into your account, deducts when a customer disputes a card payment.
The dispute starts with the customer. They ask the bank that issued their card to reverse a payment, often because a renewal they forgot about went through or they do not recognize a line on their statement.
The issuing bank reviews the claim and may give the customer a temporary credit while it investigates. It then sends the case to you through the card network.
Your processor handles the case from there. It retrieves the transaction record, passes messages and evidence between you, the card network and the issuing bank, and tracks deadlines until the case closes. The chargeback fee pays for that work, and the provider sets the amount.
The short version
The fee is only part of what a software chargeback costs. Reversed revenue, compute already used and hours spent on evidence all add to the final loss, and these six points determine how large it gets and who handles the work:
- Price the fee from your own agreement, because it varies with your account's market, its currency, the pricing you negotiated and the stage the dispute reaches.
- Expect more than one charge, since some fee schedules bill once when a dispute is received and again when you counter it with evidence.
- Treat the reversed sale as cash withdrawn, which becomes a final loss only if you don't recover it.
- Count compute as spent on usage-priced or AI products, because the consumption behind a disputed charge already ran on your infrastructure.
- Contest on incremental cost, weighing the added fee and evidence hours against the sale amount times your realistic chance of winning.
- Check who the legal seller is, since a processor leaves you selling and working each dispute, while a merchant of record becomes the legal seller and runs each case.
How much does a chargeback fee cost?
There is no single chargeback price. Your account’s fee schedule sets the cost, either as one flat fee or as separate charges for each dispute stage.
Flat fees and per-stage fees
Flat pricing means a fixed fee for each case. Stage-based pricing charges separately when the dispute arrives and when you submit evidence.
For example, if your schedule charges $20 when a dispute arrives and $10 when you send evidence, accepting costs $20 and contesting costs $30, before the reversed sale and staff time.
If you pay an automated service to prepare and file responses, add that fee to the contest total. In this example, it is a third charge on top of the $30.
Contract-priced and gateway fees
If you negotiated pricing, use the dispute fee in your agreement rather than the provider’s public standard rate.
A separate payment gateway has its own fee schedule, distinct from the acquiring bank’s dispute pricing. Check both for dispute charges, and count a gateway fee only if its schedule lists one that applies to your case.
You should end up with two fee totals, one for accepting the dispute and one for contesting it.
When is the fee charged, and do you get it back if you win?
When a dispute opens, the fee and often the sale amount leave your balance as separate lines, before the case is decided. Winning gets the sale amount back. Your agreement says whether the opening fee and any separately charged evidence-stage fee come back too.
Accept, contest and lose, or contest and win
| Outcome | Disputed payment | What remains out of pocket |
|---|---|---|
| Accept | Unrecovered | Sale amount plus fees not credited back |
| Contest and lose | Unrecovered | Sale amount, fees not credited back and hours spent on evidence |
| Contest and win | Recovered | Fees not credited back and hours spent on evidence |
If the sale amount already left your balance when the dispute opened, losing the case does not deduct it again.
Chargeback vs refund
You issue a refund yourself, while a chargeback goes through the customer’s bank. Once the bank opens the case, sending a refund does not close it.
If a customer asks you to return a payment and you agree, issue the refund before they call their bank. If a dispute is already open and the sale amount has left your balance, respond through the dispute rather than sending a second refund.
How do you read a chargeback fee on your statement?
One dispute can leave several lines on your statement, and on a small renewal the fees can add up to more than the sale debit. Group every line with the same dispute or transaction reference before you add them up.
A bank line labelled “return item chargeback” can mean a deposited check bounced. Check what the line refers to before you count it as a card-dispute fee.
For a card dispute, check each line against the payment:
- Match the sale debit to the original payment, then identify the handling fee on its own line.
- Look for a second fee for sending evidence, or a third for a response service, if your schedule has them.
- Tick off each credit against the line it returns, checking the sale amount, dispute fees and original processing fee individually.
- If the customer paid in euros and you settle in dollars, match any conversion line for the reversal separately.
- Count a fee appearing on both an invoice and a settlement record once when the invoice marks it as already deducted.
If your schedule charges a $20 dispute fee and a $10 evidence fee, reversing a $100 sale puts $130 in debits on your statement. A $100 credit after a win still leaves $30 charged if neither fee is credited back.
Finish with two separate totals, the revenue that never came back and the fees that stayed charged. In this example, all the revenue came back but $30 in dispute-related fees stayed charged, and the original processing fee still needs to be reconciled separately.
What does a chargeback really cost a software business?
You already paid for the tokens, API calls and storage this customer used, and reversing the payment does not undo that cost. Count the cost of their usage, not a slice of your whole infrastructure bill.
Here is what an illustrative lost contest costs on a $10 monthly renewal:
| Cost | Amount |
|---|---|
| Reversed sale | $10 |
| Dispute fees | $20 opening + $10 evidence = $30 |
| Original processing fee retained | $1 |
| Compute used | $5 |
| Staff time | 0.5 hours × $60 = $30 |
| Total | $76 |
The total is $66 more than the sale, and the $20 opening fee alone is twice the renewal.
Only add a response-service bill or monitoring charge if you were actually billed for this dispute. Leave lost profit out because it is already included in the reversed sale, so adding it again counts the same money twice.
Is a chargeback worth contesting?
Compare only the costs and recoveries that change when you contest rather than accept. Compute already consumed and an opening fee you cannot recover cancel out.
For this renewal, divide the added labor and contest fees by the payment you could recover plus the refundable contest fee:
($30 + $10) ÷ ($10 + $10) = 200%
Contesting only pays off on average if your chance of winning exceeds that number. A probability cannot exceed 100%, so contesting this renewal loses money on average regardless of the evidence.
If the contest fee stays charged after a win, the threshold rises to ($30 + $10) ÷ $10 = 400%.
Use the final outcomes of your past disputes with the same reason as your chance of winning, and compare it with the threshold. Without that history, the threshold alone can still tell you when contesting cannot pay off.
At 100% or above, contesting cannot pay off on average. Below 100%, the threshold is attainable, but strong evidence alone does not tell you your chance of winning.
What happens when your chargeback ratio climbs?
Card networks measure disputes against your transaction volume, and crossing a network's limit can put your account into a monitoring program. The formula, threshold and assessment are not the same for every account, so check your provider agreement and any risk notice for the limits and charges that apply.
For example, 20 disputes across 2,000 renewals in a month gives a 1% ratio. If a billing change confuses 20 more customers and each calls their bank, that ratio doubles to 2% in one cycle, even though the product has not changed.
Your provider also has its own risk controls with separate triggers. If your agreement allows it, the provider may increase a reserve or restrict your account based on your dispute pattern, even when you are below every network limit.
When a risk notice arrives, separate the money it names into two kinds:
- Network assessment, a charge tied to a monitoring program that leaves your balance for good.
- Reserve, money held against future disputes, then released or used under your agreement.
Count the assessment as a dispute cost. Keep the reserve separate in your numbers because it is cash tied up, not a cost.
Watch your monthly dispute ratio against the limit in your agreement. Tag each dispute by its stated reason every month, so clusters help you see which renewal reminder, statement line or card-testing pattern needs to change.
How do you prevent chargebacks on subscriptions and usage billing?
A valid payment can turn into a dispute over a forgotten renewal or unexpected usage charge after you have already spent the compute. Before payment, show renewal dates, explain how usage becomes a charge and what appears on the buyer’s statement, and screen for stolen cards with checkout fraud controls.
Many customers would take a refund if they reached you before their bank, so give them a clear route to help prevent disputes and keep your chargeback ratio below its threshold. Put cancellation, support and refund options where a confused buyer looks, including receipts and the billing page.
1. Renewals the customer forgot about
A customer who cancels costs you one renewal. If they find the charge on their statement and call the bank instead, you risk that renewal plus a dispute fee, and the dispute adds to your chargeback ratio.
For an illustrative $50 renewal, a $20 opening fee puts $70 at stake before you do any evidence work. A reminder gives the buyer a chance to recognize the payment or cancel without involving their bank.
Compare these two reminder lines for that illustrative subscription:
- “Your subscription is renewing soon.”
- “Your Pro plan renews on 1 March for $50 USD. Cancel through your billing page by 28 February to stop this renewal.”
Make “billing page” a direct cancellation link. The specific version gives the buyer the plan, date, amount and currency, so they can decide from the message itself.
The trial button needs the same clarity, with the commitment for that same plan beside “Start your trial,” and a cancellation link beside the terms. “Your trial ends on 1 March, when we charge $50 USD. Billing then repeats monthly.”
Cancellation should not depend on someone answering a ticket. Creem’s Customer Portal lets buyers cancel subscriptions themselves, so make it easy to reach from your app’s billing page.
Keep supporting records for each subscription so you can pull them when a renewal is disputed:
- The receipt and renewal notice.
- The cancellation terms the buyer accepted.
- Usage logged after the renewal date.
Those records also help you respond when Creem asks for supporting documentation.
2. Charges the customer doesn't recognize
An unfamiliar card statement name can send a buyer straight to their bank, putting the sale and dispute fee at risk and raising your chargeback ratio. The billing descriptor is the text identifying the charge, and it needs to connect the payment to the product they know.
On a processor, use the product name buyers recognize wherever you control the descriptor. Keep that name consistent on receipts and invoices, alongside the subscription period, usage period or credit purchase the payment covers.
For a Creem purchase, the statement line starts with CREEM.IO*, identifying Creem as the seller. Add this line to your confirmation page, onboarding email or billing page. “Your card statement will show this payment with a name starting with CREEM.IO*.”
If a buyer still doesn't recognize the charge, they can find it on Creem's order page with their checkout email and match the amount and date. Put your support or refund contact beside that note so buyers who find the order but want a refund can reach you.
Usage billing adds another question, because a customer may recognize your product without knowing how their activity became that total. A receipt that says only “Usage” leaves them to work it out.
For an illustrative postpaid charge, use “API calls, 1–31 March, 1,000 × $0.05 = $50.00.” This explains the $50 total before tax, while any base subscription charge and tax belong on their own lines.
Prepaid credits work differently, because a $50 credit purchase adds to the customer's balance and later consumption reduces it without another card charge. Label the receipt as a credit purchase and show consumption in the usage history.
Creem's credit wallets with auto-refill record each refill as its own order and send you a credits.auto_recharged webhook when the charge succeeds. Use that event to notify the buyer when their card is charged again, identifying the payment as another credit purchase.
3. Card testing and stolen cards
An attacker tests stolen card numbers through your forms, using small charges or card saves to see which pass. Cards that work can fund purchases the cardholders dispute as unauthorized, costing you the sale plus the fee and adding to your chargeback ratio.
A testing burst can look like rapid tiny charges or card saves from new accounts, mostly failing but with a few going through. Monitor failed attempts alongside successful low-value payments, and set an alert on failed attempts per hour so you can investigate a spike as it happens.
Protect every route in your app that can validate a card:
- Rate-limit payment and card-saving requests to stop repeated attempts from running unchecked.
- Verify requests server-side on add-card pages, update-payment-method screens and trial signups that save a card, as well as purchase flows.
These controls limit repeated attempts, but fraud screening also needs to assess successful purchases. A card that works can still be stolen.
On a processor, you configure fraud screening yourself. Creem’s Merchant of Record service includes fraud prevention, but rate limits on routes your own app runs remain your job.
Creem may hold a payout for up to 90 days while investigating a potentially fraudulent transaction. Account for that possible hold in your cash planning, especially if you pay compute costs before the payout reaches your bank.
Processor vs merchant of record: who carries the chargeback?
When a bank reverses a payment, the legal seller gets the case and handles the response, but the contract determines whose balance takes the loss.
| Processor | Merchant of record |
|---|---|
| Legal seller is your business | Legal seller is the provider |
| Your business receives the case through the processor | The provider receives and runs the case |
| You supply evidence, with optional filing assistance or automation | The provider submits the response and may request your product records |
| Your business pays the reversed sale and fee | The contract determines what reaches your balance |
| Your business watches its dispute ratio | The provider manages account risk, while you still prevent disputes |
Creem handles the dispute. We notify you, may ask for supporting documents and make your case to the payment provider, which makes the final decision.
Creem typically refunds the buyer in full, then deducts the sale amount and associated fees, including the 25 USD/EUR chargeback fee, from your payouts or invoices you for them. You still pay for the lost sale and that fee.
Dispute handling is included in the service, but the chargeback fee is separate from the 3.9% + 40¢ successful-transaction rate and goes to payment providers and partners. Creem does not profit from it.
Creem may hold a reserve for potential chargebacks and suspend a store with excessive chargebacks. The renewal, statement and card-testing work above still protects your payouts, even with a merchant of record.
I would ask any provider these questions:
- Who files the response and tracks the case?
- Whose payout pays for the reversed sale and fee?
- Does winning return the fee?
Let Creem run your chargebacks as your merchant of record
With a processor, your team still runs disputes. That suits you if disputes are rare and someone already files evidence and watches the ratio. If each dispute takes a founder away from the product while VAT filings and invoices compete for the same hours, compare a merchant of record.
Creem sells to the buyer on your behalf, so disputes land on Creem's merchant account and we handle the case, while the disputed amount and its fee still come out of your payouts.
Creem also handles tax, which gives you back the hours VAT filings take. That work is included in the 3.9% + 40¢ rate per successful transaction, so a $100 sale leaves $95.70 after Creem's fee.
If you would rather ship product than track a bank's deadlines, try Creem and let the legal seller handle your disputes.
