AI top-up bonus expiry during a running task: reservations and released credits

An AI task reserves bonus credits before midnight; the bonus expires while the task runs. Returning the reservation to a single balance after cancellation can accidentally revive it. This guide addresses owned or authorized AI-service billing implemented by the merchant. 稳付pay is not claimed to supply model billing, authorization holds or expiry APIs.

Continue by topic

Define lot identity and the rule before purchase

Separate funded credits, promotional credits and membership rights. For each bonus lot retain source, granted amount, eligible uses, start, cutoff, timezone and rule version. A total balance cannot explain which lot a release belongs to. Do not retroactively expire funded credits sold without a limit.

Disclose consumption order and treatment of tasks crossing the cutoff. Whether a previously reserved bonus may finish its original task, for how long, and how unfinished work is reviewed must match real capabilities and published terms. Do not invent a less favorable rule after failure.

Reserve by lot; release to the same source

A reservation references quantities from specific lots and one task. Protect validity checking and reservation with a lock or version condition under the chosen expiry policy. Expiration cleanup shares that concurrency boundary so the same credits cannot also fund another task.

Releasing a hold is not a new grant. If the original bonus lot expired, place the released quantity in expired credits or apply a previously disclosed grace rule. Do not turn it into usable funded balance. Verify actual consumption first; cancellation is not evidence that usage was zero.

Reconcile one task crossing midnight

Illustration uses a disclosed policy: a pre-expiry hold can settle its original task, but released remainder does not regain validity. Funded balance is 100 and bonus 40. Task reserves 30 bonus. At cutoff, unreserved 10 expire. Confirmed usage is later 18; remaining hold 12 expires on release. Final funded availability is 100; bonus consumed 18, expired 22 and reserved zero.

These are internal units, not a Token conversion or real transaction. If task outcome is unknown, retain the 30 in controlled review with a deadline. Do not both expire it and charge it again. Any additional funded deduction must fit original authorization and cost limits.

Reconcile each lot using exclusive categories

Granted credits plus sourced adjustments reconcile to available, reserved, consumed and expired quantities. For the bonus example, 40 equals 0 plus 0 plus 18 plus 22. Refunds and compensation use separate linked adjustments; do not delete the original grant. Persistent task and operation identities prevent repeated settlement or release.

Test reservation at cutoff, cleanup racing cancellation, partial usage, task timeout, repeated release and mixed lots. Keep task, lot, policy version, timestamps and reviewer. Uncertain metering needs review rather than invented supplier states or charging endpoints.

Frequently asked questions

Does releasing an expired reservation make it usable again?

Not automatically. Return it to its original lot and apply the disclosed expiry or grace policy. A balance increment alone does not extend validity.

Can an expired bonus be refunded as cash?

Do not equate them. Payment amount, internal bonus and cash refunds are separate records. Eligibility and processing follow actual product terms and confirmed channel arrangements.

References