Apparatus and methods for generating a unique token that can be imprinted on a document to attest to the verification of an executor's signature. The apparatus and methods may include a platform that may present a token electronically to the executor via a first electronic channel. The executor may use a registered device to capture a portion of the token, and transmit the portion from the registered device to the platform via a second channel to the platform. The platform may verify that the portion is registered to the executor. The platform may combine the portion with another portion of the token, and imprint the pair of combined portions on the document with another token.

BACKGROUND

Typical signature verification schemes control access to documents by requiring parties to log on to a signature platform based on a pre-arranged email address. Such schemes are vulnerable to “middleman attacks,” in which a malfeasant intercedes between the platform and one of the parties. The interceding malfeasant with knowledge of such an email address can capture transmissions from the platform that are intended for one of the parties, and reroute the transmission to an unintended email account. The malfeasant can then exploit information or change the document.

Therefore, it would be desirable to provide apparatus and methods for securely executing an electronic document over a geographically distributed electronic communication network.

DETAILED DESCRIPTION

Apparatus and methods for securely executing an electronic document over a geographically distributed electronic communication network are provided.

The apparatus and methods may generate a unique pattern that can be imprinted on the document. The apparatus and methods may include a platform that may present the pattern electronically to a document executor via a first electronic channel. The executor may use a registered device to capture a portion of the pattern, and transmit the portion from the registered device to the platform via a second channel to the platform. The platform may verify that the portion is registered to the executor. The platform may combine the portion with another portion of the pattern, and imprint the pair of combined portions on the document with another pattern. When a higher level of signatory authority is required, the platform may present the pattern to a “super-executor.” The super-executor may return along a different channel a different portion of the pattern. The platform may verify that the different portion is registered to the super-executor. The platform may then combine the portions of the executor and the super-executor with the over pattern, and imprint the document with the three-way combination to certify that the execution was verified as to identities of the executors and sufficient signatory power.

The term “executor” may include one who is designated to issue an instruction, an order, a request, or otherwise cause an act to be performed. The act of execution may include inscribing or applying a signature, a facsimile of a signature, or a digital element that has the effect of a signature. A “super-executor” may include an executor that has more executive or signatory authority than another executor. A “co-executor” may include one or more executors whose combined execution is required to perform an act of execution.

The platform may receive from an executor's device a special code taken from the device and then used to generate a token. The code may be tokenized by a splitter. Tokens from different registered executors may be combined into bonded tokens that may be imprinted on a document in addition to or in place of an electronic signature. The bonded token may be in the form of a watermark.

In some embodiments, each document that requires signature will have a unique pattern on it. The pattern may be generated based on pre-filled data input on the document. The receiver of the document may: a) use a registered device with camera, pointed at the pattern to receive a special one-time code; b) key that code into the screen to authenticate and apply their digital signature, d) depending on parameters such as dollar-amount limits, additional authentication steps may be applied such as a multi-pair entry sent to different executors, which may be registered to different devices.

In some embodiments, the generated code can be used to create a token on the device, and can carry authentication information such as location and time stamp which can be captured and retained with the completed documents. This token is then imprinted on the signature either as a tokenized string in place of the signature or as a watermark on in-line with the signature. Important for security and fraud prevention—because the document does not carry the image of a wet signature it cannot be copied and used elsewhere like on a fraudulent check. This process makes it more difficult for a bad guy to steal and then fake an authorized signature.

In some embodiments, the platform may split or combine codes with other parties to strengthen authorization and authentication. For example, a user could have a co-signer be part of the overall signature to confirm the executor's identity. The code could carry the requirement of two approvers, which may be specified at registration time.

The platform may include one or more of: a generator, a verifier, which may track signatures across the documents, an imprinter, which may effect the imprint as a watermark or replace a digital signature, and a combination/splitter engine, which may allow for single a imprint or multiple imprints

The platform may electronically scan a document and based on the content determine one or more of what signature is needed, who needs to sign, and with what level authority.

The apparatus and methods may provide for the application to documents of unique signatures across multiple documents.

The apparatus and methods may be used for securely executing an action, an instruction, an authorization, a delegation, an approval or any other suitable executive act without a document. For example, the act may be performed by clicking on a control element. The control element may include textual information. The control element may include graphical information. The control element may be displayed on a user device. Actuation of the control element may convey the act to a verification platform.

