kz_api

[quaint sierra]

👋 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/1340973981016264705

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[vagrant smelt]

Is it enabled in your Connect PM settings on the platform? https://docs.stripe.com/connect/payment-methods

[astral sinew]

Actually no, but I would need to mention that I don't use Checkout or any Stripe frontend component, rather I build my own frontend and call my server from it, then do server-to-server API call to /payment_intents

And why would having this inactive in this UI only affect specific accounts?

[vagrant smelt]

I think the inferred capabilities are requested from the specific PM settings when you create an Account in the Dashboard

[vagrant smelt]

I don't know, we don't really know how the Dashboard works. If this is an issue, then use the API

[astral sinew]

I am not sure if I understand correctly, but we don't use the dashboard to create accounts, the customers onboard themselves via OAuth flow that we offer by adding our client_id to the request

What do you mean by use the API? Which API? POST/accounts you mean?

[vagrant smelt]

Ah, maybe that request is inaccurately flagged internally then

[vagrant smelt]

Yes

[astral sinew]

So you mean this request req_bkcVdcKU6euyTq shows that the account has been created using the dashboard?

[astral sinew]

This is not optimal, I am already having a system using the OAuth flow for a couple of years.

Why would I need to change it because suddenly some unexpected behaviour started to emerge?

[vagrant smelt]

Yeah but I suspect that's inaccurate

As I said, we're not really sure what determines whether or not an account has a certain capability requested via OAuth. Did you try turning it on as I suggested?

Maybe it is inferred by the existing Stripe accounts that are being onboarded to your platform already having SEPA enabled?

i.e. account B1 has SEPA capability, they onboard to your platform and create account B2 (the request you shared) so we automatically request the capabilities they already have

[astral sinew]

I will do so now, is there anything you recommend doing in order to assure that SEPA is by default enabled for our connected accounts?

[astral sinew]

But we also have plenty of managed accounts that never signed up with Stripe before and still have it enabled

[vagrant smelt]

Then I am not sure, as I've said

[astral sinew]

Ok thanks

Should i do sth else other than enabling it in the ui you provided?

[vagrant smelt]

I'd recommend just requesting to capability after account creation if necessary: https://docs.stripe.com/connect/account-capabilities?connect-account-creation-pattern=typed#requesting-unrequesting

[astral sinew]

Sounds good

Can you confirm whether this link https://docs.stripe.com/connect/payment-methods and the concept of payment method configuration apply only to "Checkout, Payment Links, Elements" or? Which means it's irrelevant in our case?

[vagrant smelt]

Well that is also where platforms can control the requested capabilities of their connected accounts in a UI as I said

The actual configuration ID and applciation only applies to those surfaces yes

[astral sinew]

I'm a bit confused sorry, so enabling the payment method here would request it on onboarding?

[vagrant smelt]

https://docs.stripe.com/connect/payment-methods#enable-payment-method

After you review and confirm your update, Stripe converts all Eligible connected accounts to Enabled, with a capability status of active. Stripe also automatically applies the capability to new accounts as they become eligible. This could happen because a new account signs up for your platform and finishes inputting their information or because an account updates their information to become eligible for the payment method, such as updating their MCC from one that’s ineligible to one that’s eligible.