Service Sessions And Commercial Flows
Emiko supports service-session flows inside the same ecosystem and access model. A user can access a service in the app, act inside the app flow, and complete the relevant session.
Neutral Session Actions
At ecosystem level, common session actions include:
- Book
- Start
- Stop
- Pay when relevant
These actions are neutral operating-model language. They do not by themselves define product scope, settlement method, or provider implementation.
Commercial Flow Variants
Commercial flow variants in Emiko can include these patterns.
- Non-billable use
- Bill later / invoice flow
- Direct in-app payment
This distinction keeps the operating model clear without forcing every service flow into the same commercial setup.
Access And Approval Still Control Use
Service sessions still follow the same access model.
- Partner-defined access remains a controlling rule.
- Granted scope still determines what the user may access and operate.
- Commercial flow does not remove the need for controlled access.
What Comes Next
The last step in this introduction is to show the breadth of products, modules, and growth direction already connected to the Emiko Ecosystem.