Chargeback vs Refund: Costs and Next Steps for Merchants

A refund returns a payment through the merchant; a card chargeback reverses it through the card issuer's dispute process. For an online store, the next step depends on whether the payment is only authorized, has been captured, or is already formally disputed. Check that status before promising a particular way to return the money.

This guide is for US online merchants. Provider examples were checked on September 14, 2026. The dollar example below uses invented fees to explain the arithmetic, not quote a processor's prices.

Chargeback vs refund vs reversal: what changes?

In Stripe's card documentation, dispute and chargeback describe the same formal process. The disputed amount and applicable fees are debited from the merchant's balance; the initial reversal is not proof that the merchant has lost the final decision. See Stripe's dispute overview.

PayPal also has its own dispute and claim process, separate from a buyer's card issuer handling a chargeback. That is why a support message saying only “the customer opened a dispute” is incomplete: name the provider and case type. PayPal explains these distinctions.

An authorization hold is not a completed sale. For an eligible uncaptured Stripe payment, cancellation releases the authorization rather than refunding captured funds. A customer's statement may not clearly distinguish the two stages. Check the processor record, not just a screenshot of a pending transaction. Stripe's authorization and capture documentation describes this flow.

An order-to-resolution timeline

Use this as an operational checklist, not a promise about how many days a bank will take:

1. Order received: link the order ID to the payment ID and record whether payment is authorized or captured.
2. Customer reports a problem: check fulfillment, cancellation terms and the current payment record together.
3. Choose the supported route: cancel an uncaptured authorization, process an eligible refund, or handle the open dispute through its case workflow.
4. Reconcile: record the actual credit or reversal, fees and case outcome. A customer-support ticket marked “resolved” is not a payment ledger entry.

Give one team member ownership of the case. A practical internal note is: “Order O-1042; payment P-1042; captured $100; refund status none; dispute case D-1042 open; owner Alex.” These are fictional IDs. The useful part is connecting the records before two teams act independently.

What does a refund or chargeback cost on a $100 order?

Hypothetical assumptions: a $100 captured sale has a $3 processing fee that is not returned. A chargeback adds a $15 received fee. Contesting it adds a $10 response fee, returned only if the merchant wins. There is no additional refund fee. These are invented contract terms; substitute your own.

The processor initially credits $97: $100 minus $3. The table follows the net payment balance attributable to this order from before the sale. It excludes the product, delivery, taxes, currency conversion, staff time and any other charges.

In the winning case, $82 remains from the customer's $100 payment: the $3 processing fee and $15 received fee still cost the merchant $18. It is not $82 of profit. If the merchant also incurred $40 for goods and $8 for shipping, the lost-dispute scenario would instead leave an economic result of −$76: −$28 − $40 − $8, assuming no inventory recovery or other adjustments.

Separate cash timing from final cost. In the contested example, the order's payment balance reaches −$28 before the outcome; winning later brings back $110. A business can therefore need cash to handle a dispute even when it ultimately wins.

Real fee schedules differ. On the date checked, Stripe's US standard Payments pricing lists a $15 dispute received fee and a separate $15 fee for a manual response, with the latter returned on a win. That is not the invented $10 response fee above. Account contracts, response products and exceptional network charges can change the bill.

The buyer asks for a refund after opening a dispute

Do not automatically create a second credit. First reconcile the payment, refund and dispute records. Stripe directs merchants to accept or challenge a formally disputed payment through the dispute process; use the case's actual deadline. Missing that deadline means losing the opportunity to contest it. Stripe's response instructions are the source for this provider-specific step.

• Identify the case: record the payment ID, disputed amount, reason, deadline and any existing refund.
• Stop conflicting actions: tell support and finance who owns the resolution before another team sends money.
• Resolve in the correct workflow: use the provider's documented options for that case type. Escalate an unclear or overlapping credit to processor support.
• Confirm the outcome: reconcile the provider record before recording another payout or telling the customer a new refund has completed.

A neutral customer reply could read: “We've located your order and the open payment case. We're checking the payment record so the resolution is handled correctly. We'll update you through this support thread.” This is a suggested message, not a representation that a refund has already happened.

If you contest it, answer the actual complaint

Build a concise chronology with readable records. Stripe recommends organizing evidence by time and type, and explaining what each item establishes. The issuer decides the outcome; a large upload does not guarantee a win. See Stripe's evidence guidance.

For your internal handoff, consider three questions:

• What was promised? Preserve the order confirmation and the product description or terms shown at purchase.
• What happened? Match the complaint to relevant fulfillment, delivery or service records and any refund record.
• What was communicated? Keep the actual support exchange and explain any gap between the order and the buyer's experience.

These are preparation prompts, not a universal list of sufficient evidence. Follow the reason-specific requirements in the case. A delivery record alone does not explain why a customer says the item was different from its description. Do not manufacture acceptance records or describe a complaint as fraud simply because you disagree with it.

“Refund sent” does not always mean “money received”

Stripe refunds return to the original payment method. A card refund can remain pending when the available Stripe balance is insufficient, and refunds can fail. Some appear as a reversal that removes the original charge rather than a separate credit. Check the status and, when available, provide the refund reference so the customer can ask their bank to trace it. Stripe's refund documentation explains these cases.

For a support handoff, distinguish “requested,” “pending,” “completed” and “failed” using the provider's actual status labels. Do not replace them with a blanket “you have been refunded” response.

Your return policy is only part of the decision

A merchant's policy does not make every refund discretionary. For example, the FTC's online merchandise delivery guidance describes obligations when an order cannot ship on time, including delay notices and refund rights. The applicable rules depend on the sale; check your obligations as well as your processor's workflow.

Would a stablecoin payment remove this problem?

It changes the payment process. Stripe's stablecoin payment product lists no dispute support and supports refunds to the original wallet. That product behavior is not a promise about every crypto payment, nor does it resolve complaints about goods. Before changing payment methods, read how stablecoins work and where their risks differ.