#realkillerps_best-practices
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/1396925915908407399
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Based on your description, it seems like you're using Direct Charges flow where the payment settles in Connected Account's balance and you just take the application fee?
https://docs.stripe.com/connect/direct-charges
If so, in that flow - the Connected Account is responsible for paying the Stripe fees. There is no way, right now, to know in advance the fee that Stripe will take. The only way to know the fee is to charge the payment method and then look at the fee on the associated BalanceTransaction as the fees are variable and depend on many diff factors.
You could start looking at the payment method itself (type, card country and brand, etc.) by saving it first. This allows you to detect enough to know which pricing we will apply and calculate it. Based on that, you calculate the fee and you increase or decrease the amount of the payment you're taking from the customer.
Would we be able to implement this if we used destination charges instead?