What gets recorded
Typical movements include:
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.