Skip to main content
Credits are the abstract unit of value inside Jaza. Customers purchase them with real money (Mobile Money or card, via Jaza) and spend them on features your app provides.

What credits are

  • Integer-only — whole numbers only; no fractional credits.
  • App-scoped — meaning comes from your bundles (how many credits a top-up buys) and features (how many credits an action costs) in the dashboard.
  • Held on a per-customer wallet in sandbox or live.

How credits map to money

Money enters when a customer tops up. Bundle pricing in the dashboard determines how many credits they receive. Jaza collects local currency via Mobile Money, credits the wallet, and settles USD to you — you do not run FX or aggregator ops yourself.

How credits map to features

After a customer has credits, your backend spends them with jaza.consume(): Use the override for variable metering — for example AI token usage where cost depends on the request:

Lifecycle

  1. Purchase — user opens top-up UI, picks a bundle, pays with MoMo.
  2. Credit — Jaza records a ledger credit and increases the wallet.
  3. Spend — your backend calls consume with featureCode (and optional credits) + idempotencyKey.
  4. Audit — movements stay in the append-only ledger.

Next steps