#timmmy-subscriptions

1 messages · Page 1 of 1 (latest)

vapid radish
#

timmmy-subscriptions

#

@steep basalt easiest way would be to get access to the Test Clocks beta(https://stripe.com/docs/billing/testing/test_clocks)

beyond that, it's probably easiest to directly cancel the Subscription via the API with and use that to test with, it generates the same overall events/flows as if using cancel_at_period_end

steep basalt
#

Alright so once a user cancels his subscription

#

the CustomerSubscriptionDeleted event would trigger on the 12th of Februrary right?

vapid radish
#

hmm, not sure I follow but I don't think so

#

what you have there is a subscription object currently with cancel_at_period_end:true. What will happens is at the end of the period(Feb 12) a customer.subscription.deleted event will be fired (maybe this is what you mean actually)

#

but you can't force that to happen right now without fastforwarding time with that beta API

so instead, you can call the cancel API directly https://stripe.com/docs/api/subscriptions/cancel , which sends the customer.subscription.deleted event right now

steep basalt
#

anyway thanks for your help

#

Am I doing something wrong or is delete not an operation anymore?

#

Apparently cancel is Delete