#Bruna Pinto

1 messages ยท Page 1 of 1 (latest)

frigid plumeBOT
cinder canyon
#

๐Ÿ‘‹ happy to help

#

could you please share on example of subscription id of each case?

craggy obsidian
#

This is the customer portal

#

this is the stripe's dashboard

#

sub_1LlApGCmcyIwF9rccenzZLKJ

#

This is the id of an example that we scheduled the cancellation using our code: sub_1LlAg7CmcyIwF9rc0akHEfpc

#

Is this the id that you need?

cinder canyon
#

let me check them

craggy obsidian
#

Ok!

cinder canyon
#

I'm trying to compare the two

#

it's a bit hard to find this needle in the haystack

craggy obsidian
#

Is there something else that we can help you out?

#

Or something that we can do or test it?

cinder canyon
#

I'm not sure to be honest, it might be a bug from ourside

#

I will try to investigate this more in depth

#

Are those 2 subscriptions handled by a schedule?

#

or just the last one you shared?

#

ok so I checked this for you, it seems that this subscription sub_1LlAg7CmcyIwF9rc0akHEfpc is a schedule while the other one is not on a schedule which explains why they behave differently in the Customer Portal

#

when you specify a schedule the customer is not able to change it in the Customer Portal

#

whereas when you set a cancel_date for a subscription the customer is entitled to change the subscription cancel date to a different date

craggy obsidian
#

Exactly. It seems to us to be a bug on the Stripe side when this cancellation is done through your dashboard.

#

This schedule is very important to us and that the Customer Portal understands this cancellation when it is done through the Stripe dashboard. Is there any prevision for this to be resolved or something we can do to work around this problem?

light juniper
#

Hi there ๐Ÿ‘‹ apologies for the delay, I'm jumping in and will be back to take a closer look in a moment.

craggy obsidian
#

ok! thanks

light juniper
#

Thank you for your patience.

#

Pulling up those objects now and taking a closer look.

light juniper
#

I'm going to try replicating this in my account.

craggy obsidian
#

Right

light juniper
#

Alright, I think I see what is happening.

As my teammate mentioned, the Subscription that you scheduled to cancel via code is controlled by a Subscription Schedule, so your customers are not allowed to make adjustments to it.

For the other Subscription, your customers are still able to see the cancel button, because your Customer Portal configuration is set up to allow customers to set Subscriptions to cancel at the end of their current period. The Subscription that you showed is scheduled to be canceled beyond the end of the current billing period, so your customers are still presented with the option to cancel the Subscription at the end of the current period and this is expected.

If you would like to fully remove the ability for customers to cancel Subscriptions, then you can update the default portal configuration here:
https://dashboard.stripe.com/test/settings/billing/portal