#bread_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1240391446574665808
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Do you have a request ID for the error you are seeing?
However, if you are using an Express Account you don't set any of those controller parameters
So you likely just want to omit that
We aren't using an express account, and it seems that you can't use an express account with treasury
the correlationId is null
This is all being done in the test mode
Not sure what a coorelationId is? Can you share a requset ID like: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Found it! req_CksEkx2kGJsBay
Thanks!
Looking
Looks like the error message wasn't updated for the newer Unified Accounts set up
My colleague is working on figuring out the right path forward
Thank you!
Hi there ๐ I'm helping look into this! This isn't something I'm super familiar with, so sorry if I stumble a bit here.
I was able to see the same error that you were seeing initially, and think that is something our teams need to look into and adjust the verbiage of. My suspicion is that this is related to one of the other values being used in the controller hash. If you set the controller hash to match what we have shown in the guide to start, does the error subside? and/or do you see a different error?