Quick Answer
Who runs KYC/AML, OFAC screening and 506(c) verification on a security token, how ERC-3643 and ERC-1400 whitelist wallets, and how Rule 144, Reg S and Reg CF lockups are coded on-chain.
Security token compliance means four layers working together: identity checks (KYC/AML and sanctions screening), investor eligibility checks (such as accredited-investor verification), an on-chain whitelist that only lets approved wallets hold the token, and transfer rules that enforce holding periods and resale limits. The legal duties sit with regulated parties such as broker-dealers, transfer agents and the issuer. The smart contract only enforces decisions those parties have already made off-chain.
This guide walks through each layer: who is responsible, which rule applies, and how it shows up in the token contract. It also covers the part most compliance guides skip. Every check is a step where a real investor can give up. If you run a tokenized raise, your onboarding flow decides your conversion rate just as much as your marketing does. All rule references are current as of November 2026.
Who has to do KYC and AML on a security token offering?
In the US, the legal AML program obligation sits with regulated financial institutions, not with the token. For most tokenized offerings that means the broker-dealer or the platform's registered affiliate that onboards investors. The issuer and its counsel then decide how much extra screening to layer on top.
Broker-dealers: the Bank Secrecy Act and the Customer Identification Program
Under FinCEN's rules, a broker-dealer must keep a written AML program approved by senior management. Under 31 CFR 1023.210, that program needs internal controls, independent testing, a designated AML officer, ongoing training, and risk-based customer due diligence. The due diligence covers the nature and purpose of each relationship plus ongoing monitoring.
The Customer Identification Program rule at 31 CFR 1023.220 sets the minimum data a broker-dealer collects before opening an account: name, date of birth for individuals, an address, and an identification number. For US persons that is a taxpayer identification number. For non-US persons it can be a passport number and country of issuance or a similar government-issued document. The firm then verifies identity with documents, non-documentary methods, or both. It keeps records for five years after the account closes. It checks customers against government lists of known or suspected terrorists. The same rule lets a broker-dealer rely on another financial institution's CIP under defined conditions. This is how many tokenization platforms share onboarding across affiliated entities.
For legal entity investors such as LLCs, trusts and family offices, 31 CFR 1010.230 requires covered institutions to identify and verify the beneficial owners. Expect entity investors to upload formation documents and owner IDs. This is one of the slowest steps in any onboarding flow.
Suspicious activity reporting applies too. Under 31 CFR 1023.320, a broker-dealer files a SAR for suspicious transactions involving at least $5,000. It generally files within 30 calendar days of initial detection.
FINRA Rule 3310
Broker-dealers that are FINRA members also follow FINRA Rule 3310. It mirrors the FinCEN program elements. It requires a written AML program approved in writing by senior management, independent testing (annually on a calendar-year basis for most firms), a named AML compliance person reported to FINRA, ongoing training, and risk-based customer due diligence. If your tokenization platform's broker-dealer arm or ATS onboards your investors, this is the program your investors pass through.
What if there is no broker-dealer in the deal?
Some issuers sell directly in a Rule 506(c) offering without a placement agent. The issuer may not be a BSA "financial institution" in that case. Even so, sanctions law still applies, and issuers and their platforms typically still run KYC. They need clean identity data to verify accredited status, to whitelist wallets and to keep a reliable holder register. Counsel will usually decide the exact scope.
OFAC sanctions screening for token holders
Sanctions screening is not limited to banks. OFAC states that all U.S. persons must comply with OFAC sanctions. That includes US companies and their foreign branches. For digital assets, OFAC's virtual currency FAQs say the obligations are the same as for fiat. Firms dealing in digital currency are expected to build a risk-based compliance program that generally includes screening.
Two points matter for token issuers:
- Wallet addresses are on the SDN List. OFAC may list specific digital currency addresses linked to blocked persons as identifiers. It also warns that those address listings are not likely to be exhaustive. Screening names alone is not enough. Most platforms also screen the wallet a buyer wants whitelisted, often with a blockchain analytics tool.
- Screening is ongoing. A holder who was clean at subscription can be designated later. This is why token contracts include freeze functions (covered below).
Accredited investor verification under Rule 506(c)
Rule 506(c) lets issuers advertise publicly. The trade-off is that the issuer must "take reasonable steps to verify" that every purchaser is accredited. This sits in 17 CFR 230.506(c)(2)(ii). The rule lists non-exclusive, non-mandatory methods for natural persons that are deemed reasonable:
- Income method: review IRS forms reporting income for the two most recent years (for example W-2, 1099, Schedule K-1, Form 1040). Then get a written representation that the purchaser expects to reach the required income level this year.
- Net worth method: review asset documents (bank, brokerage and securities statements, CDs, tax assessments, independent appraisals) and, for liabilities, a consumer report from a nationwide credit bureau. All documents must be dated within the prior three months. Then get a written representation that all liabilities have been disclosed.
- Third-party confirmation: a written confirmation from a registered broker-dealer, an SEC-registered investment adviser, a licensed attorney or a CPA. The confirmation must say they took reasonable steps to verify within the prior three months.
- Prior 506(b) investors: a certification at the time of sale from someone who bought in the same issuer's 506(b) offering as an accredited investor before September 23, 2013 and still holds.
- Re-verification: if the issuer previously verified a person under these methods, a written representation at the time of sale covers that person for five years from the original verification. This assumes the issuer is not aware of contrary information.
These methods are a safe harbor, not the only route. In Securities Act Rules C&DI 256.35 and 256.36 (dated March 12, 2025), SEC staff confirmed that issuers can apply the reasonableness standard directly. The staff also said a high minimum investment can support a conclusion that reasonable steps were taken. That conclusion depends on the facts and circumstances. It assumes no actual knowledge to the contrary and confirmation that the investment is not financed by a third party. For tokenized funds with large tickets, this can remove a heavy document step. Counsel decides whether it fits your offering.
Whichever method you use, the result usually becomes an on-chain "claim" or whitelist flag. That is where compliance turns into code.
The FATF travel rule and virtual asset service providers
Outside the US securities framework, the FATF's updated 2021 guidance on virtual assets and VASPs says VASPs are subject to the same relevant FATF measures as financial institutions. It includes guidance on implementing the "travel rule." That rule requires originator and beneficiary information to move with qualifying transfers between providers. FATF notes on the same page that the guidance does not reflect later revisions to its standards. Read it alongside newer FATF material.
In the US, the recordkeeping and "travel" provisions for funds transfers of $3,000 or more sit in 31 CFR 1010.410. Whether a given token transfer counts as a covered transmittal depends on the facts and on FinCEN guidance. Counsel and the platform's compliance team decide that, not the marketing team. In practice, the travel rule matters most when your token moves between custodians, exchanges or ATSs rather than between whitelisted self-custody wallets.
How on-chain whitelisting works
A permissioned security token checks every transfer against an eligibility list before it settles. The two most common designs are ERC-3643 and the ERC-1400 family. For a full comparison see our guide to ERC-3643 vs ERC-1400 vs ERC-20.
ERC-3643: identity registry and ONCHAINID
ERC-3643 is a Final-status Ethereum standard (created 2021) built on ERC-20. Its pieces map closely onto a compliance team's workflow:
- Identity Registry: links each wallet address to an investor's identity contract and an ISO-3166 country code. Agents can register, update and delete identities.
- Identity contract (ONCHAINID): holds "claims," which are signed attestations such as "KYC passed" or "accredited." The ERC3643 Association describes ONCHAINID as the identity linked to each holder, carrying verified credentials such as KYC status, accredited status or country of residence.
- Trusted Issuers Registry and Claim Topics Registry: define which claim types are required and whose signatures count. For example, only your KYC provider and your verification provider.
- Compliance contract: enforces offering-level rules such as investor caps per country, per-investor token limits or allowed jurisdictions.
Each transfer runs two checks. isVerified confirms the receiver is registered and holds the required claims from trusted issuers. canTransfer checks the offering's global rules. If either fails, the transfer reverts.
ERC-1400: partitions and transfer checks
ERC-1400 is a library of standards: ERC-1410 partitions, ERC-1594 issuance and transfer checks, ERC-1643 document management and ERC-1644 controller operations. Its header still reads "Draft," and the GitHub discussion was closed as stale in 2022. It is still used in production by several platforms. Partitions split one holder's balance into tranches with different metadata. For example, "Reg D locked until date X" and "Reg D unlocked." canTransferByPartition lets a wallet or platform check whether a transfer would succeed, with a reason code, before the investor submits it. Reason codes such as "funds locked (lockup period)" or "invalid receiver" make good front-end error messages.
Transfer restrictions every tokenized offering has to encode
The whitelist answers "who can hold." Transfer restrictions answer "when and to whom can they sell." These come from the exemption you raised under.
Rule 144 holding periods (Reg D and other restricted securities)
Securities sold under Rule 506 are restricted securities. Under 17 CFR 230.144(d), a holder can resell under Rule 144 after a minimum of six months if the issuer has been an SEC reporting company for at least 90 days. Otherwise the minimum is one year. Most private issuers are non-reporting, so one year is the common default. Other exemptions may be available for resales, and counsel decides which ones apply. In token terms, this is a lockup timestamp per holder or per partition.
Regulation S distribution compliance periods
Offshore sales under Regulation S carry "distribution compliance periods" during which offers and sales cannot be made to US persons. Under 17 CFR 230.903, the length depends on the category. Category 2 uses 40 days. Category 3 debt uses 40 days. Category 3 equity, which applies to most non-reporting US issuers selling equity offshore, uses one year, or six months for a reporting issuer. Category 3 equity also requires purchaser certifications of non-US status, an agreement to resell only in line with Reg S, a legend, and an issuer obligation to refuse to register non-compliant transfers. A token contract that blocks transfers to US-coded wallets during the period is one practical way to meet that last condition.
Regulation Crowdfunding one-year resale restriction
Under 17 CFR 227.501, Reg CF securities cannot be transferred for one year from issuance. The exceptions are transfers to the issuer, to an accredited investor, as part of a registered offering, or to a family member (as defined), a family trust, or in connection with death or divorce. The contract logic is a one-year lock with an allowlist of exception routes. Each exception usually needs a manual approval step by the transfer agent.
Forced transfers, freezes and lost-key recovery
Regulated securities need an override. Courts issue orders, sanctions designations happen, and investors lose private keys. Both main standards build this in:
- ERC-3643: forcedTransfer lets an authorized agent move tokens between wallets, but the receiver must still be verified. recoveryAddress moves a holder's balance to a new wallet when they lose their key, and the recovery history stays on-chain. setAddressFrozen and freezePartialTokens freeze a whole wallet or part of a balance. pause halts all transfers.
- ERC-1400 (via ERC-1644): controllerTransfer and controllerRedeem let a designated controller force-move or redeem tokens. Each controller action must emit an event, so it is visible on-chain.
Investors from crypto backgrounds sometimes see these powers as a red flag. Disclose them plainly in your offering documents and FAQ. Explain who holds the agent or controller role, what triggers its use, and how lost-key recovery works, including the identity re-verification it requires. Clear answers here reduce drop-off. Vague answers create it.
The transfer agent's role in a tokenized offering
The SEC describes transfer agents as the parties that record changes of ownership, maintain the issuer's security holder records, cancel and issue certificates, and distribute dividends. Under Exchange Act Section 17A(c), a transfer agent generally must register before performing transfer agent functions for a qualifying security. Registration is filed on Form TA-1 under 17 CFR 240.17Ac2-1.
In a tokenized offering, a key design question is whether the blockchain is the official record or a mirror of an off-chain register kept by the transfer agent. Platforms answer this differently. Ask in writing which record controls if the two disagree. Also ask who signs forced transfers and recoveries. If you are comparing vendors, our tokenization platform checklist includes these questions.
Control map: what runs on-chain, what runs off-chain, and who operates it
| Control | On-chain or off-chain | Who typically operates it | Rule or standard |
|---|---|---|---|
| Identity collection and verification (CIP) | Off-chain (result stored as a claim or whitelist flag) | Broker-dealer or platform compliance team, often using a KYC vendor | 31 CFR 1023.220 |
| Beneficial ownership for entity investors | Off-chain | Broker-dealer or platform compliance team | 31 CFR 1010.230 |
| AML program, monitoring and SARs | Off-chain (on-chain analytics as an input) | Broker-dealer AML officer | 31 CFR 1023.210, 1023.320; FINRA 3310 |
| OFAC screening of names and wallets | Off-chain screening, on-chain freeze if needed | Platform compliance, issuer's agent | OFAC regulations and FAQs |
| Accredited investor verification | Off-chain (result stored as a claim) | Issuer, or a broker-dealer, RIA, attorney or CPA providing confirmation | 17 CFR 230.506(c)(2)(ii) |
| Wallet whitelist and eligibility check | On-chain | Platform or transfer agent acting as registry agent | ERC-3643 Identity Registry; ERC-1400 transfer checks |
| Holding periods and lockups | On-chain | Smart contract, configured by the platform | 17 CFR 230.144; 227.501 |
| Reg S US-person block | On-chain (country code) plus off-chain certification | Platform and issuer | 17 CFR 230.903 |
| Investor caps per country or per holder | On-chain | Compliance contract | ERC-3643 Compliance contract |
| Forced transfer, freeze, lost-key recovery | On-chain action, off-chain decision | Transfer agent or designated agent | ERC-3643 forcedTransfer, recoveryAddress; ERC-1644 |
| Official holder record | Depends on platform design | Registered transfer agent | Exchange Act 17A; 17 CFR 240.17Ac2-1 |
| Travel rule data between providers | Off-chain messaging | VASPs and financial institutions | FATF guidance; 31 CFR 1010.410 |
Privacy: what goes on-chain and what never should
Public blockchains are permanent and readable by anyone. Personal data does not belong there. The ERC-3643 model stores a claim and the signature of a trusted issuer on-chain. The underlying passport scans, tax forms and bank statements stay with the verifier.
For broker-dealers, SEC Regulation S-P at 17 CFR 248.30 requires written policies and procedures to safeguard customer information, including administrative, technical and physical safeguards. Non-US investors may bring their own data protection laws into play. Practical rules most counsel will support:
- Never put names, emails or document hashes that could be reversed into token metadata.
- Remember that country codes in an identity registry are visible. Decide with counsel whether that is acceptable for your investor base.
- Ask your platform where KYC files are stored, who can access them and how long they are retained. The CIP rule requires at least five years after account closure.
Where compliance friction kills conversions, and how to design around it
Every control above is a step where a qualified, interested investor can stall. The heaviest steps are easy to spot, because they ask investors for sensitive documents or new technical skills. They are accredited verification document requests, entity beneficial-ownership uploads, and wallet setup for investors who have never self-custodied. None of them are optional. All of them can be designed better.
A step-by-step onboarding design that keeps compliance intact
- Pre-qualify before the form. Explain on the landing page who can invest (accredited only, non-US only, minimum ticket) so unqualified traffic self-selects out before it reaches KYC.
- Tell investors what they will need up front. List the ID, proof of address, income or net worth documents, and entity documents before step one. Surprise document requests are the biggest single source of abandonment.
- Offer every verification route your counsel approves. Third-party letters from a CPA, attorney, RIA or broker-dealer are often faster for high-net-worth investors than uploading statements. Where counsel approves a high-minimum approach under C&DI 256.36, say so clearly.
- Separate "identity done" from "wallet done." Let investors finish KYC and sign subscription documents first. Then offer a custodial wallet option for those who do not want to manage keys.
- Explain lockups and controller powers in plain English. State the holding period, what the transfer agent can do, and how lost-key recovery works. Put it in the FAQ, not only in the PPM.
- Trigger nurture on every stalled state. Use separate follow-ups for "started KYC, did not finish," "KYC passed, accreditation pending," "verified, not funded" and "funded, wallet not whitelisted." Each needs a different message and often a human call.
- Measure the funnel by compliance stage. Track conversion from lead to KYC start, KYC pass, accreditation pass, signed and funded. That shows you whether your problem is traffic quality or onboarding friction.
For the broader picture of why tokenized raises stall, see why investors don't buy tokenized offerings. For planning these steps into a launch, see our 90-day tokenized offering launch plan. The tokenization hub at growthturbine.com/tokenization collects every guide in this series.
Frequently Asked Questions
Does the issuer or the platform do KYC in a security token offering?
In most US tokenized offerings, the broker-dealer or platform affiliate that onboards investors runs the formal AML and Customer Identification Program under FinCEN rules and FINRA Rule 3310. The issuer remains responsible for its own exemption conditions, such as verifying accredited status in a 506(c) raise. Many issuers rely on the platform for both but should confirm the split in writing.
What is wallet whitelisting for security tokens?
Whitelisting means the token contract only allows transfers to wallets linked to a verified investor identity. In ERC-3643, an Identity Registry maps each wallet to an identity contract holding signed claims such as KYC and accreditation. Any transfer to an unverified wallet fails automatically.
How long are tokenized Reg D securities locked up?
Securities sold under Rule 506 are restricted, and Rule 144 requires a minimum six-month holding period for reporting issuers and one year for non-reporting issuers before resale under that rule. Most private issuers are non-reporting, so one year is the common default. Counsel may identify other resale exemptions, and the token contract typically enforces the lockup by date.
Can a security token be recovered if an investor loses their private key?
Yes, if the token standard supports it. ERC-3643 includes a recoveryAddress function that moves a verified investor's balance to a new wallet and records the recovery on-chain, and ERC-1644 provides controller transfers in ERC-1400 tokens. Recovery normally requires the investor to re-verify their identity with the transfer agent or platform.
Do OFAC sanctions apply to crypto wallet addresses?
Yes. OFAC says sanctions obligations are the same for digital currency as for fiat, and it may list specific digital currency addresses on the SDN List. OFAC also warns those address listings are not exhaustive, so platforms typically combine list screening with blockchain analytics and can freeze tokens if a holder is later designated.
Turn compliant onboarding into funded investors
Compliance is fixed. Conversion is not. Growth Turbine builds the investor acquisition side of tokenized raises: landing pages that pre-qualify, onboarding messaging that explains KYC, accreditation and lockups in plain English, and nurture sequences triggered at each compliance stage. We are a marketing services provider only. We work alongside your counsel, your transfer agent and your platform's licensed broker-dealer, and we do not run the offering or give legal advice. Growth Turbine has supported 200+ campaigns and has provided marketing support across more than $540M in issuer-reported totals. See our tokenization of RWA marketing service and security token sale marketing, or contact us to map your onboarding funnel.
Disclaimer: The information provided in this article is for educational and informational purposes only and does not constitute legal, financial, or investment advice. Always consult with qualified legal counsel and financial advisors before launching a capital raise.



