Mobile tokenization hub

• US 9,978,062 B2
• Filed: 05/15/2014
• Issued: 05/22/2018
• Est. Priority Date: 05/15/2013
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Raj, Thanigaivel Ashwin, Flurscheim, Christian, Subramanian, Kaushik, Greene, Bradley, Laxminarayanan, Prasanna
• Primary Examiner(s): Hewitt, II, Calvin L
• Assistant Examiner(s): Keritsis, Dennis G
• Application Number:
  US14/279,186
• Publication Number:
  US 20140344153A1
• Time in Patent Office: 1,468 Days
• Field of Search: 705 66
• 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 for providing tokens to a first mobile device and a second mobile device, wherein the first mobile device comprises a secure element and a memory and is associated with a first user, and wherein the second mobile device comprises memory and does not include a secure element, the method comprising:

receiving, by a server, a first token request from the first mobile device, wherein the token request comprises an identifier of the first mobile device;

determining, by the server, based on the identifier for the first mobile device, that the first mobile device comprises the secure element;

based on the determining that the first mobile device has the secure element, generating, by the server, a first token and mapping the first token to an account identifier of the first user;

writing, by the server, the generated first token to the secure element of the first mobile device;

receiving, by the server, a second token request from the second mobile device, wherein the second token request comprises an identifier of the second mobile device;

determining, by the server, based on the identifier of the second mobile device that the second mobile device does not comprise a secure element;

based on the determination that the second mobile device does not contain a secure element, generating by the server, a time-to-live token; and

sending, by the server, the generated time-to-live token to the second mobile device.

2. The method of claim 1, further comprising:

sending, by the server, the first token to a provisioning service.

3. The method of claim 1, further comprising:

persisting, by the server, first device information associated with the first mobile device in a credential database in a payment processing network, wherein the first device information is included with the first token request.

4. The method of claim 1, wherein the server further comprises a token rules generation module comprising rules for generating specific token types, token formats, and security and storage requirements for the tokens.

5. The method of claim 1, further comprising:

receiving, by the server, a registration request for the first mobile device.

6. The method of claim 1, wherein the first mobile device and the second mobile device are a first mobile phone and a second mobile phone, respectively.

7. The method of claim 1, wherein the server is part of a tokenization hub.

8. The method of claim 1, wherein the server comprises rules that allow the server computer to manage lifecycle management of the time to live token.

9. The method of claim 1, wherein the method further comprises:

receiving, by the server, a de-tokenization request;

providing, by the server, the de-tokenization request to a tokenization module in the server;

receiving, by the server, the account identifier from the tokenization module; and

providing, by the server, a de-tokenization response with the account identifier in response to the de-tokenization request.

10. The method of claim 1, wherein the first token request includes an alias for a primary account number.

11. The method of claim 1, wherein the first token request comprises an alias for a primary account number, device information, and a purchase amount for a transaction.