#shroomlife - Invoices
pseudo sonnet
Thank you
pseudo estuary
That Subscription's billing cycle anchor date was changed by the Subscription Schedule you created in this request: https://dashboard.stripe.com/logs/req_VoOG6377hnuTfK
pseudo sonnet
The request you sent was used to create the subscription. The start date is Mon Sep 20 2021 00:00:00 GMT+0200 (Central European Summer Time) but still the invoice coming on 19th. Why?
When I create a subscription on 20th of any month. I would like to have that billed on the 20th of the month. This is causing my client problems.
There are more like this. This subscription is just an example of many.
pseudo estuary
The request is to create a Subscription Schedule, not a Subscription. You specified a start_date in that request on the 19th.
pseudo sonnet
in UTC.
My client added a start date of 20th. The 19th is coming from your system.
It's simply wrong.
There seems to be a bug with timezones. I know that feeling.
pseudo estuary
The start date you specified is Sun, 19 Sep 2021 22:00:00 UTC. Is that your intended start date or no?
pseudo sonnet
My customer has his dashboard in his timezone as you are probably aware of. He wanted to create a subscription to start at the 20th of september. He selects it. Your system is translating the time from his dashboard 20th 00:00 to UTC 19th 22:00. That is working until timezone switches in Germany at 30th october. Then the difference between UTC and Germany is 1 hour and no longer 2 hours. But that is something your system should be aware of. My client cannot setup a schedule for 6 months in that timezone and then another 6 months in the other...
pseudo estuary
Our system does not handle timezones at all. The API only accepts timestamps, which are timezone independent.
You specified a start_date of 1632088800 for this Subscription Schedule. That's Sun, 19 Sep 2021 22:00:00 UTC.
If that's incorrect you need to make adjustments to your code to provide the correct timestamp.
pseudo sonnet
So what should my customer do then in the future? Set the start to 02:00 to be sure?
pseudo estuary
No, this is something you need to handle on your end. Your code needs to do whatever is required to produce the desired timestamp to the Stripe API.
pseudo sonnet
Can you tell me what the start date of https://dashboard.stripe.com/test/subscription_schedules/sub_sched_1KUbYLAIBz8zc47oCIzcCCWV is?
I used Stripe Dashboard to create it on 20th... So who is handling timezone here? You save it as UTC... I never entered a UTC timestamp or anything.
pseudo estuary
Have a look at the creation request here: https://dashboard.stripe.com/test/logs/req_FH77oowsOKtZKD
Looks like it was set to 1645311600.
pseudo sonnet
Yes but I used you Dashboard?!
I didn't use any code for my example.
Are you aware of the special timezone conditions of Germany?
pseudo estuary
When using the Dashboard the times you see are defined by the time zone you have configured here: https://dashboard.stripe.com/settings/account
Is that setting what you expect?
pseudo sonnet
Yes.
When I set the 20th in your Dashboard. Your system should save it the way that it is always executed on the 20th. I think that is what the Dashboard is selling to be able to.
pseudo estuary
That's what it is doing. It's setting it to the 20th in the timezone you have configured in your Dashboard.
pseudo sonnet
Yes. But if I would do that in your Dashboard on a 20th before 30th of october. There would be a problem after october 30th as I mentioned in the example of my first message.
pseudo estuary
Not sure I understand, can you provide more details?
pseudo sonnet
Need to go now. I will ask some on else another time. I highly assume there is a bug cause of the special edge case of timezones in Germany. Bye thank you.