GovFaceMatch

The first identity solution to match biometrics against DMV records

Name: GovFaceMatch
Brand: Incode

A new standard in identity verification. Higher conversion and stronger fraud prevention, with no tradeoff. GovFaceMatch verifies a live selfie against the issuing state’s DMV record in real time, with no document capture.

Request a demo

faster verification vs document-based verification

+20%

higher conversion vs document-based verification

1,000x

lower false acceptance rate vs non-document checks

Measured in Incode production deployments against document-based flows.

Partnership

“Identity is the foundation of trust in nearly every transaction that matters, from opening a bank account to accessing healthcare. As the agency responsible for issuing that identity credential, we have a duty to help get it right. By working with Incode, we’re enabling private-sector partners to rely on the same trusted records we do, with clear consumer consent at every step. Georgia DDS is proud to be part of a partnership that strengthens the broader identity ecosystem.”

Angelique B. McClendon · Commissioner of the Georgia Department of Driver Services

The problem

Identity verification has always meant choosing between friction and fraud

Most solutions rely on either data or documents. Neither can deliver both high conversion and strong fraud prevention.

Impacts conversion

Catches more fraud, but adds friction that drives users away. Up to 40% never complete the process.

Weakens fraud prevention

Keeps users moving, but allows synthetic and stolen identities to pass undetected.

40%

of legitimate users drop off due to verification friction

Incode customer data

95%

of synthetic identities go undetected during onboarding

Thomson Reuters

$23B

projected losses from synthetic identity fraud by 2030

Deloitte

How it works

The only solution that delivers higher conversion without compromising identity assurance

What you gain

What changes when identity is verified against DMV records

Lower user friction

Complete verification with a barcode scan and selfie. No document capture required.

Stronger protection

Verify the person, not just the data. Stops synthetic identities and AI-assisted fraud that bypass traditional checks.

A forged or AI-generated document cannot match a portrait that already exists in the state’s DMV record.

Built-in privacy

Matching occurs within the DMV’s secure environment. No biometric data is stored and no government PII is shared.

How it looks together

Verify more users with government-record assurance

GovFaceMatch is part of Incode's GovMatch™ suite of solutions for verification against government records, combining image-based and data-based verification to deliver the highest assurance across every supported state.

Unified offering

GovMatch

Routes each transaction to whichever method the issuing state supports.

ID barcode scan + selfie

Issuing state identified

GovFaceMatch

Document number First name Last name Birth date Issue date Expiration date

GovDataMatch

Document number First name Last name Birth date Issue date Expiration date

Real-time result

GovFaceMatch

Matches a live selfie against the DMV portrait. Confirms the person.

ID barcode scan + selfie

DMV Environment

Incode Face Match Engine Models deployed within DMV infrastructure

DMV Image Database Images retrieved for biometric comparison upon data match

Real-time result

GovDataMatch

Matches identity attributes against DMV data. Confirms the identity exists.

ID capture

Verify against DMV records

Document number First name Last name Birth date Issue date Expiration date

Real-time result

Why Incode

The first and only identity platform to partner directly with state DMVs for real-time biometric verification

No other vendor can improve both conversion and fraud outcomes at the same time.

Direct integrations with state DMVs

Signed agreements with state DMV and DDS agencies, not resold or cached data.

Real-time verification at the source

Every check queries the state’s live record at the moment of the transaction.

Matching occurs within secure DMV systems

Incode’s face match engine runs inside DMV infrastructure. Portrait images never leave.

Deterministic confirmation from the issuing authority

A yes or no from the authoritative source, not a probabilistic risk score.

GovFaceMatch suits US platforms in banking, lending, iGaming and telecom that need government-grade identity assurance without the drop-off that document capture creates.

FAQ

Frequently asked questions

The questions buyers ask most about GovFaceMatch, answered straight.

Still have questions? Talk to an expert

How is GovFaceMatch different from document-based verification?

Document checks authenticate a picture of a credential. GovFaceMatch matches a live selfie directly against the issuing DMV's official record in real time, so the confirmation comes from the source itself. Users complete it with a barcode scan and a selfie, 6x faster and with 20% higher conversion than document-based verification.

What happens to the user's biometric data?

Matching occurs within the DMV's secure environment, with clear consumer consent at every step. No biometric data is stored and no government PII is shared.

Does it stop synthetic identities and AI-generated fraud?

Yes. GovFaceMatch verifies the person, not just the data, so synthetic and stolen identities that pass traditional data checks fail the biometric match against the official record. That delivers a 1,000x lower false acceptance rate than non-document checks.

How is GovFaceMatch different from AAMVA’s DLDV service?

AAMVA’s Driver’s License Data Verification (DLDV) service confirms that the data printed on a license matches the issuing state’s record. GovFaceMatch adds the biometric layer, comparing a live selfie to the DMV’s own portrait for that record. Data verification proves the credential exists. Biometric verification proves the person presenting it is the person it was issued to.

Is GovFaceMatch a non-documentary verification method under FinCEN CIP rules?

Yes. GovFaceMatch confirms identity against a government source of record rather than by examining a submitted document image, which is the distinction FinCEN draws in its Customer Identification Program requirements. Institutions should confirm treatment with their own compliance counsel, as CIP procedures are set at the institution level.

What is the difference between GovFaceMatch, GovDataMatch and GovMatch?

GovFaceMatch performs biometric matching against the DMV portrait. GovDataMatch verifies identity attributes against DMV data records. GovMatch routes each transaction to whichever method the issuing state supports, expanding coverage automatically as new states go live with no additional integration required.

What happens if a user’s state is not supported?

GovMatch routes the transaction to whichever method the issuing state supports, falling back to GovDataMatch or to standard document verification. No integration change is required when new states go live, and no user is blocked because of where their license was issued.

From the blog

Featured reading

View all posts

Incode news · 4 min read

Incode partners with Purdue University for deepfake detection research

Incode and Purdue University are partnering on deepfake detection research to improve how detection is tested against real-world identity fraud.

Read the post

Incode news · 4 min read

Incode ranks among the most accurate age estimation providers in NIST testing

Incode's age estimation model ranked third of 29 providers on NIST's largest dataset. Learn what these results mean and why they matter.

Read the post

Incode news · 3 min read

Incode wins Fraud & Compliance Solution of the Year at the 2026 SBC Awards

Incode won Fraud & Compliance Solution of the Year at the 2026 SBC Awards. See how Incode helps gaming operators stop AI fraud and meet compliance.

Read the post

What's next

Stop losing customers to verification. Increase conversion without increasing fraud.

Request a demo Explore the platform