Skip to content

Connecting Custody to Core Banking: Native Connector vs Provider Ledger vs Integration Layer vs Own Subledger

After choosing a custody or stablecoin platform, a bank or payment firm still has to decide where client positions, fees and network costs are booked. The firm also has to decide which system the general ledger trusts. Vendor and bank announcements show four patterns: the core banking vendor's own connector, the crypto provider's ledger with an omnibus booking at the bank, an integration layer between custody and core, and a subledger the bank builds itself. Temenos, Avaloq and finnova have published links for the first pattern. Each of these core vendors relies on a custody vendor such as Taurus or Fireblocks for the custody technology.

Luis Medeiros

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

TL;DR

There are four ways to connect a custody or stablecoin platform to core banking. A native connector keeps client positions in the core (Taurus in Temenos, Avaloq's Crypto Assets solution, finnova's crypto settlement API). A native connector is the shortest path when your core and custodian are a supported pair. A crypto-as-a-service provider keeps the per-client register, and the bank books an omnibus position plus fees. Crypto-as-a-service needs the least build, but the provider's ledger is the book of record, and leaving that ledger means migrating every client. An integration layer translates custody events into core postings and ISO 20022 statements for any pair. With an integration layer, a second custodian becomes one more adapter behind the same booking rules. A custom subledger keeps the per-client register inside the bank. A custom subledger suits banks that run their own key custody, as BBVA announced for Spain, and it is the most to build and run. MiCA sets no reconciliation frequency. MiCA requires a per-client register of positions, with movements recorded as soon as possible (Article 75).

Patterns three and four, the integration layer and the own subledger, are the work Protofire sells to banks and payment firms. We are therefore paid more when a bank picks one of those two patterns. Where your core and custodian have a supported native connector, it beats a custom build on effort and on the number of systems to run. A provider's ledger that fits the product beats a custom build in the same way, and the verdicts in this guide say so. Protofire holds no banking, payment or MiCA license and gives no legal or accounting advice. We sell none of the core banking or custody products named here. None of the vendors named here sponsors or endorses this guide. On 5 November 2026, vendor statements were read on the vendors' own sites and rules on EUR-Lex and the ECB site. One bank example comes from a finews report. Choosing the provider itself is covered in crypto-as-a-service for banks. Choosing custody software is covered in custody platforms for banks. The rest of the series is in our decision guides.

Scorecard

How do the four patterns compare on booking, reconciliation, payments and exit?

Per-client crypto positions (book of record)In the core, through the vendor's booking modelAt the provider, as custodian; the bank mirrors per client or books an omnibus totalIn the core or a ledger the layer feeds; the layer holds the booking rulesIn the bank's own subledger
Omnibus and fiat legsCore books fiat legs on its own accountsBank books an omnibus position and fiat settlement with the providerLayer posts fiat legs and omnibus wallets to the GL accounts the bank definesSubledger posts summaries to the GL; omnibus wallets map to client positions inside it
Fees and network costsFee management in the core, where the vendor documents it (Temenos with Taurus)Provider fees per its schedule; the bank books its own client feesBooked from custody event fields such as Fireblocks feeInfo.networkFee; invoiced costs accruedBank's own fee and network-cost model
ReconciliationVendor-described; bank still matches core, custodian and chainBank matches provider reports to its own bookings and fiatLayer matches chain, custodian and core and queues breaksBank matches subledger, custody software and chain
ISO 20022 and payment railsFiat legs on existing SEPA and T2 flows; crypto legs stay in the vendor linkFiat to and from the provider as ordinary ISO 20022 paymentsCan map custody events to camt-style statements the core already readsFiat on existing flows; statement formats are the bank's choice
Stablecoins and EMTsNot stated by the core vendors we checkedAs far as the provider supports themAny token the custodian supports, with rules per tokenAny token the bank models
DORA register entriesCore vendor and custody vendorCore vendor, plus the provider where its service counts as ICT rather than a financial serviceCore vendor, custody vendor and the integrator if it runs the layerCore vendor and custody software vendor; the subledger is in-house
ExitTied to another listed connector existingClient-by-client migration off the provider's ledgerNew custody adapter behind the same booking rulesCustody software can change under an unchanged register
Who typically builds itCore vendor or its implementation partner, with the custody vendorProvider supplies the API; the bank's core team connects itBank IT or an engineering firmBank engineering, often with outside engineers
Effort driversCore release, connector version, product setupStatement mapping, client view, fiat settlementNumber of custodians, chains and tokens; core interfaces; booking rulesLedger build, controls, reporting, resilience testing
In detail

