Jurisdiction • El Salvador
El Salvador: company setup and digital asset structuring (incl. DASP route, where applicable).
El Salvador is often considered by crypto and tokenization teams that want a pragmatic jurisdictional base,
a clear corporate layer and a licensing/compliance narrative for counterparties. The right route depends on your activity:
custody responsibility, exchange/brokerage flows, token issuance, marketing footprint and the need for banking/PSP support.
We focus on “workable compliance + contracts” that match real flows — and reduce friction with banks, partners and exchanges.
Best fit for El Salvador
- Crypto and Web3 teams needing a clean operating/holding layer.
- Tokenization projects preparing disclosures and contracts.
- Businesses building compliance readiness for partners.
- Teams looking for a pragmatic jurisdictional base.
Often paired with Compliance and
Web & Crypto.
Routes
Typical engagement routes in El Salvador
We start with activity mapping and counterparties (banks/PSPs/exchanges). Then we lock the structure and the document scope.
Route
Company setup & structuring
A clean corporate layer for operating or holding.
- Structure and activity fit memo.
- Ownership / governance baseline.
- Founders’ arrangements (control, vesting, exit).
- Contract baseline for vendors and partners.
Best for: cross-border operations, Web3 builders, holding structures.
Route
DASP positioning (where applicable)
If your activity requires a regulated narrative and approvals.
- Services map (custody/exchange/transfer/issuance).
- Compliance baseline and evidence trail.
- Policies/procedures aligned to real flows.
- Partner/bank readiness narrative.
We avoid “license assumptions” without mapping activity.
Route
Tokenization & disclosures
When risk disclosures and investor/partner documentation are core.
- Token/asset flow classification memo.
- Risk disclosures and restricted jurisdictions logic.
- Website/product legal docs.
- Contracts with issuers, vendors and counterparties.
Best for: RWA/tokenization and cross-border marketing control.
Deliverables
What we prepare for El Salvador projects
Scope depends on your business model and counterparties. Below is a baseline that covers most cross-border crypto setups.
Core
Route memo & controls map
A practical plan tied to your real flows.
- Activity mapping and regulatory positioning.
- Custody/control responsibility matrix.
- Counterparties map (banks/PSPs/exchanges).
- Deliverables checklist + timeline plan.
Outcome: fewer surprises and less rework.
Corporate
Corporate & governance baseline
Clean ownership, governance and decision-making.
- Founders/shareholder arrangements (if needed).
- Board/management roles and delegated authorities.
- Resolutions and governance register baseline.
- Group structuring support (if multi-jurisdiction).
Useful for banking, investors and DD.
Compliance
AML/KYC & sanctions baseline
Implementable onboarding and monitoring rules.
- CDD/EDD logic and client risk scoring.
- SOF/SOW evidence rules (as needed).
- Sanctions/PEP/adverse media workflow.
- Recordkeeping and incident escalation.
Critical for banks/PSPs and serious partners.
Legal
Client-facing & product legal docs
Terms, privacy, disclaimers and risk disclosures.
- Terms of Use / service terms (product-specific).
- Privacy & cookie notices (as needed).
- Risk disclosures for crypto/tokenization models.
- Restricted jurisdictions and client type rules.
Goal: reduce legal risk in cross-border onboarding.
Ops
Operational procedures (SOPs)
Day-to-day procedures the team can execute.
- Onboarding procedures and periodic reviews.
- Approvals and escalation workflow.
- Outsourcing controls and vendor due diligence.
- Incident handling and communications baseline.
Designed for real execution, not templates.
Deal
Partnerships & deal support
Contracts and due diligence support as you scale.
- Exchange listing / partner agreements (as needed).
- Custody / liquidity / payment provider contracts.
- Tokenization SPV or issuer agreements.
- Cross-border deal support and legal review.
Good for scaling and institutional counterparties.
Approach
How we reduce licensing & banking friction
In practice, the biggest delays come from unclear flows, missing evidence, and inconsistent documents. We fix that early.
What we map first
- Client types, geographies, risk exposures.
- Flow of funds and assets (fiat rails, wallets, custody).
- Counterparties: banks, PSPs, exchanges, custodians, LPs.
- Outsourcing and technology stack responsibilities.
Output: a controls map showing responsibilities, evidence and escalation lines.
Typical engagement paths
Banking readiness
AML/KYC + sanctions → onboarding SOPs → evidence pack.
Licensing readiness
Compliance framework → policies set → narrative alignment.
Tokenization readiness
Disclosures → issuer/SPV contracts → restricted markets logic.
Existing business clean-up
Gap review → rewrite docs → implement procedures → reporting cadence.
Related: Compliance and
Tokenization.
FAQ
Common questions
Short answers. We confirm the exact route after mapping your business model.
Is El Salvador a “one-step crypto license” jurisdiction?
No. The route depends on what you actually do (custody, exchange/brokerage, issuance, marketing footprint). We start by mapping services and counterparties, then define the correct compliance and documentation scope.
Can we start with company setup and add compliance later?
You can, but it often slows down banking and partnerships. Banks/PSPs typically ask for AML/KYC, sanctions controls, onboarding procedures and a coherent funds/asset flow narrative early.
What documents do we need at minimum?
Usually: corporate governance baseline, business description and flow narrative, contracts (vendors/partners), and client-facing legal docs (terms/privacy/risk disclosures). Add AML/KYC and SOPs if you touch client assets or need banking.
Can you start with a route memo first?
Yes. It’s often the best start: we prepare a short recommendation (structure + compliance baseline + deliverables plan), so you can make decisions before committing to a full licensing track.
Need an El Salvador route memo and document scope?
Send a short description: what you do, target markets, whether you hold client assets, and your banking/licensing goal.
We’ll propose a practical structure and the first deliverables.
If you already have policies/docs, we can start with a gap analysis and update only what is missing.
Good fit for this route:
- Crypto/Web3 teams needing a clean corporate base.
- Projects preparing a “bankable” compliance baseline.
- Tokenization/RWA teams needing disclosures and contracts.
- Businesses aligning counterparties and jurisdictional narrative.
We focus on mapping controls to real flows — that’s what banks and partners care about.