Components
API-First approach
but you can use prebuild components
You can do everything independently and individualize how you want. But we want to make life easy for you. So, we give you all APIs, but you can also use our prebuilt components wherever you want.
1 Find
You know which Ticket fits your User the best. So give him the right city, the right ticket type, or the right age type that makes the most sense to him.
OR
Your Composition
2 Order
The Part where the money goes. You can sell the ticket in your shop and buy the ticket from your backend via our API or send the user to our web service and payment page.
OR
3 Activate
Every Ticket needs to be activated and personalized to the user. This is needed because the transport agencies want to prevent the user from copying the ticket for multiple persons. In every area, other options and requirements are available. You can individualize the tickets via our API, or you can use our SDK, which provides all the correct form fields for you.
OR
OR
4 Render
In the situation of an inspection, the user needs to show the Ticket to the Ticket Inspector. In every area, the inspectors expect a differently rendered ticket. Our rendering engine ensures the correct rendering for you. You can get it via API, from our SDK, or simply use the prebuilt Mobility-Wallet App.
OR
OR
Your customer, your solution
You can optimally combine the various options to serve your customers.
Solution 1: Your checkout, No App
Add a Ticket to your own Check-Out-Process without the need of an App.
1 Find
Give your users the option of all ticket types in your city.
Your Composition
2 Order
You sell the ticket in your check-out process and buy the ticket from your backend via our API.
3 Activate
You do the checkout on your site and let the users manage their Tickets in the "Mobility Wallet"-App so you do not need an own App.
4 Render
You do the checkout on your site and let the users manage their Tickets in the "Mobility Wallet"-App so you do not need an own App.
Solution 2: Link only Fastest integration
Do you want to determine whether your users would buy public transport tickets?
1 Find
Give your users the option of all ticket types in your city.
Your Composition
2 Order
Provide the User a Link to a branded check-out-process.
3 Activate
Send the users to the "Mobility Wallet"-App, so you do not need to deal with anything here.
4 Render
Send the users to the "Mobility Wallet"-App, so you do not need to deal with anything here.
Solution 3: Full Integration
You want full control over the user flow. Do you want everything styled on your own? Of course, you can do that.
1 Find
Give the users automatically the tickets that fit them best. For example, by filtering for all tickets available at his current location.
2 Order
Do your checkout with your payment service provider and order the ticket via your backend.
3 Activate
Render your own Form for personalisation of the tickets. Be aware that you sometimes need to update your app if you are not using our SDK as soon as new locations or ticket types become available.
4 Render
Render the Inspection-View with our SDK so we ensure that every ticket is displayed how the local authorities expect it to be. (But you can also do that via API if you want.)
Solution 4: Your App, our payment-solution
You want to serve your user in your app but do not have a payment solution? We've got you covered.
1 Find
Give the users automatically the tickets that fit them best. For example, by filtering for all tickets available at his current location.
2 Order
We can do the payment integration for you via our FastLink-Service.
3 Activate
Render the Activation-View with our SDK so you always have the correct personalisation-schema for every location at ease.
4 Render
Render the Inspection-View with our SDK so we ensure that every ticket is displayed how the local authorities expect it to be. (But you can also do that via API if you want.)