Reembolsos por «artículo no recibido»: la guía más completa para comerciantes en 2026
Contracargos?
Ya no es problema tuyo.
Recupera cuatro veces más Contracargos y prevención , hasta un 90 % de las entradas, gracias a IA y a una red global de 20 000 comercios.
En resumen:
- Match the disputed item to its promised and actual fulfillment.
- Distinguish shipment creation, delivery, and complete order receipt.
- Use the actual network subtype and response deadline.
- Reconcile partial fulfillment, replacements, and refunds before responding.
An item not received chargeback is a dispute alleging that purchased goods or services were not provided as agreed. The merchant’s response should connect the disputed payment to the promised delivery or service date and the actual fulfillment record.
{{cta}}
Distinguish Non-Receipt From Other Claims
Non-receipt can concern an entire order, part of a shipment, digital access, or an unperformed service. It is different from receiving something that did not match its description or disputing authorization of the payment.
Do not classify every non-receipt complaint as friendly fraud. A carrier delay, incorrect address, failed digital entitlement, or cancellation can create a valid complaint. A delivered status is a record to investigate, not proof of customer intent.
Use the Actual Code and Claim
Visa uses condition 13.1 for merchandise/services not received. Mastercard’s current merchant guide includes goods/services not provided within its cardholder-dispute framework, including 4853. Legacy or provider-specific labels can differ, so do not use 4855 as the universal current code for all non-receipt claims.
Consult the Visa merchant dispute guide and Mastercard merchant chargeback guide alongside your notice. The reason-code guide explains why the claim and subtype matter.
For American Express non-receipt cases, consult Amex C08 goods or services not received when that code appears on the notice. Match the claimed missing goods or services to the disputed order and the fulfillment records.
Match Evidence to the Fulfillment Model
| Fulfillment Model | Records to Connect | Important Limit |
|---|---|---|
| Productos físicos | Order, promised date, shipment, delivery address, and carrier events | A created label does not show delivery |
| Split shipment | Each item, parcel reference, and delivery result | One delivered parcel does not prove the entire order arrived |
| Productos digitales | Entitlement, delivery of access instructions, access attempts, and usage | Provisioning access does not prove it worked |
| Subscription service | Billing period, service availability, account access, and cancellation | Payment history alone does not establish service delivery |
| Event or appointment | Scheduled date, attendance or access, changes, and cancellation notices | A confirmation proves booking, not that the event occurred |
Investigate Before Deciding to Challenge
Follow the current case and provider requirements
Investigate the missing item before choosing a response
Match the payment
Match the dispute amount and payment ID to the order.
Identify what is missing
Identify what the customer says is missing and the promised date.
Verify fulfillment
Check whether delivery or service actually occurred.
Review exceptions
Review address changes, failed access, carrier exceptions, and support messages.
Check prior remedies
Check completed refunds and replacement orders.
Choose the supported response
Choose acceptance or a supported challenge based on the records.
For a hypothetical split order, the customer may have received one parcel while the disputed item was still in transit. A response showing only the first parcel’s delivered status would not answer the missing-item claim. Map each disputed item to its own fulfillment record.
For digital products, use the digital goods evidence guide to distinguish access granted from actual use. For physical goods, explain any difference between the checkout address and the delivery destination.
Use the Case Deadline and Relevant Dates
The filing window can depend on when goods or services were expected, not just the payment date. The merchant’s response deadline is a separate clock. Use the cutoff displayed by your provider rather than a generic network-day count.
Retain the promised date, any agreed change, and the actual fulfillment date. Do not silently replace the original promise with a later estimate when building the timeline. The chargeback process guide explains submission ownership and confirmation.
Keep Buyer Protection and Chargebacks Separate
A marketplace or payment platform may assess a buyer-protection request under its own terms. A card chargeback follows the issuer’s dispute process. Coverage under one process does not automatically establish coverage under the other.
Check the applicable protection terms and whether a refund has already been completed. Use refund reconciliation to avoid duplicate credits. Do not assume a customer’s report of withdrawal closes an active card dispute.
Build a Clear Submission and Fix Repeated Failures
Present the relevant order, fulfillment, and communication records in date order with a short explanation of what each establishes. Use the representment guide and evidence standardization checklist to keep identifiers consistent.
After resolution, review complaints by carrier, product, digital entitlement process, and promised service date. Improve the specific failures instead of making every order harder to complete. If evidence collection needs coordination, explore Chargeflow’s automated recovery workflow.
Annotated physical and digital nonreceipt packets
| Exhibit | Physical order | Digital product |
|---|---|---|
| Payment and order match | Order ID, payment ID, item, amount, and delivery promise. | Payment ID, account ID, purchased entitlement, and access promise. |
| Fulfillment chronology | Carrier events, destination match, and any signature record. | Entitlement creation, access events, timestamps, and relevant account records. |
| Customer allegation | Customer messages and any address or delivery issue. | Reported access failure and support troubleshooting records. |
| Limits to explain | A delivered scan alone may not identify the recipient or prove the contents. | An entitlement alone may not prove successful customer access. |
Write a short chronology that identifies the disputed payment and explains each exhibit’s relevance. Use the nonreceipt response templates and digital-goods guide for the appropriate product type. Do not use payment authentication as a substitute for fulfillment evidence.
Continue learning: Evidence and escalation
Use Chargeback Evidence and Escalation: Choose Your Next Step to choose the next merchant task in this topic.
- Chargeback Reason Codes: Network Examples and Evidence: Reason-code interpretation and routes to claim-specific evidence.
- What Is Chargeback Representment? Definition and Process: Merchant evidence submissions and the decision to counter a dispute.
Sources and scope
Source notes updated: October 11, 2026. Merchant evidence and response handling. Match records to the actual allegation and payment. Escalation eligibility, file requirements and the submission cutoff come from the applicable network and merchant provider.
- Stripe: claim-specific evidence guidance
- Stripe: responding to card disputes
- Visa: current public rules and editions
For a live case, retain the governing document’s edition or effective date, the relevant provision, and the provider notice.
Preguntas frecuentes
Does a tracking number prove an item was received?
A tracking number identifies a shipment. Its status, delivery destination, and connection to the disputed item determine what it can establish about receipt.
Can digital goods receive item not received disputes?
Digital goods can receive non-receipt disputes when access or delivery is alleged to have failed. Review entitlement, access instructions, system events, and support records.
Is Mastercard 4855 always the current non-receipt code?
Do not treat 4855 as a universal current code. Mastercard’s cardholder-dispute framework includes goods/services not provided under 4853, and the actual notice and subtype should guide the response.
What if only part of an order was received?
For partial receipt, identify the disputed items and match each to its shipment or service record. Reconcile the disputed amount with any completed partial refund.
Contracargos?
Ya no es problema tuyo.
Recupera cuatro veces más Contracargos y prevención , hasta un 90 % de las entradas, gracias a IA y a una red global de 20 000 comercios.













.png)


