#harry_api
atomic remnantBOT
👋 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/1293567826300370954
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- harry_api, 4 hours ago, 16 messages
low mulch
Hello
Give me a moment to take a look
low mulch
I'm here, things are just running busy.. Please be patient
wheat slate
sure
low mulch
When you created the subscription, you passed a backdate_start_date which is an hour earlier than billing cycle anchor (when you created the subscription)
https://dashboard.stripe.com/logs/req_cvK9ooLN53MXTj
So $0.04 is the prorated amount for that duration
wheat slate
Based on America/Chicago Backdate start date is Tuesday October 08, 2024 00:00:00 (am) and billing cycle anchor is Friday November 08, 2024 00:00:00 (am)
https://www.epochconverter.com/timezones?q=1728363600&tz=America%2FChicago
https://www.epochconverter.com/timezones?q=1728363600&tz=America%2FChicago
the timezone set on our platform for the connected account is America/Chicago based on which the backdate_start_date and billing_cycle_anchor was sent
low mulch
The request I sent above shows your code sent
billing_cycle_anchor: "1731045600"
yes i checked that please refer to above links to see the same
Billing cycle anchor https://www.epochconverter.com/timezones?q=1731045600&tz=America%2FChicago
Backdate start date https://www.epochconverter.com/timezones?q=1728363600&tz=America%2FChicago
low mulch
Our APIs use UTC
wheat slate
So I have a requirement where my clients want the recurring charges to happen at 12:00 am based on there timezone that's the reason I sent these timestamps
Can you help me with that
low mulch
You'd need to pass in the correct UTC time that matches with midnight time in that timezone.. i.e. 1731045600 for backdate and anchor
low mulch
sorry what I meant was both timestamps need to match.. Otherwise they'll generate prorations.
wheat slate
so both billing_cycle_anchor and backdate_start_date need to be 1731045600 this?
but isn't billing_cycle_anchor meant to be a future date? as in when next charge should happen?
low mulch
The invoice you've shared is the first invoice of a subscription.. That finalizes immediately.
low mulch
👍