danf-sh_unexpected | Stripe Developers | Page 1

edgy juncoBOT Apr 4, 2025, 5:35 PM

#

👋 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/1357770445989875923

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

#

errant agate Apr 4, 2025, 5:35 PM

#

Hi, can you share the invoice id where you see this?

clear ocean Apr 4, 2025, 5:36 PM

#

I just want to confirm is the invoice id okay to share in discord given that this is public?

errant agate Apr 4, 2025, 5:38 PM

#

Yes, as long as you don't share PII data, it is safe to share invoices IDs here. However, if you don't feel comfortable with that, you can contact our support team to help you look into this: https://support.stripe.com/contact

clear ocean Apr 4, 2025, 5:39 PM

#

Alright, I don't think I need to share any PII. Here is the invoice id: in_1Qz5PLCmY3oKb1vJUsqlDNbn

#

The description says: Feb 4 - Mar 4, 2025

#

But the period start/end timestamps are:
start: 2025-02-05 00:00:00
end: 2025-03-05 00:00:00

#

Coming from the api

#

I think the end being Mar 4 is fine but the start being Feb 4 is wrong

#

These times are in utc btw

#

Looking closer at the api output. Seems to match to the line_item period start/end, why would that be different from the overall period start/end?

errant agate Apr 4, 2025, 5:50 PM

#

Still looking. You would have expected to see 'Feb 5 - Mar 4, 2025'?

clear ocean Apr 4, 2025, 5:51 PM

#

That is what I would expect

#

You can also see from our usage reporting we only reported usage for Feb 5 - Mar 4

errant agate Apr 4, 2025, 6:04 PM

#

There were multiple subscription update requests but I do not see them being the culprit after looking at all of them. Is this happening only on this invoice? Are you able to reproduce this on your end? Can you share exact steps for me to try to reproduce it?

clear ocean Apr 4, 2025, 6:10 PM

#

I'm not able to repro, I'm going to try to do some experimenting with the test clocks today to see if I can repro. We have seen this with other invoices as well

errant agate Apr 4, 2025, 6:24 PM

#

I tested this but I can't replicate what you see here. Looking at the previous invoices on this subscription

clear ocean Apr 4, 2025, 6:27 PM

#

Alright, sounds good

errant agate Apr 4, 2025, 6:28 PM

#

Wait, you added the price on 2023-12-04 and all the invoices for that price is always in_1PYzdiCmY3oKb1vJgqQ51DzC billed from 4th - 4th.

#

Still trying to replicate it

clear ocean Apr 4, 2025, 6:30 PM

#

When users sign up we create the subscription but move the billing anchor date to the next closest utc midnight because our systems expect the anchor dates to be at utc midnight

errant agate Apr 4, 2025, 6:33 PM

#

Yeah, since that subscription creation is is from 2023, it's hard to understand how to even reproduce this fully. I can see that the subscription was created at 2023-12-04 at 17:06:11 and not at midnight

clear ocean Apr 4, 2025, 6:34 PM

#

Yeah that makes sense given how our systems operate but I wouldn't expect that to cause this particular issue

errant agate Apr 4, 2025, 6:36 PM

#

Can you try a test scenario by passing a billing cycle anchor when creating the subscription? I think that is the issue.

clear ocean Apr 4, 2025, 6:38 PM

#

Yeah so this is what we do. When we create the subscription we provide the billing anchor timestamp which is the next closest utc midnight

#

Would using the billing anchor config make any difference here?

errant agate Apr 4, 2025, 6:44 PM

#

Yes, it would

clear ocean Apr 4, 2025, 6:46 PM

#

Can you explain why that would be the case? What would the difference between setting the billing anchor timestamp to Jan 10 12:00am and billing anchor config to day of month 10, hour 0, min 0, sec 0

#

I would expect those to be equivalent

edgy juncoBOT Apr 4, 2025, 6:49 PM

#

errant agate Apr 4, 2025, 6:54 PM

#

We document this here: https://support.stripe.com/questions/subscription-charge-date

clear ocean Apr 4, 2025, 6:56 PM

#

But that relates the issue to timezone issues, all our time stamps are in utc which you can see from the api output

#

When we set the billing anchor timestamp its at utc midnight

#

If you're not able to get to the bottom of it, that's okay, I can just try to do some experimenting on my side to see if I can repro. If updating to billing anchor config fixes the issue that would be great, but I don't really understand why that should be the case

errant agate Apr 4, 2025, 7:07 PM

#

yeah, you still have not share exact steps to reproduce this so I'm still not able to test fully

#

The only way I can reproduce this issue is when I backdate the subscription and report usage

#

I'm using Test Clocks, and creating the subscription from Apr 4 2025, and backdating it to Apr 2. My subsequent invoice start from the 5th so it looks like it's just how it works

#danf-sh_unexpected