Returned Merchandise & Credit Not Processed Defense Playbook

Customer Timeframe 120 days from expected credit

Customer Difficulty Medium must prove merchant possession

Merchant Difficulty Low–Medium advantage if you know the rules

Industry Win Rate 62%+ when properly defended

Networks All 4 Visa · MC · Amex · Discover

The Most Misunderstood Rule in Chargeback Defense

THE KEY INSIGHT

When it comes to returned merchandise, merchants are generally provided the same benefit of the doubt that customers receive on non-receipt claims. It's not enough for a customer to show that they shipped merchandise back to you, or that it was delivered to a location that may or may not be associated with your business. Customers have to prove that the merchant has the returned merchandise back in their possession.

Most merchants instinctively assume they are on the defensive in every chargeback. When a customer claims they returned merchandise and never received a credit, the natural reaction is to scramble for proof that the return was never received, or that the refund was already issued.

But this framing is wrong. The same evidentiary standard that governs non-receipt disputes works in your favor on returns.

Think about how non-receipt claims work: when a customer says "I never received my order," it is not enough for the merchant to show they shipped the item. The merchant must prove the customer received it — with delivery confirmation, signature, GPS coordinates, or other proof of receipt. Simply showing a "shipped" status is not compelling.

Now apply that same logic in reverse: when a customer says "I returned the merchandise and never got my refund," it is not enough for the customer to show they shipped something back to you. They must prove you received it. A tracking number showing a package was shipped to your general business area is not the same as proving your business has the merchandise back in its possession.

This symmetry is the foundation of every successful return dispute defense.

Why This Matters

"Credit Not Processed" and return-related chargebacks are among the fastest-growing dispute categories, driven by the rise of e-commerce returns. Many merchants accept these chargebacks by default, assuming the customer's claim of having returned the item is sufficient. It is not. The same burden-of-proof principles that protect customers also protect you.

What This Dispute Means

The cardholder claims they returned merchandise to you and are owed a credit that was never issued. This dispute falls under the "Credit Not Processed" or "Cancelled/Returned" category across all four networks, and it requires the customer — not the merchant — to establish that the return was completed.

There are three common scenarios:

Customer returned merchandise and the refund was delayed or never issued — the most legitimate version of this dispute
Customer shipped something back but the merchant never received it — lost in transit, wrong address, or no actual return
Customer claims a return was made but has no proof of shipment or delivery — often friendly fraud or a fishing attempt

Your defense strategy differs significantly depending on which scenario you are facing. But in all three, the evidentiary burden starts with the customer.

Network Coding

Network	Code	Official Name
Visa	13.6	Credit Not Processed
Mastercard	4860	Credit Not Processed
American Express	C02	Credit Not Processed
Discover	RN2	Credit Not Processed

The Burden of Proof: Who Must Prove What

Understanding exactly where the burden of proof falls is the single most important factor in winning return-related disputes. This table breaks down the parallel between non-receipt and return claims.

Element	Non-Receipt Claim (Customer Says "Never Received")	Return Claim (Customer Says "I Returned It")
Who has the burden?	The merchant must prove the customer received the item	The customer must prove the merchant received the return
Shipping alone is not enough	Showing "shipped" status without delivery confirmation is insufficient for the merchant	Showing "shipped" status without delivery confirmation to the merchant is insufficient for the customer
Delivery to a general area	Delivery to "a location" near the customer is not the same as delivery to the customer's address	Delivery to "a location" near your business is not the same as delivery to your business and receipt by your team
What constitutes proof of possession?	Signature, delivery photo at correct address, post-delivery usage, customer acknowledgment	Your RMA system confirming receipt, warehouse scan of returned item, refund already processed based on received goods
Benefit of the doubt goes to...	The customer (when merchant can't prove delivery)	The merchant (when customer can't prove merchant received the return)

THE MERCHANT'S ADVANTAGE

This parallel means that on return-related disputes, you start with the same structural advantage that customers have on non-receipt claims. The customer must prove you have their merchandise. If they cannot, the dispute should resolve in your favor — regardless of what they claim happened.

Your Defense: Required Evidence

Even though the burden of proof is on the customer, you still need to build a structured response. Here is what to include.

#1 — Your return policy as disclosed at checkout

