FinTech licence Switzerland: market-entry checklist

Short answer: A financial platform cannot determine its Swiss authorisation from its brand name or app features alone. The analysis starts with the actual activity: whether the business accepts or controls client assets, deals in securities, manages assets, operates a financial market infrastructure, provides payment services or intermediates insurance. The legal entity, client journey, custody model, target market and location of the activity then determine which supervisory questions must be answered.

Launching a broker, digital bank, investment app or trading platform in Switzerland is not only a technology project. It is a business-model and governance project. The same user interface can sit on top of very different legal arrangements: a regulated Swiss institution, a foreign institution serving clients cross-border, a technology provider with no client-asset role, or a marketing partner that must still control what it says to prospects.

This guide is designed for founders, compliance teams, product leaders and commercial partners who need a structured first pass. It is not a legal opinion and it does not replace a FINMA enquiry or advice from Swiss counsel. Its value is practical: it helps a team describe the model precisely before choosing a licence path or publishing acquisition content.

Start with the activity, not the label

The words bank, broker, fintech, trading platform and prop firm are commercial descriptions. They do not answer the regulatory question by themselves. A useful first document is an activity map with one row for every service offered to a customer.

This map prevents a common mistake: treating the technology layer as the business model. A white-label platform, cloud provider or API vendor may not have the same role as the entity that contracts with the customer or controls assets. Conversely, outsourcing technology does not automatically outsource responsibility for the customer experience, records or communications.

The Swiss authorisation questions

FINMA explains that banks and securities firms, including relevant branches and representative offices of foreign institutions, need a licence for the activities covered by the Swiss framework. Its authorisation material also describes the broader principle: entities that accept money from investors, issue insurance policies or establish and manage collective investment schemes require authorisation before operating. FINMA’s overview of banks and securities firms and FINMA’s authorisation types are the right starting points for a project file.

The practical question is not “Which licence sounds closest to our company?” It is “Which regulated activity is our company actually performing, for which customer, from which location and with whose assets?”

Banking and FinTech routes are not interchangeable

A platform that accepts deposits or holds client assets may need to analyse a banking route or another form of permission. A FinTech route may be relevant to a narrower model, but it does not turn every financial application into a bank. The team must document what happens to customer money, whether it is invested or used, who bears the insolvency risk and what the customer is told.

FINMA’s FinTech guidance explains that innovative financial companies should assess authorisation, supervision and anti-money-laundering requirements before starting commercial activity. It also distinguishes activities such as accepting client assets, securities activity and insurance intermediation. Read the FINMA FinTech guidance.

Securities-firm analysis

An online broker should describe every step between the customer’s order and the market. Does the platform only transmit an instruction? Does a group entity execute the order? Is the platform itself a counterparty? Does it hold a position before selling? Does it arrange access to a Swiss trading venue or to another market?

The answers affect the legal-entity map, the client agreement, the conflicts-of-interest analysis and the custody explanation. A marketing page that says “Swiss trading” is not enough evidence. A serious platform should be able to identify the contracting entity, the execution route, the custody arrangement and the complaint channel in plain language.

Insurance intermediation

An investment comparison site or financial platform may also touch insurance regulation if it recommends, arranges or concludes insurance contracts. This is relevant to insurtechs, wealth platforms, pension tools and lead-generation partners.

FINMA’s guidance on insurance distribution explains that the revised framework places obligations on insurers and intermediaries, with different supervision and control expectations depending on whether the intermediary is tied or untied. See FINMA’s guidance on insurers and insurance distribution.

The commercial implication is important: an insurer should assess a distribution partner before sending it traffic or customer data. A platform should be able to explain who provides the advice, who concludes the contract, what information is displayed and how complaints are handled.

A six-layer market-entry due-diligence model

The following model is useful before a founder commissions a large website, buys traffic or signs a white-label agreement.

Layer one: legal entity and governance

Record the proposed contracting entity, its registered office, directors, beneficial owners, group relationships and intended Swiss presence. If a foreign group will serve Swiss customers, describe where staff work, where decisions are made and which entity signs the customer agreement.

The objective is not to create a complicated group chart. It is to remove ambiguity. The public website, onboarding flow, contract, regulatory register entry and customer support channel should not point to contradictory entities.

Layer two: customer and geography

Define the target customer precisely. Retail investors, professional investors, corporate treasuries, insurance policyholders and evaluated traders do not create the same conduct questions. Then define where the customer is resident, where the service is delivered and which languages are used.

Cross-border business should not be described with a generic “available worldwide” claim. A platform needs a country matrix, an eligibility rule, an onboarding blocklist, a review process for exceptional cases and a method for updating the public information when the model changes.

