Multiple tokenization for authentication

1. A method comprising:

receiving at a first entity computer operated by a first entity, a first token from a consumer;

determining, by the first entity computer, a second token associated with the first token; and

sending, by the first entity computer, the second token to a server computer at a second entity, wherein the server computer determines an account identifier associated with the second token and,

wherein the method further comprises generating, by the first entity computer, an authorization request message comprising the second token; and

wherein sending the second token to the server computer at the second entity comprises

sending, by the first entity computer, the authorization request message to the server computer at the second entity, wherein the server computer receives the authorization request message, determines the account identifier by electronically searching a database for an account identifier associated with the second token, modifies the authorization request message to include the account identifier, and sends the modified authorization request message to an account issuer computer to authorize the transaction.

2. The method of claim 1 wherein the first entity is a merchant and the second entity is an acquirer.

3. The method of claim 1 wherein determining the second token associated with the first token further comprises generating the second token by altering information from the first token, wherein the second token is derived from a first entity identifier, and wherein the second entity uses the first entity identifier to determine the account identifier associated with the second token.

4. The method of claim 3 wherein altering information from the first token further comprises using a predetermined algorithm to generate the second token, and wherein the second entity uses the first entity identifier to determine the predetermined algorithm, and wherein the second entity uses the predetermined algorithm to convert the second token into a recognizable value associated with the first token, and wherein the recognizable value associated with the first token is used by the server computer to electronically search the database for the account identifier.

5. The method of claim 1 wherein determining the second token associated with the first token further comprises electronically searching a second token database for the second token associated with the first token, wherein the second token is derived from a first entity identifier, and wherein the second entity uses a predetermined algorithm to determine the account identifier associated with the second token.

6. The method of claim 1 wherein the second token is in a format of a payment card number, wherein the format of the payment card number comprises a payment processing network indicator and a check sum digit.

7. The method of claim 1 wherein the database is a first database and wherein determining the second token associated with the first token further comprises electronically searching a second database to determine the second token associated with the first token, wherein the second token was generated during consumer registration, and wherein the second token is not generated by altering data in the first token.

8. The method of claim 7 wherein the first token includes information that is less sensitive than information of the second token.

9. The method of claim 1 wherein the server computer is in a payment processing network.

10. The method of claim 9 wherein the payment processing network is configured to process credit and debit card transactions.

11. The method of claim 10 further comprising:

receiving an authorization response message from the account issuer computer.

12. The method of claim 1 wherein the first entity computer includes a POS terminal.

13. The method of claim 12 wherein the first token is an e-mail address.

14. An apparatus comprising:

a processor and a non-transitory computer-readable storage medium coupled to the processor, the computer-readable storage medium comprising code executable by the processor for implementing a method comprising:

receiving a first token from a consumer;

determining a second token associated with the first token; and

sending the second token to a server computer at a second entity, wherein the server computer determines an account identifier associated with the second token,

wherein the method further comprises generating an authorization request message comprising the second token, and wherein sending the second token to the server computer at the second entity further comprises

sending the authorization request message to the server computer at the second entity, wherein the server computer receives the authorization request message, determines the account identifier by electronically searching a database for an account identifier associated with the second token, modifies the authorization request message to include the account identifier, and sends the modified authorization request message to an account issuer computer to authorize the transaction.

15. The method of claim 14 wherein determining the second token associated with the first token further comprises generating the second token by altering information from the first token, wherein the second token is derived from a first entity identifier, and wherein the second entity uses the first entity identifier to determine the account identifier associated with the second token.

16. The method of claim 14 wherein the database is a first database and wherein determining the second token associated with the first token further comprises electronically searching a second database to determine the second token associated with the first token, wherein the second token was generated during consumer registration, and wherein the second token is not generated by altering data in the first token.

17. The apparatus of claim 14 wherein the first token includes information that is less sensitive than information of the second token.

18. A method comprising:

receiving a second token at a second entity server computer operated by a second entity from a first entity computer operated by a first entity, wherein the second token is associated with a first token that is received by the first entity computer from a consumer;

determining, by the second entity server computer, an account identifier associated with the second token; and

processing, by the second entity server computer, a transaction using the account identifier,

wherein receiving the second token further comprises receiving an authorization request message comprising the second token and wherein processing the transaction using the account identifier further comprises modifying, by the second entity server computer, the authorization request message to include the account identifier and sending the modified authorization request message to an account issuer computer to authorize the transaction.

19. The method of claim 18 wherein the first entity is a merchant and the second entity is an acquirer.

20. The method of claim 18 wherein determining the account identifier associated with the second token further comprises:

determining a first entity identifier from the second token; and

using the first entity identifier to determine the account identifier associated with the second token.

21. The method of claim 20 wherein using the first entity identifier to determine the account identifier associated with the second token further comprises:

using the first entity identifier to electronically search for a corresponding predetermined algorithm;

using the predetermined algorithm to convert the second token into a recognizable value associated with the first token, and

searching a consumer account database for the account identifier associated with the recognizable value associated with the first token.

22. The method of claim 18 wherein the second token is in a format of a payment card number, wherein the format of the payment card number comprises a payment processing network indicator and a check sum digit.

23. The method of claim 18 wherein the first token includes information that is less sensitive than information of the second token.

24. An apparatus comprising:

a processor and a non-transitory computer-readable storage medium coupled to the processor, the computer-readable storage medium comprising code executable by the processor for implementing a method comprising:

receiving a second token from a first entity computer operated by a first entity, wherein the second token is associated with a first token that is received by the first entity computer from a consumer;

determining an account identifier associated with the second token; and

processing a transaction using the account identifier,

wherein receiving the second token further comprises receiving an authorization request message comprising the second token and wherein processing the transaction using the account identifier further comprises modifying the authorization request message to include the account identifier and sending the modified authorization request message to an account issuer computer to authorize the transaction.

25. The apparatus of claim 24 wherein the method further comprises:

determining a first entity identifier from the second token; and

using the first entity identifier to determine the account identifier associated with the second token, wherein using the first entity identifier to determine the account identifier associated with the second token further comprises:

using the first entity identifier to electronically search for a corresponding predetermined algorithm;

using the predetermined algorithm to convert the second token into a recognizable value associated with the first token, and

searching a consumer account database for the account identifier associated with the recognizable value associated with the first token.

26. The apparatus of claim 24 wherein the first token includes information that is less sensitive than information of the second token.