AML full screening
Available on request. Regular AML screening with sanctions, PEP and adverse media, search datasets, a match threshold and ongoing monitoring
Available on request. Contact IDCanopy for access; details may change.
This section documents full AML screening, the regular tier: screening a person against sanctions, politically exposed persons and adverse media, with search controls and rich hit records, plus ongoing monitoring of people and entities.
Full AML is available on request: contact IDCanopy for access. Test implementations may exist, but no contract is published yet. Every path, field and example here follows the data provider's model plus our design and is to be defined with the contract. Do not code against it.
Full AML gets its own paths, separate from AML light.
Full or light
| AML light | AML full screening | |
|---|---|---|
| Status | Published specification; the tier to integrate today | Available on request |
| Search input | name + dob | Name, date of birth, countries, datasets, threshold and matching |
| Result | foundRecords list (sourceType, pepType, and so on) | Best-match person profile with rich hit records |
| Monitoring | Register by profileId with names | Available on request; registration shape to be defined with the contract |
What full screening adds
- More than a name. The request carries search constraints: a country focus, the datasets to search, a match threshold between 75 and 100, and a fuzzy or strict name match.
- Richer hit records. A best-match profile with names and aliases, dates of birth and death, nationalities, addresses, contact details, supporting evidence, sanctions, PEP, profiles of interest, regulatory and reputational entries, and linked individuals and businesses.
- Ongoing monitoring. Register individuals and entities for periodic re-screening, remove a profile, and query the matches found since registration.
Pages
- Screening an individual: the check request, the datasets, the threshold and the matching modes.
- Hit records: the fields of a returned profile.
- Ongoing monitoring: register an individual or an entity, and remove a profile.
- Query monitoring results: the alerts found for a registered profile.
Open questions
The contract will define:
- The wire field names and types, where the retired guide and the published light specification disagree.
- The registration and monitoring-result shapes, and the path of every operation.
- Authentication for full AML.
- The source's own inconsistencies, shown on the pages that carry them:
countriesas a string or an array; the individual registration nested underdataagainst a flat entity registration; the event key spelling (dateIsoandevidenceIdsagainstdateISOandevidenceIDs); and the REL/RREeventscollection as a string array or an object array. - The shape of an entity monitoring alert.
Contract status
The paths stay unset here: each operation names no path and says "path to be defined (separate from AML light)". The registration and result shapes are to be defined with the contract. The reference carries no operations yet.