White-Label Crypto Exchange: What to Look For

What is a white-label crypto exchange?

A white-label crypto exchange is a trading platform built by a technology provider and presented to end users under another firm's name, logo and domain. The provider supplies the software, and the brand owner supplies the clients, the regulatory status and usually the liquidity. In Liquid Mercury's terms, white label means the vendor's technology running behind a client's own brand, with no visible vendor name or logo to the end user.

Liquid Mercury, the Chicago-based institutional digital asset infrastructure provider, sells white-label OTC and marketplace software to institutions. If you want a retail exchange script, this page will help you ask better questions, but Liquid Mercury is not that product. See the section on how we approach white label.

What a white-label platform includes

Platforms differ, but a complete offering usually covers the same eight components.

Three white-label models

White label covers three different problems. Pick the one that matches yours.

Exchange (order book). Buyers and sellers post orders that are matched against each other. This model needs liquidity from the start, which is the hard part for a new venue.

OTC desk (RFQ and streaming). Clients ask a desk for a price, or trade against streamed prices, instead of matching on a book. This model fits brokers who already have client relationships and sources of liquidity. See the OTC definition.

Tokenized asset marketplace. Issuers or platforms run a venue where tokenized assets can be discovered, bought and sold, with eligibility and transfer rules built in.

White-label OTC: Mercury OTC

Mercury OTC is fully white-labeled for client branding, with desktop and mobile layouts. A desk offers its clients RFQ, RFS and streaming quotes under its own name, with a ledger, settlement automation and reporting behind it. One execution algorithm in Liquid Mercury's suite, OTC Posting, is described as primarily used by OTC brokers that have white-labeled the OTC platform. For buyer-side questions about this category, see the guide to crypto OTC desk software and the OTC desk comparison.

White-label marketplace: Mercury RWA

Mercury RWA is a white-label marketplace solution for tokenized assets that carries your branding. The materials describe asset discovery and onboarding, investor eligibility verification, automated KYC and AML checks, programmable transfer restrictions and custody integration. You set the rules, control access and define the trading parameters for your assets.

Evaluation checklist

Put these eight questions to any provider, including us.

1. Licensing responsibility. Who holds the licences? Many white-label platforms are technology only. For example, Talos describes its white-label offering as a SaaS technology platform that does not provide registrations or satisfy KYC, AML or compliance obligations. Expect the same from most vendors, and ask.
2. Custody. Which custodians are integrated, and who controls the keys or accounts?
3. Liquidity. Does the provider supply liquidity, or do you source your own? Talos, for example, states that clients negotiate arrangements with liquidity providers themselves. Know which model you are buying.
4. Risk controls. Are credit, balance and size limits enforced before a trade, and can you halt trading?
5. Branding depth. Can you change the domain, layout, emails, documents and workflow, or only the logo?
6. API access. Which protocols can your clients and your own systems use?
7. Reporting. Can you get audit trails, trade records and settlement reports in a usable format?
8. Exit terms and IP. Who owns client data and configuration, what happens if you leave, and what do you pay to move?

Build, buy or white label

Firms that want to offer trading usually weigh three routes.

• Build in-house. You control everything, and you carry the engineering, maintenance and regulatory-readiness burden. K33, a Norwegian crypto exchange service and broker, described building infrastructure in-house as an option that carried significant development time, regulatory readiness risk and ongoing maintenance overhead, in its own case study. The published results are on the live K33 case study.
• Buy components. You assemble a quoting engine, a ledger, a risk layer and a front end from separate vendors. This gives flexibility and moves the integration work to you.
• White label. One provider supplies the stack under your brand. You configure it instead of building it, and you depend on the provider for the roadmap.

None of these is correct for every firm. The deciding questions are how much control you need over workflow, how much engineering capacity you have, and how soon you need to serve clients.

Features that separate platforms

Beyond the eight components, a few features decide whether a white-label platform fits a broker's business. Talos, which lists them on its own white-label page, is a useful reference for what vendors in this category describe:

• Customer pricing engine. Can you set spreads and markups per client and per instrument, and adjust them when markets move? This is how a broker earns on flow.
• Auto-hedging. Can the platform hedge each client trade with a liquidity provider before booking it, and can you set hedging rules by symbol and client? This decides whether the broker holds risk.
• Transaction ledger. Can clients export trades and pull history over an API without contacting your team?
• Margin and derivatives. If you offer leveraged products, can you configure margin policy per client and instrument?
• Balance management. Can you see and reconcile client balances across custodians?

For an OTC desk, the same ideas appear as pricing models (single-dealer, multi-dealer or hybrid) and a dealing book that can internalize a trade, hedge it, or pass it through back-to-back. When you compare providers, ask for each of these by name and ask the vendor to show it in a demo, not describe it.

Questions to ask in a demo

• Show me a client onboarded under our brand, from sign-up to first trade.
• Show me a limit being breached, and what the client and the desk each see.
• Show me how a trade is recorded, settled and reported, and how I would reconcile it.
• Show me what I can change without a vendor release, and what needs the vendor.
• Show me what happens to a client's open orders if the desk halts trading.

What it takes to launch

The software is one part of a launch. The rest is outside the vendor's control:

• Regulatory status. Decide which regulator oversees your activity and which licences apply in the jurisdictions you serve. In the UK, the FCA sets out its approach to cryptoassets, and in the EU ESMA covers MiCA on its MiCA page.
• Banking. You need banking relationships for fiat in and out, if you offer fiat.
• Custody. You need a custody arrangement that fits your clients and your regulator. In the US, the OCC has said national banks may offer cryptocurrency custody services.
• Liquidity. You need prices to quote, from your own book or from liquidity providers.
• Operations. You need people to onboard clients, monitor risk and reconcile.

We do not give cost or timeline figures here, because they depend on the points above and on the provider.

How Liquid Mercury approaches white label

Liquid Mercury builds modular trading and settlement infrastructure for banks, brokers, exchanges and asset managers, and most end users never see the Liquid Mercury name. The front end is white-labeled and available on desktop and mobile, and each component can be used on its own or together with the others.

To be plain about it, Liquid Mercury is not a retail exchange script or a launch-in-a-box product for founders. It sells institutional software for OTC desks and tokenized asset marketplaces, and Mercury Pro is a separate execution terminal for trading across venues. For the wider picture, read about institutional crypto trading infrastructure.