Guide · Compliance

How compliance works across Defactor

Clear compliance once, reuse it everywhere — the layer underneath Raise, Mint and Yield.

For everyone6 min read

Compliance isn't a product sitting beside Raise, Mint and Yield — it's the layer that runs underneath all three. Every asset carries its eligibility, transfer rules and audit trail wherever it goes.

This guide explains how verification, whitelisting and audit records work, and why doing compliance once means you can reuse it everywhere.

The idea

Compliant by design, across everything

Because compliance is built into the foundation, you don't re-solve it for each product. Investors verify once, then take part across every eligible asset without repeating onboarding.

For issuers and operators, this means the rules you set are enforced automatically — non-compliant transfers simply can't happen.

The pieces

KYB, whitelist, audit — all automated

Automated KYB

Everyone is verified before they can join a deal, so you always know who you're dealing with.

Region rules

Transfer rules are built in. Non-compliant transfers are blocked automatically, by design.

Whitelisting

Only approved holders can hold or transfer an asset — eligibility is enforced at the token level.

Audit-ready records

Holder registers and full audit trails are available on demand, not reconstructed after the fact.

Why it matters

Verify once, reuse everywhere

The biggest cost in private markets isn't the deal — it's the repeated compliance work around every deal. Defactor removes that repetition.

An investor who verifies once can participate across eligible assets. An issuer who sets rules once has them enforced on every transfer. That's what 'clear compliance once, reuse it everywhere' means in practice.

Tip. Compliance follows the asset, not the platform screen. Even as a token moves between Mint and Yield, its rules and audit trail move with it.

Compliant by design

See how KYB, whitelisting and audit trails run underneath every Defactor product.

Keep learning