#hesoyam_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/1336627464289652778
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- hesoyam_best-practices, 2 days ago, 8 messages
Hi, let me help you with this.
hhi @vale axle , thank you.
We have used direct changes. In this way: stripe processing fees AND the platform fees are paid by the seller, but during the checkout, the seller brand appears (while we want to show the platform branding).
- on_behalf_of
didn't produced any difference for us
Switching from Destination to Direct charges is not a good way to control who pays the fees. There's much more to this change than that. You can always control how much the seller receives by application_fee_amount or transfer_data.amount.
on_behalf_of is only for Destination charges. It doesn't work the other way round.
You should stick to the Destination charges to present your Platform to the customers, and then calculate the correct application_fee_amount to cover the Stripe fees.
this means the platform will be for the stripe processing fees, instead fo the seller, no?
There is already a market place which I use as seller, where the as a seller I pay the stripe processing FEE AND the platform fees, while the platform branding is shown.
And they dinnamically create on the seller account products, for the changes.
I am happy to share in 1-1 platform name and stripe account ID where as a seller I pay both stripe processign fees and platform fees and platform branding is shown during checkout.
(So this setup is possible, today).
Maybe you can verify how these connect account mangement is achieved there and suggest the same APIS to use?
What is presented to the user of your Platform doesn't necessarily need to mirror exactly how things work behind the scenes.
As I said, there's no way to present Platform branding when making Direct charges. Fees is a minor detail of the difference between these payment flows, and you can always adjust the fees to reflect your business requirements in both setups.
Got it.
So, how can we we achieve our goals?
- show platform brand during checkout.
- let seller pay the stripe fees.
(using connected accounts)
hi! I'm taking over this thread.
show platform brand during checkout.
Then you have to use Destination Charges or Separate Charges & Transfers
hi
using destination charges or separate charges and transfers, will sellers pay the stripe fees instead of the platform?
i know we can adjut the application fee to make up for the stripe fees, but will they be able to see the total of the stripe fees in the receipt? instead of just the app fee
using destination charges or separate charges and transfers, will sellers pay the stripe fees instead of the platform?
The platform.
thanks, what about the second question?
i know we can adjut the application fee to make up for the stripe fees, but will they be able to see the total of the stripe fees in the receipt? instead of just the app fee
no they would only see the application fee
hi
so no way to change payment branding to match the platform's AND have the seller pay stripe fees (or at least, label them in the receipt), correct?
Sounds like you're using standard accounts? So no
As explained, you need to use destination charges for Checkout to use platform branding and generally those are charge types for non-standard accounts
the types are Standard/Express/Custom, correct? which one would suit our needs?
Only you can answer that – it goes beyond the branding and fee liability
Equally you can use controller properties to have more control of config: https://docs.stripe.com/connect/migrate-to-controller-properties
thanks!
i'm a bit confused about this one: so it's either use standard/custom/express OR use an api to config it all?
Yep
It's important you understand the differences overall with how funds flow between different payment types and where loss/fraud liability falls
You can't blindly pick an account and charge type just to get the branding you need
i see, where can i read more about the liabilities in this case?
On either of the links above
thank you very much