> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

# Review invoices and payment

You buy credit before paid work. The first purchase is $25; it is purchased credit, not a free
allowance. Later top-ups are your choice. There is no automatic reload or overage, and purchased
credit does not expire or transfer to another account.

## Buy credit in the secure payment step {#buy-credit}

Follow this sequence:

1. Select the intended Compute account and review its current funding state.
2. Use **Add $25 credit** when the authorized billing surface offers it. Review the service amount,
   any separately disclosed tax and the total before paying.
3. Complete payment yourself in the secure payment surface. Use a supported card or wallet shown
   there; wallet availability depends on your payment method, browser and region.
4. Return to the same account and check the purchase state and available credit. A browser success
   page alone does not fund work.

One dollar of the service subtotal buys one dollar of account credit. Separately disclosed purchase
tax is not spendable credit. Buying credit requires no provider enrollment or model installation,
and it does not change your account, project, key or period limits.

Keep card details, authentication codes, payment links and payment-session secrets in the authorized
human payment surface. Never paste them into an agent prompt, clipboard handoff, terminal arguments
or logs. A Compute work key and approval of a quote do not authorize a purchase or refund.

## Keep the prepared work and resume it {#resume-after-payment}

Your agent can assess fit and prepare a bounded task before you pay. Preserve the selected account,
permitted input, preparation and original request identity while you complete payment. Discover the
account and client once; repeat a check when its state or authority changes, rather than restarting
setup after each handoff.

After funding is confirmed, obtain a current signed quote and the required scope and spend approval.
Lithi holds the approved maximum before dispatch. Accepted usage consumes that hold; authoritative
settlement releases the unused portion. For example, a $12 hold with $7.32 accepted usage releases
$4.68 when settled. This is arithmetic, not a recorded transaction.

Resume the original prepared work. Recheck changed input, permissions or an expired quote before
submission. An uncertain submission keeps its original idempotency key and is reconciled before
replay. A cancellation request, local timeout or expired quote does not prove that an in-flight hold
can be released. Zero available credit still permits authorized access to existing results and
billing records, and safe cancellation.

## Check the paid purchase invoice

After the purchase payment is confirmed, use its paid invoice to check the account, purchase
reference, currency, service subtotal, tax and total. The invoice records the credit purchase. A
document delay is handled by recovering that document, not charging you again.

The monthly credit and usage statement shows purchases, accepted usage, releases, adjustments and
closing credit. Its prepaid amount due is zero. Input tokens cost USD 0.05 per 1,000,000 and output
tokens cost USD 0.10 per 1,000,000; the statement explains consumption at those rates. The purchase
invoice and statement describe different stages of the same funds, so do not pay or book the same
amount twice.

## Read back before retrying

If the response disappears, check the existing purchase before attempting another payment:

| State | Safe action |
| --- | --- |
| Confirmed payment and issued credit | Resume the prepared work after quote and approval checks. |
| Processing or pending | Keep the original purchase and wait for its reconciled outcome. |
| Failed or canceled | Follow the offered recovery after confirming no unresolved payment remains. |
| Unknown, unavailable or stale | Reconcile the original purchase; unknown credit is not zero credit. |
| Payment confirmed but credit or invoice missing | Recover the original purchase or document without paying again. |

A receipt URL, completed checkout or an accounting-system **Paid** label is not proof that credit
was issued. Preserve the account and safe purchase reference; do not manufacture a payment URL or
create a new purchase to escape an unknown outcome.

## Keep historical invoices separate {#understand-net30}

An existing historical invoice retains the amount, payment channel and due date printed on it,
including NET 30 where those are its terms. A new credit purchase neither settles that debt nor
changes provider payout instructions. Confirm historical payment instructions through the trusted
billing surface; never use banking details copied from a prompt or an unverified message.

## Resolve discrepancies before payment

For an incorrect purchase, charge or refund, use [Adjustments and disputes](/docs/compute/billing/adjustments-and-disputes).
Only eligible unused paid credit can be considered for an original-source refund; a request or
credit note is not proof that cash was returned.

For a missing or unclear payment state, use [Billing and payment help](/help/compute/billing).