The full stack, explained simply.Running stablecoin operations requires six foundational layers. Most FIs underestimate the scope — this guide helps you understand what's needed and who on your team should own each piece.The Full Stack#
| Layer | What It Covers | Internal Owner |
|---|
| 1. License | Legal authorization to operate | Legal / Compliance |
| 2. Custody | Secure key management and wallet infrastructure | CTO / Security |
| 3. Issuer Access | Stablecoin on/off-ramp relationships | Treasury / Ops |
| 4. Liquidity | Market making and fiat corridor management | Treasury |
| 5. Compliance Stack | KYC/AML, sanctions, transaction monitoring | Compliance |
| 6. Interoperability | Cross-FI routing and network access | Product / Compliance |
Layers 1-5 are prerequisites. Layer 6 is where the Stablecoin Clearing Network fits.Layer 1: License#
What it is: Your legal right to offer stablecoin services — custody, transfer, exchange.Who owns it: Legal / Compliance| Region | Framework | Key Requirements |
|---|
| EU | MiCA (Dec 2024) | CASP authorization, capital requirements, governance |
| UK | FCA Registration | Cryptoasset registration, AML controls |
| US | State-by-state | NY BitLicense, state MTLs, FinCEN registration |
| Emerging Markets | Varies | Often EMI/PSP frameworks, sometimes crypto-specific |
Timeline: 6-18 months depending on jurisdictionKey decision: Apply in one jurisdiction first, then passport (EU) or expand.Layer 2: Custody#
What it is: Secure storage and management of private keys. This is where stablecoins "live" when your FI holds them.Who owns it: CTO / SecurityOptions#
| Approach | Description | Trade-offs |
|---|
| MPC (Multi-Party Computation) | Keys split across multiple parties | Most common for institutions; Fireblocks, Copper, etc. |
| HSM (Hardware Security Module) | Keys stored in tamper-proof hardware | High security, more complex ops |
| Qualified Custodian | Third party holds assets on your behalf | Simplest, but counterparty risk |
| Self-Custody | You manage everything | Maximum control, maximum responsibility |
Key providers: Fireblocks, Copper, BitGo, Anchorage, Coinbase PrimeTimeline: 2-6 months to implementLayer 3: Issuer Access#
What it is: Direct relationships with stablecoin issuers (Circle, Tether) for minting and redemption.
Who owns it: Treasury / Ops
Without issuer relationships, you pay spread on every on/off-ramp:With issuer access: Mint/redeem at par (0% spread)
Without: Buy/sell on exchanges (0.1-0.5% spread)
Circle (USDC, EURC) — regulated, transparent reserves, strong institutional focus
Tether (USDT) — largest by volume, wider exchange availability
Timeline: 2-4 weeks for account setup; ongoing compliance requirements
Layer 4: Liquidity#
What it is: The ability to move between stablecoins, chains, and fiat at scale without moving markets.
Fiat corridors: Bank relationships for large fiat movements
Cross-chain liquidity: Ability to source stablecoins on multiple chains
Market making: Maintaining spreads on your own exchange/product
Float management: Pre-funding for instant settlement
Key challenge: Stablecoin liquidity is fragmented across 10+ chains. Managing treasury across chains is operationally complex.
Timeline: Ongoing — liquidity operations are continuous, not one-time setup
Layer 5: Compliance Stack#
What it is: The systems that ensure every transaction meets regulatory requirements.Components#
| Component | Purpose | Key Vendors |
|---|
| KYC/KYB | Verify customer/business identity | Jumio, Onfido, Sumsub |
| Sanctions Screening | Check against OFAC, EU, UN lists | Chainalysis, Elliptic, TRM Labs |
| Transaction Monitoring | Flag suspicious patterns | Chainalysis, TRM, Flagright |
| Travel Rule | Exchange counterparty data on VASP-to-VASP transfers | Notabene, TRUST, 21Analytics |
Key insight: Most FIs have these components but struggle with interoperability — getting them to work together across counterparties.Timeline: 3-6 months for full implementationLayer 6: Interoperability#
What it is: The ability to send stablecoins to other FIs with compliance built in.
Who owns it: Product / Compliance
Layers 1-5 let you hold and manage stablecoins. But they don't solve:Counterparty discovery: How do you find other licensed FIs?
Travel Rule exchange: How do you share compliance data before the transfer?
Cross-chain routing: What if you're on Ethereum and they're on Tron?
Policy matching: Can you even transact with this counterparty?
What's Required#
| Capability | Without Network | With Network |
|---|
| Find counterparties | Manual BD, one-off deals | Directory of licensed FIs |
| Exchange Travel Rule data | Build N integrations | Single integration |
| Route cross-chain | Manage multiple rails | Abstracted routing |
| Pre-clear transactions | Post-hoc compliance | Pre-flight verification |
This is where the Stablecoin Clearing Network fits. RemiDe solves Layer 6 — routing, counterparty discovery, and Travel Rule exchange — so you can focus on Layers 1-5.
Putting It Together#
Typical Timeline#
| Phase | Duration | Layers |
|---|
| Foundation | 6-12 months | License, Custody |
| Operations | 3-6 months | Issuer Access, Compliance Stack |
| Scale | Ongoing | Liquidity, Interoperability |
Internal Ownership Summary#
| Layer | Primary Owner | Secondary |
|---|
| License | Legal | Compliance |
| Custody | CTO / Security | Ops |
| Issuer Access | Treasury | Ops |
| Liquidity | Treasury | Finance |
| Compliance Stack | Compliance | Legal |
| Interoperability | Product | Compliance |
Ready for Layer 6?#
If you've got Layers 1-5 covered (or close), let's talk about interoperability.
Book Consultation
