| Information |
Why it matters |
| Subscriber email |
Identifies the subscription |
| Publication name |
Identifies the paid subscription |
| Creator name |
Helps route publisher requests |
| Payment date |
Determines 7-day refund timing |
| Charge amount |
Matches the payment |
| Receipt |
Supports refund review |
| Cancellation date |
Supports charged-after-cancel complaints |
| Refund request date |
Determines policy handling |
| Subscriber perk status |
Can affect 7-day refund handling |
| Apple receipt |
Supports iOS in-app purchases |
| Support ticket |
Keeps escalation focused |
| Privacy request |
Separates data issues from billing |
For refund complaints, lead with publication, payment date, refund request date, receipt, and whether any perk was claimed.
Reader Cancellation and Refund Complaints
Substack says readers can cancel a paid subscription from account settings, under Subscriptions, by selecting the paid publication. A reader may also manage the subscription from the publication's manage subscription page. Paid subscriber benefits continue until the end of the paid period.
Use this table:
| Reader issue |
Complaint focus |
| Cannot cancel |
Subscriber email, publication, error |
| Charged after cancellation |
Cancellation date and receipt |
| 7-day refund request |
Payment date, request date, perk status |
| Dormant publication |
Publication activity and receipt |
| Duplicate charge |
Two receipts and timestamps |
| Wrong account charged |
Subscriber emails and receipt |
Ask Substack or the publisher to confirm the subscription status, cancellation date, and refund policy applied.
Publisher Refund and Subscriber Management Complaints
Substack says publishers can cancel a subscriber and issue a prorated or full refund for the most recent subscription transaction from the Subscribers dashboard. Substack also warns publishers to issue refunds through the Substack Subscribers dashboard rather than through Stripe, because platform fees can be affected.
Use this table:
| Publisher issue |
What to include |
| Subscriber refund request |
Subscriber email and transaction |
| Cannot find refund option |
Subscriber status and dashboard |
| Prorated refund question |
Transaction and subscription period |
| Full refund question |
Transaction and reason |
| Stripe fee issue |
Substack dashboard and Stripe record |
| Subscriber dispute |
Payment, evidence, Stripe notice |
Ask Substack to confirm whether the refund should be handled by publisher dashboard, Substack support, Apple, or Stripe dispute process.
iOS In-App Purchase and Payment Channel Complaints
Substack supports iOS in-app payment options for eligible publications. In-app purchase complaints may involve Apple receipts, app-store billing, subscriber visibility, publisher payout timing, or a payment route different from the web/Stripe flow.
Use this table:
| Payment channel issue |
Evidence |
| Apple-billed subscription |
Apple receipt and publication |
| Web subscription |
Substack receipt and subscriber email |
| Publisher cannot see payment |
Subscriber email and receipt |
| Duplicate web and app charge |
Both receipts and timestamps |
| Payout timing issue |
Publisher dashboard and payment month |
| App cancellation issue |
Purchase channel and device |
Ask support to identify the purchase channel before requesting a refund or cancellation decision.
Account Access and Privacy Complaints
Account access problems can block cancellation and refund requests. Privacy requests should be separated from ordinary subscription support.
Use this table:
| Issue |
What to include |
| Cannot log in |
Subscriber email, device, error |
| Subscription not visible |
Publication, receipt, account email |
| Email change problem |
Old and current email |
| Publisher account access |
Publication, admin email, error |
| Data access request |
Account email and request type |
| Deletion request |
Account and records to preserve first |
Save receipts, publisher messages, and support replies before deleting an account.
When to Escalate Beyond Substack
| Situation |
Escalation path |
Notes |
| Publisher-controlled refund |
Publisher first, then Substack support |
Include publication and receipt |
| Apple in-app purchase |
Apple Support |
Include Apple receipt |
| Stripe dispute notice |
Stripe records and Substack support |
Publisher should preserve evidence |
| Card charge review |
Payment issuer |
Preserve Substack records first |
| Privacy request unresolved |
Substack privacy route or applicable authority |
Include dates and responses |
| Publisher payout issue |
Substack publisher support |
Include dashboard and payout record |
Escalation is strongest when the publication, subscriber email, payment date, request date, and purchase channel are clear.
What to Say in a Substack Complaint
Use this script:
"I need Substack to review a complaint for subscriber email [email] and publication [publication name]. The issue is [paid subscription cancellation, refund request, creator-issued refund, 7-day refund policy issue, dormant publication, iOS in-app purchase, duplicate charge, account access, publisher payout, privacy request, or support delay]. The relevant details are [creator name, payment date, amount, receipt, purchase channel, cancellation date, refund request date, perk status, publication activity, Apple receipt, payout record, support ticket, or privacy request]. I am requesting [cancellation confirmation, refund review, publisher routing, dormant publication review, duplicate charge review, iOS purchase routing, account access help, payout review, privacy response, or written policy explanation]. Please confirm the decision and next step in writing."
Let Pine AI Help File the Complaint