#Tom Hüser
1 messages · Page 1 of 1 (latest)
Hello 👋
Just to clarify, what do you see exactly when you list all account capabilities using the API?
https://stripe.com/docs/api/capabilities/list
I see an overview of all capabilities marked active or pending in the case of eps_payments. The same capabilities are marked active or pending when looking in the dashboard's profile of the connect account. For example in the capability list bancontact_payments is marked as active and requested, but looking as the connect account itself, it is not turned on.
In total there are 14 capabilities listed, all of which are active after onboarding, except for eps_payments
But the connect account only has card, apple pay and google pay turned on and the latter two are not listed in the list
This is all againt test data, if that is relevant
can you share the account ID of the connected account?
The connect account id of the test data account is acct_1LrjJ9RgsToFLxkL.
Or do you mean another id?
the above ID should work, looking..
Since you're using Standard accounts, I'm assuming you're creating direct charges?
Can you share the example payment intent ID that you're using to render PaymentElement?
I am creating direct charges yes. When testing the PaymentElement I used the API to create a payment intent to render the PaymentElement. The ID of the payment intent was pi_3LrjWURgsToFLxkL0OYGNF0H
One thing that I do see is that you allow the connected account to customize their own methods using the dashboard
https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts
In test mode however, most payment methods are off by default
but I do see that some payment methods do show up as active so digging
Yes the connected accounts should have the option to customize their own methods via dashboard. That is why I wanted to show them in my application, which ones they have turned on, without needing to access the dashboard.
Still haven't been able to find much 😦
Appreciate your patience
No worries, I will be away for the rest of the day anyways. For the sake of my implementation, can I assume that active on a capability should mean it is turned on by the connect account? Then I can continue with my implementation in the meantime.
Yes, active should mean it is enabled. Pretty sure I'm missing something very obvious here.
Okay, thanks for the info in the meantime
Hey @arctic garden apologies but I missed this thread for a bit. Unfortunately the API doesn't currently allow you to view/set the enabled payment methods for an account at the moment. I will put in a feature request for this at the moment, but for now the dashboard is the only way to directly check this.
You might be able to get some relevant information by creating a SetupIntent or PaymentIntent on the account with automatic payment methods enabled, that will return an intent will all relevant payment methods include. If you need this info in another context please let us know and we can try to think of another workaround that might help here