Credit system module

FastStaq includes an optional credit system for usage-based products: grant credits, deduct them on actions, and show balances and history. It is fully built but easy to leave off if your product does not need it.

Note: this sales site does not expose credits to buyers, because credits are not relevant to selling a boilerplate. The full module still ships in the code you receive, ready to enable for your own product.

What the module provides

• Credit balances per user (and per workspace when multi-tenancy is on).
• Atomic transactions with optimistic concurrency so balances never go negative or double-spend under load.
• A transaction ledger recording every grant and deduction with a type, amount, before/after balance, and metadata.
• Admin grants and an automatic yearly drip worker (CREDIT_DRIP_CRON).

Common operations

• Grant credits when a user signs up, upgrades, or as an admin adjustment.
• Deduct credits when a user performs a billable action; the deduction is rejected if the balance is insufficient.
• Read the balance and ledger to power dashboards and usage meters.

New admins created with the CLI start with a pool of credits so you can test the flow immediately.

Wiring it into your product

1. Decide what action consumes credits and how many.
2. Call the credit deduction in your feature's service before performing the work.
3. Surface the balance in your UI using the existing endpoints and hooks.

Turning it off

If your product is flat-rate or one-time (like this sales site), simply do not surface credit UI and do not deduct credits. The module stays dormant with no impact.

Related articles

• Billing and subscriptions module
• Background jobs and observability

Still need help?

Open a support ticket for help wiring credits into a feature.