Switzerland has built one of the most permissive – and most technically sophisticated – legal environments for tokenizing real-world assets. Under the DLT Act (the package of amendments to the Code of Obligations, the Banking Act, and related statutes that Switzerland adopted to accommodate distributed-ledger technology), Swiss law formally recognizes ledger-based securities as a distinct instrument: rights registered on a blockchain carry the same legal force as rights entered in a traditional register. That foundation changes the risk calculus for any business structuring a real-world asset tokenization project, whether the underlying is real estate, private credit, infrastructure debt, or a commodity.
The classification question is the starting point. FINMA, Switzerland's financial regulator, applies a three-category token taxonomy – payment, utility, and asset tokens – and classifies instruments on the substance of the rights they convey, not the label attached to a whitepaper. A token granting its holder a participation right, an income stream, or a claim against the issuer reads as an asset token and, depending on its structure, may constitute a security under Swiss law. The regulatory consequences follow that classification, not the marketing narrative.
This guide walks through the legal steps – classification, structure, registration, distribution, and ongoing compliance – that a business must complete to operate a lawful real-world asset tokenization program in Switzerland. The cross-border interaction with EU distribution, US investor restrictions, and Swiss banking access is addressed at each stage.
What is a ledger-based security under Swiss law?
A ledger-based security (Registerwertrecht) is a claim or membership right that is registered on a distributed ledger in a way that makes the ledger entry the definitive record of ownership. Swiss law introduced this concept through the DLT Act, which came into force in stages from 2021 onward. The key structural requirement is that the registration agreement must specify the ledger, the rights, and the rules governing transfer – and those rules must be technically enforced so that only the registered holder can dispose of the right.
In practice, this means the token smart contract must function as the register. The contract logic – not a side agreement or a custodial database – must be the operative record. That technical discipline is a legal requirement, not a best practice. Operators who deploy a token on a public chain but maintain a parallel off-chain ledger as the "real" register undermine the legal characterization and may find themselves outside the Registerwertrecht regime entirely.
The legal clarity here is real. Before the DLT Act, Swiss practitioners had to argue by analogy that a blockchain entry could have the legal effect of a securities register entry. The Act ends that argument. It also means that a correctly structured ledger-based security can be transferred by blockchain transaction without a written deed – a significant operational advantage for secondary market activity.
How does FINMA classify a real-world asset token?
FINMA classifies tokens by the economic substance of the rights attached to them, applying its published guidance on the token taxonomy. An asset token representing a claim on a real-world asset – such as a fractional interest in real estate or a coupon-bearing note – will typically be treated as a security, triggering the licensing and prospectus requirements that apply to securities issuers and intermediaries under Swiss law.
The classification analysis turns on four questions. First: does the token represent a monetary claim, a participation right, or a right to receive future cash flows from the issuer or from an underlying asset? Second: is the token marketed or sold as an investment? Third: is the value of the token dependent on the performance of an enterprise or asset that the holder does not control? Fourth: is the token fungible and transferable?
If the answers point toward an asset token, the issuer must address two distinct regulatory tracks. One is the securities track – the obligations around prospectus publication or exemption, secondary market rules, and the licensing of any intermediaries who deal or advise. The other is the AML track – Swiss anti-money-laundering rules require any party who professionally transfers assets on behalf of third parties to affiliate with a recognized self-regulatory organization or obtain a FINMA license. A DeFi protocol that facilitates secondary transfers of asset tokens is not automatically exempt from either track.
FINMA has confirmed, in its published guidance on DeFi, that decentralization is not a regulatory shield. Where a party controls a protocol, profits from its operation, or can influence its parameters, that party is in scope. In our cross-border practice, we see this classification issue arise most acutely when a Swiss-domiciled foundation or association acts as a putative "decentralized" operator while retaining substantive control over fee settings, upgrade keys, or treasury allocation.
The process above describes the standard classification path. Your facts – the asset type, the token structure, the investor base, the secondary market arrangement – change the analysis materially.
For a scoped classification assessment, contact OBOLUS at info@oboluslaw.com. We work through the FINMA taxonomy against your specific instrument, not a generic checklist.
What legal structure suits a Swiss real-world asset tokenization?
The right legal structure depends on the asset class, the investor profile, and the intended secondary market. Three configurations appear most frequently in Swiss practice, and each carries distinct regulatory and operational implications.
The first is a Special Purpose Vehicle (SPV) model. A Swiss AG or GmbH holds the underlying asset. The SPV issues ledger-based securities representing participation rights or debt claims against the SPV. Investors hold tokens; the SPV holds the asset. This is conceptually clean and maps well onto the Registerwertrecht regime. The SPV itself must comply with Swiss corporate formalities, and if it accepts deposits or performs banking-like functions, it risks triggering FINMA's banking authorisation requirements.
The second is a collective investment scheme model. Where the token structure pools investor capital and the manager exercises discretion over the underlying assets, Swiss law may characterize the arrangement as a collective investment scheme. That triggers the collective investment scheme regime, which imposes regulatory obligations on the fund manager and, for distribution to non-qualified investors, on the fund itself.
The third is a debt instrument model. The issuer issues tokenized notes – structured as bonds or structured products – under the Registerwertrecht regime. This avoids the equity-like collective investment classification but requires careful drafting of the bond terms and, if offered to the public in Switzerland above the applicable prospectus threshold, a FINMA-compliant prospectus or a recognized exemption.
Each model interacts differently with Swiss stamp duty, withholding tax on distributions, and the securities transfer tax that applies to securities dealers. These tax dimensions are not optional considerations to address after structure selection – they constrain which structure is economically viable for a given asset class and investor base.
What is the registration and issuance process for ledger-based securities?
Registration of a ledger-based security begins with the registration agreement – a document executed between the issuer and the initial holders (or, in a public offering, incorporated by reference into the subscription terms) that specifies the DLT system on which the rights are registered, the rights attached, and the technical rules governing transfer and disposal.
The smart contract is the operative register. That means the contract must be audited for both legal compliance and technical correctness before issuance. In our practice, we see projects that treat the audit as a post-launch activity. That approach is legally indefensible: a contract that contains a bug allowing unauthorized transfers is not functioning as a Registerwertrecht register, regardless of what the documentation says.
FINMA requires financial intermediaries involved in the issuance or distribution of asset tokens to hold the appropriate authorisation or to operate through an authorised party. For a typical tokenized real estate transaction, that means the placement agent or the platform facilitating investor onboarding must hold, or operate within the scope of, a securities dealer licence or equivalent authorization. Identifying and engaging a compliant distribution partner is a structural decision, not an afterthought.
The timeline from structure finalization to first issuance varies. For a private placement to qualified investors – which avoids the public prospectus obligation – a well-prepared Swiss SPV structure can reach issuance in a matter of weeks once the underlying asset is held and the contract is audited. A public offering subject to prospectus review extends the timeline materially. We describe timelines qualitatively because the variables – FINMA pre-consultation, legal opinions, tax rulings, and third-party audit scheduling – interact in ways that make precise forecasting unreliable without knowing the specific facts.
How does cross-border distribution affect a Swiss real-world asset tokenization?
Switzerland sits outside the EU, which means a Swiss-issued ledger-based security does not benefit from MiCA passporting or from EU prospectus passporting. Distribution into EU member states requires a separate analysis under MiCA for crypto-asset classifications and under the EU Prospectus Regulation for securities classifications – and the two regimes do not map neatly onto the Swiss token taxonomy.
In practice, Swiss issuers distributing to EU investors have three options. They can restrict the offering to non-EU investors and use private placement exemptions for any EU-resident qualified investors who approach the issuer. They can establish a parallel EU issuance vehicle – typically in a MiCA-ready jurisdiction – that mirrors the Swiss structure. Or they can seek a jurisdiction-by-jurisdiction exemption analysis for the target EU member states, which is fact-intensive and adds both time and cost.
US investor restrictions add a further layer. Any offering of tokens that constitute securities under US law to US persons requires either Securities Act registration or a valid exemption – most commonly Regulation S (offshore transaction safe harbor) or Regulation D (accredited investors only, with corresponding transfer restrictions). Swiss issuers routinely apply Regulation S restrictions to their token transfers, but the smart contract must enforce those restrictions technically – a manual compliance check at the point of transfer is not adequate.
Banking access for a Swiss tokenization vehicle depends heavily on the asset class and the investor profile. Swiss cantonal banks and private banks vary significantly in their appetite for digital-asset-related corporate accounts. Operators in our practice routinely find that a structurally sound and legally compliant Swiss SPV still faces a multi-month banking onboarding process. Planning for that timeline – including backup banking options in jurisdictions where allied counsel can assist – is a standard part of our structuring advice.
What are the AML and Travel Rule obligations for a tokenized RWA platform?
Swiss AML law applies to any party that professionally transfers assets on behalf of third parties or acts as a financial intermediary. A platform facilitating secondary transfers of ledger-based securities is, in most structures, acting as a financial intermediary and must affiliate with a recognized self-regulatory organization or hold a FINMA licence under the applicable provisions of the Anti-Money Laundering Act.
The Travel Rule – the obligation, grounded in FATF Recommendation 15, to pass originator and beneficiary information with a virtual asset transfer above the applicable threshold – applies to Swiss VASPs. A secondary market for tokenized real-world assets, if it processes transfers above the threshold, must transmit the required data. The technical implementation of this requirement on a blockchain-native platform is a non-trivial engineering problem: the data must travel with the transaction, and the receiving VASP must be able to verify it.
KYC at the point of token issuance is necessary but not sufficient. The platform must also conduct ongoing transaction monitoring, maintain records for the period required under Swiss law, and file suspicious activity reports where warranted. For a fractional real estate token that changes hands in secondary trading, each transfer is a potential AML event. Operators who treat AML as a one-time onboarding exercise and not as a continuous monitoring function expose themselves to regulatory sanction and, in the event of a supervisory investigation, to the reputational consequences of a public enforcement action.
In practice: a cross-border tokenized real estate structure
In a recent matter, a real estate technology company approached us to structure the tokenization of a portfolio of commercial properties held through a Swiss holding entity. The company had already engaged a blockchain developer and drafted a whitepaper describing the tokens as "utility tokens" granting holders access to a property management platform. We identified that the economic substance – a right to receive distributions from net rental income – placed the tokens squarely within FINMA's asset token category, and that the planned distribution to retail investors in two EU member states would require prospectus compliance in those jurisdictions.
We restructured the offering as a private placement of ledger-based debt securities to qualified investors, eliminated the retail distribution, and engaged allied counsel in the relevant EU jurisdictions to confirm the private placement exemption conditions. The smart contract was revised to enforce transfer restrictions technically, not through documentation alone. The matter reached first close in a subsequent quarter. The legal classification issue – identified early – prevented a launch that would have constituted an unregistered securities offering in multiple jurisdictions simultaneously.
What is the decision point for choosing Switzerland as the tokenization jurisdiction?
Switzerland is the right jurisdiction for a real-world asset tokenization project when the legal recognition of ledger-based securities at the statutory level is a priority, when the issuer has – or can efficiently build – a compliant Swiss corporate and banking infrastructure, and when the target investor base is predominantly non-US and either Swiss or accessible through private placement exemptions.
Switzerland is a less efficient choice when the primary investor base is EU retail investors (because there is no MiCA passport), when the business model depends on a DeFi-native secondary market that would require FINMA authorization, or when the timeline pressure is acute and the banking access problem has not been solved.
Profile A: An asset manager with existing Swiss relationships, a qualified-investor target market, and a real estate or private credit asset base – the Swiss SPV with ledger-based debt securities is the natural fit. The timeline to issuance, assuming a pre-cleared banking relationship and a completed smart contract audit, is measured in weeks for the legal work and somewhat longer for the overall process.
Profile B: An early-stage DeFi protocol seeking to tokenize commodities for a global retail market – Switzerland adds structural credibility but does not solve the EU distribution problem, and the FINMA DeFi guidance creates real compliance risk if the protocol operator retains substantive control. A parallel MiCA-jurisdiction structure deserves serious consideration.
Profile C: A corporate treasury tokenizing its own receivables for internal capital efficiency, not for external investor distribution – the Swiss Registerwertrecht offers a legally clean mechanism without triggering securities dealer licensing, provided the instrument is not marketed to third parties.
A common assumption is that labeling a token "utility" in the whitepaper resolves the classification question. It does not. FINMA's classification analysis is substance-driven: the rights conferred by the token, not the name given to it, determine the regulatory category. We assess classification against the economic reality of the instrument – and we do so before a whitepaper is published, not after a regulator asks the question.
If your tokenization structure is at the decision stage – or if a prior attempt hit a regulatory or banking obstacle – contact OBOLUS at info@oboluslaw.com or message us at t.me/oboluslaw to discuss where the analysis stands.
Related at OBOLUS
- DeFi, Tokenization & Smart-Contract Law – our full practice covering token classification, smart-contract structuring, and protocol legal risk across jurisdictions
- Cross-chain bridge legal risk in Gibraltar – how Gibraltar's DLT regime addresses legal exposure at the bridge protocol layer
- Digital asset licensing in Gibraltar – the DLT Provider licence framework and what inbound operators need to understand before applying
FAQ
Can a DeFi protocol be regulated?
Yes. FINMA has confirmed that decentralization does not automatically place a protocol outside Swiss regulatory reach. Where a party controls a DeFi protocol, profits from its operation, or retains the ability to alter its parameters, that party is treated as performing a regulated function. The legal analysis looks at who holds technical keys, who receives fees, and who governs upgrade decisions – not at whether the codebase is open source or the governance is nominally community-led.
What legal wrapper suits a DAO?
Swiss law offers the association (Verein) and the foundation (Stiftung) as the wrappers most commonly used by DAO-like structures. The association suits a member-governed protocol community. The foundation suits a structure where assets are earmarked for a defined purpose and no member has a direct financial interest. Neither eliminates regulatory risk automatically: if the entity performs regulated financial services, the legal form does not shield it from FINMA supervision.
Who is liable when a smart contract fails?
Liability for a smart contract failure depends on the facts: who deployed the contract, whether the code was audited, whether known vulnerabilities were disclosed, and whether the failure constituted a breach of the terms governing the underlying instrument. Under Swiss law, the issuer of a ledger-based security bears obligations toward holders. A bug that destroys value or prevents transfer may give rise to contractual or tort claims against the deploying entity, regardless of whether the contract was advertised as autonomous or immutable.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers, and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking, and compliance obligations that sit around them. Digital assets are the whole of our practice. We assess token classification against the substance of rights, not the marketing label – and our disputes team coordinates freezing relief and on-chain tracing across leading common-law forums where misappropriation is in issue. To discuss your tokenization structure, contact info@oboluslaw.com.
By Roman Levitt, Technology & DeFi Counsel – specialising in smart-contract legal architecture, token classification, and protocol-level regulatory risk for Swiss and cross-border digital-asset issuances.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.