#SC0909-backdated-futuredated-subscriptions
golden lynx
Subscriptions created via the API.
novel rapids
Do you have a request ID for the Subscription update API call?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Also, can you describe how you have this set up? Specifically, listing chronologically each API call you make to the Subscription in order for this to work?
golden lynx
https://dashboard.stripe.com/test/logs/req_is3DOl9uqjWEul
Only making 1 call to create the subscription with a backdated start date and billing anchor.
novel rapids
At first glance I think the difference has to do with GMT and your local timezone. What timezone are you in when you're logged into the Dashboard?
golden lynx
Its set to PST
novel rapids
the unix timestamps used in your request are for July 27th, but your Dashboard will automatically sync times to whatever your local time is
golden lynx
So the gray dates shown in the invoice on the dashboard are "only" for the dashboard and don't affect the invoice itself?
If we updated our account timezone to GMT, then the gray dates would match?
novel rapids
I believe so. The results in the API will always take precedence over the Dashboard, so if you're worried about the dates being correct, always look at the API responses before the Dashboard