VerifyNow™ AML for FICA ongoing due diligence

VerifyNow™ AML is an API for screening customers against sanctions, PEP and RCA sources after onboarding. Your integration sends rescreen requests when lists change or a review is due under your RMCP.

For FICA accountable institutions, including banks, insurers, attorneys, estate agents and other Schedule 1 businesses. Fintech, iGaming and marketplaces can use the API for post-onboarding screening under their RMCP.

Annual licences start at R2 999, excluding VAT. Enrolment credits are priced at checkout.

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

Screening sources and update times

We check publishers for changes on the schedules below. Updates become available after collection and validation; an outage or failed collection can delay them.

The catalogue contains records for people and companies, along with listed entities, vessels and aircraft. Each screening result records the dataset version used.

60m

UN, OFAC, UK and EU

These core sanctions feeds and selected additional sanctions sources are scheduled for checks every 60 minutes.

6h

Other lists

Most other publisher sources are scheduled for checks every six hours.

Targeted financial sanctions (TFS)

FIC requires accountable institutions to screen against targeted financial sanctions (TFS). VerifyNow™ AML supports that screening with configured United Nations, OFAC, UK, EU and Australian sources. Each result records the dataset version used for the screen.

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

See watchlists update

VerifyNow checks each source on schedule. When a list changes, this feed shows when it changed and how many records were added, updated or removed.

Refresh window25 Aug 2026 · 07:00 SAST
Cycle progress0 / 5 checked

How it works

  1. 01Lists are checked
  2. 02Changes are dated
  3. 03Your team is notified
  4. 04You rescreen when required

Illustrative watchlist refresh feed dated 25 August 2026. It shows publisher lists being checked in sequence and records which entries were added, updated or removed.

Dataset notification prepared

Your team receives an email and signed webhook when visible list content changes. Your system runs the rescreen when your RMCP calls for it.

Configured source catalogue+

A listed source contributes records once a validated snapshot has been collected. You can request a dated source-status record for due diligence. Coverage has gaps, including South African domestic court orders; this catalogue is not a complete global register.

Your team remains responsible for transaction monitoring and managing EDD cases.

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

How the matching engine works

VerifyNow built and owns the matching engine. It uses records from official publishers, with attributed Wikidata records for additional PEP information.

  1. Name matching

    Names are compared with source names and aliases, including spelling variations and changes in name order.

  2. Supporting details

    Supplied identifiers, birth dates and countries help distinguish records with similar names. Conflicting details can lower the score.

  3. Ambiguous names

    A fuller legal name helps resolve multiple hits for a short name. Returned scores and source evidence support your analyst’s review.

Fewer false positives with an SA ID or date of birth

When date-of-birth refinement is enabled, each enrolment or rescreen compares the supplied birth date with the dates on listed records. An SA ID number can supply the birth date. A different date lowers the match score; records without a date remain eligible for review.

  • An exact ID, passport, registration number, LEI or tax number match raises the score.
  • Each match shows its confidence score and the reasons behind it: name similarity, identifier, date of birth and country.
  • Send refineWithDob: true to enable refinement or false to disable it. When omitted, the account default applies. Include the person’s name and identifier on each request, plus the birth date when needed.

Connect the ongoing AML API

Use your account API key to test requests in sandbox mode. Switch to production after buying your licence. The API response includes the screening outcome and any possible matches.

Set up a signed webhook to receive dataset-change notices, with email as an optional notification. Your integration chooses which customers to rescreen and submits the requests. Delivery depends on your settings and successful processing.

API documentation

  1. First screen

    Send the name and an identifier for each customer. A successful first screen creates the enrolment and uses onboarding credits.

  2. Later reviews

    Use the same name and identifier to screen the customer again. Check the returned matches against the customer record before recording your decision.

  3. End of the relationship

    Call the withdrawal endpoint to remove the customer from the active population. The audit metadata remains subject to the retention period below.

VerifyNow AML

