Skip to content

Custody Platforms for Banks: Fireblocks vs Taurus vs Ripple Custody vs BitGo vs Dfns vs Utila

Six vendors sell the key management, approval rules and wallet software that a European bank or licensed crypto firm uses to run custody. Seen from the integration side, the six platforms differ on four questions. The questions are where the keys and the platform run, how approvals are enforced, what already connects to a core banking system, and whose license covers custody. On the license question, ESMA's register of 5 November 2026 lists one of the six as authorized for custody: BitGo's German entity.

Luis Medeiros

Reviewed by Luis Medeiros, Field CTO at Protofire · Updated November 2026

TL;DR

A bank should choose a custody platform by deployment first and by its core banking link second. A bank custody platform is the software that generates and guards private keys, enforces who may approve a transfer and keeps wallets in step with the bank's books. On deployment, Taurus-PROTECT and Ripple Custody document a full deployment in the bank's data center on its own hardware security modules (HSMs). Dfns' home page now offers a customer-hosted model as well, but its documentation describes on-premises signing that still calls Dfns' API. Fireblocks can keep signing keys in the bank's HSM through KeyLink, while the platform runs in Fireblocks' cloud. BitGo always holds one key. Utila holds one of two MPC key shares unless the bank signs through Utila's HSM connector. The core banking links to check are Taurus with Temenos Core, Fireblocks with Avaloq at Zürcher Kantonalbank, Ripple inside DXC's Hogan, Dfns on Temenos Exchange and Utila with Matera. BitGo is the only one of the six with an EU custody authorization of its own, held by BitGo Europe GmbH. Whichever platform it picks, the bank still builds ledger booking, reconciliation, Travel Rule data and payment flows.

Protofire integrates the six platforms compared here with core banking, general ledgers, payments and reporting. Fireblocks, Taurus, Ripple, BitGo, Dfns and Utila are not affiliated with Protofire. None of them sponsored or reviewed this page, and none endorses it. Every route here needs integration work we could be paid for, so we gain whichever platform a bank picks. We hold no MiCA license and custody no client assets. Vendor facts come from each vendor's documentation and press pages, read on 5 November 2026. License data comes from ESMA's interim MiCA register, a CSV file of the same date. Key-management models, from multisig to multi-party computation (MPC), are compared in crypto custody models. Renting a licensed provider's crypto service instead of running a platform is compared in crypto-as-a-service for banks. The rest of the series is in our decision guides.

Scorecard

The six platforms at a glance (November 2026)

Key technologyMPC, or signing keys in the bank's HSM via KeyLinkFIPS 140-2 HSMs (Level 3, or 3 or 4 per its docs), optional MPCBank's HSM (Thales, Securosys, IBM, BlockSafe, AWS CloudHSM) or 3-of-4 MPCUser, backup and BitGo keys; BitGo holds oneMPC (managed, hybrid or self-hosted) or HSM (Thales, Securosys, IBM, AWS CloudHSM)Two-party MPC with Utila holding one share, or the bank's HSM through a local connector
Can run entirely on bank premisesNo: co-signer and KeyLink attach to Fireblocks' cloudYes: SaaS, hybrid or fully on premisesYes: Kubernetes or OpenShift in the bank's data centerNo: user and backup keys on premises, BitGo key with BitGoHome page shows a customer-hosted model; docs describe on-premises signing that calls Dfns' APINo: SaaS with a co-signer on bank infrastructure
Policy engineTransaction Authorization Policy: ALLOW, BLOCK, 2-TIERRoles and rules down to smart-contract functionsApproval policies on governed changes (intents)Policy Builder; user-plus-backup recoveries bypass itPolicies that block or require approvalPolicies set by a quorum of admins
Published core banking linkAvaloq at Zürcher Kantonalbank (Sep 2024)Temenos Core (Dec 2024); claims 10+ core systemsDXC Hogan (Jan 2026); Avaloq at BBVA Switzerland (as Metaco)None publishedTemenos Exchange listing (Sep 2024); FIS, Fiserv, Mambu, Thought Machine listed as integrationsMatera Digital Twin (Aug 2026)
Ledger and accountingTRES Finance, acquired Jan 2026Real-time booking inside Temenos CoreInternal balance accounting; no general ledger connector publishedAccounting software integrations for tax reportingCryptio and Bitwave shown as accounting integrations, marked coming soonMatera's ledger layer; Cryptio integration (Oct 2026)
Vendor's own EU custody license (ESMA, 5 Nov 2026)NoneNone; FINMA in Switzerland, CySEC MiFID license in CyprusNone for custody; exchange and transfer (CSSF, 29 Jun 2026)BitGo Europe GmbH, BaFin, 9 May 2025, custody includedNoneNone
Best fitBanks that accept cloud orchestration, keys optionally in their HSMBanks that want everything in house, especially on TemenosLarge banks with HSM and platform teams, or on HoganFirms that want to hand custody to a MiCA custodianFirms building their own wallet product on an APIPayment and stablecoin operations run as a service
In detail

