Skip to main content

Consumer portal — screen specifications

Status: Proposed MVP UX contract; consent copy and payment-network rules need review.

Overview, Upcoming Bills, Merchants, Payment Methods, Payment History, Notifications, Profile and Help. Mobile-first; plain language and accessible error states.

C01 — Invitation and account linking​

  • Display inviting merchant identity, reason for invitation, Sparelane role and link expiry.
  • Actions: create account, sign in, verify email/mobile where required, confirm merchant link.
  • Inputs: verified contact details and an additional signed/challenge-based linkage factor.
  • Validation: expired/used invitation, account mismatch, revoked merchant invitation, throttled verification.
  • Acceptance: matching an email address alone never links an unrelated merchant's customer record.

C02 — Overview​

  • Cards: next expected collection, upcoming bills, active merchant relationships and actions required.
  • Upcoming list: merchant, amount, bill due date, planned collection date, selected masked method and status.
  • Alerts: expired method, inactive mandate, failed payment, authentication action.
  • Acceptance: never imply payment has completed when only scheduled or processing.

C03 — Merchant relationship detail​

  • Merchant identity, mandate status, authorisation scope, consent date/version, next bill, recent collections and support details.
  • Actions: review mandate, change authorised preference, revoke authorisation, contact merchant.
  • Acceptance: changes affect only this merchant unless consumer explicitly chooses otherwise.

C04 — Payment methods​

  • Add method through provider-hosted tokenisation, view brand/type and masked suffix, expiry/status, remove or replace.
  • Show linked merchant mandates before removing a method.
  • Acceptance: raw card data never reaches Sparelane application servers or logs.

C05 — Primary and backup preferences​

  • For a selected merchant: reorder eligible methods, choose primary, optionally enable backup, review consequences.
  • Validation: active mandate covers methods, no duplicate preference rank, eligible method status.
  • Acceptance: adding a method globally does not automatically authorise its use by another merchant.

C06 — Bill and payment detail​

  • Bill amount, merchant, due date, scheduled attempt date, current collection status and timeline.
  • Show attempt history at consumer-safe level; distinguish failed attempt from exhausted recovery.
  • Actions: update eligible method, view support route, access payment confirmation where available.
  • Acceptance: no display of internal risk codes, sensitive provider IDs or unsupported guarantee language.

C07 — Mandate review and revocation​

  • Clear authorisation scope, covered payment methods, fallback rules, effective dates and merchant identity.
  • Actions: affirm consent, download/view terms version, revoke future authorisation.
  • Confirmation warns that already-submitted attempts may still settle and merchant obligations may remain.
  • Acceptance: revocation event is immutable and blocks future initiation.

C08 — Notifications, profile and recovery​

  • Notification preferences, verified contact details, security settings, account recovery, device/session review, complaints and support.
  • Sensitive profile changes require verification and rate limits.
  • Acceptance: optional marketing choices are separate from essential service notices.

Accessibility and content standards​

Target WCAG 2.2 AA; keyboard navigation, screen-reader labels, accessible errors, colour-independent statuses, mobile tap targets and date/currency clarity. Do not ask for sensitive payment information in email/SMS messages.