#sergio-snchez_unexpected
main voidBOT
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.
- sergio-snchez_api, 2 days ago, 14 messages
worn zealotBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255874187520770138
đ Have more to share? Add details, code, screenshots, videos, etc. below.
cunning siren
Hello
rapid herald
Hello bismarck
cunning siren
Taking a look
Is your customer in your payment flow at this time?
Or are you attempting to charge at a later time here
After previously saving the payment method
rapid herald
We create a setup intent, them the customer provide the payment method we associated to that setup intent... and almost immediatelly (because the process allow it for some specific cases) wecreate a payment intent and confirm it to charge it
but considering your question I guess that the charge is a later time here
because we do in a backend process
cunning siren
How long is "almost immediately" for these situations?
Because ideally you don't do SetupIntent --> PaymentIntent
Since this can result in your customer having to complete 3DS twice
Which is a bad UX
rapid herald
the setup intent is confirm at 12:25:15
cunning siren
I more am asking whether it is possible to just charge the customer on payment method collection in this flow?
rapid herald
and the payment intent we try to confirm at 12:25:45
cunning siren
Okay and it is necessary to wait that 30 seconds in the flow as opposed to refactoring to do this in one step?
rapid herald
the issue is that to check if we can do it instant or we need to wait until approval is a process we need to check in our backend services
so for that info by default we want to execute the setup intent in a way that later we can charge with the custome off-session
is it something we miss in the setup-intent call?
cunning siren
No you didn't do anything wrong, the issuer just requested 3DS on the setup and the payment which can happen.
That's why it is better to do this in one step.
However if you want to leave your integration as-is, then when the PaymentIntent moves into requires_action you pass the client secret to your frontend and call confirmCardPayment() (https://docs.stripe.com/js/payment_intents/confirm_card_payment) to handle 3DS here
cunning siren
Yep
rapid herald
ok understood
cunning siren
That's why I would switch to doing a flow like: https://docs.stripe.com/payments/build-a-two-step-confirmation
rapid herald
ok thanks for the context