Zodia Custody Integration for Funds, Trading Firms and Banks
Zodia Custody runs custody and signing for funds, trading firms and banks. Each firm still needs signed service requests, an event feed within rate limits, and transfers and settlements booked in its ledger. Protofire builds all three. We helped build the Gnosis Safe web app from 2019 to 2021.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Zodia Custody service requests need a maker and a checker
After you choose Zodia Custody, your Zodia Custody integration has to get each transfer signed by your maker and approved by your checker. Then the transfer has to reach your ledger.
Zodia Custody takes a wallet, an address, a transfer or a staking instruction as a service request. One API user creates the request as maker and signs it with an ECC key. A second API user approves the request as checker (Zodia Custody). Three things are on your side: who plays each role, how a status reaches your books and what a late answer costs.
A Zodia Custody service request, from order system to ledger
Each request leaves the order system and waits for the firm's maker and checker. It returns as notifications and reads that the booking job posts.
Ledger and order systems
Keys and roles
Service desk API
Wallets and notifications
Request service
Event feed and gap reads
Booking, matching and mapping
Zodia Custody rate limits and approval timeouts
A ledger that polls one Zodia Custody endpoint every ten minutes needs 144 calls a day, but the endpoint allows 128.By default, each Zodia Custody endpoint answers 1 request a second and 128 a day. Above that, the API returns HTTP 429 (Zodia Custody). So the polling ledger passes the limit before the day is out, and its later reads return 429.
Zodia Custody's approval window is shorter still. The maker has 120 seconds to confirm after submission, and a request that nobody approves in the allocated time expires (Zodia Custody). A missed window ends as a CONFIRMATION TIMEOUT or an APPROVAL TIMEOUT. The timeout then has to reach the order that raised it. If both are left to a script written in launch week, a transfer can end up missing from the ledger.
Zodia Custody facts we build against
- EU entity
- Zodia Custody (Europe) S.A. is based in Luxembourg. The CSSF authorized it on 12 December 2025 for custody and transfer of crypto-assets, for all 30 EEA states (ESMA register).
- Interchange
- Zodia Custody's release of 14 September 2026 says that "Interchange is supported by Zodia Custody Limited (UK)" (Zodia Custody).
- Notifications
- Zodia Custody posts notifications to a REST callback or by JMS, with payloads encrypted and signed. They cover beneficiary, crypto address, wallet, transfer and validator events (Zodia Custody). Service requests and Interchange settlements are not on that list.
- Staking
- ETH staking runs through Bitwise, Twinstake, Blockdaemon, Figment, Galaxy and Pier Two (Zodia Custody).
Checked November 2026 against Zodia Custody's documentation and ESMA's CASP register. Protofire integrates Zodia Custody for firms that have chosen it.
What Protofire delivers in a Zodia Custody integration
Service requests signed within the 120-second window
Your maker signs inside the 120 seconds. Your checker then approves. A timeout returns to the order that raised it, with its status. Protofire builds the request service, which puts your own end-to-end ID on each request. The service searches on that ID before a second create, because a timed-out call does not say whether the first one exists (Zodia Custody).
Private keys kept in your own key store
You keep your RSA and ECC private keys in your HSM or vault, and Zodia Custody receives the public halves. Protofire writes the ceremony script that your custodians run. We also write a signing service in your environment that returns signatures, not keys. A system checker runs apart from the request service under its own key, so no single service holds both keys.
Ledger kept current within the daily limit
Protofire's event feed books each verified notification from its own payload. Reads fill the gaps and cover the states that have no notification. A counter per endpoint stops the reads below the daily limit. Until Zodia Custody confirms how it redelivers missed notifications, one daily read of all your wallets catches what an outage missed.
Transfers posted once per wallet and matched at your close
A transfer posts once per wallet and direction on its Transaction ID. So a move between two of your wallets posts one leg on each. Amounts arrive in the smallest unit, and token fees arrive in the native coin (Zodia Custody). So Protofire converts by currency and books a separate fee leg. A client is credited when the transfer reaches UNLOCKED. Zodia Custody gives that status to an approved incoming transfer (Zodia Custody). Balances are read when your day closes, and UTC timestamps are cut to your business day.
Interchange settlement lines matched to the desk's fills
An Interchange instruction holds gross lines and net lines, and PAY points in opposite directions on the two. On a gross line the counterparty sends, and on a net line the exchange sends (Zodia Custody). So Protofire's posting rule reads the line type before the direction. The mapper ties lines to your fills by the venue's reference. Rejected and failed settlements go to separate break lists.
Staking rows posted by reward type
Zodia Custody's staking report lists protocolRewards, txFeeRewards and mevRewards per validator (Zodia Custody). Protofire maps each reward type into a posting that your finance team signs off.
What Zodia Custody does and what your firm supplies
Zodia Custody runs custody and signing.Your firm holds the keys and meets the approval window, and it plans its reads within the daily limit. Sources: authentication, rate limits, transfer and Interchange statuses.
Keys
What Zodia Custody does: Takes the company RSA public key and, per API user, an email, an ECC public key and a role: Viewer, Maker or Checker.
What the firm supplies or builds: The private keys, and the decision on which person or service holds each role.
Approval window
What Zodia Custody does: Gives the maker 120 seconds to confirm, and expires a request that is not approved in time.
What the firm supplies or builds: A maker step that signs inside the window, checkers on hand, and an alert on each timeout.
Volume
What Zodia Custody does: Allows 128 requests a day per endpoint, raised for specific endpoints on request.
What the firm supplies or builds: A callback endpoint or JMS broker, set up through Zodia Custody customer service, and a planned number of reads per endpoint.
Incoming funds
What Zodia Custody does: Holds an incoming transfer in PENDING_UNLOCK until system approval, and in UNDER INVESTIGATION while it reviews the transfer.
What the firm supplies or builds: The rule for when a client is credited, and a suspense line for transfers under investigation.
Interchange
What Zodia Custody does: Opens a settlement wallet per venue and reports settlement statuses from received to complete.
What the firm supplies or builds: A direct trading relationship with each venue, the approval mode, and the map from settlement lines to fills.
Our record: a migration blueprint and the Gnosis Safe web app
Protofire's record consists of a published blueprint on custody migration and the Gnosis Safe web app that we helped build.The record applies here because the blueprint covers reconciling a client book across a custodian change.
A custody migration blueprint
Protofire's Lapsed VASP Migration blueprint names Zodia Custody Europe, the group's Luxembourg entity, among the CASPs a firm can move its client book to. The blueprint also covers the cutover reconciliation. Our MiCA migration service moves an existing client book to a MiCA-authorized custodian, including the cutover match.
The Gnosis Safe web app
Protofire engineers helped build the Gnosis Safe web app from 2019 to 2021, working with the Gnosis Safe team.
Project steps, from role plan to operation
- Step 1
A role plan comes before the first key
Your authority matrix sets who plays Viewer, Maker and Checker before the first key is made. Your firm then generates the keys in your HSM. - Step 2
Sandbox testing comes before production keys
Zodia Custody's sandbox runs testnets such as Sepolia, Stellar Testnet and Bitcoin Testnet (Zodia Custody). The same maker and checker steps apply in the sandbox. So the key store, the request service and the timeout handling are tested before production keys exist. - Step 3
The request service and the event feed go live first
Booking and the daily match go live with the request service and the event feed. Interchange and staking follow. - Step 4
Who runs the integration after launch
The request service and a system checker run in your environment. They act only on orders that your staff recorded or on rules that your firm signed. Your team runs the integration. Alternatively, Protofire may run only the read-only services under a written scope: the event feed, the daily match and reports.
What Protofire needs to start
You start by sending Protofire your Zodia Custody wallet layout, Interchange venues and staking chains.You also send your ledger and cut-off. Protofire's first written proposal maps the request service, the event feed and the posting rules onto that setup.
- 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.
Four cases where Zodia Custody's own products or screens are enough
- You are a bank that wants the keys and the custody stack in its own environment. Zodia Solutions covers that case. "Institutions deploy Zodia Solutions into their preferred cloud environment and connect their own key management system" (Zodia Custody). Protofire's bank custody platforms guide compares such platforms.
- You run TCS BaNCS. With Zodia Solutions, TCS BaNCS manages the transaction lifecycle, from order instruction to delivery and reconciliation (Zodia Custody, 23 July 2026).
- You move assets a few times a month. The platform's own screens cover those operations. Zodia Custody's staking guide describes unstaking in the platform UI.
- You serve retail clients. Zodia Custody's services are "exclusively available to institutional investors" (Zodia Custody).
Protofire holds no custody or crypto-asset license.
FAQ
What is a Zodia Custody integration?
Who can build a Zodia Custody integration for a fund or a bank?
Who holds the keys that sign Zodia Custody API calls?
How does a Zodia Custody integration keep the ledger current at 128 requests a day per endpoint?
What is the difference between a rejected and a failed Interchange settlement?
Which Zodia Custody entity should an EU firm check?
Where does Protofire appear in our DORA register of information?
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.
