#shru-separate-charges

1 messages · Page 1 of 1 (latest)

left horizon
#

hey there, this is a fairly complex flow

weak ibex
#

Thanks, these were the 2 docs we were already looking into but our current implementation required that we use standard connected accounts and that the connected account be responsible for disputes and refunds. I guess we couldn't maintain that approach if we head in the transfers direction?

left horizon
#

So you'd manage the customer on your platform primarily, along with the representation of the total payment, then you could complete many separate payments on each connected account but this will happen as multiple charges to the customer

#

Right that's where the payment method sharing comes in, and you could manage multiple direct charges on the accounts

#

so you wouldn't be doing charges & transfer, it would be direct charges, as recommended for standard accounts

weak ibex
#

so with payment method sharing we can still keep our standard account structure and with a single checkout flow distribute direct charges across multiple connected accounts?

left horizon
#

Yes, that's an expected use for it

weak ibex
#

But this is card payments only currently? As we would implement klarna, sepa also in our checkout?

left horizon
#

As long as you understand there will be multiple multiple customer payments

#

Correct, this kind of cloning is only supported for cards. others would need to be set up per account and may not be possible to support the way you're trying to do, for which you might need to use express/custom accounts with destination charges or transfers, and a a different liability model

weak ibex
#

Ok that great synth, thanks for the help once again 🙂

left horizon
#

quite welcome 🍻