System and method for selecting load options for use in radio frequency identification in contact and contactless transactions

• US 20040010449A1
• Filed: 12/13/2002
• Published: 01/15/2004
• Est. Priority Date: 07/10/2001
• Status: Active Grant

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Chartoleaux KG LLC (Intellectual Ventures LLC)
• Inventors: Isenberg, Susan E., Mayers, Alexandra, Berardi, Michael J., Williamson, John R., Scheding, Kathryn D., Elwood, Jennifer Anne, Bliman, Michal, VonWald, Kristin L., Saunders, Peter D., Perry, Trevor J., Hood, Matthew C., Shah, Sejal Ajit, Bonalle, David
• Granted Patent: US 9,454,752 B2
• Time in Patent Office: Days
• US Class Current: 705/16
• CPC Class Codes: G06Q 20/00 Payment architectures, schemes or protocols apparatus for performing or posting payment transactions G07F7/08, G07F19/00; electronic cash registers G07G1/12
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/40145 Biometric identity checks
• CPC Class Codes: G07C 9/257 electronically G07C9/26 takes precedence
• CPC Class Codes: G07C 9/26 using a biometric sensor integrated in the pass
• CPC Class Codes: G07C 9/28 the pass enabling tracking or indicating presence
• CPC Class Codes: G07C 9/29 the pass containing active electronic elements, e.g. smartcards

Abstract

A transponder-reader payment system includes a fob including a transponder, and a RFID reader for interrogating the transponder. In exemplary operation, the fob identifying information may be presented to the RFID reader for completion of a transaction request. The transaction request may be provided to a fob issuer system which retrieves a value for satisfying the transaction request from a fob associated transaction data file. The issuer system may deplete the transaction data file in accordance with the transaction request and replenish the data file in accordance with fob user or fob issuer defined reload protocol.

Claims

1. A transponder-reader payment system comprising:

a. a transponder system responsive to a Radio Frequency (RF) interrogation signal, said transponder system including a universal serial connector and BUS (USB) connector and a transponder database, said transponder database storing at least a transponder system identifier;

b. a Radio Frequency Identification (RFID) reader in RF communication with said transponder system, said RFID reader providing said interrogation signal transponder system and receiving said transponder identifier.

c. a merchant system including merchant identification and a merchant point of interaction device, said merchant point of interaction device in communication with said RFID reader, wherein said RFID reader provides said transponder system identifier to said merchant point of interaction device, said merchant point of interaction device associating said transponder system identifier to a user transaction request and said merchant identifier forming a merchant transaction request, said merchant point of interaction device providing said merchant transaction request to an issuer system;

d. an issuer system for receiving said merchant transaction request comprising

i an issuer system server, said issuer system server in communication with said merchant point of interaction device and a user interface, and

ii an issuer system database including a preloaded value data file and a reload protocol data file, said preloaded value data file and said reload protocol data file associated with said transponder system identifier, said preload value data file storing a predetermined value for use in satisfying a user transaction request;

e. a first funding source associated with said transponder system identifier and said preloaded value data file, said funding source in communication with said issuer system, said funding source containing a funding source value, and

f. a user interface in communications with said issuer system for use in updating at least one of said preloaded value data files and said reload protocol data file.

2. A transponder-reader payment system according to claim 1 wherein said predetermined value is preloaded into said preloaded value data file prior to transponder system usage, said predetermined value greater than zero.

3. A transponder-reader payment system according to claim 2 wherein said issuer system compares said user transaction value to said predetermined value.

4. A transponder-reader payment system according to claim 3 wherein said user system server retrieving at least a portion of said user transaction value from said preloaded value data file and providing a transaction approved transmission and said portion of said user transaction value to said merchant system.

5. A transponder-reader payment system according to claim 4 wherein said issuer system server deducts at lest a portion of said user transaction value from said preloaded value data file forming a deplete value data to be of a depleted value, said depleted value less than said preloaded value.

6. A transponder-reader payment system according to claim 5 wherein said issuer system server retrieves said portion of said funding source value and increments said preloaded value data file said portion of said funding source value.

