Visa reason code 13.1 is commonly used for disputes alleging that merchandise or services were not received. For a merchant, the operational question is straightforward: can you show what was purchased, when it was supposed to be delivered, and what record demonstrates that delivery or service performance occurred?
This guide is an evidence workflow, not a substitute for the current Visa rules or your acquirer’s instructions. Processor interfaces may translate, group, or rename network categories, and deadlines can vary.
Confirm the allegation shown in your processor
Read the full dispute notice and confirm that the issue is non-receipt rather than quality, cancellation, fraud, or duplication. Similar customer stories can be routed to different categories, and the response should follow the category actually filed.
Record the response deadline, disputed amount, order ID, and transaction ID before building the packet.
For physical goods, prove the fulfillment chain
Pair the order with the shipment: item, address, fulfillment time, carrier, tracking number, final delivery event, and signature or pickup information if available. If there were multiple packages, show which items traveled under each tracking number.
If the address changed after purchase, include the customer request or account action authorizing the change.
For services, prove performance
Use appointment records, signed completion documents, delivered work product, project milestones, access logs, meeting records, or customer acknowledgements. The evidence needs to connect the disputed payment to the service actually provided.
For ongoing services, show the period covered by the charge and the work or access delivered during that period.
Address delays and exceptions explicitly
If delivery was late, explain the promised date, actual date, customer communication, and any remedy. Hiding a delay can make an otherwise understandable case appear incomplete.
If the merchant ultimately refunded the transaction, include the refund record and check whether the dispute amount already accounts for it.
Keep the rebuttal short
A useful summary might identify the transaction, state the delivery or performance event, and point to the supporting record. Avoid long arguments about policy when the central issue is whether the customer received the goods or service.
Use your processor’s current evidence fields and formatting requirements because submission rules can change.
Separate non-receipt from late delivery and partial fulfillment
A Visa 13.1 case may look like simple non-receipt, but the merchant should check whether the real fact pattern is delay, partial shipment, failed delivery, service rescheduling, or a replacement. Label each item or service milestone and reconcile any credits so the packet does not defend value that was never delivered.
If the carrier shows return-to-sender or the service record shows cancellation before performance, treat those as adverse facts. A concise packet that concedes the failed portion is stronger than a full-value defense built around one successful event.
Example: Visa 13.1 after a replacement shipment
A merchant's original parcel is marked lost, the customer reports non-receipt, and the merchant sends a replacement that is delivered before the chargeback deadline. The 13.1 packet should show the original failure openly, then the replacement agreement, new tracking, delivery event, and customer communication. Hiding the original failed shipment makes the chronology look inconsistent.
If the replacement arrived after the customer filed the dispute, timing matters. The merchant should state when the remedy occurred and check the live case to determine what evidence or action is available. The article's workflow organizes facts; it does not turn late performance into an automatic defense.
Match evidence to what was allegedly not received
Visa 13.1 can involve physical merchandise, services, or other promised value, so the first job is to identify the exact undelivered item or service in the live case. For a multi-item order, do not submit one tracking number as though it proves every line was fulfilled. For services, replace shipping evidence with appointment, access, completion, or acceptance records that fit the transaction.
If the merchant refunded or replaced part of the order, include that event and reduce the supported amount accordingly. A clean item-by-item or service-by-service ledger is often more persuasive than a large packet of screenshots.
A practical Visa 13.1 review from promise to performance
For a Visa 13.1 case, organize the file around the promised delivery or service date rather than around whatever evidence is easiest to export. Identify what the merchant agreed to provide, where or how it would be delivered, and the expected date. Then show the actual fulfillment event. For merchandise, connect order line items to carrier or pickup records. For services, use appointment, work-order, attendance, completion, or account-use records appropriate to the service. The dispute is about receipt or performance, so authorization evidence alone usually does not resolve the core allegation.
Delayed delivery needs its own chronology. Preserve messages telling the customer about the delay, any revised date the customer accepted, and the eventual fulfillment or cancellation. Visa's merchant guidance emphasizes keeping customers informed when delivery will be delayed, which is operationally important because an unexplained delay can turn a fulfillment problem into a dispute. If the customer canceled before late fulfillment, do not frame the later shipment or service as though the original timing problem never existed.
When a replacement or partial remedy exists, reconcile it explicitly. Show the failed original shipment or service attempt, the replacement agreement, the new fulfillment event, and any remaining missing value. If an order contained several items, map each item to delivered, replaced, refunded, or unresolved status. A full-order defense is weak when the evidence only proves part of the order was received. The amount being contested should match the value the merchant can actually support.
Before submission, compare the live processor case with current Visa documentation and the acquirer's instructions because available responses and required documentation can depend on the specific dispute record. The article's workflow should help merchants assemble facts; it should not imply that any one tracking scan guarantees a win. A strong 13.1 packet is a transparent performance history that answers when, where, and how the promised value reached the customer—or candidly identifies the portion that did not.
Reconcile service non-receipt differently from merchandise non-receipt
Visa 13.1 can involve services as well as shipped goods, so the evidence model must match the fulfillment method. For an appointment, show booking, attendance, provider work, and any deliverable. For consulting, use meeting records, reports, or accepted milestones. For a digital service, use entitlement and meaningful account activity. A tracking screenshot is irrelevant when no physical shipment existed, and an invoice alone does not establish service performance.
If the transaction combines physical and service components, split the value. A hardware purchase with installation, or a product bundle with training, may have one part delivered and another missed. Show the amount or contractual allocation where available, then reconcile any partial credit. This prevents the merchant from proving the easy half of the transaction while ignoring the service component the customer actually says was not received.
VERIFY CURRENT RULES
Primary references
Processor interfaces, reason-code mappings, filing windows, and network rules can change. Check the active dispute notice and current official documentation before submitting.