Перейти к содержимому
guide16 ноября 2026 г. · 8 min read

Crypto trading for neobanks and fintech apps: embed a partner or run your own venue

Three ways a neobank or fintech app adds crypto trading: a crypto-as-a-service partner, a hybrid on your own ledger, or your own venue. Keys, costs, MiCA.

BitPolaris Engineering

English original

Crypto trading for neobanks comes in three shapes, and the choice is made by your licence more than by your product team. You can embed a crypto-as-a-service partner that is the licensed provider and holds the coins; you can keep your own client ledger and pricing while a partner executes and holds the assets; or you can run your own venue, with your own authorisation, custody and order book. All three can look identical in the app: a “Crypto” tab, a buy button, a balance. What differs is who the client contracts with, who holds the keys, who keeps the spread and what your regulator sees.

This guide sets out what each model puts on your side, using three public European examples, what MiCA says about who may provide the service, and what each model costs to build. Third-party facts were read on 16 November 2026 and are listed under Sources. Regulatory points are a technical reading of the rules, not legal advice; counsel should confirm.

Three ways a neobank adds crypto trading

Model 1: embedded partner (crypto-as-a-service). The partner is the crypto-asset service provider. It runs execution, custody and settlement, and may run its own onboarding checks on top of yours; you supply the customer, the app screens and the brand. Kraken describes its Embed product this way: “Kraken handles infrastructure, custody and settlement” while partners keep brand control. N26 states that N26 Crypto “is powered by Bitpanda Asset Management GmbH” and that the coins are “stored in a cold offline storage managed by Bitpanda”. Your revenue is whatever share of fees or spread the contract gives you; neither N26 nor Kraken publishes the split.

Model 2: hybrid, your ledger on a partner’s rails. You keep the client relationship in your own books: the quote the client sees, the per-client positions and the sub-ledger, while one partner fills orders in an omnibus account and a custodian holds the coins. A bank can end up here even when it starts with model 1, because the partner’s API returns a pooled fill and a street price, not a client statement. Wyden, a vendor of institutional trading software, lists four things the institution still has to do in a crypto-as-a-service set-up: turn the provider’s price into a client quote with its own spread, track positions and P&L per client, allocate pooled fills to clients, and keep client sub-ledgers reconciled with the provider and posted to the core banking system and general ledger.

Model 3: your own venue. You hold the authorisation, the keys and the order book; liquidity comes from your own market makers, from hedging each client fill on an external venue, or both. Revolut is the public example in Europe: its entity Revolut Digital Assets Europe Ltd appears on the French AMF’s list of MiCA crypto-asset service providers, authorised in Cyprus on 21 October 2025, for custody, operation of a trading platform, exchange of crypto-assets for funds and for other crypto-assets, placing and transfers.

Who holds what in each model

Embedded partner Hybrid Own venue
Licensed provider of the crypto service The partner Usually you, or you and the partner; counsel decides You
Who the client contracts with for crypto The partner, often through your app You You
Keys and coins Partner Partner custodian, or your own custody You
Client quote and spread Partner’s price; your share by contract Yours Yours
Client ledger and statements Partner, mirrored in your app Yours Yours
Withdrawals to external wallets Partner’s policy; sometimes none Depends on the custodian Your policy
Coin list Partner’s list Partner’s list, filtered by you Your listing decisions
Technical evidence for your regulator Mostly the partner’s Split Yours
Integration effort Lowest Highest per feature Highest overall
Exit Clients and coins move only if the partner cooperates Ledger is yours; coins move custodian to custodian Yours

Two rows decide most projects. “Who the client contracts with” decides what your compliance team owns: in model 1 complaints, disclosures and suitability may sit largely with the partner, but so does the customer’s crypto history. “Withdrawals” decides what the product is: a client who can only buy and sell back inside your app owns an economic exposure, not coins they can move. N26’s crypto page lists trading fees of 1.5% for Bitcoin and 2.5% for other coins and does not mention transfers to external wallets; check the current terms of any partner you consider before promising “send to any wallet” in your roadmap.

