-
Notifications
You must be signed in to change notification settings - Fork 41
Planning phase prices
Q: What should be send in the planning as price? The agreed price between TO and MP or the consumer price?
A: if you have agreements between TO an MP, this price should be used, but it must always be marked “estimated”: “true” in the planning, because the trip isn’t finished yet and the price can change.
Q: Is there a possibility to make payment happen directly from end user to TO?
A: One of the main thoughts of the TOMP API is that there is no direct contact needed between the end user and the TO. Therefore payments from the end user should be going to the MP and the TO will receive payments from the MP.
Q: And what about existing arrangements (contracts, discount cards etc.) between the end user and the TO?
A: the API facilitates in supplying this information in the planning call (cardType)
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