#henrique_error
strong foxBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1311441954650984478
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
slow geode
Just to give more context, these errors are happening for multiple connect accounts we have connected in our platform.
This is an example of the error we have: https://dashboard.stripe.com/acct_1PMEV64Gks2D6VFY/logs/req_vsFhY2xflGOey4
past mica
Thanks for the info, looking in to this
slow geode
We only list the ["card", "link"] payment methods whenever the Link capability is active
past mica
Gotcha, is that to say you manually pass paymentMethodTypes=["card", "link"] when initializing Elements on your page? Still trying to get to the bottom of the mismatch
slow geode
Yep, we do this manually because PE is always relying on the Payment Methods from the Invoice settings
past mica
Where you seeing mismatches when not specifying manualy? If you leave that out, we should automatically refer to the same settings that your subscriptions use as far as I know. That should theoretically keep things in sync
slow geode
The problem is that, we as a platform account we can't change the payment methods on the invoice settings for the connected accounts
And some times the admin of the connect account is able to enable payment methods we can't supporte
I know it is possible to control the payment methods on the PMC's connect account, but changing in this place won't affect the payment methods on the Invoice settings.
past mica
Ah right, I forgot that direct charge flows work like that. In that case it would probably make sense to manually pass payment_method_types when creating the subscription as well. That way you can ensure that they are PMs that you support and that they match what you are passing on the client https://docs.stripe.com/api/subscriptions/create#create_subscription-payment_settings-payment_method_types
past mica
Good question, I think when creating intents directly we have better PMC support where you can set things on the platform and have the setting be respected on connected accounts. Double checking that and will get back to you
Yep there are platform settings for direct charge payment methods https://dashboard.stripe.com/test/settings/connect/payment_methods
slow geode
In our app, for onetime payments I think we create invoices as well, do you think it would be a problem?
I mean, we create the invoices and then charge the customer
past mica
Invoices would also use your billing settings, though I think billing may support PaymentMethodConfigs now. I am looking in to this and will get back to you
slow geode
Pompey, do we have an API to fetch the payment methods available on the Invoice settings?
past mica
If you list the Payment Method Configurations and look for one named "Billing Payments" I think that would work https://docs.stripe.com/api/payment_method_configurations/list
Also unfortunately it is looking like you can't pass your own PMC ID to the subscription or invoice API. So I think manually specifying the payment method types would be the best way to go at the moment