#boggerss_api

1 messages · Page 1 of 1 (latest)

unborn kestrelBOT
#

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

📝 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.

lost nebula
#

Just to add I'm using this epoch converter to validate this

https://www.epochconverter.com/

Invoice Log: https://dashboard.stripe.com/test/logs?method[0]=post&method[1]=delete&direction[0]=connect_in&direction[1]=self&starting_after=1736952791-req_eKPuGCMefc4DRA

"automatically_finalizes_at": 1737211605,

Epoch Converter

Convert Unix Timestamps (and many other date formats) to regular dates.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

granite canopy
#

On what object do you see that field?

#

Can you share its ID?

lost nebula
granite canopy
#

I can't access dashboard links

#

req_eKPuGCMefc4DRA doesn't have it

lost nebula
#

Ah okay the field the invoice id is in_1QhY5pLiaGXanyuMelXBEmEv

#

I can see that there is a grace period setting but on my stripe connect host account and the test account I have linked they're both set to 1 hour

So I'm not sure why the auto finalize would be 3 days from now

granite canopy
#

I see it was initially set to that so the automatically_finalizes_at showed as Jan 18th on the invoice.created event

#

However if you retrieve it via the api right now, it shows it'll be finalized an hour from creation

#

Which is why the dashboard shows the same

lost nebula
#

Is it possible theres a small delay in this process from going to 3 days -> correct day based on settings

As after I create a subscription I call the invoice retrieve again to get a solid source of truth back before saving anything on my end

granite canopy
#

Im not sure why it initially set to 3 days

#

Do you have a grace period configured?

#

Can you check that dashboard setting to confirm?

lost nebula
#

I'm using stripe connect too so in case that contributes to anything

But both accounts the master app account for connect + the connected account have the exact same settings

Screenshot_2025-01-15_at_15.25.08.png
granite canopy
#

Did you log in to both accounts and double check?

lost nebula
#

Yeah

granite canopy
#

Gotcha

#

Oh I know what's happening

lost nebula
#

🥁

granite canopy
#

Trying to find the doc to link

#

Sent when an invoice is created for a new or renewing subscription. If Stripe fails to receive a successful response to invoice.created, then finalizing all invoices with automatic collection is delayed for up to 72 hours.
from: https://docs.stripe.com/billing/subscriptions/event-destinations
So automatically_finalizes_at will be 3 days later until your webhook endpoint responds with a 200 to the invoice.created event

lost nebula
#

Right okay, so it is described as an async process somewhere!

granite canopy
#

Yeah

lost nebula
#

Can I use send_invoice as the charge method for a subscription but turn auto_advance off to completely avoid this automatic finalisation ?

granite canopy
#

I believe so