#rjt
1 messages · Page 1 of 1 (latest)
Hello
If you want to confirm client-side you can pass the PaymentMethod ID to the client and use stripe.confirmCardPayment: https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-existing
I see, so for each type of payment method you'd need to call a different method? 👍
Well overall yes. But really I'd recommend just confirming on the backend and then just passing to the frontend to call confirmCardPayment if the PaymentIntent moves to requires_action
The reason that I ask is that we are planning on supporting ACH payments in the future.
Thanks
Yep you don't need to confirm client-side for ACH
Since there is no authentication needed
So it would be easier to just confirm server-side and then handle next actions when needed
As that will scale better
Interesting. Is it possible to confirm server-side when adding a new payment method via the Payment Element?
I ask because my primary motivation for wanting everything confirmed client-side is not wanting to implement two different flows (client-side confirm when adding cards and server-side when using existing cards)
I mean these are going to be two different flows no matter what
But no, you can't really confirm Server-side with Payment ELement unless you use this flow: https://stripe.com/docs/payments/run-custom-actions-before-confirmation