POST /api/external/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.5,
          "RiskCategories": [
            "sanctions"
          ],
          "Topics": [
            "sanction"
          ],
          "MatchExplanations": {
            "name_match": {
              "score": 1,
              "weight": 0.5,
              "impact": 0.5,
              "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.5,
          "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"
}

Dataset webhook and email

Licensed organisations get aml_monitoring.dataset_updated on the registered HTTPS webhook, HMAC-SHA256 signed. Organisation owner and admin contacts also get an email; TFS source changes are called out there. These are notifications — enrolled subjects are not rescreened automatically. POST the same name and identifier after the webhook or email, or on your RMCP review dates.

{
  "id": "evt_amlmon_aml_20260817_sample",
  "type": "aml_monitoring.dataset_updated",
  "createdAt": "2026-08-17T07:12:00.000Z",
  "data": {
    "datasetVersion": "aml_20260817_sample",
    "sourceStatus": "current",
    "dataOrigin": "publisher_direct"
  }
}

Headers: x-verifynow-event-id, x-verifynow-timestamp, x-verifynow-signature (v1= hex HMAC). Same payload for the first enrol and later rescreens: name plus identifier. Sample JSON uses synthetic names.

Read full API reference

Customer data and retention

The enrolment registry links repeat requests to the same customer. The storage and retention periods below apply to screening inputs, responses and audit records.

  1. 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.

  2. Hashed identifiers

    The enrolment registry holds an HMAC-hashed identifier and a name digest within your account. Each rescreen request supplies the name and identifier again.

  3. Encrypted replay

    Full responses are encrypted for replay, with a 48-hour expiry. Removal depends on the scheduled cleanup job completing.

  4. Audit records

    Enrolment and operational audit metadata is retained for seven years. Withdrawal removes the customer from the active population.

Annual licence pricing

Choose a 12-month licence based on how many customers you want to monitor. The prices below exclude VAT.

Initial onboarding screen
Enter your initial customer count at signup. Checkout shows the enrolment price per customer at your credit volume tier and adds those credits to your purchase.
Rescreening
Rescreen an enrolled customer for 0 credits while the licence is active, within its population and request limits.

Volume discounts apply to enrolment credits. The annual licence fee is charged in full.

Licence fees are non-refundable once screening has been run.

VerifyNow™ AML annual licence prices, excluding VAT
Active customersAnnual licence, ex VATChoose licence
Up to 1,000R1 999Choose licence
Up to 2,000R2 999Choose licence
Up to 5,000R5 999Choose licence
Up to 7,500R7 999Choose licence
Up to 10,000R9 999Choose licence
View all 13 tiers Up to 1,000,000 customersShow first 5 tiers
VerifyNow™ AML annual licence prices, higher tiers, excluding VAT
Active customersAnnual licence, ex VATChoose licence
Up to 15,000R13 999Choose licence
Up to 20,000R16 999Choose licence
Up to 25,000R19 999Choose licence
Up to 50,000R34 999Choose licence
Up to 100,000R59 999Choose licence
Up to 250,000R124 999Choose licence
Up to 500,000R224 999Choose licence
Up to 1,000,000R399 999Choose licence

One-shot, batch or VerifyNow™ AML

Comparison of AML/PEP screening, batch AML and VerifyNow™ AML
If you need toUseWhat it is
Screen one name nowAML/PEP ScreeningOne-shot dashboard or API screen. Identifier optional.
Screen a list of customers from a fileBatch AML Screening10 to 1,000 spreadsheet rows. Manual, repeatable file review.
Rescreen enrolled customers through an APIVerifyNow™ AMLAnnual licence for a defined customer population. Supports repeat screening and withdrawal.

VerifyNow™ AML questions

How does VerifyNow™ AML support FICA ongoing due diligence?

It provides screening results and source evidence for your customer due diligence (CDD) records. Your compliance team assesses possible matches and decides whether enhanced due diligence (EDD) is required under its RMCP.

How often must FICA ongoing due diligence be conducted?

Your institution’s Risk Management and Compliance Programme (RMCP) sets the review schedule. Choose review dates based on the customer’s risk and the events that require another check.

Does VerifyNow AML rescreen customers when a list changes?

Your integration sends each rescreen request. A dataset-change webhook tells it that source data has changed so it can choose which customers to screen. Notifications depend on your settings and successful delivery.

Can an individual account buy an ongoing AML licence?

Yes. Individual accounts and organisation owners or admins can buy a licence through the AML signup page. Enter your full name and company or trading details, choose a population band and pay the annual fee. Access activates after payment confirmation.

Does a 2,000-customer licence cover customers or screening requests?

It covers up to 2,000 active customer enrolments at one time. You can rescreen those customers during the licence year within the request-rate limit. Withdraw a customer when the relationship ends to free a population slot.

What happens when I reach my licensed customer limit?

The API rejects a new enrolment with HTTP 403 and POPULATION_LIMIT_EXCEEDED when the active and reserved enrolments fill the allowance. Review your customer population or arrange a larger licence before adding more customers.

Does the licence include adverse media and transaction monitoring?

Adverse Media Search uses a separate service and API endpoint. This licence covers customer screening against the listed sources; your business remains responsible for monitoring transactions and managing compliance cases.

Which lists does VerifyNow™ AML screen against?

The licence covers the sanctions, PEP, RCA, crime, wanted, regulatory and debarment sources listed on this page. Each response identifies the dataset version used. Publisher outages and failed collections can affect which sources are available for a screen.

Can I enrol a customer without an ID or company number?

Yes. Use customer_reference with a unique numeric reference from your system. Keep it unchanged for that customer’s rescreens and withdrawal. The reference links the requests to one enrolment; matching uses the name and screening details you supply.

How does the matching engine decide a possible match?

It compares the supplied name and identifying details with source records. Scores and source evidence help your team decide whether a result refers to the same person or company. A high score alone does not confirm identity.

What customer data does VerifyNow™ AML keep?

The enrolment registry holds hashed identifiers and name digests. Full responses are encrypted with a 48-hour replay expiry and removed by scheduled cleanup when that job completes. Enrolment and operational audit metadata is retained for seven years.

Set up your AML API

Create an account to buy your licence and enrolment credits. After payment, the setup page shows how to send your first API request.

Matching, coverage and ongoing screening

Names are compared with listed names and aliases using fuzzy matching, including spelling variations and name order. Supplied birth dates and other identifying details influence the score where the source contains them. Conflicting details can lower the score. The default threshold is 90 out of 100, configured at service level. It expresses a matching score rather than the probability of a confirmed identity; the API has no per-call threshold setting.

Results are potential matches with source evidence for customer review. Customers record their decisions in their own compliance system. VerifyNow has no false-positive dismissal or suppression workflow, and no validated false-positive percentage is published.

UN-based designations relevant to the FIC targeted financial sanctions framework are screened through the direct UN Security Council consolidated feed. That feed is checked hourly; validated changes are published after collection and processing. The schedule is not a one-hour publication SLA. Separate South African domestic designations and freezing orders are not represented as a complete corpus.

South African PEP feeds include national executive and municipal leadership records. Wider coverage draws on public government, parliamentary and leadership records, with relationship evidence where supplied. Complete provincial, SOE, Africa-wide PEP and comprehensive RCA coverage is not guaranteed. Available designations, relationships and source evidence support customer assessment. Complete role dates and a dedicated foreign/domestic PEP or prominent-influential-person classification are not guaranteed.

A dataset-change webhook prompts your integration to submit rescreens. Per-subject new-hit and cleared-hit alerts are not provided. Customer dataset-update emails are optional and off by default. The default licensed rate is 1,000 requests per minute per organisation, shared across its keys. Queue population rescreens, limit concurrency and honour Retry-After on HTTP 429. Reuse the same idempotency key when retrying the same request.

A numeric customer_reference can identify a person or company enrolment when an official identifier is unavailable. Keep it unique across the organisation and stable across rescreens. The reference does not affect the match score. Read the identifier requirements. Adverse Media Search is a separate endpoint.