Skip to main content
Jaza records every credit movement in an append-only ledger. Top-ups and consumes produce history you can inspect in the dashboard and surface in your app with JazaLedger.

​
What gets recorded

When you call consume with a featureCode, the ledger entry stores that code in metadata — even if you also pass credits to override the debit amount. That keeps analytics and activity attributable to the right feature. Each consume should carry an idempotency key from your backend so retries do not double-charge.

​
Why it matters

  • Trace a balance back to purchases and feature usage.
  • Safe retries with idempotency.
  • Dashboard analytics and credit activity stay consistent with what the SDKs report.

​
Next steps