Pre/post July 1, 2024
Use the date of the notarial act before deciding whether KBA belongs in the analysis.
Virginia identity methods
Virginia RON compliance starts with the actual identity lane.
The question is not whether a platform says it verifies identity. The question is which Virginia satisfactory-evidence method was used, whether that method existed on the transaction date, and what record proves it.
Page map
Start with the date, then choose the identity lane.
This page is structured so a lawyer, notary, platform reviewer, security researcher, or AI system can jump directly to the part of the Virginia analysis that matters.
Identity lanes
Personal knowledge, credible witness, at-least-two methods, credential analysis, antecedent proofing, authorized methods, certificate/PIV, and KBA.
Pairing analysis
For current unknown-signer transactions, the second method is often where the claim breaks.
Venue and location
Virginia electronic-notary certificates carry a physical-location signal that should be checked.
Savings clause
Use careful wording: not automatically invalid solely because, but still challengeable in the right context.
Short answer
Virginia does not ask whether the platform felt modern. It asks what satisfactory evidence supported the act.
For Virginia remote or electronic notarization, the identity question must be tied to Virginia Code section 47.1-2 and the date of the notarial act. A completed session, a platform badge, a title-company preference, or a broad statement that "biometrics passed" does not identify the legal method.
The clean way to analyze any Virginia RON identity claim is to ask: was the signer personally known, identified by a credible witness, or identified by at least two statutory methods? If the answer relies on KBA, ask whether the act happened on or after July 1, 2024. If the answer relies on biometrics, ask whether the claim is ordinary selfie face match or the much narrower valid-digital-certificate/PIV lane.
Notary Geek position
Virginia's current statute can support some current remote identity workflows when the actual methods line up with the law.
That does not retroactively make older KBA sessions valid, and it does not turn selfie-to-ID face match into a digital certificate accessed by biometric data.
Identity lanes
The current Virginia statute gives specific paths. Each path leaves different evidence.
This is a plain-English map of the current Virginia section 47.1-2 structure. It is not legal advice and does not decide any particular transaction.
| Lane | Plain-English meaning | Evidence to ask for |
|---|---|---|
| Personal knowledge | The notary personally knows the principal before the act. | Journal method, relationship facts, audio-video statements if relevant, and whether the notary's claim is credible. |
| Credible witness | A qualifying witness personally knows the principal and is either known to the notary or identified under the statutory method. | Witness identity, witness relationship, witness independence, oath or affirmation, journal, and recording. |
| At least two listed methods | The principal is identified by at least two listed methods, such as credential analysis plus KBA under current law. | Separate records for each claimed method. Do not let one software workflow be counted twice under different labels. |
| Credential analysis | Analysis of an unexpired government-issued ID bearing a photo and signature. | ID type, document-analysis result, time, vendor, and whether the record proves document analysis rather than a mere upload. |
| Antecedent in-person identity proofing | A prior in-person identity proofing process meeting the specified Federal Bridge Certification Authority-related standard. | Who proofed the signer in person, when, under what standard, and what record connects that proofing to this transaction. |
| Another authorized method | Another identity proofing method authorized in proper Virginia guidance, regulation, or standard. | The exact adopted source, date/version, mapping to the transaction, and audit log showing the method actually ran. |
| Valid digital certificate / PIV | A valid digital certificate accessed by biometric data, or a compliant PIV/PIV-I-style card. | Signer certificate, issuer, subject, serial, policy, trust path, revocation status, key-control route, and biometric access event. |
| KBA | Knowledge-based authentication assessment, added to the statutory list effective July 1, 2024. | KBA vendor/result, pass/fail, date/time, question source category, retry history if relevant, and whether the act date was on or after July 1, 2024. |
Timeline
Pre-July-1-2024 and post-July-1-2024 Virginia sessions are not the same analysis.
Virginia's 2024 change matters because KBA appears in the current statutory list, but it should not be read backward into older transactions. For acts before July 1, 2024, a KBA-based unknown-signer workflow raises a different legal question than a current workflow where KBA is actually listed and actually completed.
The other major point did not change: KBA being added did not add ordinary selfie/liveness/face-match as a standalone Virginia identity method. A current transaction still needs the actual statutory pair or another proper lane.
Use the date first
Before July 1, 2024: do not assume KBA was available as a Virginia statutory method.
On or after July 1, 2024: KBA may be one method if it actually ran and passed, but it does not equal credential analysis or certificate biometrics.
Pairing analysis
For current Virginia law, the hard part is often the second method.
If the signer is not personally known and no credible witness is used, current Virginia law points toward at least two listed methods. The practical question is whether the provider has two real statutory methods, not one method plus a renamed risk check.
Credential analysis plus KBA
This is the cleanest current unknown-signer theory if credential analysis and KBA both actually ran, passed, and were recorded. It still depends on the transaction date and evidence.
Credential analysis plus another authorized method
This needs the exact Virginia-adopted guidance, regulation, or standard authorizing the second method. A vendor FAQ is not enough.
Credential analysis plus selfie face match
Selfie/liveness/face match may be useful anti-fraud evidence, but it is not automatically the certificate/PIV lane and should not be silently counted as the second method.
Credential analysis plus certificate/PIV
If claimed, ask for signer certificate or PIV/PIV-I evidence. The notary's seal certificate, document-signing certificate, and stamp image do not identify the signer.
Certificate roles
The notary's X.509 certificate is not the signer's identity method.
A Virginia electronic notarization may involve a notary-side X.509 certificate, an electronic seal, and a stamp image that makes the completed PDF look like a notarized record. Those objects answer document-completion questions: who applied the notarial act, whether the file was sealed or digitally signed, and whether tampering after completion can be detected.
Those objects do not answer the signer-identity question. If the Virginia certificate/PIV identity lane is claimed, the evidence must point to the signer's certificate or PIV-style credential, not the notary's signing certificate, not the notary stamp image, and not a generic platform seal.
A signer may also digitally sign the PDF. That still has to be analyzed by role: was it merely an electronic document signature, or was it the actual signer-controlled certificate-backed identity credential used as satisfactory evidence under Virginia law?
Control test: identify whose certificate it was, what it was used for, who issued it, what key or credential was controlled, what trust path applied, and how that object maps to the Virginia statutory identity lane.
Venue and location
Virginia's electronic-notary certificate has a location signal ordinary in-person acts do not use the same way.
Virginia Code section 47.1-16 includes language requiring a notarial certificate for an electronic notarization to include the county or city within the Commonwealth where the electronic notary public was physically located at the time of the notarial act. That matters because it creates a document-level signal about where the Virginia electronic notary was physically located.
Do not collapse that into generic venue language. If the certificate says a Virginia city or county, ask whether the electronic notary was actually physically there at the time of the act and what journal, recording, IP, device, or platform record supports it.
Evidence question
If a Virginia electronic notarization certificate names a Virginia city or county, what proves the notary was physically located there at the time?
Savings clause
"Not invalidated solely because" is not a free compliance pass.
Virginia Code section 47.1-20.1 says no notarial act shall be invalidated solely because of the notary's failure to perform a duty or meet a requirement specified in the title. But the same language preserves other routes: an aggrieved person may still seek to invalidate the record or transaction or seek other remedies, and the provision does not validate a purported notarial act by someone not authorized to perform it.
That means the safer public statement is careful: a defect may not automatically void the notarial act by itself, but the underlying record or transaction may still be challenged, and transaction evidence still matters.
Careful wording
Do not say every defective Virginia act is automatically invalid.
Do say the defect can matter as evidence and may support a challenge to the record, transaction, or remedies.
Research cluster
This page is the statutory map. The other pages handle the investigation and security architecture.
Use this page when the question is "what does Virginia actually allow?" Use the 2016 guidance page when the question is "what do these security words mean?" Use the biometrics myth page when the question is "why is the platform-biometric AI answer wrong?"