Ian Kaplan

[twin estuary]

Hey there

The general advice is to just re-initialize Stripe with the correct key

[vivid rapids]

ok thanks!

and when retreiving a resource on a connect account is there a difference between using a stripe client with the key corresponding to the connect account and passing the account_id in the request options?

[restive venture]

Hi taking over for bismarck as they have to step out. Using the platform's key and passing the stripe account header is the recommended flow. That way you won't have to deal with juggling multiple secret keys. Just the platform one + passing an account id

But functionality-wise I guess there's no difference (to answer your question)

[vivid rapids]

the reason why im juggling multiple keys is to handle international debit

when i create an SEPA debit payment method it seems like i need to create it in the customer account. we have historically kept cards and ACH in the platform account

and it doesnt seem like cloning from the platform to the connected account is supported

do you know of another way to handle creating payment methods in connected accounts?

[restive venture]

when i create an SEPA debit payment method it seems like i need to create it in the customer account
Why? I haven't heard this

[vivid rapids]

by customer i mean connect

[restive venture]

Yeah I know

Why can't you do it on the platform?

[vivid rapids]

i wasnt the one who tried but i beleive we were getting errors

[restive venture]

Hm maybe if there's some sort of country restriction on the platform. Would be helpful to know the error.

But if you absolutely have to do this for whatever reason, recommend just passing stripe account header to create objects on the connect account