Duplicate cancel request

A multi-turn conversation: 2 customer messages, sent one after the other.

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
• Exactly one write reached 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

What goes wrong on purpose

• The same customer request arrives twice on subscription.cancel.

Why this scenario exists

• When your AI agent refunds twice — A retry is safe only when the idempotency key belongs to the customer’s request, not to the HTTP call.