7. A transponder-reader payment system according to claim 6 wherein said issuer system server retrieves said portion of said funding source value in accordance with said reload protocol data file, said reload protocol data file including at least one reload indicia.

8. A transponder-reader payment system according to claim 7, wherein said transponder system identifies and at least one update reload indicia is provided to said user interface said user interface further providing said transponder system identifier and said at least one update reload indicia.

9. A transponder-reader payment system according to claim 8, wherein issuer system server updates aid at least one reload indicia in accordance with said at least one update reload indicia said at least one update reload indicia corresponding to said at least one reload indicia.

10. A transponder-reader payment system according to claim 9, wherein said updating said at least one reload indicia is performed in real-time.

11. A transponder-reader payment system according to claim 9, wherein said at least one reload indicia corresponds to said merchant system identifier.

12. A transponder-reader payment system according to claim 11, wherein said at least one reload indicia corresponds to a minimum depletion value, said issuer system server incrementing said preloaded value data file where said depleted value is less than or equal to said minimum depletion value.

13. A transponder-reader payment system according to claim 9, wherein said at least one reload indicia may include a maximum load value.

14. A transponder-reader payment system according to claim 12, wherein said at least one reload indicia may include incrementing said preloaded value data file in accordance with a predetermined time period.

15. A transponder-reader payment system according to claim 12, wherein said preloaded value data file is incremented a predetermined number of occurrences.

16. A transponder-reader payment system according to claim 12, further including a second funding source in communication with said issuer system server, and said preload value data file, said second funding source containing a second funding source value.

17. A transponder-reader payment system according to claim 16, wherein said issuer system server retrieves at least a portion of said second funding source value and increments said preloaded value data file said at least a portion of said second funding source value.

18. A transponder-reader payment system according to claim 3, wherein said user transaction value is greater than said predetermined value, said issues system server providing a transaction authorization required notice to said user interface.

19. A transponder-reader payment system according to claim 18, wherein said transaction authorization required notice is provided in real-time.

20. A transponder-reader payment system according to claim 19, wherein said transaction authorization required notice is provided to a message retrieval account, wherein a transaction approved transmission is provided to said issuer system server via said user interface.

21. A transponder-reader payment system according to claim 20, wherein said message retrieval account is accessible via said user interface.

22. A method of Radio Frequency Identification transponder-reader payment comprising:

a. providing a transponder system identifier to a merchant system, associating the transponder system identifier to a merchant system identifier and a user transaction request forming a merchant transaction request, the user transaction request containing a transaction value and a transaction identifying marker;

b. providing the merchant transaction request to an issue system server; and

comparing said user transaction request to a preloaded value data file, the preloaded value data file associated with a transponder system identity, the preloaded value data file containing a value.

23. A method according to claim 22, further comprising:

a. determining that the user transaction is less than or equal to the preloaded data file value;

b. retrieving a portion of the preloaded data file value and providing the portion of the preloaded data file value to the merchant system;

c. deducting the portion of the preloaded data file value from the preloaded data file value forming a depleted preloaded data file value;

d. determining that the depleted preloaded data file value is one of less than and equal to a minimum depletion level;

e. replacing at least a portion of the deducted portion of the preloaded data file value according to a reload protocol.

24. A method according to claim 23, wherein the replacing is performed in response to the merchant system identifier.

25. A method according to claim 23, wherein the replacing is performed in response to the transaction identifying marker.

26. A method according to claim 23, wherein the replacing at least a portion of the depleted portion of the preloaded data file includes retrieving at least a portion of the depleted portion from at least one of a first funding source and a second funding source.

27. A method according to claim 23, further comprising:

providing the transponder system identifier to an issuer system server via a user interface remote from the issuer system;

providing in real-time an update reload protocol to the issuer system server, the issuer system server updating in real-time the reload protocol in accordance with the provided update reload protocol.

28. A method of providing a Radio Frequency Identification transponder-reader payment system comprising

a. providing a transponder system identifier and at least one load indicia to an issuer system server in real-time;

b. forming a load criteria protocol including the at least one load indicia; and

c. loading a preloaded data file account with value in accordance with the load indicia.