#samcic
oblique field
slate warren
Hi there 👋 are you able to share the IDs of the requests that encountered errors that I can take a closer look at?
I also saw you mentioned that you set the confirmation_method parameter so you could capture the payment later, and just wanted to make sure we were aligned regarding whether you're manually handling the confirmation step of the intent's lifecycle, or if you're manually handling capturing the intent?
slate warren
Hm, thinking through some options.
vernal otter
yes, so when we create the PaymentIntent we set confirm=true, but of course it might fail due to SCA requirements ("requires_action"), and in this case the server passes the relevant info back to the client so the user can complete SCA, then the request is repeated but with the additional info of the existing payment intent, which is then "confirmed" (rather than created fresh)
slate warren
Gotcha, so it is the confirmation step rather than the capture step.
vernal otter
(trying to remember the difference between capture and confirmation :))
I don't think we do "capture" at all
we try to confirm it immediately on the server side when we create the payment intent, and if that doesn't work we try to confirm it again after they've done SCA. So I guess yes, it's always a "confirm" operation
slate warren
Since you're planning to use this with the Card Element, which only accepts cards, can you try passing payment_method_types instead of automatic_payment_methods, and set it to ['cards']?
Confirming is the step of the payment process where the authorization with the issuer occurs. That authorization can be separated from the capture process, which is when the funds for the payment are actually moved. They're typically done simultaneously, so we can ignore the capture part if you aren't doing those separately.
Would you prefer to accept more than just cards? Our Payment Element now supports server-side confirmation:
https://stripe.com/docs/payments/finalize-payments-on-the-server
vernal otter
correct, we're not doing them separately
trying your suggestion...
nice, setting payment_method_types=['card'] seems to solve it
I think we're set now, appreciate the quick assist toby!
slate warren
Awesome, any time!
vernal otter
Do you know if there are any plans to support manual confirmation for the "Payments" Element (assuming we limit it so that only payment types are used that don't require redirect) so that we can move away from the (Legacy?) Card element?
I'm referring to the warning here: https://stripe.com/docs/payments/accept-card-payments?platform=web&ui=elements
slate warren
Yup, it already does, I linked to the related doc above.
vernal otter
oh ok cool, I'll check it out, thanks!
I'll leave you alone now, thanks again!
(been with Stripe for ~10 years and we're always impressed with the service!)
slate warren
The only thing I'm a little unclear on, is whether it explicitly supports confirmation_method: manual or if the flow leaves that as automatic but assumes you'll only make confirmation requests from your server-side code.