NETWORK TOKEN SYSTEM

• US 20150127547A1
• Filed: 10/14/2014
• Published: 05/07/2015
• Est. Priority Date: 10/11/2013
• Status: Active Grant

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated), Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Powell, Glenn Leon, Sheets, John F., Rutherford, Bruce, Williamson, Gregory, Anderson, James
• Granted Patent: US 10,891,610 B2
• Time in Patent Office: Days
• US Class Current: 705/67
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing

Abstract

Embodiments of the invention are directed to methods, apparatuses, computer readable media and systems for providing, along with a token, a token assurance level and data used to generate the token assurance level. At the time a token is issued, one or more Identification and Verification (ID&V) methods may be performed to ensure that the token is replacing a PAN that was legitimately used by a token requestor. A token assurance level may be assigned to a given token in light of the type of ID&V that is performed and the entity performing the ID&V. Different ID&Vs may result in different token assurance levels. An issuer may wish to know the level of assurance and the data used in generating the level of assurance associated with a token prior to authorizing a payment transaction that uses the token.

Claims

1. A method comprising:

receiving, by a computer, an authorization request message from a requestor, the authorization request message comprising a payment token representing a primary account number, the primary account number assigned by an issuer, wherein the authorization request message is for conducting a payment transaction using the primary account number;

receiving, by the computer, a token assurance level associated with the token along with data used to generate the token assurance level;

modifying, by the computer, the authorization request message to include the token assurance level and the data used to generate the token assurance level; and

transmitting, by the computer, the modified authorization request message to the issuer for approval.

2. The method of claim 1, further comprising:

prior to receiving the authorization request message;

receiving, by the computer, a token generation message for generation of the payment token to represent the primary account number, the token generation message including a requested token assurance level associated with the payment token;

generating, by the computer, the payment token and the token assurance level associated with the payment token; and

storing the payment token, the token assurance level and the primary account number associated with the payment token at a repository.

3. The method of claim 2, wherein the requested token assurance level is different from the token assurance level that is generated and stored at the repository.

4. The method of claim 1, wherein the token assurance level represents a level of trust in an association between the payment token and the primary account number represented by the payment token.

5. The method of claim 1, wherein the token assurance level is based on an identification and verification method used when the payment token is generated.

6. The method of claim 5, wherein the token assurance level is based on an entity performing the identification and verification method.

7. The method of claim 5, wherein the token assurance level is updated when additional identification and verification method is performed on the payment token.

8. The method of claim 5, wherein a first identification and verification method results in a first token assurance level and a second identification and verification method results in a second token assurance level different than the first token assurance level.

9. The method of claim 1, further comprising:

receiving, by the computer, an authorization response message from the issuer, the authorization response message generated in response to the authorization request message; and

transmitting, by the computer, the authorization response message including the token assurance level to the requestor.

10. The method of claim 1, further comprising:

interacting with a repository storing a one-to-one mapping between one or more primary account numbers and one or more payment tokens generated for the one or more primary account numbers.

11. A system comprising:

a processor; and

a non-transitory computer readable medium coupled to the processor, the computer readable medium comprising code, that when executed by the processor, causes the processor to;

receive an authorization request message from a requestor, the authorization request message comprising a payment token representing a primary account number, the primary account number assigned by an issuer, wherein the authorization request message is for conducting a payment transaction using the primary account number;

receive a token assurance level associated with the token along with data used to generate the token assurance level;

modifying the authorization request message to include the token assurance level and the data used to generate the token assurance level; and

transmit the modified authorization request message to the issuer for approval.

12. The system of claim 11, wherein the code, when executed by the processor, further causes the processor to:

prior to receiving the authorization request message;

receive a token generation message for generation of the payment token to represent the primary account number, the token generation message including a requested token assurance level associated with the payment token;

generate the payment token and the token assurance level associated with the payment token; and

store the token assurance level and the primary account number associated with the payment token at a repository.

13. The system of claim 12, wherein the requested token assurance level is different from the token assurance level that is generated and stored at the repository.

14. The system of claim 11, wherein the token assurance level represents a level of trust in an association between the payment token and the primary account number represented by the payment token.

15. The system of claim 11, wherein the token assurance level is based on one or more of an identification and verification method used when the payment token is generated and an entity performing the identification and verification method.

16. The system of claim 15, wherein the token assurance level is updated when additional identification and verification method is performed on the payment token.

17. The system of claim 15, wherein a first identification and verification method results in a first token assurance level and a second identification and verification method results in a second token assurance level different than the first token assurance level.

18. The system of claim 11, wherein the code, when executed by the processor, further causes the processor to:

receive an authorization response message from the issuer, the authorization response message generated in response to the authorization request message; and

transmit the authorization response message including the token assurance level to the requestor.

19. The system of claim 11, further comprising:

a repository storing a one-to-one mapping between one or more primary account numbers and one or more payment tokens generated for the one or more primary account numbers

wherein the code, when executed by the processor, further causes the processor to;

interact with the repository.

20. A method comprising:

generating, by a computer, a payment token and a token assurance level associated with the payment token, the payment token representing a primary account number assigned by an issuer;

sending, by the computer, the payment token to a requestor;

receiving, by the computer, an authorization request message from the requestor, the authorization request message comprising the payment token, wherein the authorization request message is for conducting a payment transaction using the primary account number;

modifying, by the computer, the authorization request message to include the token assurance level and data used to generate the token assurance level; and

transmitting, by the computer, the modified authorization request message to the issuer for approval.