Compliance Infrastructure10 min read
MB
Editorial Team
·June 28, 2026·Updated November 5, 2026

KYC/AML in Layer-0 Compliant RWA Tokenization: How Blockmaze Enforces Identity at Protocol Level

KYC/AML enforcement in RWA tokenization means binding the result of customer due diligence and sanctions screening to the token, so a transfer to an unverified wallet fails instead of being caught later. Where the check runs, in a front end, the token contract or the chain, decides which transfers can get around it.

TL;DR — Key Takeaways

  • ✓Due diligence: FATF Recommendation 10 sets four CDD measures: verify the customer, identify the beneficial owner, understand the relationship and monitor it. For virtual asset service providers the occasional-transaction CDD threshold is USD/EUR 1,000.
  • ✓Token checks: An ERC-3643 transfer fails unless the receiver is verified in the Identity Registry and the compliance contract approves. Agent mint and forcedTransfer bypass the compliance rules; burn bypasses all eligibility checks.
  • ✓EU refresh cycle: From 10 July 2027, AMLR Article 26 caps the gap between customer-information updates at 1 year for higher-risk customers and 5 years for all others.
  • ✓Entity investors: Both the US CDD rule (31 CFR 1010.230) and AMLR Article 52 use a 25% ownership threshold. FinCEN's February 13, 2026 order ended routine re-verification at each new account.
  • ✓Records: FATF Recommendation 11 and AMLR Article 77 require CDD records for at least five years after the relationship ends; the AMLR then requires deletion of personal data, which keeps identity files off-chain.

Ready to get started?

Join others who are already using our platform.

KYC/AML in Layer-0 Compliant RWA Tokenization: How Blockmaze Enforces Identity at Protocol Level

Where can KYC/AML be enforced in a tokenized RWA stack?

In three places: the investor-facing front end, the token contract, or the chain's own transaction rules. A front-end check stops only users of that front end. A contract check, as in ERC-3643, runs on every transfer call. A chain-level rule covers every contract on the network, but only where the chain implements one.

None of these layers performs know-your-customer (KYC) or anti-money-laundering (AML) work itself. Identity checks, beneficial-owner mapping and sanctions screening happen off-chain, run by the issuer, its transfer agent or a KYC provider. What the stack decides is how that result is enforced: as a gate in a web form, as a condition in the token's code, or as a rule the network applies before it accepts a transaction.

Enforcement pointWhat it checksWhat gets around it (our analysis)
Front end only (plain ERC-20)Login and KYC status before the app builds a transactionAny direct call to the token contract, any other wallet interface, any DEX pool
Token contract (ERC-3643)Receiver verified in the Identity Registry; compliance modules approve the transferAgent functions (mint, forcedTransfer, burn); a verified wrapper or bridge contract that issues its own unrestricted token
Chain-level ruleNetwork-wide conditions applied before a transaction is acceptedWhatever the chain's governance allows; activity on other chains the asset is bridged to

The common weak point is the boundary, not the check. A contract that enforces identity on its own transfers still has no say over a second token issued against it. The trade-offs between contract rules and chain-level governance are set out in our guide to smart contract compliance versus Layer-0 governance for RWA.

What does ERC-3643 check on every transfer, and what does it skip?

A standard ERC-3643 transfer requires the receiver to be verified in the Identity Registry and the compliance contract to approve, or the call reverts. Agent functions are treated differently: mint and forcedTransfer bypass the compliance rules, and burn bypasses all eligibility checks.

ERC-3643 is a Final Standards Track ERC, created on July 9, 2021. Its Identity Registry links a wallet address to an Identity contract and a country code. The isVerified() function checks that the Identity contract holds claims for the topics listed in the Claim Topics Registry, signed by issuers listed in the Trusted Issuers Registry. In the sample code, a failed identity check reverts with “ERC-3643: Invalid identity” and a failed rule check with “ERC-3643: Compliance failure”.

Two consequences follow. First, the token never sees the KYC file. It sees a signed claim that a trusted issuer made about an identity, so the quality of the check depends on who signs claims and when those claims expire. Second, the agent role sits outside parts of the rule set. Anyone holding an agent key can place tokens in a verified wallet that breaks a country or balance limit, or burn a position with no eligibility check at all. Who holds those keys, and under what controls, is covered in who really controls an ERC-3643 token's agent keys.

“... the mint function and the forcedTransfer function only require the receiver to be whitelisted and verified on the Identity Registry (they bypass the compliance rules). The burn function bypasses all checks on eligibility.”

