#jry_j
radiant gulchBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- jry_j, 20 hours ago, 31 messages
thorny relic
account.update is still used. As for account onnboarding, I don't know what you mean. There are a few different account onboarding options. Which one are you talking about?
carmine egret
for account_update, I tried creating links for both express and standard accounts, is it only for custom accounts?
carmine egret
for account_update, I tried creating links for both express and standard account...
when I tried with express account, it comes back with an error:
You cannot create account_update type Account Links for this account. Valid types for this account are ["account_onboarding"].
and when I tried with standard account, it comes back with:
StripeInvalidRequestError: You cannot create account_update type Account Links for this account. Valid types for this account are ["account_onboarding", "embedded_popup_auth", "embedded_popup_onboarding"].
The account onboarding option I'm looking at is:
stripe.accountLinks
.create({
account: retrievedAccount.id,
type: 'account_onboarding',
})
wondering if this is a reliable option for users to edit their payout and profile details?
thorny relic
You can't update an account that hasn't onboarded
You need to send them through the onboarding flow first
carmine egret
I tried generating the link for standard account that is complete and an express account that is enabled
thorny relic
Do you have an example request ID I can look at?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
thorny relic
It looks like there are still outstanding onboarding requirements for each account that need to be satisfied first
You can see them by retrieving the Account object and looking at the requirements hash
carmine egret
that's with stripe.accounts.retrieve() correct?
res.requirement comes back with this object: {
alternatives: [],
current_deadline: null,
currently_due: [],
disabled_reason: null,
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
}
I'm not quite sure what to make of it
thorny relic
Which account is that for? If it's the Standard account, then that makes sense. You can't use and Account Links to update the Standard account. The user of the Standard Account would need to just log in to update their information.
carmine egret
I updated the Express account, and it's coming back with the same object
thorny relic
Did you try to create another Account Link and get the same error?
carmine egret
yea, I switched out the account: {stripeID}
thorny relic
Do you have a request ID for that request?
thorny relic
With the Standard account, again, this error is expected. Standard account users have access to the Stripe Dashboard and would simply login to update their details
carmine egret
ok
thorny relic
For Express, once they have finished onboarding, you want to send them to the Express Dashboard via a Login Link. This will allow them to update information they've already entered during the onboarding process.
Docs on the Login Link can be found here: https://stripe.com/docs/connect/integrate-express-dashboard
Apologies for the initial confusion. I somehow got mixed up about the Account Links and the Login Links (gotta love Stripe's product names)
carmine egret
haha gotcha
For my second part of the question, I understand that users should go to the respective links you've mentioned above to update details
I was playing around with the same accountLinks, and was able to access it using 'account_onboarding' and it seems like users can edit their profile and payout accounts from there
I'm wondering if there will be any implications for using this rather than going through loginLink or general stripe website
because ultimately, I just want to provide a simpler user experience for making those changes
and hopefully keep users within the app
thorny relic
That's a good question. My gut instinct is telling me that's not a good idea, but I'm having a hard time coming up with a good reason not to.
That being said, if you're trying to keep users within your app and control the entire experience, you might want to look into Custom Connect accounts instead. Like, Express and Standard are good if you want Stripe to do some of the heavy lifting, but it sounds like Custom might actually be a better fit here. Account Links still work, and you can call them with account_update when the user wants to update their account info