The transfer agent is the regulated function that tokenisation operators reach for when they need the on-chain share register to be the legally operative one. In the US under the Securities Exchange Act §17A, in Delaware corporate law, and in adjacent state-law treatments of beneficial ownership, the transfer agent is the legal record-keeper of share ownership for a registered security. Without that designation in the chain of legal recordkeeping, an on-chain token representing a fund interest is a representation of an off-chain register held elsewhere; with it, the on-chain entry is the operative record. For a tokenisation product team picking a US fund wrapper, the transfer-agent question is the load-bearing structural choice that determines what the on-chain instrument legally is. This page maps why the role exists, how Securitize and adjacent platforms discharge it, what changes when the transfer agent and the platform are the same entity, and the European parallel under the DLT Pilot Regime.
Why the role exists
The transfer agent function is mid-twentieth-century US securities-law infrastructure that the tokenisation cycle has had to either route around or absorb. The Securities Exchange Act §17A, originally enacted to address the back-office crisis of the late 1960s, requires that any entity acting as a transfer agent for an SEC-registered security be itself registered with the SEC (or the appropriate banking regulator for bank-affiliated transfer agents). The transfer-agent registration carries a defined set of recordkeeping, customer-protection, and operational-resilience obligations under SEC Rule 17Ad-1 through 17Ad-17.
The legal function the transfer agent performs is the maintenance of the issuer's record of beneficial ownership for the specific security. Issuers of registered securities (mutual funds, certain ETFs, and private fund vehicles where transfer-agent appointment is required by the offering documents) are legally required to maintain the record through a registered transfer agent. The transfer agent processes share transfers, maintains the register, handles dividend distributions, and serves as the issuer's record-keeper for SEC examination purposes.
In the conventional pre-tokenisation US securities market, transfer agents are typically large administrative firms (Computershare, EQ, Equiniti, the in-house transfer-agency teams at large fund administrators) operating off-chain registers maintained on conventional databases. The function is invisible to most market participants because the holder rarely interacts directly with it: a holder buys a fund share through a broker, the broker holds the share at DTC in street name, and the transfer agent's register reflects DTC as the holder of record on behalf of the broker, who in turn reflects the customer as beneficial owner on the broker's own books.
The tokenisation challenge is that an on-chain share register is structurally different from an off-chain database. The chain's state is the register; the operative ownership entry is the on-chain token balance. If the tokenisation product wants the on-chain entry to be the legally operative record (rather than a representation of a record held off-chain), the entity maintaining the on-chain state has to be a registered transfer agent. Otherwise, the on-chain record is a parallel data layer that may or may not match the off-chain register, with the off-chain register controlling in any disputed case.
This is the legal-control distinction from 01 3 tokenisation legal control. The genuinely-tokenised product (where the chain entry is the operative record) requires transfer-agency registration. The wrapped or referenced-product (where the chain entry is a derivative or representation of an off-chain register) does not, but it also does not deliver the legal-clarity benefit that a genuinely-tokenised product can.
How Securitize discharges the function
Securitize is the most-cited example of an SEC-registered transfer agent operating end-to-end inside the tokenisation perimeter. The firm operates Securitize LLC as the registered transfer agent (the legal record of share ownership for the funds it services), Securitize Markets as a broker-dealer and ATS (alternative trading system), and the technology platform itself as the operating layer. The combination is what allows BUIDL and adjacent products to keep the share register on-chain through whitelisted addresses while remaining inside the SEC perimeter (details).
The mechanics of how Securitize discharges the transfer-agent function on a tokenised fund follow the SEC's existing regulatory grammar with a thin tokenisation overlay. KYC and qualified-purchaser-eligibility verification happen at the platform layer; addresses that clear the verification get added to the smart-contract whitelist; the on-chain transfer of tokens to whitelisted addresses is the change of legal ownership for transfer-agent purposes; the records are maintained both on-chain (the smart-contract state) and in Securitize's own registered-transfer-agent records, with reconciliation between the two.
The cross-chain dimension is the part that does not have a clean off-chain analogue. BUIDL is live on nine chains; Apollo's ACRED runs across Provenance, Solana, and adjacent networks. The legal-recordkeeping requirement is that the transfer agent maintain a single consolidated record of beneficial ownership across all chains, with the same legal counterparty identifiable across chain identities. Securitize's whitelist consistency across nine chains is the operational discipline that satisfies the requirement, and it is the part of the function that is genuinely new relative to the pre-tokenisation transfer-agent role.
The dividend distribution function for BUIDL runs through a daily on-chain rebase mechanic rather than through the conventional off-chain dividend-payment process; for ACRED, the function runs through more conventional fund cadence. The transfer-agent recordkeeping accommodates both patterns; the operating choice flows from the underlying fund's distribution mechanics rather than from the transfer-agency function itself.
What happens when transfer agent and platform are the same entity
The Securitize pattern (registered transfer agent and operating technology platform inside the same group) is structurally different from the conventional split where a fund issuer appoints an external transfer agent and contracts with a separate technology vendor for distribution.
Three consequences worth flagging.
First, the operational integration is tighter. The whitelist that gates token transfers and the share register that the transfer agent maintains are operated by the same entity, which removes the reconciliation problem between the two. In a conventional split, the issuer's transfer agent maintains the register and a separate KYC platform gates investor onboarding, with the two needing periodic reconciliation. In the integrated Securitize model, the on-chain state and the registered-transfer-agent records are kept in sync at the contract level rather than through reconciliation.
Second, the regulatory perimeter is concentrated. SEC examination of the transfer agent function lands at the same entity as SEC examination of the broker-dealer function (Securitize Markets) and at the same entity as the technology platform's operational discipline. For an asset manager picking a partner, the integration means a single operational counterparty for multiple regulated functions, which is operationally simpler than running across separate counterparties but creates a larger single point of operational dependence.
Third, the strategic implication for new entrants is that the integrated model is materially harder to replicate than the technology-platform-only model. SEC transfer-agent registration is a non-trivial administrative process and requires standing operational capacity for the recordkeeping function. Most US tokenisation platforms are technology vendors without the registrations; the asset managers using those platforms have to bring their own transfer agents. Ondo Finance's October 2025 acquisition of Oasis Pro is the closest competing move, reaching for the same broker-dealer plus ATS plus transfer-agent combination.
The European parallel: registrar role under the DLT Pilot Regime
The EU does not have a single regulatory function exactly equivalent to the US transfer agent. Different functions are split across the registrar role under national company law, the central securities depository (CSD) role under the Central Securities Depositories Regulation (CSDR), and the issuer-services functions under the relevant fund-management directives.
The DLT Pilot Regime, which entered into force in March 2023, is the EU-level mechanism for accommodating distributed-ledger-based market infrastructure for tokenised financial instruments. The Pilot Regime allows for a DLT settlement system, a DLT trading and settlement system, or a DLT multilateral trading facility to operate under specific exemptions from CSDR and MiFID II requirements, with the designated operator taking on functions structurally analogous to the US transfer-agent role. The Pilot Regime is the closest EU analogue to the integrated platform-plus-transfer-agent model that Securitize operates in the US.
The substantive difference is that the DLT Pilot Regime is designed primarily for tokenised securities (bonds, equities, money-market instruments) traded on a DLT-based market infrastructure, rather than for tokenised fund interests. The latter route in the EU is generally through the existing fund-management directives (UCITS, AIFMD) with the on-chain wrapper layered on top of conventional fund-administration arrangements. The result is that the EU has not converged on a single tokenisation-specific recordkeeping function in the way the US has crystallised around the SEC-registered transfer agent.
For a tokenisation operator running both US and EU distribution, the structural implication is that the US-side recordkeeping is concentrated in a single regulatory function (the SEC transfer agent) and the EU-side recordkeeping is split across multiple functions depending on the underlying instrument and the chosen market-infrastructure overlay. The MiCA regulation does not address transfer-agent-equivalent functions directly, because tokenised securities and tokenised fund interests are explicitly outside MiCA's scope (details).
What the role does not do
Three things the transfer-agent function does not, in the tokenisation context, accomplish.
It does not provide custody of the underlying fund assets. BNY custodies the BUIDL T-bill and repo sleeve; Securitize is the transfer agent for the fund interest, not the custodian for the underlying. The two functions sit at different counterparties and serve different regulatory purposes.
It does not provide custody of the on-chain token. The whitelisted holder chooses the wallet (self-custody, an institutional custody platform, Coinbase Custody, Anchorage Digital Bank, or whatever the holder selects). The transfer agent's recordkeeping reflects which whitelisted address holds what balance, but the operational custody of the private keys associated with each address is the holder's responsibility.
It does not solve the DeFi composability problem. The transfer-agent function gates transfer at the smart-contract level by reference to the whitelist; that gating is what creates the composability constraint discussed in the institutional composability paradox page. A transfer agent maintaining a whitelist-gated register cannot also accommodate arbitrary DeFi composability without breaking the regulatory perimeter that the registration provides. Securitize's Vault Registrar EIP work is the candidate Ethereum standard that would put compliance logic on chain in a way DeFi protocols can read; if the EIP lands, it is a partial resolution to the trade-off (details).
Open questions
- Whether the US transfer-agent function eventually accommodates AI-agent-controlled wallets as whitelisted holders. The structural fit is plausible (the agent's wallet is just another address subject to the same KYC and qualified-purchaser-eligibility verification), but no major asset manager has publicly confirmed agentic-commerce-compatible whitelist policies.
- How the Vault Registrar EIP lands and which other US tokenisation platforms adopt it. The standardisation question is consequential for the broader institutional-composability story.
- Whether the EU DLT Pilot Regime accumulates enough live deployments to crystallise an EU-level transfer-agent-equivalent function. As of late April 2026 the uptake remains thin.
- How transfer-agent-equivalent functions develop in APAC. The Singapore SCS framework, the Hong Kong Stablecoins Ordinance, and the Japan PSA EPI category each handle the recordkeeping function differently, with no APAC-level convergence on a single tokenisation-specific function.