#theonlybigbad_connect-onboarding-bug

1 messages · Page 1 of 1 (latest)

next craneBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1329585408597819503

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

flat loom
#

Hi 👋

We focus on helping developers code integrations with Stripe APIs here so I might not be able to help with all the details but, can you share more about how you are creating the accounts and onboarding links?

hollow moat
#

Use Postman and that was successful. Then implemented the Create Account, Create Account Link, Create Payment Link and a Deactivate Payment Link methods that call stripe. The Create Account and Create Account Link seem to work and is all good. But when attempting to Onboard the new account from the Account Link or just tested within the Test Dashboard UI, it gets stuck on SSN field. Can't get passed that.

flat loom
hollow moat
flat loom
#

Request Ids will be more useful on my end

hollow moat
#

Account - req_1Ffa3Jx7AapS2s

#

Last account link - req_dgccdi3XtimdGX

#

Just did it from Postman, and I can get past the sticking point... The only difference I see is that my app sends the phone number as +14044449144 vs 404-444-9144 in postman. I'll try the +14044449144 in postman.

#

Nope Postman worked with +14044449144 format for the phone number. So I'll check all of the fields again.

flat loom
#

Sorry I'm not getting what the actual problem is. Are you specifically saying there is a point in the Stripe hosted onboarding where it hangs?

hollow moat
#

Yes. When I create the account and account link via my app, and then take the onboarding url into a browser window, and do the test phone, then test verify code, then shows the info and contact info, and then prompts for Social Security Number, won't accept an invalid number but when entering in 9 digits, the continue button spins for one second and then goes back to "Continue" and no error, just stuck.

#

I just did another postman request and made sure all parameters are identical to the API request, and onboarding works with the Post man created account but still stuck on the API onboarding.

flat loom
#

Postman does some additional processing of requests (one of the reasons I don't use it). So you may see some odd discrepancies. But it sounds the the onboarding flow being stuck is the real problem here.

hollow moat
#

Yes. Onboarding flow is stuck when trying to submit the SSN.

flat loom
#

Ack okay. Unfortuantely that isn't something I can help with here. We are focus on helping code integrations with the APIs. Your API requests all look good and there's nothing wrong there. We need to investigate the internal tooling that is powering the hosted onboarding.

I'm going to send you a link to create a support case with us.

hollow moat
#

ok

next craneBOT
#

Hello @hollow moat, we have sent you a direct message, please check it at https://discord.com/channels/@me/1329595453406445569

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
flat loom
#

I wanted to let you know we received your email and we'll be working on testing this out

hollow moat
#

In comparing the POST requests of a working and non working, I found several issues that could be the problem... Working state: NC, not working: North Carolina; default_currency: USD vs usd, tax_reporting_us_1099_misc.requested: true vs True, and transfers.requested: true vs True. One or more of those four things have got to be the issue. Otherwise I think they're identical.

flat loom
#

Okay but in both cases you still wound up with an onboarding session that gets hung up at SSN collection?

hollow moat
#

The two true vs True, is an issue, because that's caused by the .NET C# API code, latest version.

#

No. The "working" above goes through and the "not working" gets stuck as SSN submission.

flat loom
#

You should be able to pass the boolean value for True and the Stripe .NET SDK will conver it to what our API needs

hollow moat
#

ok. So then the only difference is the NC works, and North Carolina doesnt, and the USD works and usd doesn't.

#

I'll try "North Carolina" via postman.

flat loom
#

I'm getting stuck on requesting transfers without card payments but not explicitly passing the "recipient" service agreement.

hollow moat
#

Hah. The "North Carolina" breaks it.

flat loom
#

🫣

#

What a weird place to break

#

I will flag this internally so we provide a more meaningful error and hopefully catch this during account creation

hollow moat
#

Yeah. And I can't seem to find in the stripe dashboard anywhere to view the address info for a connect account.

flat loom
#

Okay yup I can reproduce with "California" instead of "CA"

hollow moat
#

Cool. I did see the address info in a working one when doing the onboarding so good to include it. I just need to fix my data source into the API to not use the long form. Thank you.

flat loom
#

Okay great. Well I'm glad you have a clear way forward and I'll work to get those bugs addressed so others don't fall down this rabbit hole