# US 12,192,190 B2 · Universal access to document transaction platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,192,190 B2
- Document ID: US12192190B2
- Status: Granted
- Kind: B2
- Application number: 17/575,347
- Filed: 2022-01-13
- Published: 2022-05-05
- Granted: 2025-01-07
- Earliest claimed: 2016-06-03
- Assignees: DocuSign, Inc.
- Applicants: DocuSign, Inc.
- Inventors: David Steeves; Gregory J. Alger; Joshua D. Wise; Jayson C. McCleery; Peleg Atar; Ezer Farhi; Ryan J. Cox
- Web page: https://patentgrep.com/patent/US12192190B2

## CPC

- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/645: {using a third party}
- G06Q 20/367: {involving electronic purses or money safes}
- H04L 9/006: {involving public key infrastructure [PKI] trust models (network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 9/3242: {involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC}
- H04L 9/3247: {involving digital signatures}
- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- H04L 63/10: {for controlling access to devices or network resources}
- G06F 21/31: User authentication
- G06F 21/33: using certificates
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06Q 20/3674: {involving authentication}
- G06Q 50/26: Government or public services (business processes related to the transportation industry G06Q50/40)
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A system and method are described in which a document transaction management platform coordinates performance of trust actions across a plurality of trust service providers. For example, a method can include operations executing on a connector module in communication with a digital transaction management platform and a trust service provider, such as the following. Receiving, from the digital transaction management platform, a transaction request including a token and a requested trust action. Accessing user information for a recipient involved in the requested trust action using the token. Obtaining, from the digital transaction management platform, transaction data associated with the requested trust action. Coordinating, with the trust service provider, performance of the trust action on at least a portion of the transaction data. Transmitting, to the digital transaction management platform, a proof received from the trust service provider confirming performance of the trust action.

## Claims

### Claim 1

A method comprising:
receiving, by a client device, from a server, a request including a requested trust action to be performed with respect to an electronic document, wherein the requested trust action comprises obtaining electronic signatures on the electronic document from a plurality of users;
transmitting, by the client device, to a trust service provider, a performance request including a token for performance of the requested trust action on the electronic document;
obtaining, by the client device, a proof confirming performance of the requested trust action, wherein the proof includes evidence to verify presentation of data representative of the electronic document to each of the plurality of users and performance of an event on the electronic document by each of the plurality of users, wherein performance of the event on the electronic document comprises one or more of electronically signing or electronically initialing the electronic document, wherein obtaining the proof comprises receiving a digitally signed version of the electronic document from the trust service provider, and wherein the performance of the requested trust action is with respect to a rasterized image of at least a portion of the digitally signed version of the electronic document;
validating, by the client device, based on one or more pre-defined signature related criteria, for each of the plurality of users, the proof to determine that the proof meets one or more minimum requirements as the evidence; and
transmitting, by the client device, the proof to the server, wherein the server and the trust service provider do not communicate directly.

### Claim 2 (depends on 1)

The method of claim 1, wherein obtaining the proof includes: receiving a cryptographically transformed digital hash that provides the evidence of a particular event or processing of the electronic document.

### Claim 3 (depends on 1)

The method of claim 1, wherein the token is a short-lived token issued by a digital transaction management platform used to identify a transaction request.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining, by the client device, a type of the requested trust action; and
selecting, by the client device, from a plurality of candidate trust service providers, the trust service provider based on the type of the requested trust action.

### Claim 5 (depends on 4)

The method of claim 4, wherein selecting the trust service provider is performed using a policy chosen based on the type of the requested trust action.

### Claim 6

A non-transitory computer-readable medium comprising memory with instructions encoded thereon, the instructions, when executed by one or more processors of a client device, cause the one or more processors to:
receive, from a server, a request including a requested trust action to be performed with respect to an electronic document, wherein the requested trust action comprises obtaining electronic signatures on the electronic document from a plurality of users;
transmit, to a trust service provider, a performance request including a token for performance of the requested trust action on the electronic document;
obtain a proof confirming performance of the requested trust action, wherein the proof includes evidence to verify presentation of data representative of the electronic document to each of the plurality of users and performance of an event on the electronic document by each of the plurality of users, wherein performance of the event on the electronic document comprises one or more of electronically signing or electronically initialing the electronic document, wherein to obtain the proof the instructions cause the one or more processors to receive a digitally signed version of the electronic document from the trust service provider, and wherein the performance of the requested trust action is with respect to a rasterized image of at least a portion of the digitally signed version of the electronic document;
validate, based on one or more pre-defined signature related criteria, for each of the plurality of users, the proof to determine that the proof meets one or more minimum requirements as the evidence; and
transmit the proof to the server, wherein the server and the trust service provider communicate by passing communications through the client device.

### Claim 7 (depends on 6)

The non-transitory computer-readable medium of claim 6, wherein to obtain the proof the instructions cause the one or more processors to receive a cryptographically transformed digital hash that provides the evidence of a particular event or processing of the electronic document.

### Claim 8 (depends on 6)

The non-transitory computer-readable medium of claim 6, wherein the token is a short-lived token issued by a digital transaction management platform used to identify a transaction request.

### Claim 9 (depends on 6)

The non-transitory computer-readable medium of claim 6, the instructions further comprising instructions to:
determine a type of the requested trust action; and
select, from a plurality of candidate trust service providers, the trust service provider based on the type of the requested trust action.

### Claim 10 (depends on 9)

The non-transitory computer-readable medium of claim 9, wherein selecting the trust service provider is performed using a policy chosen based on the type of the requested trust action.

### Claim 11

A system comprising:
memory with instructions encoded thereon; and
one or more processors that, when executing the instructions, are caused to:
receive, by a client device, from a server, a request including a requested trust action to be performed with respect to an electronic document, wherein the requested trust action comprises obtaining electronic signatures on the electronic document from a plurality of users;
transmit, by the client device, to a trust service provider, a performance request including a token for performance of the requested trust action on the electronic document;
obtain, by the client device, a proof confirming performance of the requested trust action, wherein the proof includes evidence to verify presentation of data representative of the electronic document to each of the plurality of users and performance of an event on the electronic document by each of the plurality of users, wherein performance of the event on the electronic document comprises one or more of electronically signing or electronically initialing the electronic document, wherein to obtain the proof the one or more processors are caused to receive a digitally signed version of the electronic document from the trust service provider, and wherein the performance of the requested trust action is with respect to a rasterized image of at least a portion of the digitally signed version of the electronic document;
validate, by the client device, based on one or more pre-defined signature related criteria, for each of the plurality of users, the proof to determine that the proof meets one or more minimum requirements as the evidence; and
transmit, by the client device, the proof to the server, wherein the server and the trust service provider communicate by passing communications through the client device.

### Claim 12 (depends on 11)

The system of claim 11, wherein to obtain the proof the one or more processors are caused to receive a cryptographically transformed digital hash that provides the evidence of a particular event or processing of the electronic document.

### Claim 13 (depends on 11)

The system of claim 11, wherein the token is a short-lived token issued by a digital transaction management platform used to identify a transaction request.

### Claim 14 (depends on 11)

The system of claim 11, wherein the one or more processors, when executing the instructions, are caused to:
determine a type of the requested trust action; and
select, from a plurality of candidate trust service providers, the trust service provider based on the type of the requested trust action.