Clément Salaün and the money after the payment

The payment has cleared. A small green tick appears. Somewhere behind it, a much longer conversation begins: who gets the money, how much belongs to the platform, what happens if the buyer changes their mind, and which record will explain it all next Tuesday? Clément Salaün has made a career in that conversation. His subject is the money after the payment, when a reassuring interface gives way to obligations that software must remember.

There is a pleasingly ungrand beginning to this interest. Salaün learned programming through a project that allowed Minecraft server owners to sell items to players. A game supplied the setting; payments supplied the discipline. There was inventory to track, a buyer to satisfy and money arriving from somewhere. A purchased item needed to reach the right person. Even in a world made of blocks, a transaction carried a promise.

The distance from that project to financial infrastructure is shorter than it first appears. A player buys an item. A marketplace buyer purchases a chair. A platform promises a seller a payout. Each leaves a relationship behind, and each needs a system that can distinguish an amount received from an amount owed. The graphics may improve. The bookkeeping continues to insist on being invited.

A marketplace teaches the second half of the transaction

At Selency, the furniture marketplace, Salaün worked on the backend and payments, eventually leading that engineering work. When he announced his departure in 2021, he described five years with the company and thanked its founders, Maxime Brousse and Charlotte Cadé, alongside a long list of colleagues. The farewell gives his next venture a practical starting point: years of maintaining systems with other people, rather than a problem discovered on a pitch-deck slide.

His public writing from that period already shows the preoccupations. In July 2019, he published “Migrating to Stripe Connect”. In February 2020 came “Your balance is $0.30000000004”, an inventory of mistakes in software handling money. The latter title is a small joke with a serious audience. Nobody wants their account balance to develop an experimental relationship with decimal places.

The essay examined arithmetic errors and other reliability problems. Its opening compared the standards expected of an elevator with the more forgiving attitude often taken toward software failure. It is an engineer’s complaint about engineering, made specific enough to be useful: money gives familiar programming shortcuts consequences that a harmless display glitch does not carry.

Selency also supplied the commercial insight. Payment providers such as Stripe and MangoPay could accept and process payments. The challenge came afterward, allocating and tracking the amounts across orders, promotions, returns and differing seller commissions. Conversations with peers suggested that other platforms were building their own versions of this internal machinery. Salaün saw a backend that might become a product.

The distinction matters because the customer’s receipt and the business’s internal account of a sale answer different questions. The receipt says a payment occurred. The internal record must say what that payment means. Add a refund or an exception and a tidy checkout becomes a small committee meeting, with every participant expecting an accurate minute.

A company built around the missing record

The venture founded in 2021 was initially called Numary and joined Y Combinator’s Summer 2021 batch. It became Formance. Salaün’s work sits in product and engineering: he is co-founder and CTO. His co-founder, Anne-Sybille Pradelles, is CEO, overseeing the company’s commercial and operational functions.

Pradelles brought a different apprenticeship. She had been COO at cybersecurity company Alsid, joining when it had four people and helping it grow to more than 120 before its acquisition in 2021. A business angel introduced her to Salaün, who had already started building the product and participating in YC. The partnership joined experience in making the software with experience in making a company work around it.

A ledger became the foundation. Think of it as the record that explains balances through transactions. A number can tell you what an account contains now. A ledger should let you follow the movements that produced that number. For a business dealing with multiple parties, that history is part of the product’s everyday usefulness.

Consider a hypothetical hundred-dollar sale with a ten-dollar platform fee. The arithmetic is easy. The record must also preserve what belongs to the seller, when it became payable and what changes if the sale is reversed. A balance table alone can conceal how a number changed. Recording transactions gives a later investigator something to inspect.

Formance’s educational material uses examples like these to explain increasingly disciplined ledger models. Double-entry bookkeeping adds a balancing constraint across the entries in a transaction. Preserving history addresses another problem: a correction should remain legible rather than quietly overwrite the evidence. Those are useful distinctions in a field where a reassuring total can still conceal an unhelpful past.

