#mzir_unexpected

1 messages ยท Page 1 of 1 (latest)

hardy groveBOT
#

๐Ÿ‘‹ 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/1222204556557947010

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

deft grailBOT
woven bone
#

Hi ๐Ÿ‘‹ trying to double check, but I don't think voiding the Invoices is expected to bring the Subscription back to an active state. I believe the most recent Invoice needs to be paid before it's due date to restore a past_due Subscription.

onyx dune
#

hey

#

There's nothing to be paid, so past due doesn't seem appropriate

#

can I force the subscription status to be active somehow?

woven bone
#

No, you can't forcibly change the status of a Subscription.

onyx dune
#

okay, but can I create like a $0 invoice for the user to reset that?

woven bone
#

I'm still trying to double check that.

#

Can you share the ID of the impacted Subscription?

onyx dune
hardy groveBOT
royal cobalt
#

Hi ๐Ÿ‘‹

I'm stepping in as my colleague needs to go soon. Looking at the latest invoice for this Subscription and it looks like it was voided. I don't see a successful payment anywhere here

onyx dune
#

this is how it looks for me

#

$490 is paid, $588 is voided

royal cobalt
#

The latest invoice for this subscription is not paid. I think that is why this shows as past_due. Can you share the ID for that invoice that shows as paid?

onyx dune
#

in_1Os4vAKujHy4K0OUjh6pp3pV

royal cobalt
#

Hmmm okay

#

But then what changed that triggered the second invoice?

onyx dune
#

so the way we do pricing is you are always subscribed for a full year (1st Jan - 31 Dec) and there are different tiers of subscription. On some trigger, you are upgraded, which includes updating the subscription price, and charging a specific amount that depends on when you were upgraded.

To achieve this we created a custom invoice for the $490 (the intended charge) and updated the price. Turns out we had a bug in the code and did not send the billing_cycle_anchor: "unchanged", which created an additional, unintended invoice for full 1 year period ($588)

#

in the interest of time - if I just create a new subscription for that user, and cancel the old one that should remove the problem completely, yes?

royal cobalt
#

Yes that is one way to go about it. The problem curently is that, even though the previous invoice was paid, the latest one is not and that is why the Subscripiton remains in past_due

onyx dune
#

right, okay

#

thanks

#

I understand that you consider this expected, but my feedback would be that this behavior is not intuitive and left us with a subscription that is perfectly fine -- everything that was due was paid -- but Stripe still signals that there's something wrong with it, shows it in red, etc. Worse, there's nothing we can realistically do about it except either cancelling the subscription or just dealing with it for a year (until a new invoice is created).

royal cobalt
#

I can take that feedback and raise it internally