Licensed API · ongoing CDD · ODD · pKYC

VerifyNow AML for FICA ongoing due diligence

Enrol a person or company on VerifyNow AML through the licensed API, run the initial screen, then keep that customer on ongoing CDD and ongoing due diligence (ODD) against refreshed sanctions, PEP, crime and watchlist sources. Rescreen on your RMCP cadence. Screening supports CDD and enhanced due diligence (EDD) reviews after onboarding.

For FICA accountable institutions — banks, insurers, financial services, attorneys, estate agents, gambling operators, crypto and other Schedule 1 businesses — plus fintech, iGaming and marketplaces whose RMCP calls for post-onboarding screening.

Annual licence. First enrol on AML/PEP credits. Unlimited rescreens after that.

Request a licence Speak to a compliance specialist See coverage

VerifyNow AML licensed API: desktop POST /v1/aml/ongoing JSON, dataset-update webhook, and a phone reading SANCTIONS and PEP from a 200 response

Coverage and cadence

Lists, refresh and rescreen

Official UN, OFAC, UK and EU lists are checked every 60 minutes. Other lists refresh every six hours.

You enrol people and companies. VerifyNow AML screens those names against publisher lists that include persons, companies, entities, vessels and aircraft.

60m

UN, OFAC, UK and EU

Core TFS files are checked every 60 minutes. A dataset webhook notifies a list version change.

Other lists

Remaining publisher lists refresh every six hours. Sanctions, PEP, RCA, crime, wanted, regulatory and debarment categories are in scope.

Targeted financial sanctions (TFS)

FIC requires accountable institutions to screen against targeted financial sanctions (TFS). VerifyNow AML meets that requirement on customer screens with the United Nations, OFAC, UK, EU and Australian lists.

United Nations Security Council
United States OFAC SDN
United States OFAC consolidated
United Kingdom
European Union
Australia

Sources+

Core TFS lists

UN Security Council Consolidated Sanctions
US OFAC Specially Designated Nationals List
US OFAC Consolidated Non-SDN List
UK Sanctions List
EU Financial Sanctions Files
Australian Sanctions Consolidated List

South Africa

South Africa Wanted Persons
South Africa FSCA Enforcement Actions
South Africa Cabinet Ministers and Deputy Ministers
South Africa CIDB Removed Contractors
South Africa Companies Tribunal Decisions and Orders
South Africa Municipal Leadership
South Africa NCR Credit Providers Cancelled by Tribunal
South Africa Prudential Authority Administrative Sanctions
South Africa Register of Tender Defaulters
South Africa Restricted Suppliers

Sanctions

Argentina RePET Entities
Argentina RePET Persons
Austrian National Bank Terrorism Financing Restrictions
Belgian Consolidated Financial Sanctions
Canada Freezing Assets of Corrupt Foreign Officials: Tunisia
Canada Justice for Victims of Corrupt Foreign Officials Sanctions
Canada Listed Terrorist Entities
Canada Special Economic Measures Act Sanctions
Canadian Named Research Organizations list
Czech National Anti-Terrorism Designations
Czech Republic National Sanctions List
Estonia Government National Sanctions Subjects
EU Geographic Restrictive Measures
French National Asset Freezing Register via Open Licence Catalogue
Georgian Otkhozoria-Tatunashvili List
India MHA Terrorist Organizations
India MHA Unlawful Associations
Ireland Unlawful Organisation Orders
Japan METI Russian Export Restriction Entities
Kyrgyz National List
Latvia FIU Sanctions and Asset Freezes
Latvia's Magnitsky Law Sanctions List
Malaysia Ministry of Home Affairs Designations
Monaco Fund Freezing List
Morocco CNASNU Local List
Nepal Prohibited Persons List
Netherlands National Sanctions List for Terrorism
New Zealand Designated Terrorist Entities
New Zealand Russia Sanctions Register
Nigeria Sanctions Committee List
Philippines Anti-Terrorism Council Designations
Poland GIIF Article 118 AML/CFT Sanctions
Poland National Sanctions List
Singapore Terrorism Suppression of Financing Act Schedule
Switzerland SECO Sanctions and Embargoes
UK Russia Financial and Investment Restrictions List
Ukraine SFMS Terrorist List
UN Security Council 1718 Designated Vessels
United Arab Emirates Local Terrorist List
United Kingdom Geographic Sanctions Regimes
United Kingdom Proscribed Organizations
United Nations Security Council Sanctions Regimes
US Consolidated Screening List: Commerce and State Sources
US Department of Defense Section 1260H List
US FinCEN 311 and 9714 Special Measures
US State Department Cuba Prohibited Accommodations List
US State Department Cuba Restricted List
US State Department Foreign Terrorist Organizations
US State Department Terrorist Exclusion List

