#alpha-mouse
forest lodge
buoyant ermine
Sure, thanks
hybrid tapir
would you mind sharing the request id that triggered the error? https://support.stripe.com/questions/finding-the-id-for-an-api-request
buoyant ermine
That was not an api request, but rather oauth flow https://stripe.com/docs/connect/oauth-express-accounts
With the url of the form https://connect.stripe.com/express/oauth/v2/authorize?client_id=ca_HYYMvYBIbO6Chv23VlahX5F7Hem6MVhr&response_type=code&suggested_capabilities[0]=transfers&suggested_capabilities[1]=card_payments&suggested_capabilities[2]=us_bank_account_ach_payments (I've excluded most of the parameters)
And got that in the browser
open snow
Hey! Taking over for my colleague. Let me catch up.
open snow
You need to pass suggested_capabilities as an array, according to the url you are sharing, suggested_capabilities is a String
buoyant ermine
Am I passing as string? effectively there are three parameters, suggested_capabilities[0], suggested_capabilities[1], suggested_capabilities[2]
open snow
Ah I see. Does the Connected Account located in US ? because for us_bank_account_ach_payments the connected account must be in the US
buoyant ermine
Yes, as a stripe_user%5Bcountry%5D parameter we send US
open snow
Do you have the AccountId of that user ?
buoyant ermine
that user - no, the error happens when trying to create an account for them.
open snow
Not sure I'm following then. why are you using oauth is the user don't have an Account already ?
You should probably follow this guide then and create an Express Account using Stripe API for that user
https://stripe.com/docs/connect/express-accounts#create-account
buoyant ermine
We're doing that flow
https://stripe.com/docs/connect/oauth-express-accounts
where the user is directed to create an account themselves. Don't know why exactly we use this flow, not the one you've linked.
open snow
Don't know why exactly we use this flow, not the one you've linked.
You should be using the guide I shared above. this guide is used when the user has an Account and you want them to be registred to your Platform Account
buoyant ermine
In our case, they don't. They are always creating accounts for the first time to be used with us as platform.
tacit fog
Hi 👋 jumping in as my teammate needed to step away. It looks like you're working with Express accounts, and with those we strongly recommend using our Destination Charge flow as it is designed to work with those type of accounts. With the Destination Charge flow all payments happen on the Platform account, and you the resulting funds are then transferred to your Connected accounts. So the capability would be requested for the Platform account rather than the Connected account.
Are you/were you planning to use Destination Charges?
https://stripe.com/docs/connect/destination-charges
buoyant ermine
In fact we do use Destination Charges. With on_behalf_of. Do you say that in this scenario we only need the capability on the platform, not on the connected accounts?
tacit fog
I believe so, but am trying to think whether on_behalf_of changes that.
I don't think you need the capabilities on the Connected Account, but am having trouble locating a documented definitive answer on that. Out of curiosity, did you try to test the payment process and encounter a capability related error that prompted this question?
buoyant ermine
No, haven't tried yet. But will do.
Thanks for the info, i don't have any more questions at the moment)