The following relates to a method and system for conducting an electronic signing ceremony, and more particularly an electronic signing ceremony system and method that can consolidate and streamline the process of originating, organizing, signing, verifying, storing, and retrieving multiple documents requiring multiple signatures virtually anywhere and at any time.
A detailed description and accompanying drawings are set forth below.
As required, detailed embodiments of the present application are disclosed herein. However, it is to be understood that the disclosed embodiments are merely exemplary of the invention that may be embodied in various and alternative forms. The figures are not necessarily to scale, and some features may be exaggerated or minimized to show details of particular components. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a representative basis for teaching one skilled in the art to variously employ the teachings of the present application.
The eSign Act of 2000 defines an electronic signature broadly to encompass a wide variety of different ways that two individuals have available when they want to meet and have an understanding. Non-limiting examples of electronic signatures identified in the eSign Act include a symbol, sound or process. According to the eSign Act, an electronic signature must attest to both the meeting of two minds and the willingness of two minds to meet. Handwritten signatures or electronic signatures (e.g., captured using a signature pad) have limited capabilities, since they can only partially attest to the former. The mathematics related to “digital signatures” are an improvement over handwritten signatures because it provides a certain and secure way to attest not only that two minds met and agreed on a subject but also when the meeting occurred.
The willingness of two minds to meet, which is often called “intent to sign,” has not been properly addressed to date because current systems revolve around the notion of an audit trail. As the word “audit” implies, an audit trail attests to what has happened during a signing session, i.e., an audit trail is nothing more than a reporting mechanism. In addition, an audit trail, by its nature, is a reflection of the signing session. If the signing session is a fragmented set of disjointed signing activities, the audit trail will also be fragmented, falling short from capturing intent properly.
The eSign Act focuses on the context of obtaining a digital signature as reinforcing or negating the validity of a digital signature. The systems on the marketplace today do not take advantage of this focus. Instead, the systems ensure the validity of a party's signature within a single page of a document. Other systems proceed to specify the type of signature or impose an order on how digital signatures are to be obtained, but within the confines of a single document. However, none of these systems take full advantage of the benefits of the eSign Act.
In light of the foregoing, there exists a need to provide a system and method of using the context of a signing ceremony to reinforce or negate the validity of a digital signature.
The electronic signing ceremony method and system embodiments described herein can be carried out using a computer. Moreover, the computer may be programmed, e.g., via the development of a computer program, to carry out the steps and functionality of the method and system embodiments disclosed herein.
Computer 12 includes volatile memory 22, non-volatile memory 24 and central processing unit (“CPU”) 26. Non-limiting examples of non-volatile memory include hard drives, floppy drives, CD and DVD drives, and flash memory, whether internal, external, or removable. Volatile memory 22 and/or non-volatile memory 24 can be configured to store machine instructions and other information. CPU 26 can be configured to execute machine instructions to implement functions of the present application, for example, executing an electronic signing ceremony according to one or more embodiments of the present application. Volatile memory 22 and/or non-volatile memory 24 can be configured to store data relating to a signing ceremony.
Display 14 can be utilized by the user of the computer 12 to view content relating to an electronic signing ceremony and to conduct the signing ceremony through a ceremony session. A non-limiting example of display 14 is a color display, e.g. a liquid crystal display (“LCD”) monitor or cathode ray tube (“CRT”) monitor.
The user input device 16 can be utilized by a user to input instructions to be received by computer 12. The instructions can be instructions for receiving a digital signature of a user. The user input device 16 may be an electronic signature pad, a keypad, a microphone, or a fingerprint scanner. In other embodiments, the user input device 16 can be a keyboard having a number of input keys, a mouse having one or more mouse buttons, a touchpad or a trackball, or combinations thereof.
Computer 12 can be configured to be interconnected, wired and/or wirelessly, to network 20, through communication line 18, for example, a local area network (“LAN”) or wide area network (“WAN”), through a variety of interfaces, including, but not limited to dial-in connections, cable modems, high-speed lines, and hybrids thereof. Firewalls can be connected in the communication path to protect certain parts of the network from hostile and/or unauthorized use.
Computer 12 can support TCP/IP protocol which has input and access capabilities via two-way communication lines 18. The communication lines can be an intranet-adaptable communication line, for example, a dedicated line, a satellite link, an Ethernet link, a public telephone network, a private telephone network, and hybrids thereof. The communication lines can also be intranet-adaptable. Examples of suitable communication lines include, but are not limited to, public telephone networks, public cable networks, and hybrids thereof.
In one embodiment, an electronic signing ceremony method and system is disclosed. The electronic signing ceremony may include a number of defined steps performed by one or more people on a number of documents in a predetermined order. A non-limiting example of an electronic signing ceremony is a mortgage transaction. For instance, a mortgage banker may create an electronic signing ceremony that includes a number of documents that are signed by the mortgage banker's customer, e.g., a home buyer and spouse.
As used in one or more embodiments, a step is an activity performed on a document. For example, a step may be the presentment and execution of a signature. As used in one or more embodiments, a signature is a digital way to bind a signer to a document. Non-limiting examples of signatures include an electronic signature, biometric signature, infometric signature, cryptographic signature, electronic sound, symbol, video, song or process. As used in one or more embodiments, a document means information in an electronic format. Non-limiting examples of documents include a loan application, a claim form, a lease agreement, and an insurance form. As used in one or more embodiments, a page is a well-defined part of a document.
Referring to
The ceremony template module 140 may include functionality to generate a ceremony template. A ceremony template can be used external to the signing ceremony system to generate an electronic ceremony for use with a ceremony execution module, as described in detail below. The ceremony template may be a document including one or more blanks that are filled in by the entity building the signing ceremony. For instance, the ceremony template may be a loan agreement document and the one or more blanks may be provided for a borrower's name and address. In one embodiment, the ceremony template document is a PDF document. The loan agreement template can be sent to a bank so that the bank may use its borrower database to provide the information in the one or more blanks.
In another embodiment, the ceremony template may include a number of documents, each having one or more blanks. The ceremony template may also include inputs for collecting and organizing documents, signers and signing devices by the bank or other entity responsible for such activities. As mentioned above, the result of utilizing the ceremony template is the generation of a signing ceremony that can be utilized by the ceremony execution module 150 during a ceremony session. As used in one or more embodiments, the ceremony session is a session in which a signing ceremony is executed.
As mentioned above, in one or more embodiments, the electronic ceremony system includes a ceremony execution module 150. The ceremony execution module 150 may use a signing ceremony as the input to conduct a signing session, which may include reviewing and signing documents in a ceremony. The ceremony execution module 150 can also be configured to format data from the generated signing ceremony for display on a computer display via a graphical user interface (“GUI”).
The ceremony pane 202 may include a horizontal scroll bar 208 for scrolling content displayed within the ceremony pane 202. As can be seen from
Each document or page depicted within the ceremony pane 202 may include a header portion 218, which includes the activity that is to be carried out on each document or page. Non-limiting examples of activities that can be carried out as depicted in
The page pane 204 may include a vertical scroll bar 222 for vertically scrolling the content displayed within the page pane 204. The content displayed within the page pane 204 may be the current page of the current document.
The GUI 200 thus described can provide the feature of presenting, reviewing and signing the documents in a signing ceremony in a pre-determined order, therefore establishing a sequence for presenting and signing documents. Beneficially, such GUI can display a road map, e.g., the ceremony pane 202, that shows the stepwise progression of the signing ceremony in a pre-determined order.
In one or more embodiments, the ceremony execution module 150 may be configured to record certain data regarding a signing session as an executed ceremony. The recorded data may be stored in a secure database. In one or more embodiments, the executed ceremony includes each document in the signing ceremony, each digital signature within the signing ceremony, a date and time of signature for each digital signature, and the date and time at which each page viewing through the GUI 200 begins.
The contents of the ceremony container, e.g., digital signatures, signers and documents, are described below for developing an example of a ceremony container.
As used herein with respect to at least one embodiment, a digital signature is a secure container that contains a single document, e.g., hash, a single signer, e.g., credentials, and a timestamp bound together. Once it is created, a digital signature secure container may only be read and verified, or destroyed.
As used herein with respect to at least one embodiment, a document is an unsecure container for one or more digital signatures. These documents are considered an unsecure container in that digital signature containers may be embedded and/or removed from the document at will. For example, a portable display format (“PDF”) document does not provide a mechanism to protect embedded digital signature containers from improper access, placement within the PDF document and removal from the PDF document.
In one or more embodiments, the electronic signing ceremony system may include a ceremony validation module 160. The ceremony validation module 160 may use an executed ceremony container as input to conduct a signing validation, which may include validating the steps and activities of the ceremony.
The ceremony validation module 160 may also be configured to format data from the ceremony container for display on a computer display via a GUI.
The ceremony pane 706 can display each document (and each page of each document in one or more embodiments) within the selected signing ceremony. Each document (or each page thereof) may include a status icon generated from a plurality of icons depicting the status of the one or more activities associated with the document (or page thereof) based on the ceremony container of the selected signing ceremony. Non-limiting examples of status icons may include first checkmark 712, second checkmark 714 and “x” icon 716. The first checkmark 712 denotes that the document (or page thereof) has been viewed and the activity has been carried out in the pre-determined order of the signing ceremony. The second checkmark 714 denotes that the document (or page thereof) has been viewed but the activity has not been carried out according to the pre-determined order of the ceremony. The “x” icon 716 denotes that the document (or page thereof) has been viewed but the activity has not been carried out.
In one or more embodiments, the digital signatures and documents used within the signing ceremony described above can utilize the Adobe PDF DigSig standard, available from Adobe Systems Inc. Therefore, the digital signatures generated through the signing ceremony of one or more embodiments of the present application can be verified by the use of the Adobe Acrobat Reader. Furthermore, the signing ceremony system of one or more embodiments of the present application may support other digital signature standards as well. Non-limiting examples include the MISMO DigSig standard for the mortgage industry, the SAFE standard for the pharmaceutical industry, and the NAVA standard for the annuities industry.
According to another embodiment, a computer platform for developing digital signature software products, for example, electronic signature touch pad software products, is disclosed. The computer platform may include an operating system, services, applications, and a software development architecture. The software development architecture can be utilized to develop signing, authentication and signer identification applications.
The computer software platform of one or more embodiments includes the capability to develop one or more software applications for one or more digital signing devices including one or more of the following features: secure access to the Internet, secure transmission of data, secure local storage, and secure storage of the device's credentials for device authentication. The computer software platform includes a toolkit for developing software applications for one or more digital signature devices.
The computer software platform of one or more embodiments includes the capability to develop one or more software applications for one or more digital signing devices for capturing high-quality handwritten signatures, displaying one or more color images, and measuring bio-behavior, e.g., pressure, direction, velocity, etc. The computer software platform may be used to develop applications for smart phones, iPhones, PDAs, tablet-PCs, etc. The platform may be based on the Windows Mobile 6.0 operating system. Alternatively, the platform may be based on Windows XP and VISTA, Mac OS, Linux and Blackberry (Java), and digital signature pads.
The computer platform of one or more embodiments includes the capability to migrate developed software applications from a first digital device to a second digital device. For example, the first digital device may be a desktop computer and the second digital device may be a palm device.
In one or more embodiments, the computer platform includes a fragmented signing engine, which is generally referenced as system 800 in the schematic diagram of
Using the distributed and fragmented signing engine of one or more embodiments, user and signer authentication may be added using the PKI infrastructure of the client and of the server to provide mutual authentication.
While embodiments of the invention have been illustrated and described, it is not intended that these embodiments illustrate and describe all possible forms of the invention. Rather, the words used in the specification are words of description rather than limitation, and it is understood that various changes may be made without departing from the spirit and scope of the invention.
This application claims the benefit of U.S. Provisional Application Ser. No. 61/072,612, filed Apr. 1, 2008.
Number | Name | Date | Kind |
---|---|---|---|
5120908 | Zank et al. | Jun 1992 | A |
5122623 | Zank et al. | Jun 1992 | A |
5544255 | Smithies et al. | Aug 1996 | A |
5666420 | Micali | Sep 1997 | A |
6091835 | Smithies et al. | Jul 2000 | A |
6134326 | Micali | Oct 2000 | A |
6236740 | Lee | May 2001 | B1 |
6307955 | Zank et al. | Oct 2001 | B1 |
6381344 | Smithies et al. | Apr 2002 | B1 |
6613100 | Miller | Sep 2003 | B2 |
6671805 | Brown et al. | Dec 2003 | B1 |
6745327 | Messing | Jun 2004 | B1 |
6796489 | Slater et al. | Sep 2004 | B2 |
6807633 | Pavlik | Oct 2004 | B1 |
6895507 | Teppler | May 2005 | B1 |
6972754 | Zank | Dec 2005 | B2 |
7051206 | Giest et al. | May 2006 | B1 |
7106888 | Silverbrook et al. | Sep 2006 | B1 |
7123143 | Zank et al. | Oct 2006 | B2 |
D532009 | Zank et al. | Nov 2006 | S |
7139910 | Ainsworth et al. | Nov 2006 | B1 |
7143290 | Ginter et al. | Nov 2006 | B1 |
7190815 | Zank et al. | Mar 2007 | B2 |
7200749 | Wheeler et al. | Apr 2007 | B2 |
7221781 | Silverbrook et al. | May 2007 | B2 |
7436397 | Zank | Oct 2008 | B2 |
7526108 | Zank et al. | Apr 2009 | B2 |
7693312 | Zank et al. | Apr 2010 | B2 |
7822690 | Rakowicz et al. | Oct 2010 | B2 |
7876930 | Zank et al. | Jan 2011 | B2 |
7933840 | Zank | Apr 2011 | B2 |
20020053021 | Rice et al. | May 2002 | A1 |
20020091651 | Petrogiannis et al. | Jul 2002 | A1 |
20030078880 | Alley et al. | Apr 2003 | A1 |
20030093677 | Neill | May 2003 | A1 |
20040085355 | Harmes et al. | May 2004 | A1 |
20040181756 | Berringer et al. | Sep 2004 | A1 |
20040193543 | Nord et al. | Sep 2004 | A1 |
20040236694 | Tattan et al. | Nov 2004 | A1 |
20050102520 | Baxter et al. | May 2005 | A1 |
20050177389 | Rakowicz et al. | Aug 2005 | A1 |
20050243371 | Kanaya et al. | Nov 2005 | A1 |
20060161838 | Nydam et al. | Jul 2006 | A1 |
20060179320 | Berringer et al. | Aug 2006 | A1 |
20070022032 | Anderson et al. | Jan 2007 | A1 |
20070078853 | Shutt | Apr 2007 | A1 |
20070118732 | Whitmore | May 2007 | A1 |
20070143324 | Eichhorst | Jun 2007 | A1 |
20070265962 | Bowe et al. | Nov 2007 | A1 |
20080016357 | Suarez | Jan 2008 | A1 |
20080034213 | Boemker et al. | Feb 2008 | A1 |
20080097777 | Rielo | Apr 2008 | A1 |
20080098305 | Beland | Apr 2008 | A1 |
20080235577 | Veluchamy et al. | Sep 2008 | A1 |
20080243554 | Pappas | Oct 2008 | A1 |
20080243662 | Subramaniam | Oct 2008 | A1 |
20090157538 | Subramaniam et al. | Jun 2009 | A1 |
20090292786 | McCabe et al. | Nov 2009 | A1 |
Entry |
---|
Adobe Acrobat 7.0 Professional Signature Screenshots, Sep. 23, 2005, Adobe Systems Inc., 7.0.5. |
Number | Date | Country | |
---|---|---|---|
20090249191 A1 | Oct 2009 | US |
Number | Date | Country | |
---|---|---|---|
61072612 | Apr 2008 | US |