Can a Tokenized Fund Rely on Another Firm's KYC?
CIP reliance is the provision in 31 CFR 1024.220(a)(6) and 1023.220(a)(6) that lets a US mutual fund or broker-dealer rely on another financial institution to perform steps of its customer identification program. It works only if the reliance is reasonable, the other firm is subject to a BSA anti-money laundering program rule and a federal functional regulator, and it certifies annually under a contract. An on-chain KYC credential meets none of the three conditions by itself.
TL;DR — Key Takeaways
- ✓Three conditions: Under 31 CFR 1024.220(a)(6) and 1023.220(a)(6), reliance must be reasonable, the other institution must be subject to a 31 U.S.C. 5318(h) program rule and a federal functional regulator, and it must contract to certify annually.
- ✓Same customer: Reliance covers only a customer who is opening, or has opened, an account or similar business relationship with the other institution. A wallet that a vendor screened once is not that.
- ✓Advisers: FinCEN delayed the investment adviser AML rule from January 1, 2026 to January 1, 2028. Our inference: until then, an adviser does not meet condition (ii). Confirm with counsel.
- ✓On-chain gap: An ERC-3643 isVerified check proves a trusted issuer signed a claim. It does not prove a reliance contract or this year's certification exists. Keep that evidence off-chain and link it to each trusted issuer.

