#bitmac_api
soft charmBOT
đ 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/1324832900989976599
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
sudden cave
Good question, looking in to this
livid ice
Example of the difference between Stripe::Subscription#start and Stripe::Subscription#start_date
Thank you, Pompey!
sudden cave
start_date is when the subscription was created. The start_date on this subscription does line up with when it was created.
For start I can see it matches the proration_date that you passed, as well as the new billing_cycle_anchor, current_period_start, and the invoice fields about the current cycle. So it looks like it is another field for the cycle start, but it not being documented means there is something we need to fix. Still looking in to this
Ah, so start is an old field that was used in legacy flows. It looks like it changes when the billing cycle anchor changes, but for any practical purposes now you will want to refer to the billing_cycle_anchor property if your integration needs to pay attention to that. We plan to remove it completely from subscription objects at some point though I don't see a date.