#yb-stora_unexpected
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/1496457308593721354
📝 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.
- yb-stora_webhooks, 5 days ago, 13 messages
Taking a look!
Sorry, had to step away. Back now
Looks like the fee was computed from your platform pricing config: https://docs.stripe.com/connect/platform-pricing-tools
i'm not sure i understand. to clarify even though we set the fee amount to 0, a fee amount is still calculated and charged?
Yeah, unclear if this is unexpected in scenarios you specifically set 0 though:
The payment doesn’t explicitly apply application_fee or transfer_data[amount] parameters that override managed application fees.
are you able to help me clarify?
because we're explicitly setting the application fee to 0 but somehow we end up with application_fee_amount on the PI
You'll probably need to write in to my team and we can figure out what is expected here
Hello @marsh sleet, we have sent you a direct message, please check it at https://discord.com/channels/@me/1491080560238395412
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
i guess the link in the DM was supposed to launch a support wizard (guessing from the query params)? it didn't, unfortunately
Can you try just omitting the app_fee_amount param when you create the Invoice?
Actually, sorry. That's not the behaviour you want
yup. on basil the app fee amount is no longer on the invoice. i'm worried that i'll create an invoice with a zero app fee and end up with a payment intent with positive app fee. in fact lemme try that right now
We just got your email, so will continue to investigate and reply there
ack! thanks. if it helps, on basil invoice.application_fee_amount: 0 in the create call -> payment_intent.application_fee_amount: null. so that seems to be alright 👍
test invoice: in_1TOyXZRGCWPnlEBEv6Z3yD2W (req ID: req_GL298G8pSSPy0s)
Interesting, so looks to be a bug specific to pre-Basil versions
perhaps