Start with the entity, not the terminal
A common mistake is adding devices or cashiers before defining the business, branches, and authority model. LuxPay starts with the business entity, then memberships, branches, and operating points. This makes every payment inherit trusted context rather than relying on fields sent by a device.
Recommended sequence
- Create the business profile and complete required legal verification.
- Assign owners and finance operators with separate permissions.
- Add branches with clear names, locations, and operating scope.
- Define roles such as branch manager, cashier, and reviewer; do not make everyone an administrator.
- Bind each operator to a clear branch or scope.
- Configure transaction, approval, and refund limits.
- Test a payment and daily-close cycle before public launch.
Two decisions to make early
Decide who can refund funds and who can approve or review settlement. Separating these authorities reduces errors and prevents one person from initiating, correcting, and reviewing the same financial action.
What readiness means
Readiness is not only a working payment screen. It means branches are correct, users are constrained, receipts are clear, pending states have a process, and daily reports can be reviewed.
Continue with Branches and operators and Roles and permissions.