What MiCA allows a bank or an EMI to do

In the EU, Article 59 of MiCA, Regulation (EU) 2023/1114 reserves crypto-asset services for authorised CASPs and the financial entities listed in Article 60. Article 60 is what separates neobanks:

  • Credit institutions. Article 60(1): a credit institution “may provide crypto-asset services if it notifies” its home regulator “at least 40 working days before providing those services for the first time.” A neobank with a banking licence can therefore run model 2 or model 3 without a separate CASP authorisation.
  • E-money institutions. Article 60(4) is narrower: an EMI may provide custody and transfer services “with regard to the e-money tokens it issues”, and nothing else by notification. On our reading, an EMI-licensed app that wants to offer bitcoin trading itself needs a CASP authorisation, usually in a group entity, or a partner who is one.
  • Investment firms. Article 60(3) allows services equivalent to the investment services the firm is already authorised for; crypto broker software covers that case.

The notification is not a formality. Article 60(7) lists what must be sent, including a programme of operations, AML controls and business continuity plan, “the technical documentation of the ICT systems and security arrangements”, the procedure for segregating clients’ crypto-assets and funds, the custody policy where custody is offered, and the trading-platform operating rules and market-abuse detection where a platform is operated. Those are the same items a CASP files; our MiCA CASP application guide maps them to evidence. In model 1 the partner produces most of that file. Whether your role in model 1, passing orders from your app to the partner, is itself a crypto-asset service such as reception and transmission of orders is a question for counsel, and so is the marketing of crypto in your app.

Outside the EU the regimes differ, but the same question applies: does the licence you hold cover holding client crypto and exchanging it for fiat, or only distributing someone else’s service?

What you have to build in each model

Embedded partner. App screens for buy, sell and portfolio; the partner’s onboarding steps and disclosures; moving money between the client’s current account and the partner; webhooks for order status; statements; support scripts. Kraken says bunq’s launch took “a matter of weeks”. The constraint is that your product can only be what the partner’s API exposes.

Hybrid. Everything in model 1 plus a pricing service with your markup and cost floor, a position and P&L store per client, allocation of omnibus fills, daily reconciliation against the partner’s reports and the chain, and postings to your general ledger. If you take custody in house, add the key ceremony, approval policies and an officer console; custodial vs non-custodial wallets explains what that changes for recovery and liability.

Own venue. A matching engine or a quoted-swap service, a client ledger, wallets per chain with deposit scanning and withdrawal approvals, custody with hot, warm and cold tiers, a liquidity source, an operations console for KYC, approvals and audit, and fiat movement between the bank side and the crypto side. That is the scope of exchange software, and buying it is cheaper than writing it: our cost guide puts an in-house build at €1–2M and 12 to 24 months.

What the own-venue route costs with BitPolaris

Our prices are public in EUR on the pricing page; the numbers below are list prices before the multi-product discount the configurator applies.

Item Self-hosted licence Source-code licence Notes
Exchange €24,500 €58,100 Matching engine, Easy Trade and Pro terminal, identity and KYC tiers, Mirror liquidity engine, 53-screen console
Custody €14,000 with Exchange €33,600 with Exchange Vaults, policy engine, M-of-N approvals, reserve monitor; self-hosted only
Convert €1,050 €1,050 Quoted swaps outside the order book, the screen most banking apps want
Updates and support €7,700 a year Optional 15% update stream 20% of the Exchange and Custody licences
Extra UI language €280 each €280 each One-time delivery work

A bank would normally take the self-hosted or source-code model: Custody is not offered on our cloud, and on the cloud model, the one we call white-label, the keys are encrypted inside an instance we operate, which your supervisor may not accept for client assets. The three items above come to €39,550 one-time on the self-hosted model, plus €7,700 a year.

What is not in that figure: your servers and operations staff, KYC provider fees, chain fees, working balances on the hedging venue, and the integration into your existing app. Our software includes its own web terminal and iOS and Android apps; a neobank usually wants crypto screens inside its own app with its own login, which means building them against our APIs and connecting the ledger to your core banking system. That is custom development, quoted per project after scoping, not a setting.

