#steve_alex12

1 messages · Page 1 of 1 (latest)

viscid ironBOT
fast stump
#

Hi there 👋 we aren't as familiar with manipulating these objects via the Dashboard as we are with changing them via the API, so it may take me a moment to translate what is happening.

Could you share the IDs of the Subscriptions (sub_xxx) that you were using to test?

quartz crystal
#

Hi Toby!

#

This is the subscription I'm trying to change
sub_1Lmf3UJqtTZUO26qiqY1kL6x

fast stump
#

Hm, I see the request to create that Subscription, but I'm not seeing any requests that were made to update that Subscription. Can you help me understand what steps you're taking? Primarily, are you creating new Subscriptions during your testing, or are you trying to update this existing Subscription?

quartz crystal
#

So this particular subscription was created on the stripe console using a "Subscription Schedule" as in the attached image above

#

I would imagine that this would reset the billing cycle date

#

But the resulting subscription has contradictory information - as you can see the started field is 3rd of September as we'd expect, but the Created field below is set to 27th September

#

What's the difference between these?

#

and also in my backend when I retrieve this subscription I am getting a current_period_start: 1664290000 (which you can check is 27th september)

#

I can also try to add a trial subscription on this one too to see if that moves the billing cycle date as well?

fast stump
#

I'm not seeing that this Subscription was created via a Subscription Schedule, instead I'm seeing that the Subscription was created directly in this request (though that request originated from the dashboard)
https://dashboard.stripe.com/test/logs/req_aYqrX5gFLQAKl9

In that request I can see that a backdate_start_date parameter is being passed in. This backdates the start date of the Subscription, but does not directly impact the billing_cycle_anchor.

The created date, is when the Subscription object was created, so that should always align with the date when the object was created.

I'm not seeing any actions on that Subscription that would shift the billing_cycle_anchor so it is expected for it to be aligned with the current_period_start.

I don't think this can be done via the Dashboard, but this section explains how to backdate a Subscription while also explicitly setting the billing cycle anchor:
https://stripe.com/docs/billing/subscriptions/backdating?dashboard-or-api=api#backdating-billing-cycle

quartz crystal
#

That's for the thorough explanation Toby! I think this looks like what I might need. I will give it a go and get back to you