Back to results
US 11,122,133 B2Granted
System and method for token domain control
AssigneeVisa International Service Association
InventorPhillip Kumnick
Life of this patent
Estimating the term…
Abstract
A method for providing a token code in conjunction with a value token is disclosed. The token code serves as a shared secret for authenticating the use of the value token. Multiple token holders can possess the same value token, but each token holder may have a different token code for use with the value token.
Claims20
A method comprising:
- sending, by a processor in a token requestor computer, a first token request to a token service computer, wherein the first token request includes a payment account number and a first domain identifier,
- wherein the token service computer identifies a payment token associated with the payment account number, wherein the payment token is a substitute for the payment account number, wherein the token service computer generates a first token code associated with the payment token, wherein the token service computer assigns the payment token and the first token code to the first domain identifier, such that the first token code is specific to a first domain associated with the first domain identifier;
- receiving, by the processor in the token requestor computer, the payment token and the first token code from the token service computer;
- storing, by the processor in the token requestor computer, the payment token and the first token code;
- using, by the processor in the token requestor computer, the payment token and the first token code in place of the payment account number for a first payment transaction, wherein the payment token and the first token code are valid for the first payment transaction if they are being used within the first domain;
- sending, by the processor in the token requestor computer, a second token request to the token service computer, wherein the second token request includes a second domain identifier and the payment account number or the payment token,
- wherein the token service computer generates a second token code associated with the payment token, wherein the second token code is different than the first token code, wherein the second token code and the first token code are both associated with the same payment token, wherein the token service computer assigns the second token code to the second domain identifier, such that the second token code is specific to a second domain associated with the second domain identifier, wherein the first domain identifier is different than the second domain identifier, and the first domain is different than the second domain;
- receiving, by the processor in the token requestor computer, the second token code from the token service computer;
- storing, by the processor in the token requestor computer, the second token code;
- and
- using, by the processor in the token requestor computer, the payment token and the second token code in place of the payment account number for a second payment transaction, wherein the payment token and the second token code are valid for the second payment transaction if they are being used within the second domain.
8 more elements
A token requestor computer comprising:
- a processor;
- and
- a non-transitory computer readable medium, the non-transitory computer readable medium comprising code, that when executed by the processor, implements a method comprising:
- sending a first token request to a token service computer, wherein the first token request includes a payment account number and a first domain identifier,
- wherein the token service computer identifies a payment token associated with the payment account number, wherein the payment token is a substitute for the payment account number, wherein the token service computer generates a first token code associated with the payment token, wherein the token service computer assigns the payment token and the first token code to the first domain identifier, such that the first token code is specific to a first domain associated with the first domain identifier;
- receiving the payment token and the first token code from the token service computer;
- storing the payment token and the first token code;
- using the payment token and the first token code in place of the payment account number for a first payment transaction, wherein the payment token and the first token code are valid for the first payment transaction if they are being used within the first domain;
- sending a second token request to the token service computer, wherein the second token request includes a second domain identifier and the payment account number or the payment token,
- wherein the token service computer generates a second token code associated with the payment token, wherein the second token code is different than the first token code, wherein the second token code and the first token code are both associated with the same payment token, wherein the token service computer assigns the second token code to the second domain identifier, such that the second token code is specific to a second domain associated with the second domain identifier, wherein the first domain identifier is different than the second domain identifier, and the first domain is different than the second domain;
- receiving the second token code from the token service computer;
- storing the second token code;
- and
- using the payment token and the second token code in place of the payment account number for a second payment transaction, wherein the payment token and the second token code are valid for the second payment transaction if they are being used within the second domain.
11 more elements
Dependencies are inferred from the claim text.