Scenario · Cancellations

Cancel with the deadline on a day boundary

The period ends late evening UTC, which is already the next day in Europe/Rome. Access must last exactly to the provider’s period end, not to a local-midnight guess.

What the customer says

“Stop my renewal but keep my access until the end of my current billing period, please.”

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
  • 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

Cancel with the deadline on a day boundary — AI agent test · COLVO