Credits and Pricing

Credits are the internal currency between you and your resellers. You decide what a credit costs in real money — the panel keeps the score, and it keeps it completely.

How credits move

In: you top up a reseller’s balance — on their account or in bulk — always with a reason attached.

Out: the reseller sells. Creating a line against a package debits the package’s credit price automatically; a trial debits the trial price, if any. There is no other way content leaves the building, which is what makes the model airtight: no credits, no sales.

Down the chain: a reseller entitled to sub-resellers passes credits downstream from their own balance — your ledger with them is untouched by how they split it.

The audit trail

Two logs make every balance explainable:

• Credit logs — every movement: date, who adjusted, whose balance, amount and reason.
• Reseller logs — every sale: what was created, the package used, the cost, and the balance remaining after.

When a reseller disputes their balance, the answer is a filtered log, not an argument. Both export as CSV for your bookkeeping.

Pricing strategy lives in packages

Credits themselves are neutral — the pricing decisions are the credit costs on your packages, tiered by the groups they are granted to. Sell the same bouquets at different credit prices to different tiers, and the margin structure of your whole operation is three screens: groups, packages, credits.

Programmatic top-ups and balance checks are adjust_credits and user_info on the Admin API — the hook for billing systems that sell credits for real money. Next: the servers that actually deliver all of this — load balancers.