Smart drawers (SMARTDRAWER)
Cash recyclers / acceptors attached to a TPV print service (RASPPI). Operators charge cash through the drawer on the till that receives the payment; maintenance (backoffice) runs from cash-control on the session TPV. Protocol lives in feature/drivers; UI in feature/drawers; hosts are feature/ticket (charge) and feature/audits (BO).
| Layer | Where |
|---|---|
| Model | SmartDrawer row / TicketView.CashDrawer (charge) / PlaceView.OwnDrawer (session BO) — upp-model.mdc § SMARTDRAWER |
| Devices UI | feature/devices — smartdrawer edit/view under the service editor |
| Charge UI | upp-drawer-payment hosted by ticket edit/thumb |
| Backoffice UI | upp-drawer-backoffice (CashGuard pilot) hosted by audits cash panel |
| Wire | drawerService → print_service WS LAN or WSR (TARGET = model) |
| Bridge | pispas-connect modules cashguard / cashlogy / prosegur / glory |
Product rules (summary)
- Drawer follows the pay till (RN-SD-04): metallic charge uses
TicketView.CashDrawer— the AC drawer onPayTill(same till resolution as cash closings). SessionOwnDraweris for backoffice / pinpad warnings only. - Cash check wins (RN-SD-13):
CanCashfollows the place / pinpad cash flags (nocash). A smart drawer does not hide the cash button; whenCashDraweris set the charge opens the drawer panel, otherwise classic cash. Enabling «Allow cash» on a pinpad while the session TPV has a drawer shows a warning that cash on that terminal will not go through the machine. - One drawer per service (RN-SD-14): at most one AC
SMARTDRAWERper TPV. Adding another shows a replace warning; accepting the new drawer soft-deletes (DE) the previous one. Cancel leaves the existing drawer unchanged. - Confirmed charge before ticket pay (RN-SD-07):
DoPayment/ commit run only after the drawer panel reports paid (OnDone(true)): machine approved (status: success), or the operator accepts cash without the machine after a drawer error. Auto-close as paid happens only after machine approval — a missing connection, timeout, orSUCCESSwithout nestedstatus: successstays on the error screen with «Accept payment without drawer». Cancel / close without accept leave the ticket unpaid. The ticket host stays agnostic of device outcomes and does not chain the classic cash modal from the drawer panel. - LAN or WSR (RN-SD-05): transport is LAN when the session device has a local connect to the drawer’s
RASPPI; otherwise WSR by service name (e.g. comandero charging a table whose till owns the drawer). - Credentials stay in
pispas-connect: the app row storesname+modelonly. - Pilot family (D-SD-02): CASHGUARD for charge + backoffice. Other families share the same charge wire (
PROCESS_TRANSACTION); change/replenish UIs are not in the pilot.
Operator flows
Deferred
- Cashless charge/refund via drawer (F-SD-06 / F-SD-07).
- Prosegur / Glory change + replenish panels (F-SD-10 / F-SD-11 beyond CashGuard).
Canonical RN/RF: libs/upp-data/.../upp-model.mdc § SMARTDRAWER; feature hubs upp-feature-drawers.mdc, upp-drawer-service.mdc, ticket RN-EDIT-PAY-DRAWER-*, audits RN-AUD-SD-*.