#shru-payout
empty latch
calm crane
I am trying to fix this warning in the console. All methods are enabled on the platform account as far as we can tell, so I am assuming the warning is for the connected account passed to the stripe header?
empty latch
@calm crane the Standard account holder would activate them in their dashboard (https://dashboard.stripe.com/settings/payments) instead.
As the platform, for Standard you can see the status of the capabilities the account has, but not request them.
For your screenshot, hard to say without knowing exactly how you use Elements there(are you using just your API key, or your API key plus the stripeAccount option set to a specific connected account?)
calm crane
api plus stripeAccount set to the connected account id, so basically we can not enable payment types for all connected accounts via the platform using standard?
empty latch
cool, makes sense, Direct Charges so yes, it's the capabilities of the connected account the warning is talking about
As the platform, for Standard you can see the status of the capabilities the account has, but not request them, as I mentioned.
the connected merchant has their own relationship with Stripe for onboarding and so on. The idea I think is you could tell them "hey, you should enable this method so you can get more customers through our platform" and direct them to their dashboard to enable them(and then the options just automatically appear in Elements [0])
[0] right now you have to explicitly pass payment_method_types on PaymentIntents (maybe by checking the account's capabilities manually) but we plan to change that soon so it can be automatically inferred
calm crane
@empty latch ok currently in the payment intent creation I am passing an array of all possible methods that we wanted to accept, with the Payment Element in the frontend I guess it hides any methods not available on the connected account in live mode right?
With your comment about payment_method_types on the intent I guess you mean if we only have card, eps, sepa in there and the user activates some other payment type, then an error would result with the intent right?
And therefore until its auto inferred we should fetch the account capabilties to populate this for now?
empty latch
well you can pass all types you want to accept, that is fine!
if the connected account can't accept them then the Element just won't show them, as the warning mentions
in future we'll make it so you can just omit payment_method_types to get all possible and activated types appearing in the Element
calm crane
But if they can accept them and we haven't passed that type in the intent then we have an issue right?