What does the CIP reliance provision allow?
It lets a mutual fund or broker-dealer write into its customer identification program (CIP) that another financial institution, including an affiliate, will perform some or all CIP steps for a shared customer. It is permissive: the CIP “may include” such procedures, and only on three conditions.
The Bank Secrecy Act (BSA) requires covered financial institutions to run an anti-money laundering (AML) program. FinCEN's CIP rules then set the minimum identity steps: collect name, date of birth for an individual, address and an identification number before opening an account; verify identity within a reasonable time; check government terrorist lists; give customers notice; and keep records. The mutual fund version is 31 CFR 1024.220. The broker-dealer version is 31 CFR 1023.220. Both end with a paragraph (a)(6) on reliance.
A tokenized fund falls under the mutual fund rule only if it is a mutual fund in FinCEN's sense. Section 1010.100(gg) defines that as an open-end investment company that is registered, or required to register, with the SEC under the Investment Company Act. A registered tokenized money market fund fits. A private fund or a closed-end fund does not fit that definition, so this article's mutual fund analysis does not apply to it directly.
“The CIP may include procedures specifying when a mutual fund will rely on the performance by another financial institution (including an affiliate) of any procedures of the mutual fund's CIP...”
31 CFR 1024.220(a)(6), eCFR
What are the three conditions, word for word?
Reliance must be reasonable under the circumstances; the other institution must be subject to a rule implementing 31 U.S.C. 5318(h) and regulated by a federal functional regulator; and it must sign a contract to certify annually. All three must hold at once.
The mutual fund text in 1024.220(a)(6) reads:
- (i) “Such reliance is reasonable under the circumstances;”
- (ii) “The other financial institution is subject to a rule implementing 31 U.S.C. 5318(h) and is regulated by a Federal functional regulator; and”
- (iii) “The other financial institution enters into a contract requiring it to certify annually to the mutual fund that it has implemented its anti-money laundering program, and that it (or its agent) will perform the specific requirements of the mutual fund's CIP.”
The broker-dealer text in 1023.220(a)(6) is nearly the same. Its condition (iii) says the other institution “will perform (or its agent will perform) specified requirements of the broker-dealer's CIP.” Section 1010.100(r) lists the federal functional regulators: the Federal Reserve Board, the OCC, the FDIC board, the Office of Thrift Supervision, the NCUA, the SEC and the CFTC.
Two features matter for token programs. First, the contract is with the other financial institution, and the certification runs every year. A one-time onboarding agreement with no annual certification does not match the text. Second, the word “agent” appears in condition (iii). The relied-on institution may use a vendor to do the work. The vendor does not replace the regulated institution as the party that certifies.
“The other financial institution is subject to a rule implementing 31 U.S.C. 5318(h), and regulated by a Federal functional regulator.”
31 CFR 1023.220(a)(6)(ii), eCFR
Whose customer does the investor have to be?
Both: a customer of the fund and of the relied-on institution. The mutual fund rule covers a fund customer who is opening, or has opened, an account or has a “similar formal business relationship” with the other institution.
The broker-dealer rule uses “has established an account or similar business relationship with the other financial institution to provide or engage in services, dealings, or other financial transactions.” Either way, the shared customer is the hook. Reliance is built for distribution chains where the investor already banks or trades with the distributor.
Tokenized distribution can break that link. Our reading of the text, not a regulator's statement: three common patterns sit outside it.
- Secondary transfers. A wallet buys fund tokens from another holder. The buyer may never have had an account with the distributor that onboarded the seller.
- Credential portability. An investor presents a KYC claim issued for a different platform. The claim issuer may have checked the person without opening any account for them.
- Vendor-only checks. An identity vendor runs document and liveness checks and issues a claim. The vendor has no account relationship with the investor in the BSA sense, and is not itself a financial institution with a 5318(h) program.
In each case the fund may still need to run its own CIP steps, even though the token contract will accept the wallet. How identity claims flow through an onboarding workflow is laid out in our guide to KYC and AML at the Layer-0 level for RWA tokenization.
Which firms can a tokenized fund rely on?
US banks with a federal functional regulator, SEC-registered broker-dealers and other mutual funds can meet condition (ii). Trust companies without a federal functional regulator, investment advisers before 2028, offshore administrators and KYC vendors do not, on our reading.
Condition (ii) is the filter most token programs fail. The table maps common parties against it. Condition (i), reasonableness, is a facts-and-circumstances test, and condition (iii) depends on whether a contract is signed, so those columns say what must be checked rather than give a yes or no.
| Potential relied-on party | (ii) 5318(h) rule and federal regulator | (i) and (iii) to check |
|---|---|---|
| Bank regulated by the Fed, OCC, FDIC or NCUA | Can meet it: 31 CFR 1020.210(a) covers banks regulated by a federal functional regulator | Investor is the bank's customer; signed contract with annual certification |
| Bank or trust company lacking a federal functional regulator | Fails the regulator half: 1020.210(b) names “certain trust companies” among banks lacking one | Not reached; check each charter, since some trust companies do have a federal regulator |
| SEC-registered broker-dealer | Can meet it: 31 CFR 1023.210 program rule, SEC is a listed regulator | Investor has an account with it; contract names which CIP steps it performs |
| Another mutual fund, including an affiliate | Can meet it: 31 CFR 1024.210 program rule, SEC is a listed regulator | Shared shareholder; annual certification even inside one fund complex |
| SEC-registered investment adviser | Inference: fails until January 1, 2028, because the adviser AML rule is not yet effective | Revisit when the rule takes effect, and track any change FinCEN makes to its scope |
| Offshore fund administrator or non-US bank | Inference: fails; 1010.100(t) defines financial institutions by offices “within the United States”, and none of the listed regulators supervises it | May still act as an agent of a qualifying US institution under (iii) |
| KYC vendor or on-chain claim issuer | Inference: fails; a vendor is not a financial institution with a 5318(h) program rule | Usable as the relied-on institution's agent, never as the party that certifies |
Readers who need the broader map of which controls sit in the token and which sit outside it should start with our guide to smart contract compliance and Layer-0 governance for RWAs. Reliance is a clear case of a control that lives entirely outside the contract.
Why can't a fund rely on its investment adviser yet?
Because the adviser AML rule is not in effect. FinCEN's final rule published January 2, 2026 (91 FR 36) delayed the effective date of the 2024 investment adviser AML and SAR rule from January 1, 2026 to January 1, 2028.
The 2024 rule, published September 4, 2024 at 89 FR 72156, defines certain investment advisers as financial institutions under the BSA and requires AML programs and suspicious activity reporting. FinCEN proposed the delay on September 22, 2025, after an exemptive relief order on August 5, 2025, and announced the final rule on December 31, 2025. FinCEN said the two years give it time to review the rule and tailor it to different adviser business models.
The conclusion for reliance is our inference, not a FinCEN statement. Condition (ii) asks whether the other institution “is subject to a rule implementing 31 U.S.C. 5318(h).” An adviser is regulated by the SEC, which is a listed federal functional regulator. But the rule that would make it subject to an AML program requirement does not take effect until 2028. Until then, a fund whose CIP relies on its adviser appears to fail condition (ii). The same final rule notes that commenters asked FinCEN to reissue the separate adviser CIP proposal alongside the AML rule, so the adviser picture may change again before 2028.
This matters most where the adviser runs the token program. In many tokenized fund launches the sponsor's adviser selects the onboarding vendor and signs the vendor contract. A fund that wants reliance needs a bank, broker-dealer or another mutual fund in the chain, or it performs the CIP steps itself, for example through its transfer agent and master securityholder file process.
“As of December 31, 2025, the effective date of the rule published September 4, 2024, at 89 FR 72156 is delayed until January 1, 2028.”
FinCEN final rule, 91 FR 36 (January 2, 2026)
What does an on-chain KYC check prove, and what does it miss?
An ERC-3643 isVerified check proves that an investor's identity contract holds the required claims, signed by an issuer in the Trusted Issuers Registry. It proves nothing about the issuer's regulator, a reliance contract or an annual certification.
The ERC-3643 specification says isVerified runs inside transfer, transferFrom, mint and forcedTransfer. It checks that the receiver's identity contains the claims listed in the Claim Topics Registry and that those claims are signed by an authorized claim issuer in the Trusted Issuers Registry. The token owner manages both registries and can add or remove trusted issuers.
That is a strong technical control, and it maps poorly to the reliance conditions. Each line below is our analysis:
- Condition (i), reasonable: the chain stores that a claim exists. It does not store why the fund judged the issuer's process adequate.
- Condition (ii), regulated institution: a trusted issuer is a contract address. Nothing on-chain says whether its operator is a bank, a broker-dealer or a vendor.
- Condition (iii), contract and annual certification: the registry has no field for a contract date or a certification due date. A claim can stay valid on-chain long after the certification lapsed.
- Shared customer: a claim attaches to an identity, not to an account relationship. The chain cannot show that the investor is the relied-on institution's customer.
Removing a trusted issuer when its certification lapses is not a clean fix either. If claims from that issuer are the only ones satisfying a required topic, every affected holder fails isVerified at once, and their positions stop being transferable until a new claim is issued. The related reading below on expired and revoked claims covers that failure mode in detail. Stablecoin issuers face a different version of the same question; see our analysis of FinCEN's 2026 AML proposal for permitted stablecoin issuers.
How should a fund link trusted issuers to reliance contracts?
Keep one off-chain record per trusted issuer that names the regulated institution behind it, the signed contract, the CIP steps covered and the next certification date. These are our recommendations, not FinCEN requirements.
The record turns the on-chain registry into something an examiner can test. Suggested fields:
- Issuer address and claim topics: the contract address in the Trusted Issuers Registry and the topics it may sign.
- Relied-on institution: legal name, institution type and federal functional regulator. For a vendor, the regulated institution it acts for.
- Basis: “reliance under 1024.220(a)(6)” or “fund performs CIP itself”. Never leave this blank.
- Contract and certification: contract date, CIP steps covered, last annual certification received and the next one due.
- Reasonableness memo: why the fund judged the reliance reasonable, dated and approved.
- Lapse plan: what happens to holders onboarded through this issuer if certification is missed, decided before it is missed.
An illustrative example, with invented numbers: a registered tokenized fund lists 3 trusted claim issuers. Issuer A is operated by an SEC-registered broker-dealer that distributes the fund and signs a reliance contract. Issuer B is a vendor acting for the fund's adviser. Issuer C is a vendor acting for an offshore administrator. If 600 of 1,000 holders were onboarded through A, only those 600 have a reliance basis on the table above. For the other 400, the fund performs and records its own CIP steps, even though all 1,000 wallets pass isVerified.
A compliance layer such as Blockmaze enforces eligibility at transfer time: which wallet, which identity, which claim. The legal basis for trusting the claim stays off-chain with the fund and the institutions it contracts with.
Who is this analysis for, and when does it not apply?
It is for sponsors, transfer agents and distributors of US registered funds and US broker-dealers. It does not cover non-US funds, MiCA crypto-asset service providers or retail stablecoin onboarding, which run under different identity rules.
- For: a registered open-end fund issuing tokenized shares through broker-dealers or banks, and broker-dealers distributing tokenized securities through other broker-dealers.
- Partly applicable: private funds. They are outside the 1010.100(gg) mutual fund definition, so 1024.220 does not apply to them, but a broker-dealer that distributes them still runs its own CIP under 1023.220.
- Not for: non-US funds under local AML regimes, MiCA crypto-asset service providers, and stablecoin issuers, which FinCEN addressed in a separate June 22, 2026 CIP proposal for permitted payment stablecoin issuers.
One pending change to watch: FinCEN's April 10, 2026 AML/CFT program proposal (91 FR 18704) would revise paragraph (a)(6)(iii) of both CIP rules so the annual certification refers to an “AML/CFT program”. The proposed text keeps the contract and annual certification. Nothing in this article is legal advice; the reliance conditions apply to specific facts, and counsel should confirm each relied-on party.
Sources: 31 CFR 1024.220, Customer identification programs for mutual funds (eCFR); 31 CFR 1023.220, Customer identification programs for broker-dealers (eCFR); 31 CFR 1010.100, General definitions (eCFR); 31 CFR 1020.210, AML program requirements for banks (eCFR); FinCEN, Delaying the Effective Date of the IA AML Rule, 91 FR 36; FinCEN press release, December 31, 2025; FinCEN, AML/CFT Programs proposed rule, 91 FR 18704; ERC-3643 specification. Sources checked November 3, 2026. The adviser conclusion, the party-by-party table entries marked as inferences, the mapping of on-chain checks to reliance conditions, the record fields and the illustrative example are editorial analysis, not FinCEN or SEC statements. Not legal advice.
Frequently Asked Questions
Can a tokenized money market fund accept investors that a broker-dealer already identified?
Yes, if the fund's written CIP says so and the three conditions in 31 CFR 1024.220(a)(6) are met. The reliance must be reasonable, the broker-dealer must be subject to a rule implementing 31 U.S.C. 5318(h) and regulated by a federal functional regulator, and it must sign a contract to certify annually. The investor must also be a customer of that broker-dealer, not only a wallet it once checked.
Can a fund rely on its investment adviser for CIP before 2028?
On our reading of the rule text, not under the reliance provision. Condition (ii) requires the other institution to be subject to a rule implementing 31 U.S.C. 5318(h). FinCEN's adviser AML rule was delayed to January 1, 2028 by a final rule published January 2, 2026. Until it takes effect, an adviser does not appear to meet that condition. This is an inference, not FinCEN guidance; confirm with counsel.
Does an ONCHAINID claim from a trusted issuer count as CIP reliance?
No. ERC-3643's isVerified check confirms that an investor's identity contract holds claims for the required topics, signed by an issuer listed in the Trusted Issuers Registry. It does not show that the issuer is a regulated US financial institution, that a reliance contract exists, or that this year's certification arrived. Those facts sit off-chain and must be documented separately.
Does relying on another institution move CIP liability away from the fund?
The rule does not say so, and it should not be assumed. Section 1024.220(a)(6) only permits the fund's CIP to include procedures for when the fund will rely on another institution's performance. The CIP stays the fund's program, and the conditions must hold for each relied-on firm. Whether reliance limits the fund's exposure in an examination is a question for counsel, not something the regulation states.
Would FinCEN's April 2026 AML program proposal change the reliance conditions?
The proposed text keeps the same structure. The April 10, 2026 proposal (91 FR 18704) would revise paragraph (a)(6)(iii) of both 1023.220 and 1024.220 so the annual certification refers to an AML/CFT program instead of an anti-money laundering program. The reasonableness and regulated-institution conditions are not in the amended text. It remains a proposal; comments closed June 9, 2026.
Related Articles
RWA Investor Onboarding: KYC/AML Process for Institutional Tokenized Asset Programs
Entity identification, UBO mapping, accredited investor verification, source-of-funds review and Travel Rule data collection required before the first token is issued to an institutional investor.
Can Expired KYC Make an ERC-3643 Position Unsellable?
ERC-3643 transfer checks can turn expired or revoked identity claims into a liveness dependency for tokenized securities.