The methods may include deriving tokens from a pattern. The methods may include receiving a document from an originator. The methods may include transmitting to an executor via a first channel: (a) the document; and (b) a first of the tokens. The methods may include transmitting to the executor via a second channel: (a) a request for execution; and (b) a second of the tokens. The methods may include verifying a response, by the executor, to the request. The methods may include subsequently imprinting on the document a combination of the first token and an other token. The methods may include subsequently returning the document to the originator.

The pattern may include a multi-dimensional data object. The data object may embody a graphical image. The first channel may include a traverse of a TCP/IP network. The first channel may include a traverse of a cellular telephone network. The first channel may include traverse of a WIFI network.

The second channel may: (a) be is distinct from the first channel; and (b) include a traverse of a TCP/IP network. The second channel may: (a) be distinct from the first channel; and (b) include a traverse of a cellular telephone network. The second channel may: (a) be distinct from the first channel; and (b) include a traverse of a WIFI network.

The first channel may include a first user device that is registered to the executor. The second channel may include a second user device that is registered to the executor.

The other token may be the second token.

The combination may include a tokenized string.

The combination may include a watermark.

The verifying may include receiving from the executor, via the second channel, a copy of the second token. The verifying may include transmitting to the executor, via the second channel, a first electronic code. The verifying may include receiving from the executor, via the first channel, a second electronic code. The verifying may include ascertaining that first and second codes are identical. The other token may be the second token.

The verifying may include receiving from the executor, via the first channel, a copy of the second token. The verifying may include ascertaining that copy matches the second token.

The second token may be present in the first token. The verifying may include receiving from the executor, via the second channel, a gesture. The gesture may include an executor hand movement. The gesture may include an executor finger movement. The gesture may include an executor cursor movement. The gesture may include an executor stylus movement. The movement may correspond to an outline of a graphical representation of a token or a part of a token. The gesture may include an executor GUI control element selection. The gesture may include capturing an image using a camera in telecommunication with a first channel. The gesture may include capturing an image using a camera in telecommunication with a second channel. The gesture may include a tracing of an image. The image may correspond to a token. The image may be part of a larger image that corresponds to a different token.

The gesture may correspond to the second token. The gesture may be a gesture that does not correspond to any element of the first token that is not also part of the second token. The verification may include ascertaining that gesture matches the second token. The other token may be the second token.

The gesture may be a gesture that includes no fewer than 90% of the elements of the second token. The gesture may be a gesture that includes no greater than 10% of the elements of the first token that are not also part of the second token.

The gesture may be a gesture that includes no fewer than 90% of the elements of the second token. The gesture may be a gesture that includes no greater than 10% of the elements of the first token that are not also part of the second token.

The methods may include, after the verifying and before the imprinting: (a) transmitting to the executor an authorization exception requiring an authorized super-executor; (b) receiving from the executor an identifier of the super-executor; (c) transmitting to the super-executor, via a third channel: (i) the document; (ii) the first token; (iii) the second token; and (iv) a third token The third token may be present in the first token. The verifying may include: (a) receiving from the super-executor, via a fourth channel, a gesture that: (i) corresponds to the third token; and (ii) does not correspond to any element of the first token that is not also part of the third token; and (b) ascertaining that the gesture matches the third token. The other token may include the third token.

The methods may include, after the verifying and before the imprinting: (a) transmitting to the executor a co-execution exception requiring a co-executor; (b) receiving from the executor an identifier of the co-executor; (c) transmitting to the co-executor, via a third channel: (i) the document; (ii) the first token; (iii) the second token; and (iv) a third token. The third token may be present in the first token. The verifying may include: (a) receiving from the co-executor, via a fourth channel, a gesture that: (i) corresponds to the third token; and (ii) does not correspond to any element of the first token that is not also part of the third token; and (b) ascertaining that gesture matches the third token. The other token may include the second token and the third token.

An exception may be triggered, in addition to, or in place of, one of the aforementioned exceptions, if the executor, super-executor or co-executor is determined to be located in a location outside a geographic region. The location may be determined using location services provided on a registered mobile device of the executor, super-executor or co-executor. The registered device may be configured to transmit the location concurrently with, or in a data packet that that includes, a token. The exception may provide the originator with an opportunity to waive the geographic requirement. The exception may provide the originator with an opportunity to postpone execution. The exception may provide the originator with an opportunity to cancel execution.

The apparatus and methods may include systems for securely executing a document over a geographically distributed electronic communication network. The system may include a generation engine. The system may include a registration engine. The system may include a process flow engine. The system may include a verification engine. The system may include an imprint engine. The system may include a combination/splitter engine.

The generation engine may be configured to generate tokens.

The registration engine may be configured to register an executor to the tokens. The registration engine may be configured to register the executor to a signature grade.