What does each integration pattern book, and where?

01

Native core banking connector

A custody or trading link the core vendor lists or ships, such as Taurus in Temenos or Avaloq Crypto Assets
Strengths
  • +Client positions and transactions are booked in the core itself. For the Taurus integration, Temenos describes real-time position booking, fee management, reconciliation and reporting in its securities workflows.
  • +Crypto is part of the same portfolio as other asset classes, as Avaloq describes for BBVA Switzerland
  • +Temenos calls the Taurus link a ready-made integration, so the bank configures more than it builds
  • +The bank has no extra system between core and custody to run, register under DORA or plan an exit for
Trade-offs
  • −A native connector exists only for specific pairs. Temenos lists Taurus, Fireblocks and Dfns, and Avaloq names Fireblocks. A custodian outside the list falls back to another pattern.
  • −None of the core vendor pages we checked says the booking covers e-money tokens (EMTs). Temenos's Fireblocks listing mentions deploying stablecoins but does not describe booking in the core.
  • −Changing custodian means changing connector, so the exit plan that DORA asks for depends on another listed pair existing
  • −Connector versions follow two release calendars, the core's and the custodian's, and the bank tests both

A native connector is a link that the core banking vendor publishes or lists. With a native connector, orders, deposits and withdrawals start in the core, and positions are booked there. Temenos announced the Taurus integration with Temenos Transact in May 2021. In December 2024, Taurus said that with Taurus-PROTECT, transactions involving digital assets "are booked directly in the Temenos core banking system, ensuring real-time booking and reconciliation". Temenos's own description of the integration places the link in core securities processing and lists "real-time position booking, fee management, reconciliation, and reporting". Temenos's Digital Assets and Crypto category shows Taurus. Fireblocks and Dfns have their own solution-provider pages.

For trading, Temenos describes a Wyden proof of concept in which orders leave the core as FIX 4.4 messages. In the Wyden proof of concept, execution reports come back "to update the record keeping in core banking". Temenos presents the combined offering as its digital asset solution within securities processing. In the Temenos offering, the custody technology comes from the integrated custody vendor. We found no Temenos page that describes booking stablecoins or EMTs.

Avaloq ships its own crypto booking and takes the custody technology from a custody vendor. BBVA Switzerland's service was developed with Avaloq's proprietary Crypto Assets solution. Avaloq says the crypto management system of that solution "is linked with Avaloq's banking platforms, alongside other asset classes". The platform Avaloq rolled out at Zürcher Kantonalbank in September 2024 covers trading, settlement and custody. That platform uses the custody capabilities of "Avaloq's partner Fireblocks". In finnova's case, the link is an API. The Swiss vendor announced a Finnova Standard API for crypto settlements in March 2023, through which ecosystem partners connect "in a standardised way".

Custody vendors describe the same links from their side. Taurus's ecosystem page says "We integrated more than 10+ core banking systems, including pre-built connectors" and shows Temenos, Avaloq and finnova. Fireblocks' infrastructure partners page names Avaloq's Crypto Asset Platform and Temenos Infinity, Temenos's digital banking product. Temenos's Wyden post says Temenos "has already integrated with" Fireblocks but does not name the core product. So you need to check a Fireblocks link into Temenos Transact bookings with both vendors for your release.

02

Provider ledger, omnibus booking at the bank

