$20 wallet, two 8-second 1080p Seedance 2.5 jobs: the second gets 402

Two 8-second Seedance 2.5 clips at 1080p cost 2 x $11.3724 = $22.7448, so with a $20.00 wallet the second submit fails with 402 insufficient_credits while the first is still processing. Sume reserves the estimated amount at submit (provider list x 1.25), and the second reservation of $11.3724 does not fit in the $8.6276 that is left.

What each tier would reserve

Seedance 2.5 video is billed per output second, linear in duration. Eight seconds at each resolution:

What happens to the reserved money

A reservation is not a charge. The core workflow doc describes reserve, then capture on success, then refund on failure or on cancellation before capture. If the first clip fails, the full $11.3724 returns to the balance and the second submit will succeed on a retry. If it completes, the capture stands and the balance is $8.6276.

Fitting two jobs into $20.00

A 720p draft and a 1080p final fit together: $4.6224 + $11.3724 = $15.9948, leaving $4.0052. Three 480p drafts and one 1080p final fit as well: 3 x $2.1494 + $11.3724 = $17.8206, leaving $2.1794.

Two 1080p jobs of 6 seconds each cost 2 x 6 x $1.42155 = $17.0586, which also fits. The limit is seconds at that resolution: $20.00 / $1.42155 = 14.07 seconds of 1080p video in total, whatever the clip count.

If you want two 8-second finals at 1080p, top up to at least $22.75 (2 x 11.3724 = $22.7448, rounded up). Reservation is computed from the estimate Sume stores in USD micros and rounded up to cents, so add a few cents of margin.

How to avoid the 402

• Submit the draft first at 480p ($2.1494), then the final at 1080p once the prompt works.
• Check the balance before you submit and sum the reservations of everything in flight; do not assume the wallet covers all queued jobs.
• Treat 402 as a stop signal, not a retry signal. Retrying the same request cannot succeed until money returns or the request gets cheaper.

A pre-submit habit

Before each submit, subtract the reservation of everything still in flight from the balance, then compare the new job's estimate.

A 402 is a clean refusal: no job exists and no provider work started, so there is nothing to cancel and nothing to refund. The error body carries a request id; keep it in your log with the model, duration, resolution and the balance you read just before the call.

Resubmit only after the balance changes or the request gets cheaper. Retrying the identical 1080p request with the same idempotency key is safe but pointless until money returns, and a loop that retries every few seconds only adds rate-limit pressure.

• Balance $20.00, one 1080p 8-second job in flight ($11.3724): available $8.6276.
• New job at 720p ($4.6224): fits, leaving $4.0052.
• New job at 1080p ($11.3724): does not fit, expect 402 insufficient_credits.
• After the first job completes, the capture is final and the balance stays $8.6276 until you top up.