Equity tokenization through APIs

Platform initialization

As Daniel Admin, set up the platform administrator who initializes the system.

See First Administrator Setup for the API flow.

Configure these example values:

• Email: [email protected]
• Organization name: Digital Securities S.A.
• Base currency: EUR
• Asset factories to enable: Equity, ... (add whatever asset types you want to support)

Grant additional administrative permissions

Continue as Daniel Admin. Platform setup gives Daniel the minimum roles for managing the new organization. Grant the additional roles needed to invite users and configure extensions.

See Change Admin Roles for the API flow.

Add these roles to Daniel Admin:

• Add-on Manager: Manage platform extensions and modules
• Identity Manager: Required to invite other users

Invite platform team

Continue as Daniel Admin. Add the platform operators and external partners who participate in this example.

See Create Users for the API flow.

Platform operators:

1. Olivia Operator ([email protected])

   • Responsibilities: Creates tokens, manages corporate actions, handles minting/burning
   • Also needs: Wallet verification (to send transactions)

2. Clara Compliance ([email protected])

   • Responsibilities: Manages KYC/AML verification, registers identities, issues verifications
   • Also needs: Wallet verification (to send transactions)

External organizations:

3. Ian Issuer ([email protected])

   • Responsibilities: Legal owner of equity being tokenized

4. Colin Collateral ([email protected])

   • Responsibilities: Independent verification of collateral backing
   • Also needs: Wallet verification (to send transactions)

5. NovaX Vault ([email protected])

   • Responsibilities: Institutional vault for token custody

Assign platform admins

Continue as Daniel Admin. After onboarding the team, assign the roles each platform administrator needs.

See Add Administrators for the API flow.

Olivia Operator needs these roles:

• Asset Manager - Create and configure new assets

These roles let Olivia create and manage assets without granting compliance administration.

Clara Compliance needs these roles:

• Identity Manager - Manage the users registry, which users are known.
• Verification Issuer - Issue KYC and compliance verifications
• Compliance Manager - Will be able to manage global compliance rules
• Verification Policy Manager - Configure verification topics and trusted issuers

These roles let Clara configure verification topics, trusted issuers, and investor checks.

Colin Collateral needs these roles:

• Verification Issuer - Issue collateral verifications

This role lets Colin issue collateral verifications without broader platform administration.

Configure trusted issuers

Log in as Clara Compliance and configure which issuers can issue each verification topic.

See Configure Trusted Issuers for the API flow.

Clara Compliance as trusted issuer for investor-level verifications:

• Know Your Customer (KYC) - She verifies all investor identities
• Accredited Investor - For US qualified investor status (optional, if needed)
• Qualified Institutional Investor - For institutional investors under EU rules (optional, if needed)
• Anti-Money Laundering - Source of funds verification (optional, if needed)
• Professional Investor - For MiFID professional investor classification (optional, if needed)

Clara issues investor verifications because she owns the investor eligibility checks in this example.

Colin Collateral as trusted issuer for collateral verification:

• Collateral - Verifies that sufficient collateral backs the token

Colin issues this verification because Guardian Collateral Services is the example collateral verifier.

Olivia Operator as trusted issuer for asset-level verifications:

• Base Price - Provides reference pricing for the asset
• Unique Identifier - Manages ISIN and internal reference numbers
• Asset Classification - Confirms asset category and type
• Asset Location - Confirms jurisdiction of underlying asset (optional, needed for real-estate)

Olivia issues these asset-level verifications because she manages token metadata and classification in this example.

Register investors in registry

Log in as Clara Compliance and register the investors that will receive tokens.

See Register User for the API flow.

Register Ian Issuer:

• Choose Luxembourg as jurisdiction

Register NovaX Vault:

• Choose Luxembourg as jurisdiction

Result: Both users now show "Registered" status and can receive KYC verifications.

Issue KYC verifications

Continue as Clara Compliance and issue KYC verifications to the registered investors.

See Verify KYC for the API flow.

Verify Ian Issuer:

• Issue Know Your Customer verification

Verify NovaX Vault:

• Issue Know Your Customer verification

Result: Both users now have KYC verifications and can receive ACME tokens.

Create the ACME equity token

Create the equity token using the Asset Designer and the compliance modules needed for this example.

See Create Asset for the API flow.

Log in as Olivia Operator and configure:

Step 1: Asset Class

• Select Flexible Income class
• Choose Equity type

Step 2: Basic Details

• Name: ACME Holdings Equity
• Symbol: ACME
• Decimals: 0 (whole shares only)
• Jurisdiction: Luxembourg

Step 3: Asset Classification

• Category: Common Equity
• Class: Common Equity
• Unique Identifier: LU0000ACME01 (ISIN format)
• Internal Reference: ACME-EQ-001

Step 4: Pricing

• Currency: EUR
• Base Price: 0.71 (€0.71 per share)

Step 5: Compliance Modules

Enable Smart Identity Verification:

• Required verification: "Know Your Customer"
• Purpose: Only KYC-verified users can receive assets

Enable Collateral Requirement (optional):

• Topic: "Collateral"
• Ratio: 100% (full collateral backing)
• Purpose: Records the collateral verifier's backing check for this example

Configure token permissions

Asset creation gives Olivia the minimum token administration roles. Grant the token-specific roles needed for supply operations, emergency controls, and controlled servicing operations.

See Change Asset Admin Roles for the API flow.

Assign Olivia Operator these additional roles:

• Custodian - Execute transfers and forced transfers
• Emergency - Pause/unpause token operations
• Supply Management - Mint and burn token supply

Issue collateral verification

Colin must issue a collateral verification before minting is possible. This is a requirement when collateral modules are enabled.

See Collateral for the API flow.

Log in as Colin Collateral and issue a verification with these details:

• Amount: 100000 (covering full supply)
• Expiration: 1 year from now

This records that Guardian Collateral Services verified backing for the full token supply in the demo scenario.

Unpause the token

Log in as Olivia Operator and activate the ACME asset.

See Pause/Unpause Asset for the API flow.

Olivia can unpause because she has the Emergency role on the ACME token.

Mint and distribute ACME tokens

Continue as Olivia Operator and mint tokens to the issuer.

See Mint Assets for the API flow.

Mint to ACME Holdings:

• Recipient: Ian Issuer (select from contacts or use wallet address)
• Amount: 100000 (full token supply)
• Purpose: Initial distribution to issuer

Execute forced transfer to exchange

Continue as Olivia Operator. Move 20,000 tokens from the issuer to the exchange by using the forced transfer workflow as a controlled custodian operation.

See Forced Transfer for the API flow.

Transfer configuration:

• From address: ACME Holdings (select from contacts)
• To address: NovaX Exchange (select from contacts)
• Amount: 20000
• Purpose: Allocate tokens to exchange for secondary market custody

Use forced transfer here only to demonstrate a custodian-controlled servicing operation between verified parties. Do not model ordinary investor transfers on this step.

Olivia can execute this operation because she has the Custodian role on the ACME token.