Skip to main content

World-Check

1. Introduction and Purpose of the Process​

World-Check is a global database containing structured information on high-risk individuals and organizations, political profiles (PEPs), and international sanctions lists. It helps companies meet their international due diligence obligations, mitigating financial, legal, and reputational risks. This service is mandatory for entities subject to anti-money laundering (AML) and regulatory compliance regulations.

2. Detail Parameter Behavior (Summary vs Extended)​

Explains in detail how this endpoint responds depending on the query flags, to avoid unnecessarily large payloads:

  • Summary view (Default): Returns the overall analysis status (result) and the candidate's verified basic demographic data. The full worldCheckData node is omitted.
  • Extended view (?detail=true): Injects the structured worldCheckData object, which contains the provider's raw breakdown, including the audit history, the regulatory sources, and the array of evaluated matches (consideredResults).

3. Architecture Technical Note: Interpreting Matches​

Verdict Logic and False Positives

Integration note: A candidate may produce very high phonetic or name matches within the consideredResults array (e.g. matchScore: 94.66). However, the global result field may still end as Aprobado. This happens when the automated rules engine or the analyst team validates that the secondary fields (such as date of birth, gender, or country of origin) do not match the evaluated candidate, marking the record with a false-positive resolution (resolutionStatusType: FALSE). Integrators should always rely on the root result field.

4. Annotated Response Structure​

{
  "isSuccess": true,
  "statusCode": 200,
  "message": "Success",
  "data": {
    "processId": "f4syIeLawYNNWc2b1ecP",
    "processName": "World Check",
    "detail": {
      "result": "No aprobado", 
      "name": "JUAN PEREZ LOPEZ",
      "creationDate": "2026-07-01T18:50:22.023Z",
      
      // [Enabled only when queried with the ?detail=true parameter]
      "worldCheckData": {
        "entityType": "INDIVIDUAL", // Type of entity queried (INDIVIDUAL or ORGANIZATION)
        "caseScreeningState": {
          "WATCHLIST": "INITIAL"
        },
        "creator": {
          "fullName": "Analista Blacktrust",
          "email": "analista@blacktrust.net"
        },
        "consideredResults": [ // List of possible matches found in international lists
          {
            "resultId": "5jb68p7y2dhq1ktcxspbcp450",
            "matchStrength": "STRONG", // Match strength (STRONG, MEDIUM, WEAK)
            "matchScore": 94.66, // Exact name match percentage
            "matchedTerms": [
              {
                "term": "JUAN PEREZ",
                "submittedTerm": "JUAN PEREZ LOPEZ",
                "matchScore": 94.66
              }
            ],
            "secondaryFieldResults": [ // Secondary field comparison to rule out namesakes
              {
                "typeId": "SFCT_1", // Gender
                "fieldResult": "MATCHED"
              },
              {
                "typeId": "SFCT_2", // Date of Birth
                "fieldResult": "NOT_MATCHED" // Key field for dismissing the alert
              }
            ],
            "sourceCategories": ["Special Interest Categories", "Other Bodies"], // Risk list categories
            "resolution": {
              "reasonId": "DEFAULT_REASON_AUTO_RESOLVED",
              "resolutionRemark": "Date of Birth mismatch", // Justification for closing the alert
              "resolutionStatusType": "FALSE" // FALSE indicates it was determined to be a false positive
            }
          }
        ]
      }
    },
    "status": "Finalizado",
    "result": "Aprobado" // Final result after evaluating and ruling out namesakes
  }
}