PEP and RCA

Argentina Chamber of Deputies Members
Brazil Politically Exposed Persons
Cayman Islands Members of Parliament
CIA World Leaders and Cabinet Members of Foreign Governments
Croatia State Registry of Public Officials
Current Members of the European Parliament
Current Members of the Netherlands House of Representatives
French Mayors
French National Assembly Members and Parliamentary Collaborators
French Senators
Hong Kong Principal Officials
Israel Knesset Members
Latvian Saeima
Members of the Riigikogu
Members of the Seimas of the Republic of Lithuania
Mexico Chamber of Deputies
Mexico Senate
Slovakia Public Officials
UN Heads of State & Foreign Ministers
Uruguay Politically Exposed Persons
US Periodically Listing Updates to Management Reporting
US State Department Senior Officials
Wikidata Current Public Office Holders

Crime and wanted

FBI Wanted
Netherlands Police Nationale Opsporingslijst
Polish Police Wanted Persons
UK NCA Most Wanted
US FBI Lazarus Group Stake.com Cryptocurrency Addresses
US ICE Most Wanted Fugitives
US Secret Service Most Wanted Fugitives

Regulatory

Bank of Lithuania Illegal Financial Services Websites
Brazil Entities Prohibited from Offering Auditing Services
Brazil Ministry of Labour Employer Register
Brazil Register of Persons Disqualified from Senior Roles
Brazil TCU List of Individuals Disqualified from Public Service
ESMA Suspensions and Removals Register
EU ESMA Sanctions Register
EU High-Risk Third Countries for AML and CFT
EU Non-Cooperative Jurisdictions for Tax Purposes
FATF High-Risk and Monitored Jurisdictions via HM Treasury
France AMF Illegal Financial Services List
France Non-Cooperative States and Territories
Inter-American Development Bank Sanctioned Firms and Individuals
Japan METI Foreign End User List
Malaysia Financial Consumer Alert List
UK Companies House Disqualified Directors
US BIS Antiboycott Requester List
US CBP Withhold Release Orders and Findings
US DDTC Penalties and Oversight Agreements
US FDA Clinical Investigator Disqualification Proceedings
US FDA Current Debarments
US FDIC Failed Banks
US Federal Reserve Enforcement Actions
US HHS OIG List of Excluded Individuals and Entities
US SEC Public Alert: Unregistered Soliciting Entities
US UFLPA Entity List

Debarment

Brazil National Register of Disreputable and Suspended Companies
Brazil TCU List of Debarred Bidders
US SAM Procurement Exclusions

Matching

How the matching engine works

VerifyNow AML compares enrolled customers to publisher-direct official lists with a proprietary matching engine built by VerifyNow. The lists are the public sanctions, PEP and related files in the coverage catalogue. The engine is how a possible match is scored for ongoing CDD.

Compare to official lists
VerifyNow’s proprietary matching engine compares the enrolled name and identifier against publisher-direct official lists.
Score names and identifiers
The engine scores names, aliases, identifiers, dates of birth and countries. An identifier match after normalisation is a strong signal.
Corroborate the legal name
Where a short name produces several hits, the engine corroborates against the fuller legal name to reduce false positives. Possible matches return with scores and source evidence for analyst review, including EDD.