The process flow engine may be configured to receive the document from an originator. The process flow engine may be configured to identify any executors. The process flow engine may be configured to scan the document to determine the identities of the executors. The process flow engine may provide the originator with an electronic form. The electronic form may provide fields for entry by the originator of the names of the executors. The process flow engine may be configured to retrieve from machine readable memory signature grades corresponding to the executors.

The process flow engine may cause the registration engine to register all executors to a first of the tokens. The process flow engine may cause the registration engine to register each of the executor to one of a plurality of second tokens, each executor corresponding to a different one of the second tokens. The process flow engine may cause the registration engine to register each of the executor to one of a plurality of different signature grades, each executor corresponding to one of the signature grades.

The process flow engine may pass to the verification engine control of the document. The process flow engine may pass to the verification engine control of the the first tokens. The process flow engine may pass to the verification engine control of the second tokens. The process flow engine may pass to the verification engine control of the signature grades for each executor.

The verification engine may be configured to cause the imprint engine to embed a portion of the first token in the document, the portion corresponding to the first token less any part of the first token that is also part of the second token. The verification engine may be configured to transmit the document and embedded first token, via a first channel, to a first executor. The verification engine may be configured to transmit a request for signature, via a second channel, to the first executor, the request for signature including the first token, and the first token including the second token. The verification engine may be configured to receive a gesture, via the second channel, from the first executor. The verification engine may be configured to verify that the gesture corresponds to the second token. The verification engine may be configured to cause the combine/split engine to bind the second token to the portion of the first token to form a bound token. The verification engine may be configured to cause the imprint engine to imprint the bound token on the document.

Illustrative embodiments of apparatus and methods in accordance with the principles of the invention will now be described with reference to the accompanying drawings, which forma part hereof. It is to be understood that other embodiments maybe utilized and that structural, functional and procedural modifications or omissions may be made without departing from the scope and spirit of the present invention.

FIG. 1is a block diagram that illustrates a computing device101(alternatively referred to herein as a “server or computer”) that may be used in accordance with the principles of the invention. The computer server101may have a processor103for controlling overall operation of the server and its associated components, including RAM105, ROM107, input/output (“I/O”) module109, and memory115.

I/O module109may include a microphone, keypad, touchscreen and/or stylus through which a user of device101may provide input, and may also include one or more of a speaker for providing audio output and a video display device for providing textual, audiovisual and/or graphical output. Software may be stored within memory115and/or other storage (not shown) to provide instructions to processor103for enabling server101to perform various functions. For example, memory115may store software used by server101, such as an operating system117, application programs119, and an associated database111. Alternatively, some or all of computer executable instructions of server101may be embodied in hardware or firmware (not shown).

Server101may operate in a networked environment supporting connections to one or more remote computers, such as terminals141and151. Terminals141and151may be personal computers or servers that include many or all of the elements described above relative to server101. The network connections depicted inFIG. 17include a local area network (LAN)125and a wide area network (WAN)129, but may also include other networks.

When used in a LAN networking environment, computer101is connected to LAN125through a network interface or adapter113.

When used in a WAN networking environment, server101may include a modem127or other means for establishing communications over WAN129, such as Internet131.

Additionally, application program119, which may be used by server101, may include computer executable instructions for invoking user functionality related to communication, such as email, short message service (SMS), and voice input and speech recognition applications.

Computing device101and/or terminals141or151may also be mobile terminals including various other components, such as a battery, speaker, and antennas (not shown). Terminal151and/or terminal141may be portable devices such as a laptop, tablet, smartphone or any other suitable device for receiving, storing, transmitting and/or displaying relevant information.

Any information described above in connection with database111, and any other suitable information, may be stored in memory115. One or more of applications119may include one or more algorithms that may be used to perform the functions of one or more of the registration engine, generator engine, the process flow engine, the verification engine, the imprint engine, and the combination/splitter engine and/or perform any other suitable tasks.

FIG. 2shows an illustrative apparatus200that may be configured in accordance with the principles of the invention.

Apparatus200may be a computing machine. Apparatus200may include one or more features of the apparatus that is shown inFIG. 1.

Apparatus200may include chip module202, which may include one or more integrated circuits, and which may include logic configured to perform any other suitable logical operations.

Apparatus200may include one or more of the following components: I/O circuitry204, which may include a transmitter device and a receiver device and may interface with fiber optic cable, coaxial cable, telephone lines, wireless devices, PHY layer hardware, a keypad/display control device or any other suitable encoded media or devices; peripheral devices206, which may include counter timers, real-time timers, power-on reset generators or any other suitable peripheral devices; logical processing device208, which may compute imminence, permanence, edge weights, mapping, and perform other methods described herein; and machine-readable memory210.

