Visa 13.6 — Credit Not Processed
The customer was promised a refund that never came
By Byron Kiriibwa · Updated
When a customer says they were promised a refund that never came, the dispute is usually Visa 13.6, credit not processed. The bank decides on what you actually told the customer about a refund, the policy they agreed to at purchase, and whether a refund or credit was already issued.
The bank's test
The bank checks:
- Whether the seller gave the customer a refund confirmation, credit, or void notice for this payment.
- Whether that refund or credit was processed, and when.
- What the seller actually told the customer about a refund.
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Refund or credit already issued | Showing the credit or reversal, with its date, amount, method and reference. | Refund date, amount, and reference. | Stripe: Uncategorized fileSquare: Generic evidence | Every seller |
| Receipt or invoice | Showing that credit is tied to the disputed payment. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Messages with the customer | Showing the credit confirmation the cardholder holds is for a different purchase, or, dated after the dispute opened, saying they no longer dispute it. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
| Refund or return policy | Showing the cardholder didn't meet the policy's conditions, used only when the seller never confirmed a credit. | The policy as it read at the time of purchase, with the relevant clause quoted, plus how it was shown to the customer. | Stripe: Refund policy, Refund policy disclosure or Refund refusal explanationSquare: Cancellation or refund documentation | Every seller |
| Terms accepted at checkout | Showing the cardholder didn't meet the policy's conditions, used only when the seller never confirmed a credit. | A screenshot of the checkout page as it was at the time of purchase, showing the terms and the checkbox or statement, plus the acceptance timestamp if recorded. | Stripe: Refund policy disclosure, Cancellation policy disclosure or Uncategorized fileSquare: Purchase acknowledgement | Every seller |
| Return status | When the promised credit depended on a return that never arrived. | State whether a return was received, when, and in what condition, with any return tracking. | Stripe: Refund refusal explanation or Uncategorized fileSquare: Generic evidence | Online stores |
What doesn't help
- Proof of delivery, use or quality. Visa's question is whether the credit was due and processed.
- A refund the seller says it made, with no date, amount or reference tying it to this payment.
- A policy raised after the seller already confirmed the credit: a promised credit is expected to be processed.
- Internal delays as the reason a credit was late.
Visa's rules for 13.6
- Visa 13.7 (cancelled merchandise/services) shares this Stripe category; a claim about a cancellation rather than a promised credit is covered by Visa 13.7.
- Visa: 13.6 covers a credit or void receipt the cardholder received that wasn't processed, including a receipt marked "void" or "cancelled". Visa's accepted responses: a credit or reversal the seller issued that the issuer didn't take into account; the dispute is invalid (for example, the cardholder says the payment was fraud); the cardholder no longer disputes it. Visa's rules don't list a refund policy among them: once the seller has given a credit, the question is only whether it was processed. Source: Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.11.7; read 2026-10-29.
- From 24 April 2027, before filing, the issuer must add up every related credit and debit from the same seller, from 120 days before the disputed payment to the dispute, and dispute only the net amount; a credit it leaves out it must identify and explain. Until then, the issuer applies the credit or explains why it doesn't resolve the dispute. Source: Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.3.3; read 2026-10-29.
- Visa's merchant guide (Visa Dispute Management Guide for Merchants, October 2026, Condition 13.6; read 2026-10-29) adds one response the rules don't: no credit was due under the policy the seller disclosed, and the cardholder didn't meet its conditions for a refund. It applies only where the seller never confirmed a credit.
Common mistakes with Visa 13.6
- Arguing about the original purchase instead of whether the credit was due and processed.
- Sending a refund confirmation before the refund is actually processed.
- Refunding once it's a chargeback, so the customer is paid twice.
- Not saying the dispute is invalid when the cardholder calls the payment fraud.
Should you fight it?
Fight it only when you never promised a refund and your policy, shown at purchase, doesn't allow one, or when the refund was already issued. If you promised it in writing, accept the dispute. Accept it when any of these is true:
- The seller confirmed a refund or credit and it wasn't processed.
- The seller voided or cancelled the payment and the card was still charged.
- The seller can't show a credit tied to this payment by date, amount and reference.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- State who qualifies for a refund, and how long it takes, before purchase.
- Refund promptly in Stripe, within the time you told the customer.
- Once a refund is processed, email the customer a confirmation saying when it will appear; don't confirm earlier.
- Keep each refund's date, amount, method and messages.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
A customer buys a $120 item on July 3. On July 10 they ask for a refund; your reply on July 11 explains that the item can be returned within 30 days for a refund once it arrives back. They never send it back, and dispute on August 20 saying the refund never came.
The response would attach:
- Exhibit A: the refund policy shown at checkout on July 3: refunds once the item is returned within 30 days.
- Exhibit B: your July 11 email to the customer, explaining how to return the item for a refund.
- Exhibit C: your returns record, showing no return received.
- Exhibit D: the order receipt and delivery confirmation.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Visa reason code 13.6, for $120.00 charged on July 3. No refund was promised beyond our return policy, and no return was received.
The customer agreed to the refund policy at purchase. Checkout showed that refunds are given once the item is returned within 30 days (Exhibit A).
We told the customer how to get a refund. On July 11 we explained that the item could be returned within 30 days for a refund once it arrived back (Exhibit B). We did not promise a refund without a return.
No return was received. Our returns record shows nothing received from the customer (Exhibit C), and the item was delivered on July 6 (Exhibit D).
The customer was told how to get a refund under the policy they agreed to, and did not return the item. We ask that the dispute be decided in our favor.
Questions people ask
We did promise a refund but forgot to issue it. Should we fight?
No. Accept the dispute, and don't issue the refund as well: once it's a chargeback the money has already gone back, so a refund would pay them twice. The bank will look at what you told the customer, and a written promise decides it.
Can we issue the refund now, after the dispute started?
Not once it's a chargeback. Accept the dispute instead: the money has already gone back, so a refund would pay them twice. Before any dispute is filed, refunding is right. If it's still an inquiry, it depends on your platform: on Stripe and Shopify a full refund settles it while the platform still allows one; on Square, or for a dispute you entered by hand, ask the platform first.
Our policy says no refunds. Does that win?
Only if the customer saw it at purchase and you didn't promise otherwise. Internal notes the customer never saw don't help.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.