cho_subscription-schedules-billingcycles

[velvet obsidian]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1222225991544344686

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[spice cloak]

Between the three, which would help me identify things such as "next payment date" ? I'm leaning toward the subscription ID (not the schedule), but I'd like insight from a dev

[queen siren]

I would recommend the Subscription ID. However, you can also use the Subscription Schedule ID (the Schedule has at current_phase property useful for payment dates) and make sure to expand the Subscription object when retrieving the Schedule from the API.

That would give you plenty of data to make decisions with.

Here's a document on how to use expand: https://docs.stripe.com/expand

[spice cloak]

oh I see, qq my sub schedule is very simple its:
1 month discounted
every month thereafter set price

so after 1 month, my schedule will swap to the second phase indefinitely.

In this case should I get the subscription schedule if I plan to access accurate subscription data 1 month down the line?

I guess I'm asking, do the different phases have different ID's when they happen

for instance, will expand return a different subscription ID after the first phase completes?

[queen siren]

No the sub will always have the same ID. The schedule is just used to "schedule" updates to the same subscrption