#mufa-proration-more

1 messages · Page 1 of 1 (latest)

cedar gust
#

Hello! This is still a question for support

#

This is really specific to your own account. Prorations is explained in a lot of details in our docs

mossy yarrow
#

yes, but that documentation does not include any coupon/discount part

cedar gust
#

there's nothing "wrong" with your account, you're just asking "can you explain this invoice" and this isn't a developer question for Discord

mossy yarrow
#

thank you koopajah, but what I'm seeing so far I rather consider that as a Stripe's potential bug, given that I can't find any logical explanation on why it looks as it does. Customer Support also can't really find a clear reason on why it is the way it is. And I can't believe this is an expected behaviour

cedar gust
#

I understand, but it is unlikely to be a bug, just your misunderstanding and the person you spoke to on support. They can escalate to someone else with deep expertise on this.
Really this is just a proration question

mossy yarrow
#

Let me ask the question differently:
I have an annual plan, that allows to add a $40 coupon.

On top of that plan, user can add an addon that is nowhere associated with the coupon.

Now, when user has annual plan, $40 coupon, and an addon, and decides to cancel an addon, their prorated credit is deducted by the coupon (which should not even be applicable to the addon they removed)

#

okay, CS will escalate that further from what I've just received

cedar gust
#

Now, when user has annual plan, $40 coupon, and an addon, and decides to cancel an addon, their prorated credit is deducted by the coupon (which should not even be applicable to the addon they removed)
The fact that it says "with $40 off" doesn't mean it applied at all. It just means it was taken into account

#

Also reproducing this in Test mode with clear end to end steps would likely help you debug this further instead of looking at an ad-hoc live mode Invoice

mossy yarrow
#

okay, let me try to do that then. Thank you

#

Okay, I was not able to reproduce that locally with almost identical circumstances. CS has escalated the issue internally, so hopefully will get more light to this there. Thank you for your replies though, appreciate your time.