#nihilist_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1220697379309621281
๐ 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.
- nihilist_best-practices, 3 days ago, 16 messages
hi! in general if an off_session attempt on the PaymentIntent fails, the PaymentMethod is removed yes and the status goes back to requires_payment_method. Not sure if that's what you're referring to?
ah ok so what would you recommend to make this situation easier for user when they failed 3ds. I don't want my user to re-enter the card information again if it's a recurring subscription payment but failed because 3ds
are you handling the retry on your own payment page that you contact the user and bring them to?
yes i'm trying to handling that on my own payment page.
cool. Then on that page you can set it up so that you get the pm_xxx that you want to charge(for example from the last_payment_error on the PaymentIntent) and then pass it to https://docs.stripe.com/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-existing when the user clicks a "retry payment" button, no need to re-collect the details
ah ok make sense tks for your help
but my payment intent with the id above doesn't have last_payment_error can you check if there's any issue
yeah it gets cleared if there are more attempts on the PI, and that one has had a bunch of activity
ultimately you can know the pm_xxx to use in multiple ways, it's the default_payment_method on the related Subscription, for instance.
so is there any doc listing what attribute of paymentintent got reset
when there is an update
Depends what you mean by 'reset'?
sorry i mean cleared, so far i do notice that 2 setup_future_usage and payment_method got cleared when payment failed
Nothing specific on that really no
No fields other than payment_method should reset which my colleague explained. Just the status field which will transition to reflect the failure
ok i see so will an invoice.payment_failed webhook event got triggered if i failed 3ds challenge for a payment
Yes
ok so how do you distinguised between invoice.payment_failed webhook of a 3ds failed and a renewal payment failed
assuming the test card i use for renewal payment failed is 4000000000000341
To be clear renewal payments can fail because 3DS was requested too โ that's not a problem limited to the initial invoice payment. But to get the reason for the failure you'd expand the payment_intent field and look at the last_payment_error hash
Ok do you have a doc the list of errors code in last_payment_error hash
We have: https://docs.stripe.com/error-codes and https://docs.stripe.com/declines/codes more specifically for declines