#browning_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/1290541289061744706
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi! As each account has its own API keys, you can use them to create products for each Stripe account that belongs to one of the countries. You can then use the same API key to create a subscription for a customer in that country.
For example, you can use the API key for the US account to create products for US and then use the same API key to create a subscription with that product for your US customers.
I understand
Our application needs to use both accounts (depending on the customer)
How can we switch between accounts easily when using the sdks?
This will still need to be done via the API keys on your end. When creating subscriptions for UK customers, you will need to use the UK API key.
OK, thank you!
Is there any advantage to linking the accounts together using Stripe connect for this use case?
There is no advantage to using Connect if you are processing only for these 2 US and UK accounts. But if you are processing for other accounts then it meets Connect's use case.