Machine-readable memory210may be configured to store in machine-readable data structures: tokens, patterns, codes, executor registration information, super-executor registration information, co-executor registration information and any other suitable information or data structures.

The chip may be silicon-based.

FIGS. 3-4show illustrative architectures that may include one or more of the features show in or described in connection withFIGS. 1 and 2.

FIG. 3shows illustrative architecture300for securely executing an electronic document over a geographically distributed electronic communication network. Architecture300may include enterprise core302. Architecture300may include enterprise operational unit304. Architecture300may include enterprise operational unit306. Architecture300may include enterprise execution security platform308. Architecture300may include enterprise WAN310. Registered customer C may be in communication with WAN310via internet I. Architecture300may include access to cellular communication network311.

Enterprise core302may include server312for exchanging execution related information. Execution related services may be provided by one or more applications served by application servers314. Servers314may exchange applications and data with machine readable memory in data stores316. Data stores316may be backed up by backup system318.

Enterprise operational unit304may provide retail or business-to-business services to registered customer C. Unit304may include one or more originator workstations318. Workstations318may be provided to document originators. An originator may create a document using an application served by application server322. Server322may exchange document information with data stores324. HTML server326may provide the originator with the document and suitable forms and data for completing the document. Elements in operational unit304may be interconnected through LAN326.

Enterprise operational unit306may provide support to operational unit304. Unit306may include one or more executor workstations328. Workstations328may be provided to document executors. An executor may receive a document and associated verification or authorization information using an application served by application server330. Server330may exchange document information with data stores332. HTML server334may provide the originator with the document and suitable forms and data for executing the document. Elements in operational unit306may be interconnected through LAN336.

Operational unit306may include registered device338. Device338may be in wireless communication with cellular network311. Cellular network311may be in wireless connection with platform308.

Platform308may include registration engine340. Platform308may include generation engine342. Platform308may include verification engine344. Platform308may include imprint engine346. Platform308may include combination/splitter engine348. Platform308may include supplemental channels I/O transceiver350. Transceiver350may provide second, third, fourth and nth channels for the transmission of token information in parallel with a first channel.

The originators and executors may be distributed geographically. Both originators and executors may be present at one or more of the operational units, such as304and306.

FIG. 4shows illustrative architecture400for securely executing an electronic document over a geographically distributed electronic communication network. Architecture400may include execution security services core402. Architecture400may include enterprise execution security services platform408. Architecture400may include execution security services WAN410. Registered subscribers S may be in communication with WAN410via internet I. Architecture400may include access to cellular communication network411.

Execution security services core402may include server412for exchanging execution related information. Execution related services may be provided by one or more applications served by application servers414. Servers414may exchange applications and data with machine readable memory in data stores416. Data stores416may be backed up by backup system418.

Execution security services core402may provide document execution security services to registered subscribers S. Registered subscribers S may include document originators. Registered subscribers S may include one or more originator workstations (not shown). Registered subscribers S may include one or more executor workstations (not shown). An originator may upload a document for security services to core402. Core402may provide to the originator document forms and other suitable forms for completing the execution of the document.

Registered subscribers S may include document executors. Registered subscribers S may include one or more executor workstations (not shown). Registered subscribers S may include one or more executor workstations (not shown). An executor may receive a document for execution from core402. Core402may provide to the executor the document, one or more tokens, and other information for completing the execution of the document.

The originators and executors may be distributed geographically. Both originators and executors may be present at one or more subscribers S.

Each executors of subscribers S may have a registered device (not shown). The device may be in wireless communication with cellular network411. Cellular network411may be in wireless connection with platform408.

Platform408may include registration engine440. Platform408may include generation engine442. Platform408may include verification engine444. Platform408may include imprint engine446. Platform408may include combination/splitter engine448. Platform408may include supplemental channels I/O transceiver450. Transceiver450may provide second, third, fourth and nth channels for the transmission of token information in parallel with a first channel.

Apparatus may omit features shown and/or described in connection with illustrative apparatus. Embodiments may include features that are neither shown nor described in connection with the illustrative apparatus. Features of illustrative apparatus may be combined. For example, an illustrative embodiment may include features shown in connection with another illustrative embodiment.

For the sake of illustration, the steps of the illustrated processes will be described as being performed by a “system.” The “system” may include one or more of the features of the apparatus that are shown inFIGS. 1-4and/or any other suitable device or approach. The “system” may include one or more means for performing one or more of the steps described herein.

