Visa 13.1 - Merchandise/Services Not Received
- The customer paid and never got the goods or the service
- Your deadline is the date on your notice. The bank's own filing clock can start at the expected delivery date, not the sale. It's in Time Frames
- Your case is delivery proof with the full delivery address, showing receipt at the agreed place or by the agreed date. A partial-address scan isn't enough, and a signature isn't always required
- For digital goods there's no carrier to point at, so log access timestamps and IP from day one
Got this code?
Your deadline: The date on your notice wins. Your processor can set it earlier than Visa's standard limit for the response from your acquirer, the bank behind your processor (30 calendar days), and some domestic markets are shorter.
The claim: The customer paid for goods or services and says they never received them. They aren't denying the purchase, so the argument is never about whether they bought it. It's about whether it arrived.
Records that answer it:
- Carrier tracking: was it delivered? Get the carrier's confirmation
- Signed proof of delivery, if you have it
- For digital goods: download or access logs
- For services: the signed work order or completion record
Next: Decide whether it's worth fighting, then fill in the response outline for this claim and follow the Representment Workflow.
Records by what you sell
The same claim needs different records depending on what you sold. Find your column.
| What you sell | Shipped goods | Digital or online | In person or a service |
|---|---|---|---|
| Records that answer it |
|
|
|
| Where to find them |
|
|
|
Sources: Stripe's evidence by product type VENDOR; Shopify's evidence by reason VENDOR; Shopify's chargeback response page VENDOR; Square's dispute walkthrough VENDOR; Square's transaction search VENDOR. Source links accessed 24 October 2026; follow the labels shown in your processor dashboard.
When This Code Applies
- Physical goods never delivered
- Digital goods not accessible
- Services not performed
- You cancelled or can't deliver. If the customer cancelled before the expected delivery date, that isn't this code; see 13.7
- Merchant went out of business before delivery
Before the Bank Files
Two different things happen before the bank files with the network. The bank sits out a wait. Separately, the customer has to have tried to sort it out:
- The bank sits out the wait that fits the case - each wait, what starts it and when it falls away are in Time Frames below. The wait is the bank's, before it starts the network dispute. It doesn't stop the customer reporting the problem to the bank. A bank that files early has to explain why
- Attempt to contact merchant - A good-faith try with you, or with the liquidator, Ramp Provider or Conversion Affiliate where one applies. That try isn't needed where a travel agency used a Visa Commercial Card Virtual Account under an agreement with a travel and entertainment merchant covering the services in question
- Allow reasonable time - For delayed delivery
- Not receive the goods/services - For a partial claim, the amount is the missing goods or the unused service
Time Frames
| Scenario | Dispute Window |
|---|---|
| Bank files: by expected receipt date | 120 calendar days from the Transaction Processing Date or the customer's last expected receipt date, capped at 540 days from processing, except for a no-expiry third-party gift-card purchase where insolvency or bankruptcy prevented the third party providing the goods or services |
| Bank files: by expected service date | 120 calendar days from the Transaction Processing Date or the last expected service date, capped at 540 days from processing, except for a no-expiry third-party gift-card purchase where insolvency or bankruptcy prevented the third party providing the service |
| Bank files: Europe, required bond or insurance claim | Where the customer or traveler, or their bank for them, had to seek reimbursement from the scheme: a separate 60 calendar days from the scheme's letter or advice |
| Bank waits first: no expected date given | 15 calendar days from the Transaction Date. The wait falls away if you're insolvent or bankrupt, or waiting would run past the filing limit |
| Bank waits first: customer returned late goods, or tried to | 15 calendar days from the return or the attempt. The wait falls away if you're insolvent or bankrupt, or waiting would run past the filing limit |
| Bank waits first: you cancelled | 15 calendar days from your cancellation. The wait falls away if you're insolvent or bankrupt, or waiting would run past the filing limit |
| Bank waits first: travel agency (MCC 4722) or third-party event tickets, outside Europe | 30 calendar days from the service provider's cancellation. The wait falls away if you're insolvent or bankrupt, or waiting would run past the filing limit |
| Bank waits first: travel agency (MCC 4722) or third-party event tickets, Europe | 30 calendar days from your cancellation as merchant. The wait falls away if waiting would run past the filing limit, or the claim is for travel services from an insolvent or bankrupt provider covered by a bond or insurance scheme |
| Bank waits first: Europe, required bond or insurance claim | Where that reimbursement attempt was required: 60 calendar days from submitting the claim. Waived where the cover isn't enough, or waiting would overrun the filing limit. Insolvency on its own doesn't waive this one. This wait isn't the 60-day letter filing limit above |
NETWORK The issuer filing limits and waits for 13.1 are set out in the table above (Visa rules, 24 October 2026, section 11.11.2.4, Table 11-93, printed pages 755-756); source links accessed 28 October 2026.
Calculating Expected Delivery
- Merchant-stated delivery date, OR
- Reasonable shipping time if not stated, OR
- If no delivery or service date was specified, the bank waits 15 days from the Transaction Date before filing. That wait isn't a deemed delivery date, and it isn't the filing trigger
Representment Options
The answers also include an overlooked credit or reversal, an invalid dispute, a withdrawn dispute, and goods, services or flights the customer actually received or took, plus a qualifying future-availability route.
1. Goods/Services Were Delivered
Requirements:
- Proof merchandise was delivered
- Proof services were rendered
- Receipt at the agreed place or by the agreed date and time. For delivered goods the proof still needs the full delivery address. A scan with only part of the address isn't enough
Evidence:
- Signed delivery confirmation
- Carrier tracking showing delivered
- Proof of service completion
- Customer signature on work order
2. Delivery Confirmation
For physical goods:
- Tracking number with delivery status
- Signature confirmation (if obtained)
- Photo proof of delivery
- GPS coordinates of delivery
For digital goods:
- Download logs
- Access timestamps
- Email delivery confirmation
- Account usage after purchase
3. Refund Was Issued
When merchant already provided credit:
- Refund transaction details
- Date refund processed
- Refund confirmation email
4. Customer Picked Up Goods
For in-store pickup:
- Signed pickup receipt from the customer or their authorized person, or the collection code or PIN acknowledgment your pickup flow uses. A signature isn't the only way
- ID verification records
- Store security footage (if available)
- Pickup confirmation email
5. Services Were Rendered
For service businesses:
- Service completion documentation
- Work orders signed by customer
- Before/after photos
- Appointment records with outcomes
Required Documentation
For Delivery Claims
| Evidence Type | Where that leaves you |
|---|---|
| Signed delivery + full address | Meets the delivery test where the agreed place or the agreed date and time also matches |
| Tracking delivered + full address | The address on the proof must be complete, not partial |
| Tracking delivered + different address | The agreed-location test fails on this record |
| No tracking | Other permitted records can still prove receipt |
For Service Claims
| Evidence Type | Where that leaves you |
|---|---|
| Signed service completion | Records the service was received |
| Work order + photos | Supporting records of the work done |
| Appointment record only | Shows a booking, not receipt of the service |
| No documentation | Still check invalidity and any overlooked credit |
Representment Time Frames
| Stage | Window |
|---|---|
| Acquirer's response (Visa standard limit) | 30 calendar days; work to the date on your notice, which your processor can set earlier |
| Pre-arbitration, a second round if the bank pushes back | Your acquirer answers, normally 30 calendar days from the attempt's Processing Date. One shorter exception: Tanzania domestic gets 10 calendar days. Time Frames has the windows |
| Arbitration, where Visa decides | The bank files within 10 calendar days from the answer's Processing Date |
Which defenses hold up
| Evidence Type | What the evidence needs to show |
|---|---|
| Signed delivery + AVS match | The proof still needs the full delivery address. An AVS match doesn't replace it |
| Tracking delivered only | Carrier tracking shows delivery to the order address |
| Digital access logs | Logs show download or access after purchase |
| Service completion signed | Customer's signature records service completion |
| No delivery proof | No records to show delivery |
Track your own win rate by reason code.
A signature threshold is your own policy choice. Example: orders over $100. Visa doesn't set one. With no delivery proof, check for a refund you already issued, an invalid dispute, and the future-availability route. Nothing fits? Accept it, then fix how you prove delivery for what you sell.
Common Mistakes
- No tracking - No carrier record to send. Other records can still prove receipt
- Wrong address - Shipped to different address
- Missing signature - High value without confirmation
- Late response - Missing the deadline on your notice
- Insufficient logs - Digital goods with no access proof
Partial Delivery
When only some items delivered:
- Document what was delivered
- Provide tracking for delivered items
- Explain missing items (backorder, etc.)
- Limit the dispute to the undelivered portion, and handle any credit through your processor's instructions for the open case. Don't send a separate refund
Related Codes
Prevention Strategies
Shipping Best Practices
- Always use tracking - Every shipment
- Require signature - For high-value orders
- Ship to verified address - AVS match preferred
- Send shipping notifications - With tracking links
- Insure valuable items - Carrier liability
Delivery Confirmation
- Photo proof - Where carrier supports
- GPS confirmation - Delivery location
- Recipient name - Who signed
- Date/time stamps - When delivered
For Digital Goods
- Instant delivery - Reduce wait time
- Download logging - IP, timestamp, device
- Access confirmation - Email with details
- Multiple delivery methods - Email + account
For Services
- Completion documentation - Always get signature
- Before/after evidence - Photos, videos
- Appointment confirmations - Written records
- Follow-up communication - "How did we do?"
Next Steps
Prevent future 13.1 chargebacks:
- Always use tracking on shipments
- Require a signature above your own order value
- Send proactive shipping updates with tracking links
- Set up dispute alerts to catch early
See Also
- Reference - The whole reference section
- Is it worth fighting? - Weigh what responding costs against accepting this chargeback
- What proof each network accepts - Evidence requirements
- Refund Fraud - Return abuse patterns
- Friendly Fraud - First-party disputes
- Chargeback Prevention - Stop disputes
- Chargeback Alerts - RDR, Ethoca
- Representment - Fighting chargebacks
- AVS & CVV - Address verification
- Mastercard 4853 - MC equivalent
- Descriptors and Communication - Customer clarity
- Processor Management - Dispute handling