#eoghanobrien_api
sick mapleBOT
👋 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/1338605402207551711
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fleet bloom
Hello
Taking a look
fleet bloom
Based on the request IDs you've shared, it looks like these payments were blocked due to wrong CVC based on your radar rule settings.
These weren't retried by Stripe but the customer retried and confirmed these payments themselves via your application. So these were processed synchronously.
wheat flower
Got it, is there anything you would suggest we could do here? The customer didn't realize they successfully purchased and purchased again.
fleet bloom
One option would be to poll the API to check PaymentIntent status manually to retrieve it's status. If it has the status succeeded then the payment went through.
The other option would be to listen to webhook events - https://docs.stripe.com/webhooks
Stripe sends webhook events for actions on your account. So once the payment has succeeded - we'd send payment_intent.succeeded event to your server which then you can use to fulfill the order.
wheat flower
So if I initiate a PaymentIntent, the Stripe SDK will keep attempting to update that PaymentIntent for a given session, it doesn't create a new paymentIntent if the card number/cvc/expiry etc are invalid. So you think, in this case, the user kept submitting until they got the card info correct, so they should have known the payment succeeded?
fleet bloom
So if I initiate a PaymentIntent, the Stripe SDK will keep attempting to update that PaymentIntent for a given session, it doesn't create a new paymentIntent if the card number/cvc/expiry etc are invalid.
PaymentIntent creation is dependent on how you handle declines on your end. Stripe allows multiple confirmation attempts on PaymentIntents, yes and we don't create PaymentIntents automatically in case of declines.
Edit to add more context: Unless you update the client-side clientSecret manually - when the customer attempts to confirm a PaymentIntent - the SDK will use the existing clientSecret / the same PaymentIntent.
So you think, in this case, the user kept submitting until they got the card info correct, so they should have known the payment succeeded?
Correct. The confirmation happened synchronously so the customer would've seen the confirmation of payment succeeding (assuming everything in your app logic functioned correctly)
wheat flower
great, it sounds like we're at least not missing functionality on our end, we could add additional checks perhaps
fleet bloom
Yup 👍
sick mapleBOT
wheat flower
awesome, thanks for the assist!