Recevoir un rejet de débit après un remboursement : causes et solutions

A chargeback after a refund is a payment dispute that overlaps with a merchant credit on the same transaction. It can involve a pending, failed, partial, or completed refund, so the first step is to reconcile the payment records rather than assume the customer received money twice.

A support message saying “refunded” is not enough to establish the settlement outcome. You need the original payment, refund status, credited amount, and dispute details in one timeline. That distinction determines whether to submit evidence, resolve an outstanding credit, or ask your processor to investigate an apparent duplicate debit.

Why a Refund and Chargeback Can Overlap

Customers may contact their bank before seeing a credit, while a refund is still processing, or because a partial refund did not resolve the whole purchase. A failed refund can also leave a legitimate complaint unresolved. Deliberate double recovery is possible, but an overlapping notification alone does not establish friendly fraud.

The distinction between initiation and completion matters. A refund request can enter a pending state, fail, or complete according to the payment method and account circumstances. Stripe’s refund documentation describes these states and situations where a payment is disputed while its refund is pending. Use the status of the actual transaction instead of promising one universal posting window.

Use the Refund Status to Choose Your Next Step

These are operational starting points, not automatic dispute outcomes. Read the case instructions and reason code before choosing an action. Your provider’s available controls and deadlines take priority over a generic workflow.

Build a Single Reconciliation Timeline

For example, a partial merchandise refund may exclude an item the customer kept. A dispute for the full order needs a clear explanation of both the credited amount and the remaining purchase. Attach the itemized order and refund breakdown. Do not present a partial credit as evidence that the entire transaction was refunded.

Assign one person to own the reconciliation. Support may hold the customer conversation while finance sees settlement movements and risk owns the response deadline. A shared case record prevents each team from making a separate decision from incomplete information. The support and payments coordination workflow can help formalize those handoffs.

Submit Evidence That Shows What Was Credited

A useful response identifies the disputed payment, explains the refund chronology, and includes a readable record of the completed credit. If a network or processor reference is available, include it with a plain-language label. Do not invent a reference number or imply that every payment method provides the same tracing information.

Include relevant customer correspondence, such as confirmation of the amount agreed and when the refund was issued. Remove unrelated conversations and sensitive information. A screenshot of a refund request without its final status is weaker than a clear record showing completion. For more on case presentation, use the evidence standardization guide.

Keep the response focused on the allegation. A credit-not-processed claim and an unauthorized-payment claim can require different explanations, even when both involve a refund. Your issuer evidence review should address the actual disputed condition, not simply assert that the customer is wrong.

Avoid a Second Credit While a Case Is Open

Merchants using Stripe can review its dispute response instructions for the available resolution actions. Where a case requires evidence, submit it by the displayed deadline. A customer promise to contact their bank does not replace that operational step.

Do not ask a customer to repay an apparent duplicate credit until your provider has reconciled the ledger. An account statement can show provisional entries that later change. Keep communication factual: identify the transaction, explain the refund status, and give the customer the available reference and support route.

Reduce Refund-Related Disputes at the Source

Send an accurate confirmation when a refund is initiated and update the customer if it fails. Make the credited amount clear, especially for partial refunds. Use provider-specific timing guidance and explain how the customer can get help tracing a missing credit. Avoid promising that a refund makes all later disputes impossible.

Review why customers dispute refunded purchases alongside refund failures, support response times, and duplicate-credit incidents. Separate unresolved service problems from processing delays and suspected abuse. This makes prevention work more useful than grouping every case under one fraud label.

Foire aux questions

Can a customer file a chargeback after receiving a refund?

A dispute notification can overlap with a refund, especially when timing or partial credits are involved. Check whether the refund completed and follow the provider’s case instructions; notification alone does not prove duplicate recovery.

Should I refund again after receiving a chargeback?

Before issuing another refund after a chargeback, reconcile the original refund and dispute debit with your provider. A separate payment can create an avoidable second credit.

Does refund evidence guarantee a chargeback win?

Refund evidence does not guarantee a chargeback win. The result depends on the completed credit, disputed amount, applicable condition, and timely submission.

You can organize evidence and manage supported responses with Chargeflow’s automated chargeback recovery.