#jeffrey-paymentelement-types
drifting scarab
limber lantern
jeffrey-paymentelement-types
@light thunder can you give me a bit more context? Are you a Connect platform or building a plugin?
light thunder
<@278599682299789312> can you give me a bit more context? Are you a Connect plat...
sure, we build a solution where a customer can connect his stripe account and then display the payment element, but over the api not connect plattform.
so we are not controlling the account and don't want to show something that is not working
limber lantern
What does "connect his stripe account" mean exactly though? Like they give you their API keys?
light thunder
they add the inside the plugin by there self
limber lantern
Okay and what do you mean "is not enabled inside the account" exactly? That they don't have access to SEPA Debit at all? Or just that they have not made it enabled by default in their settings?
light thunder
by default SEPA Debit is not enabled, but with our setupIntents the payment element shows SEPA Debit event if its not enabled
limber lantern
okay so the settings in the Dashboard is tailored for our "automatic payment methods" feature
if you use this instead of passing payment_method_types it'll surface the right ones. But there's no way to only filter the one you want and know which ones are enabled by default
light thunder
got it thank you, can I add an option to only display payment methodes that are able to get added into the customer account for later charges?
limber lantern
yes that's already the case with SetupIntents since it's explicitly to collect payment method details for future payments
light thunder
thank you
I have another question regarding 3D Secure.
In our real world test we where facing the problem that some paymentIntents where returing the status: requires_action because of 3D Secure.
Can we force that the user needs todo 3D Secure directly when setting it up?
limber lantern
Can you reword your last sentence? Who is "the user" in that sentence? The end customer paying? Someone else?
light thunder
sure, yes the end customer that pays "our customer" using our plugin 😅
limber lantern
So you use PaymentElement already. So there's nothing that should be needed beyond confirming the SetupIntent and having 3DS "just happen"
light thunder
ok sounds good then I will have a look why that was happening.
thank you for your fast help