RON state readiness

Where SealBook can launch remote online notarization.

RON is controlled by the notary's commission state. This page separates three things: whether RON is legally available, whether SealBook is approved or ready as a provider, and whether an individual notary has completed onboarding.

Ready: 0Approval pending: 45Blocked: 6
Notary onboarding checklistVA/MD/DC/WV/PA plan
Production rule
State lawallowed
SealBook providerpending
Notary docsrequired
Start ceremonyblocked until verified
USA map

State-by-state SealBook RON readiness

Click a state. Yellow means RON may be available but SealBook approval/compliance work is still pending. Red means do not enable production RON for notaries commissioned there.

First approval sprint

VA, MD, DC, WV, PA action plan

Remote notarization not currently implemented

District of Columbia

Authority/body: D.C. notary office rules/implementation approval not fully live per FAQ checked

SealBook approval work: DC FAQ says remote notarizations are not allowed at this time, even though a law was passed. Keep DC commissioned notaries blocked for production RON until the office changes implementation status.

Notary must do: D.C. Code authorizes remote notarization, but D.C. notary FAQ has warned remote notarizations were not implemented. Require written confirmation of live process, rules, and any registration before enabling.

Retention: 10 years by D.C. Code

Official source

Vendor authorization required before SealBook can be selected

Maryland

Authority/body: Maryland Secretary of State remote notary notification/registration

SealBook approval work: Maryland has explicit authorized remote online notary vendor criteria: U.S. incorporation, U.S.-based company operating at least 3 years, U.S. encryption/decryption, commercially reasonable technology, 10-year A/V retention, and notary access to recordings.

Notary must do: Hold Maryland commission; notify/register with SOS for remote notarial acts; identify communication technology/provider; comply with rules before use.

Retention: 10 years

Official source

Approved technology provider path required

Pennsylvania

Authority/body: Pennsylvania Department of State RON technology notification

SealBook approval work: Pennsylvania permits remote notarization, but notaries identify approved technology. SealBook needs provider application/approval/listing before PA notaries can select it for production RON.

Notary must do: Hold PA commission; notify Department of State that notary will perform RON; identify approved communication technology; wait for approval/acceptance if required.

Retention: 10 years unless Dept. sets another period

Official source

RON/e-notary allowed; SealBook conformity packet pending

Virginia

Authority/body: Virginia Secretary of Commonwealth electronic notary registration

SealBook approval work: No separate public vendor approval list confirmed in this pass. SealBook needs a Virginia conformity packet against e-notary/RON standards, identity proofing, secure live A/V, certificate wording, and 5-year record retention before production.

Notary must do: Hold Virginia commission; register as electronic notary; use compliant secure A/V and electronic notarization technology; receive e-notary registration before use.

Retention: 5 years

Official source

Electronic/RON path exists; SealBook technology review/listing pending

West Virginia

Authority/body: West Virginia Secretary of State remote online notarization process

SealBook approval work: WV notaries select technology meeting 153 CSR 45, submit e-Notarization Authorization Form N-2, and must notify SOS if technology changes. SealBook should request inclusion/review and document remote-use compliance.

Notary must do: Hold WV commission; register/qualify for RON if required; use compliant communication technology; comply before first act.

Retention: 5 years unless otherwise provided

Official source

Approval operating model

How we get approved state by state

Classify the state. Allowed, vendor approval/listing required, notary-only notification, no formal vendor approval found, or blocked/not implemented.
Build the state launch file. Official statute/rule links, provider application or listing process, sample certificate wording, retention, identity proofing, recording, journal, export, incident, and shutdown obligations.
Submit vendor packet where needed. Company profile, security architecture, identity/KBA/credential analysis flow, A/V recording custody, retention, audit trail, disaster recovery, privacy/DPA, incident response, and sample notarized document.
Configure product gate. Set state to pending until approval evidence is stored; block Start Ceremony in production when state, provider, identity, certificate, or notary documents are incomplete.
Onboard notaries. Collect commission proof, RON/e-notary authorization, digital certificate, e-seal, bond/E&O/training if required, and signed SealBook terms.
Corporate foreign qualification is a separate tax/business-law analysis. It is not the same as RON vendor approval. Do not register in all 51 jurisdictions just because users may exist there; have counsel review nexus and physical operations.