Northern Trust is developing tokenized-asset custody and servicing capabilities on Canton, but institutions needing deployable digital-asset custody today should compare regulated specialists such as Anchorage Digital, Zodia Custody and Komainu. The right alternative depends on jurisdiction, legal custody model, API depth, reporting, asset coverage, settlement connectivity and whether the buyer needs direct custody or white-label infrastructure.
Short answer
Northern Trust is extending its traditional asset-servicing model into tokenized assets, including announced development work on the Canton Network. That makes it relevant to institutions that want digital assets alongside an established custody and servicing relationship.
It does not remove the need to compare deployable specialist options. Anchorage Digital, Zodia Custody and Komainu are three credible alternatives or complementary providers, but each has a different public product surface, regulatory footprint and operating model.
The procurement question is not simply, "Who holds the keys?" It is whether the provider can support the buyer's legal custody model, account hierarchy, approval policy, asset and chain set, reporting obligations, settlement workflow and exit plan.
Northern Trust's current position
Northern Trust announced in April 2026 that it had entered an agreement with Digital Asset to develop custody capabilities for tokenized financial assets on Canton. The announcement describes custody and asset servicing for tokenized assets and integration with Northern Trust's core servicing infrastructure.
That is strategically important, but an announcement is not the same as a production service available for every asset, client type and jurisdiction. An RFP should separate:
- available production capabilities;
- controlled pilot capabilities;
- roadmap items;
- Canton-specific functions;
- broader cryptoasset custody;
- traditional servicing functions connected to the digital position.
Comparison at a glance
| Decision area | Northern Trust | Anchorage Digital | Zodia Custody | Komainu |
|---|---|---|---|---|
| Natural starting point | Existing institutional servicing relationships and tokenized-asset workflows | US institutions needing regulated custody and documented platform APIs | Financial institutions needing regulated custody, off-venue settlement or white-label capability | Institutions seeking regulated custody, settlement connectivity and collateral or staking services |
| Public evidence reviewed | Canton custody development and digital asset-servicing strategy | Custody platform, developer APIs, subaccounts, statements and tax-data documentation | Custody, Interchange, Gateway and white-label Solutions materials | Custody, Connect, CORE and regulatory materials |
| API and reporting diligence | Confirm production scope and interfaces | Strong public documentation for permissions, balances, transactions, subaccounts and statements | Confirm APIs, reports and data export for the chosen service and entity | Confirm integration depth, reporting and operating model for the chosen entity |
| Main watch-out | Do not treat announced development as universally available production capability | Distinguish Anchorage Digital Bank, platform capabilities and product-specific account models | Availability varies by jurisdiction, asset and contracted service | Entity, jurisdiction and product scope must be matched to the mandate |
This table is a procurement orientation, not a score or endorsement. Contracting entities, products and availability change.
Anchorage Digital
Anchorage Digital is a natural candidate for US institutions that want regulated custody within a broader institutional platform. Its public custody materials emphasize segregated custody, transaction approvals, staking and governance participation.
Its developer documentation is especially useful during early diligence. Public guides cover API permissions, vault operations, balances and transaction history, while wealth-management documentation covers end-client onboarding, subaccounts, fee handling, statements and tax data.
Best fit when: the buyer wants a US regulated custody relationship, programmatic operations and evidence that specific account and reporting workflows can be integrated.
Test carefully: which capabilities apply to the exact product and legal entity, how approval quorums interact with API permissions, supported assets in production, statement identifiers, tax-lot responsibilities and export on termination.
Zodia Custody
Zodia Custody positions itself as digital asset infrastructure for financial institutions. Its public product set includes custody, Interchange for off-venue settlement, Gateway access to additional services and Solutions for institutions that want to offer custody under their own brand.
The white-label model is a meaningful distinction. A bank or wealth platform may want to keep its own client experience while using specialist custody technology and operations underneath. That model creates additional diligence around responsibility boundaries, data sovereignty, client disclosures, service branding and incident communications.
Best fit when: a financial institution needs regulated custody, off-venue settlement or a white-label route to market.
Test carefully: contracting entity and jurisdiction, role and approval configuration, 24/7 withdrawal operations, report and API coverage, asset onboarding, data location and the ability to migrate records and wallets.
Komainu
Komainu serves institutional digital asset custody and related workflows. Its public materials present regulated custody alongside Komainu Connect for off-exchange settlement, Komainu CORE and services that can include staking and collateral management.
The attraction for some buyers is the combination of custody with market access and collateral workflows. Those connections also need strict separation of duties: custody, trading venue, settlement instruction, collateral control and valuation should not become one opaque process.
Best fit when: the mandate combines regulated custody with settlement connectivity, collateral or staking requirements.
Test carefully: the regulated entity serving the client, asset and jurisdiction coverage, approval and recovery controls, settlement-finality evidence, collateral rights, statements and incident ownership.
API requirements that matter
A long endpoint list is not evidence of an operable custody integration. Require a controlled demonstration of these workflows:
- Account and subaccount creation. Can internal client and portfolio identifiers remain stable across onboarding, custody and reporting?
- Address and asset management. How are deposit addresses created, attributed and monitored? What changes when a network or token migrates?
- Transaction initiation and approval. Which permissions can propose, approve, cancel or retrieve a transfer? Can policy be enforced consistently across UI and API?
- Idempotency and ambiguous outcomes. What happens when the client times out after submitting a withdrawal? A retry must not create a duplicate movement.
- Events and reconciliation. Do webhooks and transaction states distinguish requested, approved, broadcast, confirmed, settled, rejected and reversed operations?
- Statements and exports. Can the buyer obtain human-readable statements and machine-readable records with the same identifiers?
- Audit evidence. Are policy changes, approvals, failed attempts and administrative actions exportable?
- Exit. Can balances, history, wallet mappings, tax lots and configuration be exported without screen scraping?
Reporting requirements
Institutional reporting should connect the custody record to the books and to the people accountable for the mandate. At minimum, ask for:
- opening and closing balances by account, asset and network;
- complete transaction history with network references;
- pending and failed transactions;
- fees, staking rewards and other asset events;
- approval and policy-change history;
- valuation source and timestamp where fiat values are shown;
- statements for legal account holders;
- cost-basis or tax-data responsibilities, where applicable;
- bulk exports and API access;
- reconciliation support and correction procedures.
A dashboard is not a reporting strategy if its records cannot be exported, reconciled and retained independently.
RFP questions
- Which legal entity will contract with us and which regulator supervises the relevant service?
- Is the arrangement legal custody, custody technology, sub-custody or a combination?
- How are client assets segregated in systems, books and legal documentation?
- Who can initiate, approve and execute a withdrawal?
- What is the recovery process if our authorized users are unavailable or compromised?
- Which assets and networks are supported by the contracted entity today?
- Which API functions and reports are production-ready for our account model?
- How are forks, airdrops, token migrations and chain incidents handled?
- What evidence is available for security controls, penetration testing and service continuity?
- What insurance applies, and what is excluded?
- What are the service levels for withdrawals, incidents, asset onboarding and support?
- How do we export data and transfer assets if the relationship ends?
Recommendation
Keep Northern Trust on the shortlist when the desired future state is integrated traditional and tokenized asset servicing, particularly where the existing institutional relationship matters. Compare specialist providers in parallel when production timing, cryptoasset breadth, APIs, white-label delivery or 24/7 digital operations are central.
Do not choose from brand familiarity alone. Run the same difficult workflow with each finalist: onboard an account, receive an asset, apply an approval policy, attempt a prohibited withdrawal, complete an approved transfer, reconcile the statement and export the full record.
Primary sources
- Northern Trust: tokenized asset custody capabilities on Canton
- Anchorage Digital custody platform
- Anchorage Digital developer documentation
- Anchorage Digital statements and reporting
- Anchorage Digital subaccount tax data
- Zodia Custody
- Zodia Solutions
- Komainu
- Komainu regulation overview
FAQ
What are the best Northern Trust alternatives for digital asset custody?
Anchorage Digital, Zodia Custody and Komainu are credible starting points for institutional buyers, but they are not interchangeable. Compare the exact regulated entity, supported assets and jurisdictions, account structure, API operations, reporting and recovery model required by the mandate.
Does Northern Trust already offer tokenized-asset custody?
Northern Trust announced in April 2026 that it is developing custody and asset-servicing capabilities for tokenized financial assets on the Canton Network. Buyers should verify current production availability and scope directly.
Which alternative has the clearest public API evidence?
Anchorage Digital publishes detailed developer documentation covering custody operations, subaccounts, permissions, statements and tax data. Public documentation depth is useful, but a proof of concept and contractual commitments are still required.
Can a specialist custodian replace a traditional asset servicer?
Not automatically. Custody, fund accounting, transfer agency, tax reporting, corporate actions and investment reporting are separate responsibilities. Map every required function before replacing or supplementing an incumbent.
What reporting should an institutional custody RFP require?
Require balances, transactions, fees, statements, tax-lot or cost-basis support where relevant, approval history, exception records and exportable data identifiers that reconcile to internal books.
Should a bank choose white-label custody or direct custody?
Direct custody may reduce implementation scope, while white-label infrastructure can preserve the bank's client experience and operating control. The correct model depends on licensing, governance, data location, staffing and time to market.
Are custody insurance claims enough for approval?
No. Obtain the current policy or evidence of cover, limits, exclusions, named insureds, deductibles and claims process. Insurance does not replace segregation, governance, recovery or financial due diligence.
How should buyers test custody APIs?
Test account creation, deposits, policy approvals, withdrawals, ambiguous retries, webhooks, statements, reconciliation, permission changes, emergency recovery and complete data export in a sandbox and controlled production pilot.
Build an evidence-based custody shortlist
Compare institutional custodians by jurisdiction, operating model, API requirements, asset coverage and reporting workflow.