Amex C08 Chargeback: Goods or Services Not Received

Physical goods: prove the last mile

Use the carrier, tracking number, ship date, delivery event, and destination details that connect the package to the order. Where available, include signature, pickup, or delivery-photo information. A tracking screenshot that shows only a ZIP code may be less persuasive when the customer claims delivery went elsewhere.

If the customer requested an address change or carrier hold, include the request and updated delivery path. That context explains why the final destination may differ from the original checkout address.

Services need a different evidence stack

For appointments and professional services, use booking records, attendance, work logs, delivered files, customer approvals, or access history. The objective is to show that the merchant performed or made the service available according to the purchased terms.

An invoice proves that the merchant billed. It does not prove that the service occurred. Pair billing records with completion evidence that an outside reviewer can understand.

C08 can cover goods or services not received or only partially received, so the evidence should match the delivery model. Physical goods need shipment and delivery records tied to the order. Digital goods need access, download, activation, or usage events. Services need appointment, work-order, milestone, or completion evidence. If the customer received only part of an order, show which line items were delivered and what happened to the rest instead of treating one delivered package as proof of the whole purchase.

Handle partial receipt explicitly

If a five-item order shipped in three packages and one item was delayed, list each item, shipment, and outcome. If the dispute amount corresponds only to the missing item, do not argue as if the entire order was received. A precise partial-fulfillment explanation is more credible.

The same logic applies to services: separate completed milestones from undelivered work. The merchant’s response should match the amount and scope actually disputed.

Customer messages can connect the fulfillment trail

A message such as “I received the first package but not the second” can be useful because it narrows the issue. So can a support conversation that confirms successful access to a digital product. Preserve the full context rather than cropping one favorable sentence.

If support acknowledged a lost package and promised replacement or refund, that later resolution becomes part of the case. The merchant cannot reasonably ignore its own remediation promise.

Reduce C08 through fulfillment observability

Track delivery exceptions, unscanned handoffs, split shipments, failed digital entitlements, and missed appointments before they become disputes. For high-value goods, consider stronger delivery confirmation when the economics justify it.

A monthly C08 review should distinguish carrier loss, wrong address, porch theft, warehouse error, customer confusion, and service non-performance. Those are different operational problems despite sharing the same network reason family.

Partial fulfillment deserves its own accounting. Split shipments, backorders, cancellations, and partial refunds should be visible in the same timeline. A reviewer should be able to see that a $300 transaction contained, for example, $220 of delivered goods and an $80 item later refunded. This structure also helps the merchant decide whether contesting the full disputed amount is appropriate or whether only part of the transaction is supportable.

Example: Amex C08 for a service with no shipping record

A consultant delivers a scheduled remote workshop. There is no carrier proof, so the merchant should use booking confirmation, meeting/session logs, attendee access, deliverables, and follow-up communication to show performance. The evidence must connect the disputed customer or organization to the service event.

If the session was canceled or the customer could not access it, those facts matter more than an invoice marked paid. C08 for services is a completion problem, not a shipping problem, and the evidence stack should reflect how the service is actually delivered.

Create a delivery model that fits the product instead of forcing everything into tracking

C08 evidence should mirror how the merchant actually fulfills the sale. For shipped merchandise, connect the order to the label, tracking number, destination, delivery event, and any signature or pickup record. For local pickup, show ready-for-pickup notification and handoff. For digital products, show entitlement creation, access or download events, and customer-support history. For services, use booking, attendance, work orders, deliverables, sign-off, or other completion records. A generic invoice marked paid proves the charge, not the customer's receipt of goods or services.

Partial fulfillment needs item-level accounting. If a three-item order shipped in two parcels and one item was canceled, create a table with each item, price, shipment or service record, delivery status, and refund. The disputed amount may correspond to only one line. Proving the other two items arrived does not answer non-receipt of the third. The same principle applies to multi-session services or subscriptions where one period was delivered and another was not.

Customer communications can close gaps in the fulfillment trail. A message acknowledging receipt, asking how to use the product, reporting a defect after arrival, or arranging a return may corroborate that the transaction progressed beyond non-receipt. Present those messages in context and avoid treating them as stronger than they are. A support ticket about a related order should not be used unless it can be linked clearly to the disputed transaction.

After the case, distinguish true non-delivery from visibility failures. A merchant may have delivered successfully but retained inadequate records, or it may have a real carrier, fulfillment, scheduling, or digital-access problem. Track C08 by fulfillment method, carrier, warehouse, service team, and product. The prevention goal is twofold: improve actual delivery performance and ensure that the systems keep a verifiable record of successful performance long enough to answer later disputes.

Use customer acknowledgement to corroborate service delivery without overstating it

For services, post-performance communication can be especially valuable. A customer who asks for a revision to a delivered report, discusses the content of a completed session, or requests support for a service outcome has provided transaction-specific context that the service occurred. Preserve the complete message and date. Do not describe the message as acceptance of quality unless the customer actually says that. The same communication may prove receipt while also documenting a complaint, and both facts should remain visible in the case.

In a not-received case, delivery or service completion should be mapped to the specific item the cardholder says was missing. Multi-item orders, partial shipments, substitutions, and staged services can make a generic “order delivered” statement misleading. List the disputed item, its fulfillment event, destination or access record, and any customer acknowledgement that refers to that item. If one part of the order failed while another succeeded, do not use the successful portion to imply complete performance. For services, identify the session, appointment, access period, or completed milestone instead of relying on a final invoice alone. This item-level approach makes the response easier to review and also helps the merchant identify whether the root cause was fulfillment failure, customer recognition, or an internal order-splitting problem.