Architectural overview

ENotary Packages are a specialized type of package in the Pactima eSignature API that facilitate electronic notarization processes. They are designed to accommodate the specific requirements and workflows associated with notarizing documents electronically.

High-level Data Model

The high-level data model for ENotary Packages includes the following key components:

{
  "id": "string",
  "isTestMode": boolean,
  "ownerId": "string",
  "eSignaturePackageId": "string",
  "validationRequests": [
    {
      "signerId": "string",
      "idv": {
        "enforcementCriterion": "REQUIRED" | "OPTIONAL" | "SKIP"
      },
      "kba": {
        "enforcementCriterion": "REQUIRED" | "OPTIONAL" | "SKIP"
      },
      "locationVerification": {
        "enforcementCriterion": "REQUIRED" | "OPTIONAL" | "SKIP"
      }
    }
  ],
  "validationResponses": [
    {
      "signerId": "string",
      "idv": {
        "id": "string",
        "outcome": "PASSED" | "FAILED" | "SKIPPED"
      },
      "kba": {
        "id": "string",
        "outcome": "PASSED" | "FAILED" | "SKIPPED"
      },
      "locationVerification": {
        "id": "string",
        "outcome": "PASSED" | "FAILED" | "SKIPPED"
      }
    }
  ]
}

Relationship to eSignature Packages

ENotary Packages are closely related to eSignature Packages and are linked to them via the eSignaturePackageId property. This property establishes a connection between an ENotary Package and its corresponding eSignature Package.

There are two main types of ENotary Packages:

1. RON (Remote Online Notarization): RON packages correspond to the LIVE kind of eSignature Package. They are used when the notarization process is conducted remotely, with the signer and notary participating in a live video session.

2. IPEN (In-Person Electronic Notarization): IPEN packages correspond to the IN_PERSON kind of eSignature Package. They are used when the notarization process is conducted in person, with the signer and notary physically present in the same location.

The eSignaturePackageId property in the ENotary Package model serves as the link between the ENotary Package and its associated eSignature Package. This linkage allows for seamless integration and coordination between the notarization process and the overall signing workflow.

Validation Requests

One of the key features of ENotary Packages is the concept of validation requests. Validation requests are used to specify the authentication and verification requirements for each signer participating in the notarization process.

The validationRequests property in the ENotary Package model is an array of objects, where each object represents a validation request for a specific signer. Each validation request can include the following properties:

• signerId: The ID of the signer for whom the validation request applies.
• idv: Identity verification settings, specifying the enforcement criterion for identity verification (REQUIRED, OPTIONAL, or SKIP).
• kba: Knowledge-based authentication settings, specifying the enforcement criterion for KBA (REQUIRED, OPTIONAL, or SKIP).

The enforcement criterion determines whether the corresponding validation step is mandatory, optional, or skipped for the signer.

Validation Responses

As signers go through the notarization process, the results of their validation steps are captured in the validationResponses property of the ENotary Package. Each validation response object contains the following properties:

• signerId: The ID of the signer associated with the validation response.
• idv: Identity verification response, including the ID of the identity verification package and the outcome (PASSED, FAILED, or SKIPPED).
• kba: Knowledge-based authentication response, including the ID of the KBA package and the outcome (PASSED, FAILED, or SKIPPED).

The validation responses provide a record of the authentication and verification results for each signer, ensuring the integrity and validity of the notarization process.

Other Considerations

When working with ENotary Packages, there are a few additional considerations to keep in mind:

• Notary Public: The owner of an ENotary Package must be a valid notary public. The API enforces this requirement and ensures that only authorized notaries host the notarization process.