Why neobanks die: the compliance stack behind $245M-a-week crypto cards
Figures in this post describe a snapshot of 365 tracked neobanks. The dataset now tracks 380, so counts here will not match the live site — the analysis stands, but for current numbers use the browsable cuts, the live directory or data.json.
Last week crypto-card top-ups hit an all-time high: over $245M in a single week, 18% above anything previously recorded, per Paymentscan ↗. Demand is emphatically not the problem. And yet the honest read of the last eight years is that most of the companies riding that chart will not exist when the market is ten times bigger — not because users leave, but because of what they built underneath. This post maps the stack that actually decides who survives, layer by layer, grounded in our data on 365 tracked neobanks.
The graveyard has a pattern
| Year | Event | The lesson |
|---|---|---|
| 2018 | Visa terminates WaveCrest, the issuer behind most of Europe's crypto cards | Every card in the portfolio died overnight — Bitwala, TenX, Cryptopay and more, in one stroke |
| 2020 | Wirecard collapses; the FCA freezes Wirecard Card Solutions | Curve, Pockit, Anna and dozens of "real" fintechs went dark for days — customer funds untouchable |
| 2022 | FTX implodes | Commingled customer funds are an insolvency bomb, whatever the terms of service say |
| 2023 | Binance loses Visa in Europe (July), then Mastercard in LatAm and the Middle East (September) | Network confidence is a compliance judgment; when it goes, the card is gone by Christmas |
| 2025 (Dec) | Bank of Lithuania fines Monavate €270,000 and bans it from serving Kulipa — the issuer relationship breaks before the cards do | Regulator action on your sponsor is a leading indicator; the brand on the card finds out last |
| 2026 (Jun) | Ready (ex-Argent) ends non-EEA cards after issuer Kulipa tightened footprint — user assets stayed self-custodial, only the spending rail changed | Card termination ≠ neobank death — but the issuer layer is always someone else's call |
| 2026 (Jul) | Kulipa winds down on solvency — Solflare card paused Jul 28; Ready program goes with it | Same WaveCrest topology for self-custodial cards: one issuer failure, every brand on its rails stops — wallet balances unaffected when spend is at POS from your keys |
Four institutional failures, three card-rail disruptions — same underlying mechanism on the card layer (the brand doesn't control the issuer), very different outcomes for customer funds. Wirecard froze balances; Ready and Solflare users' crypto stayed in their wallets. The names change; the card dependency doesn't.
graveyard array of data.json. Deaths are data too.Case study: Kulipa — $9M peak, then the cards stopped
Kulipa is the clearest live read of what happens when issuer solvency and PR diverge. Paris-based, self-custodial at the wallet layer — 120,000+ cards issued across ~20 B2B clients, only Ready and Solflare among the names we track. Paymentscan, which monitors onchain volume for those two programs, shows the arc in numbers:
| Metric | Figure | Source |
|---|---|---|
| Lifetime card volume | $68.4M | Paymentscan (Nov 2024 – Jul 2026) |
| Peak month | $9.0M (Jan 2026) | Paymentscan |
| Last partial month | $1.84M (Jul 2026) | Paymentscan |
| Transactions | 614,676 over 21 months | Paymentscan |
The timeline runs regulator → retrenchment → wind-down, not the other way around:
| When | What happened |
|---|---|
| Dec 2025 | Bank of Lithuania fines Monavate €270,000 and bans it from serving Kulipa; the $6.2M round quietly closes the same month |
| Jan 2026 | Peak — $9.0M in card volume |
| Apr 2026 | Public $6.2M round announcement, 70% month-over-month growth claims, US expansion named — volume already sliding onchain |
| Jun 2026 | Europe-only issuer; Ready cuts every user outside the EEA |
| Jul 2026 | Cards stop; Solflare confirms wind-down Jul 28 |
The gap between the Apr 2026 press release and the Paymentscan chart is the lesson: growth marketing and issuer health are different variables. Kulipa had real volume — $9M in a month is not a toy program — but one sponsor ban and a balance-sheet problem killed every brand on its rails in seven months. Self-custody meant no Wirecard-style freeze; it did not mean a card that keeps working.
Layer 1: the card — a three-party relationship you're the junior partner in
A card program is you, your issuer, and the network — and the network's due diligence sits on top of the issuer's. If either loses confidence in your screening, monitoring or KYC, the card stops. Not gradually. Kulipa is the live case study — see above — and the pattern holds: first Ready lost non-EEA spending (Jun 2026), then the issuer itself wound down and took Solflare's card with it (Jul 2026). Both were self-custodial — wallet balances never sat with the issuer — so this wasn't Wirecard. But every program on Kulipa's rails died together anyway. Self-custody solves custody risk, not issuer risk.
Our dataset makes the dependency visible. All 35 web3-native card programs we track ride on a thin layer of BIN sponsors and issuing platforms: Rain (behind Karta and Hyperbeat's card), Baanx (behind MetaMask Card), Wirex (behind COCA), DCS, Immersve and Fiat24 (splitting Bitget Wallet's geography three ways), Marqeta (behind BFinance). That concentration is exactly the WaveCrest topology of 2018, one layer more professional. When one of these sponsors sneezes, a dozen brands catch pneumonia simultaneously.
And the bar keeps rising. Starling — a fully licensed UK bank — was fined £29M in 2024 because its automated system had screened customers against only a fraction of the sanctions list for years. If that's the standard applied to a licensed bank, imagine the diligence a network runs on a two-year-old stablecoin card startup.
Layer 2: ramps — a compliance event before it's a UX event
Every on-ramp is an account opening: identity, source of funds, risk scoring before a dollar moves. Every off-ramp is where regulators actually look, and where teams underinvest because users don't see it. The failure mode is predictable: screening happens at signup and never again, the banking partner pulls a transaction sample at quarterly review, the per-transaction trail isn't there, and the relationship ends at the worst possible moment. The SurfCash-style QR-rail products make this concrete — every VietQR or Pix payout is an off-ramp with a local counterparty, which is why "licensed local partners" appears in their structure and why that line matters more than the app design.
Layer 3: earn — the ledger question that kills diligence
Yield products look like a product decision and are actually a legal-structure decision. The question that ends shared-vault architectures is one sentence: show me the ledger entry for user X's balance. If the answer requires reconstructing it from pool accounting, there is no answer — not for a banking partner, not for a regulator, not for an insolvency court. FTX is the terminal case study of commingling; every "up to 15%" headline in our dataset should be read with that question in mind, and it's why we record yield claims verbatim rather than endorsing them.
Europe adds a twist most teams haven't priced in: MiCA prohibits paying interest on e-money tokens — euro stablecoin balances can't earn as stablecoins. The compliant path runs through tokenized T-bills and RWA wrappers, where yield comes from an underlying asset rather than the token. Whoever industrializes that first owns European earn. Background: MiCA and the crypto neobanks.
Layer 4: rewards — the cheapest layer to get wrong
Rewards with monetary value carry reporting obligations, and paying them in your own token adds volatility risk for the user plus securities-classification risk for you. The clean structure is boring: fund from interchange, pay in a regulated instrument, reconcile per user per period. The dataset already shows the pattern of promotional gravity: Kolo quietly cut its headline cashback from 5% to 2%, Lava reversed its entire custody model after raising $200M. Terms are variables, not constants — which is precisely why the U-card comparison tracks them as claims.
Layer 0: screening — the layer underneath everything
Most teams assemble compliance reactively: something breaks, a partner flags a transaction, then the stack gets built. The survivors build it in the opposite order — screening and monitoring before the card, source-of-funds framework before the ramp volume, isolated ledger before the earn product. Point tools (Chainalysis, Elliptic, TRM, Sumsub, ComplyAdvantage and peers) each do a slice well, but every gap between tools is a reconciliation problem discovered during an audit.
There's a newer twist: your compliance vendor is now itself a counterparty risk. In February 2026, researchers reported that a database linked to KYC provider IDMerit had exposed roughly a billion identity records across 26 countries (the company disputes that its own systems were breached). The identity data you're required to collect is also the data you're liable for — choosing who holds it is a survival decision, not a procurement line item.
What this means for reading the chart
The $245M week is real, and it's not a card story or a yield story — it's a stress test arriving on schedule. As volumes grow, issuer diligence tightens, network reviews deepen, and the gap between "shipped fast in year one" and "rebuilt everything in year two" becomes existential. When you compare neobanks in our directory, the fields that predict survival aren't cashback and APY — they're the boring ones: license type, custody model, and who actually issues the card. We put them on every profile for exactly this reason.
Volume data: Paymentscan (July 2026). Historical events compiled from public reporting — FCA notices, network statements, court filings; license and issuer structures per entity are sourced on each profile. Nothing here is legal or investment advice. Spotted an error? Suggest a fix.