#lozzy.
1 messages ยท Page 1 of 1 (latest)
hi! not sure what you mean โ that is a parameter on the PaymentIntent API already.
Apologies, a connect account is the only account that can use this parameter, is this correct?
no, the platform is the one making the API call, you pass the ID of the connected account in that parameter.
look at https://stripe.com/docs/connect/destination-charges for examples.
But if someone has a platform account and have lets say 3 connected accounts... they can only transfer the funds between the 3 connected accounts correct?
if you're using Destination Charges (transfer_data.destination) then you can only split the payment to one connected account
if you want to split to more than 1, you'd need to create the Transfers seprately, using https://stripe.com/docs/connect/separate-charges-and-transfers .
see also the docs for Connect : https://stripe.com/docs/connect/charges
Okay Destination charges = transferring to one connected account in a single call
separate charges and transfers = transferring to more than one connected account in a single call?
๐ taking over for my colleague. Let me catch up.
Okay
Destination charges = transferring to one connected account in a single call
correct
No if a customer already has a platform account and connected accounts, we cannot onboard them onto our platform account can we?
separate charges and transfers = transferring to more than one connected account in a single call?
no you have to create multiple calls
1 for the charge (e.g. Payment Intent, Invoice, etc.)
x for the number of transfers you need to make
that's a different subject
Okay
We have a customer that have express connected accounts, payments are processed through their platform account and then transferred to the relevant connected account by passing the destination parameter. This would be an issue as we onboard our customers with our own platform account?
The link you shared above the way we onboard customers to our platform account.
I'm not following
you want to onboard the other platform or their connected accounts?
I assume it is not possible to onboard another platform account. However, would it be possible for us to onboard their connected accounts?
I assume it is not possible to onboard another platform account
you can and I shared the link for that
as for the connected accounts you need to onboard them from scratch
create new accounts and onboard
Really? We had this issue before where we could not onboard another platform account, so we had to get them to make a generic account and connect to us like that.
this is the better approach
so what you did was good
but that doesn't mean it's not possible
it's just not recommended
Okay and if we do this, will it look something like this?
Where the customer can carry on taking payments through their platform account and distribute it to their connected accounts?
no
you wouldn't have access to the connected accounts below
you would only have access to the platform account
Yes but would the customer be able to have access to their connected accounts since they take payments through their platform account?
the Connect link is a one layer link and it's not broken if the platform is connected to other platforms
so your platform has access to the customer platform account but not to the customer connected accounts
and the customer platform account retains its relationship with the customer connected accounts
Okay so the image I provided is possible, where the customer's platform account can be onboarded onto our platform account. The customer can still make payments and distribute them to their connected accounts.
However, this method is not recommended.
Is this correct?
yes that's correct
Thank you very much. Appreciate the help!
let me know if you need any more help
Will do thanks!