#nickderobertis
1 messages · Page 1 of 1 (latest)
Hi there
So sounds like Payment Sheet as opposed to Payment Element here since you are talking about an ephemeral key?
As in... this is a mobile integration?
ah yes, sorry. well we have both react native and react native web so we will be doing both i think
Oh okay
Well Payment Element does not support handling saved PaymentMethods
So you don't have to do anything special there
With mobile, PaymentSheet does if you pass both a Customer and Ephemeral Key as you stated
So yes, if you omit the Ephemeral Key then the customer won't see saved payment methods in the PaymentSheet and can only add new ones
ok great, thanks for answering that question. it's news to me though that the payment element doesn't support saved payment methods. what is the best alternative? we need the user to be able to choose from saved payment methods when they are logged in
Yeah this is a common ask and we do hope to support this in the future. For now you would need to build your own UI for saved payment methods on web
ah ok, we are already using CardElement so i will just need to migrate that flow for setup intents then
just confirming, the react native SDK definitely won't work for react native web, right?
Right. You would use Stripe.JS with a Webview
The Stripe React Native SDK can only be used in a mobile app
got it. well one of the reasons we wanted to go to Payment Element was to support apple/google pay. i guess instead we will need to use a combination of Card Element and Wallet Button Element
Hmm not sure I follow?
Card Element doesn't give you extra functionality from Payment Element
Like both require you building a UI for saved PaymentMethods
So would still recommend using Payment Element as it provides more support (like wallets)
we want users to be able to pay on demand, and save for later use, for both cards and apple/google pay, on both web and native
Yeah so for web Payment Element is still best here
And then for mobile you should use PaymentSheet
That is the simplest integration with the most features
but you said payment element doesn't support saved payment methods? we would want them to be able to select to pay with an existing method
Sorry I think I confused you.
Payment Element supports saving PaymentMethods
But not displaying saved PaymentMethods
hmm, ok. so for native we will just use Payment Sheel for everything.
on web, I guess in our UI we will ask if they want to use a saved payment method or add a new one. if saved payment method, we handle everything in our UI and create a payment intent on the backend with confirm=true. if new payment method, then use Payment Element
You got it
ok great, thanks for explaining everything, it makes sense now. do you know if there is any timeline on supporting displaying saved payment methods in the Payment Element? if it's not far off we might just delay the integration because it would simplify things here substantially
We are working on it but I can't give any specific time frame
yeah i understand. thanks for all your help!