Method and system for managing token image replacement

• US 7,591,412 B2
• Filed: 10/25/2007
• Issued: 09/22/2009
• Est. Priority Date: 09/13/2002
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Madore, Kim, Gordon, James G., Black, Marc, Salters, Michael, Spaeth, Paul, Mazour, James, Shimko, Bryan, Jones, Douglas
• Primary Examiner(s): Labaze; Edwyn
• Application Number:
  US11/923,958
• Publication Number:
  US 20080128484A1
• Time in Patent Office: 698 Days
• Field of Search: 235/375, 235/382, 235485-487, 235/380, 707/8, 707/104, 707/200, 707/1, 707/202, 707/204, 705/204, 705/202, 705/17, 705/39, 705/41
• US Class Current: 235/375
• CPC Class Codes: G06Q 20/202 Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
• CPC Class Codes: G06Q 20/204 comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/355 Personalisation of cards for use
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0226 Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: G07C 9/253 visually
• CPC Class Codes: G07F 7/082 Features insuring the integrity of the data on or in the card
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A system for managing token image replacement is provided. The system includes a remote server, a personal computer (PC) connected to the remote server, a smartcard that can be read by the PC, and a card image server. Using application logic and rules, the remote server is able to read the card image on the smartcard and determine if the card image on the smartcard needs to be updated. If an indicator on the smartcard is set to “update”, the remote server then retrieves a backup card image that corresponds to the card from the card image server. The remote server forwards the backup card image to the PC which, in turn, writes the backup card image including transaction information to the smartcard. Once the backup card image is written onto the smartcard, the indicator in the smartcard is then reset to ensure that subsequent interactions with the system would not initiate an update.

Claims

1. A method for using a portable token, the method comprising:

providing a portable token comprising loyalty program information to a token acceptance device, the token acceptance device being external to the portable token, wherein the token acceptance device thereafter reads an update indicator on the portable token, the update indicator indicating if the portable token requires updating; and

receiving at least a portion of a backup token image at the portable token if the update indicator indicates that the portable token is to be updated,

wherein the portable token is in the form of a phone.

2. The method of claim 1 further comprising mutually authenticating the portable token with a remote server.

3. The method of claim 2 wherein the remote server comprises an open program engine.

4. The method of claim 1 wherein the token acceptance device comprises a loyalty plug-in and wherein the method further comprises:

communicating with the loyalty plug-in using the portable token.

5. The method of claim 4 wherein the loyalty plug-in further communicates with a remote server.

6. The method of claim 1 wherein the at least the portion of the backup token image comprises an entire backup token image.

7. The method of claim 1 wherein the update indicator is reset after receiving at least the portion of the backup token image.

8. The method of claim 1 wherein the token acceptance device comprises a loyalty plug-in and wherein the method further comprises:

communicating with the loyalty plug-in using the portable token, wherein the loyalty plug-in detects whether an update of the portable token is needed.

9. The method of claim 8 wherein the loyalty plug-in further communicates with a remote server.

10. The method of claim 8 wherein the update indicator is reset after receiving at least the portion of the backup token image.

16. The method of claim 1 wherein the portion of a backup token image only contains loyalty transactions conducted prior to a point in time when the portable was reported stolen.

11. A phone comprising loyalty program information and an update indicator, the update indicator indicating if the phone requires updating, wherein the phone is configured to interact with a token acceptance device, the token acceptance device being external to the phone, wherein the token acceptance device thereafter reads an update indicator on the phone and wherein the phone is further configured to receive at least a portion of a backup token image if the update indicator indicates that the phone is to be updated.

12. The phone of claim 11 wherein the phone is further configured to mutually authenticate with a remote server.

13. The phone of claim 12 wherein the remote server comprises an open program engine.

14. The phone of claim 11 wherein the at least the portion of the backup token image comprises an entire backup token image.

15. The phone of claim 11 wherein the update indicator is configured to be reset after receiving at least the portion of the backup token image.

17. The phone of claim 11 wherein the portion of the backup token image is sent to the token acceptance device in an e-mail.