michelin_api

[median igloo]

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

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

[nimble barn]

Hi Stripe Support Team,

I’m currently structuring a B2B2C system on the Bubble platform and integrating it with Stripe’s API to create connected sub-accounts. However, I’ve run into issues with the final steps for verification and account activation. I’m hoping you can help clarify what might be going wrong.

Context and Current Flow:

Account Creation:
Within my system, I initiate the connected account creation process by sending basic information, such as the email, to the Stripe API. The account is successfully created, generating a unique id in the format acct_xxxx. This part seems to be working as expected.

External Account Completion:
After the initial setup, I redirect clients to the Stripe setup page, where they complete their account information for verification. However, once they finish this process and I check back on the Stripe dashboard, these accounts are marked with a “Restricted Account” status, indicating they need further review.

Verification Challenges:
I’ve followed the recommended steps for test account configuration, using birthdates and other test details provided in Stripe's documentation. Despite filling in all necessary fields, the accounts still appear as restricted and pending review after creation.

I’m looking for guidance on whether there are any specific setup requirements for connected accounts that might have been overlooked. Additionally, I’d appreciate confirmation on best practices for filling out the mandatory fields to ensure these accounts aren’t created with restricted status.

Thank you in advance for your help, and please feel free to reach out if any additional information is needed.

Best regards,
Cristian

[fast rampart]

Hi 👋 are these testmode accounts that you're creating? If so you can use our test values shown on this page to cause/avoid certain onboarding situations:
https://docs.stripe.com/connect/testing

Do you have the ID of a Connected Account that isn't onboarding successfully that you can share? (should have an acct_ prefix)

What are you seeing in the requirements hash for an Account like that?

[nimble barn]

Thanks for your response! Yes, I am creating these accounts in test mode. However, I have already tried various test values as suggested in your documentation without success.

Could you please assist by testing the connected account ID that I’ve created? I would appreciate your help in verifying if the onboarding process works correctly on your end.

Thank you!

Best,
Cristian

[fast rampart]

No, I can't test Connected Accounts for you, but I can try to take a closer look at what is going on if you can share the ID of one of those Account objects.

[nimble barn]

Thank you for your reply! I understand that you can't test the Connected Accounts for me, but I would appreciate it if you could take a closer look at the issue.

Could you please visit this link and use the ID of one of the Account objects I created? Once you create the account link, it should show whether it’s restricted or not on my end.

Thank you for your assistance!

Best,
Cristian

[fast rampart]

Can you just share the ID of an Account that got stuck here?

[fast rampart]

The Account ID will have an acct_ prefix, please paste it here.

[nimble barn]

acct_1Q8nA101TshhjlBL

[fast rampart]

Earlier you said:

After the initial setup, I redirect clients to the Stripe setup page,

Is the "Stripe setup page" you're referring to our hosted onboarding flow that you direct the Account owner to via an Account Link? I'm asking because I don't see any evidence that an Account Link was generated for the Account that you shared.

In the request you made to create the Account:
https://dashboard.stripe.com/test/logs/req_rrO7F2gWhQNSLk
the response includes the requirements hash showing the missing details, and I don't see any futher updates made to the account after it was created.

[nimble barn]

step 1 - input email:

after click in "conectar stripe":

step 1

step 2: save the id in database

Step 3- generate link

Step 4- open an extenal link

in progress:

after click this site is opened

[fast rampart]

For the Account ID you shared before, it doesn't look like the onboarding form was completed. I can see you generated the Account Link here (sorry for overlooking that before):
https://dashboard.stripe.com/test/logs/req_YnjsDwBE0pSAjH

but I don't see any account.updated Events generated to indicate you provided details in the onboarding flow.

[nimble barn]

this account is created correct?

but this account is restricted....

[nimble barn]

i dont understand this

[fast rampart]

Based on what I'm seeing, you created an Account Link, but didn't use it to provide any information for the Connected Account.

Are you accessing the Account Link URL in the same browser window where you're logged into the Stripe dashboard as your Platform account?

It's really hard for me to tell what is going on from screenshots alone. Account IDs, as well as what you see when you retrieve the Account object from the API would greatly help me in understanding the state of these Account objects.

[nimble barn]

ok

no, my account dashboard is in Brave
my site is oppen in a chorme

