#staleriver_webhooks
spice mantleBOT
👋 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/1400628534606565407
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
humble hemlock
HI
remote patio
Apologies I copied the wrong event. It's this one evt_1RqjIfIeqdRa1lgK9ugwSaOY.
humble hemlock
D
spice mantleBOT
@humble hemlock looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
humble hemlock
Hello,
I recently made a purchase but was not aware that identity verification was required.
Is it possible for me to complete the verification and activate the gift card tomorrow morning?
Thank you for your understanding and support.
Hello,
I recently made a purchase but was not aware that identity verification was required.
Is it possible for me to complete the verification and activate the gift card tomorrow morning?
Thank you for your understanding and support.
spice mantleBOT
@humble hemlock looks like you're in the wrong place, this thread is for someone else's question.
- If you have your own thread please chat there.
- If you have a question or a followup to a closed thread use one of the buttons in https://discord.com/channels/841573134531821608/842637025524842496 to get help (we don't reopen closed threads).
Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.
lament rapids
next_payment_attempt is available in invoice.updated event: https://dashboard.stripe.com/acct_14W9T2IeqdRa1lgK/workbench/events/evt_1RqjK9IeqdRa1lgKjLAivMGo
spice mantleBOT
remote patio
hmm why isn't it available in the invoice.payment_failed event?
karmic elk
Hi @remote patio I'm taking over this thread
remote patio
Hi thank you
We've always listened to the invoice.payment_failed event and we have our integration built under the assumption that next_payment_attempt will be null only when there's no more payment attempts remaining. But I'm starting to see cases where it's null even though there's more attempts remaining.
Trying to figure out if it's some oversight on my end or if there's been a regression / bug
karmic elk
OK, let me take a look at it. Is this evt_1RqjIfIeqdRa1lgK9ugwSaOY the invoice of concern?
remote patio
Yes. Thank you!
karmic elk
Thanks for waiting.
The initial card payment was declined due to transaction_not_allowed , and that's why there won't be retries for this invoice, and therefore next_payment_attempt is null
remote patio
I was just reading about that and was suspecting that might be the case. So that's a hard decline code?
karmic elk
Yes you are right
remote patio
By any chance, did Stripe recently become more "strict" in determining whether or not a transaction becomes a hard decline? I'm going through all the past_due subscriptins and still haven't found one where there wasn't a hard decline which I'm pretty surprised about.
Or did the behavior change recently such that next_payment_attempt becomes null when it's a hard decline?
fwiw I also experienced the same thing when testing with 4000 0000 0000 0341 which I don't think ever happened to me in the past
karmic elk
Do you have the ID of a past invoice that exhibited different behavior?
remote patio
That would be difficult to find unfortunately. I just happened to stumble on this just today and haven't touched this part of our code in a long time.
But I'll try to dig through some older subscriptions
I do think the behavior is a little inconsistent though. invoice.payment_failed shows next_payment_attempt as null but if you look up the invoice itself it does have next_payment_attempt
invoice.updated which fired almost immediatley after also has next_payment_attempt populated https://dashboard.stripe.com/events/evt_1RqjK9IeqdRa1lgKjLAivMGo.
karmic elk
Hmm, let me dig deeper
karmic elk
I can confirm that this invoice won't be retried but I don't know why next_payment_attempt was populated in the invoice.updated event. Can I suggest you to write in to support and we will continue the discussion through emails?
spice mantleBOT
Hello @remote patio, we have sent you a direct message, please check it at https://discord.com/channels/@me/1362224554889449482
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.