Yield and fee accounting
Reconcile share value, accrual, positions, fees, and lifecycle events from canonical Torq state.
Torq does not expose a usage-billing product. The equivalent developer problem in tokenized credit is continuous, exact reconciliation of capital, shares, accrued obligations, realized fees, and position lifecycle. These resources are available to approved Developer Preview applications.
Canonical sources
| Question | Read from |
|---|---|
| What does a customer own? | Positions, tranches, vault holder performance, share holdings |
| What is the vault state? | Vaults, vault snapshots, portfolio holdings, liquidity, exit terms |
| What fees exist? | GET /v1/fees and the current vault fee configuration |
| What changed? | Activity, signed events, transaction tracking, canonical block freshness |
| Can the customer act? | Eligibility, wallet-scoped authority, current lifecycle state |
Accounting rules for integrators
- Treat all asset and share amounts as base-10 integer strings in the asset's smallest unit.
- Do not calculate product-visible balances from event totals alone.
- Do not treat an emitted fee event as proof that unrelated fee buckets and positions are unchanged.
- Preserve the resource freshness object and request ID with every reconciliation decision.
- After a webhook, reread the affected canonical resources before updating a customer ledger.
- Model queued redemption, restricted mobility, recovery claims, and fee claims as lifecycle state, not as immediate cash.
Reconciliation loop
Signed event -> durable inbox -> deduplicate -> canonical API read -> local ledger transactionIf event state and canonical state disagree, stop customer-visible settlement and retain the Torq request ID, event ID, delivery ID, chain ID, and transaction hash for support. Never log credentials, wallet signatures, or webhook secrets.
Use Resource APIs, Events, and Compatibility to bind the integration to current schemas.