Prepaid Credit, Balances and Refunds Explained

Prepaid API billing is easier to manage when you separate three questions: what you paid, what your requests consumed, and what remains eligible for a refund. This walkthrough explains those distinctions and gives you a practical routine for managing Vana API spending.

§ Step 1: Start with a small, deliberate top-up

Create an account with Vana API, then choose an initial top-up that matches a limited test rather than your entire expected project budget. Define that test first: a few coding sessions, a document-processing batch, or a representative set of application requests. A smaller experiment makes it easier to understand your actual consumption before committing more money.

For prepaid usage, Vana API lists per-token prices with no monthly fee. Optional monthly plans are a separate product; do not confuse their allowances with prepaid balance. This walkthrough concerns balance-funded usage. ([vanaapi.com](https://vanaapi.com/price?locale=en))

§ Step 2: Understand what your balance represents

Your prepaid balance is credit for API usage, not a cash deposit. Vana API deducts charges as requests complete, using the tokens consumed. Adding credit and spending credit are separate events: a successful top-up does not mean the full amount has already been used. ([vanaapi.com](https://vanaapi.com/agreement?locale=en))

For your own records, keep the payment receipt and note the top-up time. Before a substantial run, record the available balance; afterward, compare it with the remaining amount. This simple habit helps you distinguish a payment question from a usage question without relying on memory.

§ Step 3: Estimate spending from token categories

Read the selected model’s pricing row before estimating costs. Vana API publishes separate input, output, and applicable cache rates per million tokens. For example, when evaluating Gemini 2.5 Flash, use its individual pricing categories rather than assuming every token has the same cost. Displayed dollar prices are approximate; accounts are maintained in CNY. ([vanaapi.com](https://vanaapi.com/price?locale=en))

Start with a representative sample, not just the shortest prompt you can write. Include realistic conversation history, attached context and response lengths. Then use the observed spending to set a budget for the larger workload. Treat that estimate as a planning tool, not a guaranteed final charge.

§ Step 4: Check the balance before troubleshooting access

Vana API’s documentation identifies HTTP 402 as the response when prepaid balance has run out. If a previously working balance-funded integration returns that status, check available credit before changing authentication settings or rewriting requests. ([vanaapi.com](https://vanaapi.com/plug-in?locale=en))

As a precaution, pause automated jobs while investigating. Avoid repeated retries that cannot resolve a funding issue. After addressing the balance, send one small request before restarting a queue. Keep a spending record for recurring jobs so that a depleted balance does not become your first indication of higher-than-expected consumption.

§ Step 5: Check refund eligibility promptly

Unused balance is refundable within 3 days of the top-up, less consumed usage and the payment processor’s fee. Used credit and top-ups older than 3 days are not refundable. Requests go through the message page and are handled within 3 business days. ([vanaapi.com](https://vanaapi.com/agreement?locale=en))

If you intend to request a refund, stop unnecessary usage and gather the payment reference, top-up date and amount. State your request clearly. Do not treat the handling window as a promise that funds will appear in your payment account on a particular date.

§ Step 6: Separate purchased credit from rewards

Referral and promotional credit cannot be refunded or withdrawn as cash. Referral earnings have separate payout rules, so distinguish those earnings from usage credit when reviewing your account. ([vanaapi.com](https://vanaapi.com/agreement?locale=en))

Keep a simple record of purchased credit, rewards and consumption. Before adding more funds, review your next workload and the terms then in effect. The practical goal is straightforward: fund a measured amount of work, monitor what it consumes, and raise payment questions promptly.