assinei um plano de 20dolares na verceu pra usar a v0, e acabei não usando nada apareceu uma mensgem dizendo que meus creditos seria reiniciados em 30 dias, comprei mais 20 de credito extra pra poder usar qua acabaram nun piscar de olhos. entrei em contaco com o suporte ate agora sem resposta para prioridade1
pawlean
May 24, 2025, 5:16am
3
Hi, Fabio! Welcome to the Vercel Community.
Thanks for reporting this! You’ve done the right thing opening a support case already at vercel.com/help . Our team will get back to you as soon as possible.
Please let me know if you have any other questions
lodos3
May 24, 2025, 2:14pm
4
What about my issue ?
i have several chats, all blank, no responses and no code , but i was charged ?
why am i being charged for duplicated chats
sem resposta ainda a minha soliciação a equipe
Hi Fabio, you were affected by this bug
You had the full $20 remaining on your balance when it was reset to $5, so you can expect a credit of $15.00 soon
Closing this thread to keep the conversation in the incident thread
Last week, it came to our attention that some users were abusing the subscription system in an attempt to get free tokens. We implemented a fix to prevent this, but it was applied too broadly and in some cases caused legitimate users to not receive their new tokens.
If the payment failed while a user was subscribing to v0 Premium, we reset their credits to the free $5 amount. If they successfully purchased again in a short timespan, our system incorrectly would not re-issue the premium credits. …
A credit of $20 has been applied to your account
We’ve re-issued the missing credits to all affected users plus an additional $5
If you had a $20 balance when it was reset to the free $5 amount (losing $15 worth of credits) you should see a top-up of the full $20
If you had a $10 balance when it was reset to $5, you will see a top-up of $10
These will appear as “purchased credits” and have been extended to 60 days so you will have additional time to use them.
There is one additional edge-case where a user can still hit this bug before June…
