Start with one employee identity and one governed consumption account, then associate cards and face credentials with that person. A card read or face match answers who is attempting the transaction. It does not decide whether the charge comes from an employer subsidy, personal balance or another approved account. That decision requires the meal period, employee category, subsidy validity and transaction amount. Successful identity verification is not successful payment, and successful payment does not prove that an entrance gate released or that the person passed through it.
Separate identity, credential and account
- Identity is the stable employee ID and necessary status.
- A card or face is a credential used to find that person.
- The consumption account carries approved subsidy, personal balance, meal rules and transactions.
- Payment rules choose the funding source, permitted amount and overage handling.
Combine subsidy and personal balance deliberately
Not every employer provides a meal subsidy. Where one exists, define recipients, amount or uses, meal periods, validity, carry-over and overage handling. Without a subsidy, use only the approved account and settlement method.
Select a model for the serving line
- A fixed-price institutional or company meal may use a quota, meal count or approved subsidy.
- Multiple counters can charge the confirmed transaction amount to the employee account.
- A self-service line priced by weight may evaluate a weighing settlement device; weighing determines quantity and amount while face confirms the account.
- The website has no standalone weighing-terminal product page, so no model, precision or default feature is claimed.
Recommended transaction sequence
- Create one employee ID and valid status.
- Associate cards and face credentials with that identity.
- Configure the consumption account, subsidy, balance and meal periods.
- Verify the person and capture the current purchase.
- Apply the approved subsidy and personal-balance rules.
- Retain person, terminal, time, amount, funding source and outcome.
- Use only delivered modules for exceptions, refunds and reconciliation.
Work with the existing environment
- Existing card account: verify IDs, balances, subsidies, transactions and interfaces.
- Personnel system only: retain reliable master data but create a separate consumption ledger.
- Controlled entrance: add a face gate and keep entry events separate from counter payments.
- Visitors or contractors: use approved temporary accounts, amounts or uses.
- Offline payment: enable only when proven by the product and implementation scope.
Equipment and systems
- Face payment terminal.
- Employee cards and confirmed readers.
- Personnel, account, subsidy, order, refund and reconciliation software.
- A confirmed visual or weighing terminal where the serving line requires one.
- A face gate only where entrance control is a real requirement.
Confirm before implementation
- Ownership and deactivation of employee IDs, cards and face credentials.
- Subsidy issuance, use, expiry, refund and overage rules.
- Which lines use quota, count, open-value or weight pricing.
- Temporary diners, guest meals and overtime meals.
- Outage, insufficient balance, duplicate debit and refund procedures.
Frequently asked questions
Does a face match automatically debit the subsidy?
No. It identifies the person; the account rules decide whether a valid subsidy applies.
Do card and face use separate accounts?
They should normally resolve to one employee identity and governed account, subject to the existing data model.
Should every enterprise canteen use weighing settlement?
No. It is most relevant to self-service lines priced by weight.
Does a face payment terminal replace an entrance gate?
No. The payment terminal handles a transaction; a gate is separate and only needed for controlled entry.