#lozzy.

1 messages ยท Page 1 of 1 (latest)

indigo orbitBOT
glacial bough
#

hi! not sure what you mean โ€” that is a parameter on the PaymentIntent API already.

distant oyster
#

Apologies, a connect account is the only account that can use this parameter, is this correct?

glacial bough
#

no, the platform is the one making the API call, you pass the ID of the connected account in that parameter.

distant oyster
#

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?

glacial bough
#

if you're using Destination Charges (transfer_data.destination) then you can only split the payment to one connected account

indigo orbitBOT
glacial bough
distant oyster
#

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?

loud osprey
#

๐Ÿ‘‹ taking over for my colleague. Let me catch up.

distant oyster
#

Okay

loud osprey
#

Destination charges = transferring to one connected account in a single call
correct

distant oyster
#

No if a customer already has a platform account and connected accounts, we cannot onboard them onto our platform account can we?

loud osprey
#

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

loud osprey
distant oyster
#

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.

loud osprey
#

I'm not following

#

you want to onboard the other platform or their connected accounts?

distant oyster
#

I assume it is not possible to onboard another platform account. However, would it be possible for us to onboard their connected accounts?

loud osprey
#

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

distant oyster
loud osprey
#

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

distant oyster
#

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?

loud osprey
#

no

#

you wouldn't have access to the connected accounts below

#

you would only have access to the platform account

distant oyster
#

Yes but would the customer be able to have access to their connected accounts since they take payments through their platform account?

loud osprey
#

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

distant oyster
#

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?

loud osprey
#

yes that's correct

distant oyster
#

Thank you very much. Appreciate the help!

loud osprey
#

let me know if you need any more help

distant oyster
#

Will do thanks!