It is unclear whether an invoice is paid

Do not make a second payment yet

You attempted a credit purchase or payment of a historical Compute invoice, but the result is unclear. Keep the purchase or invoice reference and check the latest authorized view for the same account. Record when you read the payment and credit state. Unknown credit is not zero credit.

A browser confirmation, bank instruction, or finance-system label is not enough to establish the reconciled Lithi payment state.

Read the actual status

Processing: collection has not been confirmed as paid. Do not repeat the payment while the first transfer is unresolved.

Paid: verify that the status belongs to the intended invoice and current account. Compare any remaining discrepancy with the actual invoice record.

Payment confirmed but credit or invoice missing: recover the original purchase or document. Do not buy again to clear the discrepancy. Resume the prepared job only after the same account confirms funding, with a current quote and the required approval.

Unpaid, Sent, or Overdue after an attempted transfer: ask for that transfer to be reconciled. Do not assume the attempt failed merely because the displayed invoice has not changed.

Unavailable, missing, or stale information: keep the payment outcome unknown. A failed read is not a zero balance or a failed transfer.

Cancelled invoice or conflicting records: stop and ask which invoice and collection instruction apply before taking further action.

Use the authorized payment channel

Use the secure human payment step offered for the selected account. Historical invoices keep their verified payment instructions and original terms. Do not construct a payment URL from an invoice ID. Keep card details, authentication codes and payment-session links out of prompts, clipboard handoffs, terminal arguments and logs.

A paid purchase invoice records the credit purchase. A monthly prepaid usage statement has zero amount due and does not request another payment. A delayed document does not authorize another charge.

A Compute work key, model answer, or finance export does not authorize a debit. A paid annotation in an external accounting system does not replace the payment provider's reconciled status.

Request reconciliation safely

Use Contact Lithi with the invoice reference, amount, currency, attempted payment time, latest displayed state, and a safe transfer reference when available. Say that a payment may already have been initiated.

Do not include account or routing numbers, full bank statements, authentication codes, credentials, or private payloads. Success is a current reconciled outcome for the intended invoice. Until then, keep the first payment unresolved rather than creating another one.