#steven-tey_docs
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/1331725368985518132
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, you can do SC&T with any of the countries in the second doc. Both docs are accurrate but are speaking to subtlely different things. That first doc has a blurb that speaks to this a bit and actually links to the second doc
In most scenarios, your platform and any connected account must be in the same region. Attempting to transfer funds across a disallowed border returns an error. For information about cross-region support, see cross-border transfers.
So those 40 countries are ones where this flow can be done within the same region, because we support platform accounts in those countries. The cross-border transfers doc is speaking to all the countries, but that flow requires special configurations like recipient service agreements on all of the connected accounts, and you can't use features likeon_behalf_of
I will raise feedback about that difference being a confusing as is in the docs and am happy to answer further questions, I know that explanation wasn't the clearest either
Thanks for clarifying @glacial pelican! Does that mean that since we're a US platform using separate charges and transfers without the on_behalf_of param + we have recipient service agreements for all non-US connected accounts, we can send payouts to the 118 countries in the first doc?
Yep yep
Recipient service agreement has legal implications, and unfortunately we only know the API side, not the legal side of this. So make sure to double check that it make sense for your business case. Our support team may be able to provide some guidance on this but at a point they may suggest you ask your own legal experts