The customer withdrew the chargeback. Why is the dispute still open?

“I called my bank and canceled the chargeback” is useful information from a customer. It is not confirmation that your processor has closed the dispute or returned the disputed funds. Treat withdrawal as an event to investigate within the existing case, not as a replacement for the case’s current status.

Keep four different events apart

There can be a gap between a customer deciding to withdraw, asking the issuer to do so, supplying bank documentation, and the processor recording a final outcome. A support agent may only see the first two.

Stripe explains that a withdrawn dispute can still be lost when evidence was not submitted and does not necessarily resolve faster. Its guidance is to submit evidence for a dispute you want resolved in your favor even when the customer says they are withdrawing it. Apply the current instructions for your provider rather than assuming the customer conversation has replaced them.

Create a case note that distinguishes the customer’s statement from the bank’s confirmation and the processor’s status. Include the time each was received or checked. “Withdrawal reported; response still required” is a more useful internal description than “resolved” while the case remains open.

Ask for the right document for your provider

If the customer has bank confirmation, ask for it through your normal support channel. Explain why it helps and what information is relevant. Do not ask them to send an entire bank statement when a narrower document will meet the provider’s requirements.

The requirements are not interchangeable. Stripe says withdrawal confirmation can support the response but is not required. Shopify’s workflow calls for an official bank withdrawal letter and says a bank-statement screenshot is insufficient. Use the instructions for the provider managing the case.

Check that any document concerns the same payment and case. A customer with two disputed renewals may have withdrawn only one. An email mentioning “the subscription charge” is not enough to decide which case should change.

Protect the response deadline

Keep a named owner and the actual evidence deadline. Continue assembling a response to the recorded dispute reason while the customer contacts their issuer. Waiting for a promised letter should not quietly consume the submission window.

The response should explain the underlying transaction with relevant records. Add withdrawal material where the provider directs, while keeping its meaning precise. A message saying “I will contact the bank tomorrow” supports an intention to act, not a completed withdrawal.

After submission, retain the confirmation and check the live status. Do not repeatedly submit the same material just because the customer has not yet seen a change. Whether more evidence can be added depends on the provider and stage of the case.

A refund promise needs its own reconciliation

A merchant may agree that the customer should receive money back. That decision needs coordination with the dispute workflow so separate teams do not initiate conflicting reimbursements.

Stripe says an open disputed charge cannot be refunded until the issuer decides in the merchant’s favor. Do not promise an immediate refund merely because the customer has requested withdrawal. Check the current available actions and explain the dependency before committing to a payment date.

Illustrative example. A customer disputes a €48 renewal, then agrees that the charge was recognizable after support identifies the product. They report asking their bank to withdraw. Support marks the ticket closed, but the processor still requires a response. The case owner should keep the dispute task active, submit the relevant transaction records on time, and monitor the outcome. A resolved support misunderstanding and an unresolved payment case can coexist.

If a refund was also promised, attach that promise to the same case so finance can act from the verified status. Our missing-refund guide explains how to distinguish a commitment from an actual refund record.

Close the case with a verifiable outcome

The closure note should identify the final provider status, when it was checked, the corresponding funds movement, and any remaining customer commitment. A “won” label and a refunded customer are different facts; neither should be inferred from the other.

If a customer reports a late withdrawal after a loss, inspect the provider’s support route rather than promising a reversal. Stripe notes that issuer support for late withdrawals varies. Preserve the relevant correspondence and explain what is still unknown. The useful answer is the current payment state and the next accountable action, not a prediction of the issuer’s decision.

Keep the conversation connected to the payment case

Evidenz is designed to keep the customer conversation connected to the payment history that explains it. For B2B and B2C SaaS teams reviewing a withdrawal, that means preserving what the customer actually said, which subscription charge they meant, any refund promise, and the provider-status check recorded by the team. For support and finance, the value is continuity: a closed recognition question does not erase an outstanding response task or payment commitment. A shared account of those facts gives the next owner a reasoned next step without treating a customer message as a bank decision.