---
title: "Charged for a Failed Veo Generation? How Refunds Work | imaginary.app"
description: "Flow returns credits for failed or filtered Veo videos within an hour. What Google Cloud says, how our refunds work, and what to do if credits stay gone."
url: https://www.imaginary.app/blog/veo3-failed-generation-billing-fix-alternative
---

Updated November 2026

# Charged for a Failed Veo Generation? How Refunds Work in Flow, Google Cloud and Here

Usually you are not. Google Flow takes credits when a generation starts and, per Google, returns them within one hour if it fails or hits a safety filter; imaginary.app refunds failed generations automatically. If the credits stay gone, first check whether the video actually finished, then contact support with the task ID.

Key takeaways

- **Flow:** credits for failed or filtered generations come back "within one hour".
- **Google Cloud:** Google's Veo safety page does not say whether blocked requests are billed. Check your billing report.
- **imaginary.app:** refunds are automatic for failures, timeouts and Google safety blocks; a task whose outcome we can't confirm is reviewed by support.
- Refunds cover failures, not videos you dislike. Drafting on Lite is the real cost saver.

Automatic refunds

Failed Veo 3.1 generations are refunded automatically

Credits are deducted when a generation starts and returned if it fails or Google blocks it. If the outcome is unclear, support reviews the task.

