Marisa, from I Already Said No, has four screens. Each records a different event. Together they give her good reason to doubt that she has left.
The first acknowledges her cancellation request. The second marks her support ticket resolved. The third shows a free plan. The fourth shows a later attempt to collect a renewal payment (whether the attempt succeeds is a separate matter, and a less interesting one).
The confirmation concerns receipt. A closed ticket concerns a support workflow. The free-plan label concerns access or account classification. The payment attempt concerns collection. Somebody needs to reconcile these records against the effective cancellation date, and reading one screen back to her will not do it.
What each screen establishes
An acknowledgment establishes that the request reached the channel that issued it. Somewhere behind it, a scheduled job or an integration is meant to carry the request to billing. The receipt says nothing about whether it did.
A closed ticket establishes a state in the support tool. An agent may have forwarded the request while lacking authority to change the renewal setting. Closing the conversation can fit the agent’s assigned task perfectly and still leave the customer’s instruction unexecuted. The institution has to define what closure means and make the unfinished operation visible.
A free-plan label establishes what the product displays. Where product access and billing are managed separately, their states can diverge, and the label cannot settle whether a paid renewal remains scheduled. Billing should produce its own cancellation record, with the effective end date and any final amount due.
The collection attempt establishes that a payment was attempted. Its purpose and timing still matter. A final charge for an existing obligation differs from a new renewal after cancellation. Stripe’s cancellation documentation shows the distinction in practice: ending a subscription can leave final invoice items to settle, and pausing collection is a separate operation from ending the subscription.
The reconciliation job
Marisa compares the records and writes again. Support replies that the account shows a free plan. She asks about the renewal attempt. The reply answers a different question, with admirable manners.
The customer becomes the integration layer between systems the institution runs or commissions. Her attention supplies the monitoring. Without reconciliation inside the service, an active renewal can proceed despite a request recorded elsewhere. The billing process may be following its own state correctly while the institution fails the customer.
This architecture can come from a broken handoff. It can also preserve revenue by making departure tiresome. The screens do not establish motive. They establish a discrepancy, and the duty to investigate it belongs to the institution. Handed back to the person trying to leave, it becomes her part-time job.
The enforcement record
The FTC’s May 2026 complaint against Shutterstock alleges cancellation routes that required further correspondence or an email link authorizing an early cancellation fee. It describes links with a three-day response window and emails that referred to a payment-portal link without supplying it.
The case is pending, with a proposed stipulated order on file, so these remain allegations. They make the second task concrete: after asking to leave, the customer must complete another condition somewhere else.
An exit can be easy to locate and still leave the renewal active. What matters is what the route commits the institution to do, and whether the customer can tell what remains unfinished.
Joined clocks
The service should count valid cancellation instructions against the renewal-state changes they require, by effective date. A support ticket about cancellation should stay visibly linked to that operation until it completes or reaches an identified exception. A free-plan account with a paid renewal scheduled deserves a look; sometimes another valid paid service on the account explains it.
The completion message should come from the operative record and identify the canceled subscription. It should give the effective end date and any final charge. Payment authorization may need separate treatment under the arrangement in use. A bank block can prevent collection while leaving the vendor’s subscription very much alive.
Marisa should receive enough evidence to challenge a later inconsistent charge without assembling the institution’s architecture from screenshots. The discrepancy belongs to the service that created it.
Received is a status. Running is a status. Someone has to answer for the space between them.
Companions
- The cancellation frame: I Already Said No.
- Reversibility before action: Before the Commit.
Bibliography
Federal Trade Commission, Complaint for Permanent Injunction, Monetary Judgment, and Other Relief: Shutterstock, Inc. (13 May 2026), complaint.
Federal Trade Commission, “Shutterstock, Inc.” (case record, accessed 9 October 2026), legal library.
Stripe, “Cancel Subscriptions” (accessed 9 October 2026), documentation.
These notes come out of Sociable Systems, a practice that reads AI-shaped documents the way a hostile reviewer will, before a lender or a court finds the gap. The argument has an operational form: the Interim Protocol sets out four rules for AI use in environmental and social deliverables, covering disclosure at touch-point grain, evidence custody, the phrases no automated screening may settle, and a hostile read before anything ships. Free, and written to be cited or retired once institutional guidance arrives.