#saahil_api

1 messages ¡ Page 1 of 1 (latest)

serene phoenixBOT
#

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

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

still blaze
#

Hello! Can you please share the Invoice ID?

glacial fjord
#

in_1TEGgKHqwjPOXnIWbAfYvpTb

still blaze
#

Sorry for the delay! I see that payment was attempted at 2026-03-23 23:11:36 so it's strange that attempt_count is 0 as this should include the initial attempt and then any automatic retries. Let me keep digging...

glacial fjord
#

Thank you!

unique sierra
#

Hey, we want to join the agnetic selling via stripe, we are a charity and was given this dev thread by stripe, can anyone help us please?

still blaze
unique sierra
#

thank you Jazz

still blaze
#

I agree attempt_count should be non-zero if attempted is true. I'm thinking this might be because the 3DS step started but didn't finish so we haven't actually received whether the payment was accepted or declined. However, it's something I'll flag internally.

#

Are you able to share more about your use case for reading these values at this point in your flow?

glacial fjord
#

Yeah I was thinking the same thing.

#

Yeah my use case in particular is that when a users subscription is in past due I want to expose information to the user via a UI that lets them know how many payments have been attempted and when their subscription will cancel if they do not pay. Right now I'm using payment attempts as a proxy for how much time has passed since the invoice was initially due. I can use a timestamp based field which I am leaning towards doing such as current_period_end or created.

still blaze
#

Thanks for sharing! I agree it's better to use a timestamp for this. Are you hoping to use attempt_count to show how many payments have been attempted? Or are you computing this some other way?

glacial fjord
#

I'm currently doing

daysUntilCancellation = 2 grace period days - attemptCount + 1

still blaze
#

I see, so you're less interested in showing how many payments have been attempted and more interested in showing how long they have until cancellation, right?

glacial fjord
#

Yeah

#

I re-tooled to use:

daysUntilCancellation = 2 grace period days - time since invoice.created

still blaze
#

Makes sense, glad you found an alternative solution! If you'd like us to keep you updated with potential improvements that result from this, we can create a support ticket.