A phone showing a verification ring
Case study: Scenario, to confirm

When the signal drops, the closing table still knows who is signing.

Notarized.com puts an Implexus mark on every signing invite. Identity checks and signing approvals run on the signer's and notary's phones, on a video call or at a kitchen table with no coverage.

Real estate and legal services

The partner

About Notarized.com

A notarization and real estate document platform for title and escrow firms, notaries and individual signers.

Founded
To confirm.
What it does
Remote online notarization, traveling notary visits, e-signature, e-recording, deed preparation and FinCEN reporting.
Where
United States.
Regulation
State notary law, state by state. To confirm.
Scale
Not quoted. No usage figures have been verified.
Direction
Identity checks that work online and off, including at a property with no signal.

Described from Notarized.com's own product documentation, not verified by Implexus. Notarized.com's wordmark and colours are used here with the owner's direction.

Identity at the closing table

Every signing keeps working, because the check happens on the phone.

Notarized.com runs signings over video and in person, including at homes, farms and basements where the phone has no signal. Today the identity check waits on the internet. In this scenario the check runs on the signer's and notary's phones, and the record syncs when the link returns.

The case at a glance
Environment
A signing with a notary, over video or in person, where the network sometimes fails
What was imploded
The signing's identity, as a strand held by Notarized.com
What travelled
A descriptor, fifteen characters, on a printed mark or a screen
What regenerated
The signing, on the notary's phone, one at a time or a stack at a time
What was controlled
Who may see the ID record, for how long, and what the notary may do with it
What was measured
Being validated
Status
Scenario, to confirm

Scenario for discussion. The deployment described is proposed, not live, and no figure here has been measured. Notarized.com facts are taken from its own product documentation.

Before and after the mark

The same notary, the same signer, the same table.

Before
  • Identity checks run through hosted provider flows and stop when the link drops.
  • A signer with a weak connection cannot finish.
  • A traveling notary cannot confirm who is in front of them.
  • The quiz-style knowledge check is a weak fallback, because the answers can be looked up or supplied by a bot.
After
  • The notary scans the mark on the invite, or types its fifteen characters.
  • The signer taps a wallet ID or reads an ID chip. The notary's phone checks the issuer's signature and compares the face.
  • Nothing needs the network. The cancellation check and the journal entry sync afterwards.
  • A deed needs a strong method, and a weaker one is refused before the signer starts.

Scenario for discussion. The deployment described is proposed, not live, and no figure here has been measured. Notarized.com facts are taken from its own product documentation.

A bank archive of steel drawers, one glowing
In practice

A notary and a signer meet at a farmhouse with no signal.

  1. 01First

    The notary scans the mark on the invite, or types its fifteen characters. The descriptor names the signing and the document's weight. It names no person.

  2. 02Then

    The signer is identified on the device. The app offers only methods strong enough for this document, and the signer approves exactly which fields are shared.

  3. 03Finally

    The notary sees the method, the level reached and one line saying the cancellation check is queued. Implexus says whether the credential is authentic. The notary decides whether to proceed, and recording is held until the queued checks pass.

Scenario for discussion. The deployment described is proposed, not live, and no figure here has been measured. Notarized.com facts are taken from its own product documentation.

Design outputs

What the signer and the notary see.

A concept mock of the Notarized.com ID-Verify app, with three ways to decode the mark: scan, type it, or a whole stack at once.

  1. Phone screen: scan your signing code, with the Implexus mark in the viewfinderScanThe mark zooms from a point out to the full mark. The fifteen characters sit below it.
  2. Phone screen: typing the fifteen characters, with a look-alike character flaggedType itFifteen boxes in groups of five. A notary or clerk can read or type the line for the signer.
  3. Phone screen: a stack of decoded strands with a regenerate buttonBulk and regenerateA closing day's invites in one stack. Files stay locked until each signer has verified.
  4. Phone screen: choosing a method strong enough for a deedChoose how to prove itA deed needs a strong method. A photo and selfie alone is shown as not enough.
  5. Phone screen: identity checked offline with the cancellation check queuedOffline at the propertyNo signal, still checked. The cancellation check waits for the link.
  6. Phone screen: notary review of the grantor with level reached and queued checksNotary reviewImplexus says the credential is authentic. Whether to proceed is the notary's decision.
Animated Implexus mark: one point opens to four squares, then zooms out to an X of sixteen squares inside scanner corners
The Implexus scan mark. One point opens into four squares, then zooms out to an X of sixteen: fifteen for the characters and one to check them.
Animated strip reading Powered by Implexus beside the small Implexus mark
The footer strip. Shown at the foot of every screen.

Concept mock with sample names and descriptors, in Notarized.com's own colours. Not a released Notarized.com design.

What holds, online or off

Identity before access

Nobody sees an ID record until the signer is identified and has said yes. The order does not change when the link is down.

Notarized.com keeps the record

The journal and any retention follow the state's notary rules. Implexus holds no copy of the ID.

Two decisions stay apart

Implexus says whether the credential is authentic. The notary and Notarized.com say whether to proceed.

What was measured, and what it is not

No result is stated until it has been measured, with its method and date.

Signings finished with no connection
Being validatedBeing validated
Time to verify a signer
Being validatedBeing validated
Signings stopped for failed ID
Being validatedBeing validated
What it is not
Not a way to see offline that an ID was cancelled this morning. That check is queued and re-run when the link returns, and the notary is told if it fails.

Questions about this case

Draft answers. To confirm with product and engineering.

Which IDs work offline?

Wallet IDs shared by tap or QR code, and passport or ID card chips read by the phone. Both are checked against the issuer's signature on the device. Chip checks need the issuing countries' certificates stored on the phone beforehand.

What if the call drops in a remote session?

The proposal is that the verified status stays on that phone for ten minutes, then a quick face check resumes the session. The ten minutes is a proposal, not a measured setting.

Is this live?

No. It is a scenario for discussion. The deployment is proposed and nothing here has been measured.

Have a signing where the link is not always there?

Tell us the table, the phone and the check you need to make before anyone signs.