#b33fb0n3_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/1407754134257668186
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
So I'm clear, these companies have projects that require payments and you're looking for a way to integrate Stripe for the said projects? Or is this about, how they will make payment to you for working on the projects?
yea nearly. I am the developer who need to integrate the stripe API to collect payments from the customers from my client.
Imagine this:
Developer Company (Me + my Team) -> Company (My Client) -> Customer (The Company Customer)
And the company want to collect payments from the Customer. On the customer invoice should be "Company" not "Developer Company". But I am using my secrets to use the "Company" Account to create paymentintents and other stuff that the "Company" requests from me
Your describing the Connect flow, however, it's not clear why you need to do that.
I know how both flows work. I worked multiple times with the connect flow, but I also worked with the "add my account"-Flow.
For me the question is: when should I use which flow and why? Is there some kind of checklist to determine which I should use?
For example: "Use the 'add to account'-Flow in every case when you are doing XYZ "
There's no checklist that I know of that you can reference.
That doesnt help me at all this_is_fine
Just to make sure we didn't lost connection: Are you still there?
Yes, I'm here. You asked for a checklist and I informed you there isn't one. Do you have additional questions?
Yea, my initial question was on how to determine if I should use the "add to account"-flow or the "stripe connect"-flow. The checklist was just an example.
For me a solution is important. Something like "no, we don't have that" does not help. Imagine you are me, what would be a possible solution.
Please focus on solutions, not on what you don't have
Let's take a step back here before things take a wrong turn.
Can you share the docs associated with the "add to account"-flow? So I'm clear what you're attempting to describe.
Sure it's the second link from here: #dev-help message : https://support.stripe.com/questions/invite-team-members-or-developers-to-access-your-stripe-account
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Ok, what you shared is basically user roles [0]. As the name describes, this provides you with access to the account based on the preferences of the client. This is completely different from and unrelated to Stripe Connect [1]. The purpose of connect is to manage and route payments and payouts between sellers, customers, service providers, and other entities. Which based on what you have described so far you do not need to do. There's no documentation that will explain the differences between the two. The question you need to ask yourself is do you need to be a go between for your client's payments. If you do, then maybe Connect may be the solution for you.
[0] https://docs.stripe.com/get-started/account/teams
[1] https://docs.stripe.com/connect/how-connect-works
How do I know if I am between the clients payments? I as the company never collect any money.
Keep in mind the structure that I shared:
*Developer Company (Me + my Team) -> Company (My Client) -> Customer (The Company Customer)
And the company want to collect payments from the Customer. On the customer invoice should be "Company" not "Developer Company". But I am using my secrets to use the "Company" Account to create paymentintents and other stuff that the "Company" requests from me*
If you use the Connect account flow you (Developer Company) will be part of the flow. You can create Direct Charges and the customers will transact directly with the connected account [0]. However, your use case does not really justify using Connect or using your secret API keys.
You'll need to familiarize yourself with both options and determine how best to serve your clients. That's not something we can steer you in any given direction.
Ok, so the question I need to ask myself:
Do I need to use "direct charges":
Yes: Use stripe connect-Flow
No: Use the "Add to Account"-Flow
Correct?
Not necessarily. I would ask myself "why do I need to use "direct charges" or connect in general?" based on what you know about connect and how it works. With Direct Charges, the funds go directly to the connected account and you can collect a portion of the transaction in the form of fees [0]. So you'll need to discuss with the client to determine if they are ok with that approach.
[0] https://docs.stripe.com/connect/direct-charges?platform=web&ui=stripe-hosted#collect-fees
There's also the case of Stripe Fees and who will be responsible [0]
[0] https://docs.stripe.com/connect/direct-charges-fee-payer-behavior
So I would ask myself:
"Do I need to charge my customer based on the transaction":
If yes: Use stripe connect
If no: Use the "add to account"-method
Hi, taking over as my teammate needs to step away. Let me catch up.
It's like:
Stripe Connect: Payment -> Me -> My customer
"Add to Account": Payment -> My customer (and I initiate the payment)
In both cases the customer of my client will never know that I as the developer stripe account exists, correct?
Yes, depending on the charge type your summary is correct.
ah nice, so the question I need to ask myself is correct and this is also correct: #1407754134257668186 message?
Yes!