#seth_recipient-grandparent
errant hearthBOT
👋 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/1497017563299971212
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- seth_python-upgrade, 3 days ago, 12 messages
- seth_ubb-migration, 3 days ago, 7 messages
analog bloom
seth_recipient-grandparent
@pine nimbus My understanding is that what you are trying to do is not supported. We don't support creating a v2 Account of type recipient on one of your connected account
pine nimbus
oh, I wasn't aware of that.
So there isn't a way to use global payouts on behalf of a connected account in that case?
These docs seem to indicate otherwise: https://docs.stripe.com/connect/accounts-v2?lang=curl#represent-connected-accounts-using-accounts-v2
But I might be misunderstanding
Ok, I now see those docs are talking about a "connected account", not the same kind of account that receives a global payout. Still wondering if there is a way to do global payouts via connect, will continue researching
analog bloom
that is not possible/supported
pine nimbus
Ok, maybe I am going about this all wrong with connect. It seems like a common use case to me. If I explain what I'm trying to do could you suggest a workflow?
errant hearthBOT
analog bloom
Maybe, @fluid elbow is taking over and can likely guide you
fluid elbow
Hey! sure thing, let me know what you are trying to achieve and ill try to guide you along
pine nimbus
Great!
My platform has users sign up (we'll call them stores) and those stores need to send payments from their bank or stripe balance to their end-customers. This sending of money needs to be initiated from my platform.
My platform never touches the money, it's accepted via stripe terminals and then deposited to the store's bank account, and then I want them to be able to send it to their end customers
fluid elbow
Hmm, sounds like what you want eventually is:
- Payouts to be initiated by the platform account
- These payouts to first go to the Connected Account and then to their end-customers, all the actions to be controlled by the Platform accounts
Unfortunately we don't support this, currently, you can either do:
- Global Payouts:
- Your platform creates recipients (the stores' end-customers, not Connected accounts) and sends OutboundPayments from the platform's account.
- The stores don't send the money themselves, your platform acts as the single sender.
Or
- Connected Account payouts where:
- Funds go: Platform → Connected account's balance.
- The stores (connected accounts) control the last step of paying the end-customers
pine nimbus
Ok, so either way my platform would have to hold the funds at some point
fluid elbow
For option 1 yes, for option 2 no, the money will eventually flow to the Connected Account's balance