01
Prepare the payment and equipment contracts.
Establish the provider, region, merchant and qualified controller interface.
- Customer order↓
- Payment authorisation↓
- Permitted request
Connect the customer charge to what the machine actually delivered.
Connect payment to the reported service outcome.
Follow the order through to the service outcome.
02
Record what the machine delivered.
Keep a requested start, confirmed service and financial state distinguishable.
- Requested↓
- Reported outcome↓
- Capture / refund / review
03
Resolve uncertain cases.
Review provider events and equipment records after interruptions, duplicate requests or timeouts.
- Provider events↓
- Equipment records↓
- Reconciliation
Reference integration. Complete live provider verification and qualify the physical reader before accepting payments.
See the full workflow and requirements →Setup, limits and technical guidesFull workflow, configuration and qualification details
Follow the job from the first signal to the result.
Illustrative operating sequence. People choose the scope and intervention; configured collection, rules and device behaviour supply the evidence.
Step 1
Prepare the provider and equipment contract
The vendor configures regional Stripe Connect integrations; the customer organisation completes merchant onboarding. Establish the exact controller, firmware, interface and supported region. Payers are distinct from those customer organisations.
Step 2
Relate an order to a requested operation
The laundry reference joins payment authorisation to a permitted start request. Application logic must account for busy/rejected equipment, duplicate requests and lost connections. A request does not prove a machine started.
Step 3
Establish delivery and financial state
Use the qualified equipment interface to report the service outcome. Distinguish delivery, captured amount, refund and unresolved state. A timeout may require investigation; do not automatically equate it to failed delivery.
Step 4
Reconcile the uncertain cases
Review provider events and equipment records after network or power loss. Recover within the original regional/payment context. Exercise the software reference in simulation and separately qualify real hardware and live-provider behaviour.
What you do not have to reconstruct between tools
Order, customer Product Instance, payment region/currency and operation identity connect financial and physical records. Reports and recovery cannot substitute for evidence that the actual service was delivered.
Keep the responsibility clear
The reference has been tested in software simulation. Complete live Stripe verification and physical reader qualification before live use. Check reader availability, unattended-use approval, UI requirements and offline-payment support for your equipment.
What would we need to change?
Configuration, product engineering and subscription eligibility are different requirements.
Enable and configure
Integrate the payment provider/merchant setup, equipment adapter, terminal/reader application, reporting and reconciliation. Obtain authoritative machine/controller evidence and test local safeguards and physical outcomes.
What you keep
Retain equipment safety, controller behaviour and business responsibility. Payments are optional; fleet operations, customer views and other Product Application processes can stand alone.
Plan and readiness
Exploratory integration project. Qualify country and provider coverage, the equipment interface and the exact terminal before accepting live payments.
Read the guide →The tools underneath the job
Use the exact implementation guides to check the supported contract and limits.
Payments and regional prerequisites
Configuration and implementation requirements.
Read the guide →Laundry compatibility and qualification
Configuration and implementation requirements.
Read the guide →Reference commissioning gates
Configuration and implementation requirements.
Read the guide →Bring a specialist into the work
Ask for help where evidence or an integration decision is unclear. Use the context and permissions available to that conversation.
Hardware, product and operations help
Equidna helps connect supplied hardware evidence to the software path; Nutria helps plan the customer job; Pingüino helps investigate authorised operational evidence. Shared-room help remains read-only. 24/7 AI assistance has plan and usage conditions.
Read the guide →Choose one useful result to prove.
Use the reference to build your own test. Validate the hardware, integration and operating process on your product.
Review the commercial-laundry reference
Review the procedure and qualify the parts your product requires.
Read the guide →Check adoption requirements
Start with the product you have, then choose independent optional paths.
Read the guide →Start with this job.
Integrate the payment provider/merchant setup, equipment adapter, terminal/reader application, reporting and reconciliation. Obtain authoritative machine/controller evidence and test local safeguards and physical outcomes.