#ravid_53977
1 messages · Page 1 of 1 (latest)
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.
- ravid_53977, 2 days ago, 4 messages
hi! hmm let me think/research but I don't believe so initially
What would the use case be exactly?
If i want to implement my own payment method picker
that's not really supported , sorry, PaymentElement just does all this for you
no, I don't understand what you'd want that, it all kind of goes against the explicit design of the PaymentElement(to show your customers the payment methods you can accept and let them pick the one they want, to increase conversion)
one option is I suppose you could explicitly pass payment_method_types on your PaymentIntent and only pass the types (or one singular type) that you want so there are no other options. But depends on your use case and details.
Yeah i tried this, but I'm also using an ExpressCheckoutElement and it affects the options there, like: link, google pay and apple pay.
is there a way for it to affect only the Payment element and not the ExpressCheckoutElement?
not sure I understand. when you say "tried this", you mean explicitly controlling payment_method_types:[...]?
I don't see how that would effect ECE and PE at the same time unless you do something like you use the same PaymentIntent for both of them on the same page at the same time
Yep, explicitly controlling the payment_method_types. i think it's happening the ECE and PE are using the same stripe options
through the elements provider
so if i have in the payment_method_types only "cashapp" i wont see anything in the ECE
yeah if they share the same StripeProvider then that's what will happen