Changelog

Every change your team will notice in the console lands here, newest first: a new page, a new filter, a control that now behaves differently, or a reason more or fewer cases reach your reviewers. It is written for the people who use the console. Changes that only matter to the developer who connects TrustWix to your product, such as new API fields and webhook events, are listed in the developer changelog.

30 September 2026

Filter by the country that issued the document

Manual review, Verifications and Persons can now be narrowed to one document country. It goes by the country that issued the document the applicant photographed, not by where they were when they did it, so a team split by the documents each reviewer can read can give everyone their own queue. The queue's counts and its export narrow with it. See Manual review.

A repeat is recognised by the face first

When a person you have already approved tries again, the face in their selfie is now compared with the faces on your approved verifications, and a strong match stops the attempt as a repeat before any verdict is written. It holds when everything else is new: a different customer ID, a different email and a different document still belong to the same person in front of the camera. It follows the same re-verification setting as before, and if it ever stops someone who really is a different person, allow a re-verification from the verification it matched. See Re-verification.

29 September 2026

A new Fraud section

The new Fraud page gathers everyone who came back under another account, or tried the same account again and again, by person rather than as dozens of separate expired verifications. It shows how many repeat attempts were stopped, the people behind them, who used two or more accounts, and the devices that several people verified from, with a timeline for each person. Everything on it is your own data. Repeat cases that are still open now wait in their own Fraud review tab in Manual review, apart from ordinary cases.

Face links in the fraud network are stricter

Two applicants are now linked by face only when their faces agree more closely than before, so far fewer links join people who merely look alike. Links made on a shared document or email address are unchanged.

A review cannot re-decide a verification that already has its answer

A review left open after its verification was settled some other way, for example approved when it was run again, could still be decided, and deciding it sent your business a second, different verdict. It can no longer be decided: the console says the verification already has its answer, and such reviews are now closed on their own within a few minutes. Reviews on verifications that are still waiting are unaffected.

24 September 2026

Documents missing a field their kind always prints go to review

For each country and document type, we learn from the documents your team approved which fields a genuine one always carries. A document missing one of them, or carrying one that fails its own check, now goes to manual review instead of being approved automatically, because hiding a field is how an edited document conceals who it belongs to. It never rejects anyone. You can waive it in your findings policy like any other document finding. See What each finding means.

Passports are checked against their machine-readable lines more often

The two lines of characters at the bottom of a passport are now found in more of the passports we read. Where they are found and disagree with the printed passport number or date of birth, the document is refused.

23 September 2026

The document types your flow accepts are now enforced

A flow has always been able to say which documents it takes, but the setting did nothing. It is now enforced when the document is captured, so a flow restricted to passports refuses an ID card on the spot and tells the applicant what it takes. A flow that lists nothing accepts everything, as before. See Flows.

Your team can edit applicant data, and every edit is versioned

Owners, managers and reviewers can now correct the identity data on a verification, in manual review and after it has been approved or rejected. Every edit is kept as a new version and nothing is ever deleted: version 1 is always what was read from the document, and any version can be restored. An edit never changes the status or the verdict. See Editing applicant data and Roles.

Blurry documents and selfies are retaken on the spot

The verification flow now checks that a document photo is sharp and large enough to read, and that a selfie shows a clear, well-lit face, and asks the applicant to retake it there and then. After two retakes it lets them continue, so an older phone never blocks anyone. Expect fewer cases in review that exist only because a photo could not be read.

Documents that print dates day first are read correctly

A document printing its expiry as 25/05/2028 used to be treated as having no readable expiry, which sent it to manual review. Those dates are now read. When a date could be read two ways that disagree on whether the document has expired, it still goes to a person rather than being guessed.

21 September 2026

An unreadable expiry date is never approved automatically

When the expiry date on a document cannot be read, the verification now goes to manual review, whatever your review sensitivity, instead of being approved without that evidence.

16 September 2026

One person, one open case

A new verification is refused while the same person already has one waiting in manual review, and when one of their verifications is approved, their other open cases are closed. A person is now also recognised by their national ID number, so a driving licence and an ID card for the same person count as one person. See When the person is already approved.

14 September 2026

Choose what a new API key can read

When you create an API key, you now choose whether it reads outcomes only or full applicant data, and a key's last-used time is shown correctly. See What this key can read.