Before adding more Fanfinity Coins, identify which balance you already have. A subscription allowance and separately purchased Coins follow different rules. Treating them as one permanent wallet can make a monthly reset look like an unexplained loss.
Fanfinity’s published terms describe two important distinctions: allowance Coins are used before purchased Coins, and unused subscription allowance does not roll over. This guide turns those rules into a record you can use with your own account. It does not quote a current plan price or claim to have tested a payment.
Draw two boxes before doing the arithmetic
Make one box for the current subscription month’s allowance and another for separately purchased Coins. Under each, record the balance shown, the date you checked it and the label used by the interface. A screenshot can help preserve that label, but crop out account identifiers you do not need.
Do not combine the boxes until you understand the event you are investigating. A new allowance month concerns one box. A separate purchase concerns the other. A generation request concerns spending. Changing a subscription may affect the allowance again.
| Record | What to write down | Why it helps |
|---|---|---|
| Subscription allowance | Current amount and next reset date | Distinguishes a refresh from a purchase |
| Purchased balance | Amount before and after a top-up | Shows whether the purchase arrived |
| Recent action | Action name, displayed cost and time | Connects a deduction to a request |
| Plan change | Old plan, new plan and effective date | Preserves the context of a new allowance |
Use a fictional ledger to expose a mistaken assumption
Suppose a fictional account begins a subscription month with 100 allowance units and 40 purchased units. After requests use 70 allowance units, its two boxes contain 30 and 40. These numbers illustrate the bookkeeping; they are not a Fanfinity offer or a feature’s actual cost.
If the next month replaces the allowance with a fresh 100, adding the old 30 to that new figure would be the wrong expectation. The purchased box requires a separate check. This example also explains why the total number alone is an incomplete record: the same total can be made from balances with different future treatment.
Use your own displayed values in the worksheet. Do not estimate a feature’s cost from another user’s screenshot, because a different action, offer or account state may be involved.
Keep the payment schedule beside the allowance schedule
A longer billing commitment does not automatically mean that every month of its allowance arrives as one permanent balance. Fanfinity’s terms describe a monthly allowance even when the selected subscription spans several months.
Create two calendar entries in your private notes: the next payment date and the next allowance reset. If the interface presents only one, record that limitation and ask support which event the displayed date represents. Avoid replacing missing information with a guess based on when you first registered.
Before changing plans, capture the current allowance and the proposed offer. Compare what becomes available now, what happens at the next allowance month and what will be charged later. A cheaper monthly equivalent does not answer those questions by itself.
Give each session a stopping point
Choose a task before you start spending: for example, a short fictional conversation or one visual concept. Record the cost shown for that action and decide how many attempts are worthwhile. Leave room to stop when a result is usable rather than treating the entire remaining balance as a target to consume.
If a request produces an unexpected result, write down what went wrong before submitting the same request again. A balance question, a service error and an unsatisfactory creative result need different explanations. Repeated submissions can obscure the original event.
Reconcile a discrepancy with four records
When a number does not make sense, assemble the before balance, the after balance, the action or payment receipt, and the date with timezone. State whether the discrepancy concerns allowance or purchased Coins. Ask the vendor to reconcile that event instead of sending a vague report that “my credits vanished.”
Keep the original receipt privately and share only the necessary reference through an official support route. A full card number, password or unrelated conversation history is not useful evidence for a basic balance question.
Your next step is small: record the two boxes and the two dates before making another purchase. That provides a better starting point than trying to reconstruct a month of activity from one total.