Bottom line: BitGo Europe’s BaFin-licensed Crypto-as-a-Service now lets firms without a CASP license migrate clients into MiCA-compliant sub-accounts before the June 30 hard deadline.
BitGo Europe’s BaFin-regulated Crypto-as-a-Service platform now lets firms without a CASP license onboard clients into MiCA-compliant sub-accounts before the June 30 deadline. This offers a compliance lifeline as 75% of Europe’s 3,000+ pre-MiCA operators face deregistration [1].
The clock is ticking louder than most builders realize. June 30, 2026 marks the hard cutoff for crypto firms to operate under the EU’s Markets in Crypto Assets (MiCA) regime. After that date, any entity without a Crypto Asset Service Provider (CASP) authorization — or a regulated partner — must cease serving European customers.
“All of your clients can be onboarded and have sub-accounts inside of BitGo,” CEO Mike Belshe said. “Now, they are your clients: you help them with support, you help them with all of the products, you do all that stuff, we don’t do any of that. But they are now in segregated safe storage that’s MiCA-compliant.”
The Numbers Behind the MiCA Compliance Crunch
The scale of the coming shakeout is stark. Europe hosted more than 3,000 registered crypto firms as of 2024, with Poland alone accounting for over 1,400 registrations. By May 2026, only 194 entities held full CASP authorization (including credit institutions), according to law firm Hogan Lovells. The firm projects ~75% of the pre-MiCA population will lose registration status as transitional periods expire [1].
| Metric | Figure | Source |
|---|---|---|
| Pre-MiCA registered firms (2024) | 3,000+ | Industry estimates |
| Polish registrations (2024) | 1,400+ | Industry estimates |
| Authorized CASPs (May 2026) | 194 | Hogan Lovells |
| Expected attrition rate | ~75% | Hogan Lovells projection |
This isn’t theoretical. Binance — the world’s largest exchange — was reportedly rejected for an EU regulatory license by Reuters, signaling that even well-capitalized giants face hurdles [3]. The message: building your own CASP stack is no longer a default option.
How BitGo’s MiCA Compliance Bridge Works
BitGo’s pitch is operational, not aspirational. Firms that have already completed MiCA-aligned KYC on their customers can:
- Integrate existing wallets into BitGo’s infrastructure via API
- Migrate clients into segregated sub-accounts under BitGo Europe’s BaFin license
- Retain full front-end relationship — support, product, UX — while BitGo handles custody, compliance, and regulatory reporting
- Pursue their own CASP license in parallel if desired, using the bridge as runway
The prerequisite is non-trivial: KYC must already meet MiCA standards. Firms with legacy onboarding flows will need to remediate before migration.
Pricing: “A Couple of $1,000 a Month”
Belshe described the fee structure as “relatively cheap” and product-dependent:
- Monthly minimum: “a couple of $1,000 a month type of thing that can scale with volume”
- Variable plans: pay-per-transaction, higher per-unit cost
- Static plans: fixed fee, lower effective rate at scale
This positions BitGo as infrastructure middleware — not a white-label exchange. The firm does not touch end-user support, product design, or token listings. It provides regulated rails; the client provides the business logic.
Why This Matters for Builders
For Wallet & Custody Teams
If you’re shipping a non-custodial wallet or MPC-based custody product in Europe, you now have a regulated settlement layer that doesn’t require you to become a CASP. Integrate BitGo’s API, migrate keys, keep your UX.
For DeFi Front-Ends & Aggregators
On-ramp/off-ramp compliance is the hardest MiCA piece. BitGo’s sub-account model lets you segregate user funds under a BaFin license while you focus on routing, MEV protection, and UX.
For Token Issuers & Stablecoin Projects
ART/EMT issuers need CASP-authorized distributors. BitGo’s network of 194+ authorized CASPs (and growing) becomes a distribution channel — provided your token passes their compliance screen.
For Compliance Engineers
The KYC remediation burden is real. MiCA requires enhanced due diligence, travel rule compliance, and transaction monitoring that most pre-2024 stacks lack. Budget Q3–Q4 2026 for this work if you haven’t started.
The Two-Tier Market Emerging
We’re watching a structural split form:
| Tier | Profile | Examples |
|---|---|---|
| Licensed CASPs | Full MiCA authorization, own compliance stack | Coinbase Germany, Bitpanda, BitGo Europe |
| Infrastructure Tenants | Operate under partner’s license via CaaS/BaaS | Regional exchanges, wallet apps, DeFi front-ends |
The 75% attrition estimate suggests most current operators become tenants or exit. This concentrates regulatory surface area into a handful of BaFin/AMF/CBI-supervised entities — a systemic risk if one infrastructure provider fails.
Regulators Are Watching
Belshe noted regulators are aware of BitGo’s compliance-enhancing infrastructure. That’s code for: BaFin has blessed this model. But it also means supervisory scrutiny will intensify on:
- Sub-account segregation (no commingling)
- KYC/AML data sharing between tenant and provider
- Operational resilience of the CaaS platform itself
Firms using this bridge should document their shared responsibility model now — not during an audit.
Practical Checklist for Q3 2026
- [ ] Audit your KYC against MiCA Article 66–67 requirements
- [ ] Map user flows to identify which funds need segregated custody
- [ ] Evaluate CaaS providers (BitGo, Fireblocks, Copper, Tangany) on: API latency, settlement finality, fee transparency, regulator dialogue
- [ ] Negotiate data portability clauses — you may want your own CASP later
- [ ] Stress-test the provider’s disaster recovery and insolvency remoteness of sub-accounts
Related Reading
- MiCA regulation explained: See our deep dive on EU crypto rules and CASP requirements for the full regulatory framework.
- CASP license guide: Compare licensing paths in CASP license requirements for EU 2026.
- Custody infrastructure: Review BitGo Europe’s BaFin-regulated custody stack alongside Fireblocks and Copper.
The Takeaway
MiCA isn’t a suggestion — it’s a deadline with teeth. BitGo’s CaaS bridge is the first credible, BaFin-blessed “compliance-as-a-service” rail for firms that can’t or won’t build their own CASP. It buys operational continuity at the cost of dependency on a single infrastructure provider.
For builders, the strategic question isn’t “should we use BitGo?” It’s: “How do we architect our stack so we can swap the compliance layer without rewriting the product?” The firms that answer that by Q4 2026 will own the European market. The rest will be tenants — or gone.
