#deathpote-qs

1 messages · Page 1 of 1 (latest)

eternal halo
#

👋 happy to help

remote fox
#

👋 hi Tarzan, thanks !

eternal halo
#

sorry I haven't got the time yet to respond

remote fox
#

no worries

errant dawn
#

  • not needed but it would help with currency conversion since the currencies you can settle in and add bank accounts denominated in depends on the country your Stripe account is in. You need a legal entity in that country to create a Stripe account there. https://stripe.com/docs/payouts#supported-accounts-and-settlement-currencies

  • depends on the relationship between the entities really. You can use Standard Connect with OAuth to connect your accounts together and have one as a master 'platform' that makes the requests across all them, that's a really common set up for our larger users

remote fox
#

Thanks for your reply.

not needed but it would help with currency conversion

So if I understand it correctly, it's easier and/or less costly only for currency conversions. We should then think in "currencies" instead of "countries" : it's easier to create new accounts to handle other currencies, but not required if we stay in the same currency (i.e if we export our activity from € to $, we should create a new US-based account. If we export from € to €, we should use our french account)

depends on the relationship between the entities really

Can you expand a bit on this subject ? We use Stripe Customer, PaymentMethod, Subscription, Product, Price, Invoice and Charge at the moment.

errant dawn
#

I mean the business entities

remote fox
#

If we migrate to a Connect integration, can we still for example use only one Stripe api key, and reach Stripe objects via their Stripe ID only ? Or should we store and use their respective Stripe Account id ?

errant dawn
#

like do you want to have a "Cookie Company France" and a Cookie Company Germany" and a "Cookie Company Spain" and centrally administer them from the French account as a platform(so only needing their API keys)

#

overall though stuff like Customers/PaymentMethods/Subscription is all account-specific and not shared at any other level

errant dawn
remote fox
#

Thanks I'll take a look to the Connect doc.

I'll see with my boss what will be the plan for legal entities.
To sum up, please correct me if I'm wrong :
If we have only one legal entity exporting to different countries => we should use only 1 Stripe account
If we have multiple legal enitties into each country => we should migrate to Connect and create 1 Stripe account by entity

errant dawn
#

I wouldn't really say "should", it's up to you and these are just some of the options. This is not a topic I'm an expert in as it's generally something our larger users who have sales relationships do, and my team mainly works with a different cohort

remote fox
#

yes I used "should" as "recommanded way" but if I understand it right, we could use in both situations either one Stripe account or multiples accounts through a Stripe Connect integration

errant dawn
#

using Connect makes it a bit easier to do reporting and have explicit connections between the accounts and so on, so it's common to do in this sort of set up

#

I'd suggest talking to our support/sales teams at https://support.stripe.com/?contact=true instead as this channel is mostly for specific technical and API questions and this is a bit out of scope for what we know about

remote fox
#

Thanks, yes. I'll take a look into the connect documentation if they recommend to use multiple Stripe accounts.