How do the six platforms compare from the integration side?

01

Fireblocks

A cloud platform that can keep keys in the bank's own HSM through KeyLink
Strengths
  • +KeyLink connects the bank's existing HSM or key management service, which holds the ECDSA secp256k1 and EdDSA Ed25519 signing keys
  • +Transaction Authorization Policy (TAP) rules match initiator, asset, amount per transaction or over a time window, source and destination. Each rule sets an action of ALLOW, BLOCK or 2-TIER.
  • +In a published Swiss bank rollout, Avaloq launched its digital asset platform at Zürcher Kantonalbank in partnership with Fireblocks in September 2024
  • +Fireblocks bought TRES Finance on 7 January 2026 to turn wallet activity into records for ERP, ledger and reporting workflows
Trade-offs
  • −The platform, TAP and orchestration run as Fireblocks' cloud service. An API Co-signer on bank servers cannot operate unless it is attested against Fireblocks' Remote Attestation server.
  • −No Fireblocks entity is in ESMA's MiCA register, so the custody authorization and its liability are the bank's
  • −TAP governs transactions only. Adding users, whitelisting addresses and changing policies go through a separate Admin Quorum, so the bank maps its authority matrix onto two control sets.

Fireblocks is a cloud platform for MPC wallets, approval policies and transfers. A bank can leave key shares with Fireblocks, or it can bring them on premises in one of two ways. The API Co-signer runs in an Intel SGX enclave on the bank's servers and holds a key share. But Fireblocks' documentation states that the API Co-signer "cannot operate unless it is attested against Fireblocks' Remote Attestation server". With KeyLink, a bank that already runs HSMs keeps the ECDSA secp256k1 or EdDSA Ed25519 signing keys in its own HSM or key management service. Fireblocks orchestrates the transactions around those keys.

Approvals in Fireblocks go through the Transaction Authorization Policy. Each rule sets who may initiate, which asset, an amount per transaction or summed over a period, and the source and destination. Each rule also sets an action of ALLOW, BLOCK or 2-TIER. For bookkeeping, Fireblocks acquired TRES Finance on 7 January 2026. TRES turns operational records into data that aligns "with established ERP, ledger, and reporting workflows". TRES lists Bank Frick among more than 230 clients.

Fireblocks' published European bank rollout is Swiss. Avaloq integrated its digital asset platform at Zürcher Kantonalbank "in partnership with Fireblocks", as announced on 6 September 2024. Avaloq runs the platform for Zürcher Kantonalbank as SaaS, and the bank keeps the private keys itself. So a bank on Avaloq has a reference setup to ask Avaloq and Fireblocks about. Fireblocks' US trust company is covered in crypto custody models. In the EU, Fireblocks sells software and the bank is the custodian.

02

Taurus-PROTECT

HSM-rooted custody software that can run entirely on the bank's premises
Strengths
  • +Taurus' documentation lists three deployment models: SaaS, hybrid (part SaaS, part on premises) or fully on premises
  • +Keys are generated and used inside FIPS 140-2 Level 3 HSMs, and MPC is available on top. On premises, the bank owns and operates those HSMs.
  • +Taurus has had a detailed, published core banking integration with Temenos Core since December 2024. The integration includes real-time transaction booking.
  • +Taurus named Capco its implementation partner for Continental Europe, announced 3 February 2026. Taurus also lists ISAE 3402 Type II and ISO 27001.
