MOBILE TOKENIZATION HUB

• US 20140344153A1
• Filed: 05/15/2014
• Published: 11/20/2014
• Est. Priority Date: 05/15/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Prasanna Laxminarayanan
• Inventors: Raj, Thanigaivel Ashwin, Flurscheim, Christian, Subramanian, Kaushik, Laxminarayanan, Prasanna, Greene, Bradley
• Granted Patent: US 9,978,062 B2
• Time in Patent Office: Days
• US Class Current: 705/44
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes

Abstract

Embodiments of the present invention relate to systems and methods for implementing a mobile tokenization hub with a common tokenization capabilities (CTC) module that may provide tokenization for various entities in various contexts. For example, the CTC module can provide and store tokens for mobile payment transactions, transit transactions, digital wallet applications, merchant point of sale (POS) applications, personalization services, and the like.

Claims

1. A method, comprising:

receiving, by a server, a token request from a mobile device;

identifying, by the server, device information associated with the token request;

determining, by the server, a type of token corresponding to the device information;

sending, by the server, a request for the type of token;

receiving, by the server, a token having the requested type; and

returning, by the server, the token to the mobile device.

2. The method of claim 1, wherein the mobile device includes a secure element, and wherein the type of token is a static token.

3. The method of claim 2, wherein returning the requested token further comprises:

sending the token to a provisioning service, wherein the provisioning service opens a secure connection to the mobile device and writes the token to the secure element of the mobile device.

4. The method of claim 2, further comprising:

receiving a second token request from a second mobile device, wherein the second mobile device includes a non-secure element; and

differentiating the first mobile device and second mobile device, such that a first token generated for the first mobile device is different than a second token generated for the second mobile device.

5. The method of claim 4, wherein the second token generated for the second mobile device is a dynamic token.

6. The method of claim 5, further comprising:

persisting the device information in a credential database in a payment processing network, wherein the device information is captured by a payment application executing on the mobile device and wherein the device information is included with the request to activate the pre-provisioned token.

7. The method of claim 1, wherein the token request is a request to activate a pre-provisioned token stored on a secure element of the mobile device.

8. A system comprising:

a mobile tokenization hub server computer comprising a processor and a non-transitory computer readable storage medium including instructions stored thereon which, when executed by the processor cause the processor to implement a method of;

receiving a token request from a mobile device;

identifying device information associated with the token request;

determining a type of token corresponding to the device information;

sending a request for the type of token to a CTC module configured to communicate with the mobile tokenization hub server computer;

receiving a token having the requested type from the CTC module; and

returning the token to the mobile device.

9. The system of claim 8, wherein the mobile device includes a secure element, and wherein the type of token is a static token.

10. The system of claim 9, wherein returning the requested token further comprises:

sending the token to a provisioning service, wherein the provisioning service opens a secure connection to the mobile device and writes the token to the secure element of the mobile device.

11. The system of claim 9, wherein the non-transitory computer readable storage medium further include instructions which, when executed by the processor, cause the processor to:

receive a second token request from a second mobile device, wherein the second mobile device includes a non-secure element; and

differentiate the first mobile device and second mobile device, such that a first token generated for the first mobile device is different than a second token generated for the second mobile device.

12. The system of claim 11, wherein the second token generated for the second mobile device is a dynamic token.

13. The method of claim 12, further comprising:

persisting the device information in a credential database in a payment processing network, wherein the device information is captured by a payment application executing on the mobile device and wherein the device information is included with the request to activate the pre-provisioned token.

14. The system of claim 8, wherein the token request is a request to activate a pre-provisioned token stored on a secure element of the mobile device.

15. A method comprising:

receiving a request for dynamic identification information associated with a token from a registered system;

transmitting the token to a common tokenization capability module that includes a de-tokenization module that converts the token into an account identifier;

receiving the account identifier from the de-tokenization service;

transmitting the account identifier to a payment processing network to generate the dynamic identification information;

receiving the dynamic identification information from the payment processing network; and

transmitting the dynamic identification information to the registered system.

16. The method of claim 15, wherein the dynamic identification information is a dynamic card verification value.

17. The method of claim 15, wherein the account identifier is a primary account number.

18. The method of claim 15, wherein the registered system is an issuer computer or a mobile wallet provider.

19. The method of claim 18, wherein the issuer generates a second dynamic identification information and validates the token by comparing the received dynamic identification information with the second dynamic identification information.

20. The method of claim 15, further comprising:

generating a pseudo card verification value and expiration date for the token.