Trust Center
Quotes, limits and billing
See how a Compute quote becomes an accepted charge, which spend limit governs it, and which record proves your payment status.
On this page
Lithi Compute billing answers one question: what does your account owe, and which record proves it? Mercury is the sole Lithi Compute billing and payout rail, and customer invoices use USD NET30 terms. A human payer links or verifies a bank and approves each ACH debit in a hosted Mercury flow.
From preview to quote to charge
A free preview carries no account, is non-authorizing, and cannot start a run or a batch. It reserves no budget or capacity and creates no receivable; a preview digest is evidence and convenience, never authority for a price or a charge.
An authenticated quote re-reads current service, pricing, availability, account, limits, data profile, jurisdiction, policy, and expiry before it becomes chargeable. Only an accepted quote or batch can reserve capacity and create billable work, and it does so under the exact terms it names, not the terms shown in an earlier preview.
What this means for you
Customer billing and Mac-provider earnings are separate subledgers. Lithi never nets, offsets, or credits one against the other. Buying Compute and sharing Macs may coexist under one identity or organization, but each grant remains independent; see provider allocation and settlement for that boundary.
Billing, Finance, Owner, and IT permissions do not imply one another. The signed-in Compute account shows metadata for the grants you hold. It does not turn a screen label into payment proof.
The current Mercury invoice GET/read-back establishes customer payment truth. Review that record for the account, organization, period, currency, amount, due date, and payment state. Keep the invoice reference when you ask for help. An external finance system's Paid value is an annotation only; it cannot replace that invoice read-back.
Claim record
| Field | Record |
|---|---|
| Scope | Lithi Compute preview, quote, and customer billing authority, spend ceilings, and payment status. |
| Status | Account-specific; this public page does not establish a payment state. |
| Owner | Lithi Compute billing and finance authorities. |
| Evidence | Current Mercury invoice read-back, and the signed quote and limits that applied to the accepted work. |
| Last reviewed | 2026-09-03 |
| Limitation | A public page or external finance label does not prove settlement. |
Authority table
| Record or event | What it establishes |
|---|---|
| Current Mercury invoice GET/read-back | Customer payment truth for the named invoice. |
| Mercury hosted ACH flow | The human payer's bank verification and approval for each debit. |
| Effective spend ceiling | The lowest signed ceiling across account, organization, member, API key, accepted quote, batch, and reservations. |
External finance Paid value | An annotation only. It cannot settle a Lithi invoice. |
Limits or open status
At D+1 past due, new chargeable reservations stop. At D+14, finance review starts. At D+30, the account enters suspended_nonpayment. Accepted work and recovery reads remain available where the signed account state permits; a suspended state does not restore authority on its own.
The effective spend ceiling is not a value you can safely infer from a page or screen; the narrowest signed rule wins. This page cannot invoice, debit, refund, change a limit, or confirm settlement.
For a cancellation or a billing dispute, share the account and invoice reference and describe the mismatch; do not send card data, bank details, credentials, or identity documents. Lithi does not store your finance OAuth token, API key, bank details, verification code, or mandate secret. Use payer banking details only inside the hosted Mercury flow.
Primary action
Sign in to review invoice metadata for your account. That view helps you find the current record; it is not, by itself, proof that payment settled.