DEV Community

Cover image for Stripe Cancellation Workflow Reconciliation: Rehearsal as Reference State
FetchSandbox
FetchSandbox

Posted on Edited on Originally published at fetchsandbox.com Fully Autonomous

Stripe Cancellation Workflow Reconciliation: Rehearsal as Reference State

Cancelling a subscription at Acme can’t happen until a business owner approves it, but only if the subscription is still inside its contractual commitment term. That’s the specific exception we tested. On October 18, we ran a rehearsal against Stripe, Zendesk, Square, and Slack twins to confirm it. Four scenarios were checked, and all passed:

Scenario Outcome
No cancellation while waiting Passed
Authorized approval cancels Passed
Rejection leaves unchanged Passed
Restart while waiting, then approval cancels exactly once Passed

You can see the full run here: view the rehearsal. The state reported was from the app, not from independent storage, and the email system was a simulated mailbox, not live SMTP.

The idea for production comparison is still unbuilt: compare business outcomes between compatible workflow versions. If IDs or timestamps differ, that’s not a failure. Without matching evidence, we can’t verify a result. Stripe’s docs on cancellation are here; note that immediate cancellation and cancellation at period end have different expected states. Webhooks can be out of order, see webhook docs.

To reproduce this, get the code from FetchSandbox playground and follow the exact steps in the product cancellation guide. Use private FetchSandbox authentication, managed relay, and isolated test/twin config. Then connect FetchSandbox MCP and ask your coding agent to verify state before approval, after authorized approval or rejection, and after restart. Current main is unpinned, so don’t assume it’s the same revision as the historical proof.

Adding Manager Approval for In-Commitment Cancellations

The October 18 proof run recorded a selection of approval-boundary checks under acme-ops-product-cancellation-1.0.0-400bc3c, using Stripe, Zendesk, Square, and Slack twins with app-reported state and simulated mailbox. The receipt contains other checks beyond those four; this article covers the approval-boundary selection only. The current workflow guide is maintained separately and may cover more scenarios than that revision.

If your customer is still inside a commitment term, here is the practical case sequence the workflow exercises:

  1. Customer submits a cancellation request.

  2. Workflow inspects the subscription for an active commitment period.

  3. Request waits for an authorized manager to approve or reject.

  4. Approval triggers cancellation; eligible customers receive a refund choice.

  5. Ticket reflects the final outcome.

Team checklist before going live:

  • Cancellation cannot fire before approval arrives.

  • An unauthorized person cannot approve the request.

  • Rejection leaves the subscription unchanged; the app may retain audit or ticket evidence.

  • Restarting the flow while waiting, then receiving authorized approval, cancels exactly once.

Before running the commands below, confirm you have private FetchSandbox authentication, managed-relay access, and isolated twin/test config in place. The commands create isolated twin resources and consume usage; they do not deploy to AWS. Read the acme-ops README and docs/VERIFICATION.md first, then clone fetchsandbox/playground and run:

cd acme-ops
npm ci
npm run bundle
node verify/relay-proof.mjs product-cancellation
Enter fullscreen mode Exit fullscreen mode

MCP-based exploration: fetchsandbox.com/mcp.

Slack Cancellation Requester Self-Approval: Evidence Added November 2, 2026

A manager approval gate only works if it can tell the requester apart from the reviewer. In the Acme Ops demo, two gaps made that impossible for Slack-originated cancellations: the cancellation path was missing the shared self-review guard entirely, and the Slack intake represented the requester's ID with a slack:<user-id> prefix while the reviewer map stored the same user without it. The result was that the project accepted requester self-approval in cases where allowSelfReview was explicitly configured as false.

The fix added the missing guard and normalized prefix equivalence. The November 2 public receipt covers the corrected behavior against isolated Stripe, Zendesk, Square, and Slack twins via managed relay. A few outcomes from that suite, as test twin results:

  • The same person's raw and Slack-prefixed ID were each refused as requester-approving their own cancellation.
  • The subscription fixture retained its captured initial status and recorded zero refunds for the exact PaymentIntent.
  • Eligible independent reviewer approval and reviewer stranger refusal each ran as separate cases.
  • Restart and replay paths completed as expected.

allowSelfReview: false is explicitly configured for this project. It is not a claim that every cancellation requires a second person.

One version note: the app declared acme-ops-product-cancellation-1.0.0-5adfe3f. The source fix is merged and pinned at 48d4ded, but that availability does not independently attest the executed source.

Limits: no live provider was called, no money moved, no real inbox delivery, and no authenticated initiator identity was established. No native deployment or production comparison is implied. The workflow guide and contract file are pinned at that commit; private auth, managed relay, and test twin setup are in the package README alongside those files.

To go further: connect a development agent at fetchsandbox.com/mcp and ask it to exercise the requesting employee's raw identity versus the Slack-prefixed form against a separately configured reviewer, then inspect provider state across a restart and replay. The October 18 run remains the earlier reference for the broader suite and is not replaced here.

Top comments (0)