#theplay3r_best-practices
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/1430105189108678686
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
I am try to implement stripe business account using custom connect account and I know the required fields but I am stuck in verification part how we verify user business which documents I need to verify depend upon the company structure
hey there! there shouldn't be any issue with making 20 transfers per second, from a technical perspective, depending on the exact calls you make to our API
our standard API rate limit is 100 requests-per-second
for your second question, as you mentioned, this depends on things like the company structure, country, etc
this page contains a breakdown of the different required information for different configurations: https://docs.stripe.com/connect/required-verification-information
Yeah, I'm mainly concerned about how much I should go near this limit, because there is always a chance some other operation(s) might be taking place, that could also play role in the rate limiting. I guess I will bump it up to 30 and call it a safe-spot. 70 other requests should be more than enough "free space".
No idea who @somber mesa is, the guy probably got a bit lost here. ๐
that sounds good! I'd also recommend considering a retry schedule for your requests to handle rate limits gracefully: https://docs.stripe.com/rate-limits#handling-limiting-gracefully