The crypto-as-a-service provider keeps the per-client register, and the bank books totals, fees and fiat
Strengths
  • +The provider ledger needs the least integration. The bank consumes the provider's API and statements and books a position per client or an omnibus total, plus fiat legs and fees.
  • +As custodian, a MiCA-licensed provider keeps the register of positions and sends the statement of position at least every three months (Article 75)
  • +Fiat between bank and provider moves as ordinary SEPA or T2 payments, which already use ISO 20022 in the bank's payment flows
  • +The pattern can run on the provider's API alone. BancaStato connected Sygnum's API to its Avaloq core and digital channels without a separate order management system.
Trade-offs
  • −The provider's ledger is the book of record for client crypto, and the bank's books reflect what the provider reports
  • −Leaving the provider means migrating every client position and its history, which shapes the DORA exit plan
  • −Reconciliation is against the provider's reports, so the bank still needs its own job to match provider totals, client positions and fiat movements
  • −Provider statements arrive in the provider's format, and the bank does the work of mapping them into core postings and client statements

In the provider ledger pattern, the crypto-as-a-service provider is the custodian and keeps the per-client ledger. The bank books what its own accounts and client view need: an omnibus or per-client mirror of positions, the fiat legs and the bank's fees. Provider documentation shows how the ledger split is chosen. Paxos documents an omnibus model in which "the Crypto Brokerage Partner relies on their own ledger for end-user's fiat and crypto balances". In the Paxos subledger model, the partner creates a Paxos profile "to hold the fiat and crypto balances for each individual user or account". Paxos also documents a mix of fiat omnibus with per-user crypto. Paxos ties the choice to whose license is used. The omnibus model is "typically only available" where the partner relies on its own licensing. The choice of model decides which side must keep, and reconcile, every client's balance.

Under MiCA, the custodian keeps "a register of positions, opened in the name of each client" and sends each client a statement of position at least every three months (Article 75(2) and (5)). When a licensed provider holds custody for the bank's clients, the provider keeps that register. The bank keeps its own records of what it booked and reconciles them against the provider. BancaStato connected Sygnum's API directly to its Avaloq core banking system in July 2026. The BancaStato case is a live example of the API route from Switzerland, which means it falls outside MiCA. The providers that sell crypto-as-a-service, and the white-label versus disclosed-counterparty shapes, are compared in crypto-as-a-service for banks. This page covers only the booking.

03

Integration layer between custody and coreProtofire's model

Middleware that turns custody events into core postings, GL entries and ISO 20022 statements
Strengths
  • +The layer works for any custodian that publishes transaction events and any core that accepts postings, including pairs with no listed connector
  • +One booking model serves several custodians or chains. A second custodian is then a new adapter behind the same postings, which shortens a DORA exit plan.
  • +The layer controls finality. It books only on the custodian's final status, such as Fireblocks COMPLETED, and can check the balance on chain before crediting.
  • +The layer can emit what the core already consumes, such as camt.053-style statements, instead of asking the core vendor for new interfaces
Trade-offs
  • −The layer is one more system to run, monitor and register under DORA. If an outside firm runs the layer, it is an ICT third-party service with the contract terms that DORA requires (Article 30).
  • −The bank or its integrator owns the booking rules, and every change in a custodian's API or a core release is tested against them
  • −Reconciliation breaks between chain, custodian and core arrive in the layer's queue and need an operations owner
  • −The layer needs more build than a listed connector, where one exists for your exact core and custodian

An integration layer connects the custody platform's API to the core banking system's interfaces. The layer takes in custody events, applies booking rules and posts to the core and the general ledger. Custody platforms publish the events that the layer consumes. Fireblocks sends transaction webhooks such as transaction.created and transaction.status.updated. Each Fireblocks transaction includes feeInfo.networkFee and its feeCurrency. For ERC-20 tokens on Ethereum, the feeCurrency is ETH. Ripple Custody offers an Events API, webhooks and an AMQP queue. The Ripple Custody documentation advises "webhooks for real-time notifications" and "the Events API for periodic reconciliation". The core side varies by vendor and release, from event streams to end-of-day files.

