#riptired_connect-setup
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1256019370367385630
๐ Have more to share? Add details, code, screenshots, videos, etc. below.
@wicked aspen it's hard to say without more details. Is the only new feature you're building to send funds to connected accounts?
Yeah sorry I ran out of characters
Yes, we are growing our clients and some clients have more specific requests around how they are paid out. Additionally we want to pay them out automatically so that we don't have to do any payment calculation and manual payout at the end of each month.
For example for Client A that we work with, they have X subscriptions. They want their payout of the subscription fee to go to 2 bank accounts at the end of the month
What type of connected account are you going to use? There are a lot of ways to use Connect
riptired_connect-setup
What do you mean by connected account?
Yeah sorry there are so many ways to integrate our products so it's tough to try and answer you concisely and quickly
Yeah fair, what information can I give you so that we are on the same page
Usually, the first decisions you make as a platform are
- How do I configure my connected accounts (who owns liability, pricing control, onboarding)
- What flow of funds do I want to model
Ah yeah let me type that out
The flow of funds should generally be from customer > us (the platform) > end of the month > payout to client (include some grace period for payment issues so that if there are chargebacks / etc we can handle before payout to client)
yeah sorry you're missing the point a bit
you're answering what you think about for your business but it's not yet mapped to our entire vocabulary/design for Stripe Connect.
Maybe let's take a step back: are you not already familiar with Stripe Connect and ready to get coding after having made those fundamental choices?
Totally fine if you're not, but that's definitely an important piece of info
I am not super familiar with stripe connect, I have read a couple docs but haven't used it before
I am considering if this is the right option and how much work would be involved to migrate to the type of solution we need from what we are currently doing on stripe
Gotcha. For this, our support team is usually better equipped to have deep 1:1 conversation about you, your overall business model and goals so you might want to approach them instead: https://support.stripe.com/contact
I'm happy to answer code-related questions if you have any but I can't really help you weight the pros and cons of many of the potential solutions without going deep into your own business model, your risk appetite,etc.
But at a high level, assuming you hold all risk/liability for Refunds/Disputes (which seems to be what you do already) you can use Stripe Connect and Destination Charges for your flow.
The idea is that you charge John Doe (cus_123) for $20 and you configure that PaymentIntent to have a "destination account" where part of the funds will be sent (so for example $16 and you keep $4 for your platform to cover our fee and your fee). And then you can configure each connected account to have Payouts happen daily/weekly/monthly for example
Makes sense, appreciate the candor
On the API side however, purely from someone migrating from just using checkout links to stripe connect, is that a significant undertaking to migrate?
Checkout is fully compatible with Stripe Connect so no that part shouldn't be hard. What to change will depend on what "flavour" of Stripe Connect you pick. Assuming you pick the one I laid out above it's as simple as adding transfer_data to your Checkout Session creation to tell us which of your connected account should receive the money
Ah interesting, currently all of the checkout session creation is just done in the dashboard
๐
As in our team just creates a product and a link for that product
Do you create PaymentLinks?
and on the API side I am just subscribed to all of the webhook events for stripe subscriptions
yeah okay. Another crucial bit, product names matter a lot ๐
You can configure a PaymentLink to send a portion of the funds directly to a connected account even in the Dashboard!
Ah yes sorry we do create PaymentLinks
all good, I know it's a lot, especially if most of your experience with Stripe is Dashboard based
Are your PaymentLinks re-usable like you sell a $20 book and anyone can load that link to pay? Or are you creating one-off links for each individual customer and their order/subscription?
We make a Product in the product catalog that is a subscription (charged monthly) for each client. Then we create a re-usable link that anyone can use to purchase that product from that client (we are not creating one-off links). From the API side then we can discern by the product who the subscription is for and then just listen to relevant subscription events
gotcha, so yeah that is still possible with Connect and you can configure who gets the funds
this UI in the Dashboard allows you to configure the funds split
Is it possible to split out to 2 external accounts? (we retain X%, account 1 gets y % and account 2 gets z %?)
And additionally from a migration perspective if I am using the current setup I have, is it possible to migrate the existing clients and subscriptions to stripe connect or I can only use stripe connect for new clients going forward (like what about Bob who is paying a monthly subscription for a product in our catalog currently)
not directly. There are ways but that would require a lot more code where you basically accept the payments and then transfer funds (with code) to 2 separate Stripe accounts (each with their own bank account)
Or if you want just one connected account, then you'd write code to track which portion of the funds goes to which bank account and then you'd create a manual Payout (with code) for the right bank account
and yes migrating is doable
Would I be able to do the payouts with code without migrating to Stripe Connect?
since I would have to use code with Stripe Connect anyways
And then on migrating being doable, what does that mean for the end users paying subscriptions, will they have to re-sign up for a new subscription or is it mostly seamless (they wouldn't know anything had happened
You have to use Stripe Connect for what you are after
And no one needs to re-subscribe, you can update existing Subscription to send the funds to the right/new connected account
okay so in summary, the payout to 2 accounts requires a large lift in code, payout to single accounts is relatively straightforward and supported by Connect, migration of existing subscriptions is seamless, will just need to use API(?) to update subscriptions to send funds to the right account
I would say that's correct yes
okay do you have a link for the docs I would reference for the 2 account payout
other than that, I really appreciate the help
https://stripe.com/docs/connect/charges-transfers would be the flow of funds if you wanted to have 2 separate Stripe accounts receive a portion of the funds
Okay so my main question after reading these docs are can i do a single transfer to a account or multiple accounts at the end of the month that uses the funds from the payments for the month? or if I want to use a source transaction then I would need to do N transfers for N subscription payments
๐ taking over here
๐
You can do multiple transfers to multiple Connected Account, from 1 source Transaction
To be more specific the use case I am thinking about is the client that is using my platform wants to be paid out into 2 accounts and I pay them out at the end of each month
they are selling a subscription which means they could have 1000 clients
so in order to pay them out at the end of the month how does that work? do I need to maintain some balance or how do I pay out their portion of the 1000 subscription fees
Yes so you create a Charge from your customer to you (Platform), then in the end of the month you create 2 Transfers to your client's 2 accounts. The total amount of the transfer need to be <= the amount of the original Charge
so I have to do 1000 transfers if there are 1000 subscriptions?
I imagine 1000 Subscription, you will have 1000 Charges and 2000 respective Transfers. That's 1000 pairs of (1 Charge + 2 Transfers) programmatically
yikes is that the recommended way to do this? I thought I would just be able to send 1 transfer to each account at the end of the month
does that mean in the client's bank they will see 1000 transfers? that seems ridiculous
No the clients will only see 1 transfer of Payout. A monthly Payout aggregate all the transaction they receive in a month
Let's use the term clearly. "Transfer" mean funds move from your Platform Stripe balance to your Connected Account Stripe balance. "Payout" means fund is paid from your Connected Account balance to your Connected Account bank account
Think "Payout" as separated step
ahh I see
okay and all of this has to be setup via the API? especially if I need to pay out to 2 accounts for a single connected account? or can this be setup automatically in Stripe Connect via the dashboard (especially for connected accounts that only have 1 account that payment is sent to)
Yes it will need the API
so to pay out monthly I would need to setup my own system to run end of month and initiate all the transfers
do I need to initiate a payout as well I dont see that in the docs
You can setup Automatic Payout
okay so for the accounts that have a single payment recipient I can setup an automatic schedule, what about for the accounts that have multiple payment recipients
By recipients do you mean Connected Account? You can set Automatic Payout on each of the Connected Account
Yeah, I have 1 case where for 1 product that uses a subscription payment I need to pay out to 2 connected accounts
Yes, so each of that Connected Account can setup their Automatic Payout
You mean I can setup the automatic payout for each of the connected accounts? And also be able to split payment for 1 product to 2 connected accounts?
Yes