Visa Reason Code 13.6: Credit Not Processed

What Visa reason code 13.6 means

Reason code 13.6 is the Consumer Disputes code for missing refunds. The cardholder has something from you, such as a refund confirmation, a credit receipt or a return authorization that promised a credit, and says the money never reached their card.

Visa generally expects the cardholder to wait 15 days from the credit acknowledgment or return before disputing, to give the refund time to post. That waiting period has exceptions (for example when it would push the dispute past its time limit), so a 13.6 can sometimes arrive sooner.

13.6 is a collaboration code. You can respond in the dispute-response stage, and the issuer can escalate to pre-arbitration.

The key fact: many 13.6 disputes arrive after the refund was already issued. Credits can take days to appear on a statement, and cardholders who don’t see one sometimes dispute instead of waiting.

Common causes

• Refunds issued but not yet visible on the cardholder’s statement
• Returns sitting at the warehouse, unprocessed, past the promised refund window
• Partial refunds or restocking fees the customer didn’t expect
• Store credit or exchanges offered when the customer expected cash back
• Refunds issued to a different payment method or a replaced card
• Support agents promising refunds that never get processed

Evidence that wins a 13.6 dispute

1. The refund record: amount, date, and the processor’s reference or acquirer reference number (ARN) that lets the issuer trace the credit to the cardholder’s account.
2. A refund confirmation sent to the customer, with the same details.
3. If no credit was owed, your return policy as disclosed at purchase (window, condition requirements, restocking fees, final-sale items) and proof it was shown.
4. Return status: warehouse records showing the item was never received, arrived outside the window, or arrived used or incomplete.
5. For partial refunds, the calculation, with the policy clause that allows the deduction.
6. Customer communication showing what was actually promised. A “we’ll refund once we receive the item” email is not the same as a credit acknowledgment.

How to prevent 13.6 chargebacks

• Process refunds within a day of receiving returns, and say so in your policy.
• Email refund confirmations that include the amount and a reference number, and tell customers how long their bank may take to post it.
• Make return windows, restocking fees and final-sale terms visible before checkout.
• Train support not to promise refunds that depend on a return you haven’t received.

Should you fight or accept?

Fight when you already refunded (the refund record usually settles it), or when your disclosed policy meant no credit was owed. These are among the most winnable consumer disputes. Our guide to chargebacks after a refund covers the refunded case in detail.

Accept when you promised a credit and didn’t process it. Don’t refund separately after the dispute arrives, or the customer is credited twice. Then find out where your refund process broke.