b33fb0n3_best-practices

[lone grove]

👋 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/1374024793044815883

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[tough storm]

Hi 👋 that's largely dependent on which is a better fit for your use case.

Do you need Stripe Connect for your business use-case? (in which case standing up a Connect integration for testing makes sense)

Or are you building a single-account integration? (in which case getting access to the single account you're going to use probably makes more sense)

[hoary hedge]

Hmm in this case it’s a product only for a single customer. However in the future I may want to collect fee's from their payments

[tough storm]

If you don't need Stripe Connect, and don't plan to use it in your integration (it's designed for use when funds from payments need to be split between entities) then I wouldn't suggest using it.

[hoary hedge]

Then you would rather be added to the team and then if I need to charge them in the future based on their income, then create a seperate transaction?

Can I access their dashboard like that as well? The workbench is pretty helpful

[tough storm]

and then if I need to charge them in the future based on their income, then create a seperate transaction?
Can you elaborate on this? Like if you are building a Platform where you process payments for a client with the intention of taking a fee for each payment, that's funds from payments going to multiple parties and may warrant using Connect.

[hoary hedge]

yea, for now I dont want to charge them anything. But in the future I may want to charge on every payment they make or in a lump sum or similar. Like to somehow have control over that

[tough storm]

Those are two very different integrations.

[hoary hedge]

Yea, I assume those two integrations exists:

1. Add to team and handle everything with that
2. Onboad the customer with connect and handle it via connect

[tough storm]

I'm not referring to getting access to a given Stripe account. I don't think that is how you should be focusing on this.

I think you should be focusing on understanding what within Stripe you need to use to satisfy the business requirements that you/your client are trying to satisfy. That will dictate how you should build your proof-of-concept, and therefore dictates whether you should use Connect as part of that.

You shouldn't use Connect just to get access to a Stripe account. If your client wants you to use their Stripe account, they should give you the necessary access for what they're asking you to do.

If they're asking you to just build an integration that they can plug their API keys into, you may not need access to their Stripe account at all.

[hoary hedge]

In my case my job is to implement stripe into their website and collect payments from their customers when they buy something.

I just want to plan in the future. For example when I focus now on "adding to the team" and they add me there and I integrate everything and everything works and in the future we talk about that and I tell them that I will charge them for each transaction X% of the income, then I dont want to rebuild everything just to use connect to then use application_fees

[tough storm]

It sounds to me like you don't have a clear grasp of what needs to be built yet, so it's hard for me to recommend what Stripe products/features you should use.

Like if you're hired to build a new Stripe integration for a client, and there is no plan for you to create a Platform that takes a portion of each of those sales, then there is no need to use Connect, and you should avoid the complexities that come with it.

If you're considering keeping a portion of those sales in the future, then you're considering pivoting to a drastically different Stripe integration in the future where there are multiple entities involved in every transaction. That will require Connect, and you will want to design your flows with that in mind, since you'll want to decide early what kind of Charge flow to use with Connect, and what settings you want to use for your Connected Accounts.

[hoary hedge]

hm ok, makes sense. Then I gonna focus on not using connect as its more complex and not required for now. Thanks!