Most fintech founders ask the licensing question in the wrong order: build the product, find customers, then — usually prompted by a bank, an investor or a worried board member — ask whether any of it needed a FINMA license. Swiss financial market law is activity-based: labels like "platform", "app" or "marketplace" do not matter; what you actually do with other people's money and assets does. A handful of questions decides most cases. They are design questions as much as legal ones, which is why they belong at the whiteboard stage, not on the launch checklist.
Do you take money from the public — or sit on client balances?
Accepting deposits from the public is the heart of banking regulation, and it catches more business models than founders expect. Client balances that accumulate in your wallet, prepaid accounts, funds held longer than settlement requires — all of this can qualify as deposit-taking. Swiss law provides graduated regimes at the framework level: a sandbox-style exemption for activity below certain limits, a fintech license for accepting public funds without lending them out, and the full banking license beyond that. Where those limits run in numbers is exactly the kind of question to put to a lawyer, not a blog. The design question is what matters most: does your model require you to hold client money at all, or can the flows run through a licensed partner?
Do you move money for others?
Payment services — transferring funds between parties, operating accounts, issuing means of payment — make you a financial intermediary under the anti-money-laundering framework. That does not necessarily mean a FINMA license, but it does mean affiliation with a self-regulatory organisation, due-diligence duties towards your customers, and monitoring and reporting obligations that reach deep into product design and onboarding. AML status is the question founders most often miss, because it applies even where no other license is required. Onboarding flows, transaction monitoring and the ability to identify your customers reliably are compliance features that are cheap to design in and expensive to bolt on.
Do you touch securities — including tokens that qualify?
Issuing financial instruments, dealing in them, or operating a venue where they trade points towards securities regulation and the securities-firm license. For crypto models the pivotal question is classification: FINMA's established distinction between payment, utility and asset tokens determines much of what follows — and a token designed as "utility" can still qualify as a security by its economic function. Trading venues and anything resembling an exchange sit at the strictest end of the spectrum.
Do you manage — or advise on — other people's assets?
Discretionary management of client portfolios is a licensed activity for independent managers, with ongoing supervision. Advisory models trigger conduct and documentation duties under the financial-services framework even where no license attaches. The line between execution only, advice and management is drawn by what your product actually does — including what its automated features do — not by what the terms of service call it. Robo-advisory models deserve particular care: the same algorithm can sit on either side of the line depending on who takes the final decision.
The cost of asking late
Asking these questions after launch is expensive in ways founders underestimate. Operating without a required license risks enforcement, and FINMA's toolkit reaches as far as the liquidation of an unauthorised business. Well before that, the practical costs bite: banks decline accounts, investors' counsel find the gap in due diligence at the worst possible moment, and retrofitting compliance into a live product is far harder than designing around the perimeter. Often a small architectural choice — never holding client funds yourself, partnering with a licensed institution — changes the answer entirely. A licensing analysis also produces something founders undervalue: a reasoned answer to show banks, investors and partners that the regulatory question has been asked and dealt with.
The decision path above locates the question; it does not answer it. Where your model actually sits depends on its precise mechanics, and edge cases are the norm in fintech. We walk founders through this analysis at the design stage, when the answer can still shape the product. If you are building something that touches client money or assets, ask early — it is the cheapest legal question you will ever pose.