Visa reason code 13.7: what it means and how to respond
Visa reason code 13.7 covers canceled merchandise or services when the merchant fails to issue the credit owed. See rules, defenses, and deadlines.
What Visa code 13.7 means and when it applies
Visa code 13.7, “Cancelled Merchandise/Services,” covers a cancellation or return that should have resulted in a credit but did not. The central issue is not the quality of the purchase. It is the merchant’s failure to refund the amount after the cardholder canceled or returned the purchase under the applicable rule.
For a dispute to qualify as 13.7, all of these requirements must occur together:
- The cardholder canceled or returned the purchase. This includes returning or canceling merchandise, canceling a service, a timeshare, or a Guaranteed ReservationA hotel or rental reservation guaranteed with a card. If the customer does not show up and does not cancel under the policy, the merchant may charge a No-Show fee..
- The merchant did not refund the amount owed. It did not process the credit or a voided Transaction ReceiptA receipt the merchant issues to record the transaction. When marked void or canceled, it documents that the sale should not proceed to billing..
- There is a policy failure or a regional right. At least one of these conditions must apply: the merchant did not properly disclose its limited return or cancellation policy; it disclosed the policy but did not apply it; or, in Europe, the purchase came from an off-premises or distance-selling contract subject to a 14-day cancellation period.
Source for the requirements: Visa Core Rules §11.10.8.1, Table 11-128 (ID# 0030349).
Before the issuer files the case, the cardholder must try to resolve the problem with the merchant or the merchant’s liquidator. If the merchandise was shipped before cancellation and reached the cardholder, the cardholder must return it. The disputed amount is limited to the unused portion of the service or the value of the returned merchandise.
Some cases have their own conditions. For a timeshare, one of these situations is enough: the transaction was processed with an incorrect MCCMerchant Category Code identifies the merchant’s line of business. For a timeshare, an incorrect MCC may support a 13.7 dispute.; or the cardholder canceled within 14 calendar days of the contract date or of receiving the contract and related documents. After that period, the cancellation must follow the limited policy the merchant properly disclosed.
For a Guaranteed Reservation, one of these three situations is enough: the cardholder canceled under the policy but received a No-ShowA charge made when the customer does not arrive for a guaranteed reservation and does not cancel under the disclosed terms. charge; the No-Show charge covered more than one day of accommodation or rental, plus applicable taxes; or the cardholder tried to cancel within 24 hours of receiving the confirmation and was still charged.
In Europe, the 14-day cancellation right for off-premises or distance-selling contracts does not apply when at least one of these exceptions applies: the price depends on financial-market fluctuations; the goods are made to order; the goods are perishable; sealed goods are subject to health and safety restrictions; the goods are not received in physical form, such as a software download; the transaction is for travel and entertainment; or the merchant outlet is in Israel, Switzerland, or Türkiye. In that region, the cancellation itself counts as an attempt to resolve the matter.
Source for the rights, limits, and special cases: Visa Core Rules §11.10.8.2, Table 11-129 (ID# 0030350).
When the problem is different, use the corresponding code: 13.6 for a credit or voided receipt that was already issued but not processed; 13.3 for a quality or defect claim; 13.2 for a recurring charge processed after cancellation; and a Category 10 code when the cardholder says the transaction was not authorized.
Deadlines for each party under Visa 13.7
1 block represents 30 calendar days.
- IssuerWait 15 days before filing the 13.7 disputeThe waiting period starts when the merchandise is returned or canceled, or the service is canceled.15-calendar-day waiting period
- IssuerFile the 13.7 disputeThe clock starts when Visa processes the transaction, the cardholder receives the merchandise or service, or the expected receipt date arrives.Up to 120 calendar days
- IssuerFile the 13.7 dispute when timing runs from receiptThe clock starts when Visa processes the transaction.Up to 540 calendar days
- AcquirerSubmit a Visa-permitted defense pathThe clock starts when Visa processes the dispute.Up to 30 calendar days
- IssuerRespond to the acquirer’s defenseThe clock starts when Visa processes the acquirer’s defense.Up to 30 calendar days
- AcquirerRespond to the issuer’s pre-arbitration attemptThe clock starts when Visa processes the issuer’s pre-arbitration attempt.Up to 30 calendar days
- IssuerAsk Visa to decide the caseThe clock starts when Visa processes the acquirer’s pre-arbitration response.Up to 10 calendar days
Who files the dispute and what happens next
The issuer, the bank that issued the card, files the 13.7 dispute for the cardholder in VROLVisa Resolve Online is Visa’s system where the issuer files the dispute and the acquirer submits the response and case documents.. The merchant does not respond directly to Visa. It gives its records to the acquirer, the institution that represents it on the Visa network.
When the issuer files the case, it charges the transaction back to the acquirer and disputes the corresponding amount. If the acquirer accepts the claim, it may debit the merchant. If there is a defense ground, the merchant gives its records to the acquirer, which responds to Visa.
Source for the effect of the dispute: Visa Dispute Management Guidelines for Visa Merchants, pp. 5–6.
When filing the dispute, the issuer must provide all documents applicable to the case:
- For a standard cancellation or return: a detailed description of the merchandise or service, the date the cardholder received or expected to receive it, and the cancellation or return date. The description is not required when the Clearing RecordThe record sent after a purchase to present the transaction and calculate settlement among the participants. already contains sufficient Enhanced Data.
- If the merchandise was returned and the cardholder tried to resolve the issue with the merchant: the carrier’s name, invoice or tracking number, and the date the merchant received the merchandise. If the merchant refused the return or told the cardholder not to return it, the issuer certifies that fact and states where the merchandise remained.
- For a timeshare: the cancellation date and, when applicable, the date the cardholder received the contract.
- For a Guaranteed Reservation: confirmation of the No-Show charge, the expected service date, and the fact supporting the dispute: the date of a proper cancellation, the date of an attempted cancellation within 24 hours of the confirmation, or an indication that the charge covered more than one day.
- For an off-premises or distance-selling contract in Europe: the contract start date and proof that the cancellation occurred within 14 days.
Source for the filing documents: Visa Core Rules §11.10.8.5, Table 11-132 (ID# 0030353).
The issuer normally must wait 15 calendar days from the return or cancellation before filing 13.7. The wait does not apply if it would cause the case to exceed the filing deadline or if the merchant refuses the cancellation or return. After that, the issuer has up to 120 calendar days from the Transaction Processing Date or the date the cardholder received or expected to receive the merchandise or service. When the second date is used, filing may never occur more than 540 days after the Transaction Processing Date. For an Adjustment to a PIN-Authenticated Visa Debit Transaction, the clock starts on the Adjustment date.
Source for the filing deadlines: Visa Core Rules §11.10.8.4, Table 11-131 (ID# 0030352).
Code 13.7 follows the CollaborationThe dispute flow for Categories 12 and 13. In this flow, the acquirer may respond before the issuer attempts pre-arbitration. process. The acquirer has 30 calendar days from the Dispute Processing Date to submit a Dispute ResponseThe acquirer’s formal response in VROL. It contests the dispute with at least one ground Visa allows.. If the issuer rejects the response, it has 30 days to start pre-arbitrationThe stage where the issuer addresses the acquirer’s evidence and explains why the cardholder still disputes the transaction before asking Visa to decide.. The acquirer has another 30 days to respond. If the parties do not agree, the issuer may take the case to Visa arbitration within 10 days.
Source for the flow and response deadlines: Visa Core Rules §11.2.3, Table 11-2 (ID# 0030213), and §11.10.8.7, Table 11-134 (ID# 0031087).
Before building a defense, check whether this dispute is invalidProving any one condition is enough to challenge the dispute's validity.
- The transaction is an ATM Cash Disbursement.
- The transaction is a Straight Through Processing Transaction.
- The claim concerns only the quality of the merchandise or service, which belongs under code 13.3, unless there is a Credit Transaction Receipt.
- The dispute concerns only value-added tax (VAT), unless there is a Credit Transaction Receipt.
- The returned merchandise is being held by customs in a country other than the merchant’s country. In Europe, this exclusion does not apply to an off-premises or distance-selling contract.
- The dispute covers the cash portion of a Visa Cash-Back Transaction.
- The cardholder states that the transaction is fraudulent. In that case, the correct code belongs in Category 10.
- The transaction occurred at an Automated Fuel Dispenser.
Source:Visa Core Rules §11.10.8.3, Tabela 11-130 — Invalid Disputes, ID# 0030351
How to reduce the risk of this code
Visa recommends four controls that make the policy visible and the credit decision traceable:
- Show the policy before completing the sale. For a card-present sale, place the text near the signature on the Transaction Receipt or contract. If it appears on the back, obtain a signature on the front and initials beside the policy on the back. If returns are not accepted, state that on every copy before the customer confirms the sale by signature or PIN.
- Record acceptance at checkout. In e-commerce, show the policy on the same screen as the total, within the checkout sequence, or beside the submit button. Require a click, checkbox, or electronic signature. A separate link qualifies only when it is part of that acceptance and points to the return, refund, or cancellation policy.
- Apply the policy that was disclosed. Record the date, method, and content of the cancellation or return request. If the request does not follow the disclosed time limit or method, preserve evidence of that difference.
- Process the credit promptly. Keep the amount, date, and identifier linking the credit or reversal to the original transaction.
Source for the prevention measures: Visa Dispute Management Guidelines for Visa Merchants, Condition 13.7, pp. 46–47, and Visa Core Rules §11.10.8.6, Table 11-133 (ID# 0030354).
Evidence the merchant needs to gather
The merchant gives the documents to the acquirer, which must prove at least one of five grounds in the Dispute Response. The paths are alternatives; the merchant does not need to meet all of them. When one path contains multiple documents, however, every item in that path must be present.
- Credit or reversal overlooked by the issuer. Provide the record of the entry already processed, including the amount and date, and link it to the original transaction. The ARNARN stands for Acquirer Reference Number. It is the number created in the card scheme to locate a transaction, including a credit or Reversal. can provide that link.
- Invalid dispute. Prove at least one invalidity condition listed in Table 11-130 and shown above.
- The cardholder withdrew the dispute. Provide a letter or email from the cardholder stating that they no longer dispute the transaction.
- The policy was properly disclosed. For a card-present sale, provide the Transaction Receipt or contract with the required disclosure. For e-commerce, provide the checkout or order confirmation containing the policy and active acceptance. Table 11-133 treats this record as its own ground.
- The cardholder received the policy and did not follow it. Show that the cardholder received the policy and canceled outside the time limit or through the wrong method. Visa’s guidelines also allow records of continued service use or proof that the merchandise was not returned.
The two policy-related grounds are separate in the primary rule: at least one of the five grounds is enough. Even so, when the facts support it, combining proper disclosure with the cardholder’s noncompliance makes the causal link clearer: one record proves which policy was accepted; the other shows how the cardholder acted differently. This combination is a documentation recommendation, not a new Visa requirement.
A 13.7 defense cannot use CE3.0, Visa’s mechanism based on a history of three transactions and available only for code 10.4. The defense must remain within the five grounds above.
Source for the defense grounds: Visa Core Rules §11.10.8.6, Table 11-133 (ID# 0030354). Source for the credit, withdrawal, and policy documents: Visa Dispute Management Guidelines for Visa Merchants, Condition 13.7, pp. 46–47. Source for the scope of CE3.0: Evolution of Compelling Evidence — Merchant FAQs, question 1, p. 1.
Frequently asked questions
When does Visa use chargeback code 13.7?
All requirements must occur together: the cardholder canceled or returned merchandise, canceled a service, a timeshare, or a Guaranteed Reservation; the merchant did not process the credit or voided Transaction Receipt; and the merchant either failed to properly disclose a limited return or cancellation policy, or disclosed it but did not apply it. In Europe, an off-premises or distance-selling contract subject to a 14-day cancellation period may satisfy the third requirement.
When is a case Visa 13.7 instead of 13.6?
For a standard purchase, 13.6 covers a credit or voided Transaction Receipt that the cardholder already received but that was not processed; it also has a separate rule for ATM adjustments. Code 13.7 starts with a cancellation or return and a failure to issue the credit owed, in a situation tied to how the merchant disclosed or applied its policy. Both codes require the issuer to wait 15 days before filing the dispute, subject to the rule’s exceptions.
What can a merchant submit to defend a 13.7 dispute?
Visa accepts at least one of five grounds: a credit or reversal the issuer overlooked; an invalid dispute; the cardholder’s withdrawal; a record showing that the limited policy was properly disclosed; or proof that the cardholder received the policy and did not cancel according to it. Visa’s merchant guidelines recommend combining disclosure and noncompliance evidence when the defense depends on the policy.
Can a 13.7 defense use CE3.0?
No. CE3.0 applies only to code 10.4. A 13.7 response must use one of the grounds in Table 11-133 of the Visa Core Rules.
How many days does the acquirer have to respond to 13.7?
Table 11-2 of the Visa Core Rules gives the acquirer 30 calendar days from the Dispute Processing Date to submit the Dispute Response. The merchant deadline set by the acquirer or processor may be shorter.
How does 13.7 work in Europe?
In Europe, the code also covers off-premises or distance-selling contracts canceled within 14 days. The rule lists exceptions, including made-to-measure goods, perishable goods, software downloads, travel and entertainment transactions, and merchant outlets in Israel, Switzerland, or Türkiye.
View all Visa chargeback reason codes or return to Knowledge.