The ledger leaves its own front door

Open source was part of Formance from the beginning. The code could be examined by the engineering teams being asked to depend on it. The practical appeal is easy to understand: if a system keeps the records behind customer balances, the people responsible for those balances may want more than a product demonstration.

Salaün has also discussed how that openness can coexist with a commercial relationship. Hosting, premium features and support provide different dimensions of the offering. A team can value access to the source while wanting help deploying and operating the software. Owning a map does not remove every reason to hire a guide.

“Ledgers do not live in isolation.”

Clément Salaün, announcing the Formance Platform, June 2024

That sentence marked the next stage. On June 25, 2024, Formance announced a broader platform, adding Connectivity, Flows and Reconciliation around the Ledger. Connectivity dealt with financial partners. Flows addressed the orchestration of money movement. Reconciliation compared internal records with the money represented externally. The surrounding work had come into the product’s frame.

For Salaün, modularity follows the variety of systems customers build. Different platforms use different partners and arrangements. Useful common software must leave room for those choices. The attraction of a shared ledger weakens if every customer must adopt precisely the same surrounding financial world.

In January 2025, Formance announced a $21 million Series A co-led by PayPal Ventures and Portage, with existing investors also participating. The company planned to expand in the United States and build its product and engineering teams. The financing supported a wider platform ambition, while the ledger remained its starting point.

Salaün described the surrounding infrastructure as a collection of smaller problems. Buying separate products could still leave expensive integration work inside the customer’s company. Formance’s proposition was to make those pieces work together while staying independent of the providers that actually process payments and hold funds. Integration has an unfortunate habit of surviving the purchase order.

When the numbers skipped a beat

One publicly recounted incident makes Salaün’s work more tangible than a list of modules. A customer’s transaction identifiers ran through 17, 18, 19 and 20, then jumped to 24. The system was supposed to generate an unbroken sequence. A gap made the record look as though transactions had gone missing.

Three engineers spent more than a week investigating. They traced one trigger to the way a customer combined previews, using a dry-run parameter, with actual transaction commits. After fixing that problem, the team targeted the sequence with additional testing in Antithesis. The first run exposed the same symptom from a different part of the code: a storage batching queue could fail while identifiers continued to be handed out.

The episode offers a particularly useful kind of candour. The simple-looking component had tests. The engineers were confident. A production case still found a route through their assumptions, and a second cause survived the first fix. In this account, identifying the unexpected behaviour was harder than making the final code change.

“In my work, I’m always trying to create an atmosphere of certainty”

Clément Salaün, on testing financial infrastructure, May 2025

Certainty here has work attached to it: reproduce the failure, state what must hold, and test whether it holds under conditions the team did not anticipate. The attractive part of the story is its refusal to end at the first plausible explanation. A gap in a sequence demanded a better account of the system.

Money has a colour, apparently

Salaün’s interests extend beyond a single database. His personal website links a 2019 talk about using Clojure and OpenSCAD to build 3D-printed models, treating manufacturing as something that can become collaborative and composable. It also identifies him as an angel investor through the micro-fund XEQR Capital. Building, describing and backing systems occupy adjacent places in his public working life.

His 2025 fintech_devcon talk, “The Color of Money”, returned to financial relationships. Its premise questioned the casual treatment of digital funds as interchangeable. A platform works with promises from partner institutions; those promises have locations and relationships that a single customer-facing balance can obscure. The talk asks the data model to retain those distinctions.

There is a line running through the Minecraft project, Selency’s allocations and that presentation. The money on a screen always belongs to a wider arrangement. Salaün’s work keeps asking the software to remember it. A buyer, seller or engineer eventually needs an explanation, and the most useful time to preserve that explanation is when the transaction happens.

A green tick remains a very good interface. Behind it, someone has to keep the promises in order.