Layer three: money and asset flow

Draw the flow from the customer’s bank account to the final account or custody location. Add every intermediary: payment institution, bank, broker, custodian, clearing member and technology provider. Mark who can instruct a transfer and who reconciles the records.

This is where many attractive product pages become unreliable. A platform may call an account “protected” without explaining whether the statement represents a bank deposit, a custody asset, a claim against a counterparty or simulated trading performance. The language must match the legal and operational reality.

Layer four: product and execution

List every instrument and feature separately. Stocks, funds, options, CFDs, fractional interests, copy trading, lending, staking and simulated accounts should not be placed in one generic “investing” category. Each feature requires its own description, risk explanation, eligibility rule and operational owner.

For trading firms and prop programmes, document whether the customer is trading with the firm’s own capital, paying for an evaluation, receiving a simulated account or depositing funds with a separate broker. Do not allow a performance dashboard to imply that a retail customer has the same protection as an investor holding assets through a regulated custody chain.

Layer five: compliance operations

Describe KYC, AML, sanctions screening, transaction monitoring, suspicious-activity escalation, record retention, complaints and staff training. A platform should also identify who owns each control and what evidence proves that the control operated.

FINMA’s digital-identification material is particularly relevant to platforms that want a fully digital onboarding journey. FINMA’s online identification material shows why convenience does not remove due-diligence requirements.

Layer six: technology and resilience

Inventory the critical systems: identity, payments, order management, market data, customer support, records, reporting and business continuity. Identify third parties and the failure scenario for each one.

For firms in the European regulatory perimeter, DORA provides a useful reference point for ICT risk, incident response, testing and third-party arrangements. The European Banking Authority’s DORA overview explains the framework for digital operational resilience in financial entities. A Swiss project should not automatically claim that DORA applies to it; it should document which entity and service are in scope and which obligations are used as a resilience benchmark.

What a credible public website should show

A regulated or regulation-sensitive platform does not need to publish its internal manual. It does need to make the customer’s decision easier.

At minimum, a serious public website should make it possible to find:

• the legal entity serving the visitor;
• the relevant regulator or registration information where applicable;
• the products and customer types accepted;
• the custody and cash model in understandable language;
• the main risks and exclusions;
• the complaint and support route;
• the countries that are not served;
• the date on which key information was reviewed.

The content must be consistent. A disclaimer at the bottom of one page cannot cure a headline that promises something else. A platform should review advertisements, comparison pages, affiliate copy, email sequences and social posts together.

Common market-entry mistakes

Treating a licence as a marketing badge

A licence is not a universal trust label. It has a scope, an entity, a jurisdiction and conditions. The public page should explain what the authorisation covers and what it does not cover.

Hiding the contracting entity

Customers cannot assess custody or complaints if the brand is prominent but the legal entity is hidden. Make the entity visible at the point where the customer is deciding whether to open an account.

Copying a foreign website

A group website written for another country may include products, claims or eligibility rules that do not apply in Switzerland. Localise the entity map, the customer journey, the language and the source links.

Publishing before the model is stable

Marketing copy often gets written before the product and compliance teams have agreed on the money flow. That creates contradictions that are expensive to repair. Freeze the activity map first, then write the public explanation.

Confusing lead generation with advice

A comparison page can educate a reader without recommending a product. If a partner pays for a placement, the relationship and the purpose of the page must be handled transparently. Editorial analysis, sponsorship and regulated advice are different activities.

A practical readiness checklist

Before launching a Swiss-facing platform, answer these questions in writing:

1. Which entity contracts with the customer?
2. Which entity receives or controls client assets?
3. Which activities are performed from Switzerland?
4. Which regulator or register is relevant to each activity?
5. Which customers and countries are eligible?
6. What exactly happens to cash, securities and trading orders?
7. How does digital identification work?
8. Who owns AML and sanctions controls?
9. What happens if a critical technology provider fails?
10. Which public claim could a customer misunderstand?
11. Where can a customer complain?
12. Which date and source support each important regulatory statement?

If the team cannot answer these questions, it is not ready to scale acquisition. More traffic will only magnify the ambiguity.

The partner-review file

Banks, brokers and insurers rarely assess a platform from one homepage. They need a review file that can be shared between commercial, compliance, legal, technology and risk teams. Preparing that file early makes partnership discussions faster and reveals missing assumptions before they become contract issues.

The file should contain:

