#pavlos-ephemeral-key-qs

1 messages · Page 1 of 1 (latest)

hot steppeBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

umbral yew
#

Web and Mobile have different set of Stripe Elements.
While the PaymentElement can just use the publishable key, the Mobile PaymentElement (PaymentSheet) uses ephemeral key for a customer

https://stripe.com/docs/payments/accept-a-payment?platform=android&ui=payment-sheet#android-collect-payment-details:~:text=For security reasons%2C your app can’t create these objects. Instead%2C add an endpoint on your server that%3A

If you never save cards to a Customer and don’t allow returning Customers to reuse saved cards, you can omit the Customer and Customer Ephemeral Key objects from your integration.

remote fox
#

I see, this mentions:

If you never save cards to a Customer and don’t allow returning Customers to reuse saved cards, you can omit the Customer and Customer Ephemeral Key objects from your integration.

#

Which is what we want to do - save cards to a customer

#

so I assume we do really need to return an ephemeral key from the API.

umbral yew
#

Yup

remote fox
#

And Web can just ignore it whereas Android/iOS will use it

#

Ok, thanks!

umbral yew
#

NP! 🙂 Happy to help