SettleMint
User guidesCompliance

Compliance overview

Compliance modules enforce on-chain rules for your tokenized assets. Learn about available modules and how to configure them during asset creation.

Compliance modules are on-chain rules that automatically enforce regulatory and business requirements for your tokenized assets. The verification system enables trusted entities to issue attestations that prove compliance with these requirements.

Compliance Modules

Compliance modules are smart contracts that validate every transaction against your business rules.

When to configure compliance modules

You select compliance modules during asset creation using the Asset Designer wizard.

Some modules can be added or modified after deployment if you have the governance role on the asset. However, it's best to configure compliance requirements upfront to avoid disrupting existing holders.

Compliance management integrated into the operator dashboard

Available compliance modules

ModuleDescriptionValidates
Identity verificationRequires verified OnchainID with valid verifications (KYC, accreditation)Both sender and recipient
Country allow listOnly wallets from specified countries can hold the assetRecipient
Country block listWallets from blocked countries cannot hold the assetRecipient
Address block listExplicitly block specific wallet addressesBoth
Investor count limitCaps maximum unique holders (e.g., Reg D 99 investor limit)Transfers increasing holder count
Time lockEnforces minimum holding period before transfersSender
Transfer approvalRequires manual approval before each transfer executesEach transfer
Collateral requirementRequires sufficient collateral backing before minting new unitsMinting operations only

When configuring address-based modules (identity allow/block lists, address block lists, and trusted issuers), you can select from existing identities or enter custom addresses manually.

How modules work together

When multiple compliance modules are enabled, all modules must pass for a transaction to succeed. If any module rejects the transaction, it fails with an error indicating which compliance check was not met.

For example, if you enable both identity verification and country allow list:

  • The recipient must have a verified OnchainID
  • The recipient's identity must be from an allowed country
  • Both conditions must be true for the transfer to proceed

Verification System

Understanding verifications

What are verifications?

Verifications are on-chain attestations that confirm specific information about:

  • Investors - Identity, accreditation, eligibility
  • Issuers - Regulatory compliance, licensing, jurisdiction
  • Assets - Collateral backing, pricing, classification
  • Contracts - Smart contract identity verification

Verification components

Each verification contains:

  • Topic - What is being verified (e.g., KYC, Accreditation)
  • Scheme - The signature scheme used (e.g., ECDSA or CONTRACT)
  • Issuer - Who verified the information
  • Signature - The cryptographic signature of the verification
  • Data - Verification details (often hashed for privacy)
  • URI - Optional URI reference (e.g., IPFS hash for additional data)

Important: Verifications do not have expiration dates by default. Instead, issuers can manually revoke verifications when they are no longer valid.

How trusted issuers work

Anyone can issue verifications

Any identity with an on-chain presence can technically issue verifications. However, for the platform to recognize and enforce these verifications for compliance purposes, the issuer must be designated as trusted by your organization.

Organization-specific trust

Trust relationships are organization-specific:

  • Issuer X may be trusted by Organization A for KYC verifications
  • Issuer X may NOT be trusted by Organization B for the same topic
  • Each organization maintains its own list of trusted issuers per verification topic

Two types of verification issuers

Trusted issuers:

  • Can add verifications directly to user identities on-chain
  • Their verifications are automatically recognized by compliance modules
  • Require explicit configuration by platform administrators

Regular issuers:

  • Can create verifications but cannot add them directly to identities
  • Must provide verifications off-chain to users
  • Users decide whether to add these verifications to their own identities
  • Verifications are NOT automatically recognized for compliance

Verification topics define available compliance checks

Available verification topics

Investor-level verification topics

TopicPurposeCommon IssuersRegulatory Context
Know Your Customer (KYC)Identity verification (passport, government ID, residency)Compliance officers, KYC providersRequired for AML/CTF compliance and basic onboarding
Anti-Money Laundering (AML)AML/CTF screening (sanctions lists, PEP screening, adverse media)Compliance officers, banksUsually paired with KYC verification
Qualified Institutional Investor (QII)QII status under securities regulationsBanks, insurers, pension fundsUS Investment Company Act, Japanese FIEA
Professional InvestorProfessional/qualified investor criteriaRegional regulators, professional bodiesEU MiFID II, Hong Kong SFO, Singapore SFA
Accredited InvestorAccredited investor qualification (income, net worth, institutional status)Lawyers, accountants, banksUS SEC Regulation D, Rule 501
Accredited Investor (Verified)Document-verified accredited status with supporting documentationLicensed professionalsUS Regulation D 506(c) offerings
Regulation SNon-US person status as defined in Regulation SCompliance officersRequired for US Securities Act Reg S exemptions

Asset-level verification topics

TopicPurposeCommon IssuersExamples
CollateralAsset backing verificationCustodians, collateral agentsPhysical assets, cash reserves, securities
Unique IdentifierOfficial asset identificationNumbering agencies, operatorsISIN for securities, Real Estate Number (REN)
ClassificationAsset class and categoryOperators, regulatorsCOMMON_EQUITY, GROWTH_EQUITY, RESIDENTIAL, MIXED_USE
Base PriceAsset valuationPrice oracles, valuersMarket price, appraisal value
IssuerLegal issuer of the assetLegal counselCorresponds to on-chain TokenIssuer identity
LocationAsset location data (for real estate)Asset operators, registrarsCity, district code, area ID (privacy-preserving)

Issuer-level verification topics

TopicPurposeCommon IssuersRegulatory Context
Prospectus FiledValid prospectus filed or publishedRegulatory authoritiesRequired under securities/markets law unless exempt
Prospectus ExemptExemption from prospectus requirementsLegal counsel, regulatorsSmall offers, private placements, MiCA de-minimis
LicensedRegulatory license or authorization heldLicensing authoritiesMiCA CASP license, SEC registration, EU AIFM
Reporting CompliantOngoing disclosure and reporting complianceAuditors, regulatory authoritiesPeriodic financial reports, annual filings
JurisdictionIssuer's legal jurisdictionLegal counsel, regulatory authoritiesLegal domicile and regulatory oversight

General verification topics

TopicPurposeCommon Issuers
Contract IdentitySmart contract identity verificationSystem administrators

Compliance Strategies

For regulated securities

  • Government-licensed issuers
  • Multiple verification layers
  • Strict expiration periods
  • Regular re-verification

For private placements

  • Internal compliance team
  • Lawyer attestations
  • Longer validity periods
  • Risk-based approach

For institutional markets

  • Exchange verifications
  • Mutual recognition
  • Automated verification
  • High-volume capable

Setup Guides

Verification framework

Asset compliance

Developer guides

On this page