Screenshot or PDF of your return and refund policy as it appeared at the time of purchase.
If your checkout flow required the customer to acknowledge the policy, include a screenshot of that acknowledgment step with timestamp.
Key policy elements to highlight: return window, condition requirements, who pays return shipping, RMA requirements, restocking fees.

#2 — Whether the return was authorized

Scenario	Evidence to Provide
Return was authorized (RMA issued)	The RMA record showing what was authorized, the return shipping instructions provided, and the status of the return in your system.
No return was ever requested	A clear statement that the customer never contacted you to request a return or initiate the return process. Include your customer service records showing no return request on file.
Return was requested but outside policy	The customer's return request with its date, your policy showing the return window, and documentation that the request fell outside the allowed timeframe.

#3 — Whether the merchandise was actually received back

This is the core question. Your response should address it directly and factually.

Scenario	Evidence to Provide
You received the return and already issued a refund	Your warehouse receiving record, the refund transaction record with date and amount, and the ARN (Acquirer Reference Number) for the refund transaction so the issuer can trace the credit.
You received the return but it was outside policy or in unacceptable condition	Your warehouse receiving record, documentation of the condition issue (photos, inspection notes), your policy terms showing why the return was declined, and any communication sent to the customer about the declined return.
You never received the return	A clear, direct statement that no returned merchandise has been received at your facility. If you have an RMA system, show that no return has been scanned or logged. State that the customer has not provided proof of delivery to your business address.

CRITICAL POINT

When you state that no return was received, you are not required to prove a negative. The burden is on the customer to prove that you received the merchandise — with delivery confirmation to your business address, a signature from your staff, or other evidence of actual receipt. A tracking number showing a package was shipped in your direction is not sufficient, just as a tracking number showing a merchant shipped an order is not sufficient to prove customer receipt in a non-receipt dispute.

Strongly Recommended Evidence

#4 — Your RMA or returns processing records

If you use an RMA system, provide a screenshot showing the status of this customer's return (or showing no RMA exists for this order).
If you have a returns processing workflow, show the receiving log for the relevant time period demonstrating no return from this customer was logged.
If you have a third-party returns processor (like Returnly, Loop, or Happy Returns), provide their records.

#5 — Communication records

All email, chat, or phone communication with the customer about the return.
If you sent return instructions, include them — they show you acted in good faith and provided a clear process.
If the customer never contacted you before filing the chargeback, state that clearly. A dispute filed without any prior return request is a strong signal of friendly fraud.

#6 — Evidence that a refund was already processed (if applicable)

Refund transaction record from your payment processor, showing the date, amount, and transaction ID.
The ARN (Acquirer Reference Number) for the refund — this allows the issuing bank to trace the credit on their side.
If the refund was issued to a different payment method (store credit, check, etc.), document that and show the customer agreed to that method.

Critical Mistakes

Return disputes have one of the highest potential win rates for merchants, but these common errors give away cases that should be won.

Mistake #1: Accepting the chargeback because the customer "says" they returned it

This is the most expensive mistake merchants make. A customer's assertion that they returned merchandise is a claim, not evidence. Just as you cannot win a non-receipt dispute by simply asserting "we shipped it," a customer cannot win a return dispute by simply asserting "I sent it back." They need proof of delivery to your facility.

What to do instead

Respond to every return-related chargeback. Check your records. If no return was received, say so clearly and directly. The burden of proof is on the customer to demonstrate you have the merchandise.

Mistake #2: Treating a customer's tracking number as proof you received the return

A tracking number showing a package was shipped to your city, your ZIP code, or even your street address is not the same as proof your business received and processed the return. Packages are misdelivered, left at neighboring businesses, stolen from loading docks, or delivered to the wrong suite. The same logic that applies to customer non-receipt claims applies here in reverse.

What to do instead

If a customer provides a tracking number, verify it against your receiving records. If your warehouse or returns department did not log receipt of the package, the tracking number alone does not prove you have the merchandise. State this clearly: "While tracking number [X] shows delivery to a location in our area, our receiving records show no return from this customer was received or processed."

Mistake #3: Not having a documented returns receiving process

If you cannot demonstrate that you have a systematic process for receiving and logging returns, your denial of receipt is weaker. An organized returns process — with scan-in records, timestamped logs, and condition inspections — makes your "no return received" assertion far more credible.

What to do instead

Implement a documented returns receiving workflow. Every return should be scanned, photographed, and logged with a timestamp when it arrives. This creates an authoritative record you can reference: "Our returns receiving process logs every incoming package. No return from this customer appears in our receiving log for the period in question."

