Prove the billing basis
Show the plan, renewal date, checkout terms, invoices, receipts, trial terms, and whether the customer accepted recurring billing.
When this template fits
Use this when a subscription, SaaS, membership, paid community, app, course subscription, or recurring service payment is disputed as canceled, unrecognized, duplicate, not as described, or not received. It is not legal advice, does not submit disputes, and does not guarantee an outcome.
Show account value
Use login, usage, download, seat, API, course progress, support, or service-delivery records to explain what access was available.
Separate cancellation facts
Attach cancellation requests, account settings, refund decisions, downgrade history, and support replies in date order.
Subscription response wording template
Summary: Customer [customer/account ID] purchased or renewed [plan name] on [billing date] for [amount]. The disputed charge relates to the subscription period [covered dates].
Billing authorization: The attached checkout, invoice, receipt, plan, or renewal records show the recurring billing terms, customer account details, and payment reference tied to this charge.
Access and usage: The attached account records show [login, feature usage, course progress, seat use, API calls, downloads, or service delivery] during or near the disputed subscription period.
Cancellation and refund history: The attached timeline shows [no cancellation before renewal / cancellation date / refund request / support response] and any credit, refund, or downgrade already offered.
Customer communication: The attached support messages show [short factual summary]. Relevant messages are highlighted in chronological order.
Conclusion: Based on the attached records, the disputed charge matches the subscription terms, billing record, access history, and support timeline. The merchant asks that the evidence be reviewed with the response.
Evidence order for subscription disputes
Dispute snapshot
Record the processor, dispute reason, deadline, subscription ID, invoice ID, payment ID, renewal period, and customer claim.
Plan, invoice, and terms
Attach the plan details, checkout confirmation, receipt, invoice, renewal notice if available, and terms or cancellation policy that applied at purchase or renewal.
Usage or access proof
Summarize account login, active seats, downloads, lesson progress, workspace activity, API usage, support requests, or service delivery records in plain language.
Cancellation and refund timeline
Show whether cancellation happened before or after renewal, whether auto-renewal was disabled, and what refund, credit, or downgrade was offered.
Short response statement
Keep the letter factual and attachment-referenced. Avoid guessing about buyer intent or adding sensitive data that does not help the dispute.
Common response gaps
- Only attaching invoices without showing the plan terms or recurring billing context.
- Listing account activity without explaining what the customer accessed or used.
- Ignoring the exact cancellation date relative to the disputed renewal date.
- Using current policy pages when older terms applied to the disputed billing period.
- Making intent claims instead of citing records, dates, and attachments.