#albert-paris_best-practices

1 messages ยท Page 1 of 1 (latest)

hollow irisBOT
#

๐Ÿ‘‹ 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/1443912082662756392

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

edgy socket
#

hi there!

unborn jasper
#

Hi!

#

I'm not sure I saw this, let me check it

edgy socket
#

so it's defintely an option yes

unborn jasper
#

We also set transfer_data.amount when we create the payment intent. Would you say it is better to leave it and create another transfer with the tip amount, or remove it and do a single transfer?

edgy socket
#

that's completely up to you. but may be simpler to do a Separate Charge & Transfer:

  1. get all the funds directly on your platform account with a regular payment
  2. then create a transfer with the amount you want to the connected account
#

One option is to use application_fee_amount, but that has implications on how the connected account see the fees, which makes it not valid for us
can you clarify what exactly us the issue with the connected account seeing the fee?

unborn jasper
#

That fee is for our b2b and b2c commissions and to pay Stripe fees, it will be different than the fee we report to our clients

edgy socket
#

got it

#

then yes I recommend Separate Charges & Transfer to have full control on what the connected account see

unborn jasper
#

Thank you, good to verify it's a normal practice

edgy socket
#

happy to help ๐Ÿ™‚