Licensed VerifyNow AML API

Enrol, rescreen and withdraw

POST name plus identifier. The first call enrols and screens. The same payload rescreens that enrolled subject against the lists above. Your system reads Success, Found and match count.

Enrol
POST name plus identifier. The first call enrols the subject and runs the onboarding AML screen.
Rescreen
Rescreen as often as your RMCP requires. Send the same name and identifier again — included on an active licence. A dataset webhook notifies a list-version change; rescreen then, and on your RMCP cadence.
Withdraw
Remove the subject from the active population when the relationship ends. Limited metadata remains for licence, billing and audit.

VerifyNow AML

POST /v1/aml/ongoing

POST200

Request

{
  "mode": "production",
  "name": "SAMPLE MATCH PERSON",
  "entity": 0,
  "country": "za",
  "dataset": "all",
  "identifierType": "sa_id",
  "identifierValue": "8001015009087"
}

Response

{
  "success": true,
  "requestId": "enrol-sample-match-01",
  "results": {
    "Success": true,
    "ResponseCode": 200,
    "Messages": [
      "Possible financial-crime matches found"
    ],
    "Header": {
      "SearchDate": "2026-08-17T08:00:00.000Z",
      "ReportName": "SAMPLE MATCH PERSON",
      "ReportReference": "amlmon_enrolsamplematch0100000000000000",
      "ClientReference": "enrol-sample-match-01",
      "ReportType": "Ongoing Financial Crime Monitoring",
      "AuditReference": "amlmon_enrolsamplematch0100000000000000",
      "DatasetVersion": "aml_20260817_sample",
      "DatasetPublishedAt": "2026-08-17T07:12:00.000Z",
      "ScreenedAt": "2026-08-17T08:00:00.000Z",
      "CategoriesRequested": [
        "sanctions",
        "crime",
        "wanted",
        "regulatory",
        "debarment",
        "pep",
        "rca"
      ],
      "DataOrigin": "publisher_direct"
    },
    "SearchResults": {
      "InputName": "SAMPLE MATCH PERSON",
      "InputMinScore": "90",
      "InputIdentifierMatchBoostingThreshold": "",
      "InputCountry": "ZA",
      "Found": true,
      "Message": "Possible financial-crime matches found",
      "RecordCount": 1,
      "EntityMatchCount": 1,
      "JurisdictionRiskCount": 0,
      "HasNextPage": false
    },
    "PossibleMatches": {
      "Found": true,
      "Message": "Possible financial-crime matches found",
      "HasNextPage": false,
      "Results": [
        {
          "Name": "SAMPLE MATCH PERSON",
          "AltNames": [
            "SAMPLE MATCH ALIAS"
          ],
          "EntityId": "vn-a1b2c3d4e5f6789012345678",
          "EntityType": "Person",
          "CountryResidence": [
            "ZA"
          ],
          "DateOfBirth": [
            "1980-01-01"
          ],
          "Identifiers": [],
          "Address": [],
          "ConfidenceScore": 0.972,
          "RiskCategories": [
            "sanctions"
          ],
          "Topics": [
            "sanction"
          ],
          "MatchExplanations": {
            "name_match": {
              "score": 1,
              "weight": 1,
              "impact": 1,
              "query": "SAMPLE MATCH PERSON",
              "candidate": "SAMPLE MATCH PERSON",
              "detail": "Best comparison across the submitted name and source aliases."
            }
          },
          "SourceEvidence": [
            {
              "Name": "US OFAC Specially Designated Nationals List",
              "ShortName": "us_ofac_sdn",
              "RecordReference": "sample-sdn-0001",
              "ListVersion": "us_ofac_sdn:sample",
              "PublishedAt": "2026-08-17",
              "DataOrigin": "publisher_direct",
              "Attribution": null
            }
          ],
          "FieldEvidence": {
            "lastName": [
              {
                "value": "PERSON",
                "source": "us_ofac_sdn",
                "recordReference": "sample-sdn-0001",
                "listVersion": "us_ofac_sdn:sample"
              }
            ]
          },
          "DataSource": {
            "Name": "US OFAC Specially Designated Nationals List",
            "ShortName": "us_ofac_sdn",
            "RecordReference": "sample-sdn-0001",
            "ListVersion": "us_ofac_sdn:sample",
            "PublishedAt": "2026-08-17",
            "DataOrigin": "publisher_direct",
            "Attribution": null
          },
          "Program": [
            "SDGT"
          ],
          "ListedOn": "2024-01-15",
          "Designation": "Sample designation for documentation",
          "Comments": "Linked To: SAMPLE MATCH ENTITY",
          "Remarks": "Linked To: SAMPLE MATCH ENTITY Listed on 2024-01-15",
          "remarks": "Linked To: SAMPLE MATCH ENTITY Listed on 2024-01-15",
          "sanctions": "Linked To: SAMPLE MATCH ENTITY Listed on 2024-01-15",
          "Relationships": [],
          "name": "SAMPLE MATCH PERSON",
          "aliases": "SAMPLE MATCH ALIAS",
          "schema": "Person",
          "entity_type": "Person",
          "countries": "ZA",
          "birth_date": "1980-01-01",
          "addresses": "",
          "identifiers": "",
          "score": 0.972,
          "matched_name": "SAMPLE MATCH PERSON",
          "source": "US OFAC Specially Designated Nationals List",
          "source_key": "us_ofac_sdn",
          "source_record_id": "sample-sdn-0001",
          "source_version": "us_ofac_sdn:sample",
          "dataset": "default",
          "dataset_version": "aml_20260817_sample"
        }
      ]
    },
    "JurisdictionRisks": {
      "Found": false,
      "Message": "No jurisdiction risk indicators found",
      "RecordCount": 0,
      "Results": []
    }
  },
  "remainingCredits": 1840,
  "screened_name": "SAMPLE MATCH PERSON",
  "screened_entity_type": "Person",
  "screened_country": "ZA",
  "screened_dataset": "all",
  "operation": "onboarding"
}

