yourcat

[earnest creek]

Hello 👋
As far as I know, that is the canonical way to handle this (Updating the PaymentIntent with setup_future_usage)

Out of curiosity, what kind of complexity do you foresee with this flow?

[true ridge]

Well right now, basically the server isn't involved in the client side payment flow at all and is very hands off until the sale is done. This would mean some bad ux for slow mobile connections where the checkbox click introduces a request that has to be waited for before we enable the pay button. Personally with how streamlined everything else is i would have expected there to be an element that handles this, or something. Not sure, it just becomes a bit of a chore to implement this functionality.

Basically i guess i would have expected being able to, server side on pi generation, enable this option, and then the client could bundle the user choice when paying. That's how our old payment processor worked.

[earnest creek]

Unfortunately, that's not how our APIs works. You'd need to specify if you want to save the payment method while creating a PaymentIntent or update it later on

[true ridge]

Alright, thanks. Just wanted to make sure I'm not doing a lot of work that isn't necessary.