Trade-offs
  • −In a fully on-premises setup, the bank runs, patches and backs up the HSMs and the platform around the clock
  • −No Taurus entity is in ESMA's MiCA register. Taurus SA is FINMA-regulated in Switzerland, and Taurus (Europe) Ltd holds a CySEC MiFID license for financial instruments. So the bank bears custody liability in the EU.
  • −Taurus' ecosystem page claims '10+ core banking systems, including pre-built connectors' and shows Avaloq and finnova logos. But only the Temenos link is described in a dated release, so other connectors need confirming bank by bank.

Taurus-PROTECT is the custody module of Taurus, a FINMA-regulated securities firm in Switzerland. Taurus' Cyprus subsidiary, Taurus (Europe) Ltd, received a MiFID investment firm license from CySEC. The license is dated 9 March 2026 in CySEC's register. The MiFID license covers financial instruments, and no Taurus entity appears in ESMA's MiCA register.

Taurus' platform documentation lists three deployment models: "(i) SaaS, (ii) hybrid i.e., part SaaS, part on-premises, and (iii) fully on-premises". The documentation says the platform protects keys in HSMs with a "hardware root of trust in FIPS 140-2 Level 3 or Level 4". Taurus' MPC protocol is available on top. The same page says clients "can audit us and have access to our source code". The page also describes a policy engine with controls down to individual smart-contract functions. Taurus' product page places keys in FIPS 140-2 Level 3 hardware "that the bank owns and operates, on-premises if required".

Taurus has published the most about core banking. Taurus announced its Temenos Core integration in December 2024. The Temenos Core integration covers one-click wallet and address creation linked to client accounts, automated deposits and withdrawals, real-time transaction booking and tokenized-asset creation inside the bank's securities processes. Taurus' ecosystem page claims "more than 10+ core banking systems, including pre-built connectors" and automated transfers and reconciliations. The ecosystem page shows Avaloq, finnova and Temenos among its ecosystem logos but names no bank behind those connectors.

On 3 February 2026, Taurus named Capco its implementation and integration partner in Continental Europe. KBC in Belgium runs client crypto custody on Taurus-PROTECT, as set out in crypto-as-a-service for banks.

03

Ripple Custody

The former Metaco Harmonize: software the bank runs or Ripple hosts, on the bank's HSMs or a shared MPC
Strengths
  • +Ripple Custody runs in the bank's own data center on Kubernetes or OpenShift, or hosted by Ripple
  • +Ripple publishes a list of validated HSMs: Thales Luna, Securosys Primus, IBM LinuxONE (FIPS 140-2 Level 4), BlockSafe and AWS CloudHSM. MPC is the other option.
  • +In January 2026, the core banking vendor DXC agreed to integrate Ripple's custody into Hogan, which DXC says powers more than 300 million deposit accounts. At BBVA Switzerland, Ripple Custody runs on Avaloq.
  • +DZ BANK chose the platform for its institutional custody offering, and BBVA Switzerland chose it too, both as Metaco Harmonize. BBVA in Spain also chose it.
Trade-offs
  • −On premises, the bank runs the whole stack: Kubernetes or OpenShift, PostgreSQL, a message broker, blockchain nodes and HSMs. The bank runs each part with high availability and disaster recovery.
  • −In the MPC model, Ripple runs two of the four key-share nodes
  • −Ripple's MiCA authorization covers exchange and transfer and does not cover custody (Ripple Payments Europe S.A., CSSF)
  • −Metaco Harmonize became Ripple Custody after Ripple's 2023 acquisition, so the product has had two names in a few years

Ripple Custody is the custody software Ripple has sold since it bought Metaco in 2023. DZ BANK and BBVA Switzerland selected the software under its earlier name, Metaco Harmonize. BBVA Switzerland's setup is integrated with Avaloq's crypto assets platform and core banking system. BBVA also uses Ripple Custody in Spain (see crypto-as-a-service for banks).

