Skip to content
AppDues
Log in
Contact salesSign up

Launch an in-app coin or credit system

In-app currency lets you sell packs of coins, credits, or tokens, grant recurring refills through subscriptions, and manage balances across platforms.

This guide explains the main models, the operational rules that matter, and what to check before choosing a system.

Three common currency models

Most implementations combine three patterns. First, one-time packs: users buy credits, points, or tokens alongside a subscription. Second, recurring grants: a subscription includes a monthly refill of currency. Third, expiring balances: unused currency expires at the end of a cycle. A system that supports all three can handle simple coin packs and more complex hybrid models without separate billing workarounds.

What to track operationally

A currency system needs more than a number in a database. You need to track the customer balance, the source of each grant, expiration dates, prorated grants when a product changes, and a transaction log for troubleshooting. The dashboard view should let support and finance see balances and transaction history without digging through separate systems.

Decision checklist before you build

Use this checklist to scope the work:

  • Will users buy one-time packs, receive subscription refills, or both?
  • Should unused currency expire at the end of a billing cycle?
  • How will you prorate grants when a user changes plans or has a billing issue?
  • Do you need the same balance behavior on iOS, Android, and web?
  • Where will support staff view balances and transaction history?
  • Are purchase and balance events logged for troubleshooting?

Worked example: monthly refill with expiration

Suppose a subscription includes 100 credits per month, and unused credits expire at the end of each cycle. A user who subscribes mid-cycle should receive a prorated grant rather than a full 100. If the user upgrades or downgrades, the grant should adjust to the new product. If a billing issue occurs, the system should handle the grant according to the same proration rules. The transaction log should show the original grant, any adjustment, and the expiration event so support can explain the balance.

ConfigureTargetTest

Use cases beyond simple coin packs

In-app currency can power usage-based and AI features, where users pay for resource-heavy or metered actions with credits. It can also support hybrid subscriptions, where subscribers buy add-ons or usage bundles without messy billing workarounds. And it can power in-app actions and unlocks, such as coins, boosts, and lightweight feature unlocks, while keeping balances and expirations consistent.

What to verify before adopting a vendor

Ask whether the system handles one-time packs, recurring grants, and expiration in the same product. Confirm cross-platform behavior across Apple, Google, and Stripe, and ask how purchase and balance events are logged. Check whether prorated grants are automatic or require custom code. Finally, confirm how support staff view balances and transaction history, and whether the dashboard is included or a separate add-on.

Frequently asked questions

Can in-app currency be sold alongside a subscription?

Yes. One-time packs of credits, points, and tokens can be sold alongside subscriptions, and subscriptions can include recurring currency grants such as monthly credit refills.

Can unused currency expire?

Yes. Automatic expiration can be set for unused currency at the end of a cycle.

How are prorated grants handled?

Prorated grants based on product changes and billing issues can be handled by the system rather than custom code, but the exact rules should be confirmed with the vendor.

Does in-app currency work across iOS, Android, and web?

Cross-platform behavior across Apple, Google, and Stripe is part of the intended capability, with purchase and balance events logged for visibility and troubleshooting.