#Charlie GB
hollow lily
obsidian sluice
i just read this, but...
The setup_future_usage field just works when i know that i want to save the card
But i don't know if the customer wants to save their card until they check the option to save card in the UI
And the payment intent is created before the user checks the option to save card
So i can't set the setup_future_usage as off_session because i don't know if the customer actually wants to save their card.
coral hill
gimme a while to type out the options
obsidian sluice
OK
coral hill
have that check on a prior page, then create the PaymentIntent, or you can look into one of these betas :
- https://stripe.com/docs/payments/accept-a-payment-deferred
- https://stripe.com/docs/payments/run-custom-actions-before-confirmation - you probably can update the PaymentIntent before confirming
obsidian sluice
The second link doesn't work
coral hill
what do you see? it's working for me, so it might be a short hiccup
obsidian sluice
coral hill
hmmm, do you see the same error if you try on another device?
obsidian sluice
i will check
Yes, it's the same.
Mobile (Safari - iOS) and web (Chrome - Mac OS)
coral hill
hmm, okay, that's odd, maybe reach out to Stripe Support about it : https://support.stripe.com/contact/email
obsidian sluice
OK thanks
Is it possible to attach the payment method on the server side?
That is, i will assume that the customer doesn't want to save their card, so i create the payment intent without saving the card.
But if the customer checks the option to save their card...
Can i attach that unsaved payment method to the customer?
Attach is like saving the card, i guess...
Or am i wrong?
coral hill
it doesn't really work well that way i feel
obsidian sluice
OK OK, thanks
coral hill
to elaborate a bit more, it's possible to create the PaymentIntent with setup_future_usage=true but without a customer id. The PaymentMethod can then be attached to a Customer later. However, if you do it that way, you can attach the PaymentMethod anytime later to any Customer.
theoretically, if you do it that way, the card is still "saved" and can be reused. So i feel it doesn't really match the customer's expectations that you don't save their card (even if you don't attach it to a customer later)