#residex_api
hidden cargoBOT
đ 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/1400476597517160579
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- residex_webhooks, 1 day ago, 12 messages
- residex_webhooks, 1 day ago, 8 messages
blazing prism
I was really just hoping you could look and see if something is up with the request more than what the error message is saying because it doesnt make much sense to me? I see Transfers enabled on the connect account. If that is all you can see too then it might be an AWS issue
chilly jasper
Hi, taking a look here
Our connect test docs give a number of test values that can be used to mimic various verification on accounts:
https://docs.stripe.com/connect/testing#identity-verification
Can you use these test data when creating the connected account and try again: https://docs.stripe.com/connect/testing?
blazing prism
So you are saying my test account onboarding information is blocking the payment somehow? How have I been able to make test payments for this same account using Stripe Payment elements? Is that a different thing than trying to automatically confirm a payment with API?
chilly jasper
It should have always been the same. You can look at this event: https://dashboard.stripe.com/test/events/evt_1Rool1DXCj44931gj9wDZLVc to better understand why it was disable: disabled_reason: "requirements.fields_needed"
It could be possible that you might have been using an account that already provided the required fields
blazing prism
That event is not showing up for me.... can you tell me the account ID for the request I gave?
chilly jasper
That is your Connect event on acct_1RookyDXCj44931g