Components

API-First approach

but you can use prebuild components

You can do everything on your own and individualize how you want. But we want to make live easy for you. So we give you all APIs but you can also use our prebuild 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.

API
OR
Your Composition

2 Order

The Part where the money goes. You can sell the ticket in your own shop and buy the ticket from your backend via our API or you can send the user to our webservice and payment page.

API
OR

3 Activate

Every Ticket needs to be activated and personalised to the user. This is needed because the transport agencies wants to prevent the user from simply 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.

API
OR
SDK
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 expects a differently rendered ticket. Our rendering-engine ensures the corrent rendering for you. You can get it via API, from our SDK or simply use the prebuild Mobility-Wallet App.

API
OR
SDK
OR

Your customer, your solution

You can combine the different options in order to serve your customers the best.

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 own check-out process and buy the ticket from your backend via our API.
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

You only want to find out if your users would by public transit tickets in the first place?

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 to have the full control about the user flow. You want everything styled on your own? Of course you can do that.

1 Find

Give the users automatically the tickets that fit him best. For example by filtering for all tickets available at his current location.
API

2 Order

Do your own checkout with your own payment service provider and order the ticket via your backend.
API

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.
API

4 Render

Render the Inspection-View with our SDK so we ensure that every ticket is displayed how the local authorities expects it to be. (But you can also do that via API if you really want.)
SDK

Solution 4: Your App, our payment-solution

You want to serve your user in your own app, but you do not have a payment-solution? We got you covered.

1 Find

Give the users automatically the tickets that fit him best. For example by filtering for all tickets available at his current location.
API

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 alsways have the correct personalisation-schema for every location at ease.
SDK

4 Render

Render the Inspection-View with our SDK so we ensure that every ticket is displayed how the local authorities expects it to be. (But you can also do that via API if you really want.)
SDK