The integration layer is also where ISO 20022 enters. Eurosystem payments already run on ISO 20022. T2, the euro RTGS system, moved to ISO 20022 on 20 March 2023. On-chain transfers have no settled ISO 20022 mapping. The one primary example we found is Circle Mint's daily camt.053.001.13 statement, which covers USDC and EURC activity. For on-chain entries, the Circle Mint statement shows the blockchain and the transaction hash. The statement states USDC amounts with the currency code USD and keeps the token name in supplementary data. A bank that books USDC as an asset separate from USD maps from that token field. Network fees need another rule. Circle converts the fee on each outgoing transfer to USD at the time of the transfer. Circle invoices the total in the first five business days of the following month, so the layer accrues the fee when the transfer settles.

04

Custom subledger inside the bankProtofire's model

The bank keeps the per-client register of crypto positions in its own stack and posts summaries to the GL
Strengths
  • +The bank's own register is the book of record, which fits a bank that is itself the custodian under MiCA (Article 75)
  • +The bank has full control of the data model. The bank defines per-client positions, token identifiers, fee types and network costs in its own terms.
  • +Any custody software can run underneath, and changing that software leaves the client register in place
  • +Statements, tax data and supervisory reporting come from one place the bank owns
Trade-offs
  • −The subledger is the most to build and the most to run. The ledger must distinguish each client's assets at any time and needs its own controls, audit trail and resilience testing.
  • −The bank sets its accounting policy with its auditor. The 2019 IFRS agenda decision on crypto covers a firm's own holdings and says nothing on assets held for clients.
  • −The subledger duplicates functions that a native connector or provider ledger already supplies, so it pays only with own custody or several custodians
  • −The subledger needs core banking, ledger and blockchain engineers working together through every release

A custom subledger keeps client crypto positions in a ledger that the bank owns, next to or inside its core. The subledger posts aggregated entries to the general ledger. A custom subledger is the natural fit for a bank that holds the keys itself. BBVA said in March 2025 that it will utilize its own cryptographic key custody platform for its Spanish retail service. BBVA does not publish how its ledger is built.

MiCA and its record-keeping rules set what the subledger must do. MiCA requires the register of positions per client, movements recorded "as soon as possible", client crypto held separately from the firm's own on the distributed ledger, and a statement of position at least every three months (Article 75). The record-keeping rules also require records that let the firm distinguish each client's assets "at any time and without delay" (Delegated Regulation (EU) 2025/1140, Article 5). The accounting side has less guidance. The IFRS Interpretations Committee's June 2019 decision puts a firm's own cryptocurrency under IAS 2 or IAS 38. The committee's decision does not address crypto held for clients.

Landscape

Which core banking systems have a published custody or crypto link?

TemenosTaurus (custody); Wyden (trading, proof of concept); Fireblocks and Dfns listedReal-time position booking, fee management, reconciliation, reporting in securities workflows (Taurus); FIX 4.4 order and execution flow (Wyden)Temenos and Taurus, 2021 to 2025
AvaloqOwn Crypto Assets solution; Fireblocks custody technology at ZKBCrypto positions alongside other asset classes; trading, settlement and custodyAvaloq, Jan 2022 and Sep 2024
Avaloq SaaSSygnum API at BancaStatoBuy, hold and sell crypto without a separate order management systemfinews, Jul 2026
finnovaWyden; Standard API for crypto settlementsStandardised connection for crypto settlement partnersWyden, Mar 2023

The entries in this table were read on vendor sites on 5 November 2026. "Published" means the core vendor or the custody vendor describes the link. The word says nothing about which release or region the link covers. FIS's digital-money platform, which runs beside the core, is listed under "also consider".

Verdict

Which pattern fits your bank?

If your priority is
Your core and custodian are a listed pair

