#Bruna Pinto
azure chasm
deft depot
Hello! When you say it has a "cancellation schedule" what are you referring to exactly?
deft depot
Gotcha. Instead of using a Subscription Schedule you should probably use cancel_at_period_end on the Subscription itself: https://stripe.com/docs/api/subscriptions/update#update_subscription-cancel_at_period_end
The renewal notifications don't know about the Subscription Schedule, but they should know about those properties on the Subscription itself.
gleaming thunder
Yes, but I am using this
cancel_at
"they" you mean who? the client?
What about the customer portal? Show know that this plan has a subscription schedule, right?
SHould*
knotty imp
Checking in to this. I believe we are talking about the renewal notifications here but am less familiar with them
Unfortunately the customer portal is not aware of schedules as far as I know. It can manipulate cencel_at so I will have to double check if it can display info about that as well
knotty imp
So for the renewal notification, cancel_at will actually prevent these notifications if the renewal would be after the cancel_at date, but as far as I can see that doesn't work for schedules.
The server is too busy for me to test the customer portal bit myself right now. Would you be able to set this on a test mode subscription and report back if that changes any customer portal UI?
gleaming thunder
This is an example of how is it shown to the client
There is a cancel_at in the subscription
But still the client has received the renewal notification by email
knotty imp
Can you send me the ID of that subscription (sub_123)?
gleaming thunder
sub_1M2DMDBU70BIUlFgCD6T0QTC
knotty imp
It actually looks like that subscription's current period end is 1676550377 wheras the cancel_at date is 1676559600 which is a bit after