Demonstration systemThis is a demonstration of the business system around remote online notarization. It is not a compliant remote online notarization platform, it performs no legal notarizations, and it is not registered in any state.
FairmountNotary ServicesGet started

Fairmount Notary Services LLC · Demonstration build

The notarization business, and the evidence it leaves behind.

One order, followed end to end: intake and payment, identity gating, the notarial session, a sealed and independently verifiable document, and an electronic journal whose entries cannot be edited without the next entry giving it away.

Get startedSee what it does
Electronic journalAdd-only · every entry locked to the last
Each entry carries a fingerprint of the entry before it. Change one and every entry after it stops matching — which is what makes tamper-evidence something an auditor can check for themselves rather than something we assert.

Compliance boundary

This is a demonstration of the business system around remote online notarization. It is not a compliant remote online notarization platform, it performs no legal notarizations, and it is not registered in any state.

The notarial act, identity proofing, recording retention, and the seal of record are the responsibility of a state-approved RON provider, never of this system. Fairmount’s own commissioned notaries perform the acts through that provider; this is everything built around it. Nothing here creates a notarial record, and nothing here should be relied on as one.

The pipeline

What this demonstrates

The parts a notary business owns: the pipeline, the money, the gates, the evidence, and the administration around them.

  1. 01

    Order intake

    A signer uploads a document and chooses the notarial act and the state of jurisdiction. The file is validated before payment — type, page count, size — so nobody discovers a problem after being charged. Each order is allocated a human-readable reference whose sequence resets every year.

  2. 02

    Payment

    Checkout runs through Stripe in test mode. A refund is a step the system performs and records on the order timeline, not a correction someone makes in Stripe and remembers to mention.

  3. 03

    Identity gating

    Credential analysis and knowledge-based authentication run as two gated steps with a capped number of attempts. A failed check is modelled as an ordinary outcome with its own status and its own admin metric — never as an error page.

  4. 04

    Notarial session

    Scheduling, the session view, and the recording indicator, with a retention deadline derived from the jurisdiction and surfaced to administrators before it lapses.

  5. 05

    Sealing and release

    The completed document is digitally signed, and a fingerprint of the exact file is kept so any later copy can be checked against it. Sealed documents unlock at release, not at completion — and the file is genuinely withheld until then, not merely hidden from the screen.

  6. 06

    Electronic journal

    Every act writes one journal entry, and each entry is locked to the one before it. Entries can be added and never edited or deleted — there is no way to do either, for anyone, including Fairmount. A check runs the whole journal and names the first entry that does not match.

  7. 07

    Administration

    Pipeline metrics, journal search and CSV export, retention alerts, on-screen previews of every notice the system would send, and a per-order evidence bundle.

Scope

What it deliberately does not do

Each of these is a design decision with a reason, not an unfinished corner.

The notarial act itself
In production this runs through a state-approved RON provider — Proof, BlueNotary, NotaryCam — performed by your own commissioned notaries under that provider’s compliance regime. Here the provider is simulated, but it is connected at a single, real seam built to the shape of Proof’s live interface. Switching to a live account is a settings change, not a rebuild.
Retention of identity material
Government IDs, ID images, and authentication questions and answers are never stored, logged, or cached by this application. Only the outcome is kept: method, status, attempt number, and timestamp.
A seal of record
The signature applied to a sealed document uses a self-signed certificate. It demonstrates the mechanism — a tamper-evident, independently verifiable document — not a legally operative seal.
Anything involving real people
Every name, address, document, and payment in this demonstration is synthetic. No live credentials are configured and no notice is actually sent to anyone.

Entry points

Where to start

Four ways in, one per audience. Signers need no account; staff enter a shared per-role passphrase; verification is open to anyone holding the file.