Mistake #4: Issuing a refund after the chargeback is filed

If a chargeback has already been filed, issuing a refund creates a double-credit scenario — the customer gets both the chargeback reversal and your refund. This is one of the most common operational errors in chargeback management.

What to do instead

Once a chargeback is filed, do not issue a separate refund. Fight the chargeback through representment. If you determine the customer is owed a credit, communicate that through the dispute response process so the resolution flows through a single channel.

Mistake #5: Providing no evidence and hoping the processor handles it

Many merchants let return-related chargebacks auto-close without responding, assuming the customer's claim is valid or that the amount isn't worth fighting. This is especially costly because return disputes are among the most winnable categories when the merchant simply responds with basic facts and records.

What to do instead

Respond to every return-related chargeback, even small ones. Your response can be straightforward: state your return policy, confirm whether a return was received, and if it wasn't, assert that clearly. The win rate on these disputes is high for merchants who simply show up with documentation.

Winning Response Framework

Step 1 — Identify the chargeback

Template Language

Case Number [1234567891234] (provided by your processor/acquirer) We are responding to the chargeback against the [MM/DD/YYYY] transaction made by [CUSTOMER NAME] in the amount of [$$$.$$]. Please find our response and supporting documentation attached.

Step 2 — Summarize your case and address the return claim directly

Template Language — No Return Received

The transaction was processed as payment for [product description]. The cardholder claims they returned this merchandise. Our records show that no return has been received from this customer. Our returns receiving process logs all incoming packages with timestamps and condition inspection. No return shipment from this cardholder has been received or processed at our facility for this order. The customer did not contact us to request a return authorization prior to filing this dispute. Our return policy, disclosed at checkout and included in the order confirmation email, requires customers to obtain a Return Merchandise Authorization (RMA) number before shipping any returns. No RMA was requested or issued for this order. To date, no evidence has been provided that demonstrates our business has received the returned merchandise back in our possession. The following documentation is attached: - Return and refund policy as disclosed at checkout - Returns receiving log showing no return logged for this order - Customer communication records (or confirmation of no contact) - Order confirmation and transaction details Please provide our documentation to the cardholder and request proof of return delivery to our business address.

Alternate: Refund Already Issued

Template Language — Refund Already Processed

The transaction was processed as payment for [product description]. The cardholder's return was received on [MM/DD/YYYY] and a refund of [$$$.$$] was processed on [MM/DD/YYYY] via [payment method]. The Acquirer Reference Number (ARN) for this refund is [ARN number]. The refund has already been issued for the full amount of this transaction. This chargeback, if upheld, would result in a double credit to the cardholder. The following documentation is attached: - Refund transaction record showing date, amount, and ARN - Returns receiving record confirming merchandise receipt - Original order confirmation

Step 3 — Sequence your evidence by strength

Priority	Evidence Type
First	Return status — receiving log showing no return received, OR refund transaction record with ARN if already processed.
Second	Return policy as disclosed at checkout, including RMA requirements and return window.
Third	Customer communication records (or lack thereof) — whether the customer contacted you about a return before filing.
Last	Original order confirmation, transaction details, and any prior order history.

Step 4 — Label and explain each exhibit

Template Language

Exhibit A: Returns Receiving Log Our returns processing system logs all incoming packages with date, time, sender, and condition assessment. This document shows no return from this customer was received during the period from [date] through [date].

Real-World Examples

The situation: $195 dress purchase. Cardholder disputed under Visa 13.6, claiming "I returned the item two weeks ago and never received my refund. I have a tracking number showing it was delivered."

Opening statement submitted:

Opening Statement

"The cardholder claims they returned merchandise and a credit was not processed. Our records show that no return has been received from this customer. Our return policy, disclosed at checkout and included in the order confirmation, requires customers to obtain a Return Merchandise Authorization (RMA) number before returning items. No RMA was requested or issued for this order. Our returns receiving department logs all incoming packages. No return from this cardholder appears in our receiving records. The tracking number referenced by the cardholder shows delivery to a USPS location in our city but does not confirm delivery to our business address or receipt by our staff. We have not received the returned merchandise back in our possession."

Evidence provided (in order submitted):