ERC-3643: T-REX, Token for Regulated EXchanges (Ethereum Improvement Proposals)

What due diligence do FATF and the EU require before a wallet is verified?

FATF Recommendation 10 sets four customer due diligence (CDD) measures: verify the customer, identify the beneficial owner, understand the purpose of the relationship and monitor it on an ongoing basis. For virtual asset service providers, the occasional-transaction threshold that triggers CDD is USD/EUR 1,000.

The FATF Recommendations, most recently updated in October 2025, require verification using “reliable, independent source documents, data or information”, before or during the start of the relationship. If a firm cannot complete CDD, it should not open the account or should end the relationship, and should consider a suspicious transaction report. The Interpretive Note to Recommendation 15 applies Recommendations 10 to 21 to virtual asset service providers and sets their occasional-transaction CDD threshold at USD/EUR 1,000, against USD/EUR 15,000 for other financial institutions.

In the EU, the Anti-Money Laundering Regulation, Regulation (EU) 2024/1624 (AMLR), turns these duties into directly applicable law from 10 July 2027. Article 26 makes ongoing monitoring explicit and caps how stale customer information may get. For a permissioned token, that cap is a design input: an identity claim that stays valid longer than the update interval lets a wallet keep trading on information the issuer was required to refresh. Sanctions are a separate, faster trigger. A screening hit that leads to a freeze starts its own deadlines, set out in what an issuer must report after freezing sanctioned tokens.

“The period between updates of customer information ... shall be dependent on the risk posed by the business relationship and shall not in any case exceed: (a) for higher risk customers to which measures under Section 4 of this Chapter apply, 1 year; (b) for all other customers, 5 years.”

Regulation (EU) 2024/1624, Article 26(2)

How are legal-entity investors and their owners verified?

By identifying the people behind the entity. The US customer due diligence rule (31 CFR 1010.230) and EU AMLR Article 52 both set 25% ownership as the threshold, next to a control test. A FinCEN order dated February 13, 2026 relaxed when US institutions must repeat the check.

Under 31 CFR 1010.230(d), a beneficial owner is each individual who directly or indirectly owns 25 percent or more of a legal entity customer's equity, plus a single individual with significant responsibility to control, manage or direct it. AMLR Article 52 uses direct or indirect ownership of 25% or more of shares, voting rights or other ownership interest. Indirect stakes are calculated by multiplying holdings through each chain of entities and adding the chains together, and every level of ownership counts.

FinCEN's exceptive relief order means covered US institutions no longer have to re-identify and re-verify beneficial owners each time an existing legal entity customer opens another account. They still must do so at the first account, when they have reason to doubt the information held, and when their risk-based ongoing due diligence calls for it.

On-chain, an entity investor appears as one wallet with one identity claim. The ownership chart, the individuals above the 25% line and the evidence for each sit with the claim issuer or the issuer's register. Keeping that register and the wallet mapping in step is the subject of our best practices for compliant RWA issuer registries.

Does the travel rule apply to tokenized securities transfers?

Not to the security leg in the EU. Regulation (EU) 2023/1113 has applied the travel rule to crypto-asset transfers since 30 December 2024, regardless of amount, but it excludes what MiCA excludes, and MiCA Article 2(4) excludes financial instruments. A token that is a financial instrument sits outside that regime.

The Transfer of Funds Regulation, Regulation (EU) 2023/1113, defines a crypto-asset by reference to MiCA, Regulation (EU) 2023/1114, “except where falling within the categories listed in Article 2(2), (3) and (4)” of MiCA. For crypto-assets in scope, Article 14 requires the originator's name, distributed ledger address, and either address with official document number and customer number or date and place of birth, plus the LEI where available. For a transfer of more than EUR 1,000 to a self-hosted address, the sending provider must assess whether the originator owns or controls that address.

Our reading, not legal advice: for a tokenized bond or fund unit, both parties are already identified through the token's identity registry, which covers much of what the travel rule aims at, but securities-law transfer and register rules apply instead. The cash leg is different. If settlement uses a crypto-asset within MiCA's scope and a crypto-asset service provider handles it, that leg can fall under Article 14, even though the security leg does not.

What records must the KYC process keep, and for how long?

At least five years. FATF Recommendation 11 requires CDD records for at least five years after the relationship ends, and AMLR Article 77 fixes 5 years from termination, then requires personal data to be deleted. A ledger that cannot delete data should therefore hold references to KYC files, not the files.

