Coaching Seller Chargeback Response: the Pack for Each Allegation

This guide is for the seller side of a course or coaching chargeback — the opposite side of the consumer dispute. A student or coachee has gone to their bank, and the bank has sent you a reason code. Your job is not to send everything you have. It is to send the records that answer that allegation, in an order a reviewer can follow. Build your pack with the Coaching Seller Representment Builder, then use this guide to understand why each exhibit is in it.

Start with the notice, not with your files

Read three things off the notice before opening a single export: the reason code, the cardholder’s own words, and the deadline on the notice itself. The code tells you the allegation family; the cardholder’s words tell you the specific claim inside it — and on Mastercard, the sub-condition under code 4853 matters more than the number, because 4853 is a catch-all covering not-provided, not-as-described, cancelled-recurring, and credit-not-processed claims, each needing different evidence. The deadline on your notice governs your case: this guide deliberately gives no deadline in days, because network maximums and processor deadlines differ and published figures for the same code conflict.

The chain that replaces a tracking number

For a physical sale, delivery is a scan. For a course or coaching sale, delivery is a chain with three links, and a pack missing any link reads as a gap: payment → entitlement → usage. The receipt links the disputed payment to a buyer account. The provisioning record shows that account was granted the course, the coaching tier, or the membership — with a timestamp and a welcome or access email. The usage records show that account then used it: logins, lessons completed, downloads, call attendance, homework submitted, feedback received. Stripe’s dispute-evidence fields follow the same shape: access_activity_log for the dated activity, service_documentation for proof the service was provided, receipt for the payment, and customer_communication for the message thread. Two honest limits apply to this chain, and the builder states both: a receipt records a sale, not fulfilment; and an access log shows an account was used, not who sat at the keyboard.

Not delivered (Visa 13.1): prove the door was opened and walked through

The claim is that the buyer never received the course or the sessions. The pack: provisioning record, dated access log or session attendance for this buyer account, and the support thread if one exists. If the buyer reported an access problem and you fixed it, include both the complaint and the fix — a problem solved on the record is stronger than a problem hidden. If there is no access log and no attendance at all, stop before fighting: check for a failed-access record, a bounced welcome email, or an unanswered support ticket. A buyer who genuinely could not get in is a refund case, not a representment case, and submitting a pack with no delivery proof in it says so anyway.

Not as described (Visa 13.3): promise next to delivered, line by line

The claim is that what arrived differs from what was sold. The pack therefore has two columns, and both must be dated to the purchase: the sales page and offer exactly as the buyer saw them, and the curriculum and deliverables actually provided — module by module, session by session, with recordings, slides, and written feedback as artefacts. Do not substitute the current sales page for the purchase-time one: terms and offers change, and a reviewer comparing a new page against an old complaint will notice. Do not claim a module that was not delivered. If the support thread shows a complaint you answered with re-delivery, an extra session, or a partial remedy, include it; a complaint answered on the record beats a complaint ignored, and a complaint you never answered is the weakest version of this pack.

Cancelled recurring (Visa 13.2): the timeline is the whole case

The claim is that a recurring charge was processed after cancellation. The deciding exhibit is the cancellation log set against the charge date — every request with its date, or a dated export showing no request before the charge. Around it: the signup-time recurring terms (billing interval, renewal rule, how to cancel), the renewal notice sent before the disputed charge, the billing timeline of charges, pauses, and credits, and any usage dated after the claimed cancellation date. Usage before that date proves nothing about the claim; usage after it answers it directly. And the refund-first rule applies here in full: if a cancellation was received before the charge and no refund was issued, issue the refund or credit first. Disputing a charge your own log says you should not have taken will not survive the log.

Credit not processed (Visa 13.6): the ledger decides

The claim is that a promised refund or credit never arrived. The pack is short and unforgiving: the refund ledger for this exact payment — refund ID, date, amount, destination — or a dated statement that no refund was issued, with the purchase-time refund policy showing whether the buyer’s situation fell inside or outside it. Never submit a refund record belonging to a different payment. If a refund was promised and not kept, that is a refund-first case, not a representment case.