The steps of methods may be performed in an order other than the order shown and/or described herein. Embodiments may omit steps shown and/or described in connection with illustrative methods. Embodiments may include steps that are neither shown nor described in connection with illustrative methods.

FIG. 5shows illustrative sequence500of communications, which embodies methods in accordance with the principles of the invention. The communications may include communications between execution platform502and executor device504, on channel “1”. The communications may include communications between execution platform502and executor device506, on channel “2”.

In communication506, platform502may transmit to executor device504a document containing token1. In communication508, platform502may transmit to executor device506a request for signature. In communication510, executor device506may transmit to platform502token2. In communication512, platform502may transmit to executor device506a code. In communication514, executor device504may transmit to platform502the code. Platform502may then imprint the document. In communication516, platform502may provide verification confirmation to executor device504. Platform502may then transmit the executed document to the originator.

FIG. 6shows illustrative sequence600of communications, which embodies methods in accordance with the principles of the invention. The communications may include communications between execution platform602and executor device604, on channel “1”. The communications may include communications between execution platform602and executor device606, on channel “2”.

In communication606, platform602may transmit to executor device604a document containing token1. In communication608, platform602may transmit to executor device606a request for signature. The request may include token2. In communication614, executor device604may transmit to platform602token2. Platform602may then imprint the document. In communication616, platform602may provide verification confirmation to executor device604. Platform602may then transmit the executed document to the originator.

FIG. 7shows illustrative sequence700of communications, which embodies methods in accordance with the principles of the invention. The communications may include communications between execution platform702and executor device704, on channel “1”. The communications may include communications between execution platform702and executor device706, on channel “2”.

In communication706, platform702may transmit to executor device704a document containing token1. In communication708, platform702may transmit to executor device706a request for signature. The request may omit token1. In communication710, executor device706may transmit to platform702a token2gesture. Platform702may then imprint the document. In communication716, platform702may provide verification confirmation to executor device704. Platform702may then transmit the executed document to the originator.

FIG. 8shows illustrative sequence800of communications, which embodies methods in accordance with the principles of the invention. The communications may include communications between execution platform802and executor device804, on channel “1”. The communications may include communications between execution platform802and executor device806, on channel “2”. The communications may include communications between execution platform802and super-executor device806, on channel “3”. The communications may include communications between execution platform802and super-executor device808, on channel “4”.

In communication812, platform802may transmit to executor device804a document containing token1. In communication814, platform802may transmit to executor device806a request for signature. In communication816, executor device806may transmit to platform802token2. In communication818, platform802may transmit to executor device804an authorization exception. In communication820, executor device804may transmit to platform802a super-executor identifier. In communication822, platform802may transmit to super-executor device808the document with both token1and token2. In communication824, platform802may transmit to super-executor device810a request for signature. In communication826, super-executor device810may transmit to platform802token3. Platform802may then imprint the document. In communication828, platform802may provide verification confirmation to executor device804. Platform802may then transmit the executed document to the originator.

FIG. 9shows illustrative sequence900of communications, which embodies methods in accordance with the principles of the invention. The communications may include communications between execution platform902and executor device904, on channel “1”. The communications may include communications between execution platform902and executor device906, on channel “2”. The communications may include communications between execution platform902and super-executor device906, on channel “3”. The communications may include communications between execution platform902and super-executor device908, on channel “4”.

In communication912, platform902may transmit to executor device904a document containing token1. In communication914, platform902may transmit to executor device906a request for signature. In communication916, executor device906may transmit to platform902token2. In communication918, platform902may transmit to executor device904a prompt for a co-executor instruction. The co-executor instruction may identify a pre-selected co-executor for the document. In communication920, executor device904may transmit to platform902a co-executor instruction. In communication922, platform902may transmit to super-executor device908the document with both token1and token2. In communication924, platform902may transmit to super-executor device910a request for signature. In communication926, super-executor device910may transmit to platform902token3. Platform902may then imprint the document. In communication928, platform902may provide verification confirmation to executor device904. Platform902may then transmit the executed document to the originator.

As will be appreciated by one of skill in the art, the invention described herein may be embodied in whole or in part as a method, a data processing system, or a computer program product. Accordingly, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software, hardware and any other suitable approach or apparatus.

Thus, methods and apparatus for securely executing an electronic document over a geographically distributed electronic communication network have been provided. Persons skilled in the art will appreciate that the present invention may be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation. The present invention is limited only by the claims that follow.