#juangomez0120_api

1 messages Ā· Page 1 of 1 (latest)

kind bladeBOT
#

šŸ‘‹ 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/1334258919538819223

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

delicate spade
#

The trial was set to end at 1736979840 but we received the API call about 6 secnods after that at 1736202256. I am a bit surprised we didn't error out, but that looks to be why there wasn't a trial

#

Are you trying to start a very short trial so that the first invoice goes into a draft state?

gentle lake
#

I can indeed see other requests made to the subscriptions endpoint very close in time from the creation, but taking a look at the body of the other requests there's no modification made to the trial end date

Screenshot_2025-01-29_at_2.38.46_p.m..png
delicate spade
#

Oh wow I am sorry šŸ¤¦ā€ā™‚ļø I misread the date

#

Looking into this again. Apology server had a burst, I thought I was still looking at things closely but aparently not

#

We got that call on 1/6 and the trial end was set to 1/15

gentle lake
gentle lake
delicate spade
#

the first invoice on that subscription does look to be a $0 invoice for a trial subscription in_1QeOibLcvFf9iGKk78PinBP6

#

What was the behavior that you saw on your side? I am having a bit of trouble seeing exactly what happened with some of these logs, may need to reach out to my colleagues

gentle lake
#

As you can see there's a payment intent related to the invoice, which contains a $307 amount

#

This process was made at the moment when the subscription was created

#

As you can see the amount_due isn't 0 and the billing_reason is a subscription_creation. Also, the subscription related to this invoice is the same one that had the free trial set to en on 1/16

image.png image.png
#

The invoice id is in_1QeOibLcvFf9iGKk78PinBP6 in case you want to check it on your side

delicate spade
#

Thank you for the clarification. Apologies for the delay, looking into this again now

#

I've reached out to my colleagues on this, I only see the one $0 item on the subscription but I do see that it charged them $307 in customer credit. Will get back with what we can find.

gentle lake
#

Thank you so much! I'll be here if you need any additional information

delicate spade
#

According to my colleagues, it looks like that may have happened because of previous credit transactions on that customer. Can you create a new test customer and try this again to see if it acts as excpected?

gentle lake
#

I tried this in the testing environment and I wasn't able to reproduce the issue, everything seems to be working as expected. Do you know where I can find a credit ledger for that user? So that we can identify that as the issue and communicate it with the client

delicate spade
#

Still looking for this. I thought we had a dashboard page for this

#

For some reason the "Customer invoice balance" page can say no transactions but still show transactions on the balance transactions page. I am not sure if that is just my test customer but can look into that and file something to fix the dashboard UI if that is unexpected.

gentle lake
#

Thank you lots! Checking the logs it indeed was a credit charge ty