# Billing

QuickPod uses prepaid account credit. You add credit first, then active workloads consume that balance over time.

## Current payment behavior

QuickPod's current console billing flow supports card checkout through Stripe and crypto-oriented billing flows exposed through the billing experience in Settings.

The billing area in the console also exposes invoice history and payment-link or payment-method related controls.

## How charges work

QuickPod separates compute cost from storage cost.

* Running pods accrue active compute cost plus storage cost.
* Stopped pods stop compute cost but continue to accrue storage cost while they still exist.
* Destroyed pods stop both compute and storage cost for that pod.
* Persistent storage and sync workflows can have their own associated costs depending on how you size or use them.

Internet bandwidth usage is charged at $4 per TB. This bandwidth pricing is set by the platform and is subject to change.

## What happens when your balance reaches zero

QuickPod does not immediately destroy your workloads and data when your balance reaches zero.

Instead, pods are stopped automatically so you can still recover data or add more credit. Storage charges may continue while the stopped pod still exists.

## Billing guidance

* Destroy pods you no longer need.
* Use volumes or cloud sync if you need persistence without leaving expensive pod disks running indefinitely.
* Review invoices and balance inside the authenticated settings experience regularly.

## Related console routes

* Authenticated billing area: `/settings`
* Public sign in: <https://console.quickpod.io/log-in>
* Public sign up: <https://console.quickpod.io/sign-up>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.quickpod.io/console/billing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
