#PSN-account
copper locust
@wary lintel hi! can you clarify exactly what you're doing when getting this error? Code/screenshots/request ID req_xxx if it's an API call, would be useful.
wary lintel
acct_1KH6G5R8LSgBu4zX
Here is the account id
I followed account link url to create a connect account
copper locust
fair enough
wary lintel
Connect account user boarding
copper locust
I'd suggest asking the user for their country upfront and then passing country in the API request that creates the account, especially if you expect to have IN users
wary lintel
But there is a drop down field which asks for registered business country
copper locust
basically what happens is the account is created by default in the country of your platform(US) if you don't specify one in the API call. Usually the user can pick their country in the onboarding and we change it
but it doesn't work for India
wary lintel
Oh ok
Makes sense
But strange thing is it works for other countries like Italy for example
copper locust
yep I know. Doesn't work for India, because of complications with data locality https://economictimes.indiatimes.com/tech/technology/stripe-migrates-servers-hosting-data-of-indian-customers-to-comply-with-local-laws/articleshow/81708701.cms?from=mdr
wary lintel
Ah got it
copper locust
really it's a bug and we should handle it better but realistically the best option for you is to just ask the customer for the country upfront and pass it in the API call, especially if you are going to expect to have IN accounts
copper locust
note also that there are several restrictions on Connect if you're a platform outside of India with Indian accounts, see https://support.stripe.com/questions/stripe-india-support-for-marketplaces
wary lintel
Ok
One more thing
stripe.Account.create(
type = "standard",
country = "IN",
)
This takes a lot of time,
If country is US it’s much faster.
copper locust
yep, the API latency is higher when working with IN accounts, indeed.
data locality as mentioned above
copper locust
basically it involves some syncing of data between locations within IN and outside-of-IN in our backend servers. I can't really get into specific detail but it is normal to see higher API latency on requests interacting with IN accounts for now, but it's something we are working to reduce as much as possible
wary lintel
Got it. Thanks