#Maxime - PI and SI
1 messages · Page 1 of 1 (latest)
Second question. When I try to confirm a PaymentIntent server-side to see if it succeeds before confirming it on the client, shall I put a parameter so that the auth flow (ex 3ds) is not triggered?
No need to try to confirm twice here
You can consider the PI/SI done once it has confirmed the intent
I also recommend using webhooks
This will help you manage state
ok so the mobile app can display a success message (after a PI for instance) as soon as your SDK has confirmed the status?
and server-side, I rely on the webhook to apply the correct state?
You can as long as you've confirmed payment was successful: https://stripe.com/docs/payments/intents
yeah webhooks are to manage state server side
Good insurance if client disconnects
Ok thanks!
Last question
We have an API to store/favorite credit cards
Each card is associated with a pm on stripe side
When creating a new credit card, who should initialize the setup intent ? API or client?
Can the client only send a pm (using elements) to the server that can then create the SI?
See this recommended flow: https://stripe.com/docs/payments/save-and-reuse?platform=web. SI would be created server-side