jarrett-payment-element | Stripe Developers | Page 1

pliant fiber Oct 25, 2021, 2:17 PM

#

hello, give me a sec

#

If the answer is simply "choose the payment method types on the payment intent"
PaymentElement does show payment methods on the PaymentIntent "payment_method_types" but also reorders them based on what the preference for customers generally is in that region

down the line it will also support things where you don't specif a p_m_types and PaymentElement shows you ~every payment method that is supported

Payment methods are also filtered to show only those supported by your customer’s local currency."
ah which doc is this on? can you share

amber beacon Oct 25, 2021, 2:31 PM

#

https://stripe.com/docs/payments/payment-element

Stripe Payment Element

Accept payment methods from around the globe with a single secure, embeddable UI component.

#

#

I feel like the Payment Element is great... just that it's lacking some key stuff to really make it able to provide the benefits it could. Honestly, PayPal has a junk platform (unfortunatly we just need to support it), but the one good thing they do have is that they allow you to "exclude" and "include" payment methods. Hopefully PaymentIntents will take a similiar model where you can include or exclude and the PaymentIntent would show all the possible PaymentMethods that apply based on the settings of your PaymentIntent. (currency, customer, etc vs. showing errors if you have conflicts)

Also, right now we have a purchase flow where we'd like to do things like show users all payment methods that they could use, but also save the payment method if possible. This isn't possible right now because if you want to save the payment method you have to have setup_future_usage yet you can't create a PaymentIntent with that option, but have payment_method_types that don't support that. Maybe there could be like a setup_future_usage option called like preferred_off_session or something like that so it's clear that you'd like it, but you know it may not be possible.

pliant fiber Oct 25, 2021, 2:48 PM

#

Hopefully PaymentIntents will take a similiar model where you can include or exclude and the PaymentIntent would show all the possible PaymentMethods that apply based on the settings of your PaymentIntent.
PaymentIntents already do that though, with p_m_types and currencies etc

like you get a 400 if you create a PaymentIntent with currency: usd and SEPA Debit as a PaymentMethod type

#

Maybe there could be like a setup_future_usage option called like preferred_off_session or something like that so it's clear that you'd like it, but you know it may not be possible.
yep that is something the team is looking at and solving soon

amber beacon Oct 25, 2021, 2:49 PM

#

getting a 400 isn't doing it though

#

like if I want to accept 10 payment methods I can't go through testing every combination until I don't get a 400

#

unless I'm doing something wrong or not explaining myself properly.

#

additionally a special option "all_supported" would be nice for p_m_types instead of an include/exclude option

pliant fiber Oct 25, 2021, 2:54 PM

#

additionally a special option "all_supported" would be nice for p_m_types instead of an include/exclude option
that is coming too!

#

just not fully ready yet but is probably the next main thing coming down for PaymentElement + PIs

amber beacon Oct 25, 2021, 2:58 PM

#

this makes me so happy! If you're able to... is that something you think we'll see in weeks, months, quarters? If you can't say I understand. The reason I ask is because I think it might make sense for me to just hold out on Payment Elements until that stuff comes out since right now my integration is so messy and complex to do until those options exist.

pliant fiber Oct 25, 2021, 2:59 PM

#

I expect O(multiple weeks) for that

amber beacon Oct 25, 2021, 2:59 PM

#

haha ty

#

i'm good here!

#

/thread

pliant fiber Oct 25, 2021, 3:02 PM

#

perfect, glad to hear you're excited about PaymentElement, that team would love to hear this feedback from you

to dig in a bit more

like if I want to accept 10 payment methods I can't go through testing every combination until I don't get a 400
what did you have in mind for this? how should this be solved for in your eyes

amber beacon Oct 25, 2021, 3:03 PM

#

if p_m_types took an all_supported option that would be sufficient.

#

i could imagine some people might want to go further and have inclusion or exclusion abilities

#

to say like all method except sepa_debit and wepay or something like that

#

maybe a magic array could make this possible. ['!sepa_debit'] would be everything except sepa_debit or ['card', 'sepa_debit'] would be the current way it works and then just like all_supported would be the ultimate option that just always takes everything into account and gives you the ability to show customers all the payment methods you possibly could.

amber beacon Oct 25, 2021, 3:30 PM

#

that helpful?

pliant fiber Oct 25, 2021, 3:32 PM

#

sorry stretched across >10 threads, haven't had a look yet

#

but coming back to this once I get a handle!

pliant fiber Oct 25, 2021, 3:49 PM

#

ah perfect, that helps lay it out

so yeah all_supported is hopefully coming down the line

#jarrett-payment-element