US 12,073,409 B2
Token management system
Azita Asefi, Vacaville, CA (US); Jorge Michirefe, Phoenix, AZ (US); Al Hecht, Chanhassen, MN (US); Steve Puffer, Champlin, MN (US); and Peter Ho, Walnut Creek, CA (US)
Assigned to Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed by Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed on May 15, 2023, as Appl. No. 18/197,276.
Application 18/197,276 is a continuation of application No. 15/353,586, filed on Nov. 16, 2016, granted, now 11,651,379.
Application 15/353,586 is a continuation of application No. 15/081,536, filed on Mar. 25, 2016, granted, now 11,429,975.
Claims priority of provisional application 62/139,525, filed on Mar. 27, 2015.
Prior Publication US 2023/0281633 A1, Sep. 7, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 30/02 (2023.01); G06F 21/62 (2013.01); G06Q 20/34 (2012.01); G06Q 20/36 (2012.01); G06Q 20/40 (2012.01)
CPC G06Q 20/405 (2013.01) [G06F 21/62 (2013.01); G06Q 20/34 (2013.01); G06Q 20/367 (2013.01); G06Q 20/3672 (2013.01); G06Q 20/401 (2013.01); G06Q 30/02 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer system, comprising:
a token database configured to store non-payment tokens; and
a server system comprising a processor and instructions stored in non-transitory machine readable media, the instructions configured to cause the server system to:
receive a request to provision a non-payment token based on non-payment information;
provision the non-payment token based on the request;
store the non-payment token and at least one preference for the non-payment token in the token database;
provide the non-payment token to a first remote third-party system of a first third-party, wherein the first third-party is an intermediary;
receive the non-payment token from the first remote third-party system of the first third-party;
in response to receiving the non-payment token from the first remote third-party system, determine that the first third-party is not allowed to use the non-payment token and refrain from de-tokenizing the non-payment token to determine the non-payment information associated with the non-payment token;
receive a notification that the non-payment token has been sent by the first third-party to a second third-party;
receive the non-payment token from a second remote third-party system of the second third-party;
receive, from the second third-party, identifying information associated with the second third-party and information regarding an intended use of the non-payment information;
determine, based on the identifying information associated with the second third-party and at least one token preference, that the second third-party is an intended party and is authorized to access the non-payment information for the intended use.