Systems and methods for managing multiple accounts on a RF transaction device using secondary identification indicia

• US 8,423,475 B2
• Filed: 07/13/2011
• Issued: 04/16/2013
• Est. Priority Date: 07/10/2001
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: American Express Travel Related Services Company, Inc. (American Express Company)
• Inventors: Saunders, Peter D., Bishop, Fred
• Primary Examiner(s): Coppola, Jacob C.
• Application Number:
  US13/181,846
• Publication Number:
  US 20110289001A1
• Time in Patent Office: 643 Days
• Field of Search: 705/66
• US Class Current: 705/66
• 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/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• 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/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• 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
• CPC Class Codes: G07F 7/1083 Counting of PIN attempts

Abstract

Systems and methods are configured to manage data sets associated with a transaction device. For example, a method is provided for facilitating the management of distinct data sets on a transaction device that are provided by distinct data set owners, wherein the distinct data sets may include differing formats. The method includes the steps of: adding, by a read/write, a first data set to the financial transaction device, wherein the first data set is owned by a first owner; adding, by the read/write device, a second data set to the financial transaction device, wherein the second data set is owned by a second owner; and storing the first data set and the second data set on the financial transaction device in accordance with an owner defined format. The first and second data sets are associated with first and second owners, respectively, and are configured to be stored independent of each other. The transaction device user may be permitted to select at least one of the multiple data sets for transaction completion using a secondary identifier indicia. Where the user selects multiple accounts for transaction completion, the user may be permitted to allocate portions of a transaction to the selected transaction accounts. The transaction request may be processed in accordance with the user'"'"'s allocations.

Claims

1. A method comprising:

providing, by a processor configured to manage a plurality of data sets, information relating to a first data set and a second data set for selection, wherein the information includes the first data set and the second data set being associated with transaction categories;

determining, by the processor, a selection of at least one of the first data set and the second data set based in part on a preference of data set use and a transaction category of a transaction request; and

configuring, by the processor, a first method of authentication corresponding to the first data set and a second method of authentication corresponding to the second data set,

wherein the first data set is owned by a first data set owner and the second data set is owned by a second data set owner, wherein the first data set owner is distinct from the second data set owner;

wherein the first method of authentication and the second method of authentication (1) are configured by the first data set owner and the second data set owner independently and (2) each include a distinct access authentication protocol defined by the first data set owner and the second data set owner, respectively;

providing, by the processor, the first data set owner access rights to the first data set, in response to authentication of the first data set owner using the respective distinct access authentication protocol defined by the first data set owner, wherein at least one access right includes authorization to at least one of add and remove a static field of the first format;

providing, by the processor, the second data set owner access rights to the second data set, in response to authentication of the second data set owner using the respective distinct access authentication protocol defined by the second data set owner, wherein at least one access right includes authorization to at least one of add and remove a static field of the second format;

receiving, from a user, a request to modify the first data set or the second data set;

receiving authorization of the user requested modification from the respective data set owner;

in response to the receiving authorization of the user requested modification from the respective data set owner, modifying, by the processor, the first data set or the second data set based on the user requested modification.

2. The method of claim 1, further comprising:

adding, by the processor and to a database on a radio frequency (RF) transaction device, the first data set and the second data set;

receiving, by the processor and at the RF transaction device, the selection of at least one of the first data set and the second data set to complete the transaction request;

authenticating, by the processor and in response to receiving the selection, the transaction request;

determining, by the processor and based on the authenticating, whether the transaction request is approved; and

completing, by the processor and in response to the determining indicating that the transaction request is approved, the transaction request according to the selection,

3. The method of claim 1, wherein the transaction request is authenticated by a third party.

4. The method of claim 2, wherein the transaction request is billed, by a third party, to a user account associated with the RF transaction device.

5. The method of claim 3, wherein the third party is at least one of an issuer or a phone carrier.

