Desk
For a broker-dealer
A FINRA/SEC AML officer needs CIP, a Travel Rule message, a customer rating and a 314 program. This origin prints a wallet screen and the Travel Rule fields the firm typed. It does not run 31 CFR 1023.220, does not transmit IVMS-101, and does not compare FinCEN 314(a).
What you can take off the print
“Verified by chainscore.net” means the address is in the label book. It is not documentary or non-documentary CIP. Record CIP method, who ran it and when on your own file. The print still says this origin did not run 31 CFR 1023.220.
When the Travel Rule indicator fires, name, address and account the firm typed print as a stated payload. Missing fields are not-established. This origin does not scrape names off the chain and does not transmit IVMS-101. You still send the message from the firm’s stack.
Occupation, TIN, filer and branch travel with stated identity onto the SAR packet if you typed them. chainscore.net does not e-file. The analyst re-keys into BSA E-Filing.
How to use it without making a hole
After you sign in, Screen is the path that files it. Run ScoreGuard on the wallet. Bind the wallet to a house account number and customer reference when you have them — they print when typed. If the house needs one artefact, bind the report to the procedure and download the sealed PDF. Read the coverage gate before the headline band.
Two wallets on one cash account still need a book inventory plus the house file. They are not one Holistix score.
OFAC and mixer findings bottom the score when they fire. Silence is not a pass — the not-established block says so. Use generated_at and the OFAC SDN publish date as a timestamp of the screen, not as a named “customer screened against SDN” CIP log line with the associated person who ran it.
ScoreGuard runs 1–100, lower is riskier. ChainTrace runs 0–100, higher is riskier. Holistix runs 0.0–10.0, higher is riskier. You get a wallet score and a coverage gate. You do not get a 3310 customer AML rating or a next-review clock. The house program still rates the customer.
What this origin will not be
Limits say this origin does not compare FinCEN 314(a) and does not run 314(b) sharing. Treating the screen as the whole 314 program is a hole.
Unhosted-wallet majority and the host field say when no obliged entity sits on the other side. They do not collect the originator information FinCEN expects the broker-dealer to hold for that transfer.
SHA-256 lets you prove the copy. It is not a 17a-4 WORM store. The broker-dealer’s own books-and-records still keep the PDF.