Securitize Integration for Fund Managers, Onboarding Platforms and Lending Markets
Fund managers, platforms and lending markets on Securitize onboard investors on their own KYC, track whitelisting and match balances to their books. Securitize leaves that side to them, and Protofire builds it. We built the DEX core for Swarm Markets, a BaFin-licensed DEX at launch where only KYC-verified wallets trade.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
What a Securitize integration tracks for each investor
A Securitize integration keeps three answers about each investor in step inside your records. For example, an investor passed your KYC on Monday. Is she verified at Securitize, is her wallet on the token, and does the fund's record show her? Each of these questions is answered separately, at its own time.
Securitize relies on the KYC your platform already ran, and it still screens each investor itself (Securitize). Securitize's SEC-registered transfer agent, Securitize Transfer Agent, LLC, keeps the record of who holds the fund tokens it serves (SEC). Your firm keeps the investor screens and the KYC. Your firm also handles each result and keeps its own books. Protofire builds that side of the integration and connects it to Securitize.
Who owns each layer of the integration
Verdicts go from Securitize to your systems, and whitelisting requests go to the token's registry on chain. Balances come back to your books at your cut-off block.
Investor screens and KYC
Investor records and books
SecId client
Event receiver and pollers
Balance reads and vault registrations
SecId API and screening
Transfer agent and DS Protocol
NAV and redemptions
Securitize answers arrive late, and the API cannot remove a whitelisting
Securitize answers each question about an investor or a wallet after the API call that asked it.The Securitize API cannot undo one of those answers. A screening hit moves an investor to manual review while a compliance operator decides (overview). A whitelisting request returns "processing", and the request reaches the chain later without a notification (whitelisting). Securitize delivers webhooks at least once, and they can arrive out of order (webhooks).
If a platform does not handle late, repeated or out-of-order answers, the failures are quiet. A platform that acts twice on a repeated webhook, or reads manual review as a decline, turns away an eligible investor. A platform that blocks a wallet in its own screen still finds the wallet whitelisted at Securitize until Securitize removes it. The wallet is also still whitelisted on each token that shares the registry. Securitize's docs are thorough, but the handling is left to your firm.
A fund manager faces a harder limit. Securitize's public APIs cover investor onboarding, tokenized stock trading and corporate actions on the CETs a platform lists (APIs). None of these APIs lets a manager drive the register, NAV or redemptions. BlackRock's summary prospectus of 31 July 2026 covers its Daily Reinvestment Stablecoin Reserve Vehicle (OnChain Shares, RSVXX). The prospectus lists Ethereum, Tempo and Solana, and it says who keeps the record (prospectus). So a manager's books start from what its agreement with Securitize delivers, and reads of the chain check those books.
The Fund’s transfer agent, Securitize Transfer Agent, LLC (the “Transfer Agent”), maintains the official record of ownership of OnChain Shares on the public blockchains that are used by the Fund’s investors.
Securitize facts we build against
- Transfer agent
- Securitize Transfer Agent, LLC is registered with the SEC under file 084-06638. Its Form TA-1 amendment is dated 27 August 2026 (SEC).
- Token code
- DS Protocol, with DSToken v4, an ERC-20 superset under Apache 2.0. Release 4.2.0 is dated 21 October 2026 (GitHub).
- Balances
- New DS tokens default to SCALED_UI. That mode is raw balances plus the ERC-8056 display multiplier, read through uiMultiplier and balanceOfUI (GitHub).
- Onboarding API
- The SecId API is REST with OAuth 2.0 client credentials and a sandbox. Production credentials follow a 14-point go-live checklist (checklist).
- Webhooks
- Each account has one HTTPS endpoint, and webhooks use Standard Webhooks signatures. The endpoint answers 2xx within 10 seconds. Retries run up to 72 hours, and events can be read back for 90 days (docs).
Checked November 2026 against Securitize's documentation, GitHub and SEC filings. Protofire integrates Securitize for firms that have chosen it.
What Protofire builds in a Securitize integration
Investor onboarding through the SecId client
Support sees where each investor stands without asking Securitize. Manual review shows as a pending state that grants nothing. Protofire builds the SecId client for individuals and companies, from the create call to tax forms. Each id that Securitize returns is stored with its response. The provider's checks connect through compliance integration.
Each status change booked once
A webhook that arrives twice is recognized and dropped, so a status change is booked once. Protofire builds a receiver that checks the signature over the raw body and drops repeats on sourceEventId. The receiver also reads the status back before acting. KYC webhooks run in sandbox and reach production on request (docs). So the integration keeps a poller as the backstop.
Wallet whitelisting tracked token by token
Your team knows which wallets a token's registry holds and which are still waiting. Protofire builds the whitelisting calls and a poller for each token. We also build an alert for a wallet in processing for more than a day, and a wallet table that shows shared registries. Securitize asks for no signature or challenge, so your own proof of control is taken before a wallet is sent.
Fund balances checked against the record
Your books record one number per wallet, either the raw balance or the display amount. Protofire reads balances per chain at one daily cut-off block and reads the multiplier from the same block. We match holder lists to the transfer agent records you receive. We also flag a chain read taken too long ago. Each difference names its chain, block and wallet, and the role that moved the units.
Prices and orders mapped to one dealing day
A fund's own documents set its price and its redemption path. Protofire stores each price with the time the fund set it. We store each order with the time it was received, so each order maps to one dealing day. A position is marked stale when its latest price predates the fund's last business day.
Lending vaults registered under investor signatures
A lending market that takes a DS token as collateral registers its contracts as vaults under each investor's identity. Since v2 of the VaultRegistrar, each registration needs the investor's EIP-712 signature (GitHub). Protofire builds the signing screen and the operator flow, which runs under your market's own key. We also build a watcher for permissions that are revoked or expired.
Where eligibility is held when an investor loses it
An investor's eligibility is held in five places, and each place changes on its own trigger.
Investor status at Securitize
What changes it: An expired or updates-required status, or a compliance review that sets a verdict
What your firm does: Withdraws KYC-dependent access when the webhook arrives, after reading the status back
Whitelisted wallet
What changes it: Securitize alone: "There is no call to remove a whitelisting" (docs)
What your firm does: Stops accepting the wallet and logs the request sent to Securitize
DS token transfer rules
What changes it: The compliance service checks country, retail investor count, accreditation and flowback. The Transfer Agent role can freeze the token (GitHub).
What your firm does: Books a reverted transfer as a compliance refusal and names the rule
VaultRegistrar permission
What changes it: The permission holds until the signature's deadline passes or the investor revokes it
What your firm does: Watches revocations and deadlines, and stops new registrations
Lending market collateral
What changes it: Gearbox "does not automatically remove DS token registrations, freeze CreditAccount contracts, or reassign them". A Securitize operator does (Gearbox docs).
What your firm does: Raises the freeze or reassignment with Securitize
Our record: a permissioned venue for Swarm Markets
Protofire's work on a permissioned venue applies to building around Securitize.
DEX core and subgraph for Swarm Markets
In 2021 Protofire built the DEX core, a Balancer-fork AMM, and the subgraph for Swarm Markets.Swarm Markets was a BaFin-licensed DEX at launch where only KYC-verified wallets trade. Swarm held the license and ran KYC and permissioning. A permissioned venue asks what a Securitize token asks of a wallet: is this holder eligible now, and who says so?
Project steps from your Securitize agreement to the first investor
- Step 1
Your agreement sets the scope
Your agreement with Securitize fixes when investors turn verified: at submit or once screening answers. It also fixes which tokens you may whitelist (docs). Protofire reads the agreement first and writes the states and checks to match it. - Step 2
Build and test in Securitize's sandbox
Protofire builds the client and the receiver against Securitize's sandbox. In the sandbox, the 14 checks of Securitize's go-live checklist are confirmed before production credentials are issued. - Step 3
Production access for KYC webhooks on request
KYC webhooks reach production through a request to the Securitize contact. So the status poller follows the first investors and watches the first wallets through whitelisting. - Step 4
You hold the credentials and the keys
The OAuth client id and secret that Securitize issued to your firm are kept in your secret store. Code that Protofire writes for you is yours by contract, within the license of any third-party software involved. Your team runs the integration, or we operate a service under a written scope through managed onchain operations. Protofire holds no DS Protocol role and no OPERATOR_ROLE on a VaultRegistrar. A lending market's operator key is held by that market.
How work with Protofire starts
You send three things: the tokens your Securitize account is enabled for, when your agreement makes investors verified, and your investor records system.A fund manager also sends a day of transfer agent records. Protofire's proposal answers with the states, checks and balance reads that your systems have to hold. The terms in this section apply as set out on how we work.
- 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.
When building around Securitize adds little
Building around Securitize adds little when Securitize already runs the whole fund path for your investors.It also adds little when the work needs an API that Securitize does not publish.
- Your investors subscribe and redeem through Securitize, and your administrator already receives what it books. Then a reconciliation check is the whole job.
- You want to drive the register, NAV or redemptions from your own systems. Then the scope is set with Securitize first.
- You offer tokenized stocks. They run through a separate Securitize Stocks API, which this page does not cover.
- You want contracts of your own instead of DS Protocol. Protofire's ERC-3643 development service builds one permissioned token. Our tokenization infrastructure service builds a platform for several issuers.
Protofire is an engineering firm and holds no financial or crypto-asset license. Licensed activity belongs to you and your providers. Securitize keeps the register and screens investors, and your platform keeps its own KYC.
FAQ
What is a Securitize integration?
Who can build a Securitize integration for a fund manager, an onboarding platform or a lending market?
Does Securitize repeat our KYC?
Do investors in the EEA need anything extra?
Can we remove a wallet from a Securitize token ourselves?
Which wallets and networks does a Securitize integration cover?
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.