• a one-page description of the business model;
• the group and legal-entity chart;
• a customer and country matrix;
• a client-money and custody diagram;
• a product inventory with eligibility rules;
• the KYC, AML and complaints responsibility matrix;
• the public-claims register;
• the technology and outsourcing inventory;
• the incident and continuity contacts;
• the list of open legal or regulatory questions.

Each document should carry an owner and review date. A folder full of undated files gives a false impression of control. The important test is whether a new product, country or partner can be added without silently breaking the original analysis.

How to prepare a regulatory enquiry

When a project needs clarification, the quality of the question matters. A short message saying “Do we need a licence?” leaves too much interpretation to the recipient. A better enquiry describes the entity, customer, geography, activity, money flow and planned public communication.

A useful structure is:

1. We are a company incorporated in a defined jurisdiction.
2. We intend to serve a defined customer group in defined countries.
3. The customer signs with this entity.
4. The customer pays or transfers assets through this flow.
5. The platform performs these actions and does not perform these other actions.
6. A group company or vendor performs these technical functions.
7. We plan to describe the service publicly using these words.
8. We would like clarification on the relevant authorisation and control questions.

This format does not guarantee an answer or replace counsel. It does make the project easier to understand and creates a reliable record of the assumptions used in product planning.

When a platform should refresh its analysis

The initial authorisation memo is not a one-time deliverable. Refresh it when the platform:

• adds a new financial instrument;
• changes the entity serving a country;
• begins accepting or moving a new kind of asset;
• adds leverage, lending or copy trading;
• introduces a new insurance product;
• changes the onboarding vendor;
• adds a new affiliate or distribution partner;
• opens a new country or customer category;
• changes its public protection or regulation claims;
• acquires or merges with another business.

The refresh can be proportionate. A wording change does not require the same review as a new custody route. But every material change should have a trigger, an owner and a decision record.

A useful decision tree for founders

Ask the following questions in order:

Does the platform accept or control client assets? If yes, identify the exact asset, account, entity and control rights before choosing the technology or marketing path.

Does it deal in or arrange securities for customers? If yes, map order reception, transmission, execution, counterparty and custody responsibilities.

Does it manage assets or make decisions under a mandate? If yes, separate education, execution-only functionality and discretionary management in the product design.

Does it arrange insurance? If yes, identify the intermediary status, insurer relationship, customer information and complaint route.

Does it only provide software? If yes, document the boundary carefully. A software provider can still create operational, data, advertising and outsourcing risks for its financial-institution customer.

The decision tree is deliberately simple. Its job is to identify the questions that need specialist treatment, not to produce an artificial licence conclusion.

The same inventory should identify who receives notifications when a dependency changes. A platform that knows its technology stack but cannot identify its business owner will struggle to answer a partner’s most basic resilience question: who decides what happens to customers when the service is unavailable?

Keep the editorial and commercial layers separate

An educational article can explain the questions a platform should ask without recommending a particular institution or implying that publication itself is regulatory approval. Keep research, partner content, sponsored material and regulated advice clearly separated. This helps the reader and gives future banking, brokerage and insurance partners a safer environment in which to discuss their services.

Frequently asked questions

Is every investment app a Swiss FinTech company?

No. “FinTech” describes a technology-led business model, not one universal authorisation. The relevant analysis depends on the activity, the customer, the flow of assets and the entity providing the service.

Can a foreign broker serve Swiss customers?

That depends on the service, the entity, the way the business is conducted and the applicable Swiss and foreign rules. The platform should not rely on a generic cross-border statement; it should obtain a country-specific assessment.

Does using a white-label broker platform remove regulatory responsibility?

Not automatically. Outsourcing technology may change who operates a system, but it does not by itself change who contracts with the customer, controls the relationship or makes public claims. The parties need a documented responsibility matrix.

Does a prop firm have the same obligations as a broker?

Not necessarily. A prop firm’s obligations depend on its actual model. A firm that evaluates traders with its own capital is not described in the same way as a platform accepting retail deposits or offering CFDs through a broker. The customer journey and money flow must be analysed before making a legal conclusion.

What should a bank ask a financial platform before partnering with it?

The bank should request the legal-entity map, authorisation analysis, customer eligibility rules, money-flow diagram, KYC and AML responsibilities, complaints process, technology controls and public-communications review. It should also verify that the platform’s marketing does not overstate protection or returns.

Conclusion

Market entry starts with a precise description of the business model. A credible Swiss-facing financial platform can explain its legal entity, customer scope, custody and cash flows, products, controls and technology partners without hiding behind a brand name. That clarity benefits the platform, its banking partners, its insurers and the customers who rely on its public information.

For a related investor perspective, read the FINMA broker safety checklist, the Swiss custody protection guide and the Swiss broker guide.