#samwiser_invoice-attemptcount
last badgerBOT
👋 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/1238271846491885710
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
silent swan
samwiser_invoice-attemptcount
👋 @visual osprey you don't need to change your code. This was a bug on our end and we fixed it yesterday so you shouldn't see it moving forward
visual osprey
So it should increment on those failures ?
silent swan
yes it will, it was just a bug we had and it took us a while to narrow it down unfortunately
visual osprey
oh man 😐
silent swan
It is important to know though that some of those retries won't do anything since we can't retry those cards. So you likely want to look at the original decline attempt and act accordingly son that if you get stolen_card for example you nudge your customer to come back and change their card
visual osprey
Yeah ok, where is it best to grab that key and off which hook ?
is there a common sense list of which decline keys it should send that email on ?
silent swan
We don't have a list yet though we're working on public docs. I'm sorry I know that's not the answer you want to hear right now.
Do you have an example Invoice I can look at so I can flag internally?
visual osprey
Hmm, I have this guy pi_3P8bfHGZAJzYwAuy19E9x7Z2
silent swan
I asked the team and they shared this list for now 'pickup_card','incorrect_number', 'lost_card', 'stolen_card', 'invalid_pin','revocation_of_authorization','revocation_of_all_authorization', 'do_not_honor', 'transaction_not_allowed', 'invalid_account', 'expired_card','stop_payment'
visual osprey
cool, thanks, which key and on which webhook for this ?
silent swan
last_payment_error[decline_code] on the PaymentIntent
visual osprey
ok ta,
Also, do you post anywhere about these bug-fixes. I get that bugs happen, but just so I don't loose another night up debugging something out of my control, do you post these bugfixes anywhere ?
Like https://twitter.com/StripeDev etc ?
silent swan
Not for bugs like this. We do try to reach out to affected users. This one has been really subtle sadly and we're still working on it 😦
I know because I found it yesterday and have been pushing on this internally all day yesterday and today.
It's a tricky balance between spamming about a lot of small inconsequential things and making sure to flag important things.
I think a lot of people didn't expect attempt_count to be so crucial for integrations at first until I got involved since I help developers here and I know this well
Sorry for the waste of time, I totally get it and we want to improve with this
chrome siloBOT
visual osprey
all good man, thanks for the intel and following up it. It defo caught us off-guard.
When I couldn't find a clear answer about when the attrempt_count did and didn't increment in the docs, I ended up using the old claude, and it doubled down on mis-information.
silent swan
yeah don't get me started on AI trying to answer questions about our APIs 😅
I have to run but I'm glad you were able to get to me so I could explain!
visual osprey
thanks for your help