Your summer 2026 product update from KYCAID
Twenty-one updates shipped over the summer, and looking at them together makes the direction clearer than any single release did. Verification got harder to fool: chip-level NFC reading, stronger detection of AI-generated faces, and full VPN, proxy and Tor blocking on the verification flow. Coverage widened across documents, markets and languages. And a set of controls that used to be fixed became yours to configure. Here's the complete picture — plus a look at what's coming next.
Verification got harder to fool
Three of the summer's updates target the same thing from different angles: making it harder to pass verification with something that isn't a real person and a real document.
NFC verification (July) — chip-level scanning is now available in the native SDK. Rather than reading only the printed data page, it reads the encrypted chip inside modern passports and ID cards. That chip is the authoritative source of the holder's data and considerably harder to forge than a printed page.
Liveness detection (July) — the face models were upgraded to catch more AI-generated imagery and spoofing attempts. As synthetic media tooling gets cheaper, the gap between a convincing fake and a real face keeps narrowing, and detection has to move with it.
VPN, proxy and Tor blocking (August) — you can now block the verification flow entirely for users connecting through a VPN, proxy or Tor, with a configurable list of allowed countries. This extends the address-verification VPN allowance introduced in July into a full flow-level control: rather than deciding whether a masked connection is acceptable case by case, you set the policy once and the system enforces it.
Fuzzy search for AML screening (August) — the fuzzy matching behind database screening was upgraded, improving how names are matched against sanctions, PEP and watchlist data. Better matching cuts in both directions: fewer genuine matches slipping through, and less noise for your analysts to clear.
Payment Method Verification (June) — bank statement processing now includes card mask validation, transaction amount validation, and a data match check against the statement and card photo, catching inconsistencies before a statement is fully processed.
Coverage widened
Proof of address document types (August) — Telecom bill and Identity document with address are now accepted. Both are common in markets where utility bills are less standard, and each one added reduces the number of applicants who simply have nothing eligible to submit.
South Africa ID verification (June) — three non-doc verification methods, built for speed in onboarding flows where you need to verify someone without an ID upload.
Tax ID extraction (June) — where a Tax ID appears on an identity document, it's now extracted automatically during processing and returned in the validation callback. Less manual entry, fewer transcription errors.
Localisation and user experience
Czech and Slovak (August) — both languages are now supported on KYC forms.
Italian (June) — added to the verification form earlier in the summer.
Onboarding in a user's own language consistently improves completion rates, and these three additions extend that across Central and Southern Europe.
All supported languages in the email editor (August) — form settings now expose the full language set in the email editor, so the messages your applicants receive match the language of the form they're completing. Previously the form and its emails could diverge.
KYC status page redesign (August) — rebuilt to the new design, with a countdown added. The status page is what an applicant looks at while waiting, and a visible countdown replaces uncertainty with an expectation — which matters more for drop-off than it might sound.
A new look for KYCAID (June) — the rebrand rollout began with the homepage. More pages follow in the coming months.
Controls that are now yours to set
Name match threshold (July) — set the minimum similarity score required for a record to appear in comparison results, where an applicant's name must match the name on their proof of identity document. Tighten it to cut noise, or loosen it to allow for legitimate variations in how names appear across documents.
Recognition locale strategy (July) — choose which locale is used when returning recognised data: origin only, Latin only with transliteration where needed, origin with fallback to Latin, or Latin with fallback to origin. Most relevant for teams working across non-Latin scripts, where consistency affects everything downstream.
Data deletion after completion and callback (July) — a custom setting that removes applicant verification data once verification completes and the callback is sent, putting retention behaviour under your control. Contact the team to enable it.
Effective Age Date control (June) — some jurisdictions treat the date of birth as the effective date, others the day after. This is now configurable per country rather than applying one assumption everywhere.
Questionnaires (June) — up to 100 answer options per question, giving detailed intake forms and multi-choice compliance questionnaires considerably more room.
Transaction Monitoring (June) — a new rule for maximum volume in EUR per timeframe, screening for activity exceeding a defined threshold within a set period. A common control point for flagging unusual account activity or structuring patterns.
Billing (June) — invoice details are now customisable from your side, useful when your legal entity name, address, or registration details need to appear a specific way.
Where this leaves things
The pattern across the summer is straightforward. The checks themselves got harder to circumvent, the range of documents and markets we handle got wider, and a set of decisions that used to sit with us moved to you.
There's one more thing worth flagging, though it isn't shipped yet. We've been building a dedicated anti-fraud platform — a separate layer sitting alongside verification, aimed at the fraud that doesn't announce itself at onboarding. More on it soon.
In the meantime, if any of the summer's updates are relevant to your setup — particularly NFC scanning, VPN blocking, or the custom data deletion setting — talk to our team and we'll walk you through enabling them.