By the APAC Compliance Lead, UWAY Innovation. Operational guidance, not legal advice.
An auditor asks a fund manager: why was this wallet allowed to hold the token? The file contains an onboarding form and a screenshot of the address. It does not show who approved the address, which restriction was checked or when the record was last reviewed.
That is a different problem from a stablecoin remittance corridor, where the concern is who is responsible at each handoff. For tokenized securities the control has to survive the transaction. Someone must maintain the link between a wallet, its verified controller, the holder's legal interest and the rules for this particular security.
The transfer ends. The register stays.
The FATF virtual-asset guidance distinguishes virtual assets from financial assets already covered elsewhere in its standards. Tokenisation alone does not determine the classification. If a security falls outside that virtual-asset framework, that is not a blanket exemption from AML/CFT or transfer-information duties. Map the security, any payment leg and the entities involved separately. The APAC Travel Rule guide covers a different question: obligations where the relevant virtual-asset transfer rules do apply.
The distinction matters for the register. An allowlist is a technical permission: which addresses a contract will accept. A record of legal ownership answers a different question. Depending on the structure, they may be linked, but the allowlist is not automatically the authoritative register.
What Hong Kong, Singapore and the US actually say
Hong Kong. For tokenised SFC-authorised investment products, SFC circular 26EC22, paragraphs 10–11, places ultimate responsibility for the tokenisation arrangement and ownership recordkeeping with the product provider, even when operations are outsourced. Paragraphs 13 and 17 address controls for permissionless networks and disclosure of where settlement is final. The intermediary circular 23EC53 separately addresses intermediaries' responsibilities, including those substantially involved in issuance.
Singapore. The MAS guide on tokenised capital markets products starts with the economic substance of the instrument. Existing requirements continue to apply to a capital markets product whether or not it is tokenised. Identify the parties and responsibilities under the applicable offering, custody and dealing arrangements rather than assuming that the platform running the chain also keeps the legal record. For the onboarding dimension, see how Hong Kong and Singapore differ on KYC/KYB.
United States. The SEC staff statement of 28 January 2026 distinguishes issuer-sponsored and third-party structures. In one issuer-sponsored model, a transfer on the network updates the master securityholder file, with on-chain and off-chain information linked. In a third-party structure, the token holder may instead have an interest through custody or exposure under a different instrument. The staff statement describes these models; it is not a rule that every wallet is a legal holder.
In the EU, MiCA, Article 2, excludes crypto-assets that qualify as financial instruments from its scope. The DLT Pilot Regime is a separate framework for qualifying DLT market infrastructure. The classification comes first; the technology label does not settle it.
Investor eligibility and KYC answer different questions
Investor eligibility is product- and transaction-specific: may this person participate, under which offering conditions, and on what evidence? Customer due diligence identifies and assesses the customer and, where relevant, the beneficial owners. Suitability and risk disclosures may also apply. A current passport does not prove investor eligibility, and an eligibility document does not replace identity and risk checks.
Keep the evidence, approver and review trigger separate even when the same team handles both. A change in investor status can require an eligibility review; a sanctions match or a change in beneficial ownership can trigger a CDD review. The cross-border KYC/KYB operating model explains how to retain a usable trail across teams.
A permissioned token can enforce a check, not assign accountability
ERC-3643 illustrates the difference. The specification links a wallet to an on-chain identity in the Identity Registry and defines separate compliance checks for ordinary transfers. Its specified mint and forced-transfer operations still check the recipient's registry status but do not run the same compliance rules as an ordinary transfer. That is a property of the specification, not a guarantee about every deployment or about who may change the registry.
Document who can add and remove addresses, change trusted claims or exercise exceptional transfer powers. Test what happens when the underlying eligibility or identity evidence expires. A registry entry is evidence that the system accepted an address; it is not, by itself, evidence of why a person was authorised to hold the security.
Secondary trading exposes the handoff
SFC circular 26EC23 sets conditions for secondary trading of tokenised SFC-authorised investment products, including client risk confirmation by licensed VATPs and connecting brokers before onboarding for that trading. Risk confirmation, investor eligibility and reconciliation of ownership are distinct. The circular should be read with the other SFC requirements and the terms of the product; it does not establish that nobody is responsible for secondary-buyer eligibility.
The operating question is what information the broker, platform and product provider actually exchange. Agree who verifies an incoming holder where needed, how the holder's status reaches the relevant register, what happens when a transfer is rejected or cannot be matched, and which party signs the reconciliation.
Five records the operator should be able to produce
- Entry decision. Connect the address to the person or entity and record the product-specific eligibility evidence where applicable.
- Approval trail. Record who added, changed or removed an entry, under which authority and with what independent review.
- Separate review triggers. Track identity and risk changes separately from eligibility conditions or expiry dates.
- Reconciliation. Compare the authoritative ownership record with on-chain state on a defined schedule. Name the person responsible for exceptions and sign-off.
- Handoff and exit. Record transfers or changes that require notification, renewed verification or post-onboarding monitoring.
The question is not just whether the wallet passed a check. It is whether a named party can explain why that address was allowed to hold the product, point to the evidence and show that the record is still current.
