#bohdanborkivskyi_api
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/1441422138459295836
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
I don't believe there is a way to do this, but my team doesn't know too much about fees in general, so might be best to write to https://support.stripe.com/contact
thanks
Hi there, taking over for @severe bane as they had to step away
Unfortunately, subscriptions do not let you set a fixed fee amount, because you don’t always know in advance how much you will charge the customer. There is a workaround for invoices AFTER the first one, which is you can update an invoice and pass the application_fee parameter to set the exact application fee that you want in cents. You would do this by using Webhooks and listening for invoice.created events. This would tell you that a new invoice was created and you could set your application fee which would override the default application_fee_percent set on the subscription itself.
However, the first invoice of a subscription is always closed automatically and paid immediately. Which means your platform still needs to take this into account and calculate the percentage you should set to get the right application fee on the first invoice, which is a bit painful.
Not sure if this workaround works for your use case, but I did want to share in case it is helpful
Thanks, thats actually what I already do for invoices after the first one, but I am primarily interested how to change app fee for first invoice, since customer may be located in different locations with different taxes
Yeah, in that case for the first invoice there is no workaround unfortunately. I can flag with our team internally that this is an issue for your use case, as it has come up before