you run Temenos with Taurus, or Avaloq with its Crypto Assets solution, and the published scope covers the assets and services you plan. A native connector beats a custom layer on build and on systems to run. Check the connector release against your core release before you plan anything else.

→Native connector
If your priority is
Least build, provider as custodian

a licensed provider will hold custody and keep the client register, and the bank needs positions in its own app and statements. The provider ledger needs the least build of the four patterns. Accept that leaving the provider later means a client migration.

→Provider ledger
If your priority is
No listed connector, or more than one custodian

your core has no connector for the custodian you chose, you plan a second custodian or chain, or you need ISO 20022 statements and booking rules you control, and you can give the layer an operations owner.

→Integration layer
If your priority is
The bank holds the keys itself

the bank is custodian of record under MiCA (Article 75), wants the per-client register in its own stack, independent of the custody software underneath, and can fund a ledger team for the long run.

→Own subledger
If your priority is
Stablecoin issuance or redemption for clients

you mint, redeem or move e-money tokens for clients. None of the native connectors we checked says it covers EMTs. So the booking rules for mint, redeem and network fees are kept in your own layer or ledger.

→Integration layer or own subledger
Also consider

What sits next to the core, and where do the rules come from?

  • Digital-money platforms beside the core: FIS launched Lyriq in April 2026, "production-ready and entering limited availability", for tokenized deposits and stablecoins. The platform "integrates with existing core banking systems regardless of provider". Lyriq is a platform for issuing and moving digital money. The booking of Lyriq's activity still follows one of the four patterns in this guide.
  • DORA register and exit: every pattern adds entries to the register of information required under DORA Article 28(3). The register follows the templates of Implementing Regulation (EU) 2024/2956, and those templates identify providers by LEI or EUID. For services that support critical or important functions, DORA requires tested exit strategies (Article 28(8)). For the same services, the contract must include a mandatory transition period (Article 30(3)). Our DORA third-party risk guide explains how each provider type is classified.
  • Crypto accounting subledgers: tools such as Bitwave and Cryptio connect to ERP systems such as NetSuite and are aimed at a firm's finance team. Neither the Bitwave nor the Cryptio integrations page lists a core banking system or a per-client custody register.
  • Blueprint: the bank crypto-in-app blueprint sets out the full build for a retail bank that adds crypto trading and custody to its app. The blueprint includes the core banking link that this guide compares.

FAQ

What is custody to core banking integration?
Custody to core banking integration books what a crypto custody or stablecoin platform records in a bank's core banking system and general ledger, and reconciles the two. Those records are client positions, deposits, withdrawals, fees and network costs. Vendor and bank announcements show four patterns: a native core banking connector, a provider's ledger, an integration layer, or a subledger the bank builds itself.
How does a bank connect a crypto custody platform to its core banking system?

A bank connects crypto custody to core banking in one of four ways. The first is a connector that the core banking vendor lists or ships, for example Taurus in Temenos or Avaloq's Crypto Assets solution. The second is a crypto-as-a-service provider that keeps the per-client ledger, while the bank books an omnibus position and fees. The third is an integration layer that turns the custodian's events into core postings and general ledger entries. The fourth is a subledger the bank builds to hold client positions itself.

The choice of route decides which system is the book of record for client crypto and who reconciles against whom. The choice also decides how hard it is to change custodian later. Temenos describes its Taurus integration as "real-time position booking, fee management, reconciliation, and reporting".

Does Temenos, Avaloq or FIS offer its own crypto custody?
None of the core banking vendors we checked on 5 November 2026 supplies its own custody technology. Temenos describes a digital asset solution inside its securities processing, which is pre-integrated with Taurus for custody. Temenos also lists Fireblocks and Dfns as solution providers and has shown trading through Wyden in a proof of concept. Avaloq has its own Crypto Assets solution and uses custody technology from Fireblocks, as it does at Zürcher Kantonalbank. FIS announced its digital-money platform, Lyriq, in April 2026 for tokenized deposits and stablecoins. Lyriq was then "entering limited availability".
Where are client crypto positions booked when a bank uses a crypto-as-a-service provider?

