Nex Systems

Bring compliance into your application.

Use public APIs to start identity verification, run screening and connect your data to AML workflows. Connect the product your team needs.

Smart, secure API: structured data, scoped keys, versioned endpoints and signed webhooks.

Book a demo Explore the APIs
Two blue glass connectors joined by a bridge, representing an application connected to a public API.

  • Start from your backend

    Start verification, run screening or connect AML data from the application your team already uses.

  • Keep useful context

    Retrieve structured results and supporting information for the next step in your workflow.

  • Connect with control

    Use product-specific credentials, request contracts and delivery mechanisms.

Choose the API for the job.

Connect Nex eKYC, Nex Screening or Nex AML through the public API for that product.
Explore how each fits into your application.

Start the verification. Keep your journey.

Create a verification from your backend and send the applicant to a hosted capture flow. Retrieve the outcome and permitted evidence when your application needs them.

  1. 1

    Create a verification

    Receive its identifier and applicant link.

  2. 2

    Send the applicant

    Use the hosted flow to collect identity evidence.

  3. 3

    Retrieve the outcome

    Read the decision, findings and available result resources.

KYC API guide

Sign-in required

Request example

POST /api/v1/verifications
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: onboarding-daniel-reed-001
Content-Type: application/json

{
  "customerName": "Daniel Reed"
}

Results available through the API

  • Verification ID
  • Applicant link
  • Result resources

Nex eKYC · Webhooks

Let verification updates come to you.

Receive signed notifications when a verification progresses or a review changes its outcome. Connect those events to your backend without repeatedly checking for updates.

  1. 1

    Verify the sender

    Validate the signature against the original request body.

  2. 2

    Recover a delivery

    Inspect delivery attempts and resend an event after fixing your endpoint.

  3. 3

    Handle events safely

    Use event IDs and sequence numbers to account for duplicates and ordering.

Three connected glass panes representing a verification event travelling to your workflow.

Nex AML

Bring Screening evidence into AML.

Nex AML can call Nex Screening through a configured connection and bring findings into its screening workflow. Review the provider setup and data handoff for your deployment.

The products retain their own records and controls.

Explore Nex AML

  1. Nex AML

    Requests a screening

  2. Nex Screening

    Returns findings

  3. AML review

    Evidence in context

Build a connection you can operate.

  • Keep credentials on your server

    Authenticate from your backend. Manage keys in the relevant product and give each integration the access it needs.

  • Retry deliberately

    Use an idempotency key for supported write requests. Respect retry guidance and rate-limit responses from the API.

  • Read the result in context

    Check the operation’s status as well as its findings. A completed request is not itself a compliance decision.

  • Plan the record handoff

    Map product identifiers to your own records and decide which results and evidence your workflow needs to retain.

A few things to know.

Choose Nex eKYC for identity verification, Nex Screening for screening checks, and Nex AML for customer, account and transaction integration into AML work. The APIs have product-specific setup and contracts; we can help map your application’s workflow to the right connection.

Build the connection your team needs.

Walk through the public APIs and the
data handoff for your workflow.

Book a demo