Appearance
Commercial laundry #
The commercial laundry reference uses Product Applications, Device Classes, Product Processes, authorised actions and the Customer Portal. Its equipment gateway runs as managed Software on Dataplicity-OS or another qualified Linux image, using the existing agent for credentials, command transport and event delivery.
The initial software foundation supplies machine simulators, a LaundryMachine capability contract and generic read-only Modbus instrumentation. Physical manufacturer adapters, the laundry application/owner portal and live payment commissioning are separate implementation and verification steps. No production machine compatibility or supported wiring is claimed by the simulator package.
- Shared contracts and gateway setup
- Compatibility and verification
- Safety and commissioning
- Reusable payments and Australian terminal testing
Application boundary #
Model operators, sites, machines, vends, prices and exceptions with existing Product Records and relationships. Reusable payment orders and allocation ledgers belong to the same customer Product Instance. Processes compose payment and service delivery. Normal owner navigation should use Today, Sites, Machines, Transactions and Settings, with business impact before technical cause. Manufacturer protocols, raw registers and framework objects belong in the integrator's setup and engineering surfaces.
Each command and business event retains immutable order, payment reference where present, vend, Process, Operation and machine-command identifiers. Payment failed means never vend. Definitely failed service after confirmed payment permits compensation; an unknown service outcome requires reconciliation and must never trigger a blind duplicate vend. Preserve successful vends in a multi-machine order and compensate only the confirmed failed service.
Payment readiness boundary #
Initial attended reader testing is planned in Australia/AUD; the Android reader application is deferred. See Payments for the backend settlement foundation, current boundaries and questions for Stripe.
The operator must be the merchant through Stripe Connect. A Site maps to a Terminal Location. UK/GBP and Spain/EUR are target validation combinations, not claims of approved unattended deployment. UX700 requires Stripe programme access and confirmation of country, connected-account charge behaviour, provisioning, unattended approval and the supported reader/POS experience. The gateway does not hold Stripe credentials or implement a separate payment service.