Marisa’s renewal setting has not moved. She used the cancellation route in I Already Said No and received an acknowledgment. In the same month her provider sent a notice ending a support tier, and that change went live on schedule.
Suppose the contract permits both acts: the supplier may end support on notice, and the customer may stop renewal at the end of a billing period. Each party exercises an authority the terms grant. The provider wired its own notice to an operation. Her instruction waits for a handoff. The difference lives in the machinery assigned to each authorized act.
A supplier’s words can also fail to propagate (a contract cannot make an integration work). The asymmetry arises when the institution builds a dependable route for its own changes and leaves the customer responsible for chasing hers.
Contract and permissions
The applicable terms and law determine whether an instruction is valid and when its effect is due. A supplier cannot acquire unlimited authority by sending an email. A customer’s silence cannot be assumed to accept every proposed change. In this example, each party already holds a specified right, and each instruction has a defined effect.
Workflow permissions determine who can carry that effect into the system. Say the provider’s change team can schedule the service ending, while support can read account information and add notes. Support’s lack of billing access can be a sensible control. The institution still needs a route from a valid cancellation to someone authorized to change the renewal state.
Who Is Allowed to Undo follows authority across organizational boundaries. Outsourcing execution adds a boundary to manage. If a billing provider holds the relevant setting, the service must send the instruction through the interface available to it, then reconcile the result. The customer should not need to discover which firm owns the switch.
Endings and objections
A customer with a right to end renewal can exercise it. The effective date may fall at the end of a paid period or after a valid notice requirement. A refund for an earlier charge remains a separate question. The institution’s task is to establish the applicable effect and execute it when due, without reopening her preference as a sales conversation.
Withdrawal of payment authorization addresses collection. Cancellation addresses the subscription. India’s RBI e-mandate framework gives one specific example of online mandate withdrawal with issuer authentication, including an exception for a transaction already in the notification pipeline. That payment control leaves the underlying service contract to its own terms. Other arrangements need their own rules.
An objection to a determination asks for review. Where a review right applies, the defined effect is a decision by someone authorized to weigh the evidence, with a deadline and reasons. The objection may justify an interim hold under the governing procedure. It carries no automatic veto over the outcome.
Treating cancellation as an open-ended appeal makes the customer defend a decision she has authority to make. Treating every objection as an instruction to reverse an outcome grants an authority the procedure may never confer. The four fields from I Already Said No apply to both, with different content in the defined-effect field.
Identity and authority
Authentication establishes who is speaking. Authority concerns what that person can do to this account. A user may be logged in to a shared workspace without permission to close the organization’s subscription. The institution must check the relevant authority; a login does not settle it.
If a check remains incomplete, the interface should say so and show how to complete it. Contested authority needs a named owner and a decision date. An unresolved check dressed up as a successful cancellation will eventually introduce itself to the customer as a new bill.
Once authority and the effective date are established, a separate refund dispute should not obstruct the renewal change. The uncertainty has a scope. Left attached to the whole account, it has room to become indefinite.
The ledger of authority
An institution can list each message that changes what it does to a customer, identify who may send it and record the required effect. It can then inspect the route from receipt to execution. A supplier’s notice and a customer’s cancellation each need an accountable owner, even if different teams do the work.
The test is whether an authorized instruction arrives at the relevant operation by its deadline, with evidence available to the person who gave it. A procedural check earns its place by answering a real question about authority or terms. Another retention offer answers a question the customer has already settled.
The contract grants the right. The receiving institution has to give that right a working route.
Companions
- Authority across organizational boundaries: Who Is Allowed to Undo.
- Who can start an action: Attribution at the Moment of Action.
Bibliography
Reserve Bank of India, “Processing of e-mandate on cards for recurring transactions” (21 August 2019), paragraphs 15–17, notification.
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.