1. Download the version for your computer
After payment, your secure Number Chest purchase page shows Windows, macOS, and Linux downloads. Choose the computer you are installing now.
The normal desktop path is designed for business owners—not server administrators. Advanced hosting and Docker instructions are separated below for IT-managed deployments.
Perpetual use of the purchased Merchant Core release and entitlement scope.
Production use while the paid term remains active.
Same Merchant Core features on each supported desktop platform.
You can run local POS, Owner/Admin Control Center, products, staff, and employee time clock without Docker or a public server. The desktop application creates its secure local runtime automatically.
Choose hosted/hybrid only when you need remote/shared access, multi-location access through one Internet-facing backend, or public emailed invoice payment links.
After payment, your secure Number Chest purchase page shows Windows, macOS, and Linux downloads. Choose the computer you are installing now.
Windows: run the .exe installer. macOS: open the DMG and drag Merchant Core to Applications. Linux: allow the AppImage to run as an application, then open it.
Merchant Core opens an activation screen the first time it starts. Copy the MC- activation key from your Number Chest purchase page, paste it, and choose Activate and continue.
Enter your business name, legal company name, owner/admin contact, and sales-tax percentage. Then follow the on-screen checklist for products, payments/deposits, employees, and the time clock.
Before the first real sale, run a controlled POS payment, verify the deposit destination, clock an employee in and out, send a test invoice, and open its secure payment link.
Complete bank verification directly with your supported payment provider first. Merchant Core stores the provider account reference, account type, last four digits, and verification state. Do not enter a routing number, full bank-account number, card number, or CVV into Merchant Core configuration.
For a standard desktop deployment, Number Chest or your payment-provider onboarding team can supply the references you need. The Owner/Admin screen labels exactly where they go.
These settings are for an administrator or managed-hosting operator. Normal desktop buyers do not need them.
Run the Merchant Core API on a persistent HTTPS Node.js runtime with production storage/database authority. The desktop wrapper points to that service through MERCHANTCORE_REMOTE_ORIGIN.
SYSTEM_HMAC_SECRET — unique production secret.PAYOS_ADMIN_API_KEY — production admin/payment authority key.PAYOS_WEBHOOK_SECRET — verifies inbound payment webhooks.MERCHANTCORE_PUBLIC_BASE_URL — HTTPS public origin used in customer invoice-payment links.MERCHANTCORE_INVOICE_EMAIL_WEBHOOK_URL — transactional-email handoff endpoint.MERCHANTCORE_REMOTE_ORIGIN — hosted API origin used by the desktop wrapper.Keep production credentials outside source control and rotate any secret that was exposed in plaintext.
Use Docker delivery only for a hosted/self-hosted Merchant Core backend. Download the image matching the server CPU: linux/amd64 or linux/arm64.
Verify the downloaded archive before loading it:
shasum -a 256 -c merchant-core-1.6.0-r14-linux-amd64.docker.tar.gz.sha256
gzip -t merchant-core-1.6.0-r14-linux-amd64.docker.tar.gz
gunzip -c merchant-core-1.6.0-r14-linux-amd64.docker.tar.gz | docker loadThen use the supplied release compose file and environment template. Confirm /ready before placing the API behind HTTPS.