English
Payment Elf: Installation and Sign-In
This page covers server preparation before installing on the POS computer, installation and upgrade, sign-in, and stores and terminals.
Server Preparation
Payment Elf connects directly to the DaxPay backend and does not go through the cashier-system gateway. Four items must be confirmed on the deployment side and the merchant side.
Backend Includes the Elf Module
daxpay-payment-elf is part of the standard DaxPay build: the main app start module already depends on it, so it is compiled and deployed together with the main app and needs no separate service. If the backend has been trimmed, confirm the module is still in the dependencies and that /elf/** endpoints are reachable.
Gateway Allows /elf
With an ops-panel deployment, confirm under "Gateway Management → External Endpoints" that the "Desktop cashier terminal" (/elf) rule is enabled, which is the default. The rule allows the whole /elf/ segment; requests are still protected by the merchant session and the merchant identity domain.
The sign-in flow reuses the /token, /nonce and /captcha endpoints from the "Mini program / APP API" rule, which is also enabled by default. If that rule is turned off and no mobile API domain is bound, sign-in returns 404. Full details: Gateway Management - External Endpoints.
Create a Cashier Account
A merchant administrator creates the account on the merchant panel under "Merchant Center → Basic Management → Merchant Users" and selects the "merchant cashier" role. That role grants trade-order viewing, trade-order management and refund permissions, covering collection, order query and refund. For account creation see Merchant Users.
Payment Elf signs in with the merchant identity domain and only accepts merchant-panel accounts.
Prepare Stores, Apps and Terminals
Prepare the stores and payment apps to use on the merchant panel; Payment Elf lists only enabled items after sign-in. To distinguish POS machines, first create terminal records under "Device Management → Merchant Terminals" and set the default terminal in store management; see Payment Device Management - Merchant Terminals and Merchant Profile and Stores - Store Management.
Installation and Upgrade
Choosing an Installer
| Installer | File name | Description |
|---|---|---|
| Standard edition | DaxPayOpenElf-Setup-<version>.exe | About 59MB, bundles .NET 10, ready to use after installation |
| Slim edition | DaxPayOpenElf-Setup-<version>-fdd.exe | About 12MB, requires the .NET 10 Desktop Runtime preinstalled |
Installers are packaged for the deployed platform address and delivered through a private download link. When the private link uses fixed file names, they are DaxPayOpenElf-Setup.exe and DaxPayOpenElf-Setup-fdd.exe.
Installation Steps
- Double-click the installer and follow the wizard to choose the install directory, Start menu entry and desktop shortcut. The default install path is
{autopf}\DaxPayOpenElf, and the program isDaxPayOpenElf.exe; - If the installer is not code-signed, Windows may show "Windows protected your PC"; click "More info → Run anyway" to continue;
- Running the same installer again performs an in-place upgrade. Its installer identity differs from the old Payment Elf (
DaxPosElf) and from the other Payment Elf build (DaxPayElf), so they can coexist on one computer; the old data directories are never read, migrated or deleted; - The data directory is
%APPDATA%\DaxPayOpenElf\, containingconfig.json,logs,trades.db,credential.binandprint-dump. Uninstalling does not delete this directory.
Configuring the Server Address
The sign-in window does not show the server address; the address is preset by the deployment party at install time. Read priority, highest first:
elf.defaults.json, placed in the same directory as the exe;gateway.baseUrlinconfig.json, in the data directory;- The default address burned in when the installer was built.
To change the address, place an elf.defaults.json next to the exe:
json
{ "gateway": { "baseUrl": "https://pay.example.com" } }Restart the program for the change to take effect. When installed under Program Files, writing this file requires administrator rights.
Interface Language
The Payment Elf interface supports 10 languages: Simplified Chinese, Traditional Chinese (Taiwan / Hong Kong), English, Japanese, Korean, Indonesian, Malay, Thai and Vietnamese.
- The globe button at the top right of the sign-in window switches the interface language before signing in, and "Follow system" is also available;
- After sign-in, switch under "General → Interface Language" in the settings window; the change takes effect immediately, without restarting the program;
- Voice broadcast and receipt printing stay in Chinese: the voice uses Chinese TTS and pre-recorded clips, and receipts are limited by the GBK font of thermal printers, which cannot print characters from other languages;
- Amounts, dates and currency symbols do not change with the interface language, keeping reconciliation consistent.
Sign-In and Security
Accounts are created by a merchant administrator on the merchant panel and assigned the "merchant cashier" role. The sign-in flow:
- The password is encrypted with an RSA public key before transmission, with a nonce to prevent replay; repeated failures require a graphic captcha;
- Accounts with TOTP two-step verification enabled must also enter the one-time password;
- On first sign-in or when the password has expired, a password change is required first, after which the main flow continues;
- Sign-in credentials are kept in memory only; with "Remember password" checked, the account and password are encrypted with Windows DPAPI (current user) and stored locally, then pre-filled on the next sign-in;
- When the session expires, the token is cleared and the sign-in window pops up; sign in again to continue.
Stores and Terminals
After a successful sign-in, Payment Elf pulls the enabled stores, apps and terminals of the current merchant:
- With one store it is selected automatically; with several stores a dialog asks. Cancelling does not block sign-in, but the collection entry stays disabled;
- Collection is not allowed without a selected store, which avoids orders attributed to the wrong store;
- The store follows this computer, not the account. The cashier window header shows "store · account"; click "Switch store" to change it. Other accounts of the same merchant on the same computer inherit that store;
- The payment app comes with the store, so cashiers do not choose an app;
- The cashier terminal is selected on the cashier store card under "Cashier Settings → Account", either "Follow store default" or a specific terminal of the current store. The choice is stored locally only and must be reselected after switching computers, reinstalling or clearing configuration.
Common Issues
The server address is wrong or needs changing
Close the program, create or edit elf.defaults.json next to the exe, put in the correct gateway.baseUrl and restart. This file has the highest priority and overrides the address in config.json; when installed under Program Files, save it with administrator rights.
Sign-in returns 404
Check whether the "Mini program / APP API" rule under "External Endpoints" is enabled, or whether a mobile API domain is bound. When the rule is off and no domain is bound, sign-in returns 404.
The account cannot sign in
Confirm the account is a "merchant cashier" created on the merchant panel and that the store and app are enabled. Payment Elf does not accept admin-panel accounts. With several stores, cancelling the store selection keeps the collection entry disabled; click "Switch store" to select again.