#benjamineugenewhite
proven widget
remote ermine
Hi there!
Could you clarify what you mean by "multiple trips"?
Based on what you've shared, I believe you're following our recommendation to share a new account link with the end user: https://stripe.com/docs/connect/standard-accounts#handle-users
paper mango
Correct, we generate the account link server-side then redirect user to it in SPA.
By multiple trips, I mean that when testing out the flow, as best I can tell, i filled out all required fields, but when got back to our SPA, and Stripe Account was re-retrieved, charges_enabled was not true, so went back to account link flow on Stripe and, indeed, there was additional info I had to provide.
For instance, initially, i'm prompted to provide last 4 of social security, and then when I go back, I'm prompted to provide full ssn
I just went through with business as "individual" type and that was the only additional piece of info I had to provide.
If i'm not mistaken, when I did this yesterday, it was as a different business type, and I believe I was required to supply more info.
remote ermine
This is a bit hard to follow. Could you share step by step what you're doing?
paper mango
Could I upload a screen grab?
remote ermine
sure!
paper mango
okay -- one minute, going through flow again
paper mango
ay ay ay. first pass through at screen grab, this issue happened, but i realized i exposed personal data, so scrubbed that. on second time through with new stripe account etc., the issue did not occur.
one of my colleagues just verified that she got same issue i'm trying to describe above.
almost at end of my Friday work day so may need to supply screen grabs next week (in a new thread, i gather).
remote ermine
A screen grab or list of exact steps we can use to try to reproduce would be helpful
And yes, a new thread will be perfect.
paper mango
- Get a Stripe Account link URL (I'm doing this through the front end for our app) and visit it. Fill out the multi page form providing all required fields.
- Get to "review and finish up" page (it shows no errors). Click Submit. See UI to update to say being taken back to my app.
- My front end app tells our server to retrieve the Stripe Account for which the link URL was created. The server retrieves the account. It checks the "charges_enabled" property on the account and sees that its False. It tells the front end about this state of affairs.
- Seeing that charges are not yet enabled for the account, the front end sends the user back to the account link url. It says that additional information is required, and specifically, wants full SSN, not just first 4.
- Provide the full SSN, and resubmit the Stripe account link form.
- Get redirected to our front end app, which tells server again to check if user has charges_enabled. This time, the server reports back that charges_enabled is true.
- Our front end app no longer displays the component that prompts our users to go to Stripe.
That's basically it.
I suppose there's a possibility that the server actually finds that the account has charges_enabled the first time through, and that somehow our front end has a bug that causes it not to get the refreshed data though I don't think that's the case.
And it is definitely the case that after going back to the link URL, I'm asked to provide a full SSN in order to complete the form.