Educational Demo Only — This POC illustrates how software can model MiCA (EU Reg. 2023/1114) requirements. It is not legal advice and does not constitute MiCA compliance certification.

CASP Client Asset Segregation & Safeguarding

Track and verify client crypto and fiat assets held in segregated accounts per MiCA Art. 70

Load example scenarios:

Crypto Custody

All crypto in compliant custody (Art. 70(1))

Fiat Accounts

All fiat in segregated accounts (Art. 70(3))

Insurance

€500,000 coverage

Crypto Balances

Fiat Balances

Art. 67(4) allows own funds, insurance or a combination; this POC requires insurance > 0 (policy)

Total Assets Under Management

€123,500

Crypto: €43,500 | Fiat: €80,000

MiCA Compliance Note

Implemented: Art. 70 — Clients' crypto-assets and funds must be safeguarded and never used for the CASP's own account. This POC validates that client holdings are in compliant custody types (CASP segregated wallets, Art. 75(7), or another CASP authorised for custody, Art. 75(9), for crypto; separately identifiable accounts at a credit institution or central bank for funds, by the end of the next business day — Art. 70(3)).

Implemented: Art. 75(5) — Statement of position for clients (required at least once every three months), with segregation confirmation.

Implemented: Art. 67(4)(b) — Insurance policy or comparable guarantee as a form of prudential safeguard (validated as a POC policy).

Out of scope: Art. 70(1) — Real blockchain verification of CASP's own wallet segregation. POC assumes input data is accurate.

Out of scope: Real insurance provider integration or certificate validation.

Out of scope: Crypto custody audit trail or transaction history.

What this POC does not implement

  • ❌ Live blockchain verification — requires node integration and wallet signing capabilities
  • ❌ Real bank account verification — requires licensed bank integration
  • ❌ Insurance certificate validation — requires provider API integration
  • ❌ Multi-year historical tracking — POC shows single snapshot
  • ❌ Client identity verification — assumes client data is pre-verified