Clarity on the "Save credit card" behavior

[carlos-prezzee]

Hi Stripe team 👋 ,

We are migrating to the Mobile Payment Elements on Android & iOS app and we have a miss match of behaviours in regards the "saved payment method"

We are following this mechanism, where we first collect the payment info and then we listen to the intent callback to create the payment intent on the server.
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=android

We are also passing the ephemeral key secret as per the documentation. In fact, we are able to see the checkbox in the UI to save the payment method. But after the transaction is completed, we are unable to see the saved payment method on the UI and also not present in the customer in the Stripe Dashboard.

We do the same process on iOS using the same backend and it is working as expected.

A good call out is that we are not using (neither on iOS or Android) the value that the sdk returns shouldSavePaymentMethod

Are we missing something on our android sdk to make this work? or something is missing on our backend.

When reading this part, it seems like the backend should setup setup_future_usage following the value shouldSavePaymentMethod? - If thats the case, why it works on iOS but not on Android,

When confirming a PaymentIntent from the server, pass it the mandate_data parameter to acknowledge that you’ve shown the customer the proper terms for collecting their payment details. To make sure you display the proper terms, be sure that all IntentConfiguration properties match your PaymentIntent (for example, setup_future_usage, amount, and currency).

Would really appreciate your support,
Thanks.

[yuki-stripe]

I'm sorry we never answered this! To answer directly, if your server confirms the PaymentIntent (not typically recommended), you should set setup_future_usage if shouldSavePaymentMethod == true. If your server doesn't confirm, it should all work automatically.

We highly recommend using ConfirmationTokens (the guide linked above demonstrates that API now), which takes care of saving payment methods automatically, including when your server confirms the PaymentIntent - there is no shouldSavePaymentMethod value to read anymore.

If you run into problems with any of this please open an issue!