Evidence and data quality
Chargeback Withdrawal Letters: Check the Bank Document Before Uploading
Check what the withdrawal document actually confirms before adding it to a chargeback response. A customer’s message saying “I canceled it” is different from a bank record identifying the disputed transaction and confirming a withdrawal action. Neither should be treated as a final case outcome without checking the processor’s status.
Start with an actionable case and its current response requirements. If evidence can still be submitted, preserve the relevant document and link it to the dispute. Do not assume that a withdrawal claim removes the need to respond or automatically restores the funds.
Separate customer intent from bank action
There are several possible records: a customer’s promise to contact the bank, a message saying contact occurred, a bank acknowledgment that a request was received, and a bank document describing the withdrawal itself. These records represent different stages.
Read the exact wording. “We received your request” does not necessarily mean the bank completed it. “Case closed” may refer to a bank service ticket rather than the chargeback. If the wording is unclear, ask the customer to obtain clarification from their bank through the appropriate channel; do not rewrite the bank’s statement yourself.
Shopify’s guidance distinguishes a customer’s request to reverse a dispute from the merchant’s evidence response. Preserve both the current case status and the available supporting statement. Shopify’s chargeback reversal guidance
For a formal bank document, retain the complete relevant page, including the issuing organization and date. Avoid a cropped sentence that removes the transaction reference or qualification needed to interpret it.
Check identity and transaction linkage
Verify that the document concerns the disputed merchant transaction. Shopify’s requirements checked on 6 September 2026 call for official bank letterhead, a case number, the original charge date and amount, the store or business name, confirmation of cancellation, confirmation that the customer was re-debited, and confirmation that funds were returned to the merchant. A bank-statement screenshot is insufficient. Recheck the current requirements before submission. Shopify’s withdrawal-letter checklist
A document can be genuine but unrelated. The customer may have several disputes with the same merchant or several card payments with the same amount. Use the strongest available case or payment reference, and ask the processor to confirm linkage when the bank’s reference differs from the merchant’s.
Check whether the document concerns the full disputed amount or only part of it. A withdrawal of one item does not necessarily resolve the entire case. Preserve any stated scope rather than summarizing it as “the dispute was withdrawn.”
Do not request a full card number or unnecessary bank-account information. The evidence should contain enough permitted information to establish the relationship, without turning the request into an identity-document collection exercise.
A hypothetical ambiguous bank message
A hypothetical customer sends a bank message saying, “Your request has been completed,” with no visible transaction details. The customer believes it proves their chargeback was withdrawn. The merchant has two open disputes from that customer.
The merchant should not attach the message with a caption identifying either case as withdrawn. Instead, the team records what is missing and seeks a document or clarification linking the completed request to the relevant transaction.
| Check | Finding in the example | Treatment |
|---|---|---|
| Issuing bank identifiable | Yes | Preserve the source context |
| Relevant transaction identifiable | No | Seek a matching reference |
| Nature of completed request clear | No | Do not infer withdrawal |
| Amount and scope clear | No | Keep both cases under review |
| Processor status updated | Not yet | Do not mark the case won |
If a later bank record identifies the relevant transaction and says the chargeback withdrawal was processed, attach that record with a precise caption. The merchant should still track the actual dispute status until the processor records its outcome.
Prepare a verification note
Use a short internal worksheet:
Dispute reference: [case]. Document source: [customer-supplied bank document or other accurate source]. Bank and issue date: [details]. Transaction linkage: [matching fields]. Document action: [request received, withdrawal processed or exact other description]. Amount covered: [full, partial or unclear]. Provider requirements checked: [source and date]. Unresolved questions: [specific gaps].
Keep the original document unchanged. If redaction is necessary, preserve the fields required to establish the case connection and label the evidence copy appropriately. If translation is needed, provide it alongside the original with its method disclosed.
Do not add a merchant-created bank letterhead, signature or certification. A summary can explain a document, but it must be visibly the merchant’s summary. The distinction between source and interpretation is central to the document’s credibility.
Submit the document within the existing workflow
Use the provider-supported response channel and the case’s actual evidence window. A withdrawal document belongs in the response only with an accurate explanation of what it establishes. It can accompany relevant transaction evidence rather than replacing the entire factual response with an unsupported declaration of closure.
Stripe similarly advises merchants to provide evidence even when the cardholder says the dispute was withdrawn. Its process is a separate processor workflow, but the distinction between a withdrawal claim and a recorded outcome is useful. Stripe’s withdrawal guidance
Retain the submitted document, the verification note and the response copy. If the processor later updates the case, record that event separately. A careful merchant record shows who said what, which transaction the document concerns and what the processor ultimately recorded, without collapsing those events into one assumed result.
Keep the dispute reason, amount and response deadline visible in Lower Chargeback while you prepare your response in Shopify or with your provider.
Related reading in this collection:
- Link a Chargeback to the Correct Shopify Order and Payment Record
- Using Shopify Sidekick to Understand a Chargeback Reason
- Does Canceling a Shopify Order Cancel Its Chargeback?