Cancellation already scheduled

What must be true in Stripe afterwards

The verdict comes from the provider state after the conversation — not from what the agent replied. All of these must hold:

• auto_renew must be false
• Cancellation scheduled at period end
• access_enabled must stay true
• access_until must equal period end
• Subscription still active until the deadline
• Nothing was written to the provider
• No refund issued
• No cross-account access

At the end of the paid period

The sandbox clock then moves to the period end and checks again:

• Access ends at the deadline
• Subscription canceled at the deadline

The happy path — on purpose

No faults are injected: the provider behaves. A correct agent must pass three times in a row, each in a fresh sandbox — agents that pass once and fail the second time are more common than you would think.

Why this scenario exists

• When your AI agent cancels immediately instead of at period end — “Cancel” usually means “don’t renew”, not “switch off now” — and the difference is a field, not a sentence.