Liquidity without inventory. The Mirror engine quotes order books on 97 markets from a reference venue with your markup and hedges each client fill there as it happens, so you do not pre-fund inventory per market; you keep working balances on the hedging venue. Reference connectivity today is through Binance and CCXT. Whether a given venue is an acceptable counterparty, and how balances held there fit your segregation and custody policy, is your compliance team’s call. How mirroring works.

How to choose

  • Start with model 1 if you hold an EMI or payment licence, crypto is a feature rather than a business line, and you accept the partner’s coin list, withdrawal policy and revenue share. Negotiate data export and client migration terms on day one, because leaving is the hard part.
  • Move to model 2 when the spread and the client record matter enough to own, and you have the engineering to run a pricing service and a sub-ledger. Most of the work is reconciliation, not trading.
  • Choose model 3 when you hold, or are applying for, the authorisation that covers custody and trading, crypto is expected to become a revenue line, and you want listing decisions, withdrawals and the evidence file in your own systems. Fiat movement between the bank side and the crypto side is usually internal; fiat rails for a crypto exchange covers the external cases.

Crypto trading for neobanks FAQ

What is crypto-as-a-service for banks?

A partner that is already a licensed crypto-asset service provider runs execution, custody and settlement behind your app through an API, and you present the service under your brand. Kraken Embed, the provider behind bunq’s in-app trading, and Bitpanda, behind N26 Crypto, are European examples. The partner usually holds the coins and sets the coin list; your revenue share is set by contract.

Can a neobank with an e-money licence offer crypto trading?

Under MiCA, an e-money institution may only provide custody and transfers of the e-money tokens it issues by notification (Article 60(4)). To offer bitcoin or ether trading itself it generally needs a CASP authorisation, often in a separate group entity, or a partner that is a CASP. A credit institution may notify its regulator 40 working days in advance instead (Article 60(1)). Counsel should confirm for your structure.

Who holds the coins when a banking app offers crypto?

In the partner model the partner does: N26, for example, states that coins bought through N26 Crypto are stored in cold storage managed by Bitpanda. In the hybrid model a partner custodian or your own custody holds them; in your own venue, you do, in custody you operate.

How long does it take to add crypto trading to a banking app?

The partner model is the shortest; Kraken says bunq’s launch took a matter of weeks. An own venue on licensed software takes five weeks from signature to go-live on our hosted model and one to two weeks more self-hosted, plus the integration into your app and the time your regulator needs, which in the EU starts with the 40-working-day notice for credit institutions or a full CASP authorisation for others.

What does it cost to run your own crypto venue as a neobank?

With our list prices, the Exchange block (€24,500), Custody bought with it (€14,000) and the Convert module (€1,050) come to €39,550 one-time self-hosted, plus €7,700 a year for updates and support. Servers, staff, KYC fees, hedging balances and the integration into your existing app are extra; the integration is quoted per project.

Sources

All read on 16 November 2026.

  1. Regulation (EU) 2023/1114 on markets in crypto-assets (MiCA), Articles 59 and 60, EUR-Lex
  2. AMF, MiCA CASP white list, Revolut Digital Assets Europe Ltd
  3. N26, N26 Crypto product page (partner, custody, fees, countries)
  4. Kraken, Kraken Embed announcement, 30 April 2025
  5. The Block, Kraken powers new crypto trading venture for bunq, 29 April 2025
  6. Wyden, Crypto-as-a-Service for banks and the client-side infrastructure gap, 7 September 2026

BitPolaris licenses the exchange, custody and quoted-swap software a bank or fintech needs to run crypto trading on its own systems: keys in your perimeter, an operations console with approval queues and an audit log, and a liquidity engine that hedges each fill instead of pre-funding inventory. Prices are public.

See the Exchange block · Pricing

Назначить 30-минутный звонок

Crypto exchange, payments, wallet, custody and token launch software, already running in production. Run it on your own servers, license the source code, or let us host it under your brand.