-
Notifications
You must be signed in to change notification settings - Fork 41
Customer object
home > Planning phase | Booking phase | Trip execution phase > Customer object
Please use this construct as little as possible (GDPR). The customer is the 'owner' of the app. She/he requests the planning, using hers/his account in the app. Could be the same as the traveler, but doesn't have to be the same one. Traveling in groups always means there is one customer, and this customer can be part of the group.
Contains all fields of Traveler, extended with these fields:
field | required | description |
---|---|---|
id | * | The identifier MaaS uses to identify the customer, can be MP or TO specific |
travelerReference | optional reference field to the travelers, from the planning request | |
initials | Initials of the customer | |
firstName | First name of the customer | |
lastName | Last name of the customer | |
middleName | Middle name of the customer | |
prefix | prefix of the customer, like titles | |
postfix | postfix of the customer, like titles | |
phones | phone numbers of the customer | |
the email address of the customer | ||
birthDate | birth date of the customer | |
address | registered address of the customer | |
photo | base64 encoded image of the customer | |
cards | cards of the customer | |
licenses | licenses of the customer |
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