Proof for title Pro

Identity Verification FAQs

How does Proof verify a signer’s identity during an online closing?

During a Close transaction, Proof verifies signer identities using:

If a signer is unable to complete KBA (typically due to not having a U.S. Social Security Number) they may be asked to take a biometric selfie, which is then compared in real time to their government-issued ID.

How does Proof verify a signer’s identity during an online notarization?

During a Notarize transaction, Proof verifies signer identities using:

How does Proof verify someone’s identity during an identity verification request?

Proof’s Identify solution gives businesses the flexibility to combine multiple verification methods based on their specific use case, including:

For NIST IAL2 identity verification, Proof uses credential analysis and a real-time biometric selfie check to confirm the signer’s identity. If a signer cannot be verified through the selfie comparison, they are routed to a Trusted Referee from the Notarize Network for live verification at an additional cost.

Can Proof verify someone’s identity as part of an eSign transaction?

Proof’s Sign solution offers flexible options during an eSign transaction, allowing businesses to combine multiple methods based on the level of assurance needed, including:

SMS authentication;
Knowledge-Based Authentication (KBA);
Credential analysis with selfie comparison; and/or
NIST IAL2-compliant identity verification

Priority Level

Conditions

Level 1

Critical Business Impact. The Incident seriously affects the functionality of the Services (or component thereof) and cannot be circumvented such that most of the significant functionality of the Services (or component thereof) is available.

Level 2

Significant Business Impact. The Incident partially affects the functionality of the Services (or component thereof), but can be circumvented so that most of the significant functionality of the Services (or component thereof) is available.

Level 3

Minimal Business Impact. The Incident can be circumvented such that the Services (or component thereof) can be used with only slight inconvenience. The problem can be considered insignificant and has no significant effect on the usability of the Services (or component thereof).

Priority Level

Conditions for Closure of Help-Desk Ticket

Level 1

The Incident is considered resolved and closed when an Incident Resolution has been fully implemented.

Level 2

The Incident is considered resolved and closed when an Incident Resolution has been fully implemented.

Level 3

The Incident is considered resolved and closed when one of the following occurs: (i) an Incident Resolution has been fully implemented, or (ii) 10 business days have elapsed since Proof’s communication of the information that Proof reasonably believes will resolve the Incident (communicated by email to Subscriber’s designated contact for such Incident), and Subscriber has not responded to Proof. The Incident can be reopened later if it has not been resolved.

Cumulative On-Demand Notary Availability Downtime
(in a given calendar month as measured by Proof monitoring systems, converted to minutes)

On-Demand Notary Downtime Credit

Up to 240 minutes

No On-Demand Notary Downtime Credit

241-360 minutes

361-480 minutes

481-600 minutes

601 minutes or greater

Platform Availability Percentage
‍(in a given calendar month as measured by Proof monitoring systems)

Platform Downtime Credit

99.9% or higher

No Platform Downtime Credit

97% - 99.9%

95% - 97%

93% - 95%

Below 93%

Incident Priority

Acknowledgement Time (During Business Hours)

Provision of Incident Resolution or Interim Process

If Interim Process is provided, Maximum Timeframe for Provision of Incident Resolution

Level 1

1 hour

8 hours

36 hours

Level 2

4 hours

24 hours

5 days