Page	Evidence
1	Returns receiving log for the two-week period in question, showing eight returns received from other customers but none from this cardholder.
2	Return and refund policy as displayed at checkout, highlighting the RMA requirement and 30-day return window.
3	Customer service records showing no communication from this cardholder requesting a return or providing an RMA request.
4	Original order confirmation with purchase details and the checkout acknowledgment of the return policy.

Result: Chargeback successfully represented. Dispute resolved in merchant's favor.

Why it won:

Directly addressed the core question: was the return received? The answer was no, supported by documented receiving records.
Framed the burden of proof correctly — the customer's tracking number showed delivery to the general area, not confirmed receipt by the merchant's business.
No RMA was requested, which undermined the narrative that the customer followed proper return procedures.
Receiving log showing other returns were processed during the same period demonstrated the system was operational and this return simply was not received.
Tone was factual and evidence-based — no accusations, no frustration, just documented facts.

The situation: $89 phone case order. Cardholder disputed claiming "I returned this product and the merchant won't refund me."

What they submitted:

Response Submitted

"We checked our warehouse and we don't think we received anything back from this customer. Our return policy says items must be returned within 14 days. This customer ordered over 3 weeks ago. We don't think we should have to refund this order."

Result: Dispute ruled in cardholder's favor.

Why it lost:

Mistake	Explanation
"Don't think we received"	Hedging language undermines credibility. A vague "don't think" is far weaker than "our receiving records confirm no return was logged." Without documented records, the merchant's assertion is just an opinion.
No return policy documentation	Claimed a 14-day return window but provided no evidence the policy was disclosed to the customer at checkout. An undocumented policy carries no weight.
No receiving records	No returns log, no warehouse scan records, no systematic evidence that they track incoming returns. Without a documented process, "we didn't receive it" is an unsupported claim.
Tone reads as evasive	"Don't think we should have to refund" frames the response as an opinion about fairness rather than a factual account supported by evidence.

What they should have submitted:

A definitive statement: "No return has been received at our facility for this order."
Returns receiving log or scan records for the relevant period
Return policy as displayed at checkout, with timestamp of customer acknowledgment
Customer communication records (or confirmation no return request was made)
A request for the customer to provide proof of delivery to the merchant's business address

Before You Submit

Return status

Clear statement: was a return received or not?
Returns receiving log or scan records for the relevant period
If return was received: refund transaction record with ARN
If return was received but declined: condition documentation and policy basis for denial

Return policy

Return and refund policy as disclosed at checkout
Customer acknowledgment of policy (if captured)
RMA requirement clearly stated
Return window and any conditions highlighted

Customer communication

All communication about the return included (or confirmation of no contact)
Return instructions sent to customer (if applicable)
Any resolution offers made and customer's response

Order documentation

Original order confirmation
Transaction details
Delivery confirmation of original order (to establish the customer received the merchandise initially)

Proactive Prevention

The strongest defense against return-related chargebacks is a documented returns process that creates an authoritative record — before a dispute ever arises.

Action	Why It Matters
Require RMA numbers for all returns	An RMA system creates a documented trail of every authorized return. Without an RMA, a customer sending an unsolicited package to your business address has no evidence you expected or received it.
Log every incoming package in your returns workflow	Scan-in records with timestamps, sender information, and condition photos create an authoritative receiving log. When you can show that eight other returns were logged during the same period but this customer's was not, that record is powerful evidence.
Provide prepaid return labels	When you provide the shipping label, you control the carrier, tracking, and destination address. This eliminates scenarios where customers ship returns to wrong addresses or use untracked methods.
Process refunds promptly after receiving returns	A fast refund turnaround (2–5 business days) reduces the window where a customer might file a chargeback out of frustration. Many "credit not processed" disputes are actually impatience disputes.
Send return receipt confirmations	When you receive a return, immediately email the customer confirming receipt and the expected refund timeline. This eliminates uncertainty and creates a documented record of receipt.
Make your return policy impossible to miss	Display it at checkout, in order confirmation emails, in shipping notifications, and on packing slips. The more visible the policy, the harder it is for a customer to claim ignorance during a dispute.

About This Guide

This playbook is updated at least twice annually to reflect changes in network rules and issuer practices. Document Version: 2026.1 · Last Updated: March 16, 2026 · Covers: Visa 13.6 / Mastercard 4860 / Amex C02 / Discover RN2

Related Guides

Continue building your chargeback defense knowledge: