Credit Balance

Track prepaid credits, promotional balance, expirations, recent deductions, and expected usage against the current balance. This example brings Balance and Transactions together so account administrators can find the next task without losing context.

It includes representative records such as AI generation usage and Figma export usage. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Credit Balance
Use this template in Figr

Template facts

Screen

Workspace

Primary action

Add credits

Pattern

Workspace

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Finance and operations teams need to add credits while keeping available, promo credits and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Balance gives users an obvious place to start.
  • Supporting view: Transactions keeps the related context close.
  • Primary action: Add credits stays visible when people need it.
  • First signal: Available shows a useful value (18,420).
  • Second signal: Promo credits gives additional context (3,000).
  • Sample record: AI generation usage.
  • Next record: Figma export usage.

States worth designing

  • First-use empty state: say what changed, protect progress, and offer a clear next step.
  • Data panel loading: say what changed, protect progress, and offer a clear next step.
  • Stale status or conflict: say what changed, protect progress, and offer a clear next step.
  • Action completed: say what changed, protect progress, and offer a clear next step.
  • Insufficient permission: say what changed, protect progress, and offer a clear next step.
  • Network retry: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Balance → Transactions → Add credits → Review outcome

Patterns used

Workspace, Balance, Transactions, contextual actions, error recovery

Why these choices work

Give the main job visual priority, keep supporting signals nearby and surface exceptions where people must act.

Pay attention to balance and transactions. People need to distinguish AI generation usage from Figma export usage. Keep available visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add credits”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Seat Management, Trial Expiry, Billing History.

Start from this in Figr

Design a credit balance screen inside our existing product. Use our current components, tokens and content language. Include Balance and Transactions views, credible records like AI generation usage, and a clear “Add credits” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr