#iy2011
1 messages · Page 1 of 1 (latest)
Hello!
Can you provide more details about the specific issues you're running into? You should be able to create an Express account for someone regardless of any other existing accounts they may or may not have.
Right, we are going through the steps of 1) create a new Express acct ID, 2) generate a new Account Link for that acct ID to send to the user. But the docs indicate that sending a new link to the user should be via our platform and set a return_url and refresh_url from our platform. We can't do that because our user today will be directed to their current Standard acct in our platform
So the question is what we should set for return_url and refresh_url because we're looking to just send a one-time Account Link URL
You would need separate URLs for Express accounts vs. Standard accounts in this scenario.
And/or logic in your code that provides the correct response based on this use case.
Hmm okay. Is a new connect account ID without the Account Link accessible at all, or essentially pending verification?
What do you mean by accessible?
Accessible by the user
Example - we generate the new acct ID
and then share a link with them such as the usual express login link to verify https://connect.stripe.com/internal_express_login/{{add_their_acct_id}}
I'm not sure I understand. The only thing your refresh_url needs to do is create a new Account Link for the person in question. You would use the existing Account you already created for them when creating the new Account Link. See here for more info: https://stripe.com/docs/connect/express-accounts#refresh_url
Got it. I'll review this internally. our uber goal is to migrate just one user from standard to express so hoping to not build a new URL onboarding flow in our platform for one user. Thanks
You can set the refresh_url for their Account Link to something that includes their Account ID, or point to a special URL just for this one situation.
Got it, ty!!