TWINT Case Study

TWINT is a payment solution developed and available in Switzerland, with around three dozen Swiss banks and financial institutions integrated into the platform. Especially during their start-up phase, TWINT needed a flexible system that could react to the rapid changes of a start-up environment. Not only did it have to be integrated quickly and easily into existing structures and processes, but it also had to have the necessary scalability to support TWINT’s ambitious growth plans.

The TWINT solution is available to anyone in Switzerland. This meant that right from the start of its development, TWINT had to support different types of devices and operating systems. The same flexibility applies to the app and the vendor portal: Although there are no individual peak times, a large number of users need access around the clock. And finally, as each business operates under different conditions, meeting their individual data protection and security standards requires a high level of flexibility.

In order for each bank to be able to offer its own TWINT app to its customers, all data had to be accessible via APIs. TWINT therefore needed an open content management solution that could adapt to the needs of both developers and editors supporting TWINT in each bank.

With Magnolia, TWINT found a solution that delivers its content to millions of private and business customers, while at the same time offering a highly customisable and flexible system that is easy to use. As a standards-based enterprise solution, Magnolia meets all of these criteria and provides the necessary security to make it all work. Together with Magnolia's Gold implementation partner fastforward websolutions, the software was set up and adapted to TWINT's individual preferences.

Especially during the implementation and development process, Magnolia's flexibility proved to be crucial. Thanks to its open-source origins, Magnolia can offer a high degree of customization. This freedom helped TWINT thrive in the highly competitive fintech space. Every part of the Magnolia DXP is customizable. Fastforward augments this by implementing logic in dialogues that checks inputs or dependencies, helping editors to update content while maintaining consistency.

During development, being able to integrate dev tools was necessary. In fact, it was important for the TWINT developers to be able to fall back on the many software standards supported by Magnolia, such as for the use of OpenAPI and Swagger.

In addition, it was very important to the payment service provider to integrate third-party systems via REST APIs and make them accessible to the editors. TWINT also benefits from Magnolia's flexibility in the connection of the SAS Real-Time Decision Manager, which enables customer interaction in real time. Editors can easily create messages to users in a Magnolia Content App and check in the preview how messages are displayed on different devices.

Magnolia is used for both the mobile app and the B2B portal of TWINT using a headless content approach. The mobile app is aimed at end consumers, while the portal is intended for vendors who offer TWINT as a payment method. 

TWINT had special requirements regarding the communication between the Magnolia backend and the app, which could be implemented thanks to Magnolia's open architecture. Content is now transmitted in packages of JSON, HTML and image files according to the requirements.

Thanks to Magnolia, TWINT can now manage its content across all channels centrally. This allows developers and marketers to work in a space that empowers them, increasing their efficiency and helping TWINT grow. 

The flexibility to adapt to any situation via Magnolia's composable approach and seamless integrations into the wider system landscape, were necessary for TWINT to succeed, while the high performance and solid security provided the backbone.