[Start Creating](https://www.imaginary.app/generate)[View Pricing](https://www.imaginary.app/pricing)

Sign in with Google to create an account; buy credits only when you need them.

## Who charges for a failed Veo generation?

The answer depends on where you generate. Here is what each provider says in its own documentation, as of November 2026.

| Where                      | Failed or blocked generation                                                   | Source              |
| -------------------------- | ------------------------------------------------------------------------------ | ------------------- |
| Google Flow                | Credits returned within one hour if a generation fails or hits a safety filter | Flow Help           |
| Google Cloud (Veo 3.1 API) | Not stated on Google's Veo responsible AI page                                 | Google Cloud docs   |
| BytePlus (Seedance)        | Failed or moderated generations are not billed                                 | BytePlus pricing    |
| MiniMax                    | Failed generations are not charged                                             | MiniMax pricing     |
| imaginary.app              | Credits refunded automatically on failure, timeout or safety block             | Our generation code |

Users report Flow showing "You have not been charged for this generation" on failed jobs. Google's help page doesn't quote that message, but it matches Google's stated rule that credits come back within an hour. If they do not, Google points you to Google One support. Users on Google's developer forum have reported cases where credits seemed to be taken for failed batches, so keep screenshots with timestamps before you contact support.

## What to do if your credits did not come back

1. ### Check whether the video actually finished

   A failure on screen does not always mean a failed generation. If your connection drops or a page times out while the video is still rendering, the video can finish and be saved anyway. In Flow, refresh the project (Google notes some generations only appear after a refresh). On imaginary.app, open My Creations.

2. ### Give the refund time to land

   Flow says up to one hour, and your Google One credit history can lag after that. On imaginary.app a pending refund is retried automatically. Avoid resubmitting the same prompt while a status is still unresolved, or you may pay twice.

3. ### Work out why it failed before retrying

   A filtered prompt will fail again if you resubmit it unchanged. Our [error message guide](https://www.imaginary.app/blog/google-veo3-something-went-wrong-error-fix) explains each Flow message and the Google Cloud support codes.

4. ### Contact the right support team with evidence

   For Flow, contact Google One support. For Google Cloud, use Cloud Billing support with the project and the billing line items. For imaginary.app, email hi\@imaginary.app with the task ID shown in the message.

## How refunds work on imaginary.app

We deduct credits when a generation starts, before the request goes to Google. If the generation then fails, times out, or Google's safety filter blocks every video, the credits go back to your balance automatically and the refund is linked to the original deduction. Prompts that our own screening blocks, such as deepfakes or impersonation of real people, are rejected before any credits move.

These are the status messages you can see and what each one means:

| Message                                                                                                         | What it means                                                                      | What to do                                             |
| --------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------------------------------------ |
| "Your credits have been refunded."                                                                              | The generation failed (timeout, network error, rate limit) and the refund is done. | Nothing. Retry when ready.                             |
| "Video not generated because it isn't allowed by AI Provider (Google, etc.) Terms of Service."                  | Google's safety filter blocked the video. Credits are refunded.                    | Reword the prompt or change the image before retrying. |
| "Generation failed. Your credit refund is pending and will be retried automatically."                           | The refund did not go through on the first try.                                    | Wait. The system retries it for you.                   |
| "This video is taking longer than expected. We are still checking its status; a refund has not been confirmed." | Google has not reported a result yet. The video may still arrive.                  | Do not resubmit. Check My Creations later.             |
| "Your video is generated. We are saving it to My Creations."                                                    | It worked; the file is being saved.                                                | Open My Creations in a minute.                         |
| "We could not confirm the generation outcome. Contact support with this task ID…"                               | The outcome is unclear, so a person reviews the video and the credits.             | Email hi\@imaginary.app with the task ID.              |

What a failure would have cost

For scale: an 8-second Veo 3.1 Quality video at 1080p with audio is 26 credits (about $5.55–$6.49), and Fast is 10 credits (about $2.13–$2.50). That is the amount an automatic refund protects. Google Cloud's per-second list price is lower than ours; the trade is no Cloud setup, one-time packs and refunds handled for you (see [pricing](https://www.imaginary.app/pricing)).

Draft on Veo 3.1 Lite, keep the refunds for real failures.

[Start Creating](https://www.imaginary.app/generate)

## Refunds do not cover bad results, so cut the cost of iteration

No provider refunds a video that rendered fine but is not what you wanted. That is where most money goes, so:

- Draft on Veo 3.1 Lite: 3 credits for 8 seconds at 720p with audio, then re-make only the keepers on Fast or Quality. [Lite vs Fast vs Quality](https://www.imaginary.app/compare/veo-3-1-lite-vs-fast-vs-quality) shows the differences.
- Test prompts with 4-second clips; on Fast and Quality they cost roughly half as much as 8 seconds.
- Turn audio off for silent drafts; it lowers the credit cost. The [cost calculator](https://www.imaginary.app/tools/veo-3-1-cost-calculator) shows every combination.
- Make results more repeatable with a fixed prompt structure; see [why Veo results vary](https://www.imaginary.app/blog/veo3-quality-consistency-problems-variable-results).

When not to switch: if you already pay for a Google AI plan and its credits cover your volume, Flow's own refunds work and its credits cost less per video. Bear in mind that Veo 3.1 Fast and Quality leave Flow on December 5, 2026; Lite stays.

## Frequently asked questions

### Does Google Flow charge for failed Veo generations?

Google says Flow deducts credits when a generation starts and, if it fails or hits a safety filter, returns them within one hour. The balance and Google One credit history can take time to update. If you think you were charged by mistake, Google directs you to Google One support.

### Does Google Cloud bill for Veo requests that are blocked?

Google Cloud's Veo responsible AI page explains how blocked requests and support codes work but does not say whether blocked requests are billed. Check the Veo line items in your Cloud billing report and ask Cloud Billing support if a charge looks wrong.

### Are credits refunded on imaginary.app when a video fails?

Yes. Credits are deducted when the generation starts and refunded automatically if it fails, times out or is blocked by Google's safety filters. Prompts our own screening blocks are rejected before any credits move. If we cannot confirm whether a video finished, the task goes to support review instead of an automatic refund.

### I saw an error but my credits did not come back. What happened?

Check My Creations first. If the connection dropped while the video was still rendering, the video may have finished and been saved, in which case the credits paid for that video. If there is no video and no refund after the status settles, email support with the task ID.

### How do I avoid paying for bad generations?

Refunds only cover failures, not videos you dislike. Draft on Veo 3.1 Lite (3 credits for 8 seconds at 720p with audio) and re-make only the keepers on Fast or Quality, and use 4-second test clips while you work out a prompt.

How we checked: Google's refund wording comes from the Flow help page; we read Google Cloud's Veo responsible AI page for any billing statement and found none; other providers' policies come from their pricing pages; our status messages and refund behaviour are copied from the current imaginary.app code.

## Sources

Prices, model specs and dates on this page were checked on November 8, 2026. Third-party prices change; check the source before you rely on a number.

- [Google Flow Help — requirements and troubleshooting (credits on failure)](https://support.google.com/flow/answer/16353333)
- [Google Flow Help — credits and models](https://support.google.com/flow/answer/16526234)
- [Google Cloud — Veo responsible AI and usage guidelines](https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/video/responsible-ai-and-usage-guidelines)
- [Google Cloud — generative AI pricing](https://cloud.google.com/vertex-ai/generative-ai/pricing)
- [BytePlus ModelArk — model pricing (Seedance)](https://docs.byteplus.com/docs/en/modelark/model-pricing.md)
- [MiniMax — API pricing](https://platform.minimax.io/docs/guides/pricing)
- [Google AI Developers Forum — user thread on failed Flow generations](https://discuss.ai.google.dev/t/google-flow-veo-stuck-in-queued-state-oops-something-went-wrong-failed-generations-deducting-credits-google-ai-ultra/173335)
- [imaginary.app pricing](https://www.imaginary.app/pricing)

Veo 3.1 Lite, Fast and Quality

## Generate Veo 3.1 with refunds built in

Failed and blocked generations are refunded automatically. Start with a one-time credit pack, no Google Cloud setup.

[Start Creating](https://www.imaginary.app/generate)[View Pricing](https://www.imaginary.app/pricing)

Sign in with Google to create an account; buy credits only when you need them.
