Advantages
- fast entry into the EU market
- ability to use ready-made infrastructure and spread costs between setup and ongoing services
- regulated services and the corresponding CASP obligations sit with the authorised operator
White Label Crypto Exchange - a ready-made crypto platform under your brand with access to the services of a European CASP authorised under MiCA. Regulated United Europe (RUE) selects the provider, assists with contracts and coordinates the launch. Users gain access to agreed crypto-asset exchange, custody and transfer services.
Regulated United Europe · Content updated 11 November 2026
Obtaining your own CASP authorisation requires document preparation, governance arrangements, compliance and technical infrastructure. White Label allows you to use an existing operator's infrastructure, provided your company performs only functions it is permitted to carry out. An agreement with a CASP does not, in itself, exempt you from MiCA requirements.
This format is suitable for testing demand or adding crypto transactions to an existing product. Instead of building the entire infrastructure yourself, you agree on functions, fees and working arrangements with the operator. The launch timeline depends on company checks and the scope of integration.
The Regulated United Europe Team
Platform selection and legal support for your launch
Describe your project: we will match the required functions with European operators' offerings and agree on the next steps.
We work with several licensed operators in different European countries. Rather than adapting a project to a single supplier, we look for the one that fits your needs: countries, client types, required assets, expected turnover and budget.
Post-launch support can be agreed for expanding geographic coverage, adding functions, amending contracts or preparing for your own authorisation. The scope and cost of this work are determined separately.
Countries, services and client categories are checked against the operator's terms and permissions.
Name, domain, logo, colours and interface languages. Users see your product.
Choose a standard interface or connect to your product through an API.
The CASP is responsible for its regulated services. The customer's functions are set out in the agreement.
A White Label crypto exchange is a commercial term for a ready-made crypto service under the customer's brand. In the model described here, regulated operations are performed by the partner CASP. A similar solution is known as CASP as a Service: exchange, custody and other permitted provider services are connected to the customer interface.
How this differs from two other approaches:
The basic version is an exchange service: the user buys or exchanges an asset at the provider's quoted price. An exchange with its own order book, where customers trade with one another, is treated under MiCA as a separate service (operating a trading platform) and is not included in the standard package.
A ready-made application may include registration, verification, a customer account area, wallets, exchange, transaction history and administrative tools. Branding and standard settings are specified in the technical requirements. For API integration, we separately define what the operator provides and what your team develops. Mobile applications and changes beyond the agreed scope are priced separately.
A CASP provides only the services for which it is authorised. These most commonly include exchanging crypto-assets for fiat and other crypto-assets, custody and administration of client assets, and transfers. Each provider has its own range of services and countries, which we cross-check against the ESMA register and information from the national regulator.
Individual Project Pricing
Indicative provider setup fee
from EUR 15,000
Potential Package Scope
For preliminary budgeting, the table below provides an example of Equilex's published CASP as a Service fees. It illustrates the cost structure of one offer and is neither a market-average price nor a universal RUE tariff.
|
Item |
Cost |
Notes |
|---|---|---|
|
User verification (KYC) |
from EUR 1 per user |
Document verification and liveness check. Corporate KYB is separate |
|
Ongoing monitoring |
from EUR 0.50 per user per year |
Within the provider's compliance programme |
|
Crypto transfer monitoring |
from EUR 0.30 per transfer |
Excludes network and withdrawal fees |
|
Exchange |
0.20-0.50% of turnover |
The rate decreases as monthly turnover increases |
|
Incoming SEPA |
free |
|
|
Outgoing SEPA |
from EUR 1 per transfer |
Rates of 0.25-0.55% for business volumes are published separately; applicability must be confirmed |
|
Crypto-asset withdrawals |
fixed fee + network fee |
Depends on the asset |
|
Interface, customisation and applications |
individually priced |
Confirmed when preparing the estimate |
Example. If customers exchange EUR 1 million per month, the exchange fee will be EUR 2,000-5,000 per month. Including setup, the first-year total is EUR 39,000-75,000 for these two items alone, excluding other expenses and RUE's services.
Available separately if offered by the selected provider:
|
Service |
Cost |
|---|---|
|
Branded iOS and Android mobile applications |
on request |
|
Custom development and integrations |
on request |
|
Payment cards funded from a crypto balance |
on request |
|
Virtual IBANs for users |
on request |
|
Corporate client services (KYB, higher limits) |
on request |
|
Accepting stablecoin payments |
on request |
|
User migration from another platform |
on request |
Staking, lending, yield products, derivatives and a multilateral trading platform are not automatically included. Each area requires a separate assessment of the legal framework and confirmation of the provider's capabilities. Payment services also require an appropriate legal basis: MiCA authorisation does not, in itself, replace it.
Tell us which countries you want to operate in and your expected turnover. We will suggest suitable providers and calculate the budget.
|
Step |
What the user does |
What happens in the system |
Responsible party |
|---|---|---|---|
|
Registration |
Creates an account on your website or in the application |
Accepts terms identifying the licensed operator |
You (interface), CASP (agreement) |
|
Verification |
Uploads a document and completes a liveness check |
KYC, sanctions screening and risk assessment |
CASP |
|
Funding |
Sends euros via SEPA or crypto-assets to a deposit address |
Crediting, monitoring and Travel Rule |
CASP and payment provider |
|
Exchange |
Buys, sells or exchanges an asset at the current quote |
Trade execution and fee deduction |
CASP |
|
Withdrawal |
Withdraws euros to an account or assets to an external wallet |
Recipient checks and transfer |
CASP and payment provider |
|
Support |
Submits a question or complaint |
First-line support, followed by the complaints procedure under MiCA |
As agreed: you and/or the CASP |
Businesses with existing customers or an acquisition channel that need to add crypto-asset services quickly:
Approval is not automatic. The provider checks the company, owners and management, source of funds, business model, target countries and marketing. Projects with opaque structures or high risk may be rejected.
Regulated services are provided by the CASP, which is responsible for them to the regulator and customers. The customer develops the brand and performs agreed functions: marketing, customer acquisition and first-line support. RUE supports the project under its own agreement and does not itself provide crypto-asset services.
Article 59 of MiCA defines who is entitled to provide crypto-asset services in the EU. Article 73 governs the outsourcing of operational functions: the CASP retains responsibility for its regulatory obligations. These provisions do not create a licence rental regime or allow an unauthorised partner to provide crypto-asset services independently.
|
Participant |
Role |
Responsible for |
|---|---|---|
|
Partner CASP |
Provider of regulated services |
Exchange, custody, transfers, KYC/AML, Travel Rule, complaints and reporting |
|
Customer |
Owner of the brand and audience |
Marketing under agreed rules, customer acquisition and first-line support |
|
RUE |
Consultant and coordinator |
Provider selection, permission checks, contracts and launch |
|
User |
CASP's client |
Accurate information and compliance with the terms |
The need for authorisation is determined by the company's actual functions, not only by whose name it acts in. Owning a brand and developing an interface do not, in themselves, amount to providing crypto-asset services. However, receiving and transmitting orders, providing advice or executing transactions may require the company's own regulated status.
MiCA does not provide a general agent regime allowing firms to deliver crypto-asset services under another CASP's authorisation. RUE therefore analyses the customer journey, contracts and your team's activities before setup. The agreement must define permitted functions and the procedure for referring matters to the operator.
The agreement for regulated crypto-asset services is concluded with the relevant CASP. Terms for using the interface and payment services may be documented separately. For custody, the provider ensures that client assets are segregated from its own and maintains records of each client's rights. This does not necessarily mean a separate blockchain wallet for every user. Access rights and key management are determined by the custody architecture and agreements.
The operator must be clearly identified in the interface, terms of service and advertising: name, country of authorisation, registration number and regulator. Users must understand who they are dealing with and who holds their money.
To provide cross-border services in the EU, a CASP follows the notification procedure under Article 65 of MiCA. We verify the specific countries, services and client categories available through the selected operator. For EEA countries outside the EU, the applicable framework and ability to provide services are confirmed separately. The UK and Switzerland are not included in this offer.
The provider checks your business in much the same way as a bank checks a corporate client. Prepare the following in advance:
Articles of association, a registry extract and the ownership structure down to the ultimate beneficial owners.
Passports, proof of address and information on reputation and experience.
Where the launch funds come from and how the project is financed.
Target countries and customers, projected user numbers and turnover, and acquisition channels.
Where and how you will advertise the service. Copy is agreed with the provider.
Who responds to users, in which languages and during which hours.
Individual identification (KYC), corporate checks (KYB), sanctions screening and monitoring are organised within the CASP's compliance programme. For transfers covered by Regulation (EU) 2023/1113, the required information on the originator and beneficiary is collected and transmitted. Checks on external wallets and additional documents depend on the transaction and the risk.
The agreement sets out what the provider does, what you do (for example, first-line support) and what the technology contractors do. The decision to accept a client or block a transaction remains with the CASP.
White Label lets you use ready-made infrastructure, while your own authorisation offers greater independence within the scope of permitted services. The full budget needs to be compared: development, staff, controls, servicing and dependence on contractors. The choice depends on the business's functions and scale.
|
Criterion |
White Label |
Own CASP authorisation |
|---|---|---|
|
Time to market |
After checks and integration; according to the project schedule |
Preparation and authorisation procedure; depends on document completeness and the regulator |
|
Initial budget |
Setup, integration and RUE's services; individual estimate |
Documentation, operational arrangements, infrastructure and prudential safeguards |
|
Prudential requirements |
The operator bears the CASP's obligations; the customer may have other requirements and contractual deposits |
At least the higher of EUR 50,000 / 125,000 / 150,000, depending on services, or one quarter of annual fixed overheads; in a form permitted under MiCA |
|
Ongoing obligations |
Provider fees and the customer's own contractual and legal obligations |
Governance, compliance, controls, reporting and applicable checks |
|
Responsibility |
CASP – for its regulated services; customer – for its own actions |
Your company – for its services and compliance with requirements |
|
Control over the product |
Within the agreement and the platform's capabilities |
Broader, but within the limits of permissions, the law and resources |
|
Dependence on contractors |
Significant dependence on the CASP and its infrastructure |
Remains when using external software, custody and payment services |
If you plan to move to your own licence in the future, arrangements for migrating clients and assets should be included in the provider agreement from the outset.
Countries, customers, functions and turnover. We select a provider and prepare a proposal.
The provider checks the company, owners and business model.
CASP agreement, customer documents and marketing rules.
Branding, domain, functions, API and payment methods.
We test the entire user journey and train your team.
We open the service once readiness is confirmed and arrange the agreed support.
The timeline depends on the package, the speed of checks and interface readiness. Development and mobile applications take additional time. The precise schedule is set out in the proposal.
|
Work |
Scope |
Who issues the invoice? |
|---|---|---|
|
One-off RUE services |
Project analysis, provider selection and due diligence, legal arrangements and launch coordination |
RUE |
|
CASP services |
Setup, user checks, exchange, custody and transfers |
CASP at its own rates |
|
Post-launch support |
Advice, contract amendments, new countries and functions, and preparations for your own licence |
RUE under a separate agreement |
RUE does not provide crypto-asset services, hold client assets or money, or act as a party to agreements with users.
The lowest fee is of little use if the CASP does not cover the countries or assets you need.
Phrases such as "our MiCA licence" or "licence rental" mislead customers and create risks for both parties.
If users cannot see who their provider is, both customers and the regulator will have questions.
Without termination and migration clauses, switching providers can turn into lengthy negotiations.
Advertising has started, but no one is available to answer users. First-line support must be in place before launch.
This depends on your company's actual activities. Owning a brand and a technical interface does not, in itself, require CASP authorisation. If your team provides regulated services, including receiving and transmitting orders, an agreement with the operator does not replace the necessary status. The model is assessed before launch.
The licensed CASP. The operator is identified in the interface and terms of service, while your brand remains the public face of the service.
Custody is provided by the authorised provider identified in the customer documents. It segregates client assets from its own and keeps records of users' rights. Wallet arrangements and access to keys are determined by the custody terms; a separate address for every client is not a universal feature of the model.
Countries confirmed for the selected operator and specific product. Permitted services, cross-border notifications, client categories and payment restrictions are taken into account. The offer focuses on the EU and confirmed coverage in the EEA.
Yes: the name, domain, logo, colours and languages are yours. Changes beyond the template are priced separately.
User fees, the spread and the brand owner's remuneration are agreed with the operator. The contract determines whether a markup can be applied, how fees are disclosed and how settlements are made. The ability to change fees freely is not assumed.
The timeline is agreed after the company checks and review of the technical requirements. A ready-made interface requires less development than an API integration. A specific date can be committed to once the operator, payment integrations and documents are confirmed ready.
You usually handle first-line support, while questions about transactions, checks and complaints are referred to the CASP. Response times are set out in the agreement.
The agreement sets out the notice period, return or transfer of user assets, data export and the process for moving to another provider or operating under your own licence. We review these terms before signing.
The overall budget includes setup, RUE's work, integrations and ongoing fees. The publicly advertised starting fee of EUR 15,000 relates to setup with one provider. Exchange, verification, transfer, customisation and support fees are accounted for separately.
Software provides technical functions. In the solution described here, the CASP's regulated services are connected to it. Neither the software nor a White Label agreement transfers the operator's authorisation to your company.