MMS Features Document v2.5¶
Summary: High-level feature overview of the Merchant Manager System (MMS) — a centralized web platform for managing payment terminals, merchants, and companies — covering existing, in-development, and planned features with their delivery status.
Source: raw/specs/MMS features v2.5.pdf (web: MMS → Source PDFs)
Source PDF pages: 1–57 (of raw/specs/MMS features v2.5.pdf). Printed footer page numbers match PDF page numbers 1:1. Revision date on cover: 2026-05-24.
Status: approved
Scope¶
A stakeholder-facing overview of MMS capabilities. The system centrally manages payment terminals, with terminal configuration, application/firmware deployment, template-based setup, and role-based access control by company and job role. Eight top-level feature areas are described, each with a description, key capabilities, reference images, and delivery status.
Out of scope¶
Detailed technical specifications and implementation details are explicitly out of scope for this document (stated in the Introduction, p.4).
Feature areas (→ pages)¶
| # | Feature | Status (per doc) | Source pages | Page |
|---|---|---|---|---|
| 1 | Login & User Authentication | Completed | 6–7 | shipped |
| 2 | App Manager | Completed | 8–11 | shipped |
| 3 | Cloud Security | Completed | 12–15 | shipped |
| 4 | Stakeholders | Completed | 16–27 | shipped |
| 5 | Device Manager | Mostly complete; Location Tree in progress | 28–49 | in-development |
| 6 | Global Setup | Completed | 50–54 | shipped |
| 7 | Audit Log | Completed | 55–56 | shipped |
| 8 | Bulk Changes | In progress / Design UI — EST 2026-05-31 | 57 | in-development |
Key requirements¶
- Centralized terminal lifecycle management — setup, configuration, maintenance (p.5).
- Company and merchant management with hierarchical relationships (p.5).
- Centralized deployment of applications, firmware, and configuration templates to terminals (p.5).
- Role-based access control, with permissions defined by company and job role (p.5).
- Web-based interface for administrators and operational users (p.5).
Open questions¶
- [ ] Per-feature owners are not specified in the document — confirm who owns each feature area.
- [ ] Bulk Changes (§8) shows EST 2026-05-31 for both sub-modules — confirm whether this date still holds.
Risks and unknowns¶
- Status values in the source are informal ("Completed", "Complete", "In Progress", "Progress - EST", "Design UI - EST"); mapped to vault feature status vocabulary on each feature page.
Affected features¶
- login-user-authentication
- app-manager
- cloud-security
- stakeholders
- device-manager
- global-setup
- audit-log
- bulk-changes
Related decisions¶
- (none yet)
Change history¶
- 2026-05-27 — initial ingest from
raw/specs/MMS features v2.5.pdf; created 8 feature pages.