#jack_api
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/1417969930657206353
📝 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.
- jack_api, 10 hours ago, 39 messages
Hi there
Taking a look
Ah because you don't manage external accounts for Express/Standard accounts.
You would only manage the external accounts for Custom Connected Accounts. Otherwise the Connected Account user adds their external accounts via their Dashboard themselves.
Ok interesting. So I could do this if it was a custom account and not an express account?
Yes
Is it possible to enable some kind of “Collect External Accounts for Express via API” capability while still using Express accounts?
No, for Express accounts external accounts can only be collected during the onboarding flow or via the Dashboard
Oh, so it can work if I onboard them with this capability?
When they go through onboarding there is a step in the onboarding flow that asks for their external account.
Oh, so in the onboarding, they will have to add two methods if I do this?
Or can they still use the same method they initially registered with
Sorry not sure what you mean by that?
Overall you shouldn't worry about the external account at all if you are working with Express Accounts
The Connected Account user will input it themselves.
You don't collect it from them.
Ok, so I start this connect account flow to onboard users to connect accounts and add ACH as their payout method
But I want to allow them to use this as a payment method as well
So the way to do this seems to be to create an external account during onboarding. However, now it seems like they will need to input this same bank account again in this flow.
Hi there, I'll be taking over for bismarck here, who needed to step away
Ok thank you @torpid barn !
To be clear, you're trying to collect the same account that they're paying out to as a PaymentMethod so you can charge the connected account directly, is that right?
Yes pretty much, but I understand that Connect accounts do not store payment methods and that I will have to create a customer account for this
Correct - and your question is mostly "can I streamline this during account onboarding"?
Yes pretty much
I would like them not to have to add it again when they want to use it as a payment method
Does that make sense?
Yes - you're using hosted onboarding now, is that right? I don't think you can do that - I think you'll have to recollect payment method details later.
Also wanted to draw your attention to this feature
Also, for when they are updating the payout method on their express account, I would like them to be able to add it as both
Ok, that's a cool feature. However, I feel like this is not as good as adding it as a payment method, correct?
Let's say a seller adds their connect account and then wants to buy many items as a buyer. Would it be fine to use this feature essentially as their payment method?
It seems it is built more for one time things rather than a regularly usable payment method
Well, it isn't automated, if that's what you mean. But the option is between using that feature and recollecting your user's payment method and saving it to a Customer
Ok sounds good. Thank you very much for your help
Ok, one more thing
It looks like we can basically charge connect accounts as if they are customers?
API
The create a charge API call supports providing a connected account ID as the source value:
Command Line
Select a language
Select a language
cURL
curl https://api.stripe.com/v1/charges
-u "sk_test_51PdDW5RoGUGa1FvrjFkiuljppt9HCJkrtoWYRHdbs1D554LRWixYhqzsOboa4uj5uZdweZ73oDHvlxxhEo9vNBKL00QPiyWaUT:"
-d amount=1500
-d currency=usd
-d source={{CONNECTED_ACCOUNT_ID}}
The API call returns the Payment created on the platform account. It doesn’t return a Charge.
This approach is appropriate for platforms that charge their connected accounts for goods and services (that is, for using the platform). For example, a platform can charge its connected accounts for additional fees or services through their Stripe balance, minimizing any need to collect an additional payment method and allowing for nearly instant availability of the funds.
Ahhh through their Stripe balance
Correct