Appearance
How Mintage is built โ
A map of Mintage for developers, implementers and support staff. Enough to find your way around the code and talk to the people who built it.
The big pieces โ
Browser
Vue 3 single-page app
โ
API
Laravel, one per company
โ
Calculation engine
NSGI packages
โ
Company database
one per tenant
| Layer | Technology | Repository |
|---|---|---|
| Front end | Vue 3, Vite, PrimeVue components, Pinia state, vue-i18n (English + Spanish), real-time socket client | mintage-front |
| Back end | Laravel (PHP), organised into modules (Modules/*) | mintage |
| Domain packages | packages/NSGI/{Core, Employee, Employer, Builder, Compute} โ the payroll model and maths | mintage |
| Background work | Laravel queues: closing payroll, rebuilds, imports, exports, email/WhatsApp delivery | mintage |
| Real time | WebSocket events push row updates and progress (close, rebuild, import) to every open browser | Socket module |
| PDFs | HTML templates rendered by WeasyPrint servers, with failover | Remuneration |
| Sign-in | Stytch (magic link, password, TOTP) and Microsoft Entra ID single sign-on | Stytch, Consent |
One company = one tenant โ
Each customer company is a with its own database and configuration: country, currency, enabled modules, sign-in method, integrations. Tenants run the same code; several share a server. The single web front end works out which tenant's API to call from the address it was opened on.
Users, roles, employees and settings all belong to one tenant. Tenants only talk to each other through explicit, credentialed machine clients โ for example to move an employee between companies (Exchange) or edit linked payrolls together.
Inside the back end โ
mintage/
โโโ Modules/ โ features, each with routes, controllers, jobs, migrations
โ โโโ Remuneration/ โ the payroll: grids, editing, close, net guard, exports
โ โโโ Settings/ โ company set-up, fields, tax versions, proration
โ โโโ Consent/ Stytch/ โ users, roles, sign-in
โ โโโ Epayslips/ โ payslip delivery
โ โโโ LoanManager/ Import/ AgentGateway/ โฆ
โโโ packages/NSGI/
โ โโโ Core/ โ shared models, rounding, resolvers
โ โโโ Employee/ Employer/ โ people, loans, children, employment events
โ โโโ Builder/ โ orchestrates a payroll rebuild (gross โ deductions โ net)
โ โโโ Compute/ โ pure calculators: PAYE, NIS per country/year/frequency
โโโ app/ โ console commands, shared servicesThe full list is in the modules catalogue, and the maths in the calculation engine.
Inside the front end โ
mintage-front/src/
โโโ pages/ โ file-based routes
โ โโโ monthly/ bi-monthly/ fortnightly/ weekly/ โ payroll, nis, paye, loans, import, exportโฆ
โ โโโ team-members/ settings/ customization/ tools/ analytics/ resources/
โโโ components/Payroll/ โ the grid, toolbar, exports, imports, timesheet
โโโ components/Dialog/ โ cell editors, Net Guard, Finalize Payroll, Adjust Net Pay
โโโ logic/ โ navigation, role permissions, page access
โโโ locales/ โ every user-facing label (en / es)The sidebar menu (logic/navigation.ts) is the single source of truth for page access: each item can require a permission, a role or a company option, and a page hidden from the menu shows No access if opened directly.
Life of one edit โ
๐ฑ๏ธ
Step 1 of 4
A user edits a cell
The grid opens a dialog for that field and sends the new value to the API for that frequency, year and period.
Where data protection lives โ
- Personal identifiers (TIN, NIS, ID, date of birth, address, phone) are encrypted at rest and searchable only through hashed indexes. They are excluded from activity logs.
- Payslip PDFs can be password-protected. A payslip isn't sent at all if its password can't be formed.
- Every sensitive action โ closing, purging, granting roles, AI-agent writes โ is permission-checked and audited.