Skip to content
CompanySeptember 15, 20264 min read

Cedric Albeke: From a merchant’s own problem to building FoxPay

A portrait of Cedric Albeke: the Cannaspot background to FoxPay, independent learning and his approach to product and implementation as Co-Founder & CTO.

Cedric Albeke: From a merchant’s own problem to building FoxPay
FoxPay Team
Payment Infrastructure Experts
September 15, 2026
4 min read

A shop needs more than a good product range. Customers need to place orders and pay, and the processes behind the interface need to work together. Cedric Albeke, Co-Founder & CTO of FoxPay, encountered that connection through his own entrepreneurial experience. It runs from Cannaspot to the development of a payment solution. Today, his responsibilities at FoxPay cover product, platform and technical implementation.

On his personal website, Cedric describes himself with a short sentence: “I create things.” This portrait explores concrete examples behind that description: a retail venture, public discussions about software development and his role in the FoxPay team.

Role

Co-Founder & CTO

Product and technical implementation

Starting point

A merchant’s perspective

The entrepreneurial background at Cannaspot

Responsibility

Product & Platform

From the initial idea to live operations

Collaboration

Four perspectives

Strategy, product, business development and legal

The background: a shop and its obstacles

In a LinkedIn post of his own, Cedric says that obstacles in building Cannaspot led to the development of a payment solution: FoxPay. He presents this as an opportunity to help other merchants facing similar problems. This is his personal account of the project’s origins.

The public Cannaspot company profile documents the retail context at the time: living soil under the LifeSoil brand, seeds and growing supplies. The venture was rooted in e-commerce involving physical products. That starting point matters to Cedric’s story: the need for working payments arose within a business trying to get products to its customers.

From an editorial perspective, this background explains why merchant processes make a useful starting point for product development. A payment function sits inside the purchasing process. For a shop operator, what matters is how it connects with an order, customer information and fulfilment.

Learning through practical development questions

Cedric describes his learning path on LinkedIn as “Self-taught”. Public contributions to the WeWeb community offer a more concrete look at his engagement with software.

On 26 January 2024, posting as “AlbekeIO (Cedric Albeke)”, he asked about practical access to staging: an environment for testing applications. His example concerned interactions between several users logged in simultaneously. He wanted to be able to try out those scenarios before putting an application into use.

On 3 March 2025, he also contributed to a discussion about e-commerce backends, identifying Medusa JS as part of a stack used at the time. These posts show technical questions he discussed publicly; they do not describe FoxPay’s current architecture.

Bringing product and implementation together

According to the FoxPay team profile, Cedric’s role covers product, platform and AI-assisted development from the initial concept through to live operations. It brings together two closely connected responsibilities: understanding what an interface should do for merchants and shaping the technical implementation behind it.

A simple example shows how closely those tasks are related. When an interface displays a payment status, the information needs to be understandable and consistent with the underlying transaction. A clear label is as much a part of the product as the processing of the data behind it.

Cedric’s responsibilities connect these questions. His place in the team links work on the product to decisions about its technical implementation and continued development in operation. AI-assisted development is part of the working approach described in his role. For merchants, the outcome remains what matters: an application with processes they can understand and use.

Working on the platform together

Cedric works alongside Andreas Richter, Alex Ritler and Harald Plewka. Within the leadership team, payment strategy and merchant consulting meet product development, business development and legal expertise. Questions arising from a merchant’s business can therefore be considered together from different professional perspectives.

That is also the connection between Cedric’s background and his current role: a practical problem becomes a task for a product team. His contribution at FoxPay is to translate requirements into interfaces and technical processes and guide their implementation. The path from a retail venture to a payment platform gives that responsibility a tangible starting point.

Sources and context

Research dated 15 September 2026. Historical background and personal statements draw on the linked first-person and company contributions. Parts of LinkedIn were available only through the public search index. FoxPay responsibilities come from the team profile; their interpretation is editorial. This portrait is not a complete CV.