#liam-curran_docs
proud stumpBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- liam-curran_api, 3 days ago, 19 messages
misty gladeBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252548176355786843
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
wicked drum
Any examples of what you've tried and what isn't work as you need?
oblique pebble
So I was just mainly confused around how the timestamp approach works when a month doesn't have e.g. 31 days
I understand the config object and that seems perfect
but for example, say we were trying to set the billing cycle to be the 31st of each month, and if the month has 28 days be the last day of the month instead, is that possible with the timestamps or does it have to use the billing_cycle_anchor_config object instead?
wicked drum
If you want to bill on the last day of the month, then yes use billing_cycle_anchor_config. Not sure I understand the API version part? It's backwards compatible
oblique pebble
So we're currently on a quite outdated version (2020 for most things)
So we would need to update everywhere and then pass in the stripe config object to manually set our old version
wicked drum
Why would you? That parameter isn't dependent on a new API version – should work on any version
oblique pebble
oh really?
sorry maybe I'm a bit confused - I checked the releases and that billing_cycle_anchor_config came in earlier this year, we can just pass that param and it'll work?
even if our stripe version is older?
wicked drum
Yep, should do. It's an additive parameter and (most) of those are backwards compatible. Only breaking changes require a new version: https://docs.stripe.com/upgrades
oblique pebble
oh amazing 🚀 I'll have a look at that then
wicked drum
You may need to update your SDK versions if heavily typed though and that's where it might get tricky
