Corporate Cards

Manage company cards with cardholder, spend limit, current spend, merchant controls, receipt status, and freeze or replace actions. This example brings Cards and Transactions together so finance and operations teams can find the next task without losing context.

It includes representative records such as Maya Chen · Product and Jon Bell · Sales. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Corporate Cards
Use this template in Figr

Template facts

Screen

Table

Primary action

Issue card

Pattern

Table

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 issue card while keeping active cards, spend this month and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Cards gives users an obvious place to start.
  • Supporting view: Transactions keeps the related context close.
  • Primary action: Issue card stays visible when people need it.
  • First signal: Active cards shows a useful value (84).
  • Second signal: Spend this month gives additional context (428k).
  • Sample record: Maya Chen · Product.
  • Next record: Jon Bell · Sales.

States worth designing

  • No rows in current filters: say what changed, protect progress, and offer a clear next step.
  • Sorting or bulk action in progress: say what changed, protect progress, and offer a clear next step.
  • Row update conflict: say what changed, protect progress, and offer a clear next step.
  • Bulk update partly failed: say what changed, protect progress, and offer a clear next step.
  • Restricted columns: say what changed, protect progress, and offer a clear next step.
  • Export complete: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Cards → Transactions → Issue card → Review outcome

Patterns used

Table, Cards, Transactions, contextual actions, error recovery

Why these choices work

Prioritize columns that help people act. Keep filters when readers drill into details and return; show who owns each unresolved exception.

Pay attention to cards and transactions. People need to distinguish Maya Chen · Product from Jon Bell · Sales. Keep active cards 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 “Issue card”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Treasury Dashboard, Expense Approval, Cash Flow Forecast.

Start from this in Figr

Design a corporate cards screen inside our existing product. Use our current components, tokens and content language. Include Cards and Transactions views, credible records like Maya Chen · Product, and a clear “Issue card” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr