| US 7,463,133 B2 | ||
| Systems and methods for providing a RF transaction device operable to store multiple distinct calling card accounts | ||
| David S. Bonalle, New Rochelle, N.Y. (US); Jeff Fehlhaber, Glendale, Ariz. (US); and Peter D. Saunders, Salt Lake City, Utah (US) | ||
| Assigned to American Express Travel Related Services Company, Inc., New York, N.Y. (US) | ||
| Filed on Mar. 27, 2004, as Appl. No. 10/810,469. | ||
| Application 10/810469 is a continuation in part of application No. 10/608792, filed on Jun. 27, 2003. | ||
| Application 10/608792 is a continuation in part of application No. 10/435420, filed on May 09, 2003. | ||
| Application 10/435420 is a continuation in part of application No. 10/340352, filed on Jan. 10, 2003. | ||
| Application 10/340352 is a continuation in part of application No. 10/192488, filed on Jul. 09, 2002, granted, now 7,239,226. | ||
| Claims priority of provisional application 60/304216, filed on Jul. 10, 2001. | ||
| Claims priority of provisional application 60/396577, filed on Jul. 16, 2002. | ||
| Prior Publication US 2005/0004866 A1, Jan. 06, 2005 | ||
| Int. Cl. G05B 19/00 (2006.01); G06F 7/00 (2006.01); H04B 1/00 (2006.01) | ||
| U.S. Cl. 340—5.61 [340/10.1; 340/10.51; 340/5.21] | 7 Claims |
| 1. A method for facilitating a transaction using a plurality of calling card issuer owned data sets on a transaction instrument,
the method comprising the steps of:
facilitating enrollment of a first call carrier data set owner and a second call carrier data set owner into a RF transaction
instrument program;
facilitating adding to a database, a first calling card data set of a first format at the transaction instrument, wherein
said first calling card data set is owned by said first call carrier data set owner;
facilitating adding to a database, a second calling card data set of a second format at the transaction instrument, wherein
said second calling card data set is owned by said second call carrier set owner, wherein said first owner is distinct from
said second owner, and said first format is different from said second format,
wherein said first calling card data set is stored in accordance with said first format, and said second calling card data
set is stored in accordance with said second format;
adding a header to at least one of said first and second calling card data sets, the header identifying at least a status
condition of the at least one of said first and second calling card data sets, wherein the status condition indicates an action
to be taken relative to the respective calling card data set; and
wherein said transaction instrument is operable to complete a calling card call in accordance with at least one of said first
and second format.
|