6. The method of claim 1, wherein the first data set has a first format and the second data set has a second format, wherein the first format is different from the second format, and the first data set is stored in accordance with the first format, and the second data set is stored in accordance with the second format.

7. The method of claim 2, wherein the receiving a. selection step further comprises receiving an allocation of the entire transaction request to either the first data set or the second data set.

8. The method of claim 2, wherein the receiving a selection step further comprises receiving a selection of a plurality of data sets to complete the transaction request.

9. The method of claim 1, wherein the providing information relating to the first data set and the second data set for selection further comprises audibly providing information.

10. The method of claim 1, wherein the providing information relating to the first data set and the second data set for selection further comprises providing information during a transaction.

11. The method of claim 2, wherein the receiving the selection of at least one of the first data set and the second data set to complete the transaction request further comprises the selection of a portion of a transaction to allocate to at least one of the first data set and the second data set.

12. The method of claim 1, wherein the transaction category is based on the type of good or service involved in the transaction request.

13. The method of claim 1, wherein the transaction category is based on user prioritization of the first data set and the second data set.

14. The method of claim 2, wherein an RF reader determines the selection of at least one of the first data set and the second data set based in part on the preference of data set use and the transaction category of the transaction request.

15. The method of claim 2, wherein the receiving a selection further comprises receiving an allocation of a first portion of the transaction request to the first data set for transaction completion, and wherein the receiving a selection further comprises receiving an allocation of a second portion of the transaction request to the second data set for transaction completion.

16. The method of claim 2, further comprising:

using a first secondary identifier indicium in response to the first data set being selected and using a second secondary identifier indicium in response to the second data set being selected;

wherein in response to the first data set being selected, the receiving includes receiving the first secondary identifier indicium corresponding to the first method of authentication, and in response to the second data set being selected, the receiving includes receiving the second secondary identifier indicium corresponding to the second method of authentication,

17. The method of claim 16, wherein at least one of the first secondary identifier indicium and the second secondary identifier indicium is translated to a translated identifier indicium known by a third party, and wherein the translated identifier indicium is used to facilitate at least one of the authenticating or a billing to a user account associated with the RF transaction device.

18. The method of claim 16, wherein at least one of the first secondary identifier indicium and the second secondary identifier indicium is a personal identifier number (PIN), telephone number, or a biometric identifier.

19. An article of manufacture including a non-transitory, tangible computer readable storage medium having instructions stored thereon that, in response to execution by a processor configured to manage a plurality of data sets, cause the processor to perform operations comprising:

providing, by the processor, information relating to a first data set and a second data set for selection, wherein the information includes the first data set and the second data set being associated with transaction categories;

determining, by the processor, a selection of at least one of the first data set and the second data set based in part on a preference of data set use and a transaction category of a transaction request; and

configuring, by the processor, a first method of authentication corresponding to the first data set and a second method of authentication corresponding to the second data set,

wherein the first data set is owned by a first data set owner and the second data set is owned by a second data set owner, wherein the first data set owner is distinct from the second data set owner;

wherein the first method of authentication and the second method of authentication (1) are configured by the first data set owner and the second data set owner independently and (2) each include a distinct access authentication protocol defined by the first data set owner and the second data set owner, respectively;

providing, by the processor, the first data set owner access rights to the first data set, in response to authentication of the first data set owner using the respective distinct access authentication protocol defined by the first data set owner, wherein at least one access right includes authorization to at least one of add and remove a static field of the first format;

providing, by the processor, the second data set owner access rights to the second data set, in response to authentication of the second data set owner using the respective distinct access authentication protocol defined by the second data set owner, wherein at least one access right includes authorization to at least one of add and remove a static field of the second format;

receiving, from a user, a request to modify the first data set or the second data set;

receiving authorization of the user requested modification from the respective data set owner;

in response to the receiving authorization of the user requested modification from the respective data set owner, modifying, by the processor, the first data set or the second data set based on the user requested modification.