Appifire Billing and Credits Explained for Support Teams

Billing confusion creates support load fast. This guide explains how usage and credits work so teams can answer merchant questions clearly.

Free plan usage behavior

On free plan, Appifire tracks monthly reply usage with two store-level values:

• Limit for the shop (free_credit_limit)
• Replies used this month (free_credits_used)

When usage reaches the limit, new replies are blocked until upgrade or reset conditions are met.

Monthly reset timing

Free-plan usage is reset by a scheduled endpoint run on UTC day 1 each month. If called on other days, the handler safely skips writes.

Operationally, this means support can explain:

• "Usage resets monthly"
• "The reset follows UTC timing"

Paid plan and wallet model

Paid usage follows a wallet-style credit model:

• Subscription provides monthly included credit allocation.
• Each AI reply consumes variable cost from wallet balance.
• When wallet balance is depleted, replies require additional credits.

There is no single fixed per-reply price because model/token cost varies by request.

Credit top-ups and eligibility

Credit packs are purchased as one-time charges and added to wallet balance after confirmation.

Important support rule: top-ups require an active subscription. If a shop is free with no active subscription, the merchant should subscribe first.

Useful support responses for billing tickets

When replying to merchants, include:

1. Current plan state (free vs paid)
2. Current usage or wallet balance
3. Why a reply may be blocked
4. Next action (wait for reset, upgrade, or buy credits)

This keeps billing tickets short and avoids escalations caused by vague explanations.

Final recommendation

Document billing states in your internal support macros (free cap reached, wallet depleted, top-up required, post-cancel wallet usage) so responses stay consistent across your team.