#raimund_docs
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/1275504188473741473
๐ 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.
- raimund_docs, 17 hours ago, 4 messages
- raimund_api, 21 hours ago, 9 messages
This is a follow-up question to the previous docs related one.
So a Transfer just represents the movement of one Stripe account's balance to a different Stripe account's balance. In terms of verbiage a Payout is a transfer of funds from a Stripe account balance to and external bank account.
Not sure if that answers your question though. Feel free to clarify
Notch payments follow a multistep process:
- On the front, someone pays in a big sum.
- This sum gets distributed amongst many different people, we take a small portion for ourselves.
- The people receive several transfers into their Stripe accounts.
- In order for them to actually access their funds, they have to initiate Payouts through our platform.
- In a previous version, the implementation is based on
BalanceAvailableobjects which seem to be tied to connected accounts. - All I want to know is whether this is true or if at the point of payout, the customer can have the whole balance they earned through our platform paid out to a single connected account of their choosing.
(We're using the Java API by the way)
If you platform's balance can sustain the Transfer to the connected account, then the Transfer will go through. It sounds like you're already checking the balance on the Platform account before making the transfer, so it sounds like your headed in the right direction.
Is there a question underneath the question?
The transfers are fine. But this is about a subsequent payout process.
Let me reword it. I probably made it sound too complicated.
So the end recipients (we refer to them as "officials") have already received a number of transfers into their respective Stripe balances.
We now want to offer them the option of performing a Payout of their full balance into any of their Stripe-connected accounts.
Is this possible? Basically my question is if a transfer ends up in a generic Stripe balance or if it's already tied to a connected account.
Our business side seems to have understood that we can do this. But I'm not totally sure how. For example, what happens with that source_type parameter when creating this kind of Payout?
What's the relationship of all the accounts here? It sounds like you're a platform who's creating Transfers to other platforms, who are then creating transfers to connect accounts. Is that correct?
Not other platforms in that sense. People with Stripe accounts.
Sorry, this is all very confusing. What API requests are you making to achieve this? Do you have request IDs for them?
Let me search for some...
Can you try rephrasing with a step-by-step representation of the desired flow of funds? Something like.
- Stripe account A is a platform
- Stripe account B is one of its Stripe Connect accounts
- Stripe account A receives funds to its balance
- Stripe account A transfers fund to Stripe account B
- Stripe account B has an external bank account
- Stripe account B creates a Payout from its account balance to its external bank account
That sounds about right. One transfer from today has the ID tr_1PpsOLBIMZTJKM1cET59f6SE.
That's a pretty common use-case. Can you rephrase your question to fit the above scenario then? Something like, "Can Account B payout the amount transferred to them from Account A?"
At the point of creating the payout, can Account B choose freely which of their external accounts and/or cards will receive the total? And how does the API call look to set that up?
No, it will be one of 2 accounts. Either their default external bank account, or a card (if they have Instant Payouts enabled). Account A can create the Payout for them via this endpoint: https://docs.stripe.com/api/payouts/create
Account A would need to auth themselves as Account B's platform to make the Payout request on their behalf: https://docs.stripe.com/connect/authentication
The Instant Payouts are actually the reason that brought on this whole exercise. Apparently there are external bank accounts that are eligible for Instant payouts which incur a fee.
In any case, when creating the Payout, what do I fill in for the source_type parameter?
If you want to use the Instant Payout card, then specify card if you want to use the external bank account, then specify bank_account.
Mostly you will need to specify a destination if there is more than one external account available for payout: https://docs.stripe.com/api/payouts/create#create_payout-destination
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Does the combination bank account + instant exist? This is what's creating issues with our current implementation.
Yes, some Bank Accounts are "Instant elligible". You would need to pass in the Bank Account ID and include the method: "instant" parameter as mentioned here: https://docs.stripe.com/payouts/instant-payouts#request-an-instant-payout
OK, so this is all possible indeed then. Thanks. We'll try to go ahead with this information. ๐
Sure thing!