-
Notifications
You must be signed in to change notification settings - Fork 41
Clearing house
home > Ecosystem > Clearing house
A clearing house is a role in a MaaS ecosystem. It will allow the transferral of money between MaaS participants, f.x. from MP to TO.
A clearing house should have at least 4 functions:
- registrate the willingness to pay for a leg in a trip to a specific TO
- validate the willingness to that TO
- registrate the actual costs for that leg by that specific TO
- take stock on a frequent base: what is the amount of money that should be transmitted
A clearing house can also facilitate in these roles:
- price calculator (in case of multiple legs in one trip & all participants are working together with this CH)
- travel right stock (a big stock of tickets/access data, accessible for the MPs and TOs involved by a specific leg)
Introduction
- Roadmap
- Semantic versioning
- Use cases
- Changes per version
- Contribution
- Participants
Workflow
- Operator information
- Planning phase
- Booking phase
- Trip execution phase - start
- Trip execution phase - on route
- Trip execution phase - end
- Support
- Payment
Points of attention
- Modalities
- Specifying locations
- GDPR
Eco system
- Relations
Introduction
Scope of the TOMP-API
Versioning and releases
Process Flows
- Authentication
- Operator Information
- Privacy and Registration
- Planning Module
- Booking Module
- Trip Execution Module
- Payment Module
- Support Module
Meta-Information
Reference implementations
To-dos and risks
Technical Specifications
A1 List of terms and definitions
A2 Passenger characteristics dictionary
A3 APIs available on the transportation ecosystem
A4 Overview of the User stories
A5 Authors, Architects, collaborators and stakeholders involved
A6 Adoption and Implementation of the TOMP-API