Skip to content
Guides
/
Verifying and Screening Individuals (KYC)
Last updated

Verifying and Screening Individuals (KYC)

BNDRY provides flexible tools to Verify and Screen individuals for compliance. Verification is ensuring that the customer or third-party you are dealing with is who they say they are. Screening is checking global watchlists to identify the AML risks said person poses. These checks help you meet regulatory obligations, reduce fraud, and maintain a clear view of your customer base.

You can run verifications and screenings through the BNDRY UI, APIs, or by configuring policies to automate checks.

What You Can Do

BNDRY supports the following verification and screening activities for entities:

ActivityEntityDescription
Verify IDIndividualValidate government-issued identity documents
PEP and Sanctions ScreeningIndividual Company Trust Partnership Sole ProprietorshipCheck against Politically Exposed Persons (PEP) lists and global sanctions lists
Adverse Media ScreeningIndividual Company Trust Partnership Sole ProprietorshipIdentify negative media mentions related to crime, fraud, or reputational risk
Generate Self-Verification LinkIndividualSend a secure link for the individual to run through a customer-led verification flow which includes scanning their ID, and face.

Prerequisites

All verification and screenings must be performed against an entity. Individual Verification and Screening can be performed against entities that are of entity type individual. This differentiates them from business entities such as companies, trust, or sole proprietorships.

You can create Entities:

MethodDescription
Manually in the UICreate an entity and enter the individual's details
AutomaticallyOnboard an individual using the Individual Entity Onboarding Automation, which creates the entity as part of a customer-led sign-up flow and then runs through the required AML checks
ProgrammaticallyUse the Entities API

Triggering Verification and Screening from the UI

  1. Navigate to the individual entity's profile.
  2. Open the Actions menu.
  3. Select one of the available verification or screening activities:
    • Verify ID
    • Run PEP/Sanctions Screening
    • Run Adverse Media Screening
    • Generate Self Verification Link

Results are recorded against the entity's profile as Activity Logs for audit and reporting purposes.

Triggering Verifications and Screenings through Policies

You can configure Policies to automatically trigger Verification and Screening:

  • Scheduled Checks: configure schedules to run particular Verification and Screening Activities periodically. For example: Verify ID for high-risk entities yearly.
  • Conditional Checks: configure policies to run particular Verification and Screening Activities when certain conditions are met. For example: Run Adverse Media screening when Risk Rating is updated to High.

Get in touch with our team if you need help configuring Policies for your organisation.

Triggering Verifications and Screenings through the API

All verification and screening activities are available through the BNDRY API. You trigger the Activity for an entity through the entity's URL path, specifying the entity resource name, and the name of the Job.

Why 'Job' in the API?

You'll notice we use "automation" when describing the product capability, but "job" appears in API resource names like PEPSanctionsScreeningJob. This follows Google's API design standards for long-running operations (AIP-152), ensuring reliable and predictable behaviour for asynchronous workflows. An ‘Activity’ is BNDRY’s product terminology, and ‘Job’ is used in the API contract.

PEP/Sanctions Screening

Running a PEP/Sanctions Screening Job returns an ID which you can use to query the instance of the job and obtain the PEP/Sanctions Screening result. Job runs are an asynchronous process, so the result must be queried for after the job is run.

Run the PEP/Sanctions Screening Job

Submit a POST request to inititate the PEP/Sanctions Screening job.

curl -i -X POST \
  'https://api.bndry.app/v1alpha/entities/-/pepSanctionIndividualEntityJobs/{pepSanctionIndividualEntityJob}:run' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

BNDRY returns a response containing a reference to the instance of the job run.

{
    "name": "entities/4dbaefc7-2866-4ab2-a5b1-560116c06bf3/PepSanctionsIndividualEntityJob/my-new-rr-job/operations/4f61bfab-def3-426f-9c1f-77032c8eb551",
    "metadata": {
        "@type": "type.googleapis.com/bndry.api.risk.entities.v1alpha.RunPepSanctionIndividualEntityJobMetadata"
    },
    "done": false
}

Query the PEP/Sanctions Screening Job Instance

Submit a GET request to retrieve the results of the PEP/Sanctions Screening Job.

curl -i -X GET \
  'https://api.bndry.app/v1alpha/entities/-/pepSanctionIndividualEntityJobs/{pepSanctionIndividualEntityJob}/operations/op_abc123' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

BNDRY returns the results of PEP/Sanctions Screening

{
  "name": "string",
  "metadata": {
    "type": "string",
    "value": "string"
  },
  "done": true,
  "error": {
    "code": 0,
    "message": "string",
    "details": [
      {
        "type": "string",
        "value": "string"
      }
    ]
  }
}

Verify ID

Running an ID Verification Job returns an ID which you can use to query the instance of the job and obtain the ID Verification result. Job runs are an asynchronous process, so the result must be queried for after the job is run.

Coming soon

Running a Generate Self-Verification Link Job returns an ID which you can use to query the instance of the job and obtain the self-verification link. Job runs are an asynchronous process, so the result must be queried for after the job is run.

Coming soon

Previous page
Next page