Kulipa, a Paris-based stablecoin card infrastructure provider, stopped operating on July 29 after running into what it told clients were solvency problems. The shutdown immediately disabled all cards issued through its platform and affected about 20 wallet and fintech customers, including Solflare, Ready, Flutterwave, and nSave. Its website is now inaccessible.
The company was not a consumer-facing card brand. It positioned itself as a middle layer in the issuance stack, offering white-label stablecoin card infrastructure to wallets and fintech companies that did not want to handle issuance, compliance, and settlement on their own. According to disclosures from the company and its investors, Kulipa had issued more than 120,000 cards and signed 20 clients since launching its infrastructure in February 2025, with licensed operations in the European Union, Argentina, and Nigeria.
Background, team, and funding
Kulipa had a strong-looking executive roster on paper. CEO Axel Cateland previously worked at Mastercard and Spendesk. CTO Michael Shynar spent eight years at Google as a Staff Engineer and led work on WhatsApp’s monetization platform. Its compliance lead, Benoit, had built compliance systems for Nickel, Lemonway, and Binance France.
The company had raised about $9.2 million across two rounds. That included a $6.2 million seed round led by Flourish Ventures and 1kx, with White Star Capital and Fabric Ventures participating. The round was completed in December 2025 and disclosed in April this year. From that latest financing to the company’s closure, the timeline was roughly seven months.
Kulipa gave no detailed explanation beyond insolvency
Kulipa told clients it had a solvency problem, but it did not publish a detailed explanation of how it became insolvent. According to the report, the team tried to find a buyer and explored ways to keep the business going before the shutdown, but those efforts failed.
A more developed explanation came from industry analysis. Romeo Fardeen of Alea Research argued that the real moat in the payments layer is licensing, while Kulipa pursued a lighter model that did not hold funds directly and instead relied on licensed partners. In his view, that approach amounted to a survival model built on growth and the hope that a later funding round would make direct licensing possible. He had previously written: “Useful licenses are expensive and slow, and competition at this layer is extremely unfair. Only heavily financed startups or subsidiaries of giant fintech firms can really afford to play.”
That reading suggests Kulipa was serving smaller card programs that could not meet the threshold for providers such as Rain and Reap. Those clients tend to be smaller and lower-margin, leaving little room for error. On that basis, the company failed to clear the hurdles of licensing and scale before it ran through its cash.
There were signs of strain before the closure. Not long after announcing its financing in April, Kulipa’s official X account largely stopped posting, with its last tweet dated April 28. A few months later, the company shut down. In hindsight, that silence now looks like a possible signal of internal pressure. The contrast became sharper because about three months before the closure, a16z crypto had included Kulipa in its April stablecoin infrastructure map as one of the card issuance providers worth watching, and Kulipa proudly reposted it.
On the facts available publicly, Kulipa did not collapse because there was no demand for the product. The business failed in an infrastructure segment where licenses are dense, margins are thin, and capital needs are hard to outrun.
Impact differed across client types
Kulipa’s roughly 20 clients can be grouped into two broad categories.
The first group consisted of self-custody wallets, including Solflare and Ready. Solflare is a Solana wallet. Ready, formerly Argent, is a smart contract wallet and had worked with Kulipa on a zk debit card. In these products, funds are pulled from a user’s own wallet only at the moment of purchase. No user balance sits with Kulipa in normal operation. That means even if the issuer fails, there is no client balance for it to freeze or misappropriate. That is why Solflare and Ready were able to say quickly that user assets were safe.
A co-founder of Ready said the company received no advance notice before Kulipa suddenly stopped operating and had to shut down its own card business only after the cards stopped working. Solflare faced a similar sequence: the cards stopped first, and users learned about the problem after the fact.
The second group included custody-based fintech companies such as Flutterwave and nSave. Flutterwave is an African cross-border payments company, and its card business is focused on Nigeria and other African markets. nSave is a savings platform for emerging markets. These models are not self-custody wallets and typically involve holding user balances. Kulipa’s own documentation explicitly said it supported both “prefund deployments” and “native wallet integration,” meaning some clients did use the prefunded path in which users load money into an account controlled by the card program before spending.
nSave, one of the custody-based clients, also commented publicly on X. Team member Abdallah said nSave had been affected around a month earlier. According to his account, the team learned on a Saturday morning that Kulipa was in trouble, then worked with Kulipa to delay the shutdown by a few days. On Monday, nSave notified all users and told them to spend the funds on their cards within five days or switch to another card. He said no user suffered an unexpected decline, nobody lost money, and the company had already been preparing an alternative before the failure became public.
Abdallah added that it was a competence issue if users only discovered the shutdown after their cards had already stopped working. He also criticized peers for using self-custody as a shield, saying the right response was to build redundancy and warn users in advance rather than appeal to emotion after customers had already been put in a bad position.
As of publication, the main clients that had spoken clearly in public were Solflare, Ready, and nSave. Among the roughly 20 customers Kulipa said it served, Flutterwave and the remaining unnamed clients had not publicly explained the status of user funds or the steps being taken.
The company collapsed in a market that is still expanding
The sharpest contrast is that Kulipa failed in a segment that has been growing fast. Crypto card spending rose from about $100 million a month at the start of 2023 to more than $1.5 billion a month by the end of 2025. Data cited from The Kobeissi Letter showed monthly crypto card transaction volume reached $7.8 billion in May 2026, up 230% year over year.
Demand kept climbing, yet an infrastructure provider that had already reached a meaningful issuance scale still fell apart. That points to faster consolidation and shakeout in the layer beneath the consumer-facing card story.
For users, the takeaway is straightforward. Cashback and spending limits are not the only things to check when choosing a crypto card. It also matters who holds the money before a purchase is made. Products that debit directly from a self-custody wallet at the point of sale, without leaving balances with the issuer, are structurally better insulated if another provider in the stack fails.