#winni_connect-onboarding

1 messages · Page 1 of 1 (latest)

regal rivetBOT
#

👋 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/1230541462534492232

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

grizzled roostBOT
#

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.

mystic mirage
#

Hello

grizzled roostBOT
mystic mirage
#

Hello toby

clear garnet
#

Hi 👋 it's expected for newly created Connected Accounts to be in a restricted state until they complete onboarding.

mystic mirage
#

how to complete onboarding?

clear garnet
#

What type of Connected Accounts are you using?

mystic mirage
#

custom

clear garnet
#

Gotcha. Those support either the Stripe hosted onboarding flow, or allow you to build your own onboarding flow. As you're going through the test onboarding flow you selected you should be able to use the values found in here to create new Connected Accounts and bring them active:
https://docs.stripe.com/connect/testing

Testing Stripe Connect

Before going live, test your Connect integration for account creation, identity verification, and payouts.

mystic mirage
#

I'm done with all of this.

clear garnet
#

So you have an active testmode Connected Account now?

mystic mirage
#

no not active

#

So I come to ask

clear garnet
#

So what state is the account in, what do you see in it's requirements hash?

mystic mirage
clear garnet
#

Did you build your own onbarding flow, or you using Account Links to send your Connected Accounts to a Stripe hosted onboarding flow?

mystic mirage
clear garnet
#

What is the ID of the Connected Account?

mystic mirage
#

acct_1P6wrvPLHGWdUBw8

clear garnet
#

How did you handle the onboarding for that account?

mystic mirage
#

By node.js api request

grizzled roostBOT
mystic mirage
#

I have figured out all information needed

#

Hello Koopajah

lavish wyvern
#

Hello! looks like you're all set but if you have a follow up question let me know

#

winni_connect-onboarding

mystic mirage
#

Well my subaccount still Restricted

lavish wyvern
#

Ah sorry you said "I have figured out" as if it was resolved.

mystic mirage
#

Sure

#

One moment pls

#

Above is the full response

lavish wyvern
#

Okay those are just pictures. Let's focus purely on the code and raw text, developer to developer. If you carefully look at the requirements property, and nothing else, you will see the exact issue.

mystic mirage
#

I'm sorry I didn't get it, so what do I have to do?

#

I don't see anything wrong with the code.

lavish wyvern
#

Can you please share the exact content of the requirements property. Share it as text here, not in a picture. Share only what's in that property and nothing else

mystic mirage
#

requirements: {
alternatives: [],
currently_due: [],
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
},

#

requirements: {
alternatives: [],
current_deadline: null,
currently_due: [],
disabled_reason: 'other',
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
},

#

future_requirements: {
alternatives: [],
currently_due: [],
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
},

#

future_requirements: {
alternatives: [],
current_deadline: 1724259600,
currently_due: [],
disabled_reason: null,
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
},

lavish wyvern
#

please don't dump everything one by one, it's tough to help you if you don't take a step back to think about it

#

Only share requirements and nothing else. So ignore 1, 3, and 4 above. Just focus on #2

In that JSON there are only a few lines. Does anything jump out at you, as a developer, when you read it, that could say "oh it's disabled"?

Please only look at requirements and nothing else

mystic mirage
#

requirements: {
alternatives: [],
current_deadline: null,
currently_due: [],
disabled_reason: 'other',
errors: [],
eventually_due: [],
past_due: [],
pending_verification: []
},

#

So you mean : disabled_reason: 'other',

lavish wyvern
#

yes!

#

So now I know it's cryptic, I'll explain, I'm just teaching you to read the response first

mystic mirage
#

Ok, so what's the meaning of other?

lavish wyvern
mystic mirage
#

I see, but what the other meaning?

lavish wyvern
#

I mean did you carefully read that doc? I'm sorry but you're rushing way too fast

#

Right now your account is rejected/blocked. I don't know why sadly you'll have to ask support https://support.stripe.com/contact. I'm just teaching you how to read the API response and how to navigate our docs to get to a detailed answer

#

You also don't seem to have any Connect WebhookEndpoint to listen to all the account.updated Events to know when an account becomes active or inactive which is also crucial to debug those things, make sure to build that

#

Okay looking internally it seems this account is fine but the problem might be with your own Stripe account (the platform). So yeah next step will be to go work with our support team for 1:1 help: https://support.stripe.com/contact

mystic mirage
lavish wyvern
#

You can go back to them and ask for help. Our support team should never send you to Discord. So the next step is what I just recommended and going back to our support team

mystic mirage
lavish wyvern
#

I don't understand what that question could mean

mystic mirage
#

I would like to know more about Webhook Endpoint.

lavish wyvern
mystic mirage
mystic mirage
lavish wyvern
#

I'm sorry I don't really understand what that could mean either.

mystic mirage
#

Meaning I can read the document but I don't know what to do next? What's in this document doesn't add up to my code.

#

Also regarding this account, I have emailed the support team again.

lavish wyvern
#

Sorry it's tough because you seem totally lost but can't really explain why or what is blocking you. Stripe will make an HTTP request to your server to send the details about what happened. For example for an Event type account.updated you get the whole Account object and what changed.
You, as the developer, write code to handle this request, access the Event data and look at it. That's what is covered in details in our various docs. You might want to start with our "quickstart" for using webhooks: https://docs.stripe.com/webhooks/quickstart

mystic mirage
#

So now we only have to use a webhook?

lavish wyvern
#

I'm so sorry but I don't know how to help you, you ask really vague questions

mystic mirage
#

The webhook part is currently out of my hands, I'll have to ask the rest of my team.

lavish wyvern
#

gotcha, then ignore the webhook for now

mystic mirage
#

Ok

#

So what should I do is just waiting the support email?

lavish wyvern
#

I can help if you have real/concrete questions, developer to developer.

mystic mirage
#

Ok thanks

#

But I can't do the part involving webhooks right now.

lavish wyvern
#

All good, in that case you might want to wait for the support team for next step and I will be able to close this thread!