# Refund vs. chargeback costs: compare the next action, not just the fee

[By Evidenz](https://evidenz.dev/)  5 min read

A refund and a chargeback are different payment processes, not interchangeable buttons with two fixed prices. First establish what the customer is owed and whether a dispute is already open. Then separate returned principal, provider fees, operational effort, and any additional credit before comparing the cost of the next appropriate action.

## Check which actions are still available

Before comparing costs, identify the payment, customer complaint, existing refunds, and live dispute status. A support promise, a pending refund, and an open card dispute are different states. Each changes what the next action can reasonably be.

[Stripe's dispute lifecycle explains that an open dispute must be handled through its dispute process rather than a separate refund.](https://docs.stripe.com/disputes/how-disputes-work) Do not assume a refund is still an available alternative because it would have been possible before the case opened. Check the current provider instructions for the payment method involved.

The customer's entitlement comes first. If the business charged incorrectly or agreed to a valid refund, a cost comparison does not make that obligation disappear. Use the economics to plan an appropriate resolution, not to justify keeping an amount the customer is owed.

## Separate principal from fees and effort

The amount returned to a customer is not the same category as the fee paid to a provider. A recovered amount is not automatically net profit. Keep the components visible instead of reporting one unexplained “chargeback cost.”

Cost components to reconcile for a payment complaint

| Component | What to measure | Common mistake |
| --- | --- | --- |
| Customer principal | Amounts actually debited, refunded, reinstated, or still unresolved. | Counting a pending movement as final. |
| Provider charges | Applicable refund, dispute, countering, and specialist charges under your terms. | Using a headline price as a universal fee. |
| Operating effort | Remaining investigation, approval, response, and follow-up time. | Treating staff time as zero because no new invoice arrives. |
| Additional resolution | A separate goodwill payment, account credit, or service extension. | Calling different benefits a single refund. |
| Duplicate reimbursement exposure | Concurrent refund, dispute, or off-platform payment paths. | Assuming two teams are reconciling each other’s actions. |

Measure only the components relevant to the question. An accounting reconciliation needs confirmed amounts and statuses. A decision about contesting needs the additional costs of that action. Mixing those purposes can make an already incurred cost look avoidable.

## What is the Stripe dispute fee?

Stripe's manual dispute process distinguishes the fee for receiving a dispute from the fee for countering it. Its current response guide describes returning the countered fee on a win, while the received fee normally remains unless the contract states otherwise; country exceptions apply. Confirm your account's terms and the action you are considering.

A search for “Stripe chargeback fee” can therefore refer to different charges. Record received, countered, specialist, and any automation charges separately. Do not add a charge that does not apply to the chosen route.

## Read the fee terms for your own account

[Stripe distinguishes dispute-received and dispute-countered fees, with qualifications by location and contract.](https://docs.stripe.com/disputes/responding) That is a reason to inspect your terms, not to copy one country's price into a universal calculator.

[Stripe also states that its original processing fees are not returned when a payment is refunded.](https://docs.stripe.com/refunds) Check applicable refund charges, payment-method rules, currency effects, and negotiated terms in your own setup. A specialist's contract may add another billing basis or exclusion that the processor's fee page does not describe.

Keep the effective date of the terms used in a comparison. If you later review the same decision, a saved fee definition is more useful than a link whose prices have changed. This article deliberately quotes no fixed fee or recovery estimate.

[Adyen's flow can return disputed funds at the Chargeback Reversed stage while the issuer reviews the defense.](https://docs.adyen.com/risk-management/understanding-disputes/dispute-process-and-flow) A balance improvement at that point should be recorded with its stage, rather than reported as final recovery. Reconcile case events and funds movements together before comparing net outcomes.

## Reconcile a partial refund before counting the loss

**Illustrative case.** A €120 subscription charge has a completed €40 refund. A dispute record then shows €120 for the original payment. Support proposes another €80 payment to resolve the remaining complaint.

Do not add €40, €120, and €80 and call the result the final loss. Some amounts describe completed movements, another describes the disputed amount, and the last is only proposed. The current provider record may also reflect adjustments that the support summary has not captured.

Build a dated ledger: original charge; completed refund and reference; dispute amount and status; actual balance adjustments; proposed resolution not yet executed. Have one owner reconcile the current position and available actions before another team sends money.

The example does not predict how the issuer will treat the partial refund. It shows why gross case amounts and net financial outcomes must be reconciled rather than guessed. Use the [missing-refund guide](https://evidenz.dev/articles/refund-not-received) when a promised or attempted return is itself unclear.

## How do you avoid a double refund after a chargeback?

Have one owner reconcile the original payment, provider case, refund attempts, and any off-platform payment before approving another reimbursement. A pending refund, a dispute debit, and a bank transfer are different records.

**Fictional example:** support has already sent a EUR 96 bank transfer to resolve a subscription complaint. Finance then sees a EUR 96 debit for the same payment's card dispute. The two outgoing movements total EUR 192 before fees, but the case outcome is still unresolved. Do not report that as a final customer reimbursement or assume the issuer will automatically credit the merchant.

Fictional double-reimbursement reconciliation

| Record | Status at review | Next check |
| --- | --- | --- |
| Original EUR 96 collection | Completed payment for the subscription. | Match it to the complaint and both outgoing routes. |
| EUR 96 bank transfer | Completed outside the processor. | Retain confirmation, recipient match, date, and purpose. |
| EUR 96 dispute debit | Recorded; final case outcome unresolved. | Verify provider stage and the permitted way to supply prior-reimbursement evidence. |
| Another proposed refund | Not authorized or executed. | Keep it separate from completed movements; resolve the existing routes first. |

An off-platform payment is not automatically visible in the processor. Preserve the evidence and ask how to handle it in the current case. The arithmetic identifies exposure; it does not predict the bank's decision.

## Keep payment routes coordinated

[Stripe identifies a pending refund becoming disputed as a situation requiring dispute handling to avoid duplicate reimbursement.](https://docs.stripe.com/refunds) Preserve the provider's current statuses and instructions. A customer's request for a different payment route does not by itself confirm that the original route stopped.

This matters when finance handles the card case while support offers a bank transfer, voucher, or additional credit. Record what each action would do and who can authorize it. Stop treating “customer compensated” as one undifferentiated state.

Close the cost review with the chosen action, its factual basis, responsible person, applicable fee terms, and the confirmation you still need. Later, report recovered principal, fees, effort, and unresolved balances separately. That produces a useful operating record without pretending every valid complaint should be contested or every refund will prevent a dispute.

## Connect the money to the promise

Evidenz is being built to connect payment records with the account, support, and product history behind B2C and B2B SaaS complaints. A personal-plan refund and a company-workspace seat credit both need to be matched to what was promised and what actually moved. The intended investigation puts that commitment, failed attempts, service extensions, and the disputed payment together, giving support and finance a common basis for deciding what remains unresolved. Verify amounts and available actions in the provider's current records, and apply your own fee terms. Keep the customer's entitlement, confirmed money movements, and cost of the next action separate.

## Sources and scope

Sources checked October 2026

Published by Evidenz. Examples are illustrative, not customer results. Check current requirements and the actual case against the linked sources.

- [Stripe: Refund and cancel payments](https://docs.stripe.com/refunds)
- [Stripe: How disputes work](https://docs.stripe.com/disputes/how-disputes-work)
- [Stripe: Respond to disputes](https://docs.stripe.com/disputes/responding)
- [Adyen: Dispute flow](https://docs.adyen.com/risk-management/understanding-disputes/dispute-process-and-flow)

Customer context is our starting point.

Evidenz is being built for B2B and B2C SaaS: a shared customer history across subscription billing, accounts, support, and digital product activity. Join the waitlist for early-access news.

[Join the waitlist](https://evidenz.dev/#hero)

## Keep reading

[4 min read

### Payment disputes, chargebacks, and refunds explained](https://evidenz.dev/articles/payment-disputes)[5 min read

### Refund not received: reconcile the payment before issuing another](https://evidenz.dev/articles/refund-not-received)[4 min read

### Accept or contest a chargeback: make the decision from the records](https://evidenz.dev/articles/accept-or-contest-chargeback)

Canonical page: https://evidenz.dev/articles/refund-vs-chargeback-costs