CIP Identification Documents Lookup
Exact independently verified CIP identification documents reference registry lookup in explicit institution, customer type, jurisdiction and rule context, retaining source and as-of date. Caller supplies the actual applicable record, including qualifications, exceptions and uncertainty; illustrative examples are not authoritative records. No built-in complete/current data, eligibility, authenticity, legal/coverage determination or advice.
Description
Customer identification requirements depend on institution, customer and applicable authority.
Customer identification requirements depend on institution, customer and applicable authority.1
A dated reference preserves accepted-document context without verifying a person's identity. Use CIP Identification Documents Lookup to retrieve an exact caller-supplied reference entry.
When to use CIP Identification Documents Lookup
Use CIP Identification Documents Lookup to retrieve an exact caller-supplied reference entry. Choose the relevant jurisdiction, transaction or institution context; review the source, record its as-of date and supply the reference entries.
How to use CIP Identification Documents Lookup and understand its results
- Choose the relevant jurisdiction, transaction or institution context; review the source, record its as-of date and supply the reference entries.
- Enter Caller verified source, Caller verified context, Caller verified as of date, Caller reference keys, Caller reference texts, Query reference key using the field table and validation rules below, then run the tool.
- Read Matched Caller Reference, Source, Context, As Of Date in the Result object; interpret the units, signs, ordering and unknown-value placeholders described below.
- Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSource | Caller verified source | string | Required; constraints below |
| callerVerifiedContext | Caller verified context | string | Required; constraints below |
| callerVerifiedAsOfDate | Caller verified as of date | string | Required; constraints below |
| callerReferenceKeys | Caller reference keys | array of string | Required; constraints below |
| callerReferenceTexts | Caller reference texts | array of string | Required; constraints below |
| queryReferenceKey | Query reference key | string | Required; constraints below |
Provide aligned, nonempty arrays of reference keys and independently verified notices, then enter the exact query key. Keys must be unique, nonblank and at most 128 UTF-16 code units long; notices must be nonblank. Matching is case sensitive and does not trim the query or returned text. The matching notice is returned unchanged; an unknown key is an input error. The reference contents and their applicability are supplied by the caller; the tool does not retrieve external records or verify source authority. Also supply nonblank source and context identifiers of at most 256 UTF-16 code units each and a real Gregorian YYYY-MM-DD as-of date in years 0001 through 9999. Source, context and asOfDate are returned unchanged alongside the matched reference. The date is validated, but no freshness or current-law check occurs.
matched reference = suppliedTexts[indexOfExactQueryKey(suppliedKeys)] Use the field order, units and branch conditions described above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Object containing the named result fields below. | object |
| result.matchedCallerReference | Caller reference text matched exactly by key, unchanged. | string |
| result.source | Caller source identifier, unchanged and unverified. | string |
| result.context | Caller context identifier, unchanged and unverified. | string |
| result.asOfDate | Caller Gregorian as-of date, validated as a date but not checked for freshness. | string |
{
"input": {
"callerVerifiedSource": "independently-reviewed-source/edition",
"callerVerifiedContext": "institution, customer type, jurisdiction and rule",
"callerVerifiedAsOfDate": "2026-01-01",
"callerReferenceKeys": [
"record-a",
"record-b"
],
"callerReferenceTexts": [
"Caller independently verified CIP identification documents record a",
"Caller independently verified CIP identification documents record b"
],
"queryReferenceKey": "record-a"
},
"output": {
"result": {
"matchedCallerReference": "Caller independently verified CIP identification documents record a",
"source": "independently-reviewed-source/edition",
"context": "institution, customer type, jurisdiction and rule",
"asOfDate": "2026-01-01"
}
}
}Limitations and assumptions
A dated reference preserves accepted-document context without verifying a person's identity. Apply the exact scope and assumptions explained above.
All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.
Alternative or Complementary methods
Use HMDA LAR Reportable Field Count Lookup for a related task: HMDA reporting fields depend on the reporting year's specification and institution context.
Use EDD Trigger Checker for a related task: Enhanced due diligence triggers depend on the institution's applicable risk policy.
References
-
CIP Identification Documents Lookup — tool.io
Similar or alternative tools
- HMDA LAR Reportable Field Count Lookup
HMDA reporting fields depend on the reporting year's specification and institution context.
- EDD Trigger Checker
Enhanced due diligence triggers depend on the institution's applicable risk policy.