Synchronizing
Architectural Primitives

Re-KYC and screening

A verified customer sometimes needs to verify again, because a document expired or because a previous result needs to be redone. Sentinel handles this through the Draft state and a couple of tenant settings.

Re-verification with Draft

When a customer needs to verify again, their status moves to Draft. A customer enters Draft in one of two ways: automatically when a document expires, or from the dashboard when your team sends them back after a review.

1

The customer enters Draft

Triggered by document expiry, or set from the dashboard with a reason.
2

You are notified

You receive a webhook with newStatus 2 (Draft), or you see it through result retrieval.
3

Re-deliver the link

Send the customer their verification link again, the same way you delivered it the first time.
4

The customer fixes and resubmits

They open the link, see a short review screen explaining what to correct, redo the affected steps, and resubmit.
5

It resolves as usual

The status returns to Pending and resolves from there, and you receive the outcome.

On the review screen, the customer is shown the specific reasons their submission needs attention, derived from the checks that did not pass:

  • Face verification did not pass: retake the selfie in good lighting.
  • A document has expired: use a valid, non-expired document.
  • A document photo was unclear: retake it without glare.
  • The selfie did not match the document photo.

If no specific issue is identified, the customer sees a general message asking them to redo the verification steps.

Re-KYC on document expiry

Choose which documents trigger re-verification when they expire, from your dashboard settings. When an accepted customer's chosen document reaches its expiry, Sentinel moves them to Draft, and the re-verification flow above takes over. This runs on a schedule, so no action is needed on your side beyond handling the Draft webhook.

Find customers with expired documents

To drive re-verification yourself, list customers whose documents have expired. Optionally filter by document type. Images are omitted, and each customer carries an expiredIds array.

http
POST https://api.sentinel.example.com/customers/findAllWithExpiredIDs/clientAuth
FieldTypeDescription
clientUuidrequiredstringYour client identifier.
clientSecretrequiredstringYour client secret. Server-side only.
filterstringOptional. One of passport, emiratesId, egyptNationalId. Omit for any expired document.
pagenumberPage number. Defaults to 1.
entriesPerPagenumberOne of 10, 50, or 100. Defaults to 50.
request
{
  "clientUuid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "clientSecret": "xxxxxxxxxxxxxxxx",
  "filter": "passport",
  "page": 1,
  "entriesPerPage": 50
}
response
{
  "message": "Success",
  "data": {
    "meta": { "total": 7, "perPage": 50, "currentPage": 1, "lastPage": 1 },
    "data": [
      {
        "uuid": "9a1b2c3d-4e5f-6071-8293-a4b5c6d7e8f9",
        "status": 6,
        "name": "John",
        "surname": "Smith",
        "passports": [{ "passportNumber": "X1234567", "dateOfExpiry": "2024-03-01" }],
        "emiratesIds": [],
        "egyptNationalIds": [],
        "expiredIds": ["passport"]
      }
    ]
  }
}

Expiry warnings

To act before a document expires rather than after, enable expiry warnings in your dashboard settings. You choose which documents to watch and how many days ahead to be warned (up to 90, 15 by default).

Sentinel then sends an expiry_warning webhook ahead of expiry, with expiryWarningFor listing the documents that are approaching expiry. Use it to prompt the customer to re-verify early. See the event and payload on Webhooks and callbacks.

How screening fits in

Sanctions and PEP screening run as part of each verification, contributing to the outcome. A re-verification re-runs the checks.

Related
Configure these settings in the dashboard, and handle the Draft and expiry_warning signals through Webhooks and callbacks.