Customer Identification Program field checks, recording an OFAC result screened elsewhere
One command in the Onboarding pack, available in the CLI, as an MCP tool and as a JavaScript import: onboarding validate-cip.
What it needs, and why
Every input is checked before anything is calculated. applicant and ofacStatus are required; the rest refine the answer.
| Input | Required | The question it asks | Why it matters |
|---|---|---|---|
applicant | yes | What are the applicant details: legal name, taxpayer identification number, date of birth and residential address? | These are the CIP elements. |
ofacStatus | yes | Has an OFAC/SDN screen been run for this applicant, and what was the result? | The library performs no screening; without a result CIP fails as not screened. |
Requests it answers
- “can we open this account”
- “is this application complete”
- “CIP check”
An agent with this pack loaded picks the command from phrasing like that, asks for whatever input is missing, and reports the figures with the method that produced them.
Run it
node bin/wealth-skills.js onboarding validate-cip --applicant '{"name":"Jane Doe","ssn":"123-45-6789","dob":"1990-05-15","address":"456 Elm St","ofacStatus":"CLEAR"}'Limits it inherits from wealth-onboarding
ofacStatusmust come from an actual sanctions screen. If it is missing, CIP fails withNOT_SCREENED; never fill it in to make the check pass.- The SSN check validates format only, not issuance or ownership.
- A passing result means the required fields are present and well-formed, not that the applicant's identity is verified.
The full pack, its other 1 command and what it deliberately leaves alone are on the Onboarding page.