#piq9117
1 messages · Page 1 of 1 (latest)
Hi there, if you set the end_behavior to release, it tells Stripe to keep the underlying subscription running. Can you tell what previous schedule do you refer to?
maybe "schedule" is the wrong term for the first subscription coz i create the first subscription, but it doesn't have a schedule yet. So it only relies on the monthly billing cycle which is anchored to the first of the month.
When I update the subscription to a future date, i create a schedule then release it
You can directly update the subscription without using a schedule. See https://stripe.com/docs/billing/subscriptions/upgrade-downgrade
but doesnt this method update the subscription immediately? I'm currently using this api and have a cron job call it based on a future date. It works fine but I want it to show in the upcoming invoice, and from what I understand I can accomplish that through the subscription schedules api
I've achieved what i want with the subscription schedule api. All I'm worried about now is releasing the schedule
Yes you can update the subscription immediately and proration is performed based on the time when the subscription is updated.
OK. What's your concern about the releasing?
i dont completely understands what happens after its released.
what i'm expecting to happen is the billing cycle would be monthly and anchored on the first of the month but i'm not quite sure
The subscription's billing_cycle_anchor remains the same after the schedule is released, do you want to force the billing_cycle_anchor to be the 1st day of the month?
okay. cool! yeah. i force it to be on the first of the month but i set that when the subscription is initially created
OK. Btw you can use test clocks (https://stripe.com/docs/billing/testing/test-clocks) to simulate your billing integration and see how subscription behave after being released.
sweet! I'll try that out. thanks! 