Amex C28 Chargeback: Cancelled Recurring Billing

Start with the Cardmember’s cancellation details

The chargeback information can include a cancellation number, date, email, written request, or acknowledgement. Compare those details with the merchant’s own support and subscription systems. If the merchant has no matching record, investigate whether the request arrived through a channel that was not integrated into billing.

Do not dismiss an attempted cancellation merely because the subscription status stayed active. The point of the evidence review is to determine why it stayed active.

Show how recurring billing was authorized and disclosed

Preserve the recurring-billing terms accepted at enrollment: price, frequency, trial conversion if any, and cancellation procedure. If the merchant relies on a policy, explain how it was presented to the Cardmember rather than attaching a current terms page with no transaction link.

For introductory offers or trials, keep the specific version of the offer. Recurring disputes are especially difficult when the business cannot prove what price or cadence the customer expected after the introductory period.

Cancelled recurring billing disputes are easiest to review when the merchant can show the subscription state over time. Preserve the original consent, billing interval, amount, renewal notices, disputed renewal, cancellation attempt, support response, and effective service end. If cancellation was available through multiple channels, search all of them. A customer who cancelled through support should not be treated as active merely because the self-service portal still showed the plan as enabled.

Continued use is context, not a substitute for cancellation timing

If the customer used the service after the claimed cancellation, show the relevant access history. That may help explain the merchant’s view that the account remained active. But continued use does not automatically erase an earlier valid cancellation request.

Put usage beside the subscription state and billing event. A reviewer should be able to see whether service continued because the customer chose to keep it or because the merchant failed to honor cancellation.

Use an offsetting credit when one exists

If the merchant already refunded the disputed renewal, link the credit to the charge. Include amount, transaction reference, and date. If the refund was partial, state the service period or adjustment it covered.

Avoid manually refunding an open chargeback without checking the processor workflow. The objective is to show the issuer what financial resolution already occurred, not create a second payout.

C28 prevention is a product-design issue

Cancellation should produce a durable event with channel, timestamp, effective date, and confirmation. Billing should consume that event reliably. Support agents should not need a private spreadsheet to tell finance which accounts must stop renewing.

Review C28 cases for attempted-cancellation channels that failed: email, chat, web account, app store, or phone. A pattern often reveals a broken journey long before it becomes visible in broad churn metrics.

Use cancellation analytics to reduce future cases. Measure how often a cancellation request arrives within seven days before or after renewal, how long support takes to apply it, whether customers receive confirmation, and whether the billing engine receives the new state before the next run. Those operational measures can reveal a recurring-system problem long before it appears as a large group of C28 disputes.

Example: Amex C28 where cancellation was effective at period end

A member cancels on August 10 and the merchant's terms say access remains active through August 31 with no September renewal. If the system bills September anyway, the cancellation timeline exposes the error. If the disputed charge instead covers the already-started August period and the customer continued using the service, the evidence question is different.

The merchant should show enrollment terms, cancellation request, effective date, billing events, access termination, and refund status. One generic 'subscription canceled' label cannot explain which billing period was valid.

Reconstruct recurring billing as a dated contract-and-access timeline

An Amex C28 file should begin with the original enrollment: plan, price, billing cadence, renewal terms, and the method by which the Cardmember could cancel. Preserve the version of those terms that applied at signup rather than a screenshot of today's checkout. Then add every material lifecycle event—plan change, pause, renewal, cancellation request, confirmation, access end, and refund. The objective is to determine whether the disputed recurring charge occurred before or after cancellation became effective under the actual transaction record.

Cancellation requests can arrive through several channels, and that matters operationally. Search self-service events, support tickets, email, phone notes, payment-provider cancellation objects, and account settings. A merchant should not claim 'no cancellation was found' merely because the billing system has no event if support accepted the request elsewhere. Conversely, an account that currently shows canceled does not prove the customer canceled before the challenged renewal. The date and source of the first effective request are what make the timeline useful.

Treat continued use as supporting context, not a substitute for billing authorization. If the customer canceled after a valid renewal and continued using the service during the already-paid period, usage can help explain the merchant's position. If the customer canceled before the renewal and the system billed anyway, post-charge usage does not automatically cure the billing error. Keep access, billing, and cancellation as separate tracks and reconcile them at the point of the disputed charge.

C28 prevention belongs in product and support design. Cancellation confirmations should state the effective date and whether access continues through a paid term. Billing systems should consume the same cancellation state that support communicates. Refund promises should be reconciled against settled credits. Track disputes where the business cannot locate the cancellation request, where cancellation did not propagate, or where the customer misunderstood period-end cancellation. Each category needs a different fix.

Audit cancellation confirmations for the effective date the customer was actually shown

Recurring businesses should retain the exact cancellation confirmation presented to the member, including whether cancellation was immediate or scheduled for period end. Internal billing fields can be technically correct while customer-facing language is ambiguous. If support said 'canceled today' but billing meant 'will not renew next month,' the mismatch itself can create C28 disputes. Compare the confirmation, actual billing state, and next charge. Prevention requires language and system behavior to agree, not merely a correct backend flag.

Recurring-billing cancellations often turn on the gap between the customer's request and the merchant's effective cancellation state. Preserve the request timestamp, channel, confirmation message, billing-cycle boundary, and any later account activity. If the merchant allowed service through the end of a paid term, make that distinction visible so the reviewer can see whether the disputed renewal occurred before or after the cancellation took effect. Also check whether a second subscription, add-on, or legacy billing profile remained active after the main plan was cancelled. A customer can reasonably believe “the subscription” was cancelled while the merchant's system continues a separate recurring charge. Auditing those parallel entitlements prevents the response from defending a technically active billing object that the support interaction had led the customer to believe was closed.