Ripple Custody's key management options cover on-premises HSMs from Thales (Luna 7), Securosys (Primus), IBM (LinuxONE, FIPS 140-2 Level 4) and BlockSafe, AWS CloudHSM, or MPC. The MPC option uses "3-of-4 threshold signing", where keys are split across four nodes, "2 Ripple + 2 customer".

A bank that runs Ripple Custody in house has to operate the platform's infrastructure. Ripple's readiness guide asks the bank for teams that operate Kubernetes or OpenShift and PostgreSQL with replication and backup. The guide also asks for teams that operate an AMQP broker such as RabbitMQ with high availability and disaster recovery. The core banking route most relevant to large banks is DXC's January 2026 agreement to bring Ripple's custody and payments into Hogan. DXC says Hogan powers more than 300 million deposit accounts.

Ripple's own license is a separate matter. Ripple announced its MiCA CASP license from Luxembourg's CSSF on 6 July 2026. ESMA's register lists Ripple Payments Europe S.A., authorized on 29 June 2026, for exchange and transfer services but not for custody.

04

BitGo

Wallet software, or a MiCA-authorized custodian that holds the assets
Strengths
  • +BitGo Europe GmbH has held a MiCA authorization from BaFin since 9 May 2025 for custody, exchange, execution, order transmission and transfer. A bank can therefore delegate custody to BitGo Europe.
  • +Advanced Wallets keep the user and backup keys on premises, in the bank's own HSM or key management service
  • +Policy Builder rules cover destinations, initiators, thresholds, velocity limits and approval webhooks
Trade-offs
  • −BitGo always holds the BitGo key. The on-premises Master BitGo Express needs outbound access to app.bitgo.com.
  • −With Advanced Wallets, the bank writes its own key-provider integration for its HSM or key management service
  • −Withdrawal policies apply only to transactions that involve BitGo. A recovery with the user and backup keys bypasses those policies.
  • −BitGo publishes no core banking connector or system-integrator program

BitGo is the only vendor here that is both wallet software and a custodian authorized under MiCA. In BitGo's software, every wallet has a user key, a backup key and a BitGo key. BitGo's Advanced Wallets let a bank keep the user and backup keys "within your region or jurisdiction (also known as on-prem) using your own hardware security module (HSM) or key management service (KMS)". With Advanced Wallets, BitGo still "manages the BitGo key". The Master BitGo Express server "requires outbound network access to app.bitgo.com". The bank must "provide your own implementation" of the key-provider API in front of its HSM.

BitGo's policy documentation contains a caveat that a risk team should read. The documentation says withdrawal rules "apply only to transactions that involve BitGo". According to the same documentation, recovery transactions that use the user and backup keys "bypass any policies".

As a custodian, BitGo Europe GmbH in Frankfurt appears in ESMA's register as authorized by BaFin on 9 May 2025. Custody is among BitGo Europe's authorized services. An EU bank can therefore delegate custody to BitGo. ESMA's April 2026 statement says MiCA "specifically prohibits CASPs from outsourcing or delegating certain services, namely custody, to entities not authorised as CASPs themselves". None of the other five vendors holds a custody authorization in the register.

05

Dfns

A wallet API over MPC and HSM key models, from managed MPC to the bank's own HSM
Strengths
  • +The same API across managed MPC, hybrid MPC, self-hosted MPC, on-premises HSM and cloud HSM
  • +A bank can move between models without changing application code, according to Dfns' documentation
  • +Validated HSM integrations for Thales Luna, Securosys Primus, IBM EP11 and AWS CloudHSM
  • +Dfns has been listed on Temenos Exchange since September 2024. Dfns describes the listing as a first for an EU-based wallet service.
Trade-offs
  • −In the documented on-premises models, the bank's systems still call Dfns' API, and the HSM Driver polls Dfns' API from the bank's network. The fully customer-hosted model on Dfns' home page is not in the deployment documentation.
  • −The banks named on Dfns' site (Standard Chartered, FAB, Vermont State Bank) are headquartered outside the EU
  • −Dfns is not in ESMA's register. Dfns sells software, so the bank keeps the custody liability.

