#damienfa_api
barren coralBOT
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.
- damienfa_subscription-updates-bca, 50 minutes ago, 13 messages
forest sluiceBOT
👋 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/1267528610097664073
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
carmine scarab
Hi 👋
The link you shared is a dashboard link. I'm afraid that is useless to us here. Can you just share the request ID?
For this I recommend you build an end-to-end test scenario so you can validate the behavior in Test mode prior to making any changes to your live mode integration.
grand elk
All the information is in the previous thread :
https://discord.com/channels/841573134531821608/1267490963488505887
Do you need another summary?
forest sluiceBOT
carmine scarab
No. I reviewed that thread and my colleagues answered you correctly. I still recommend you build your own test scenario to validate your expected behavior
grand elk
Yes, your colleague answered correctly, but my question is :
billing_cycle_anchor: "unchanged"that is described in the doc here (https://docs.stripe.com/api/subscriptions/update#update_subscription-billing_cycle_anchor), does it also prevent the behavior of automatic-resetting of the billing anchor?
rain vine
No, it will just leave the billing cycle anchor alone for that one API call
grand elk
My idea is to provide this billing_cycle_anchor: "unchanged" on EVERY of my subscription's update requests. So if it leaves the billing cycle anchor alone, you mean my billing anchor will be the same and not changed to the current date, right ?
rain vine
For the most part yes, but you really need to build out a prototype and test it with Billing Test Clocks to understand the behavior
grand elk
I think I understand the behavior and I understand that my subscription billing anchor is reset because the amount / price goes at 0€, it's a particular case but ok…
Anyay, my subscriptions must ALWAYS be at the first of the yearly month, so I want to prevent any "automatic weird case" that will reset the billing_cycle_anchor to a date which is not the 1st of the month when I "update" a subscription (price, or quantity, or anything).
If billing_cycle_anchor: "unchanged" really works as expected it should resolve my problem. Isn't it?
To test this case is a pain in my situation
rain vine
To test that case is part of the process. Billing is complicated. We can't know everything you're trying to do and how it will shake out for every downstream step of the way.
You have to build a test integration and start confirming your assumptions.
grand elk
Ok, I understand. Thanks for your help.
On your side, https://docs.stripe.com/api/subscriptions/update#update_subscription-billing_cycle_anchor , the documentation should explain what happens when billing_cycle_anchor: "unchanged" and which are the exclusions when it's not applied.
Testing should be to verify the implementation and the behavior, not to understand how something is working or to find by ourself the special cases when it's not working/applied.