Skip to content
Main

MiCA Survival Guide · Section 4

The Fatal Complexity Trap

Why multi-vendor approaches fail under DORA

Read
5 min
Words
1,000
Updated
Apr 2026
Topics
  • Vendor architecture
  • DORA
  • Cost analysis

The typical applicant's tech stack

10+ vendors to manage and integrate

  • Core banking system (Mambu, Temenos, or custom)
  • Custody solution (Fireblocks, Copper, BitGo, or self-managed)
  • Blockchain analytics (Chainalysis OR TRM Labs OR Elliptic)
  • AML transaction monitoring (ComplyAdvantage, Sanctions.io, or custom)
  • KYC/identity verification (Jumio, Onfido, Sum&Substance)
  • Travel Rule compliance (Notabene, Sygna Bridge)
  • Accounting system (NetSuite, Xero, SAP)
  • Cloud infrastructure (AWS, GCP, Azure)
  • Payment gateway (for fiat on/off-ramps)
  • Customer data platform / CRM

The DORA compliance burden

For EACH third-party ICT provider, you must:

  • Conduct pre-contractual due diligence
  • Verify regulatory authorization status
  • Assess financial soundness
  • Evaluate technical capabilities (cybersecurity, HSM/MPC)
  • Document in your Register of Information
  • Establish service level agreements with quantitative targets
  • Define incident notification procedures
  • Maintain access and audit rights
  • Ensure data recovery and portability guarantees
  • Document exit strategies with transition periods

Real-world failure scenario

The integration gap in action

1
Customer deposits Bitcoin from Binance.
2
Your custody solution (Fireblocks) records the deposit.
3
Your blockchain analytics (TRM Labs) flags the address as medium risk (prior mixing service exposure).
⚠️

THE PROBLEM

But this alert arrives in a separate dashboard. Your AML monitoring system (ComplyAdvantage) doesn't see the blockchain analytics alert.

RESULT: FAILURE

Your transaction monitoring misses the rapid deposit-withdrawal pattern. Suspicious transaction not flagged in real-time.

Regulator's question:

"Please provide evidence of how your blockchain analytics data feeds into your real-time transaction monitoring system, and demonstrate the latency between a high-risk wallet detection and transaction blocking."

Your answer

"They're separate systems. We manually review blockchain analytics alerts daily and update our risk scores."

The total cost of (non-)integration

IntegrationComplexityDeveloper TimeEstimated Cost
Core Banking ↔ CustodyHigh3-6 months€60,000-€120,000
Blockchain Analytics ↔ CoreHigh2-4 months€40,000-€80,000
Travel Rule ↔ MonitoringVery High3-5 months€60,000-€100,000
Custody ↔ AccountingMedium2-3 months€30,000-€60,000
Unified Audit TrailVery High2-4 months€40,000-€80,000
TOTAL DEVELOPMENT COST12-22 months€230,000-€440,000
Search
Type to search across research, articles, and pages.

    Press Esc to close · to open the highlighted result.