#SHA256Collision
1 messages · Page 1 of 1 (latest)
It should just be all supported countries for Stripe accounts. However, you'll need to keep in mind cross-border transfer restrictions if you aren't using on_behalf_of
See note in yellow at top here: https://stripe.com/docs/connect/destination-charges
Apparently, Brazil is supported Stripe country but with our platform account in Canada, we are getting error when trying to create a custom account with country set to Brazil 🤔
Hello! I'm taking over and catching up...
Can you provide the request ID showing that error? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Thanks Rubeus. Here is request Id req_cID69WRl1m3nWf
Looking...
I'm not sure why you got that error, but the error message indicates Stripe support knows what the issue is. Have you contacted them?
I did contacted them and learnt that custom accounts for Brazil can only be created by platforms in Brazil. And I asked if there were other countries that have might have such limitation and apparently got the response there is no official list at this time. This is why I reached out if anyone in the community knew here if there was a list of supported countries based on origin of platform accounts that we can use to find an alternative route.
It sounds like there's no list, no. That kinda makes sense as laws and regulations are in constant flux around the world. I imagine maintaining a list would be pretty difficult as it would be constantly changing.
Yes understood about the financial regulations constantly changing and it is difficult to maintain such list per Country. We are opening our app world wide and currently have setup of using Custom accounts with separate charges and transfers. To overcome the limitation with country like Brazil, Stripe support recommended to use Standard account and we can extend our setup however we want to have setup in a way that works not just for Brazil but other countries as well that have such limitation.
The only thing I can think to recommend beyond that is hitting the API to see what's possible and what isn't. The API is the ultimate source of truth in cases like this.
That is a good idea Rubeus. Alternatively, we can gracefully handle errors from create custom accounts at runtime to create standard account.