#benbindapp_code
pseudo basinBOT
đ 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/1471306413958627441
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
frail valve
hello! can you share the request ID where you're running into the second error? The request ID has the prefix req_
worthy breach
Yes, give me a minute to trigger the request again.
caade109-ef53-4bc6-a7fa-69d316ba0537
frail valve
The request ID has the prefix req_ , this guide has some suggestions for how to retrieve the request id https://support.stripe.com/questions/finding-the-id-for-an-api-request
worthy breach
req_z2li5qCqNh5Naf
frail valve
you set the requirements collection to Stripe : https://dashboard.stripe.com/acct_1RIuOsLT2sdMtfb9/test/logs/req_Ur5LhrxLJORwHH which is why req_z2li5qCqNh5Naf is throwing that error.
worthy breach
I did try to set the application to requirment collections and I got the following error: When controlling requirement collection, the Connect application must also control losses, fees, and specify a dashboard type of none. request ID: req_S6oW0laV0wRj1m
frail valve
yes, that's exactly what a Custom account does i.e. the platform is responsible for losses and fees, and the Custom account has no Dashboard
worthy breach
Is there no possibility to qualify for stripe managed risk? We had a meeting with a sales contact and they said this would be possible.
frail valve
so to clarify, you want this controller settings :
- controller.fees.payer : application
- controller.losses.payments : stripe
- controller.requirement_collection : ?
- controller.stripe_dashboard : none
what did you want to set for controller.requirement_collection?
worthy breach
fees.payer: account, and requirement_collection: stripe , but if necessary application works as well
We really just want stripe to handle negative liability and for connected accounts to pay fees.
frail valve
ah okay, I understand now
because you are setting requirement_collection: "stripe", Stripe doesn't allow you to disable_stripe_user_authentication
components: {
account_onboarding: {
enabled: "true",
features: {
disable_stripe_user_authentication: "true", // you shouldn't set this to true
external_account_collection: "true",
},
},
},
}
Correct. Would it be possible to disable stripe user authentication at all? We did not want to have a redirect, but it seems that may have to happen in order to have a custom account with stripe managed risk. Is this correct?
frail valve
it's not possible unless you do what the previous error message suggested which doesn't fit the controller settings you want i.e.
set the application to requirment collections and I got the following error: When controlling requirement collection, the Connect application must also control losses, fees, and specify a dashboard type of none.
worthy breach
Okay, just to clarify, if we use a custom account and want to use stripe managed risk, the stripe user authentication redirect is mandatory. Does this also mean if a connceted account uses the payout component they will have to log in on that component as well? Or will it just be the intial sign in on the onboarding component.
I can also test this if you do not know the answer for sure.
Lastly, is the fees payer parameter something that is limiting us to do what we want? Or is it mainly the negative liability