Skip to main content

Read USD Service Credits

USD Service Credits are the only customer balance. They are a non-transferable prepaid claim against Liskov service, not a bank account, stablecoin, crypto token, or withdrawable wallet.

Customer funding is release-gated

Plan selection, terms acceptance, Stripe checkout, and issuance of new Service Credits are not yet supported customer flows. Current production acceptance is limited to internal first-party organizations that are already pre-funded. Do not submit payment details or call an internal funding endpoint.

Read the balance​

The Console Billing & funding page shows the balance as an equation:

  • Settled — counted ledger rows only;
  • Held — open reserves, review holds, and purchased-credit refund holds; this value is set aside, not charged;
  • Available — settled minus held; what a new deploy may draw on;
  • Promo — promotional credit inside available, spent first and never refundable;
  • Refundable — unused purchased value after existing holds.

The Ledger page is the line-by-line audit trail, including the running balance after each counted row. A reserve, review hold, or released reserve does not move that running balance. Each row's amount is written exactly, to six decimals, so a charge smaller than a cent can leave the running balance, written to the cent, unchanged; see How amounts are written.

On an Application's Executions detail page, This spend window shows Charged so far for that Application over the rolling last 30 days. The number of turns describes the same window. It is the ledger's total for the Application, so it may include other executions; use Service credits on the page for this execution's own amounts. Reserved, not charged and Headroom show a dash when the ledger does not report a period reserve total or a cap. A measured zero charge is shown as $0.00; a missing or failed read is unavailable, not zero. This execution's own amounts are written exactly, to six decimals; see How amounts are written. Opening the page does not move Service Credits.

The release-gated refund flow sets aside purchased credit when a refund is accepted. That value cannot also pay for a deployment or platform usage, or fund another refund. The Ledger shows a Refund hold until the payment outcome is confirmed. Success replaces the hold with one refund debit; a confirmed failed or canceled refund releases it. An uncertain outcome keeps the value held while it is reconciled. Promotional credit is never refundable.

CLI reads are also available:

proof liskov organization service-credits ORGANIZATION_ID
proof liskov organization billing ORGANIZATION_ID

These commands are read-only.

The billing projection and transaction history are authoritative for the selected organization. A visible plan or checkout control does not change the release classification. If a control is disabled or unavailable, do not seek an internal workaround.

Checkout availability is reported by the server. A temporary pause stops new card purchases while already-paid purchases continue through verification. Existing Service Credits and billing history remain available. A successful redirect alone does not prove credit issuance; verify the ledger.

The billing read retains addFunds.checkoutAvailable and adds addFunds.checkoutAdmission with enabled, configured, available, and reason. Use proof liskov organization billing ORGANIZATION_ID --json to inspect these server fields. If an older server omits them, that response does not report Checkout availability. A displayed balance alone does not prove that purchases are enabled. These readbacks do not remove the release gate.

The release-gated Checkout contract treats the amount entered as the pre-tax Service Credit face value. Stripe calculates applicable VAT from the customer's billing details and shows subtotal, tax, and total before payment. VAT is collected separately: it never becomes Service Credit and never increases what an organization can spend.

Liskov uses its treasury to settle Acurast reward and network fees. You do not deposit ACU or USDC, manage an Acurast wallet, perform a swap, or withdraw the underlying settlement assets.

Spend on the Applications pages​

The Console's Applications pages show settled spend per Application. Both figures count the same settled ledger rows that name the Application: compute (deploy_spend), deployment fees (deployment_fee), and platform usage (usage_charge). They differ only in the period they cover:

  • Spend 30d, on the list of current and retiring Applications, covers the trailing 30 days.
  • Lifetime spend, in the retired Applications archive, covers the retired Application's whole retained history.

Neither figure includes Held value. Open reserves and review holds are set aside, not charged, and a released reserve was never charged. Organization charges that name no Application are counted in the organization's balance and ledger but in no Application's spend. Each column appears only when your role can read the organization's billing.

$0.00 means the ledger recorded the Application and settled nothing for it in that period. Not reported means the ledger has no record that names the Application, or the read failed. It is not zero. Opening either page is read-only and does not move Service Credits.

How amounts are written​

Liskov holds every Service Credit amount to the micro-dollar, one millionth of a US dollar. The Console writes an amount in one of two ways, depending on what it is, not on how large it is:

  • A balance, grant, purchase, or total — such as Available, a period's spend, or an Application's Spend 30d — is written to the cent, rounded to the nearest cent: $26.80. When it is not zero but under one cent, it is written exactly instead: $0.000612.
  • One execution, one ledger row, one hold, or a per-job price is written exactly, to six decimals: $0.000902 or $1.250000. The digits past the cents are in a lighter colour, so the dollars and cents still read first.

A column of amounts in a table takes one precision. If any non-zero amount in the column is under a cent, the whole column is written to six decimals, so the figures line up.

Zero and missing figures are never confused:

  • $0.00 is a measured zero: the figure was read and it is zero.
  • A non-zero amount is never written as $0.00, however small it is.
  • Not reported, or a dash, means there is no figure: nothing was recorded, or the read failed. It is not zero.

Verify​

Confirm the organization ID, available/reserved/used amounts, transaction history, and displayed currency. If a read appears stale or belongs to the wrong organization, use Sign-in, organization, and Service Credit reads.