The signed-agreement warning

Coaching sellers reach for the signed agreement first, because it feels like the strongest document in the drawer. It is the weakest delivery evidence you can lead with. An agreement proves terms were accepted; it proves nothing about whether sessions happened, lessons were watched, or access was granted. Square’s own service-evidence list makes the same distinction from the other direction: alongside contracts and terms, it asks for proof of service completion with date and customer signature, appointment confirmation, and messages showing resolution attempts. Treat the agreement as context in every pack — present, but never standing alone.

PayPal’s intangible-goods limits, stated plainly

PayPal Seller Protection for intangible goods and services is narrower than most course sellers expect. Under PayPal’s program (last updated January 26, 2026), an intangible sale qualifies only for Unauthorized Transaction claims, only when PayPal marked the transaction eligible, and only with compelling proof of delivery — a record the item was sent electronically to, or received or accessed by, the buyer. Significantly Not as Described claims are not covered at all, and Item Not Received claims that the buyer files as a card-issuer chargeback are not eligible for Seller Protection. A card chargeback on a coaching sale still needs a representment pack through the chargeback route; Seller Protection eligibility is a separate question, and this builder never lets one stand in for the other.

Fraud claims are out of scope — deliberately

If the notice says the buyer did not authorize the charge (Visa 10.4, Mastercard 4837), this builder routes you out instead of building a delivery pack, because a delivery pack does not answer an authorization claim. That case needs identity and authentication evidence — authentication results and account and device history — assessed under its own rules, including Visa’s Compelling Evidence framework where it applies. Sending attendance logs at a fraud claim wastes the one submission you get.

Before you submit: the final-review checklist

Run this list in order, and do not submit until every line is true: the code and allegation on your notice match the pack you built; every exhibit belongs to this buyer and this payment; the purchase-time versions of the sales page and terms are used, not the current ones; the complaint itself appears in the support excerpt, not edited out; the gap you could not fill is named in the “what is not included” section; and the deadline on your own notice — not any number in a guide — is the date you are working to. On Stripe, a submitted dispute response is final and cannot be supplemented, so this review is the last chance to catch a wrong-payment exhibit or a missing log. No pack promises an outcome: the issuing bank decides, on the code and the records.

Related seller tools and guides

For physical-goods evidence, use the Shopify Chargeback Evidence Checker; for Square’s dashboard flow, the Square Dispute Response Builder and the Square dispute response guide; for PayPal’s claim types, the PayPal Seller Dispute Response Builder. For the reason code itself, the Reason Code Decoder. This guide is the coaching-specific companion: it shares no copy with any consumer page, and the consumer side of a course dispute is a different reader with different rights.

Sources (verified November 2, 2026): Visa codes 13.1 / 13.2 / 13.3 / 13.6 — Merchant Fraud Journal, “How to Write a Chargeback Rebuttal Letter” (code-to-evidence rebuttal table) and Sift, “Visa Chargeback Reason Codes”; Mastercard 4853 catch-all and sub-conditions, retired 4855 folded into 4853 — Chargeback Clock’s Mastercard reason-code guide and Chargeflow, “Mastercard Chargeback Reason Codes” (October 2026); Stripe dispute-evidence fields access_activity_log, service_documentation, receipt, customer_communication, cancellation_policy — Stripe DisputeEvidence object reference, and Chargeflow, “Stripe Digital Goods Dispute Evidence” and “What Evidence Do I Need to Win a Stripe Chargeback” (both October 12, 2026); PayPal Seller Protection Program (last updated January 26, 2026, paypal.com) for the intangible-goods limits; Square Support article 7891 service-evidence list (April 23, 2026), as recorded in Chargeback Clock’s Square dispute guide (October 31, 2026). Your processor notice and account agreement govern your case.

← Back to homepage · For Business — merchant tools & guides · Back to the builder