Visa 13.7 Chargeback: Cancelled Merchandise or Services

Document the cancellation as an event, not a label

Save the customer’s request, the channel used, the timestamp, and any confirmation sent by the merchant. If the business requires a return authorization or cancellation before a cutoff, show how that requirement was communicated and what the customer actually did.

For services, identify the service period that was cancelled and whether any work had already been performed. For merchandise, identify what was returned, the tracking number, and when the merchant received or rejected the return.

Match policy to facts instead of quoting policy at length

A return policy matters only when the reviewer can see how it applies to the transaction. Provide the purchase-time version, the relevant clause, and the event that satisfied or failed the requirement. If the policy changed after purchase, do not silently substitute the new version.

If the merchant made an exception or separately promised a refund, include that communication. The actual case history can supersede the clean hypothetical flow described by the standard policy.

Cancelled merchandise or services disputes depend heavily on timing and the merchant's cancellation policy. Reconstruct when the customer asked to cancel, what had already been delivered or performed at that moment, whether the merchant accepted the request, and whether any non-refundable portion was clearly agreed before purchase. A shipping label created after the customer cancelled does not by itself show that the merchant had a right to complete fulfillment. For services, separate completed milestones from work that had not yet begun.

Reconcile the money after the cancellation decision

Once the merchant decided that credit was due, follow the credit into the processor. If the refund was completed, show the transaction reference and amount. If no refund was due, explain the reason using the cancellation timeline and terms.

Store credits, store vouchers, replacement goods, and card refunds as different resolution types. A customer may still dispute the card transaction if they expected a cash-equivalent card credit and only received internal store credit.

Weak cases usually expose a handoff problem

A support agent may approve a cancellation but fail to notify billing. A warehouse may receive a return without closing the order. A service team may stop work but finance may continue invoicing. Those are not edge cases; they are common reasons cancellation disputes become hard to defend.

Run a reconciliation report across cancelled orders and completed credits. Any item stuck between those states deserves investigation before the customer escalates through the issuer.

Measure the specific cause behind each 13.7 case

Do not classify every case as “customer changed mind.” Record whether the merchant received goods late, denied a return, failed to stop a service, missed a refund, or disagreed about policy eligibility. Different causes need different operational fixes.

If the same product, campaign, or support queue produces repeated cancellation disputes, investigate that pattern separately from fraud. The merchant’s best defense is a process that leaves a complete cancellation and credit trail before the chargeback arrives.

Operationally, cancellation status must flow to fulfillment quickly. If support can approve a cancellation but the warehouse, scheduling system, or subscription platform continues automatically, the business will create repeat disputes even with a well-written policy. Add a timestamped cancellation state that downstream systems can consume, and audit orders where cancellation and shipment occurred close together. Those edge cases often reveal the real process gap.

Example: service canceled after a nonrefundable milestone

A customer cancels a custom service after the merchant completed an agreed design milestone but before final delivery. The merchant should split the transaction into performed and unperformed value, preserve the purchase-time cancellation terms, milestone acceptance, cancellation request, and any partial credit.

Defending the full charge solely because the policy says 'nonrefundable' may ignore what actually happened. The case should show why the retained amount corresponds to value already delivered or a disclosed commitment, while any unperformed portion is reconciled separately.

Break a cancellation case into service status, contractual status, and money

Cancelled merchandise or services cases often become muddled because three questions are treated as one. The first is operational: what merchandise or service remained undelivered when the customer canceled? The second is contractual: what cancellation or return term applied to that specific purchase, and was it disclosed before the transaction? The third is financial: what amount did the merchant keep, refund, or still owe after cancellation? Build those three tracks separately before writing a response. A policy paragraph cannot prove that a service milestone was completed, and a completed milestone cannot by itself explain why the entire price was retained.

For custom or staged work, map the transaction to milestones. Record deposit, design approval, procurement, production, delivery, or scheduled service stages and the customer's acknowledgement where it exists. If the customer cancels after value has already been delivered, quantify that value using the agreement or invoice rather than saying the work was 'mostly complete.' If no milestone structure exists and the merchant simply keeps the entire charge under a broad nonrefundable clause, the evidence may be less persuasive because the retained amount is difficult to connect to documented performance.

For merchandise, show whether the item had shipped, was intercepted, returned to sender, custom-made, or made available for pickup when cancellation occurred. If the merchant stopped fulfillment and later resold the item, that does not automatically determine the dispute outcome, but it is part of the economic story. For scheduled services, preserve appointment date, cancellation date, staff or resource commitment, and any rescheduling option. The goal is to explain what the customer asked to cancel and what the merchant had already done before that request.

Close with a precise amount bridge: original charge, value already delivered or committed under the disclosed terms, amount refunded, and remaining amount defended. If the merchant's own records show the full transaction should have been canceled without charge, accept that result and fix the workflow. Track cancellation disputes by cause—unclear terms, late support response, fulfillment already started, system unable to stop shipment, or disputed nonrefundable fee. That categorization gives the business a prevention plan instead of treating every 13.7 case as an isolated customer disagreement.

For Visa 13.7, the merchant should also separate a cancellation request from the point at which performance became unavoidable. A hotel room that can still be released, a custom item already in production, and a digital service already consumed do not create the same operational record. Preserve when the customer requested cancellation, what the published terms said, what the merchant actually did after the request, and whether any value was still delivered. If a cancellation fee or retained amount was charged, show how it was calculated rather than presenting only the final balance. That chronology helps a reviewer understand whether the dispute concerns a failed cancellation, a disagreement over the cancellation terms, or a later disagreement about money after the underlying service ended. These are related but not interchangeable questions.