Case study
WFG Title and the source question.
This case study preserves the practical question raised by Notary Geek: when title practice, platform lists, or foreign-signer RON instructions treat a workflow as acceptable, what legal source proves the notary identity method complied with the commissioning state’s law?
Why WFG is here
WFG is the case study, not the whole problem.
Notary Geek uses WFG Title as a case study because the preserved record includes public WFG materials, title-platform-list communications, foreign-signer RON concerns, and a later takedown/trademark objection involving this domain.
The broader concern is title-policy laundering: private title or underwriting policy can be repeated until notaries, customers, platforms, and AI systems mistake it for notary law.
Core distinction: title acceptance may explain why a deed or closing package moved forward. It does not prove that the commissioned notary used a lawful statutory identity method.
Timeline
The timeline matters because the law changed.
2011/2012Virginia’s early electronic-notary framework used Federal Bridge, valid digital certificate, biometric access, and PIV/PIV-I-style language.
2020WFG public bulletin material addressed Florida RON requirements and Virginia RON notaries, including credential analysis and KBA language.
2023Notary Geek encountered the title-market foreign-signer routing issue directly and began documenting the Virginia/Florida/title-policy conflict.
2024Virginia added knowledge-based authentication assessment effective July 1, 2024. That affects KBA workflows going forward, but not current no-KBA selfie/passport workflows.
2025WFG-related platform-list and domain/trademark pressure became part of the preserved source record.
TodayThe current problem remains when “Virginia allows biometrics” is used to justify ordinary selfie-to-ID matching for foreign signers without identifying the statutory method.
Questions for WFG
The questions Notary Geek wants answered.
| Question | What would answer it |
|---|---|
| Before July 1, 2024, what Virginia identity method did WFG believe was being used for unknown foreign signers? | A dated source identifying the statutory method and explaining how the transaction record proved it. |
| Did WFG treat selfie-to-passport matching as Virginia biometrics? | A source showing whether WFG distinguished generic face match from a valid digital certificate accessed by biometric data. |
| What did an approved or accepted platform list mean? | A clear statement separating title-insurance acceptance from notary-law compliance. |
| Did anyone rely on a statement that NotaryCam or another RON platform was officially approved by Virginia? | The exact Virginia government source, scope, date, and workflow approved. If the source is only vendor, title, trade, or AI language, say that clearly. |
| For current transactions, does WFG distinguish KBA workflows from no-KBA selfie/passport workflows? | A current policy explaining when KBA is used, when it is not, and what statutory methods support non-KBA foreign-signer sessions. |
| Did the trademark/domain objection answer the notary-law issue? | If yes, identify the answer. If no, separate the trademark claim from the compliance question. |