https://bubble.io/plugin_editor?id=1491714407143x279212378954661900&tab=tabs-5

check this

[fast rampart]

I don't know bubble, I don't know what you want me to get from that.

[nimble barn]

}?

[fast rampart]

And it throws an error when I try to access it

Saying multi editing isn't supported

[nimble barn]

click in button blue

or esc

[fast rampart]

Sorry, we aren't familiar with Bubble.io. I don't know what I'm looking at here

[nimble barn]

Okay, but I'm following the logic.

I create an acc_ for the owner of a gym, then I create the link. After the link, he registers on the Stripe panel but the data remains restricted.

[atomic vortex]

👋 We're closing Discord for the week end. I can try to answer one question if you have a clear need about our API and the exact relevant code. We can't speak to Bubble's UI or their own implementation, we don't know hiw it works.

So what exactly is the issue? What does "the data remains restricted" means exactly?

My read of the thread is: you're a Connect platform, you are onboarding connected accounts so you create an Account in the API, then you create an AccountLink, you go to our hosted onboarding flow to provide the relevant information and then you are stuck.
is that correct @nimble barn ?

[nimble barn]

Hi koopajah

Thank you for your response.

I followed all the necessary steps to create a Stripe account, specifically an individual account. I provided the country code, currency code, email, IP address, and other required information, which returned the account ID (acc).

After that, I generated the account link to redirect the user to the Stripe onboarding process. The user successfully entered their information in the Stripe interface. However, upon completing the onboarding process, the account remains restricted.

Could you help me understand why the account is still restricted and what further steps I need to take to resolve this issue?

that's it, more or less. I do the whole system without any errors, sending it to the creation panel, but when I finish the account, it goes into restricted mode.

[atomic vortex]

Okay so you're the developer here and the best way to know what the issue is would be to call the Retrieve Account API https://docs.stripe.com/api/accounts/retrieve and then look at the requirements property which should explain exactly what the issue is.
Can you make that call and look at the response to understand exactly what the issue is?

[nimble barn]

this panel stripe creator

[nimble barn]

yes

Im create a new workflow

add this retrive an account

[atomic vortex]

Sure, I just need you to look at the response. We don't use Bubble. Honestly you'd be better off writing real code end to end locally on your computer to understand the APIs instead of using Bubble for any of this

I have to run in a couple minutes so make sure to test this quickly. You should only need one step: retrieve an existing account

@nimble barn going to close in 2 minutes sorry. Please respond now so I can help you with that last question

[nimble barn]

1 minute

im saving raw text

I receive a erros...
Stripe.js error: this header value for Authorization is not correct null

[atomic vortex]

it means you didn't pass an API key properly. Also that call should be done server-side with your Secret API key and not using Stripe.js at all

[nimble barn]

ok

1 minute

[atomic vortex]

sorry you keep copy-pasting pictures all the time. All those seems fairly clear about the problems

[nimble barn]

??

[atomic vortex]

that error looks super clear to me. You are trying to retrieve an account that is not connected to your platform

so you likely mixed up either your API keys or the account id

But okay at this point I'll just explain at a high level
To process payments an account needs to provide a certain number of information. This is required by law/for compliance rules. What do provide depends on many factors (country, business type, etc.). We document this in details here: https://docs.stripe.com/connect/required-verification-information

As a Connect platform, you have to keep track of the state of each connected account, which ones are enabled for payments or Payouts, which ones aren't, which ones will need additional information, etc.
This is done by looking at the Account resource in the API and then checking the requirements property. This will cover in details what is needed for this account both now and in the future.
I recommend reading carefully https://docs.stripe.com/connect/handling-api-verification which covers in details how those requirements work.

So really as the developer here you need to carefully look at that information to self-serve what's missing and then provide that information likely by going through hosted onboarding again.

Sorry but it's 40 minutes past our usual closing time so I need to close this thread. If you have follow up questions you can reach out to our support team: https://support.stripe.com/contact for 1:1 help
Also note that Bubble is a third-party that we know nothing about. I advised earlier that you should be trying a lot of those calls locally on your own machine by writing real code. It doesn't mean you can't use Bubble for your production website, but it clearly causes a lot of confusion for you where you're not clear which part is due to Bubble versus the API.
I also deleted you recent message as you leaked your Secret API key which should never be shared.