SPV Symbology and CUSIPs

This page describes the symbology and CUSIP used to identify the single asset pre-IPO Company SPVs offered through Monark's APIs. This symbology leverages the CMS Standard, providing a naming convention that works for existing market participants, is differentiated from other symbols, and provides a simple way to understand which security and class of stock is being traded. Think of these symbols as individual "tickers" assigned to each SPV.

Overview

Each Pre-IPO Company will be assigned its own symbol. The Pre-IPO Company symbol will serve as the "base" for each SPV-specific symbol. See the link here for a comprehensive list of the symbols assigned to each Pre-IPO company.

The prefix and suffix(es) that are prepended or appended to the "base" symbol provide additional information around the structure of the SPV and the shares that it holds. This enables market participants to quickly gather an understanding of what they are investing in when acquiring shares in an SPV. Monark will assign each SPV its own symbol upon creation. The SPV will maintain the same symbol throughout it's entire lifecycle.

Production Symbology

The table below uses SpaceX (SPAX.PVT) as as the "base" symbol.

Security CategorizationCMS SuffixExample
PreferredPRSPAX.PVT.PR
Preferred Class "A"*PRASPAX.PVT.PRA
Preferred Class "B"*PRBSPAX.PVT.PRB
Preferred Held in SPVSPRSPAX.PVT.SPR
Preferred Class "A"* Held in SPVSPRASPAX.PVT.SPRA
Preferred Class "B"* Held In SPVSPRBSPAX.PVT.SPRB
CommonSPAX.PVT
Common Held in SPVSSPAX.PVT.S
Common Class "A"*ASPAX.PVT.A
Common Class "B"*BSPAX.PVT.B
Common Class "A"* Held In SPVSASPAX.PVT.SA
Common Class "B"* Held In SPVSBSPAX.PVT.SB
TEST SymbolTESTSPAX.PVT.TEST

*Class “B” though Class “Z” securities are denoted using the same format as Class “A” securities on this matrix.

Sandbox Symbology

To avoid replication across environments, and to ensure you can run both systems in parallel, Monark will create a level of separation in the symbols used in sandbox from the symbols used in production. This is achieved by adding a "Z" in front of the SPV symbol. See matrix below.

Security CategorizationCMS SuffixExample
PreferredPRZSPAX.PVT.PR
Preferred Class "A"*PRAZSPAX.PVT.PRA
Preferred Class "B"*PRBZSPAX.PVT.PRB
Preferred Held in SPVSPRZSPAX.PVT.SPR
Preferred Class "A"* Held in SPVSPRAZSPAX.PVT.SPRA
Preferred Class "B"* Held In SPVSPRBZSPAX.PVT.SPRB
CommonZSPAX.PVT
Common Held in SPVSZSPAX.PVT.S
Common Class "A"*AZSPAX.PVT.A
Common Class "B"*BZSPAX.PVT.B
Common Class "A"* Held In SPVSAZSPAX.PVT.SA
Common Class "B"* Held In SPVSBZSPAX.PVT.SB
TEST SymbolTESTZSPAX.PVT.TEST

Duplicate SPVs

You may encounter a situation in which there are multiple SPVs with the same structure, holding shares of the same company. We account for this by prepending a single letter to the SPV symbol. The prefix will be the letter "A" for the first duplicate, "B" for the second duplicate, and so on throughout the alphabet for all subsequent duplicates. Though unlikely, once the 26th duplicate is reached (letter "Z"), Monark will update the naming convention to account for additional SPVs.

For example: if there are 5 SPVs holding shares of Preferred Class A stock in SPAX.PRIV, the following symbology would apply:

  1. First SPV: SPAX.PVT.PRA
  2. Second SPV: ASPAX.PVT.PRA
  3. Third SPV: BSPAX.PVT.PRA
  4. Fourth SPV: CSPAX.PVT.PRA
  5. Fifth SPV: DSPAX.PVT.PRA

CUSIPs

Monark will assign each SPV a unique CUSIP identifier, set up slightly differently for sandbox and production environments.

Production CUSIPs

Each CUSIP generated by Monark's system in production will be structured as "ALTM + Four Characters + Checksum."

Example: ALTM12348

Sandbox CUSIPs

Each CUSIP generated by Monark's system in the sandbox environment will be structured as "ZALTM + Three Characters + Checksum."
Similar to the SPV symbology above, the "Z" prefix in the CUSIP prevents confusion across sandbox and production environments.

Example: ZALTM1230