IP Library Granted Patent US 12712739
Granted Patent B2
US 12712739 · App. 18/893,693 · Granted Aug 18, 2026

Systems and methods of template-based digital asset exchanges using a public key cryptography (PKC) framework

Inventors: Ashish B. Kurani (Hillsborough, CA); Michael Knorr (Fairfield, CT); Erik F. Nelson (San Francisco, CA); Matthew Mullin Shepherd (Charlotte, NC); Laura Marie Fontana (San Francisco, CA)
Assignee: Wells Fargo Bank, N.A.
H04L9/3247G06F9/541G06Q20/381H04L9/006H04L9/50H04L2209/56
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12712739
App. No.
18/893,693
Granted
Aug 18, 2026
Kind
B2
Abstract

Systems, methods, and computer-readable storage media of template-based digital asset exchanges using a public key cryptography (PKC) framework. One method includes storing a plurality of exchange templates, and receiving a signed exchange request signed by a private key of a public and private key pair associated with a digital asset. The method further includes receiving an environmental dataset, and selecting, utilizing the environmental dataset, an exchange template of the plurality of exchange templates. The method further includes populating the plurality of fields of the selected exchange template based on the environmental dataset. The method further includes providing, to a plurality of user devices, a public key, updating a provider ledger, and updating a central ledger.

Claims (59)

1 . A computer system, comprising:

one or more processors; and

memory coupled to the one or more processors and storing a database configured to store tokens, and instructions that, when executed by the one or more processors, cause a server system to:

provision a token based on a corresponding request and associated non-payment information;

provide the token to a first third-party system of a first third-party;

receive the token from the first third-party system;

receive a notification that the token has been sent to a second third-party;

receive the token from a second third-party system of the second third-party;

receive identifying information associated with the second third-party and information regarding an intended use of the non-payment information; and

determine, based on the identifying information, that the second third-party is authorized to access the non-payment information for the intended use.

2 . The computer system of claim 1 , wherein the token comprises a non-payment token.

3 . The computer system of claim 1 , wherein the non-payment information comprises personal information of an account holder.

4 . The computer system of claim 1 , wherein the server system is further configured to store the token and a preference for the token in the database.

5 . The computer system of claim 4 , the preference for the token comprising at least one rule regarding expiration of the token.

6 . The computer system of claim 1 , wherein the server system is further configured to:

receive an access request including the token, wherein the access request includes a request to allow access to the non-payment information to an intended party system but not allow access to the non-payment information to an intermediary system; and

provide the non-payment information to the intended party system in accordance with the access request.

7 . The computer system of claim 1 , wherein the server system is further configured to filter, based on an input provided by the second third-party, the non-payment information to omit at least one character from the non-payment information, wherein the token does not include the omitted at least one character.

8 . The computer system of claim 1 , wherein the server system is further configured to, in response to receiving the token from the first third-party system, determine that the first third-party is not allowed to use the token and refrain from de-tokenizing using the token as a reference through a central interface to determine the non-payment information associated with the token.

9 . The computer system of claim 1 , wherein the server system is further configured to:

group non-payment information into a plurality of groups according to intended use; and

automatically generate a plurality of group tokens, wherein each token of the plurality of group tokens is associated with one of a plurality of intended uses based on the grouped non-payment information.

10 . The computer system of claim 9 , wherein the token is one of the plurality of group tokens, and wherein the server system is further configured to:

in response to determining that an entity is allowed to use the one of the plurality of group tokens, de-tokenize using the one of the plurality of group tokens as a reference through a central interface to determine updated group non-payment information associated with the one of the plurality of group tokens; and

transmit the updated group non-payment information to the entity in accordance with a corresponding rule specifying information that may be transmitted to the entity.

11 . A method of provisioning tokens, comprising:

provisioning, by a computer system, a token based on a corresponding request and associated non-payment information;

providing, by the computer system, the token to a first remote third-party system of a first third-party;

receiving, by the computer system, the token from the first remote third-party system;

refraining, based on a determination that the first third-party is not allowed to use the token, from de-tokenizing using the token as a reference through a central interface;

receiving, by the computer system, a notification that the token has been sent to a second third-party;

receiving, by the computer system, the token from a second remote third-party system of the second third-party;

receiving, by the computer system from the second third-party, identifying information associated with the second third-party and information regarding an intended use of the non-payment information; and

determining, by the computer system based on the identifying information, that the second third-party is authorized to access the non-payment information.

12 . The method of claim 11 , wherein the token comprises a non-payment token.

13 . The method of claim 11 , wherein the non-payment information comprises personal information of an account holder, and wherein the personal information includes one or more of address information or a personal identification number.

14 . The method of claim 11 , further comprising:

receiving, by the computer system, an access request including the token, wherein the access request includes a request to allow access to the non-payment information to an intended party system but not allow access to the non-payment information to an intermediary system; and

providing, by the computer system, the non-payment information to the intended party system in accordance with the access request.

15 . The method of claim 11 , further comprising:

grouping, by the computer system, the non-payment information into a plurality of groups according to intended use; and

automatically generating, by the computer system, a plurality of group tokens, wherein each of the plurality of group tokens is associated with one of a plurality of intended uses based on the grouped non-payment information.

16 . The method of claim 11 , further comprising:

filtering, by the computer system based on an input provided by the second third-party, the non-payment information to omit at least one character from the non-payment information, wherein the token does not include the omitted at least one character.

17 . A non-transitory computer readable media having computer-executable instructions embodied therein that, when executed by a processor of a computing system, cause the computing system to perform operations comprising:

provisioning a token based on a corresponding request and associated non-payment information;

providing the token to a first remote third-party system of a first third-party;

receiving the token from the first remote third-party system;

refraining, based on a determination that the first third-party is not allowed to use the token, from de-tokenizing using the token as a reference through a central interface;

receiving a notification that the token has been sent to a second third-party;

receiving the token from a second remote third-party system of the second third-party;

receiving, from the second third-party, identifying information and information regarding an intended use of the non-payment information; and

determining, based on the identifying information associated with the second third-party and a token preference, that the second third-party is authorized to access the non-payment information.

18 . The non-transitory computer readable media of claim 17 , wherein the token comprises a non-payment token, wherein the non-payment information comprises personal information of an account holder, and wherein the personal information includes one or more of address information or a personal identification number.

19 . The non-transitory computer readable media of claim 18 , the operations further comprising:

grouping non-payment information into a plurality of groups according to intended use; and

automatically generating a plurality of group tokens, wherein each of the plurality of group tokens is associated with an intended use.

20 . The non-transitory computer readable media of claim 18 , the operations further comprising:

filtering, based on an input provided by the second third-party, the non-payment information to omit at least one character from the non-payment information.