TRACKING RF TRANSACTION ACTIVITY USING A TRANSACTION DEVICE IDENTIFIER

• US 20090008441A1
• Filed: 09/08/2008
• Published: 01/08/2009
• Est. Priority Date: 07/10/2001
• Status: Abandoned Application

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Xatra Fund MX LLC (Intellectual Ventures LLC)
• Inventors: Montgomery, Joshua, Saunders, Peter D., Peart, Lee J.
• Application Number:
  US12/206,634
• Publication Number:
  US 20090008441A1
• Time in Patent Office: Days
• US Class Current: 235/379
• CPC Class Codes: G06Q 20/346 Cards serving only as information carrier of service
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• 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: G07G 1/009 the reader being an RFID reader

Abstract

In accordance with one exemplary embodiment of the invention, a radio frequency identification (RFID) transaction device is used to complete a transaction. The RFID transaction device may communicate a tertiary number and/or a URL instead of sensitive transaction device information. The tertiary number and/or URL may point the RFID transaction device to a third-party authorizing agent. The third party may verify that the URL and/or a tertiary number corresponds to a valid transaction account on the account provider system. The third party may use the URL and/or the tertiary number to locate the appropriate verifying (e.g., “validating”) information for confirming the transaction account validity. Once the third party verifies the validity of the transaction account using the URL and/or the tertiary number, the third party (e.g., account issuer or acquirer) may provide authorization to the merchant that a transaction may be completed.

Claims

1. A method for facilitating a Radio Frequency (RF) payment transaction at a transaction processing entity, comprising:

correlating a transaction device identifier to a payment account code;

providing the transaction device identifier to an RF payment device using an internet connection;

receiving, from a merchant system, a transaction request comprising the transaction device identifier, a transaction value, and a merchant system authentication tag;

authenticating the merchant system tag;

associating the transaction device identifier with the payment account code; and

providing authorization for the RF payment transaction to the merchant system when the merchant system authentication tag is authenticated.

2. The method of claim 1, wherein the merchant system is not provided the payment account code during the RF payment transaction.

3. The method of claim 1, wherein the transaction device identifier is provided in Track 1/Track 2 format.

4. The method of claim 1, wherein the transaction device identifier is provided in a data record of variable format.

5. The method of claim 1, further comprising:

updating the payment account code; and

associating the updated payment account code with the transaction device identifier without modifying the transaction device identifier.

6. The method of claim 1, further comprising:

storing at least one of a plurality of loyalty account numbers and a plurality of rewards account numbers associated with the transaction device identifier;

selecting a loyalty account number from a plurality of loyalty account numbers, the loyalty account number corresponding to the merchant system and the transaction device identifier; and

transmitting the loyalty account number to the merchant system.

7. The method of claim 1, further comprising providing a URL to the RF payment device wherein the URL is unique to at least one of the RF payment device, the payment account code, and the transaction processing entity.

8. The method of claim 7, further comprising:

receiving, from the merchant system, the URL associated with the RF payment device;

associating the URL with at least one of the transaction device identifier and the payment account code; and

facilitating the RF payment transaction using at least one of the correlative transaction device identifier and the correlative payment account code.

9. The method of claim 7, wherein the URL is the transaction device identifier.

10. A method for tracking Radio Frequency (RF) transaction device activity using an RF Identification (RFID) reader, comprising:

receiving a transaction device identifier from an RF transaction device;

mapping the transaction device identifier;

configuring an incentive offer based on at least one factor associated with the transaction device identifier; and

transmitting the incentive offer to the RF transaction device.

11. The method of claim 10, wherein the at least one factor associated with the transaction device identifier includes:

the duration the RFID reader has received the transaction device identifier, the location of the RF transaction device, a path traversed by the RF transaction device, a purchasing history associated with the RF transaction device, a user'"'"'s gender associated with the RF transaction device, a user'"'"'s age associated with the RF transaction device, and general economic information of a consumer group.

12. The method of claim 10, wherein the incentive offer is associated with at least one of a loyalty account number and a rewards point account.

13. The method of claim 10, further comprising analyzing the at least one factor to improve the effectiveness of a merchandizing process.

14. A Radio Frequency (RF) payment device comprising:

a first RF transponder to receive a device authentication code from an RF Identification (RFID) reader;

a protocol/sequence controller to communicate with the first RF transponder;

a transaction device identifier associated with a corresponding account code maintained at a transaction processing entity;

a unique device identification code;

a unique device encryption key corresponding to the transaction device identifier; and

a device authentication circuit to communicate with the database and the protocol/sequence controller, wherein the device authentication circuit is configured to use the unique device encryption key to encrypt the device authentication code and is configured to use the unique device encryption key to encrypt the transaction device identifier;

wherein the first RF transponder is configured to transmit at least one of the encrypted device authentication code and the encrypted transaction device identifier to the RFID reader.

15. The RF payment device of claim 14, further comprising a second RF transponder.

16. The RF payment device of claim 15, wherein at least one of the first RF transponder and the second RF transponder is configured to transmit an RFID reader authentication code to the RFID reader, and wherein at least one of the first RF transponder and the second RF transponder is configured to receive an encrypted RFID reader authentication code from the RFID reader.

17. The RF payment device of claim 16, further comprising an RFID reader decryption key, wherein the device authentication circuit is configured to use the RFID reader decryption key to decrypt the encrypted RFID reader authentication code received from the RFID reader in order-to authenticate the RFID reader.

18. The RF payment device of claim 17, wherein the unique device identification code comprises a personalized unique device identification code, wherein the unique device encryption key comprises a personalized unique device encryption key, wherein the transaction device identifier comprises a personalized transaction device identifier, and wherein the RFID reader decryption key comprises a personalized RFID reader decryption key.

19. The RF payment device of claim 15, wherein the protocol/sequence controller is configured to be in communication with at least one of the first RF transponder and the second RF transponder via a modulator/demodulator.

20. The RF payment device of claim 15, further comprising an enable/disable switch configured to enable/disable at least one of the first RF transponder and the second RF transponder.

21. The RF payment device of claim 15, wherein the RF payment device is an RF payment fob.

22. A method for facilitating a Radio Frequency (RF) payment transaction using a transponder at an RF payment device, comprising:

receiving, from a transaction processing entity, a transaction device identifier corresponding to a payment account code;

receiving an RF interrogation signal from an RFID reader, wherein the RF interrogation signal comprises a payment device authentication code;

activating a transponder system authentication circuit in response to the RF interrogation signal;

encrypting the payment device authentication code with a unique encryption key;

providing an encrypted payment device authentication code and a unique payment device identification code to the RFID reader;

decrypting an encrypted RFID reader authentication code;

comparing the decrypted RFID reader authentication code to an RFID reader authentication code;

authenticating the RFID reader when the decrypted RFID reader authentication code matches the RFID reader authentication code; and

transmitting the transaction device identifier to the RFID reader.

23. The method of claim 22, wherein the RFID reader receives the encrypted RFID reader authentication code and the unique payment device identification code, associates a unique payment device decryption key stored in an RFID reader database with the unique payment device identification code, decrypts and compares the encrypted. RFID reader authentication code to the payment device authentication code, and authenticates the RF payment device when the decrypted payment device authentication code matches the payment device authentication code.

24. The method of claim 22, further comprising:

receiving a second RF interrogation signal from the RFID reader; and

wherein a second transponder is configured to be responsive to the second RF interrogation signal.