sai_rez-intents

[hardy remnant]

yes (https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage)

[shell osprey]

Could you go into a little more detail regarding both options, do both save a card to the customer?

[hardy remnant]

yes they both save the card

the difference is you use the one that matches the one that you expect to be your use case for future charging of the card. If it's off-session then we know you want to qualify for a merchant initiated transaction(https://stripe.com/guides/strong-customer-authentication#merchant-initiated-transactions-including-variable-subscriptions) later, which means we set some things up internally differently, and there's more chance we ask for 3D Secure on this first PaymentIntent so that you can get the exemption on future payments because the first was authenticated.

[shell osprey]

So if we call confirmCardPayment after creating the paymentIntent that should authenticate the payment and get us the exemption for future payments?

[hardy remnant]

that's the idea yes

that might still happen with on-session, it's just that we know you want the exemption later so we might optimise for more authentication whereas with on-session we might have let the payment happen without authentication if posible