#colonelcool_unexpected
sinful scarabBOT
👋 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/1377424833482199162
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rose pewter
Hi! Can you share more details on this, like related IDs from the Stripe Dashboard?
Also, can you share the code you're using to create the Onboarding component?
chilly turret
specifically this step is confusing to me. The account is eligible to be paid out, no further information is needed (other than a SSN if volume is > 750000, but I don't expect to ever hit that kind of volume)
<div className="mt-8 bg-white rounded-2xl p-8 shadow-lg max-h-[500px] overflow-y-auto">
<h3 className="font-bold text-lg mb-4 text-center">Payout Account Setup</h3>
<p className="text-sm text-gray-600 mb-4 text-center">
Complete your payout account setup to receive Superconnector payouts through Stripe.
</p>
<ConnectAccountOnboarding
onExit={() => {
console.log('Exited onboarding');
}}
/>
</div>
</ConnectComponentsProvider>```one sec let me grab the ID
acct_1RJeQtI2Q39WMLqy
although it's not unique to any one account
rose pewter
If you scroll down, do you see the "Confirm" button?
chilly turret
yes
rose pewter
Unless they've clicked that, they haven't "Confirm"ed, right?
chilly turret
but then once I click confirm, if I navigate away and back to the page, it prompts for another confirmation
rose pewter
Why are you re-creating the onboarding form in that case?
chilly turret
I was hoping that the component would be able to tell that a user has previously confirmed and inform them as such
should I be looking for a property on the account to know not to render the onboarding component?
rose pewter
https://docs.stripe.com/connect/handling-api-verification#determine-if-verification-is-needed is what you need there.
chilly turret
basically I have this page where all the stripe components live - the onboarding and the payouts so far. If a user hasn't ever entered their information, I need to prompt them to onboard. But if a user has already onboarded, really all they need to see is the payouts component. I was hoping the component would have some messaging that handles that, but maybe I need to check the account to see if payouts are enabled and then conditionally render the onboarding component?
rose pewter
Ya, that's probably the right approach in this case. The embedded Connect components like little 'windows' into their Stripe account, and if a window is there, it'll show what's on the other side - so in this case, only show the window when they need to access what's behind it.
chilly turret
So probably somewhere in my api, when I’m getting the client secret for the components, I should find a place to check the account status and decide whether to render the onboarding at all?
rose pewter
The simplest solution here is is likely to have some kind of boolean flag on your 'user' object that represents a Connected Account, that is, say, false when either charges_enabled or payouts_enabled is false, and since you presumably retrieve the 'user' for your React app, if that flag is false, you render this component.
...And then have a webhook that listens for the account.update event and just updates your 'user' flag based on the values in the webhook.
I,e., ya. 🙂