Method and system for managing loyalty program information on a phone

• US 7,861,919 B2
• Filed: 09/17/2009
• Issued: 01/04/2011
• Est. Priority Date: 09/13/2002
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Gordon, James G., Black, Marc, Salters, Michael, Spaeth, Paul, Mazour, James, Madore, Kim, Shimko, Bryan, Jones, Douglas
• Primary Examiner(s): Labaze; Edwyn
• Application Number:
  US12/561,678
• Publication Number:
  US 20100006639A1
• Time in Patent Office: 474 Days
• Field of Search: 235/375, 235/382, 235485-487, 707/8, 707/104, 707/200, 707/1, 705/204, 705/202
• 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 token acceptance device, such as a personal computer (PC), connected to the remote server, a token, such as a phone, that can be read by the PC, and a token image server. Using application logic and rules, the remote server is able to read the token image on the token and determine if the image on the phone needs to be updated. The remote server forwards a backup token image to the PC which, in turn, writes the backup token image including transaction information to the phone. Once the backup token image is written onto the phone, 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 in the form of a phone comprising loyalty program information, to a token acceptance device, wherein the token acceptance device thereafter communicates with a remote host;

receiving at least a portion of a backup token image comprising loyalty program information at the portable token if the remote host determines that the portable token is to be updated; and

updating the portable token with the at least a portion of a backup token image.

2. The method of claim 1 further comprising mutually authenticating the portable token with the 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 1 wherein the at least a portion of a backup token image comprises an entire backup token image.

6. The method of claim 1 wherein the token acceptance device is in the form of a point of sale device.

7. The method of claim 1 wherein the portable token is provided to the token acceptance device in order to conduct a loyalty program activity.

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 1 wherein the token acceptance device is in the form of a second phone.

10. The method of claim 1 wherein the portable token is in the form of a newly issued portable token.

11. A method comprising:

determining, with a remote server, if a portable token in the form of a phone comprising loyalty information requires updating; and

sending at least a portion of a backup token image comprising loyalty information for the portable token to a token acceptance device, wherein the token acceptance device updates the portable token with the at least a portion of a backup token image.

12. The method of claim 11 further comprising mutually authenticating the portable token and the remote server.

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

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

15. The method of claim 11 wherein the determining step is performed while a loyalty program activity is being conducted.

16. A server configured to:

determine if a portable token in the form of a phone comprising loyalty information requires updating; and

send at least a portion of a backup token image comprising loyalty information for the portable token to a token acceptance device, wherein the token acceptance device updates the portable token with the at least a portion of a backup token image.

17. The server of claim 16 wherein the server is further configured to mutually authenticate the portable token and the server.

18. The server of claim 17 wherein the server comprises an open program engine.

19. The server of claim 16 wherein the at least a portion of a backup token image comprises an entire backup token image.

20. The server of claim 16 wherein the server is configured to determine if the portable token requires updating while a loyalty program activity is being conducted.