#jchannon
sweet pecan
slow birch
Yes! You'd use Account Links: https://stripe.com/docs/api/account_links
gentle marlin
thanks, any ideas what the urls should be, obviously the UI doesn't ask for that so not sure what I should put
slow birch
Well the Dashboard with return OAuth URL, which is different
But Account Links are the recommend integration path now for onboarding accounts
The refresh_url and return_url would likely be paths in your application
Where you want to return uses to when they're finished (return_url) and the refresh_url will handle creating a new Account Link with the same parameters, in cases that it has expired (they're only valid for ~5 minutes)/been used
gentle marlin
what do we have to do for the refresh url? do we need a UI for that url?
slow birch
That would depend, I guess on your app. It's just a fallback mechanism for when a user visits an expired URL. It should hit our API and create a new Account Link and redirect the user to that new URL
gentle marlin
ah ok i see
thanks
{
"error": {
"message": "You requested an account link for an account that is not connected to your platform or does not exist.",
"type": "invalid_request_error"
}
}
i assume the account field is my account number?
the docs say The identifier of the account to create an account link for. that doesn't make sense as i'm trying to create a link for them to create an account so i can't give an id as it doesn't exist yet
slow birch
the docs say `The identifier of the account to create an account link for.` that...
You'd create the Account object first with Account Links
The path you're describing is the OAuth flow
gentle marlin
and oauth isnt doable via the api?
gentle marlin
will it be turned off soon?
slow birch
Not AFAIK