#liam_best-practices

1 messages · Page 1 of 1 (latest)

stuck shaleBOT
#

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

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

trail holly
#

Hello, happy to help. Stripe Connect is our product for users that want to build their own platform, split payments, and pay others out https://docs.stripe.com/connect

wild tartan
#

We currently use Stripe checkout for taking SaaS payments from users. Would implementing Stripe connect require us to refactor our SaaS payments away from checkout?

#

Or can we run both separately.

SaaS incoming payments - checkout
Payments incoming from users for Creator products and then paid out to creators - connect

#

All within the same Stripe account

trail holly
#

You can do that all from one account if you want. We support an account taking payments for itself while also being a connect platform. So you can keep making the Checkout payments as is while also splitting other payments with connected accounts

stuck shaleBOT
trail holly
#

Handling both of those kinds of payments on one account may get complicated depending on exactly how you do things, otherwise I am not thinking of any caveats for doing that

wild tartan
#

Could you link me to the API version of these docs? We'd be looking to implement these within our platform so users can self-serve and set this up themselves

https://docs.stripe.com/connect/collect-then-transfer-guide?platform=no-code

User flow:

  • Creator creates something on our platform
  • Creator registers their payment details somewhere on our platform UI (this connects to Stripe and creates the connected account)
  • Creator enables their product and sets a price, product is added on the backend in Stripe
  • This generates payment link with URL they can share
lyric plank
#

👋 stepping in for my teammate, give me a few minutes to catch up

#

Just so I'm clear, are you using destination charges?

wild tartan
#

Thanks for the link!

We're not using anything yet - still scoping this feature out.

lyric plank
#

Ah, gotcha

#

So, to be clear, has your team started creating connected accounts yet or is this still being scoped as well?

wild tartan
#

Stil being scoped - my initial question was how to implement this feature and your colleague suggested connect.

We use Checkout to process our SaaS fees and I also wanted to make sure it was possible to run this separately

SaaS incoming payments - checkout
Payments incoming from users for Creator products and then paid out to creators - connect

All within the same Stripe account

#

And your colleague indicated that that would be fine

lyric plank
#

Got it, yep, that would be fine.

#

Depending on the charge type you choose and how you create connected accounts, the way you create PaymentLinks or Checkout Sessions will vary

wild tartan
#

Awesome - thanks so much for your help. Are there any other potential footguns I should keep in mind or best practices while we implement this?

lyric plank
#

In the world of account types, you should use direct charges when working with "standard" accounts, and use either destination or separate charges & transfers when working with "express" or "custom" accounts.

#

You can still work with these account types if you don't need to customize granular controller settings though

wild tartan
#

Thanks for your help today