Skip to main content

UX navigation and acceptance framework

Status: Proposed design-system and delivery contract for merchant, consumer and admin interfaces.

Experience map​

Reusable components​

PageHeader, StatusBadge, MoneyAmount, LocalDateTime, MerchantScopeSelector, FilterBar, DataTable, EmptyState, ErrorState, Timeline, ConfirmDialog, SensitiveActionChallenge, AuditHistory, MaskedPaymentMethod, MandateSummary and ExportMenu.

StatusBadge must distinguish scheduled, pending, confirmed, settled, payout eligible and paid out. Avoid a single ambiguous 'Paid' label.

Standard page states​

Every data page needs loading, empty, partial, stale, error, forbidden and success states. Financial actions need an additional unknown/pending-provider state; timeout must not imply failure.

Form rules​

Validate on both client and server. Display amounts with AUD currency and exact cents. Date/time inputs must clarify the merchant's business timezone and cutoffs. Use field-level errors, confirmation for destructive actions and safe retry messages. Never expose internal database IDs as consumer-facing references.

Screen specification template​

For every page or modal, record:

  1. Route and allowed roles.
  2. User goal and entry points.
  3. Data sources, field definitions and formatting.
  4. Actions, server-side validation and state transitions.
  5. Empty/loading/error/permission/unknown-outcome states.
  6. Audit, notification and webhook side effects.
  7. Accessibility and responsive behaviour.
  8. Acceptance tests, including cross-tenant negative tests.

Release definition of done​

Approved UX copy; API contract; RBAC tests; audit coverage; monitoring; loading/error states; keyboard and screen-reader testing; responsive checks; integration tests; financial idempotency tests where relevant; support documentation and rollback procedure.

Explicit design questions​

Merchant multi-entity support, consumer partial payments, invoice/bill dispute entry points, native mobile app versus responsive web, supported identity verification method, merchant self-service onboarding and operational approval thresholds.