Dfns sells a wallet and signing API and lets the customer choose where the key shares are held. Dfns' deployment models start with fully managed MPC in the Dfns cloud. In hybrid MPC, the bank runs a Dfns signing server that holds one or more shares. The hybrid model gives the bank "a direct cryptographic veto over any transaction". In self-hosted MPC, all shares are in the bank's data centers. The remaining models use an on-premises HSM through a PKCS#11 HSM Driver, or a cloud HSM. Dfns' documentation states that "the DFNS API remains consistent across all deployment models". So the bank's integration code does not change when the bank moves its keys in house.

Dfns' home page goes further than its deployment documentation and shows a customer-hosted model. In that model, the application, keys, nodes and identity are in the bank's own data centers. The code is "granted (+ escrow)". The deployment pages describe on-premises signing only, so a bank that wants the customer-hosted model should ask Dfns for technical documentation of that model.

Dfns' link to core banking is a marketplace listing, with no named bank rollout. In September 2024, Dfns joined Temenos Exchange and described itself as "the first EU-based wallet service and digital asset infrastructure" there. Dfns' home page lists FIS, Fiserv, Mambu, Thought Machine and Temenos among its system integrations.

In Dfns' documented on-premises models, the HSM Driver polls Dfns' API from the bank's network. So those models depend on Dfns' service being reachable, and the bank's DORA register should record that dependency.

06

Utila

Two-party MPC as a service, with a co-signer and an HSM connector
Strengths
  • +Utila and the customer run MPC with one key share each, so no complete key exists in one place
  • +Utila has SOC 2 Type II and ISO 27001. Halborn audited Utila's infrastructure.
  • +Utila works with Matera for a ledger layer next to the core (August 2026). Matera's Digital Twin provides real-time authorization and the ledger for customer and bank-level balances.
  • +For banks, a local connector from Utila runs inside the bank and passes approved signing requests to the bank's HSM
Trade-offs
  • −Utila holds one of the two shares in its MPC model, so every MPC signature involves Utila's service
  • −The HSM route is described in a July 2026 blog post. It is not in the product documentation.

Utila sells wallet and payment operations as a service. Utila's security page says the MPC protocol "is executed between Utila and the customer, each holding one share of the distributed key". The security page calls this setup "self-custody infrastructure" and lists SOC 2 Type II, ISO 27001 and a Halborn audit.

For banks, a July 2026 post describes "a Utila-provided local connector, operating inside the institution's environment". The connector passes approved signing requests to the bank's HSM, where keys "remain non-extractable". According to the post, Utila "receives the resulting signatures" without holding a key share.

Utila connects to core banking through a second vendor. In August 2026, Utila partnered with Matera "to help banks add digital asset services without undertaking a core banking transformation". Matera's Digital Twin acts as the real-time authorization and ledger layer for customer and bank-level balances, beside the existing core. A bank that takes the Utila and Matera route integrates two vendors. The bank still owns the reconciliation between Matera's ledger and its own general ledger. For accounting data, Utila connected Cryptio in October 2026. Cryptio imports vault, wallet and transaction data for reconciliation and reporting.

Landscape

What the platform supplies, and what the bank still builds

Client accounts and bookingWallets and addresses, per client or omnibus, with balances and events by API and webhookMapping each wallet to client accounts in core banking, and booking every deposit, withdrawal and fee to the general ledger
ReconciliationTransaction history, audit logs and reportsA daily match of platform balances, onchain balances and ledger positions, with breaks routed to operations
ApprovalsA policy engine and approver quorumsThe bank's authority matrix written as policy rules, and the change process that keeps the two in step
Travel RuleConnectors to Travel Rule providersOriginator and beneficiary data drawn from KYC records, and handling for transfers to self-hosted wallets
Fiat and paymentsStablecoin pay-ins and payouts on some platformsSEPA and ISO 20022 payment messages for the euro leg, and the bank's on/off-ramp
Operations and exitStatus pages, audit logs and service levels24/7 monitoring, incident runbooks, key ceremonies and a DORA exit plan that can move wallets to another platform

In Fireblocks' 2026 survey of more than 600 executives, continental European institutions ranked integration with existing bank systems joint second (46%) when choosing a digital asset provider. Scale, reliability and performance also scored 46%, and custody and wallet governance ranked first at 67%. The same survey found that only 16% of institutions overall had reached production. Fireblocks is one of the vendors compared here, so read the figures as directional. The rows below apply to all six platforms.

