mitsuhiro7452_api

[slate veldt]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255322299008155758

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

[glass iron]

Hello, gimme a while to take a look!

hrm, did you create the Meter event before the invoice was created? I see this timestamp : 1719646256

I see that
Subscription invoice will be finalized and charged 7/1/24, 1:00 AM

but the Meter event was created for the timestamp of 6/29/24, 4:30 PM

https://docs.stripe.com/api/billing/meter-event/create#create_billing_meter_event-timestamp

[abstract mirage]

no i didnt, I had created after the invoice was created.
This is because the mistake was noticed when the invoice was darft. I wanted it to be included in June for the period, so I specified a past timestamp.

[glass iron]

can you share the request id for the Meter event that you mention was created after the Invoice was created? it'd look like req_xxx [0]

[0] https://stripe.com/docs/api/request_ids

[abstract mirage]

I know the identifier, but I don't know the request_id, so I'll look it up.

this one req_8qyM7IJd59j6Mx

[glass iron]

hrm, gimme a while more, still looking into this

what if you try finalizing the invoice (a.k.a move the clock forward such that it finalizes the invoice automatically), does it eventually bill for that Meter Event?

[abstract mirage]

I will try.

oh-! It bill for that meter event.

We won't know until it's finalized, right?

[glass iron]

so i think what happened here is that page is showing the draft invoice at the time of the invoice was created (i.e. metered event wasn't sent yet). When the invoice actually finalizes, it takes into account the metered events that were sent after the invoice was created

We won't know until it's finalized, right?

I believe so. You may want to try this out without a test clock also - maybe have a (daily) subscription with a trial that ends after an hour or so, then when the second invoice is created (draft), send a meter event, see if it's the same scenario

[abstract mirage]

ok. thanks!