Set Up eOriginal Vault

The short answer: Before connecting eOriginal to Proof, real estate org admins need to configure the required status values, API user, and transaction type in both the Test On Demand and Production eOriginal environments. Work directly with your eOriginal representative if you need help setting up or maintaining your eVaults.

eOriginal provides two environments:

• Test On Demand (TOD) — connects to your Proof Fairfax account for testing eNotes before going live.
• Production — connects to your Proof Production account once testing is complete.

Set up both environments identically to ensure testing accurately mirrors your production configuration. Once your vaults are configured, see Connect eOriginal to Proof for next steps.

Status Values

Proof requires the following status values to be set in both eOriginal environments. If a status value is missing, Proof will display an error in its logs — contact your Proof Solutions Engineer if this occurs.

In the eOriginal Dashboard, open Preferences and navigate to Status Values:

Confirm the following six status values are set:

• Created — scope: Transaction
• Ready to Sign — scope: Document
• Signed — scope: Global
• Complete — scope: Global
• Authoritative Copy — scope: Document
• Ready to Register — scope: Global

API User Setup

Proof adds documents to your eOriginal vault via API. eOriginal admins can create API users under Preferences > Vault Administration > API Users.

Create a dedicated API user for Proof with the following settings:

• API Login ID — create your own name, typically something like "notarize-integration"
• Application — create your own name; this appears in the audit trail as the First Name. Either this or the Purpose field should contain "Notarize"
• Purpose — create your own name; this appears in the audit trail as the Last Name
• Email — support@proof.com
• Permissions — at minimum:
  • Create Document Profile
  • Create Transaction
  • Full Org Search
  • Get Org Configuration
  • Throw Custom Event
• Container Permissions — at minimum:
  • Authorize Document Destruction
  • Cancel Document Destruction
  • Create New Version
  • Delete Document Profile
  • Delete Transaction
  • Edit Transaction/Document Properties
  • MERS Register eNote
  • MERS Register eNote Reversal
  • Reject Document Destruction
  • Request Document Destruction
  • Retrieve Document
  • View Document Activity History Report
  • View Transaction/Document Properties

Transaction Types

Create a "Notarize Closing" transaction type with the following settings:

• Name — Notarize Closing
• Retention Policy — None
• Container Permissions — Default Container Permissions
• Status — Created
• Signing Rules Expiration Days — 0
• Active — check this box
• eSign option — eSign and eAsset Management
• For Third-Party Closing (Mortgage) — No
• Included Documents — leave blank

Once both environments are configured, see Connect eOriginal to Proof for next steps.

Summary Checklist

• All six required status values are configured in both Test On Demand and Production eOriginal environments.
• A dedicated Proof API user has been created with the required permissions and container permissions in both environments.
• The "Notarize Closing" transaction type has been created and set to Active in both environments.
• I'm ready to proceed to Connect eOriginal to Proof.

Updated June 25, 2026 14:51