Credits

1 credit = ¥0.04 (one fen). So 1620 credits is ¥16.20, and the app prints the money value next to your balance.

A new account gets 500 credits (about ¥20) — enough for a dozen images or a few short videos, which is enough to walk a whole workflow through once.

That one big balance is really three buckets, and the rules differ:

A charge always comes out of whichever bucket lapses soonest: a model pack that matches the model, then subscription credits, then general ones. Which is why "how many subscription credits are left" is worth more of a look than the total — the Membership page in your account keeps the subscription and general numbers apart, and says when the current period resets.

The price is not a flat fee per generation. It follows what this particular call actually cost:

That is why two runs of the same kind can differ more than tenfold: a 15-second 2K video costs far more than a 5-second 480P one, images are priced per image, and voice-over by character count. What each kind is charged by, and which models exist right now, are in 14.8.

You see the price before you submit: the small number with an icon at the bottom-right of the input bar is what this run will cost, and it tracks the model, resolution, duration and count you pick, live (see 14.8).

Open Credits in your account (or go straight there from the credits line in the avatar menu).

The tag on the balance card tells you which wallet this is (see the team wallet below), and the Credit store button next to it is where you top up (see 14.4). The table under it holds one entry per row:

• Time
• Item — what was done (Video / Image / Speech…), with the sum in small text underneath, like seedance 720P × 5s. That line is the answer to "why did this one cost so much". Rows that aren't generations name their reason instead: Top-up, Refund, Subscription credits granted, Subscription credits lapsed.
• Change — a negative number is a charge, a positive one is money in (shown in green).

The history really does page back: there is a pager under the table, 20 / 50 / 100 rows a page, so you can keep going when you reconcile.

Once you have topped up, this page also carries a Top-up orders table (time, credits paid + free, amount, status). It is not the same thing as the history: the history records what moved in the wallet, the orders record that you bought something — unpaid and cancelled orders never show up in the history at all. Each paid row has an Invoice action (CNY orders only); fill in the title and email, submit, and the invoice is sent to that email once processed.

A generation that fails (the model errored, or it timed out) gets its credits back automatically, recorded as a positive entry in the history. So a +180 in there is not necessarily a top-up — it may be the refund for the failure just above it.

It goes the other way too: one kind of negative row is not something you spent. When last period's unused subscription credits lapse, the history records a Subscription credits lapsed row. That row is the answer to "where did my credits go".

A wallet belongs to a space: one for you, and one for every team you join.

• Generate in your personal space and you spend your own;
• generate in a team space and you spend that team's.

So switching spaces swaps the whole set of numbers — your credits did not shrink, you are looking at a different wallet. The team's own history lives under Credits in team management (see 14.6), where every member can see it.

A membership is bought for a space as well: the one you bought for yourself does nothing for a team. Who can place a team's orders, and how, is in 14.4.