Crypto-as-a-Service Integration for Banks

We book each buy and sell against the client's cash account and hold crypto positions next to funds and securities in the portfolio view. We also produce the data for statements, cost basis and tax reporting in the formats your core already uses.

Public deployments show the range of starting points. BancaStato connected Sygnum's API directly into its Avaloq SaaS core banking without a separate order management system, and BBVA Switzerland's custody software integrates with Avaloq.

Taurus-PROTECT has an integration with Temenos Core, and finnova announced a crypto trading partnership with Wyden in 2023. We build against the core you run, whether Avaloq, Temenos, finnova or an in-house ledger, and reuse an existing connector where one covers the job.

We build on the bank's existing onboarding: the KYC record, the client classification and the investor questionnaires your compliance team already runs decide who may trade, which assets and up to what amount.

Every crypto transfer carries originator and beneficiary data under the EU Transfer of Funds Regulation. For a transfer above EUR 1,000 to a self-hosted address, the crypto-asset service provider sending it must take adequate measures to assess whether the client owns or controls that address (Article 14(5)).

We wire Travel Rule messaging and address screening into the flow, or design external transfers out. KBC keeps crypto bought on Bolero within the platform, and DekaBank's offer allows withdrawals only to addresses at certain crypto-asset service providers.

For the KYC and screening vendors themselves, see compliance integration; the Travel Rule networks and vendors are compared in our EU Travel Rule guide.

At the end of each day we compare every client position in core banking with the custodian's records, and each break is assigned to an owner before the next business day opens. On a rented rail the custodian's statement is the reference. On the bank's own custody the chain is, so we index the bank's addresses and reconcile client sub-ledgers against onchain balances and the custody software's records.

That indexing comes from our subgraphs on The Graph and our blockchain data indexing work. A daily position check also resembles the proof-of-reserve work we delivered for a large auditing firm, across 15+ deployments for asset-backed tokens.

A bank's MiCA Article 60 notification has an engineering half. Delegated Regulation (EU) 2025/303 asks for the ICT services that support critical or important functions, which of them third parties provide and how those arrangements meet MiCA Article 73 and DORA. It also asks for the custody policy and, where custody is delegated, who holds the assets and under which license.

We produce those inputs from the system we build: architecture and data-flow documents, the outsourcing map of every provider and subcontractor in the chain, the key-management and security description, and the entries your DORA register of information needs. The notice period and the rules for each route are set out in our guide to crypto-as-a-service for banks.

MiCA's Article 73 asks for exit strategies in the outsourcing policy, and DORA asks for tested exit strategies for ICT services that support critical or important functions. We build the exit into the system.

Positions are recorded first in the bank's own ledger, and every provider is reached through its own adapter. The migration runbook is rehearsed in test, with positions reconciled on both custodians before and after the cut-over.

In the disclosed-counterparty shape, where the client holds the crypto account with the provider, a switch also means moving each client's account, so we plan the data transfer and the client consent steps that requires.

We watch order flow, provider API health, reconciliation breaks and custody events around the clock, plus key use and chain upgrades on the bank's own custody. Responses follow runbooks the bank approves, and the service is delivered through our managed onchain operations.

For own custody we can run key ceremonies and hardware security module (HSM) or multi-party computation (MPC) procedures with your security team, on Ripple Custody, Taurus-PROTECT, Fireblocks or Utila.