Verdict

Which platform fits which bank?

If your priority is
Keys and platform inside the bank's data center

the risk function wants no vendor cloud in the signing path and the bank has HSM, Kubernetes and 24/7 operations teams. Choose Taurus if the core is Temenos, and Ripple Custody if the core is Hogan or the bank wants an IBM LinuxONE HSM.

→Taurus-PROTECT or Ripple Custody
If your priority is
A cloud platform, with keys optionally in the bank's HSM

the bank accepts Fireblocks' cloud for orchestration and policies, wants KeyLink or an API Co-signer for its keys, and, if its core is Avaloq, has the Zürcher Kantonalbank setup to point to.

→Fireblocks
If your priority is
Custody delegated to a MiCA-authorized custodian

the bank or crypto firm would rather have BitGo Europe hold client assets under its BaFin authorization, or would rather keep two of three keys on premises with Advanced Wallets.

→BitGo
If your priority is
An own wallet product on one API, key model decided later

the team builds its own client-facing product and wants to start on managed MPC and move to self-hosted MPC or its own HSM without rewriting the integration.

→Dfns
If your priority is
Stablecoin operations as a service

the firm runs payment or treasury flows, accepts a two-party MPC where Utila holds one share, and can add Matera or its own ledger beside the core.

→Utila
Also consider

Custodians, an in-house build and related decisions

  • Copper, Komainu, Zodia Custody and Hex Trust: these four firms hold client assets themselves. So a bank that uses them delegates custody instead of running a platform. Under MiCA, custody may be delegated only to an authorized crypto-asset service provider (CASP), according to ESMA's April 2026 statement. Of the four, only Zodia Custody (Europe) S.A. was in ESMA's register on 5 November 2026. Luxembourg's CSSF authorized Zodia Custody (Europe) S.A. on 12 December 2025 for custody and transfer.
  • An in-house build on bare HSMs: a bank can buy HSMs, such as Thales Luna or Securosys Primus. The bank then writes the wallet, policy, chain-connection and indexing layers itself. A bank that builds in house is responsible for every chain upgrade and every curve-support gap. That responsibility comes on top of the custody liability described in crypto-as-a-service for banks. Banks that announced their own key custody, such as BBVA and Zürcher Kantonalbank, run it on vendor software. BBVA uses Ripple Custody, and Zürcher Kantonalbank uses Avaloq's platform with Fireblocks.
  • Renting the whole service instead: Sygnum, Boerse Stuttgart Digital, Bitpanda Enterprise, Crypto Finance and Kraken Embed supply custody and trading to banks by API. So a bank that uses them runs no custody platform at all. These five providers are compared in crypto-as-a-service for banks.
  • DORA: each of the six platforms, used as software, is an ICT third-party provider to an EU bank. SaaS models also put the vendor in the signing path. The guide DORA third-party risk for onchain providers compares what the register of information, the contract terms and the exit plan must cover.

FAQ

What is a digital asset custody platform for a bank?
A digital asset custody platform is the software a bank uses to generate and protect private keys. The bank also uses the platform to approve and sign transfers under its own rules and to track balances per wallet. The platform holds keys in hardware security modules (HSMs), as multi-party computation (MPC) key shares, or both. Fireblocks, Taurus-PROTECT, Ripple Custody, BitGo, Dfns and Utila sell such platforms. None of the six replaces core banking.
Which custody platforms can a bank run entirely on premises?

Taurus-PROTECT and Ripple Custody document a full deployment in the bank's own data center. Taurus documents SaaS, hybrid and "fully on-premises" deployment. Ripple Custody installs on the bank's Kubernetes or OpenShift, with the bank's own HSMs. Dfns documents models that keep all keys and signing on premises, but the bank's systems still call Dfns' API in those models. Dfns' home page also shows a customer-hosted model, which a bank should ask Dfns to document.

Fireblocks can hold keys in the bank's HSM through KeyLink. BitGo can keep user and backup keys in the bank's HSM through Advanced Wallets. But Fireblocks and BitGo both run in the vendor's cloud. Utila is a service in which Utila holds one of two MPC shares or signs through the bank's HSM via a local connector. Each platform's section in this guide gives the detail and sources.

