Reference token service

• US 8,489,894 B2
• Filed: 05/26/2011
• Issued: 07/16/2013
• Est. Priority Date: 05/26/2010
• Status: Active Grant

• Current Assignee: Paymetric Incorporated (Fidelity National Information Services Incorporated)
• Original Assignee: Paymetric Incorporated (Fidelity National Information Services Incorporated)
• Inventors: Comrie, Stewart, Carpenter, Eric, Epple, Gary
• Primary Examiner(s): Shiferaw, Eleni
• Assistant Examiner(s): SHOLEMAN, ABU S
• Application Number:
  US13/116,993
• Publication Number:
  US 20110307714A1
• Time in Patent Office: 782 Days
• Field of Search: 713/189, 713/193, 713/152, 713/172, 713/183, 705/908
• US Class Current: 713/189
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself

Abstract

A reference token service (RTS) is disclosed. Generally, the RTS receives sensitive data items from trusted source applications associated with particular merchants. Upon receipt of a particular sensitive data item from a particular merchant, the RTS identifies one or more reference token pools corresponding to the merchant. Each reference token pool includes a plurality of reference tokens comprising formats and data structures corresponding to sensitive data items and compatible with the merchant. The RTS receives a crypto token associated with the sensitive data item which may not conform to the merchant'"'"'s formatting or data requirements. The RTS associates the crypto token with a reference token corresponding to the merchant, which is provided to the merchant for sharing and retrieval of the sensitive data item amongst the merchant'"'"'s various applications.

Claims

1. A method for utilizing reference tokens to enable sharing of sensitive data amongst a plurality of applications associated with one or more merchants, comprising the steps of:

receiving a particular item of sensitive data at a reference token service, wherein the particular item of sensitive data is of a particular data type comprising a particular format, and wherein the particular item of sensitive data is received from a trusted source application associated with a particular merchant;

identifying at the reference token service one or more reference token pools corresponding to the particular merchant, wherein each reference token pool includes a plurality of reference tokens each having a specific format corresponding to a respective sensitive data type utilized by the particular merchant;

identifying at the reference token service a particular reference token pool from the identified one or more reference token pools based on the particular format of the received particular item of sensitive data;

transmitting the particular item of sensitive data from the reference token service to a crypto system for tokenization;

receiving a crypto token corresponding to the particular item of sensitive data at the reference token service from the crypto system;

associating the crypto token received from the crypto system with a particular reference token selected from the particular reference token pool; and

transmitting the particular reference token to the trusted source application,

whereby the trusted source application is able to share the particular reference token with other trusted source applications associated with the particular merchant.

2. The method of claim 1, wherein the particular merchant specifies to the reference token service one or more sensitive data types and one or more data formats utilized by the particular merchant.

3. The method of claim 1, wherein the one or more reference token pools are stored in a database associated with the reference token service.

4. The method of claim 1, wherein the plurality of reference tokens are preexisting.

5. The method of claim 1, wherein the particular reference token is generated on-the-fly after the crypto token is received from the crypto system.

6. The method of claim 1, wherein the crypto-token is merchant agnostic.

7. The method of claim 1, further comprising the step of modifying the particular reference token to include one or more predetermined attributes.

8. The method of claim 7, wherein the one or more predetermined attributes are selected from the group comprising:

a portion of the in the particular reference token, a predetermined identifier in the particular reference token, a routing number in the particular reference token.

9. The method of claim 1, further comprising the step of transmitting a masked value to the trusted source application along with the particular reference token.

10. The method of claim 9, wherein the masked value comprises one or more characters from the particular item of sensitive data and one or more masking characters.

11. The method of claim 1, further comprising the step of prior to transmitting the particular item of sensitive data to the crypto system for tokenization, verifying that the trusted source application is a known application associated with a trusted merchant.

12. The method of claim 7, wherein the one or more predetermined attributes are pre-stored in a database at the reference token service.

13. The method of claim 7, wherein the one or more predetermined attributes comprise specific token formatting or data requirements associated with the user.

14. The method of claim 13, wherein the specific token formatting or data requirements are dictated by the user.