#dan_unexpected

1 messages ¡ Page 1 of 1 (latest)

thorny kilnBOT
#

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

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

winter epoch
#

I am working on YardPark btw. I can send you the parent account id if needed

vagrant nymph
winter epoch
#

That's right, but I think my settings say No yet it requires a bank account.

#

I can send screenshots

#

Sorry for the shitty pics but yeah, is this a bug or a missconfig on my end?

WhatsApp_Image_2025-03-27_at_16.52.01_1ddafad4.jpg WhatsApp_Image_2025-03-27_at_16.52.01_78027214.jpg
vagrant nymph
#

I would check to see if the setting is on "no" in both live mode and test mode versions of the dashboard settings page if you are using test mode. Otherwise, I'm not sure.

We focus on API and integration issues in this server and aren't deeply familiar with the dashboard and onboarding flows/requirements. I'd recommend reaching out to our colleagues at https://support.stripe.com/

winter epoch
#

This is in prod / live mode

#

I guess my next question is, could this have to do to the API call I'm making when creating the express account?

vagrant nymph
winter epoch
#

And yes, the account is then linked via another API call and the host is re-directed to Stripe to complete onboarding

# 
// then create a Account Link with that account's ID
    const link = await stripe.accountLinks.create({
        account: account.id,
        refresh_url: `${process.env.NEXT_PUBLIC_FRONTEND_BASE_URL}/stripe-payments`,    // TODO: this page should try to fix the link-ing
        return_url: `${process.env.NEXT_PUBLIC_FRONTEND_BASE_URL}/stripe-payments?refresh_token=true&refresh_count=0`,    // TODO: this page should try to fix the link-ing
        type: 'account_onboarding',
        collect: 'eventually_due',
    })
vagrant nymph
#

Do you have a recently created account to hand? Maybe the one you are testing the onboarding flow on?

winter epoch
#

For sure, 1 sec let me dig it

vagrant nymph
#

great, thanks

winter epoch
#

Could it be maybe the transfer.requested = true?
I do want folks who enter their bank account to get transfers automatically enabled so they can cash out but also not have it as a requirement so they don't get worried I'm trying to steal their info

thorny kilnBOT
vagrant nymph
#

I don't think so - we pretty explicitly give you an option to not collect a bank account

next linden
#

Hi hi! I’m going to be taking over for my colleague here.

#

On that part of the Dashboard, the second sentence says:

Connected accounts will still be required to add an external account to receive payouts.

...So I'd expect they'd still have to add a bank account for payouts.

#

Also 'transfers' are not 'payouts'.

#

I do want folks who enter their bank account to get transfers automatically enabled so they can cash out

More specifically, the 'transfers' capability is not related to payouts, it's something different.

winter epoch
#

Hmm I see so is there a way to allow but not require "payouts" when I make the API calls?

next linden
#

What does that mean to you?

#

And why would you want that?