Securitize

About

Securitize is treated as a platform integration with N funds behind one issuer. Each fund is issued as a DS Protocol token whose transfers are gated by an on-chain whitelist (the DS Registry). The funds exposed natively through the Yield API are all denominated in USDC:

On entry, USDC is deposited through the fund's on-ramp contract, which mints the DS token to the user at the current NAV. There are no separate reward tokens, no claim transactions, and no compounding actions — yield accrues through NAV appreciation of the DS token and is auto-compounding by construction.

Withdrawals are issuer-processed. Exit transfers the DS token to the fund's redemption wallet, after which Securitize settles the USDC off-chain. There is no on-chain claim step.

Considerations

Subscribe / redeem flow

Entry subscribes via the on-ramp; exit hands the DS token to the fund redemption wallet:

Entry is preceded by an APPROVAL transaction when the current USDC allowance is insufficient. The on-ramp swap is built with a minDsTokenOut floor derived from the current NAV to protect against slippage.

NAV-priced value

The DS token, NAV, and input token (USDC) all share 6 decimals. The user's underlying value is computed as balance × navPerShare. For value-accruing funds with no distributions (e.g. ACRED, STAC), APY is the inception-to-date annualized NAV return (CAGR); distribution funds (e.g. VBILL) use a published rate feed.

Compliance layer

Every fund is KYC-gated by the DS Registry whitelist. The whitelist is checked before transaction construction on both entry and exit (and again in preCheck). A non-whitelisted wallet is rejected, and KYC status is exposed through the unified KYC interface (GET /v1/yields/:id/kyc/status) — returning NotStarted with the Securitize onboarding URL when the wallet is not yet registered.

Eligibility is deny-by-default with a US-only allow-list and per-fund investor tiers (Accredited Investor or Qualified Purchaser), verified through Securitize onboarding via third-party attestation.

Minimum amounts

Each fund enforces an initial and a lower subsequent minimum subscription (the subsequent minimum applies once the wallet already holds the asset). The effective minimum is the greater of the on-chain minimum and the policy minimum:

Minimums are surfaced via getStakeArguments and enforced in preCheck; sub-minimum requests are rejected with 400 Bad Request before transaction construction.

List of Integration IDs