#willy-quanta_connect-separate-charge-transfer
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/1440059850271756300
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
๐
Hi ๐
You use on_behalf_of to specify the settlement merchant. If you are splitting payments it doesn't make sense to specify OBO for 2 accounts
You would settle the funds on your platform account and then transfer portions to both accounts
ok, so how do i automate that transfer to those 2 accounts?
i'm managing hundreds of studios, and they all have different % splits that they have set on their in-app accounts
when we accept a payment, it comes to us, then X% goes to their studio, and X% goes to their resident artist that did the appointment
Okay lets take a step back
i can get payments to my account, or automatically to one account, with no problems, splitting is where im having issues
First
This is the payment flow you would use: https://docs.stripe.com/connect/separate-charges-and-transfers
Here we cover
- How to collect the payment <- this happens on your Platform account
- How to create Transfers <- this send money to Connected accounts
In step 2 is where your integration would need to determine what % of the original charge each account should get.
so there is not a way to determine % split inside of the stripe api, i would need to determine that separately and then pull those values in
to plug those into amount=''
can transfer_group be whatever the hell we want it to be?
from my understanding, this is just telling us to run that one chunk of code twice, with separate amounts and destinations, but the transfer_group is the same
should be transfer_group always be different for each transaction, or could i just tie them to something like the Connected Account ID?
Transfer group is generally used to connect the Transfers to the Charges, so generally we recommend it be unique to the transaction. The primary purpose is to help you keep it all straight.
i see. is there anyway to generate a UUID or something inside of the request, and attach that transfer group to both transfers?
or should i generate a UUID in my app and assign that value to the transfer_group
You would do that in your app
willy-quanta_connect-separate-charge-transfer
alright, ill give it a go. thank you'