MiCA CASP license alternative — without becoming a CASP yourself.
Our rail partner holds EU Crypto-Asset Service Provider and Payment Institution authorisations under MiCA. ItisPay is the software layer above. Plug in via API, keep your brand and your AML, go live in one week.
Build your own CASP for €295K+ in year 1 —
or plug in for €0 upfront.
EU regulators are moving operators off transitional regimes. Going for your own MiCA CASP licence takes 12–18 months and locks up hundreds of thousands in capital and ongoing costs. There's a faster path.
See the alternativeApplying for your own MiCA CASP
Year 1 cost breakdown
Integrate ItisPay. Inherit a fully licensed CASP + PI counterparty.
ItisPay is a non-custodial orchestration layer above a licensed EU rail partner. You don't take custody of client funds, you don't run a separate compliance stack, you don't relicense — you plug into ours.
Submit KYB
Standard corporate documents, UBO disclosure, source-of-funds attestation, activity declaration.
Compliance review
Our licensed rail partner runs full KYB. Sumsub shared KYC means existing applicants pass through without re-verification.
API integration
Three API calls to integrate: create invoice, query status, register webhook. Sandbox available immediately.
Go live
Pre-fund your settlement account, push your first transaction. Real-time deposit callbacks under 200ms.
The full crypto-fiat capability surface — under one licensed counterparty.
All flows below run through a single EU-licensed CASP and Payment Institution. One commercial contract, one compliance review, one settlement reconciliation.
On-ramp & off-ramp
SEPA, SEPA Instant, SWIFT. 14 fiat currencies for deposit (incl. GBP via FPS, auto-converted to EUR). Settlement in EUR or USD.
Mass crypto payouts
Stablecoin payouts to 140+ countries. USDT (ERC-20, TRC-20, Polygon), USDC (ERC-20, Polygon, Base), BTC, ETH, LTC, DOGE, SOL, TON.
Named vIBANs
EUR virtual IBAN issued in your client's company name. Incoming crypto deposits auto-converted to fiat on receipt.
API automation
100% API-driven settlement. Webhook callbacks under 200ms. Sandbox environment available from day one.
No fund handling
Client funds never touch your books. Custody, settlement, AML monitoring, sanctions screening — all on the licensed counterparty.
White-label dashboard
Customisable merchant portal, invoicing UI, sub-accounts. Your brand on the front, our API and our partner's licence behind it.
MiCA CASP license vs alternatives: the honest comparison.
Four ways to get MiCA-compliant rails. Three of them take a year or longer, or come with substantial recurring cost. Here's the side-by-side.
| ItisPay (Software Layer) | Apply for your own CASP | OTC desk arrangement | Direct banking partner | |
|---|---|---|---|---|
| Time to live | 1 week | 12–18 months | 1–3 months | 3–6 months |
| Upfront regulatory capital | €0 | €125K–€150K+ (MiCA Art. 67) | Pre-funding only | €50K–€200K reserves |
| EU passporting | ||||
| Cryptocurrency settlement | ||||
| No fund handling on your side | ||||
| Recurring cost | Volume-based fee | Compliance team €€€ | Spread + manual ops | Account fees + minimums |
MiCA + DORA compliance, audit-ready by default.
Every transaction generates a structured evidence object. Every KYB check is logged. Every decision is traceable. Built for FATF Travel Rule, MiCA Article 19a, and EU AML directives.
EU-licensed counterparty
Our rail partner holds both MiCA CASP and Payment Institution authorisations. AML and KYC handled at the licensed level.
Shared KYC via Sumsub
Existing applicants pass through with a shareToken — no re-verification, no duplicate compliance friction.
Sanctions & AML screening
Sanctions screening (sanctioned addresses, PEPs, adverse media) and ongoing AML transaction monitoring run automatically at the licensed counterparty.
Documented screening trail
Every pre-qualification check, KYB document, and compliance decision is stored with timestamps and audit chain — ready for supervisor review.
50-country exclusion list
Geographic restrictions applied automatically at intake. Full FATF and EU sanctions list compliance.
GDPR & data protection
EU data residency, DPA in place, contractual safeguards across the chain. Your clients' data stays inside the EU regulatory perimeter.
Questions VASPs ask before plugging in.
If your question isn't listed, book a call — we'd rather answer once with full context than send a generic FAQ entry.
It stays yours. ItisPay doesn't replace your authorisation — we plug your operation into a licensed CASP + PI counterparty so you can continue serving the EU market without applying for a new MiCA licence yourself. Your existing AML program, your existing customer base, your existing brand.
No. ItisPay is a non-custodial orchestration layer. Funds flow directly between your client and the licensed rail partner. We never hold, transfer, or have signing authority over crypto or fiat balances.
EU/EEA, UK, Switzerland, Canada, most of LatAm and APAC. We follow our rail partner's geographic policy — 50 countries are excluded (full list available under NDA). US-incorporated entities and US-citizen UBOs are not onboarded under current scope.
Standard corporate structures — LLC, GmbH, S.A., Sp. z o.o., Ltd., etc. Partnerships, trusts, foundations, sole traders, SPVs, and micro-enterprises (under EU definition) are not currently in scope. Reach out if you're unsure where your structure sits.
Volume-tiered transaction fee plus a monthly platform fee. Specific rate is shared after the pre-qualification call — it depends on your expected volume, vertical, and add-ons (Named IBAN, FX coverage). Setup fees may apply depending on the engagement.
We use Sumsub shared KYC. Your existing applicants flow into the rail partner's review via a shareToken — no double verification, no extra friction for your users. We'll walk through the configuration during integration.
A TFR vendor sits beside the payment, generating compliance artefacts after the fact. Our layer lives inside the payment flow — every verification step is captured with full transaction context (counterparty profile, rail-side metadata, intent). The result is one signed evidence object per transaction, not three logs stitched together at audit time.
30 minutes. Your KYB scope. A timeline.
Tell us your jurisdiction, expected monthly volume, and primary use case. We'll come back with a pre-qualification answer the same day — and a draft integration timeline.
Or email [email protected] directly.