Avaloq Crypto Integration for Private Banks That Add a Crypto Provider
Avaloq ships crypto trading and custody, and banks decide who holds keys and executes orders. Protofire builds the provider link, posting rules and daily match that this decision leaves to them. Lido's grants organisation funded Protofire to deploy Safe on the Holesky testnet in 2023 and on Hoodi in 2025.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What Avaloq covers and what the bank decides
Avaloq offers crypto on its core platform, and each bank still chooses the setup around it. Avaloq's core platform trading page says Avaloq fully integrates crypto asset trading, settlement and custody (Avaloq). Banks that run Avaloq have also integrated a custody vendor's platform on it or connected an outside provider's API to the core. In an Avaloq crypto integration, Protofire builds the bank's own part of that setup.
Avaloq leaves the choice of route to the bank. Avaloq's integration page says Avaloq helps a bank decide "where it makes most sense to partner or to build in-house" (Avaloq). So the bank decides who holds the keys and who executes client orders. The bank also decides who builds the link between an outside provider and its Avaloq bookings.
On a provider route, the bank's part is a link with posting rules. Protofire's services send orders from Avaloq e-banking to the provider and post each fill and transfer once in the core. The same services check transfers against the bank's verified client wallets and match positions each day. Without such a link, operations staff key each provider fill and transfer into Avaloq by hand.
Who runs each part of crypto on an Avaloq core
Avaloq provides the core and its crypto functions. The bank picks the custody model and the providers, and Protofire builds the links and checks that the bank owns.
Core and e-banking
Crypto functions
Custody and execution
Provider link and postings
Wallet checks and daily match
Four routes to crypto on Avaloq and the work each leaves
Banks on Avaloq have published different routes to crypto, and each route leaves different work to the bank.
Avaloq's own crypto functions
Published example: Avaloq's release of 6 September 2024 says it rolled out its digital asset platform at Zürcher Kantonalbank. ZKB's own release says clients' crypto holdings appear in their existing custody-account view.
Left to the bank: The broker that executes orders, and the KYT tool. Avaloq's ecosystem lists Crystal Intelligence's crypto AML and KYT platform and Lukka's AML platform as separate entries.
Protofire builds on this route: A daily match of Avaloq positions with the chain, and checks against verified client wallets, where the bank wants them.
A custody vendor's platform integrated on Avaloq's platform
Published example: BBVA's December 2023 release calls Metaco's Harmonize "fully integrated as a software as a service (SaaS) on Avaloq's Crypto Assets platform and Core Banking system".
Left to the bank: The choice of custody vendor, the contract with that vendor and the vendor's own setup.
Protofire builds on this route: A daily match of the custody platform's records with Avaloq positions and the chain.
A provider's API connected to the Avaloq core
Published example: Sygnum's release of 23 July 2026 says BancaStato "has connected Sygnum's API with Avaloq's core banking system and digital banking channels".
Left to the bank: The connection itself: order routing from e-banking, postings in the core and the match with the provider.
Protofire builds on this route: Order routing to the provider's API, one posting per fill or transfer, booking dates for weekend events and the daily match.
Keys the bank holds itself
Published example: ZKB's release of 4 September 2024 says ZKB takes on the safekeeping of the private keys and has client orders traded through Crypto Finance AG.
Left to the bank: Key safekeeping, approval of outgoing transfers and the custody setup, run by the bank's own staff.
Protofire builds on this route: The register of verified client wallets, and a daily match of Avaloq positions with the bank's own wallets on chain.
What an Avaloq crypto integration adds to your bank's systems
On a provider route, client orders, fills and transfers reach your Avaloq books without retyping.
Each provider fill posts once in Avaloq
A client order from Avaloq e-banking reaches the provider, and its fill appears in the core as one posting. A repeated provider event adds nothing. Protofire's posting service keys each posting on the provider's order or transfer ID, and reads the provider's record after a lost reply before any retry.
Weekend transfers get the booking date your Avaloq team sets
A transfer that the chain confirms on a Sunday gets the booking date your Avaloq team agreed in advance. Protofire's service holds events that arrive outside your bank's booking day and posts them with that date.
Transfers checked against verified client wallets
Each transfer to or from a client wallet passes your compliance rules before the posting service books it. For banks that FINMA supervises, FINMA's guidance of 26 August 2019 set a practice on verified client wallets (FINMA). FINMA wrote that the practice applies as long as information about the sender and recipient cannot be transmitted reliably in the payment system. Your compliance team decides how the practice applies to your bank today. Protofire's service checks each transfer request and deposit against your register of verified client wallets.
Avaloq positions matched daily with the custodian and the chain
Each morning, your staff see whether Avaloq positions agree with the custodian's statement and with the chain. Each break goes to a named owner in operations or finance. Protofire's match job reads the three sources at a cut-off block and time that your finance team sets, and marks a source that reports late.
Test runs before each Avaloq or provider release
Your Avaloq team sees test results for the crypto connection before a new Avaloq release or provider API version goes live. Protofire builds the posting, wallet and match tests as a suite that your team reruns in your test environment before each release.
Institutions supervised by FINMA are only permitted to send cryptocurrencies or other tokens to external wallets belonging to their own customers whose identity has already been verified and are only allowed to receive cryptocurrencies or tokens from such customers.
What Avaloq's public pages say about its platform and crypto
- Client channels
- Avaloq says clients can "trade and transfer crypto assets via web or mobile banking" (Avaloq).
- Staff tools
- Avaloq's trading page describes a web-based workbench that lets staff "trade on behalf of clients, handle compliance tasks, and manage operational risks".
- Custody technology
- Avaloq's ecosystem lists Fireblocks in its "Crypto Assets" category as "Embedded" (Avaloq).
- Deployment
- Avaloq offers its core platform as SaaS Go, "a ready out-of-the-box solution", and as SaaS, platform as a service or on premises (Avaloq).
- Interfaces
- Avaloq names "Avaloq system APIs and Open Banking standard APIs such as PSD2 and Open Wealth", plus data streaming and standard adapters (Avaloq).
- Trading connectivity
- Avaloq's trading page says banks connect to trading systems, exchanges and brokers "via standard protocols, including ISO 20022 and FIX protocol, as well as APIs".
Protofire read these facts on 17 November 2026 on Avaloq's public product pages and its ecosystem listing.
Our record: Safe deployed and maintained under Lido grants
Lido's grants organisation (LEGO) funded Protofire to deploy Safe on the Holesky testnet in 2023 and on Hoodi in 2025.LEGO has renewed the maintenance grant every half-year through Q4 2026. An Avaloq connection also needs upkeep after launch. Avaloq and the provider each publish new releases. Protofire's Safe multisig deployment page describes the Safe service.
From the bank's route to a live Avaloq connection
- Step 1
Your team names its route, provider and Avaloq setup
Your team sends the route it chose, the provider or custody vendor, and that vendor's API documentation. It also names your Avaloq release and whether your bank runs Avaloq as SaaS or on premises. A Protofire engineer then maps each order, fill, transfer and fee to the booking your Avaloq team expects. - Step 2
Your Avaloq team decides how the core books each event
Your Avaloq team sets the booking for each event type, including the date for events outside your bank's booking day. Protofire writes the posting rules from those decisions. The same team makes any configuration change in the core. - Step 3
Protofire builds against test systems on both sides
Protofire builds the order link, the posting service, the wallet check and the daily match. The build runs against the provider's test environment and your bank's Avaloq test system. - Step 4
A test run with a lost reply and a Sunday transfer
The test plan includes an order whose reply is lost, an event that arrives twice and a transfer confirmed on a Sunday. The run passes when each case ends in one posting and a match with no break. - Step 5
Your staff switch the connection on in production
Your staff move the connection to production. Your bank owns the code, configuration and runbooks. From then on, your team runs the connection itself or hands its operation to Protofire under a written scope (managed onchain operations).
How work with Protofire starts
Protofire works from the Avaloq documentation that your bank's own Avaloq license opens to your team.The connection calls Avaloq and the provider under credentials that your staff issue and keep in your bank's vault. A scope under which Protofire operates a service lists every write call that the service makes.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
Avaloq work that belongs with another team
Three kinds of Avaloq project need a different team or a smaller build.
- Avaloq's crypto functions already cover your assets and channels. Avaloq and the custody technology it embeds then deliver the service. Protofire adds an independent match with the chain only where your bank asks for one.
- The work is the Avaloq core itself. Parameterization, upgrades and migrations of the core belong to Avaloq and your bank's Avaloq team.
- Your volumes are at pilot level. At that volume, staff can book a daily provider statement by hand.
Protofire holds no banking license or client assets and gives no legal or accounting opinion. After launch, Protofire holds no key, credential or admin role in your Avaloq environment or at your custody platform.
FAQ
What is an Avaloq crypto integration?
Do Avaloq's crypto functions require an Avaloq SaaS core?
Can a bank connect a crypto provider to Avaloq without an order management system?
Who holds the clients' crypto when a bank on Avaloq uses an outside provider?
Which crypto assets can a bank offer on Avaloq?
Who can build an Avaloq crypto integration for a private bank?
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.
