KYCAID Product Update: July 2026

July brought a mix of new verification capability, finer configuration control, and improvements to the models running behind the scenes. Several of these updates come directly from client requests — particularly around data management and how recognised data is returned.

Here's what changed.

NFC verification: reading the chip, not just the page

You can now add a chip-level NFC (Near Field Communication) scanning step to your verification flow.

Instead of relying solely on the printed data page and its photo, NFC reads the encrypted chip embedded in modern passports and ID cards — the authoritative source of the holder's data. It's a meaningful step up in document authenticity assurance, because chip data is far harder to forge than a printed page.

Availability: native SDK only.

Name match threshold

You can now set the minimum similarity score required for a record to be included in comparison results.

This applies to cases where the applicant's name needs to match the name on their proof of identity document. Setting the threshold yourself means you control how strict or permissive that match needs to be — tightening it to reduce noise, or loosening it to account for legitimate variations in how names appear across documents.

Recognition locale strategy

Names and data don't always come back in the script you expect. This setting defines which locale is used when returning recognised data, with four options:

🔹Origin — return data only in the origin locale.

🔹Latin — return data only in Latin. If only the origin locale exists, transliteration is applied.

🔹Origin with fallback to Latin — prefer the origin locale, fall back to Latin.

🔹Latin with fallback to Origin — prefer Latin, fall back to the origin locale.

This matters most for teams operating across regions using non-Latin scripts, where consistency in how data lands in your system affects everything downstream.

Address verification: VPN allowed for selected countries

Address verification now supports a list of countries for which VPN usage is permitted.

If the applicant's address country appears on that list and a VPN is detected, they're allowed to continue with the check rather than being blocked. This removes a common friction point for privacy-conscious users and anyone connecting through a corporate network, while keeping VPN restrictions in place where they still matter.

Delete applicant verification data after completion and callback

A new custom setting for clients with advanced data management requirements.

When enabled, applicant verification data is deleted once the verification is complete and the callback has been sent. For teams operating under strict data minimisation policies — or with internal rules on how long third-party systems may hold personal data — this puts retention behaviour under your control.

Availability: custom setting; contact the KYCAID team to enable it.

Liveness verification: improved face models

The face models behind liveness verification have been upgraded to catch more AI-generated images and face spoofing attempts.

As synthetic media tooling gets cheaper and better, the gap between a convincing fake and a real face keeps narrowing. This update pushes detection accuracy further on both fronts — generated imagery and presentation-based spoofing.

Phoenix365 and KYCAID: partnership kickoff

We've kicked off a partnership with Phoenix365, a next-generation B2B platform delivering sportsbook and casino solutions for ambitious operators.

Phoenix365's modular stack — sportsbook, casino, risk and trading, engagement, and a built-in CRM — is engineered for real-time performance, high automation, and 24/7 reliability at scale.

With KYCAID embedded into the platform, identity verification and AML checks become part of the same automated workflow. Operators can onboard players efficiently, manage risk, and adapt their compliance processes as they grow — without bolting on a separate system.

For iGaming operators, that matters most at the point of expansion. Entering a new market usually means new verification requirements, new document types, and new regulatory expectations. Having compliance built into the platform rather than alongside it makes that transition considerably less painful.

Already running your project on Phoenix365? Get in touch and we'll walk you through integrating KYCAID's KYC and AML solution into your workflow.

ICYMI: June 2026

If you missed last month's release, here's a quick recap.

Brand

💠A new look for KYCAID. We began rolling out our rebrand, starting with the homepage. More pages will follow in the coming months.

Core updates

💠Payment Method Verification — deeper bank statement checks. 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.

💠South Africa ID verification — three methods. South Africa now supports three non-doc verification methods, built for speed in onboarding scenarios where you need to verify an applicant without an ID upload.

💠Questionnaires — more room per answer. The number of possible answer options per question expanded to 100, giving detailed intake forms and multi-choice compliance questionnaires far more structural room.

New features

💠Italian added to the verification form. Applicants can now complete verification in Italian — onboarding in a user's own language typically means smoother completion and fewer drop-offs.

💠Age Restriction Settings — Effective Age Date control. Some jurisdictions treat the date of birth as the effective date, others use the day after. You can now configure this per country instead of applying one assumption everywhere.

💠Tax ID extraction from ID documents. Where a Tax ID appears on an identity document, KYCAID now extracts it automatically during document processing and returns it in the validation callback.

💠Billing — customizable invoice details. Clients can now set their own company details for invoices — useful when your legal entity name, address, or registration details need to appear a specific way.

💠Transaction Monitoring — maximum volume in EUR per timeframe. A new rule for screening activity that exceeds a defined volume threshold within a set period, a common control point for flagging unusual account activity or structuring patterns.

Wrapping up

July's updates land in two camps: expanding what KYCAID can verify (NFC chip data, stronger liveness detection) and giving you more control over how it behaves (name match thresholds, locale strategy, VPN allowances, data deletion).

If any of these apply to your setup — particularly the custom data deletion setting or NFC scanning in the native SDK — reach out to the KYCAID team and we'll walk you through enabling them.