After paying for two sets of 500 fast requests ($20 each), I downgraded my subscription for the following month. Despite having approximately 200+ unused fast requests that were already paid for, I am unable to access these remaining requests and am limited to slow requests only. This effectively means I’ve lost access to pre-paid resources.
Steps to Reproduce
Purchase premium model fast requests (500 for $20)
Purchase additional 500 fast requests ($20)
Use more than 500 of the total 1000 fast requests
Downgrade subscription for the next billing cycle
Attempt to use remaining ~500 fast requests
Observe that only slow requests are available despite having pre-paid fast requests remaining
Expected Behavior
Pre-paid fast requests should remain available for use until depleted, regardless of current subscription status. Since these requests were already paid for, they should be accessible even after downgrading the subscription for future months
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.43.5
VSCode Version: 1.93.1
Additional Information
This issue affects paid users who want flexibility in their subscription choices while retaining access to already purchased resources. The inability to use pre-paid requests after downgrading creates a negative user experience and effectively results in losing paid-for services
When you cancel a subscription, we refund a pro-rated amount to your account, which comes off on future purchases.
It looks like you’ve had this in your situation, where you’ve had months “cheaper” than the full $20 as you’ve had credit on your account.
Because we have this system in place, we do take away the extra usage immediately when you downgrade, to avoid someone upgrading, using a ton of requests, downgrading the same day and getting those requests for free.
The requests are a monthly rolling allowance, like data on your mobile phone contract, so don’t roll over to the next month. But as you are refunded for the remaining time, we think this is a fair system.
If you think there’s a better way to do this, without risking giving away free usage, I’d be interested to hear it!
Just today I was charged another $20, and the invoice shows only a -$0.60 “Applied balance”. This seems very low considering I had about 200 unused requests out of my 1000 (which should be worth around $8).
I understand the need to prevent abuse from people who might upgrade/downgrade quickly, but that’s not what happened here - I used the service normally over time and simply had leftover paid requests.
Could you take another look at my account? The latest invoice is attached above, showing the $0.60 credit applied. I haven’t seen any other refunds hit my card either.
I have the same issue here. I would like to keep my existing 1500 FAST requests that I’ve already paid for, and simply have the reduced fee of $20 USD applied for the next billing cycle when I renew. In other words, I want to retain what I’ve already purchased, while having the new, lower price take effect for future billing periods.
Same here usually 500 fast requests was enough for me but this month I needed more(slow requests was too slow) I also used 796 requests and downgraded for next month and I loose my pre-paid 204 fast requests that I need right now this is ■■■■■
Sorry this wasn’t clear when you upgraded your fast requests!
If you drop us an email at [email protected], they should be able to sort a refund out for you.
However, for the future, you can now enable usage pricing and be charged $0.04 per fast request outside of your usage, so instead of having to upgrade and downgrade in batches, you will only page for what you use!
I think this needs to be better communicated or fixed.
Im holding off on the subscription due to such unclear situations. While we use several such tools, most of them have clearer pricing. The cost is not the issue.
What happens if i have to add additional batch of 500 if i have an monthly or an annual plan (both cases are important).
What happens then at the end of the month in both cases?
Why would a user need to contact support to refund instead of just keeping the remaining requests until renewal of the primary subscription?
1a. If you add an additional batch of fast requests monthly, your account will be immediately invoiced based on how far through that month you are. If you remove them, you will be credited for the time remaining on that batch.
1b. If yearly, the same should occur, but as you’ve signed up for the yearly plan, your credit will not be available until your yearly renewal. While less flexible, this is due to the cost savings by signing up for a yearly plan.
If you leave the additional requests on your account, your renewal will be $20 per 500 requests you have, and you will only get one monthly payment from that point onwards. On a yearly plan, the same occurs, but for yearly renewals.
Requests do not carry over month by month if you don’t use them, but as this was unclear to the user, we’d be happy to offer a refund as a gratuity. If they downgraded manually, they would be credited for the remaining time, but would have still paid for the additional requests for a period of time, which may not be what they intended.
For all of the above, I’d recommend using the usage-based pricing as I mentioned, as this is substantially simpler, as regardless of your plan, you are invoiced at the start of each month based on what you used last month (outside your allowance).
The bulk fast request upgrades described here are only beneficial if a user doesn’t mind losing a few extra requests each month, in exchange for a predictable cost each month!
