US 12,294,630 B2
System and method for token domain control
Phillip Kumnick, Phoenix, AZ (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Filed by Visa International Service Association, San Francisco, CA (US)
Filed on Aug. 10, 2021, as Appl. No. 17/398,955.
Application 17/398,955 is a continuation of application No. 15/806,947, filed on Nov. 8, 2017, granted, now 11,122,133.
Application 15/806,947 is a continuation of application No. 14/704,571, filed on May 5, 2015, granted, now 9,848,052, issued on Nov. 5, 2015.
Claims priority of provisional application 61/988,815, filed on May 5, 2014.
Prior Publication US 2021/0368012 A1, Nov. 25, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 67/53 (2022.01); G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); H04L 9/40 (2022.01); H04L 67/02 (2022.01); H04L 67/10 (2022.01)
CPC H04L 67/53 (2022.05) [G06Q 20/385 (2013.01); G06Q 20/4016 (2013.01); H04L 63/083 (2013.01); H04L 67/02 (2013.01); H04L 67/10 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
receiving, by a processor in a token service computer, a first token request including a payment account number and a first domain identifier;
identifying or generating, by the processor in the token service computer, a payment token associated with the payment account number;
generating, by the processor in the token service computer, a first token code associated with the payment token;
assigning, by the processor in the token service computer, the payment token and the first token code to the first domain identifier, such that the first token code is specific to a first token domain associated with the first domain identifier;
providing, by the processor in the token service computer, the payment token and the first token code, wherein the payment token is subsequently used in place of the payment account number for a first payment transaction, wherein the payment token is valid for the first payment transaction if the payment token is accompanied by the first token code and used within the first token domain, the payment account number is identified based on the payment token for the first payment transaction, and the first payment transaction is authorized based on the identified payment account number;
receiving, by the processor in the token service computer, a second token request including the payment account number or the payment token and further including a second domain identifier;
generating, by the processor in the token service computer, a second token code associated with the payment token, wherein the second token code is different than the first token code;
assigning, by the processor in the token service computer, the payment token and the second token code to the second domain identifier, such that the second token code is specific to a second token domain associated with the second domain identifier, wherein the first domain identifier is different than the second domain identifier, and wherein the first token domain is different than the second token domain; and
providing, by the processor in the token service computer, the second token code, wherein the payment token is subsequently used in place of the payment account number for a second payment transaction, the payment token is valid for the second payment transaction if the payment token is accompanied by the second token code and used within the second token domain, the payment account number is identified based on the payment token for the second payment transaction, and the second payment transaction is authorized based on the identified payment account number, wherein the same payment token is used for both the first payment transaction and the second payment transaction, the same payment token is associated with both the second token code and the first token code, and the same payment token is usable within both the first token domain and the second token domain.