Multiple tokenization for authentication

• US 10,552,828 B2
• Filed: 01/26/2016
• Issued: 02/04/2020
• Est. Priority Date: 04/11/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Hammad, Ayman
• Primary Examiner(s): Rankins, William E
• Application Number:
  US15/006,714
• Publication Number:
  US 20160140542A1
• Time in Patent Office: 1,470 Days
• Field of Search: 705 11, 705 35, 705 38
• CPC Class Codes: G06F 9/30196 using decoder, e.g. decoder per instruction set, adaptable or programmable decoders
• CPC Class Codes: G06F 9/3822 Parallel decoding, e.g. parallel decode units
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a 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/401 Transaction verification
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: H04L 9/32 including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials

Abstract

Embodiments of the present invention are directed generally to systems, methods, and apparatuses for authenticating a cardholder using multiple tokenization authentication. Embodiments of the invention are directed at a method. The method includes receiving at a first entity a first token from a consumer and determining a second token associated with the first token. Once the second token is determined, the second token is sent to a server computer at a second entity. The server computer then determines an account identifier associated with the second token and processes a transaction using the account identifier.

Claims

1. A method comprising:

receiving at a server computer, a modified first authorization request comprising an account number from a first processing computer, which determined the account number from an initial merchant token received in a first authorization request from a first merchant computer, which determined the initial merchant token from a consumer token;

transmitting, by the server computer, the modified first authorization request comprising the account number to an issuer computer, which approves or declines the modified first authorization request;

receiving, at the server computer, a modified second authorization request comprising the account number from a second processing computer, which determined the account number from a subsequent merchant token received in a second authorization request from a second merchant computer, which determined the subsequent merchant token from the consumer token; and

transmitting, by the server computer, the modified second authorization request comprising the account number to the issuer computer, which approves or declines the modified second authorization request.

2. The method of claim 1 wherein the server computer is in a payment processing network and is configured to process credit and debit cards transactions.

3. The method of claim 1 wherein the consumer token is a phone number.

4. The method of claim 1 wherein the first and second authorization requests are ISO 8583 messages.

5. The method of claim 1, wherein the first processing computer is a first acquirer computer and the second processing computer is a second acquirer computer.

6. The method of claim 1, wherein the account number comprises 16 digits.

7. The method of claim 1, wherein the account number comprises 16 digits, and wherein the initial and subsequent merchant tokens are each 16 digits long.

8. The method of claim 7, wherein the initial and subsequent merchant tokens are different numbers.

9. The method of claim 7, wherein the first processing computer is a first acquirer computer.

10. The method of claim 9, wherein the second processing computer is a second acquirer computer.

11. The method of claim 1, wherein the consumer token is less secure than the initial merchant token, which is less secure than the account number.

12. The method of claim 1, further comprising:

deriving, by the first processing computer, the account number from the initial merchant token; and

deriving, by the second processing computer, the account number from the subsequent merchant token.

13. A system comprising:

a first processing computer;

a second processing computer; and

a server computer comprising

a processor, and

a computer readable medium coupled to the processor, the computer readable medium comprising code executable by the processor for implementing a method comprising

receiving a modified first authorization request comprising an account number from the first processing computer, which determined the account number received in a first authorization request from an initial merchant token from first merchant computer, which determined the initial merchant token from a consumer token,

transmitting the modified first authorization request to an issuer computer, which approves or declines the modified first authorization request,

receiving a modified second authorization request comprising the account number from the second processing computer, which determined the account number from a subsequent merchant token received in a second authorization request from a second merchant computer, which determined the subsequent merchant token from the consumer token and

transmitting the second authorization request to the issuer computer, which approves or declines the modified second authorization request.

14. The system of claim 13, wherein the consumer token is a phone number.

15. The system of claim 13, wherein the first and second authorization requests are ISO 8583 messages.

16. The system of claim 13, further comprising:

a token association database in communication with the server computer.

17. The system of claim 13, wherein the server computer comprises data processing subsystems and networks to deliver authorization services, exception file services, and clearing and settlement services.

18. A method comprising:

deriving, by a first processing computer, an account number from an initial merchant token specifically created for a first merchant;

receiving at a server computer, a first authorization request comprising the account number from the first processing computer;

forwarding, by the server computer, the first authorization request to an issuer;

deriving the account number, by a second processing computer, from a subsequent merchant token specifically created for a second merchant

receiving, at the server computer, a second authorization request comprising the account number from the second processing computer; and

forwarding, by the server computer, the second authorization request to the issuer;

wherein the initial merchant token and the subsequent merchant token were previously derived from a same consumer token.