Which custody platform vendors hold a MiCA license for custody?
Of the six vendors, only BitGo holds a MiCA license for custody. BaFin has authorized BitGo Europe GmbH for custody and five other services since 9 May 2025, according to ESMA's register of 5 November 2026. Luxembourg's CSSF has authorized Ripple Payments Europe S.A. for exchange and transfer, but not for custody. Fireblocks, Taurus, Dfns and Utila have no entity in the register. A vendor's license does not matter for a bank that runs the software itself, because the bank is the custodian. The license matters only if the bank wants the vendor to hold client assets.
Does a bank need its own MiCA license to run custody software?
A bank that runs custody software for clients is the custodian, so the bank needs MiCA cover for custody. An EU credit institution gets that cover through an Article 60 notification to its supervisor rather than a separate license. The credit institution then bears the custodian's liability to clients. The guide MiCA license routes compares the routes. A bank that would rather not be the custodian can delegate custody. The bank can delegate only to a provider that is itself MiCA-authorized for custody, such as BitGo Europe or Zodia Custody (Europe).
How does a custody platform connect to core banking and the general ledger?

A custody platform connects to core banking through its API and webhooks on one side and the core's own interfaces on the other. A published connector shortens the work. Taurus-PROTECT integrates with Temenos Core for wallet creation and real-time booking. Avaloq runs its Fireblocks-based platform for Zürcher Kantonalbank. DXC is integrating Ripple Custody into Hogan, and BBVA Switzerland runs Ripple Custody on Avaloq. Dfns is listed on Temenos Exchange, and Utila works with Matera's ledger layer.

Without a connector, an integrator maps wallets to client accounts and books each deposit, withdrawal and fee to the general ledger. The integrator also runs a daily reconciliation between the platform, the chain and the ledger. BitGo publishes no core banking connector. The guide custody to core banking integration compares the four booking patterns, from a native connector to the bank's own subledger.

What does a bank still build after choosing a custody platform?
The bank still builds everything between the custody platform and its existing systems. The bank's build includes wallets mapped to client accounts, bookings to the general ledger and a daily reconciliation of platform, onchain and ledger balances. The bank writes its authority matrix as policy rules and draws Travel Rule data from its KYC records. The bank also builds SEPA and ISO 20022 flows for the euro leg, statements, and 24/7 monitoring with a DORA exit plan. Vendors supply connectors and APIs for parts of the build, but none of the six vendors delivers the whole list. The comparison table in this guide shows where each vendor stops.
Is Ripple Custody the same as Metaco Harmonize?
Yes. Ripple bought the Swiss custody software firm Metaco in 2023 and sells Metaco's Harmonize platform as Ripple Custody. Banks that chose Harmonize before the acquisition appear in older releases under the Metaco name, as noted in crypto-as-a-service for banks. Examples include DZ BANK and BBVA Switzerland. Ripple Custody is software that the bank runs or Ripple hosts. Ripple Payments Europe S.A. in Luxembourg holds Ripple's own MiCA authorization, which covers exchange and transfer but not custody.
Who implements these custody platforms in Europe?
The vendors' own professional services, core banking vendors and named integration firms implement these custody platforms in Europe. In February 2026, Taurus named Capco its implementation and integration partner in Continental Europe. Avaloq delivered the Fireblocks-based setup at Zürcher Kantonalbank. DXC is building Ripple Custody into its Hogan core, and Utila works with Matera for the ledger layer. Engineering firms, Protofire among them, can build the connection to core banking, ledgers and payments on any of the six. Before signing, ask any implementer which core banking system it has connected the platform to. Also ask for the implementer's reconciliation design.
Build it

On any of the six platforms, Protofire connects the custody software to the bank. The connection maps wallets to client accounts in Temenos, Avaloq or FIS and books every movement to the general ledger. It also includes a daily reconciliation against the chain, your authority matrix written as policy rules, and the monitoring that runs after go-live.

Custody platform integration for banks →

Get a proposal

Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.

Luis MedeirosField CTO, reads every request · LinkedIn

A demo or repository link also works.