When a licensed crypto-as-a-service provider holds custody, the provider's ledger keeps the per-client register of positions that MiCA requires of the custodian (Article 75(2)). The bank books what it needs on its side: an omnibus or per-client mirror of positions, the fiat legs and its own fees.

The split between provider and bank depends on the provider and on whose license is used. Paxos, for example, documents an omnibus model and a per-user subledger model. Paxos typically offers the omnibus model only where the partner relies on its own licensing. In that case the partner's ledger records each client's balance. The bank still reconciles its bookings against the provider's reports.

Does MiCA require daily reconciliation of client crypto?

MiCA and its record-keeping standards set no reconciliation frequency. MiCA requires a register of positions per client, and movements must be recorded "as soon as possible" (Article 75). Under the same article, client crypto must be held separately from the firm's own on the distributed ledger. A statement of position is due at least every three months. Delegated Regulation (EU) 2025/1140 requires records that distinguish each client's assets "at any time and without delay".

The bank sets in its own controls how often the client register is matched against the custodian and the chain. The stablecoin reconciliation guide compares tools and routes for matching stablecoin movements to the ledger.

How are blockchain network fees booked in the general ledger?

Network fees are booked from the custody platform's transaction data or from the provider's invoice. Fees from transaction data are booked in the token that paid them. Fees from an invoice are booked in the invoice currency. Fireblocks reports network fees per transaction in feeInfo.networkFee, with a feeCurrency such as ETH for ERC-20 tokens. So the fee on a transfer of a euro stablecoin can be in another asset.

Circle Mint invoices network fees on outgoing transfers, converted to USD at the time of the transfer. Circle Mint sends the invoice in the first five business days of the following month, so the cost is accrued at transfer and settled later.

Is there an ISO 20022 message for on-chain transfers?

No ISO 20022 mapping for on-chain transfers is settled across custody vendors. The one primary example we found is Circle Mint's camt.053.001.13 daily statement, which reports USDC and EURC activity. On on-chain entries, the statement gives the blockchain and transaction hash. The statement reports USDC amounts under the currency code USD and puts the token name in supplementary data.

The fiat side of a crypto service already runs on ISO 20022. T2, the Eurosystem's RTGS system, moved to ISO 20022 on 20 March 2023. SEPA credit transfers and direct debits must use ISO 20022 XML (Regulation (EU) No 260/2012). An integration layer usually maps custody events into the statement formats the core already reads.

What does DORA require when a bank connects custody to core banking?

DORA requires the bank to record every contractual arrangement for ICT services from third parties in its register of information (Article 28(3)). The register follows the templates of Implementing Regulation (EU) 2024/2956. Where the service supports a critical or important function, the bank must also have a tested exit strategy (Article 28(8)). The contract for such a service must contain the Article 30 terms, including a transition period.

A native connector usually adds the core and custody vendors as third-party providers. An integration layer run by an outside firm adds that firm. A custom subledger built in-house adds no provider of its own. Our DORA third-party risk guide classifies providers by type.

Can a bank change custody provider without re-integrating its core?

A bank can change custody provider without touching its core booking when it keeps its client register and booking rules outside the custody link. The bank can keep them in an integration layer or in its own subledger. The new custodian then needs a new adapter and a migration of wallets, but client positions are not moved.

With a native connector, a change of custodian depends on whether the core vendor offers a connector for the new custodian. With a provider ledger, every client position and its history moves to the new provider. DORA asks for exit strategies that are tested (Article 28(8)), so the route out is part of choosing the pattern.

Build it

Protofire builds the layer between a custody or stablecoin platform and core banking. The layer consists of event intake from the custodian, booking rules for client positions, fees and network costs, ISO 20022 statement mapping, the reconciliation job and its break queue, and a tested switch to a second custodian.

Custody and crypto-as-a-service integration with core banking →

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.