Need help? Check our guides or contact support.
Wallets & billing
ikigize uses two wallet types: one per user and one per organisation. Campuses, courses, sessions, and tasks do not have their own wallets. Instead, hosting and storage costs for those entities are billed to whoever owns them (a user or an organisation), and AI usage is always charged to the user who triggered it.
User wallet
Every ikigize account has a personal wallet. It receives a free monthly token allocation and can be topped up with purchased tokens.
AI: Token-consuming AI features (agents, embeddings, etc.) debit your user wallet. If you belong to an organisation that offers coverage, part of that spend may be subsidised from the organisation wallet up to the limits your admins configure — your wallet screen shows your spend and any coverage that applies.
Hosting & storage: If you personally own a campus, course, session, or task, ongoing hosting and library storage for those entities are charged to your wallet as part of monthly billing.
Organisation wallet
Each organisation has one wallet. Admins purchase token packages and can allocate tokens to member user wallets — not to separate campus or course wallets.
Hosting & storage: When the organisation owns a campus, course, session, or task, the corresponding hosting and storage charges accrue to that entity’s bill and are paid from the organisation wallet.
Member support: Organisations can set default monthly and daily allocation limits for members and adjust limits per member. Optional coverage for member AI spend (within caps) may also use the organisation wallet when configured.
How charges work (not a four-step chain)
There is no “course → campus → organisation → user” walk for AI. The platform uses separate rules for AI vs infrastructure:
User wallet
Every account has a personal balance (free monthly grant + purchased tokens). AI usage debits this wallet. Hosting and storage for entities you own are also charged here.
Organisation wallet
Organisations buy tokens and allocate them to member user wallets. Bills for hosting and storage attach to the owner of a campus, course, session, or task — when the owner is the organisation, costs come from this wallet. Optional member coverage for AI spend can also draw from here, within limits.
How billing paths differ
AI
Charges post to the user wallet. If your organisation subsidises members, a portion may be paid from the organisation wallet according to your plan and limits — not by walking through campus or course wallets.
Hosting & storage
Each campus, course, session, and task has an owner (user or organisation). Ongoing costs accrue to monthly bills for that entity and are paid from the owner's wallet. Public resources can split cost across libraries; each share still settles against the relevant owner wallet.
Your wallet shows an estimated monthly total that combines hosting, storage, and recent AI usage so you can budget — exact debits still follow the rules above.
Free vs. purchased tokens
Every user receives a free monthly allocation of tokens that resets at the start of each billing cycle. Unused free tokens do not carry over. Purchased tokens, on the other hand, never expire — they accumulate and roll over month to month.
When a wallet is charged, free tokens are always consumed first. Purchased tokens are only drawn on once free tokens are exhausted.
| Feature | Free tokens | Purchased tokens |
|---|---|---|
| Monthly reset | Yes | No |
| Carry over | No | Yes |
| Expires | Monthly | Never |
| Used first | Yes | After free tokens |
What happens when a wallet is empty?
If your user wallet cannot cover an AI charge (and no applicable organisation coverage applies), that AI feature is temporarily blocked. Core platform features — course access, task management, reading content — remain fully available. You can purchase tokens or receive an allocation from your organisation to restore access.
If an organisation wallet cannot cover its hosting or storage obligations, affected paid features may be limited until the balance is restored.
Uploads are blocked (not deleted) if storage billing cannot be covered. Existing files remain safe.
Next steps
- AI Token Usage — what AI operations cost and how the price is calculated
- Storage Billing — how storage costs are tracked and split
- Allocation & Limits — allocating from an organisation wallet to members and setting limits