Skip to main content

Partner billing and TCU

Metering

Postpaid TCU — per-context visibility, forecasts, and invoices for trust producers.

Audience: trust producers reviewing usage, forecasts, and invoices.

Outcomes​

  • Read TCU this period and USD estimate in Partner Operations
  • Split usage by operation (ingest vs recompute) and context
  • See MTD TCU per context via trust-contexts and billing APIs
  • Understand quota soft alerts and sandbox waive tiers

Trust producers are billed after usage (postpaid) in Trust Compute Units (TCU). TCU measures compute and ingest work attributable to your partner profile — with breakdowns by operation, trust context, and ingest channel (webhook, API, CSV).

What you see in the hub​

WidgetMeaning
TCU this periodRunning total for the open billing period
USD estimateProjected invoice from contract rate
ForecastEnd-of-period projection if current burn continues
Quota statusOK / soft alert / processing paused
BreakdownBy operation (ingest vs recompute) and by context

Surfaces: Partner operations, Pulse (producer mode), institution shell topbar TCU badge (sandbox tiers show label).

What consumes TCU​

OperationTypical trigger
Event ingestWebhook, API, or CSV row accepted into the pipeline
Score recomputeTrust refresh after signals update for a subject/context

CSV batches show estimated TCU in the upload studio before confirm; actual TCU is recorded on the batch when processing completes.

Per-context attribution​

Multi-context partners see TCU split by context_id — so merchant load does not obscure lending burn.

API (session):

  • GET /institution/<slug>/api/partner-operations/billing/tcu/?context=merchant
  • GET /institution/<slug>/api/partner-operations/billing/tcu/breakdown/ — context × operation matrix

Invoices​

Recent invoices appear in Partner operations with amount, status, and due date. Payment methods and contract terms are managed in Billing.

Sandbox plans may not charge TCU during integration testing.