#nox7_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/1354159969846558862
π Have more to share? Add more details, code, screenshots, videos, etc. below.
hi! just want to acknowledge your question and let you know that the server is a little busy atm so it might be a bit before i can get to you
Hello
The rounding behavior is calculated based on the settings you've selected in the billing settings - https://dashboard.stripe.com/settings/billing/invoice#:~:text=Manual tax amount rounding
Based on your setting, the tax rounding changes old amount from 7.42 to 7.43 usd on the taxable amount (99 usd)
Hanzo,
Thanks for the reply. I changed the setting; but I am still getting the error.
See request: req_8wQowmFYlcg2G1
Ah you're using a direct charge, in which case the above request might be using settings from the connected account
Its still using line item level rounding behavior (similar to the previous request)
Ah, okay, I will try changing them on the connected account
Apologies, but I've now changed both the Connected account and the Standard child-account to be "Invoice level" rounding instead of line-item rounding but receive the same error.
Request: req_trrm2FRkvSPz6k
At this point I'd want to just fully refund the invoice, but I can't even do that either.
Ah I see. Let me check with a colleague
Hello @lost galleon, we have sent you a direct message, please check it at https://discord.com/channels/@me/1354175992058351657
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
@lost galleon go ahead and follow the instructions from the DM to open a Support case and I'll file a ticket internally about this bug.
Let me know when you have submitted that.
It has been submitted