#nt_unexpected

1 messages ยท Page 1 of 1 (latest)

rustic daggerBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1247556616211927192

๐Ÿ“ Have more to share? Add details, code, screenshots, videos, etc. below.

carmine skiffBOT
carmine skiffBOT
rocky siren
#

Hi there ๐Ÿ‘‹ apologies for the delay here catching up.

rich bay
#

Hey, thanks answer whenever you are ready no issue

rocky siren
#

For the toolkit accepting a float, I think that will need to be reported to our Support team to have that flow further investigated, it isn't one we're too familiar with in this forum (we mostly focus on working with our API here).
https://support.stripe.com/?contact=true

For the Subscription that you say was created with the wrong amount, can you share the ID of that by chance? That behavior may be due to how the tooklit is functioning, in which case it should also be routed to our Support team, but I want to take a look and see if we're prorating the amount instead.

rich bay
#

Sure here's a subscription scheduled id: sub_sched_1PNy4ZDgQLhhFEp9tZvMWohn
And here's a subscription id (when the migration completed): sub_1PNykIDgQLhhFEp9WNgEJPqk

rocky siren
#

Oh I see, the actual amount of the Price object that was created doesn't match what you provided. Am I understanding correclty?

rich bay
#

Correct, we pass a csv with an amount item priced 34.80 and the toolkit creates a subscription with the corresponding amount 34.79

#

If we pass inside the csv the amount as 34.801 then the toolkit correctly rounds it to 34.80. I think it's a rounding/precision issue with the toolkit and not something from our end

rocky siren
#

Totally agree based on what you're describing! I'd suggest compiling these details and opening a case with our Support team. They should be best suited to get you to the right folks to take a closer look at that.