#gearoid_api

1 messages ¡ Page 1 of 1 (latest)

normal willowBOT
#

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

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

gilded quest
#

Asking a colleague. Will get back to you

tawny gazelle
#

great thanks

#

This is the code in the docs for reference

gilded quest
#

Can you link the doc you're looking at

#

Where you set:

      type: "none",
    },```
#

So you can't use account links

gilded quest
#

Got it thanks

#

I'll let the team know they need to update that

tawny gazelle
#

Ok

#

can you help provide guidance then? Out current setup is account type: 'custom'

#

but need to have controller.losses.payments: 'stripe'

#

is this possible without having stripe_dashboard.type: 'full'

gilded quest
#

Yep

#

The issue is you have bothj:

controller.requirement_collection = stripe```
#

You don't explicitly specify requirement_collection in your code

#

So you'd have to set it to application if you want to maintain dashboard type as none

tawny gazelle
#

ahh ok

#

I have not specified requirement_collection in the accounts.create

#

is stripe the default?

gilded quest
#

Yeah I said that above

tawny gazelle
#

sorry sorry

gilded quest
#

no worries

tawny gazelle
#

Ahh yes, now i remember how i got here

#

when specifying controller.requirement_collection = application i get this error "When controlling requirement collection, the Connect application must also control losses, fees, and specify a dashboard type of none."

#

My controller config for reference

gilded quest
#

Ah ok

tawny gazelle
#
      fees: { payer: 'application' },
      losses: { payments: 'stripe' },
      stripe_dashboard: { type: 'none' },
      requirement_collection: 'application',
    }
gilded quest
#

Yep yep

#

"When controlling requirement collection, the Connect application must also control losses, fees, and specify a dashboard type of none." is accurate

#

So if you need losses to be stripe, dashboard to be none, and requirement_collection to be stripe you just can't use account links

tawny gazelle
#

Will api-onboarding work with requirement_collection = stripe ?

gilded quest
#

I think so, but not sure offhand

tawny gazelle
#

Ok thanks. I was wrong with the assumption then that requirement_collection = stripe only allows for a "Stripe-hosted onboarding" then?

gilded quest
#

Correct

tawny gazelle
#

Ok that is confusing. I will try embedded or api onboarding

#

Thanks for your help this far