FATF Recommendation 11 also requires transaction records detailed enough to reconstruct individual transactions as evidence. AMLR Article 77(2) lets obliged entities keep references to information instead of copies, provided the method ensures the information can be produced immediately and “cannot be modified or altered”. That fits a common token design: identity documents stay with the KYC provider, the claim on-chain carries a hash or reference, and the issuer can rebuild who held what, when.

“Financial institutions should be required to keep all records obtained through CDD measures ... for at least five years after the business relationship is ended, or after the date of the occasional transaction.”

FATF Recommendations, Recommendation 11 (updated October 2025)

The deletion duty after 5 years is where permanent ledgers and AML law pull in opposite directions. How to split what goes on-chain from what stays off-chain is covered in our guide to immutable audit trails for RWA compliance.

Which parts of this does the Blockmaze protocol handle?

Issuer-level checks, not investor KYC. Blockmaze's public site describes identity verification and a BMZ bond for issuers at admission, a BMZ3643 template for registry-dependent title assets, and an on-chain record of issuer status changes. It does not describe investor KYC, AML screening or sanctions monitoring.

In practice, investor due diligence, beneficial-owner mapping, sanctions screening, record retention and any reports to authorities stay with the issuer, its transfer agent and its KYC and screening providers. A token template can enforce their result on every transfer; it cannot replace the people the AML rules name as responsible. This article is not legal advice, and the rules that apply depend on the jurisdiction and the legal form of each token.

Sources: FATF Recommendations (updated October 2025); Regulation (EU) 2024/1624 (AMLR); Regulation (EU) 2023/1113 (Transfer of Funds Regulation); Regulation (EU) 2023/1114 (MiCA); 31 CFR 1010.230; FinCEN exceptive relief release, February 13, 2026; ERC-3643 specification; blockmaze.org. Sources checked November 5, 2026. The enforcement-point comparison, the travel-rule reading for security tokens and the design recommendations are editorial analysis. Not legal advice.

Frequently Asked Questions

What is the difference between front-end, contract-level and chain-level KYC enforcement?

A front-end check only stops people who use that website or app; anyone can still call a plain ERC-20 contract directly. A contract-level check, as in ERC-3643, runs inside the token's transfer function, so every transfer call is tested against the identity registry. A chain-level rule applies to all contracts on a network, but only where the chain implements one. None of the three performs due diligence itself; each enforces a result produced off-chain.

Can ERC-3643 tokens reach an unverified wallet?

Not through a normal transfer: the sample transfer function requires isVerified on the receiver and reverts with "ERC-3643: Invalid identity" if the check fails. Agent functions differ. The specification says mint and forcedTransfer only require the receiver to be verified and bypass the compliance rules, such as country or balance limits, while burn bypasses all eligibility checks. The practical gap is therefore agent-key control, not the identity check on ordinary transfers.

How often must investor KYC information be refreshed under the EU AMLR?

Article 26(2) of Regulation (EU) 2024/1624 says the period between updates of customer information depends on risk and must not exceed 1 year for higher-risk customers under enhanced due diligence, and 5 years for all other customers. Article 26(3) adds earlier reviews when a customer's relevant circumstances change. The regulation applies from 10 July 2027, so token claim expiry dates should be set no later than these intervals.

What ownership threshold triggers beneficial-owner checks for entity investors?

25%. The US customer due diligence rule at 31 CFR 1010.230(d) covers each individual who directly or indirectly owns 25 percent or more of a legal entity customer's equity, plus one individual with significant control. EU AMLR Article 52 uses direct or indirect ownership of 25% or more of shares, voting rights or other ownership interest, counted through every level of the ownership chain. Control by other means is tested in parallel.

Does the EU travel rule cover tokenized securities?

Generally not the security leg. Regulation (EU) 2023/1113, applicable from 30 December 2024, defines crypto-assets by reference to MiCA and excludes the categories MiCA excludes. MiCA Article 2(4) excludes crypto-assets that qualify as financial instruments. A tokenized bond or fund unit that is a financial instrument therefore falls outside the crypto travel rule, while a crypto-asset used as the cash leg may still be in scope.

How long must KYC records for token investors be kept?

At least five years. FATF Recommendation 11 requires CDD records for at least five years after the business relationship ends. EU AMLR Article 77 sets 5 years from the end of the relationship, then requires personal data to be deleted unless another law requires longer retention. Because a public chain cannot delete data, the identity documents belong off-chain, with only claims or references recorded on the ledger.

Ready to get started?

Join others who are already using our platform.