#bojan_api
unique canyonBOT
đ 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/1268406321741562047
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
upper marlinBOT
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.
- bojan_api, 3 hours ago, 22 messages
subtle python
Hi, could you share the request you created the Subscription Schedule?
Which time does each phase have?
modern rose
evt_1PipN2KGiMOAr4gsFWi2RnYw
The first phase stats on Aug 19th and ends on Sept 2nd, but the first invoice if for Aug19 -> Sept 18
I'd like the first invoice to be Aug 19 -> Sept 2 (end of phase 1)
subtle python
Can you also set the billing_cycle_anchor on phase 1 to phase_start?
Btw here is the request you created it https://dashboard.stripe.com/test/logs/req_wMR7vphuEZ0Q0E. It's req_xxx. What you shared is a webhook event evt_xxx
modern rose
created a new one; it's still the same behavior
subtle python
Hmm I think the Upcoming Invoice display could be incorrect. Can you use the Test Clock API and try to advance the time?
modern rose
The other alternative is to start the subscription via cron job when the time comes (ie. Aug 19th in our case) and use ordinary subscriptions instead of subscription schedule. However, I just did it, and it didn't respect the billing_cycle_anchor_config property. This one resets on 8/1, instead of 8/2. Am I using the API wrong?
Let me check that - I thought that only subscriptions created through the dashboard could be advanced with the test clock API
Do you have instructions on how to do that handy by any chance?
modern rose
The other alternative is to start the subscription via cron job when the time co...
actually never mind - it's a off-by-one error. I need to day_of_month: 3 if i want the invoice to end on Sept 2nd
subtle python
Okie but keep in mind that these time is UTC. If you think of your timzone time you could see discrepancies
modern rose
Good callout - will probably add the hours as well
btw, i don't see the siumlation banner on the subscription schedule page. I do see one on the normal subscription page
subtle python
Yeah they are 2 different objects
modern rose
i think i'll go with an ordinary subscription - thanks for your help
unless you are certain tha that's just an UI bug and that it'll actually do the correct proration
subtle python
I think it just doesn't take the phase configuration into account. If you use Test clock and advance past Sep 2 (ie. Sep 3), I would expect to see an Invoice there
unique canyonBOT
modern rose
I didn't use the test clock but did create a subscription that started just now instead of Aug 19
https://dashboard.stripe.com/test/subscriptions/sub_1Piq8YKGiMOAr4gsMUkfA1vA (req: https://dashboard.stripe.com/test/logs/req_MY6fB3Oh49xikK)
What hapened is that the customer got charged the full-month price (ie. $150). The proration kicks in on the second invoice, when phase 2 starts (the invoice preview has the "unused time" refund + full month line items)
thanks for the help - unless there are some flags to force the first invoice to be prorated & charge only for it's phase, this is not the behavior i'm looking for