Same payload for the first enrol and later rescreens: name plus identifier. Rescreen as often as your RMCP requires; included on an active licence. Sample JSON uses synthetic names.

Security

Data minimisation and purpose-limited retention

VerifyNow AML keeps enough to attach later rescreens to the same identified customer, and to administer licence, billing and audit. Screening queries stay transient at match time.

Match-time queries
The name and identifier used to search the lists are inputs at match time. They are not kept as a customer portfolio in the screening dataset.
Hashed identifiers
The enrolment registry stores an HMAC-hashed identifier and a name digest, scoped to your organisation. Plaintext ID numbers are not stored in the subject table. You send the name and identifier on every rescreen.
Encrypted replay
Full screening responses are stored as ciphertext for 48 hours so the same request can be replayed. After that window the ciphertext is purged.
Purpose-limited retention
Enrolment metadata for licence, billing and audit is retained on a purpose-limited basis, designed around five years. Withdrawal removes the customer from the active population.

Licence

Request a VerifyNow AML licence for your book

Annual licence. First enrol on AML/PEP credits. Unlimited rescreens after that. Request a licence sized to your customer book. The first enrol of each person or company uses the same credits as an AML/PEP screen. After that subject is enrolled, same-subject rescreens on an active licence use no extra credits.

First enrol

AML/PEP

Initial onboarding screen

The first enrol for a name and identifier uses the same credits as an AML/PEP screen.

After enrolment

0 credits

Unlimited same-subject rescreens

Later screens of that enrolled identifier on an active VerifyNow AML licence use no extra credits.

Request a licence

Choose the right AML tool

