Code13.6TypeConsumer disputeFiling window120 days from when the credit was expectedMonitoringDispute count (VAMP)What does Visa 13.6 mean?
The cardholder says a credit they were entitled to never appeared: a promised refund, a return that was accepted, a cancellation that came with money back.
Which makes 13.6 the most avoidable code on the network. The merchant usually agreed the money was owed. The dispute exists because the refund lost a race against the customer's patience.
What causes a 13.6 chargeback?
- A promised refund processed late, or never processed at all.
- A refund issued to a different card or method than the customer expected.
- Refund timelines nobody told the customer: 5 to 10 business days reads as never.
- A cancellation credit that was agreed on the phone and forgotten afterward.
Why do subscription businesses get 13.6?
The subscription version is predictable: a customer cancels, support promises a refund of the last rebill, and the refund takes long enough that the customer disputes it anyway. Now the same money goes back through a chargeback, plus a fee, plus a mark on the ratio.
Every 13.6 is a double payment for the same mistake: you refund the money and you take the dispute. Speed is the entire fix.
Can a chargeback alert stop 13.6?
Alerts catch 13.6 before it becomes a chargeback.
The customer contacts their bank first, so Visa RDR and CDRN see the dispute in time to resolve it, and it stays out of the VAMP dispute count. There is an irony to appreciate: the alert lets you refund quickly the money you were already refunding slowly. Cheaper to just be fast the first time.
Alerts are one of the two levers here. See how RDR, CDRN and Ethoca work together, and check where your ratio stands before the letter checks it for you.
How do you respond to a 13.6 dispute?
You win 13.6 by proving the credit was processed, or was never owed. Send:
- The refund transaction: amount, date, and the card or method it went to.
- The refund policy the customer agreed to, if the claim falls outside it.
- The communication where the refund terms were set, including any timeline given.
- For returns: whether the goods were actually returned as the policy requires.
Your processor sets your response deadline, usually 20 to 30 days from the chargeback.
How do you prevent 13.6?
- Process refunds the day they are agreed. The dispute clock is the customer's patience.
- Confirm every refund in writing with the amount and the arrival window.
- Refund to the original payment method unless the customer asks otherwise.
- Track promised-but-unprocessed refunds daily. That queue is tomorrow's 13.6 list.
The cardholder gets 120 days from when the credit was expected to file. You usually get 20 to 30 days to respond. And the dispute counts the day it files, win or lose, which is why prevention beats response.
FAQ
What causes a 13.6 chargeback?
A credit the customer was entitled to that never arrived or arrived too slowly: a promised refund, an accepted return, a cancellation credit. In most cases the merchant agreed the money was owed, and the dispute filed because the refund lost a race against the customer's patience.
How do I win a 13.6 dispute?
Show the credit was processed: the refund transaction with its amount, date, and destination. If the credit wasn't owed, show the policy the customer agreed to and the communication trail. If the refund went out before the dispute, the case usually resolves quickly.
Can chargeback alerts stop 13.6?
Yes. The customer contacts their bank first, so RDR and CDRN see the dispute before it becomes a chargeback, and resolving it through the alert keeps it out of the VAMP dispute count. The cheaper fix is refunding fast enough that the bank never gets the call.
Do refunds prevent chargebacks?
Only if they arrive before the dispute. A refund processed promptly usually ends the matter; a refund processed after the customer called their bank doesn't undo the dispute, which already counted. Refund speed, confirmed in writing, is the whole prevention story for 13.6.
Checked against Visa's Dispute Management Guidelines (June 2024) and Visa's dispute rules. Last reviewed August 28, 2026.
