Using the Notary Block functionality

Overview/Background

One of the methods employed by eNotaries is the use of a digital signature and digital notary seal to notarize digital documents and validate them with a digital certificate. Electronic notarization is a process whereby a notary affixes an electronic signature and notary seal using a secure Public key to an electronic document (such as a PDF or Word document). Once affixed to the electronic document, the document is rendered tamper evident such that unauthorized attempts to alter the document will be evident to relying parties. The eNotary will use cryptography and Public key infrastructure to create, manage, distribute, use, store, and revoke the digital certificate. The eNotary also must keep an electronic register of each action performed.

In most cases, electronic notarization does not mean that the notary can perform the electronic notarization remotely as some states still require that the participants and the notary must all be physically present at the time of signing. There are also significant benefits to having the notarization done electronically such as cost savings, superior security, authenticity, audit trails, and document integrity, which are things that are not available to paper-based notarization.

Best practices and notes when using

A sample response with a Notary signature would appear as follows:

 <r:Signer>
                        <r:Id>NotaryID</r:Id>
                        <r:Description>Notary, Notary</r:Description>
                        <r:SignaturePoints>
                           <r:SignaturePoint>
                              <r:IncludeDate>true</r:IncludeDate>
                              <r:PageNumber>10</r:PageNumber>
                              <r:PageOrder>0</r:PageOrder>
                              <r:Height>36.0</r:Height>
                              <r:Width>162.0</r:Width>
                              <r:SignatureText>NotaryID</r:SignatureText>
                              <r:XCoordinate>37.0</r:XCoordinate>
                              <r:YCoordinate>307.22</r:YCoordinate>
                              <r:Type>Signature</r:Type>
                              <r:SignatureRequired>true</r:SignatureRequired>
                              <r:SignatureUniqueIdentifier>NotaryBlockSection1</r:SignatureUniqueIdentifier>
                           </r:SignaturePoint>

• The fields and signature fields for the Notary will generate without the name, ID, and email address; for typical fillable field use and functionality, name and ID are required; however, when Notary is used, these elements are not required as the Notary is not known at the time of document generation.
• Notary Stamp: A <FieldType> element would contain an enumerated value of NotaryStamp to include an image within the content. This value allows integrators to use the Expere response to determine what field(s) on the document are intended for notary use. Electronic signing partners will then be able to appropriately assign signer roles based on the FillableFieldType. This is an optional requirement and entirely within the control of the eNotary provider and Notary Provider whether to add the image.
• Identifier: A SignatureUniqueIdentifier element is assigned to each Notary field, including FillableText and NotaryStamp fields. The unique identifier is the indicator that the fields are for notary notice; each unique ID signifies a single notary section.
• Role: A Notary role is used with the fillable field and is a requirement when notarizing and signing.

Signature Fields

Signature fields contain a unique ID, which is used to link to the associated notary fields.