One-shot, batch or VerifyNow AML

Comparison of AML/PEP screening, batch AML and VerifyNow AML
If you need to	Use	What it is
Screen one name now	AML/PEP Screening	One-shot dashboard or API screen. Identifier optional.
Screen a customer book from a file	Batch AML Screening	10 to 1,000 spreadsheet rows. Manual, repeatable file review.
Keep the same customer in scope after onboarding	VerifyNow AML	Licensed API. Identifier required. Enrol, rescreen on your RMCP cadence, withdraw when the relationship ends.

VerifyNow AML questions

How does VerifyNow AML support FICA ongoing due diligence?

VerifyNow AML is built for accountable institutions that must perform ongoing due diligence under FICA. After onboarding identity is in place, enrol the identified person or company, keep them on refreshed sanctions, PEP, crime and related lists, and withdraw when the relationship ends. Compliance officers get the screening result, list coverage, rescreen cadence, dataset webhook and match evidence to run ongoing CDD and to support EDD reviews. Product and engineering licence the API and wire rescreens when a list version changes, on the review dates in your RMCP.

How often must FICA ongoing due diligence be conducted?

The institution’s RMCP sets the cadence. VerifyNow AML refreshes core TFS lists every 60 minutes and other lists every six hours. Rescreen on the dataset webhook when a list version changes, and/or on the review dates in your RMCP.

How do we enrol, rescreen and withdraw customers on the API?

POST name plus identifier. The first call enrols the subject and runs the onboarding AML screen. The same payload rescreens that enrolled customer. A dataset webhook notifies licensed systems when a list version changes, so ops can rescreen on that signal or on RMCP review dates. Withdraw through the licensed API when the relationship ends. Enrolment is API-first; there is no dashboard enrolment. Your system reads Success, Found and match count — the artefacts a compliance officer files with the CDD review.

Which lists does VerifyNow AML screen against?

Customer screens cover sanctions, PEP, RCA, crime, wanted, regulatory and debarment sources from publisher-direct official lists. The core targeted financial sanctions lists are the United Nations, United States OFAC, United Kingdom, European Union and Australia. PEP and RCA coverage supports EDD reviews after a politically exposed person or sanctions hit. The source catalogue is in the coverage section. VerifyNow’s matching engine scores names against those lists.

Why does enrol need an ID number or company number?

Ongoing CDD has to attach later screens to the same identified customer. People enrol with a South African ID or passport. Companies enrol with a CIPC registration number, LEI or tax number. Product teams use that identifier as the join key from onboarding through ops. One-shot AML/PEP checks can still run on a name only.

How does the matching engine decide a possible match?

VerifyNow’s proprietary matching engine compares names, aliases, identifiers, dates and countries against publisher-direct official lists. An identifier match after normalisation is a strong signal. Where a short name produces several hits, the engine corroborates against the fuller legal name to reduce false positives. Possible matches return with scores and source evidence for analyst review, including EDD.

What customer data does VerifyNow AML keep?

Screening queries are transient at match time. The enrolment registry stores an HMAC-hashed identifier and a name digest, not plaintext ID numbers in the subject table. You send the name and identifier on every rescreen. Full responses are encrypted for 48 hours, then the ciphertext is purged. Enrolment metadata for licence, billing and audit is retained on a purpose-limited basis, designed around five years. Withdrawal removes the customer from the active population.

Built for accountable institutions that must perform ongoing due diligence under FICA.

Related checks

Related AML and CDD checks

AML/PEP ScreeningRun a one-shot person or entity screen from the dashboard.Batch AML ScreeningScreen a customer book from a spreadsheet when you need a periodic review.FICA ComplianceSee how ongoing due diligence fits CDD, EDD and RMCP work.

Keep customers in scope after onboarding

Annual licence. First enrol on AML/PEP credits. Unlimited rescreens after that. Then enrol, rescreen and withdraw through the licensed API.

Request a licence Speak to a compliance specialist