Patent Grant
9213965
1. Field of the Invention
The present invention relates generally to electronic inventory management. More specifically, the present invention relates to machines, methods, and program products for facilitating electronic inventory management of products through messaging over existing financial services electronic payment networks.
2. Description of the Related Art
As computers continue to become faster and faster and as database access and database management continues to improve, the prospects of, and the desire for, instituting viable and cost-effective electronic inventory tracking systems by managing entities, e.g., manufacturers, product suppliers, shippers, etc., has evolved. A conventional application of an electronic inventory tracking system includes barcodes or radiofrequency identification tags placed on products, which can be readily scanned as products are shipped between various brick and mortar facilities. Such electronic inventory tracking systems perform superbly when the product stays within the control of the specific entity, i.e., manufacturer, product supplier, or shipper.
Such systems, however, have an inherent lag and often fail when the products are being placed outside the control of the managing entity. That is, once the products are delivered to retail merchants, for example, the managing entity must rely on the retail merchants to provide the desired data or incur significant expense to send in manual teams to collect this data. Various large retail merchants having robust information technology departments have tried to help reduce such inherent lag by allowing manufacturers and suppliers direct access to their sales activity data. Individual local franchises and other smaller retailers, however, although collectively accounting for substantial portions of the products being sold in certain select categories, generally do not have the resources to provide the manufacturers and suppliers such data in such manner—instead, periodically providing sales data in compiled reports, if at all.
As such, in order for the managing entity to determine what and how much of its product or products have been sold by the merchant, the managing entity must either wait for reports sent from the merchant, or in many cases, send a person on-site to visually inspect current inventory. Such personal visits, although having some benefits, still do not necessarily provide accurate inventory or sales reporting data. On countless occasions, the person sent to perform the on-site inspection, being only marginally familiar with the storage facilities owned by the retail merchant, may overlook a storage location that the busy retail merchants forgot to identify. Other errors occur when, for example, various inventory is misidentified or shelved improperly; an error that may only be discovered after the on-site visitor pre-orders additional product, only to have it refused by the merchant.
Although not necessarily employing or even familiar with the latest computer technology being used for inventory or sales tracking, these same retail merchants have been found to be quite familiar and extremely comfortable with employing the latest in point-of-sale (“POS”) technology. Accordingly, a machine, program product, and methods for facilitating electronic inventory management of products through messaging over existing financial services electronic payment networks which utilizes existing POS technology, and which does not require use of a conventional online computer system to retrieve sales tracking or other inventory management data is described herein.
In view of the foregoing, various embodiments of the present invention advantageously provide a machine, program product, and method for facilitating electronic inventory management of products through messaging over existing financial services electronic payment networks, which utilize existing point-of-sale (“POS”) technology, and which does not require use of a conventional online computer system to retrieve sales tracking or other inventory management data. Various embodiments of the present invention advantageously provide a service that enables a product provider (e.g., manufacturer, supplier, etc.) to obtain real-time inventory data by assigning individual product sets traditional credit card identification numbers compatible with a traditional financial services electronic payment network, e.g., MasterCard®, Visa®, American Express®, or Discover® network, and that enables a consumer or retail merchant to scan or otherwise enter such data into a POS terminal which can correspondingly relay real-time purchase transaction data over the payment network for use by the product provider or other managing entity. Advantageously, such service can be offered to any business and can be made available anywhere that the associated financial services electronic payment network is available.
More specifically, an example of an embodiment of a machine for facilitating electronic inventory management of serialized products through messaging over an existing financial services electronic payment network can include a database containing lookup tables positioned to relate each of a plurality of universal product-transaction identifiers to a corresponding product set of a plurality of product sets and a corresponding associated product set code, such as a universal product code, and a processor configured to operate on the computer, the processor executing a program product stored in a memory accessible by the processor and executable on the processor and positioned to perform a process of messaging over an existing financial services electronic payment network and the process of updating inventory data for each of a plurality of product sets, the computer program product performing the steps of generating a plurality of unique financial services electronic payment network compatible universal product-transaction identifiers (often referred to as a Primary Account Number or PAN when applied to a payment card), and assigning or otherwise associating each separate one of the plurality of universal product-transaction identifiers with a different set of a plurality of product sets. Each of the plurality of universal product-transaction identifiers includes a common, e.g., financial transaction bank identification number (“BIN”) also interchangeably referred to as an issuer identifier number (“IIN”) and a product identification number. According to this example, each product within each single product set of the plurality of product sets is characterized by being a same type, size, and quantity as each other product in the respective same product set. Each product within each single product set of the plurality of product sets also has a same universal product code associated therewith that is different from the universal product code associated with each product in any of the other product sets of the plurality of product sets. Further, each product within each one of the plurality of product sets is different or otherwise differentiated from each product in any of the other product sets of the plurality of product sets by at least one of the following: type, size, quantity, and delivery mode. The products, either through enhanced product packaging or through use of an enhanced product identification purchase ticket or slip, are configured to interface with the merchant's POS terminal (e.g., through use of a magnetic stripe) to enable electronic inventory tracking over the existing financial services electronic payment network, e.g., MasterCard®, Visa®, American Express®, and/or Discover® networks.
The machine can also include providing the plurality of universal product-transaction identifiers to a product provider for placement on respective associated products, with each associated product coupled with a transaction identifier storage medium for storing the respective associated universal product-transaction identifier, and with each transaction identifier storage medium configured to interface with a POS terminal positioned to receive the respective universal product-transaction identifier to thereby facilitate electronic inventory management over the existing financial services electronic payment network using the universal product-transaction identifier. The machine can also of receive a purchase transaction message sent through the financial services electronic payment network from each of a plurality of retail merchants each having a POS apparatus including a POS terminal. The purchase transaction message can include the universal product-transaction identifier that is associated with the respective product being purchased. According to this example, the universal product-transaction identifier is received through a respective POS terminal responsive to the POS terminal receiving the respective universal product-transaction identifier as a result of the customer or merchant, for example, swiping the product container or product identification ticket or slip through the magnetic stripe slot of the POS terminal. The method can also include storing purchase transaction data associated with the plurality of product sets purchased across the plurality of retail merchants, for access by the product provider—with the purchase transaction data being related by universal product code to the received universal product-transaction identifiers (for storage).
An example of an embodiment of a machine for facilitating electronic inventory management of a serialized product through messaging over an existing financial services electronic payment network, can also include an externally accessible storage medium for storing a universal product-transaction identifier associated with each same product within one single set of a plurality of sets of, e.g., non-transaction card, products, and a retail container carrying the storage medium. The retail container can be in the form of a packaging container containing a non-transaction card, a product associated with the universal product-transaction identifier stored in the storage medium, or a product identification ticket or slip. According to this example, each product within each single product set of the plurality of product sets is characterized by being a same type, size, and quantity as each other product in the respective same product set. Each product within each of one the plurality of product sets is different from each product in any of the other product sets of the plurality of product sets by at least one of the following: type, size, quantity, and delivery mode. Additionally, each product within each single product set of the plurality of product sets also has a same universal product code associated therewith that is different from the universal product code associated with each product in any of the other product sets of the plurality of product sets. Further, according to this example, the transaction identifier storage medium is configured to interface with a point-of-sale terminal positioned to receive the respective universal product-transaction identifier. Advantageously, as described above, such universal product-transaction identifier assigned or otherwise associated with the product can be used to access the existing financial services electronic payment network to enable the provision, receipt, and storage of purchase transaction data over the payment network, as part of the purchase process.
An example of an embodiment of a machine for facilitating electronic inventory management of serialized products through messaging over an existing financial services electronic payment network, can receive data from a product apparatus, i.e., either a product with enhanced product packaging or an enhanced product identification purchase ticket/slip, such as, for example, that described above; an inventory management computer positioned remote from and in communication with a merchant POS apparatus/terminal over the existing financial services electronic payment network to receive and process purchase transaction data; and electronic inventory management program product stored in the memory of the inventory management computer, for example, as described below.
An example of an embodiment of an electronic inventory management program product for facilitating electronic inventory management of serialized products through messaging over an existing financial services electronic payment network, can include a set of instructions that, when executed by one or more computers or processors, cause the one or more computers or processors to perform various operations including, for example, receiving a first purchase transaction message from a merchant POS apparatus responsive to a user interfacing the storage medium storing a universal product-transaction identifier of a selected one of the products of the plurality of product sets with the merchant POS apparatus. If the merchant POS apparatus supports partial authorization messaging, the message can include a flag indicating a capability of the merchant POS apparatus to, support partial-authorization messaging, along with at least a portion of the universal product-transaction identifier assigned to the selected product. The operations can also include storing purchase transaction data associated with the product being purchased for use by the respective product provider, sending partial-authorization approval data to the respective merchant POS apparatus responsive to receiving the first purchase transaction message, and receiving a second payment message defining a purchase acknowledgment from the respective merchant POS apparatus acknowledging that the merchant POS apparatus or a merchant associated therewith received from a purchasing customer sufficient monetary funds to purchase the respective product. The operations can also include making available through an external communications network not associated with the financial services electronic payment network, at least portions of the purchase transaction data to the product provider.
The operations can also include either the same computer/processor or a different computer/processor, generating the plurality of unique financial services electronic payment network compatible universal product-transaction identifiers on a common, e.g., financial transaction IIN, and associating each separate one of the plurality of universal product-transaction identifiers with a different product set of the plurality of product sets. The operations can further include providing the plurality of universal product-transaction identifiers to the product provider for universal product-transaction identifier placement on respective associated products.
Embodiments of the present invention provide at least two primary benefits: (1) efficiency for product distribution; and (2) the provision of real-time sales data to identify customer trends and behavior. Regarding efficiency, if a distributor, for example, can eliminate the step where the driver performs a manual inventory at the merchant site, and instead pre-stocks the delivery truck with only what is needed in the order of the route, the distributor can substantiality increase delivery throughput. Regarding the provision of real-time sales data, if there is a spike in demand for 32 oz. orange soda on a Tuesday, the bottler can start producing more on Tuesday or Wednesday, if needed.
To accomplish these benefits, according to various embodiments of the present invention, the unique universal product-transaction identifier assigned to a specific group of same products is in the form of an electronic payment network compatible transaction card number, which includes an, e.g., financial transaction IIN and a product identification number associated with a specific type of product. Also, a product itself can be configured to interface with a POS terminal to enable electronic product purchase tracking over the existing financial services electronic payment network using the universal product-transaction identifier, for example, which can be assigned according to a product identifier such as a universal product code or stock keeping unit.
So that the manner in which the features and advantages of the invention, as well as others, which will become apparent, may be understood in more detail, a more particular description of the invention briefly summarized above may be had by reference to the embodiments thereof, which are illustrated in the appended drawings, which form a part of this specification. It is to be noted, however, that the drawings illustrate only various embodiments of the invention and are therefore not to be considered limiting of the invention's scope as it may include other effective embodiments as well.
The present invention will now be described more fully hereinafter with reference to the accompanying drawings, which illustrate embodiments of the invention. This invention may, however, be embodied in many different forms and should not be construed as limited to the illustrated embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout. Prime notation, if used, indicates similar elements in alternative embodiments. Note, the term product as used herein includes packaged and unpackaged goods, documentation of services, or goods and services collectively and individually defining products.
Manufacturers and other product suppliers typically know how much product from a batch has been shipped to their retail outlet. Without a physical count, however, they generally do not know, real-time, how many products of different batches have been sold to individual customers for a single retail outlet/merchant, much less across multiple retail outlets/merchants. Barcodes, RFID tags, etc., affixed to products, however, provide the downstream merchant an automated methodology of tracking product sales. In a typical scenario, the manufacturer or other product suppliers affix to the product a barcode label identifying the product. The serialized product is then typically delivered either directly, or through wholesalers, to multiple retail merchants for distribution to individual retail customers. Then, as the product is sold, the barcode is scanned to record the sale. This data can be compiled by each separate retail merchant and provided to the product supplier. Such data, however, is often stale upon arrival and is often plagued with inaccuracies.
Various embodiments of the present invention include systems, apparatus, program product, and methods which use a magnetic label, RFID tag, or other storage media containing a “universal product-transaction identifier” often referred to as a “Primary Account Number” or “PAN,” which includes an, e.g., financial transaction issuer identifier number (“IIN”) to track sales of each individual product. According to various embodiments of the present invention, at checkout, the IIN/PAN is swiped or read using, e.g., RF-PayPass®, PayWave®, etc., at a point-of-sale (“POS”) terminal having access to a conventional financial services electronic payment network. Partial authentication logic, for example, can then be used to capture its sale and keep the transaction moving. Such data can beneficially provide a real time record of specific product items being sold, allowing the manufacturer or product supplier to perform real-time inventory management based on real-time product sales data.
For example, at the end of the transaction, the manufacturer or product supplier can know with certainty that 32 oz Product X was sold at the Merchant Gas Station Y located on 100 Main St on October 1 at 10:02 PM. The product manufacturer or supplier can beneficially not only access this near real-time sales data to find out not only how much overall product has been sold, but can do so at the universal product code (“UPC”) or stock keeping unit (“SKU”) level, as well as receive the date and time of the purchase behavior. This data, across multiple merchants, especially the smaller merchants, can be extremely valuable to the manufacturer or supplier of Product X for product manufacturing or inventory planning. In addition, since the manufacturer of Product X, or the distributor, generally delivers Products X, Y, Z, on a regular basis, according to embodiments of the present invention, the delivery truck driver can arrive and know in advance which of Products X, Y, Z, is needed, and in what quantity.
A substantial improvement in delivery and efficiency can be realized, compared with that of the conventional process where the distributor loads the truck with all SKU's and the delivery driver enters the merchant store, performs a manual inventory, and then returns to the truck to replenish the inventory levels. As a result of implementation of various embodiments of the present invention, the distributor can eliminate the step where the driver performs a manual inventory check and can instead pre-stock the delivery truck with only what is needed and in the order of the route, thereby increasing delivery throughput. Additionally, such real-time sales data can be used to identify customer trends and behavior. If there is a spike in demand for Product X is identified on a Tuesday, the manufacturer they can start producing more Product X as early as that day.
A machine 30 for facilitating electronic inventory management of products 31 through either traditional or partial authentication messaging over an existing (traditional) financial services electronic payment network 33 is shown in
Communication network 101 connects the product apparatus 35 to the merchant acquirer computer 63, financial services electronic payment network 33, issuer processor computer 61, the transaction tracking computer 81 and the product provider 97 (though the communications network 101 is depicted connecting only the customer 65, product provider 97 and transaction tracking computer 81) and can include, for example, a telecommunication network 103, which can include a wire-based telephone network, pager network, cellular network, or a combination thereof, and a computer network 105. As one skilled in the art will appreciate, the computer network 105 can connect all of the system components using a local area network (“LAN”) or wide area network (“WAN”), or a combination thereof. For example, financial services electronic payment network 33, issuer processor computer 61, and transaction-tracking computer 81 may be associated with the same entity and are thereby configured as a plurality of servers operating together in a LAN. Alternatively, the merchant acquirer computer 63 and payment network may be the same entity and operate together using a LAN, but use a WAN to connect to the issuer processor computer 61. Accordingly, though not all such configurations are depicted, all are within the scope of the disclosure.
Product apparatus 35 connects to the POS terminal 67, which can be, e.g., a terminal at a merchant or, alternatively, a device interface such as a telephone or computer connected to an internet, connection, and initiates the product order by accessing the machine 30 using same. As shown in
To use the POS terminal 67, and thereby access the machine 30, a user swipes or otherwise enters order information carried on a product apparatus 35 for a consumer product or the like. An exemplary product apparatus 35, 35′ is shown in
In one configuration, the product apparatus 35 can include the container medium 37 containing a product 31, e.g., medication or the like, and having a universal purchase transaction identifier number 41 carried thereon. The container medium 37 may be, e.g., a pill bottle or other packaging, that may be manufactured so that at least one of a storage medium 39, a purchase transaction identifier number 41, or a bar code 49, is printed or otherwise affixed on the product apparatus 35. For example, the container medium 37 may be a pill bottle with a cap portion and a bottle portion, with the cap portion having a distal end for engaging a magnetic stripe reader in, e.g., POS 67. To engage the POS 67, the cap portion may have a substantially card shaped, flat portion made from, e.g., 30 mm plastic and a magnetic stripe formed thereon. As one skilled in the art will appreciate in these exemplary configurations, the purchase transaction identifier number 41 may be manually entered into the POS terminal 67 using the keypad 69 e.g., a product apparatus using the bar code 49 or the transaction identifier number image 47; the purchase transaction identifier number 41 can be read by swiping the product apparatus 35 through the a magnetic stripe reader/slot 73, e.g., a product apparatus using the storage medium 39 disposed on the card-shaped, flat potion of the product apparatus 35; or the purchase transaction identifier number 41 can be read using bar code scanned 71, e.g., a product apparatus using the bar code 49. As one skilled in the art will appreciate, the product apparatus 35, may use the storage medium 39; the purchase transaction identifier number 41, the bar code 49 printed on the product apparatus 35, or any combination thereof or any equivalent methods as known or obvious to those skilled in the art.
An alternative product apparatus 35′ is illustrated in
As shown in
Moreover, as one skilled in the art will appreciate, the product apparatus 35, 35′, may use the storage medium 39, 39′, the purchase transaction identifier number 41, 41′, the bar code 49, 49′ printed on the product apparatus 35, 35′, individually or in any combination thereof or any equivalent methods as known or obvious to those skilled in the art. For example, the purchase transaction identifier number 41 can be printed on the product apparatus and stored in the storage medium, while the bar code 49, 49′ contains the product UPC or SKU number for inventory management by the merchant. Such a system would require two data entry steps at the POS terminal, but could reduce any delay between inventory updates between the merchant and issuer. Alternatively, the bar code could contain the purchase transaction number, and no other identification means could be used. Moreover, rather than labeling or embossing the actual universal product-transaction identifier number 41 on the external surface of the container medium 37, 37′, some businesses may choose to not visually divulge the universal product transaction identifier number 41, i.e., some may provide no identifier number at all on the container medium surface, or may use/assign some other identifier number that is uniquely associated with the universal product transaction identifier number 41, for example, for use during conversations with customer service, etc.
The universal product-transaction identifier 41 may be a numerical identifier that includes an IIN 51, i.e., a number, typically six (6) digits, for example, used to identify the issuing bank or other issuer so that messages can be routed through the payment network; a unique product identifier number 53 used for identifying a specific product, and a checksum digit 55. In operation, a manufacturer or product supplier working with an issuer or processor, or the issuer, itself, assigns a different payment network compatible payment card number received from the issuer to each product. In addition, an individual issuer could assign multiple IIN numbers for different product providers, and the payment network would route each of the IIN numbers to the same issuer for processing, i.e., parsing the universal product transaction identifier number 41, by manufacturer and then associating the product identifier number to the product. For example, as shown in
Moreover, according to various embodiments of the present invention, the IIN 51 may identify a financial issuer, such as a bank, that will settle financial transactions, or may identify a non-financial issuer, such as a manufacturer, that will not settle financial transactions, and in such embodiments, the IIN is used to route the transaction data to the issuer through the financial services network not to identify the product provider. Here, different read tracks of the storage device, i.e., that might contain data related to a product provider associated with the universal product transaction identifier, could be read into the network for transmittal to the issuer so that the issuer could match an incoming universal product transaction identifier with the product provider identified in the message. Moreover, a single issuer may assign an IIN according to transaction type, i.e., whether the IIN is associated with a financial transaction or the IIN is associated with an inventory management transaction, and manage incoming purchase transaction messages accordingly. As one skilled in the art will appreciate, several other configurations compatible with at least one traditional financial service electronic payment network 33, however, are within the scope of the present invention.
Once the POS terminal 67 receives the universal product-transaction identifier 41, and any other data that may be stored in the storage medium, from the product apparatus 35, the POS terminal 67 may append time of sale data thereto for transmission, i.e., and any additional transaction information such as the transaction date, transaction time, merchant identification, etc., and thereby assemble a purchase transaction message for transmittal. The purchase transaction message is then encrypted and transmitted through the communications network 101 to the merchant acquirer computer 63. The merchant acquirer computer is both configured and positioned in communication with the issuer processor computer 61 through the financial services electronic payment network 33, and decrypts the purchase transaction message, including the universal product-transaction identifier 41, and appends additional data, such as the merchant acquirer identification, there to for transmission of the purchase transaction message to the financial services electronic payment network 33. As one skilled in the art will recognize, in addition to transmitting the universal product-transaction identifier 41, the merchant acquirer could also transmit settlement data to the payment network so that the merchant or product provider 97 can receive payment in conjunction with the order. To perform these duties, merchant acquirer computer 63, for example, consists of at least one computer, though it can be implemented as one or more computers each having a processor and memory coupled to the processor to store operating instructions therein, which can be configured in the form of a server.
The merchant acquirer computer 63 transmits the purchase transaction message, including the universal product-transaction identifier 41, to the financial services electronic payment network 33, which operates to set transaction rules, facilitate transactions, settles funds between parties, engages in risk mitigation etc. Examples of payment networks 31 are e.g., MasterCard®, Visa®, American Express®, or Discover® network. At the financial services electronic payment network 33, the purchase transaction message is decrypted so that the issuer can be identified using the IIN portion of the universal product transaction identifier 41, and the purchase transaction message is then routed to the appropriate issuer 61. The financial services electronic payment network 33 can be configured as one or more computers each having a processor and memory coupled to the processor to store operating instructions therein, which can be configured in the form of a server.
The financial services electronic payment network 33 routes the purchase transaction message, including the universal product-transaction identifier 41, which may be encrypted before transmission, to the issuer processor computer 61. The issuer processor computer 61 traditionally funds transactions, i.e., bills the customer a charge, and can be e.g., a bank. Here, in addition to settling merchant accounts, the issuer processor computer 61 transmits inventory data, using for example, the purchase transaction message and universal product-transaction identifier 41, for inventory management by a transaction-tracking computer 81. To achieve this end, the issuer processor computer 61, can be implemented as one or more computers each having a processor and memory coupled to the processor to store operating instructions therein, which can be configured in the form of a server.
The issuer processor computer 61 sends at least a portion of the purchase transaction message, including the universal product-transaction identifier 41, to the transaction-tracking computer 81. Transaction tracking computer 81 performs many of the functions of the machine related assigning a plurality of universal product-transaction identifiers. To achieve this, transaction tracking computer could be configured as an application server or plurality of application servers connected to and as a part of the issuer processor computer 61 and accessible by a plurality of workstations associated with the issuer processor computer 61, as shown in
It should also be understood that the illustrated merchant acquirer computer, payment network, issuer processor computer and transaction tracking computer configuration are given by way of example and that other types of servers or computers configured according to various other methodologies known to those skilled in the art, can be used. For example, a single computer, a plurality of computers, a server, or server cluster or server farm may be employed, and this disclosure does not limit any configuration of computers and servers for each. Moreover, each may be deployed at a server farm or server cluster managed by a server host, and the number of servers and their architecture and configuration may be increased based on usage, demand, and capacity requirements for the machine 30.
As shown in
The database server 95 can be used to store product, merchant, and transaction information in separate records, tables, or columns in an associated database, which may be received from the financial services electronic payment network 33. As is understood in the art, the database server 95 includes a processor directing data from a bus into the database memory, which can be e.g., a hard drive, optical storage or the like, and computer software that provides each of the plurality of issuer component computers (not shown), including the transaction tracking computer 81, access the data therein.
As shown in
Transaction tracking computer 81 can be configured as a computer, a server, or a system of distributed computers or servers that at least include memory 93, program product 91, processor 508, input/output device and (“I/O”) 1410, as shown in
As can be seen, the I/O device is connected to the processor 1408. Processor 1408 is the “brains” of the transaction-tracking computer 81, and as such executes program product 91 and works in conjunction with the I/O device 1410 to direct data to memory 93 and to send data from memory 93 to the database server 95, telecommunications interface 107, and web server 109. Processor 1408 can be any commercially available processor, or plurality of processors, adapted for use for the transaction tracking computer 81, e.g., Intel® Xeon® multicore processors, Intel® micro-architecture Nehalem, AMD Opteron™ multicore processors, etc. As one skilled in the art will appreciate, processor 1408 may also include components that allow the transaction tracking computer 81 to be connected to a display [not shown] and keyboard that would allow a user to directly access the processor 1408 and memory.
Memory 93 stores instructions for execution on the processor 1408, and consists of both non-volatile memory, e.g., hard disks, flash memory, optical disks, and the like, and volatile memory, e.g., SRAM, DRAM, SDRAM, etc., as required to process embodiments of the instant invention. As one skilled in the art will appreciate, although memory 93 is depicted on, e.g., the motherboard of the transaction-tracking computer 81, memory 93 may also be a separate component or device, e.g., FLASH memory, connected to the transaction-tracking computer 81. Memory 93 may also store applications that various workstations can access and run on the transaction-tracking computer 81. Importantly, memory 93 stores the program product 91 of the instant invention. As one skilled in the art will understand, the program product 91, along with one or more databases/tables/fields/records can be stored either in memory 93 or in separate memory associated, for example, with a database server 95, positioned in communication with the transaction tracking computer 81, e.g., as shown in
The electronic inventory management program product 91 can be configured to process the received purchase transaction message and purchase transaction data and is described in more detail in reference to
The transaction tracking computer 81, or alternatively the issuer processor computer 61, can also include at least portions of an electronic inventory management program product 91 loaded or otherwise stored in memory associated therewith. Note, the program product 91 can be in the form of microcode, programs, routines, and symbolic languages that provide a specific set for sets of ordered operations that control the functioning of the hardware and direct its operation, as known and understood by those skilled in the art. Note also, the program product 91, according to an embodiment of the present invention, need not reside in its entirety in volatile memory, but can be selectively loaded, as necessary, according to various methodologies as known and understood by those skilled in the art.
According to the exemplary embodiments of the present invention, the electronic inventory management program product 91 can include a set of instructions that, when executed, for example, by the transaction tracking computer or server, etc. 81, cause the transaction tracking computer 81 to perform various operations to include receiving a purchase transaction message from a POS terminal 67 through the financial services electronic payment network 33 and the issuer processor computer 61 responsive to a user interfacing the universal product-transaction identifier 41 of a selected one of the products 31 with POS terminal 67, i.e., by swiping the magnetic stripe, placing an RFID tag within range of a reader, or scanning the barcode if appropriate software is preloaded in the POS terminal 67 or other controlling portion of the merchant POS apparatus. The purchase transaction message can include at least a portion of the universal product-transaction identifier 41 assigned to the selected product 31 along with other merchant POS identifying and transaction related data.
If the POS terminal 67 supports partial message authorization messaging, the message can include a flag indicating a capability of the POS terminal 67 to support partial-authorization messaging. That is, during checkout involving a purchase of, for example, Orange 32 oz supplied by Soft Drink Company X, according to such embodiment of the present invention, a purchase transaction message is sent over the payment network 33 with data including the 4000 . . . 02 identifier and the partial auth flag. Partial-authorization approval data is sent to the POS terminal 67 in response to receiving the purchase transaction message. The partial authorization approval data can include data indicating a partial authorization approval balance, typically in an amount of zero dollars, to indicate to the merchant via the POS terminal 67, a requirement to tender funds in full from another source (cash, check, credit card, etc.).
The operations can also include receiving from the respective POS terminal 67, a second payment message defining a purchase acknowledgment that the POS terminal 67, or a merchant associated therewith, received from a purchasing customer sufficient monetary funds to purchase the respective product 31. In case of a failure to pay, in response to a cancellation initiated by the merchant, the transaction reverses and the indication of the sale of the product 31 associated with the specific UPC or SKU 49 is deleted/expunged.
The operations can further include storing purchase transaction data associated with the respective product 31 being purchased for use by a provider 97 of the product 31 being purchased. According to one configuration of many different types of configurations known to those skilled in the art of computer systems, one or more look-up tables/lists/databases of product providers 97, particular products 31 and their respective UPCs or SKUs 49, and associated universal product-transaction identifiers 41 or product identifier numbers 53 (i.e., the “card” number portion which translates to the assigned UPCs or SKUs, and thus, the product being purchased), can be stored either in memory 93 or in separate memory, for example, associated with a database server 95 positioned in communication with the transaction tracking computer 81. The transaction tracking computer 81 can use the universal product-transaction identifier 41 (e.g., 16 digit card number) and/or product identifier number 53 to access the tables associated with the transaction message, and to update various relevant tables with the received purchase transaction message data into usable sales, inventory, and other purchase transaction data for the associated product 31 for the respective product provider 97. This data can also be stored in a database associated with memory 93, or in memory associated with a database server 95, in one or more tables or databases which can include columns or fields, such as, for example: product name, UPC or SKU 49, universal product-transaction identifier 41, a merchant category code, merchant identification number (which corresponds to a merchant location), terminal identification number, and time-of-day the product 31 was purchased, etc.
As one skilled in the art will appreciate, the program product can be written to parse the product transaction message and to store relevant portions in one or more tables, and then to query tables that contain the relevant data for each product provider and assembles a product provider transaction message from the database tables. Since each product provider could request different provider transaction message, the provider tables and fields could be static, i.e., not change for each provider, but each transaction message could be programmed to be unique or custom to the product provider, i.e., contain information important or relevant to a particular product provider. These operations could also include making at least some of the stored purchase transaction data available to the product provider 97 through one or more external communications networks 101 not associated with the financial services electronic payment network 33, or alternatively, compiling such data, real-time, for transmission to the product provider 97. Beneficially, subscribing product providers 97 could access near real-time sales data to find out, not only how much overall product 31 has been sold, but at the UPC/SKU level, as well as the date and time of the purchase behavior. Such data across multiple merchants, especially the smaller merchants, can be invaluable to the product providers 97 for product production and stock planning. In operation, according to an embodiment of the present the product provider transaction message could include data that would allow Soft Drink Company X to know with certainty that an Orange 32 oz soda was sold at the Merchant Gas Station Y located on 100 Main St on October 1 at 10:02 PM.
In addition since the product providers 97 or their distributor deliver their respective products 31 on a regular basis, as noted previously, the distributor can also be programmed to receive the product provider transaction message so that a delivery truck can arrive and know in advance what product 31 is needed. Compared to the current process where the distributors load up the truck with all UPCs/SKUs, and the delivery driver enters into each the merchant's store on his/her delivery route, takes an inventory of existing product 31 and then returns to the truck to then extract the necessary product 31 to replenish the inventory levels, embodiment of the present invention provide a substantial improvement in efficiency.
As shown in
According to one configuration, the universal product-transaction identifiers 41 generated for each separate product provider 97 are done so on a different common, e.g., financial, transaction issuer identifier number IIN 51 for each product provider 97. The common IIN 51, which is included in the universal product-transaction identifier 41, is typically used by the payment network 33 to identify the issuer, but in this exemplary configuration, can also be used by the issuer to identify the product provider 97. In other words, the IIN identifies both the issuer and a particular product provider associated with the issuer. As one skilled in the art will appreciate, other configurations, such as one where the IIN identifies the issuer and the purchase transaction message includes other data to identify the product provider, may also be used in this system and are within the scope of this disclosure.
Note, the singular term product provider 97 includes reference to not only a single individual entity, but can also include reference to a separate division, subdivision, section, product line, or other type of grouping, as desired. As such, it should be understood that different IINs 51 need not be assigned to product providers 97 in the form of different legal entities, but can be assigned to a single legal entity, and that each such entity division, subdivision, section, product line, or other grouping, can be considered a separate product provider 97, whether or not it would be so considered in the “legal” sense. Note also, although indicated as numeric, if supported by the payment network 33, each of the “unique” universal product-transaction identifiers 41 can alternatively be differentiated from each other identifier 41 by containing therein a distinct series of letters, numbers and letters, code scheme, and arrangement of characters selected for such purpose. And, although applicable to product providers 97 having only a single product, most product providers 97 provide multiple different types of products 31 or, at least, multiple different versions of a same or core product 31, which typically have different sales characteristics and may appeal to different types of customers. Thus, each “different” product 31, whether differentiated by type (e.g., orange vs. grape) or by some other characteristic (e.g., 12 oz. vs. 32 oz.) should be assigned a product identification number 53 which is different across products 31 affiliated with the single product provider 97.
As further shown in
Each product 31 is also assigned a product identifier (e.g., UPC or SKU 49), which can also be carried or otherwise contained by the container medium 37, 37′, typically using a paste-on label, to allow electronic product identification using the bar-code scanner 71 of the POS terminal 67. The universal product-transaction identifiers 41 selected for storage in the storage medium 39 of the particular product 31, are done so, according to a preferred configuration, such that each product 31 within each single set 43 of the plurality of sets 45 of products 31, for each same product provider 97, have the same UPC/SKU 49 associated therewith that is different from the UPC/SKU 49 associated with each product 31 in any of the other sets 43 of products 31.
As further shown in
As shown in
As shown in
Regardless of the configuration, the merchant POS apparatus/terminal 67 sends a purchase transaction message sent through the financial services electronic payment network 33, which can use the IIN 51 of the purchase transaction identifier 41 associated with the product 31 being purchased to identify the appropriate issuer, and to route the purchase transaction message thereto via the issuer processor computer 61 and/or transaction tracking computer 81.
As shown in
In a partial authorization messaging environment, the purchase transaction message is a first message, which, along with the purchase transaction identifier 41 associated with the respective product 31 being purchased, includes a flag indicating a capability of the merchant POS apparatus/terminal 67 to support partial-authorization messaging, and generally the following data items: merchant category code, merchant identification number, merchant identification number, terminal identification number, and time-of-day. As such, the steps/operations can also include the issuer sending partial-authorization approval data to the respective merchant POS apparatus/terminal 67 in response to receiving the first purchase transaction message (block 255), and the issuer receiving a second payment message from the respective merchant POS apparatus/terminal 67 acknowledging that the merchant POS apparatus/terminal 67 or a merchant associated therewith received sufficient monetary funds to purchase the respective product 31 (block 257). In a preferred configuration, the partial authorization approval data includes data indicating a partial authorization approval balance of zero dollars that can function as prompt to do the merchant/customer to tender funds in full from another source.
The steps/operations can further include making the purchase transaction data available to the product provider 97 (block 259), for example, over an external communications network 101. The data can be either immediately available, or a delay can be incorporated to allow the respective merchants to cancel the purchase transaction if either sufficient funds are not received or if the product 31 is returned/refunded. Also or alternatively, transaction reports can be generated to provide near real time or slight-time-delayed purchase transaction data to allow real-time inventory manufacturing and delivery management of the products 31.
Note, although the operations of receiving and storing were discussed with respect to a single product purchase, the operation of receiving a purchase transaction message can include receiving a plurality of purchase transaction messages from a plurality of retail merchant apparatus/terminals 67 each positioned across separate and spaced apart retail merchant sites. Additionally, the stored purchase transaction data can include purchase transaction data for each of the products 31 supplied to each of the retail merchants by the product provider 97 and separately purchased therefrom.
Moreover, while embodiments of the present invention have been described in the context of a fully functional system, those skilled in the art will appreciate that the mechanism of at least portions of the present invention and/or aspects thereof are capable of being distributed in the form of a computer readable medium of instructions in a variety of forms for execution on a processor, processors, or the like, and that embodiments of the present invention apply equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of computer readable media include, but are not limited to: nonvolatile, hard-coded type media such as read only memories (ROMs), CD-ROMs, and DVD-ROMs, or erasable, electrically programmable read only memories (EEPROMs), recordable type media such as floppy disks, hard disk drives, CD-R/RWs, DVD-RAMs, DVD-R/RWs, DVD+R/RWs, flash drives, and other newer types of memories, and transmission type media such as digital and analog communication links. For example, such media can include both operating instructions and operations instructions related to the program product 91 and the computer implemented method steps/operations, described above.
In the drawings and specification, there have been disclosed a typical preferred embodiment of the invention, and although specific terms are employed, the terms are used in a descriptive sense only and not for purposes of limitation. The invention has been described in considerable detail with specific reference to these illustrated embodiments. It will be apparent, however, that various modifications and changes can be made within the spirit and scope of the invention as described in the foregoing specification. For example, although reference has been made to merchant POS apparatus/terminals, it should be understood that no actual sale is required. Thus, use of non-merchant apparatus/terminals having access to one or more of the existing financial services electronic payment networks, is within the scope of the present invention.
This application claims priority to and the benefit of U.S. Provisional Patent Application No. 61/118,127, filed Nov. 26, 2008, titled “System, Apparatus, Methods, And Program Product For Electronic Inventory Tracking,” and is related to U.S. Non-Provisional patent application Ser. No. 12/554,432, filed Sep. 4, 2009, titled “System, Method, and Program Product for Retail Activation and Reload Associated with Partial Authorization Transactions,” and U.S. patent application Ser. No. 12/609,896, filed Oct. 30, 2009, titled “Machine Methods, And Program Product For Electronic Order Entry,” each incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3752904 | Waterbury | Aug 1973 | A |
| 4247759 | Yuris et al. | Jan 1981 | A |
| 4334307 | Bourgeois et al. | Jun 1982 | A |
| 4439636 | Newkirk et al. | Mar 1984 | A |
| 4449040 | Matsuoka et al. | May 1984 | A |
| 4528643 | Freeny, Jr. | Jul 1985 | A |
| 4532416 | Berstein | Jul 1985 | A |
| 4577061 | Katzaff et al. | Mar 1986 | A |
| 4625276 | Benton et al. | Nov 1986 | A |
| 4677565 | Ogaki et al. | Jun 1987 | A |
| 4678895 | Tateisi et al. | Jul 1987 | A |
| 4706275 | Kamal | Nov 1987 | A |
| 4722054 | Yorozu et al. | Jan 1988 | A |
| 4727243 | Saver | Feb 1988 | A |
| 4750201 | Hodgson et al. | Jun 1988 | A |
| 4797540 | Kimizu | Jan 1989 | A |
| 4827113 | Rikuna | May 1989 | A |
| 4868900 | McGuire | Sep 1989 | A |
| 4877947 | Mori | Oct 1989 | A |
| 4879744 | Tasaki et al. | Nov 1989 | A |
| 4884212 | Stutsman | Nov 1989 | A |
| 4951308 | Bishop et al. | Aug 1990 | A |
| 4968873 | Dethloff et al. | Nov 1990 | A |
| 5012077 | Takano | Apr 1991 | A |
| 5048085 | Abraham et al. | Sep 1991 | A |
| 5050207 | Hitchcock | Sep 1991 | A |
| 5068891 | Marshall | Nov 1991 | A |
| 5101098 | Naito | Mar 1992 | A |
| 5138650 | Stahl et al. | Aug 1992 | A |
| 5146067 | Sloan et al. | Sep 1992 | A |
| 5148481 | Abraham et al. | Sep 1992 | A |
| 5151582 | Fujioka | Sep 1992 | A |
| 5155342 | Urano | Oct 1992 | A |
| 5163086 | Ahearn et al. | Nov 1992 | A |
| 5192947 | Neustein | Mar 1993 | A |
| 5220593 | Zicker et al. | Jun 1993 | A |
| 5221838 | Gutman et al. | Jun 1993 | A |
| 5225666 | Amarena et al. | Jul 1993 | A |
| 5264689 | Maes et al. | Nov 1993 | A |
| 5265155 | Castro | Nov 1993 | A |
| 5266782 | Alanärä et al. | Nov 1993 | A |
| 5272320 | Hakamada | Dec 1993 | A |
| 5278752 | Narita et al. | Jan 1994 | A |
| 5285382 | Muehlberger et al. | Feb 1994 | A |
| 5327482 | Yamamoto | Jul 1994 | A |
| 5334821 | Campo et al. | Aug 1994 | A |
| 5340969 | Cox | Aug 1994 | A |
| 5352876 | Watanabe et al. | Oct 1994 | A |
| 5359182 | Schilling | Oct 1994 | A |
| 5409092 | Itako et al. | Apr 1995 | A |
| 5416306 | Imahata | May 1995 | A |
| 5438186 | Nair et al. | Aug 1995 | A |
| 5442567 | Small | Aug 1995 | A |
| 5448044 | Price et al. | Sep 1995 | A |
| 5465206 | Hilt et al. | Nov 1995 | A |
| 5477038 | Levine et al. | Dec 1995 | A |
| 5504808 | Hamrick, Jr. | Apr 1996 | A |
| 5511114 | Stimson et al. | Apr 1996 | A |
| 5513117 | Small | Apr 1996 | A |
| 5550358 | Tait et al. | Aug 1996 | A |
| 5577109 | Stimson et al. | Nov 1996 | A |
| 5577112 | Cambray et al. | Nov 1996 | A |
| 5577121 | Davis et al. | Nov 1996 | A |
| 5661254 | Steuer et al. | Aug 1997 | A |
| 5696908 | Muehlberger et al. | Dec 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5732136 | Murphree et al. | Mar 1998 | A |
| 5814798 | Zancho | Sep 1998 | A |
| 5841365 | Rimkus | Nov 1998 | A |
| 5859419 | Wynn | Jan 1999 | A |
| 5870721 | Norris | Feb 1999 | A |
| 5875437 | Atkins | Feb 1999 | A |
| 5878141 | Daly et al. | Mar 1999 | A |
| 5893907 | Ukuda | Apr 1999 | A |
| 5897620 | Walker et al. | Apr 1999 | A |
| 5920848 | Schutzer et al. | Jul 1999 | A |
| 5923016 | Fredregill et al. | Jul 1999 | A |
| 5933812 | Meyer et al. | Aug 1999 | A |
| 5963921 | Longfield | Oct 1999 | A |
| 6000608 | Dorf | Dec 1999 | A |
| 6012635 | Shimada et al. | Jan 2000 | A |
| 6021397 | Jones et al. | Feb 2000 | A |
| 6032859 | Muehlberger et al. | Mar 2000 | A |
| 6041308 | Walker et al. | Mar 2000 | A |
| 6065679 | Levie et al. | May 2000 | A |
| 6112191 | Burke | Aug 2000 | A |
| 6144948 | Walker et al. | Nov 2000 | A |
| 6154738 | Call | Nov 2000 | A |
| 6189787 | Dorf | Feb 2001 | B1 |
| 6208978 | Walker et al. | Mar 2001 | B1 |
| 6249773 | Allard et al. | Jun 2001 | B1 |
| 6253998 | Ziamo | Jul 2001 | B1 |
| 6304860 | Martin et al. | Oct 2001 | B1 |
| 6315193 | Hogan | Nov 2001 | B1 |
| 6450407 | Freeman et al. | Sep 2002 | B1 |
| 6467684 | Fite et al. | Oct 2002 | B2 |
| 6704714 | O'Leary et al. | Mar 2004 | B1 |
| 6739506 | Constantine | May 2004 | B1 |
| 6793131 | Hogan | Sep 2004 | B2 |
| 6865544 | Austin | Mar 2005 | B1 |
| 6920434 | Cossette | Jul 2005 | B1 |
| 6999943 | Johnson et al. | Feb 2006 | B1 |
| 7010507 | Anderson et al. | Mar 2006 | B1 |
| 7031939 | Gallagher et al. | Apr 2006 | B1 |
| 7072862 | Wilson | Jul 2006 | B1 |
| 7127452 | Yashiro | Oct 2006 | B1 |
| 7177829 | Wilson et al. | Feb 2007 | B1 |
| 7206761 | Colvin | Apr 2007 | B2 |
| 7252223 | Schofield | Aug 2007 | B2 |
| 7258273 | Griffin | Aug 2007 | B2 |
| 7370076 | Friedman et al. | May 2008 | B2 |
| 7392224 | Bauer et al. | Jun 2008 | B1 |
| 7398919 | Cooper | Jul 2008 | B2 |
| 7426492 | Bishop et al. | Sep 2008 | B1 |
| 7451920 | Rose | Nov 2008 | B1 |
| 7472089 | Hu et al. | Dec 2008 | B2 |
| 7493279 | Kwan | Feb 2009 | B1 |
| 7509286 | Bent et al. | Mar 2009 | B1 |
| 7546945 | Bucci et al. | Jun 2009 | B1 |
| 7567936 | Peckover et al. | Jul 2009 | B1 |
| 7599879 | Louie et al. | Oct 2009 | B2 |
| 7606918 | Holzman et al. | Oct 2009 | B2 |
| 7607570 | Constantine | Oct 2009 | B1 |
| 7628319 | Brown et al. | Dec 2009 | B2 |
| 7653591 | Dabney | Jan 2010 | B1 |
| 7702583 | Hamilton et al. | Apr 2010 | B1 |
| 7702587 | Nguyen et al. | Apr 2010 | B2 |
| 7752102 | Thomas | Jul 2010 | B2 |
| 7757944 | Cline et al. | Jul 2010 | B2 |
| 7783571 | Fish et al. | Aug 2010 | B2 |
| 7792717 | Hankins et al. | Sep 2010 | B1 |
| 7810735 | Madani | Oct 2010 | B2 |
| 7813955 | Ariff et al. | Oct 2010 | B2 |
| 7814012 | Johnson | Oct 2010 | B2 |
| 7856399 | Wilkes | Dec 2010 | B2 |
| 7865434 | Sheets | Jan 2011 | B2 |
| 7873569 | Cahn | Jan 2011 | B1 |
| 7899750 | Klieman et al. | Mar 2011 | B1 |
| 7904333 | Perkowski | Mar 2011 | B1 |
| 7933833 | Hotz et al. | Apr 2011 | B2 |
| 7954704 | Gephart et al. | Jun 2011 | B1 |
| 8024242 | Galit | Sep 2011 | B2 |
| 8046256 | Chien et al. | Oct 2011 | B2 |
| 8051006 | Rourk | Nov 2011 | B1 |
| 8055557 | Sorbe et al. | Nov 2011 | B2 |
| 8065187 | Ahlers et al. | Nov 2011 | B2 |
| 8069085 | Ahlers et al. | Nov 2011 | B2 |
| 8086494 | Dooley et al. | Dec 2011 | B2 |
| 8090649 | Galit et al. | Jan 2012 | B2 |
| 8103549 | Ahlers et al. | Jan 2012 | B1 |
| 8108272 | Sorbe et al. | Jan 2012 | B2 |
| 8108279 | Galit et al. | Jan 2012 | B2 |
| 8108977 | Miller | Feb 2012 | B1 |
| 8150764 | Crowe et al. | Apr 2012 | B2 |
| 8175962 | Galit et al. | May 2012 | B2 |
| 8175972 | Galit et al. | May 2012 | B2 |
| 8190480 | Ahlers et al. | May 2012 | B1 |
| 8214286 | Galit et al. | Jul 2012 | B1 |
| 8244611 | Galit | Aug 2012 | B2 |
| 8244637 | Galit et al. | Aug 2012 | B2 |
| 8260678 | Miller | Sep 2012 | B2 |
| 8266047 | Galit | Sep 2012 | B2 |
| 8286863 | Brooks | Oct 2012 | B1 |
| 8290853 | Galit | Oct 2012 | B2 |
| 8296227 | Galit et al. | Oct 2012 | B2 |
| 8301557 | Crowe et al. | Oct 2012 | B1 |
| 8306912 | Galit | Nov 2012 | B2 |
| 8341021 | Ahlers et al. | Dec 2012 | B2 |
| 8355984 | Galit et al. | Jan 2013 | B1 |
| 8371502 | Galit et al. | Feb 2013 | B1 |
| 8386375 | Galit | Feb 2013 | B2 |
| 8392299 | Sorbe et al. | Mar 2013 | B2 |
| 8392330 | Sorbe et al. | Mar 2013 | B2 |
| 8403211 | Brooks et al. | Mar 2013 | B2 |
| 8485441 | Brooks | Jul 2013 | B2 |
| 8494960 | Galit et al. | Jul 2013 | B2 |
| 8538879 | Galit et al. | Sep 2013 | B2 |
| 8589295 | Sorbe et al. | Nov 2013 | B2 |
| 20010021925 | Ukigawa et al. | Sep 2001 | A1 |
| 20010034663 | Teveler et al. | Oct 2001 | A1 |
| 20010034676 | Vasic | Oct 2001 | A1 |
| 20010042785 | Walker et al. | Nov 2001 | A1 |
| 20020002075 | Rowe | Jan 2002 | A1 |
| 20020032612 | Williams et al. | Mar 2002 | A1 |
| 20020038285 | Golden et al. | Mar 2002 | A1 |
| 20020042744 | Kohl | Apr 2002 | A1 |
| 20020055904 | Mon | May 2002 | A1 |
| 20020055909 | Fung et al. | May 2002 | A1 |
| 20020077971 | Allred | Jun 2002 | A1 |
| 20020107797 | Combaluzier | Aug 2002 | A1 |
| 20020111886 | Chenevich et al. | Aug 2002 | A1 |
| 20020138415 | Siska | Sep 2002 | A1 |
| 20020152161 | Aoike | Oct 2002 | A1 |
| 20020194122 | Knox et al. | Dec 2002 | A1 |
| 20020194124 | Hobbs et al. | Dec 2002 | A1 |
| 20030001005 | Risafi et al. | Jan 2003 | A1 |
| 20030004997 | Parker et al. | Jan 2003 | A1 |
| 20030055782 | Slater | Mar 2003 | A1 |
| 20030061170 | Uzo | Mar 2003 | A1 |
| 20030074311 | Saylors et al. | Apr 2003 | A1 |
| 20030097331 | Cohen | May 2003 | A1 |
| 20030135459 | Abelman et al. | Jul 2003 | A1 |
| 20030144935 | Sobek | Jul 2003 | A1 |
| 20030158811 | Sanders et al. | Aug 2003 | A1 |
| 20030167225 | Adams | Sep 2003 | A1 |
| 20030191702 | Hurley | Oct 2003 | A1 |
| 20030191714 | Norris | Oct 2003 | A1 |
| 20030197059 | Tidball et al. | Oct 2003 | A1 |
| 20030200118 | Lee et al. | Oct 2003 | A1 |
| 20030208443 | Mersky | Nov 2003 | A1 |
| 20030217003 | Weinflash et al. | Nov 2003 | A1 |
| 20040036215 | Butler, II | Feb 2004 | A1 |
| 20040047459 | Diaz | Mar 2004 | A1 |
| 20040098351 | Duke | May 2004 | A1 |
| 20040111370 | Saylors et al. | Jun 2004 | A1 |
| 20040117250 | Lubow et al. | Jun 2004 | A1 |
| 20040117302 | Weichert et al. | Jun 2004 | A1 |
| 20040133515 | McCoy et al. | Jul 2004 | A1 |
| 20040143527 | Benkert et al. | Jul 2004 | A1 |
| 20040148252 | Fleishman | Jul 2004 | A1 |
| 20040153407 | Clubb et al. | Aug 2004 | A1 |
| 20040199463 | Deggendorf | Oct 2004 | A1 |
| 20040210484 | Lee | Oct 2004 | A1 |
| 20040211830 | Algiene | Oct 2004 | A1 |
| 20040215554 | Kemper et al. | Oct 2004 | A1 |
| 20040225545 | Turner et al. | Nov 2004 | A1 |
| 20040230523 | Johnson | Nov 2004 | A1 |
| 20040235542 | Stronach et al. | Nov 2004 | A1 |
| 20040236646 | Wu et al. | Nov 2004 | A1 |
| 20040249752 | Prato et al. | Dec 2004 | A1 |
| 20050004839 | Bakker et al. | Jan 2005 | A1 |
| 20050015332 | Chen | Jan 2005 | A1 |
| 20050021363 | Stimson et al. | Jan 2005 | A1 |
| 20050071230 | Mankoff | Mar 2005 | A1 |
| 20050075939 | Bao et al. | Apr 2005 | A1 |
| 20050077350 | Courtion et al. | Apr 2005 | A1 |
| 20050082364 | Alvarez et al. | Apr 2005 | A1 |
| 20050108121 | Gravett et al. | May 2005 | A1 |
| 20050167481 | Hansen et al. | Aug 2005 | A1 |
| 20050167487 | Conlon et al. | Aug 2005 | A1 |
| 20050173520 | Jaros et al. | Aug 2005 | A1 |
| 20050177489 | Neff et al. | Aug 2005 | A1 |
| 20050177502 | Thomas | Aug 2005 | A1 |
| 20050203837 | Leigh et al. | Sep 2005 | A1 |
| 20050205663 | Allgiene | Sep 2005 | A1 |
| 20050228724 | Frangiosa | Oct 2005 | A1 |
| 20050273430 | Pliha | Dec 2005 | A1 |
| 20050278188 | Thomson et al. | Dec 2005 | A1 |
| 20050278347 | Wolf et al. | Dec 2005 | A1 |
| 20050283436 | Greer et al. | Dec 2005 | A1 |
| 20050289044 | Breslin et al. | Dec 2005 | A1 |
| 20060054682 | De La Huerga | Mar 2006 | A1 |
| 20060059085 | Tucker | Mar 2006 | A1 |
| 20060074804 | Cinar | Apr 2006 | A1 |
| 20060085269 | Guilfoyle | Apr 2006 | A1 |
| 20060085334 | Murphy | Apr 2006 | A1 |
| 20060149665 | Weksler | Jul 2006 | A1 |
| 20060149670 | Nguyen et al. | Jul 2006 | A1 |
| 20060161499 | Rich et al. | Jul 2006 | A1 |
| 20060169784 | Collins et al. | Aug 2006 | A1 |
| 20060190322 | Oehlerking et al. | Aug 2006 | A1 |
| 20060206402 | Sullivan | Sep 2006 | A1 |
| 20060212392 | Brown | Sep 2006 | A1 |
| 20060212393 | Brown | Sep 2006 | A1 |
| 20060224502 | McGowan | Oct 2006 | A1 |
| 20060247975 | Shapiro et al. | Nov 2006 | A1 |
| 20060249570 | Seifert et al. | Nov 2006 | A1 |
| 20060249870 | Tachauer | Nov 2006 | A1 |
| 20060259364 | Strock et al. | Nov 2006 | A1 |
| 20060259957 | Tam et al. | Nov 2006 | A1 |
| 20060282356 | Andres et al. | Dec 2006 | A1 |
| 20060282374 | Stone | Dec 2006 | A1 |
| 20060293966 | Inouye | Dec 2006 | A1 |
| 20070000997 | Lambert et al. | Jan 2007 | A1 |
| 20070011089 | DeSchryver | Jan 2007 | A1 |
| 20070038515 | Postrel | Feb 2007 | A1 |
| 20070038924 | Beyer et al. | Feb 2007 | A1 |
| 20070045401 | Sturm | Mar 2007 | A1 |
| 20070061206 | LeFebvre | Mar 2007 | A1 |
| 20070083462 | Cubillo et al. | Apr 2007 | A1 |
| 20070087819 | Van Luchene et al. | Apr 2007 | A1 |
| 20070090183 | Hursta et al. | Apr 2007 | A1 |
| 20070100745 | Keiser | May 2007 | A1 |
| 20070100746 | Blair et al. | May 2007 | A1 |
| 20070100748 | Dheer et al. | May 2007 | A1 |
| 20070106603 | Whyte et al. | May 2007 | A1 |
| 20070136194 | Sloan | Jun 2007 | A1 |
| 20070152038 | Ciancio et al. | Jul 2007 | A1 |
| 20070168265 | Rosenberger | Jul 2007 | A1 |
| 20070174189 | Bishop et al. | Jul 2007 | A1 |
| 20070175982 | Bonalle et al. | Aug 2007 | A1 |
| 20070175984 | Khandaker et al. | Aug 2007 | A1 |
| 20070198352 | Kannegiesser | Aug 2007 | A1 |
| 20070198354 | Senghore et al. | Aug 2007 | A1 |
| 20070198403 | Aloni et al. | Aug 2007 | A1 |
| 20070233596 | Ambrose | Oct 2007 | A1 |
| 20070244778 | Bailard | Oct 2007 | A1 |
| 20070250380 | Mankoff | Oct 2007 | A1 |
| 20070260536 | Stone | Nov 2007 | A1 |
| 20070262140 | Long, Sr. | Nov 2007 | A1 |
| 20070265957 | Advani et al. | Nov 2007 | A1 |
| 20070265960 | Advani et al. | Nov 2007 | A1 |
| 20070267479 | Nix et al. | Nov 2007 | A1 |
| 20070271178 | Davis | Nov 2007 | A1 |
| 20070276736 | Guilfoyle | Nov 2007 | A1 |
| 20070282740 | Wendt | Dec 2007 | A1 |
| 20080005001 | Davis et al. | Jan 2008 | A1 |
| 20080021772 | Aloni et al. | Jan 2008 | A1 |
| 20080040261 | Nix et al. | Feb 2008 | A1 |
| 20080040265 | Rackley et al. | Feb 2008 | A1 |
| 20080052189 | Walker et al. | Feb 2008 | A1 |
| 20080052224 | Parker | Feb 2008 | A1 |
| 20080059363 | Hotz et al. | Mar 2008 | A1 |
| 20080065532 | De la Motte | Mar 2008 | A1 |
| 20080091519 | Foss | Apr 2008 | A1 |
| 20080103968 | Bies et al. | May 2008 | A1 |
| 20080103970 | Books | May 2008 | A1 |
| 20080120129 | Seubert et al. | May 2008 | A1 |
| 20080140561 | Neel | Jun 2008 | A1 |
| 20080140568 | Henry | Jun 2008 | A1 |
| 20080140576 | Lewis et al. | Jun 2008 | A1 |
| 20080162271 | Benjamin | Jul 2008 | A1 |
| 20080162337 | Greenland et al. | Jul 2008 | A1 |
| 20080210753 | Plozay et al. | Sep 2008 | A1 |
| 20080228643 | Hall | Sep 2008 | A1 |
| 20080235095 | Oles et al. | Sep 2008 | A1 |
| 20080270298 | McElroy et al. | Oct 2008 | A1 |
| 20080281734 | Longe et al. | Nov 2008 | A1 |
| 20080294977 | Friedman et al. | Nov 2008 | A1 |
| 20080301162 | Wall et al. | Dec 2008 | A1 |
| 20090006203 | Fordyce et al. | Jan 2009 | A1 |
| 20090048963 | Bishop et al. | Feb 2009 | A1 |
| 20090061929 | Evans | Mar 2009 | A1 |
| 20090063297 | Dooley et al. | Mar 2009 | A1 |
| 20090063342 | Beckers | Mar 2009 | A1 |
| 20090063351 | Schmeyer et al. | Mar 2009 | A1 |
| 20090078757 | Hanson et al. | Mar 2009 | A1 |
| 20090094125 | Killian et al. | Apr 2009 | A1 |
| 20090157220 | Walker et al. | Jun 2009 | A1 |
| 20090164351 | Sorbe et al. | Jun 2009 | A1 |
| 20090164362 | Moore | Jun 2009 | A1 |
| 20090164363 | Ahlers | Jun 2009 | A1 |
| 20090171775 | Cashion et al. | Jul 2009 | A1 |
| 20090192934 | Chu et al. | Jul 2009 | A1 |
| 20090222367 | Jenkins et al. | Sep 2009 | A1 |
| 20090228307 | Sorbe | Sep 2009 | A1 |
| 20090254431 | Crowe et al. | Oct 2009 | A1 |
| 20090265241 | Bishop et al. | Oct 2009 | A1 |
| 20100030687 | Panthaki et al. | Feb 2010 | A1 |
| 20100057554 | Lanford | Mar 2010 | A1 |
| 20100057609 | Sibson | Mar 2010 | A1 |
| 20100076836 | Giordano et al. | Mar 2010 | A1 |
| 20100076875 | Ernst et al. | Mar 2010 | A1 |
| 20100106555 | Mneimneh et al. | Apr 2010 | A1 |
| 20100222132 | Sanford et al. | Sep 2010 | A1 |
| 20100280949 | Van Rensburg | Nov 2010 | A1 |
| 20100306104 | Johnson | Dec 2010 | A1 |
| 20100312684 | Kemper et al. | Dec 2010 | A1 |
| 20110047039 | Crames et al. | Feb 2011 | A1 |
| 20110093323 | Prus et al. | Apr 2011 | A1 |
| 20110106698 | Isaacson et al. | May 2011 | A1 |
| 20110112957 | Ingram et al. | May 2011 | A1 |
| 20110270664 | Jones | Nov 2011 | A1 |
| 20120271697 | Gilman et al. | Oct 2012 | A1 |
| 20130124429 | Zou et al. | May 2013 | A1 |
| 20130173407 | Killian et al. | Jul 2013 | A1 |
| 20140032381 | Killian et al. | Jan 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 0348932 | Jan 1990 | EP |
| 0397512 | Nov 1990 | EP |
| 0397512 | Nov 1990 | EP |
| 0619565 | Oct 1994 | EP |
| 0619565 | Oct 1994 | EP |
| 0348932 | May 1995 | EP |
| 2-238593 | Sep 1990 | JP |
| 2-238593 | Sep 1990 | JP |
| 2-278495 | Nov 1990 | JP |
| 2-278495 | Nov 1990 | JP |
| 3-100791 | Apr 1991 | JP |
| 3-100791 | Apr 1991 | JP |
| 4-165588 | Jun 1992 | JP |
| 4-165588 | Jun 1992 | JP |
| 2010010217 | Feb 2010 | KR |
| WO 8602757 | May 1986 | WO |
| WO8602757 | May 1986 | WO |
| WO 8607647 | Dec 1986 | WO |
| WO8607647 | Dec 1986 | WO |
| WO 8803297 | May 1988 | WO |
| WO8803297 | May 1988 | WO |
| WO 8908899 | Sep 1989 | WO |
| WO8908899 | Sep 1989 | WO |
| WO 9109370 | Jun 1991 | WO |
| WO9109370 | Jun 1991 | WO |
| WO 9309515 | May 1993 | WO |
| WO9309515 | May 1993 | WO |
| WO 9410649 | May 1994 | WO |
| WO9410649 | May 1994 | WO |
| WO 9428498 | Dec 1994 | WO |
| WO9428498 | Dec 1994 | WO |
| WO 9503570 | Feb 1995 | WO |
| WO9503570 | Feb 1995 | WO |
| WO 9746986 | Dec 1997 | WO |
| WO9746986 | Dec 1997 | WO |
| WO0060487 | Oct 2000 | WO |
| WO2007133315 | Nov 2007 | WO |
| 2008102329 | Aug 2008 | WO |
| 200709282 | Oct 2007 | ZA |
| Entry |
|---|
| Orszag, Peter, “Unemployment Insurance as an Economic Stimulus”, Center for Budget and Policy Priorities, Nov. 15, 2011. |
| Powell, Robert L., “Statewide Electronic Commerce Program Status Report”, State of North Carolina Office of the State Controller, Mar. 7, 2007. |
| Parrott, James, “Jittery Wall Street, Calm City?”, Gotham Gazette, Apr. 16, 2007. |
| Zandi, Mark, “Washington Throws the Economy a Rope”, Moody's Economy.com, Jan. 22, 2008. |
| Blair, Christine E., et al., “Challenges to the Dual Banking System: The Funding of Bank Supervision”, FDIC Bank Review, Mar. 31, 2006. |
| Office Action for co-pending U.S. Appl. No. 12/367,187 dated Jun. 27, 2011. |
| “Developing Asia and the World”, Asian Development Bank 2002. |
| Office action from co-pending U.S. Appl. No. 12/338,497 dated Aug. 18, 2011. |
| Notice of Allowance of co-pending U.S. Appl. No. 12/417,199 dated Aug. 18, 2011. |
| Notice of Allowance of co-pending U.S. Appl. No. 12/417,211 dated Aug. 22, 2011. |
| Wolfe, Daniel, “An E-Variation on Payday Loan Theme”, American Banker, Jul. 28, 2005 (cited in Notice of Allowance). |
| “Letter of Credit Explained: What is Letter of Credit?”, Dec. 26, 2005, pp. 1-2 (cited in Office Action from co-pending U.S. Appl. No. 12/338,540 dated Sep. 1, 2011). |
| Office Action from co-pending U.S. Appl. No. 12/338,540 dated Sep. 1, 2011. |
| Notice of Allowance of co-pending U.S. Appl. No. 12/338,365 dated Sep. 1, 2011. |
| Co-pending U.S. Appl. No. 12/562,331, filed Sep. 18, 2009, titled Computerized Extension of Credit to Existing Demand Deposit Accounts, Prepaid Cards and Lines of Credit Based on Expected Tax Refund Proceeds, Associated Systems and Computer Program Products. |
| Final Office Action in co-pending U.S. Appl. No. 12/338,584 dated Sep. 15, 2011. |
| Final Office Action in co-pending U.S. Appl. No. 12/338,684 dated Sep. 23, 2011. |
| Lazarus, David, “120% rate for Wells' Advances”, Oct. 16, 2004, San Francisco Chronicle (cited in Final Office Action in co-pending U.S. Appl. No. 12/338,684 dated Sep. 23, 2011). |
| Office Action in co-pending U.S. Appl. No. 12/397,113 dated Sep. 30, 2011. |
| Notice of Allowance in co-pending U.S. Appl. No. 12/338,645 dated Oct. 3, 2011. |
| Office Action in co-pending U.S. Appl. No. 12/417,182 dated Sep. 28, 2011. |
| Office Action in co-pending U.S. Appl. No. 12/609,896 dated Apr. 5, 2011. |
| Office Action in co-pending U.S. Appl. No. 12/417,162 dated Apr. 13, 2011. |
| Notice of Allowance in co-pending U.S. Appl. No. 12/554,659 dated Aug. 2, 2011. |
| Office Action in co-pending U.S. Appl. No. 12/338,712 dated Jul. 28, 2011. |
| Office Action in co-pending U.S. Appl. No. 12/338,440 dated Aug. 1, 2011. |
| Financial Advice Investment Money Oct. 1, 2009 at 5:50pm, HSBC Offshore Internet Banking (as cited on Notice of Allowance in co-pending U.S. Appl. No. 12/554,659). |
| Financial Advice Investment Money Oct. 1, 2009 at 7:25am, HSBC Offshore Internet Banking (as cited on Notice of Allowance in co-pending U.S. Appl. No. 12/554,659). |
| Jane Boon Pearlstine, Lenders, Borrowers Hook Up Over The Web: Prosper.com and Other Sites Provide Forum for Individual Bidders Willing to Offer Small Loans, Wall Street Journal, May 20, 2006. |
| United Nations Conference on Trade and Development, E-finance and Small and Medium-Size Enterprises (SMEs) in Developing and Transition Economies, UNCTAD Expert Meeting, Oct. 17, 2001. |
| Tim Jones, Paradigms loast, RSA Journal, Oct. 2006, pp. 28-31. |
| Diego Rumiany, Internet Bidding for Microcredit: making it work in the developed world, conceiving it for the developing world, Mar. 2007. |
| Stefan Heng, Thomas Meyer, and Antje Stobbe, Implications of Web 2.0 for financial institutions: Be a driver, not a passenger, Munich Personal RePEc Archive, Jul. 31, 2007. |
| Matt Flannery, Kiva and the Birth of Person to Person Microfinance, Innovations, pp. 31-56, Winter & Spring 2007. |
| Michael K, Hulme and Colette Wright, Internet Based Social Lending: Past, Present and Future, Social Futures Observatory, Oct. 2006. |
| Richard W. Coleman, Is the Future of the Microfinance Movement to be Found on the Internet?, International Trade and Finance Association Working Papers 2007. |
| Amanda Scott and Patrick Towell, The web we weave, Financial World, pp. 12-15, Nov. 2006. |
| Prosper, Access and Transparency through Person-to-Person Lending, FDIC Advisory Committee on Economic Inclusion, Mar. 28, 2007. |
| Co-pending U.S. Appl. No. 12/338,402, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/338,440, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/338,712, filed Dec. 18, 2008, titled “Computer-Implemented Methods, Program Product, and System to Enhance Banking Terms Over Time”. |
| Co-pending U.S. Appl. No. 12/338,684, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Associated Methods”. |
| Co-pending U.S. Appl. No. 12/338,497, filed Dec. 18, 2008, titled “Private Label Promotion Card System, Program Product, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/338,640, filed Dec. 18, 2008, titled “Private Label Promotion Card System, Program Product, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/338,584, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments From Preselected Bank Accounts”. |
| Co-pending U.S. Appl. No. 12/338,645, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Methods to Prioritize Payments From Preselected Bank Accounts”. |
| Co-pending U.S. Appl. No. 12/338,365, filed Dec. 18, 2008, titled “Transfer Account Systems, Computer Program Products, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/397,113, filed Mar. 3, 2009, titled “Person-to-Person Lending Program Product, System, and Associated Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/389,749, filed Feb. 20, 2009, titled “Methods to Advance Loan Proceeds on Prepaid Cards, Associated Systems and Computer Program Products”. |
| Co-pending U.S. Appl. No. 12/417,199, filed Apr. 2, 2009, titled “System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card”. |
| Co-pending U.S. Appl. No. 12/417,211, filed Apr. 2, 2009, titled “System, Program Product, and Associated Methods to Autodraw for Micro-Credit Attached to a Prepaid Card”. |
| Co-pending U.S. Appl. No. 12/417,182, filed Apr. 2, 2009, titled “System, Program Product, and Method to Authorize Draw for Retailer Optimization”. |
| Co-pending U.S. Appl. No. 12/407,320, filed Mar. 19, 2009, titled “Computerized Extension of Credit to Existing Demand Deposit Accounts, Preparid Cards and Lines of Credit Based on Expected Tax Refund Proceeds, Associated Systems and Computer Program Products”. |
| Co-pending U.S. Appl. No. 12/417,162, filed Apr. 2, 2009, titled “System, Program Product, and Method for Debit Card and Checking Account Autodraw”. |
| Co-pending U.S. Appl. No. 12/367,187, filed Feb. 6, 2009, titled “Government Targeted-Spending Stimulus Card System, Program Product and Computer-Implemented Methods”. |
| Co-pending U.S. Appl. No. 12/465,306, filed May 13, 2009, titled “System, Program Product, and Computer-Implemented Method for Loading a Loan on a Pre-Paid Card”. |
| Co-pending U.S. Appl. No. 12/465,803, filed May 14, 2009, titled “System, Program Product, and Method for Loading a Loan on a Pre-Paid Card”. |
| Co-pending U.S. Appl. No. 12/465,277, filed May 13, 2009, titled “System, Program Product, and Computer-Implemented Method for Loading a Loan on a Pre-Paid Card”. |
| Cross, Sam Y., All About . . . the Foreign Exchange Market in the United States, 1998, Federal Reserve Bank of New York. |
| International Search Report from co-pending PCT Application No. PCT/US2009/034692 dated Apr. 14, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/039495 dated May 18, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2008/087689 dated Jun. 17, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/039492 dated May 14, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/043988 dated Jul. 14, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/039512 dated Jun. 8, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/039504 dated May 27, 2009. |
| International Search Report from co-pending PCT Application No. PCT/US2009/043978 dated Jun. 30, 2009. |
| Co-pending U.S. Appl. No. 12/554,659, filed Sep. 4, 2009, titled “System, Method, and Program Product for Foreign Currency Travel Account”. |
| Co-pending U.S. Appl. No. 12/554,432, filed Sep. 4, 2009, titled “System, Method, and Program Product for Retail Activation and Reload Associated with Partial Authorization Transaction”. |
| Co-pending U.S. Appl. No. 12/609,896, filed Oct. 30, 2009, titled Machine Methods, and Program Product for Electronic Order Entry. |
| Co-pending U.S. Appl. No. 12/607,780, filed Oct. 28, 2009, titled Shopping Center Gift Card Offer Fulfillment Machine, Program Product, and Associated Methods. |
| International Search Report for PCT/US09/56072 dated Oct. 20, 2009. |
| Bank Deals-Best Rates and Deals: EverBank's World Currency CDs—My interview with EverBank's Executive Frank Trotter, http://bankdeals.blogspot.com, Jul. 29, 2007. |
| Foreign Exchange Market, http://en.wikipedia.org. |
| Avoid Gift Card Pitfalls, ConsumerReports.org. |
| VIPGift Receives Investment From Summit Partners and Bridgescale Partners, Nov. 11, 2008, Chattanooga, TN and Palo Alto, CA. |
| Office Action dated Jul. 9, 2010 for U.S. Appl. No. 12/338,365. |
| Office Action dated Jul. 9, 2010 for U.S. Appl. No. 12/338,645. |
| Office Action dated Sep. 28, 2010 for co-pending U.S. Appl. No. 12/338,402, filed Dec. 18, 2008. |
| Office Action dated Sep. 3, 2010 for co-pending U.S. Appl. No. 12/417,162, filed Apr. 2, 2009. |
| Co-pending U.S. Appl. No. 13/036,076, filed Feb. 28, 2011, titled Machine, Program Product, and Computer Implemented Method to Construct a Person-To-Person Loan. |
| Office Action dated Feb. 18, 2011, in co-pending U.S. Appl. No. 12/338,402. |
| Final Office Action dated Jan. 26, 2011, in co-pending U.S. Appl. No. 12/338,365. |
| Final Office Action dated Jan. 26, 2011, in co-pending U.S. Appl. No. 12/338,645. |
| Final Office Action dated Jan. 19, 2011, in co-pending U.S. Appl. No. 12/417,162. |
| Office Action dated Feb. 1, 2011, in co-pending U.S. Appl. No. 12/389,749. |
| Co-pending U.S. Appl. No. 12/814,405, filed Jun. 11, 2010 titled Environmental-Friendly Fuel Credit Card System, Program Product, and Computer-Implemented Methods. |
| Co-pending U.S. Appl. No. 12/877,490, filed Sep. 8, 2010 titled System, Program Product, and Method for Debit Card and Checking Account Autodraw. |
| Co-pending U.S. Appl. No. 12/877,524, filed Sep. 8, 2010 titled System, Program Product, and Method for Debit Card and Checking Account Autodraw. |
| Co-pending U.S. Appl. No. 12/562,331, filed Sep. 18, 2009 titled Computerized Extension of Credit to Existing Demand Deposit Accounts, Prepaid Cards and Lines of Credit Based on Expected Tax Refund Proceeds, Associated Systems and Computer Program Products. |
| Krino, Gary, et al., A Birthday Card That Pays Off, The Orange County Register, Jul. 19, 1996, 2 pages. |
| Cohen, Bruce, Alternative to Cash Gains Ground, The Financial Post, Apr. 22, 1994, 2 pages. |
| Bank of Boulder POS Debit Solution at the Table Now in Beta: First Bank to Certify IVI Spirit C2000 on MAPP (R), Business Wire, Aug. 3, 1994, 1 page. |
| Co-pending U.S. Appl. No. 12/700,681, filed Feb. 4, 2010. |
| Co-pending U.S. Appl. No. 12/889,281, filed Sep. 23, 2010. |
| Co-pending U.S. Appl. No. 12/892,847, filed Sep. 28, 2010. |
| Co-pending U.S. Appl. No. 12/731,852, filed Mar. 25, 2010. |
| Microtrax Ltd., PC Electronic Payment Systems Reference Manuel, 1995 (381 pages). |
| John P. Caskey and Gordon H. Selton, Jr. Is the Debit Card Revolution Finally Here?, Federal Reserve Bank of Kansas City, Economic Review, Fourth Quarter 1994, pp. 70-95, vol. 79 #4 (17 pages). |
| Laura Castaneda, Business Promote Services to Customers Day In and Day Out, The Dallas Morning News, Nov. 26, 1994, 3 pages. |
| Margaret Mannix, Checkout Tech, U.S. News & World Report, Feb. 27, 1995, 6 pages. |
| Credit Terminals to be Used at Canadian Liquor Outlets, Card News, Jan. 23, 1995, 1 page. |
| Debit Card Popularity on the Rise, Chain Store Age Executive, Jan. 1994, 1 page. |
| Debit Goes to Dinner, Credit Card Management, New York, Oct. 1994, 2 pages. |
| Alan Peppard, Down and Dirty in Deep Ellum, The Dallas Morning News, Dec. 3, 1994, 2 pages. |
| Everest Reference Manual, VeriFone Part No. 25399, Revision A, Manual Revision 1.0, Jul. 1995, 66 pages. |
| Express Cards and Trains, Chain Store Age Executive Edition, Jan. 1995, 1 page. |
| Súzanne Brown, Goodnight Amy, Meg, Beth and Jo, Rocky Mountain News, Dec. 8, 2994, 1 page. |
| Robert J. Klein, Here Comes the Debit Card, D&B Reports, Jul./Aug. 1990, 2 pages. |
| Hypercom S7C Advertisement, Chain Store Age, Sep. 1995, 4 pages. |
| Hypercom S7SC Advertisement, Chain Store Age, Feb. 1996, 2 pages. |
| IBM 4680-4690 Advanced Payment System for Chain Drug Sales Application User's Guide, Nov. 1996, 256 pages. |
| IBM 4680-4690 Advanced Payment System for Chain Drug Sales Application User's Guide, Jul. 1996, 248 pages. |
| IBM 4680-4690 Advanced Payment System for Supermarket Application User's Guide, Sep. 1996, 222 pages. |
| Fox, Linda A., Keep an Eye on Your Credit Card, The Toronto Sun, Aug. 9, 1996, 1 page. |
| Pyatt, Rudolph A., Jr., Mobil Stations to Permit Use of Bank Cards, The Washington Post. |
| NCR 4430-5000 MSR/PIN User's Guide, 1994, 265 pages. |
| Nieman Marcus: High-Tech for the Holidays, Adweek, Dec. 5, 1994, 1 page. |
| Neiman Marcus Offers Electronic Gift Certificate, Card Fax, Jan. 23, 1995, 1 page. |
| Neiman Marcus to Lauch NM Express Automated Gift Card, PR Newswire, Nov. 22, 1994, 1 page. |
| NM Express Card Advertisement, The New Yorker, Dec. 12, 1994, 3 pages. |
| Service Mark Registration No. 1,981,044 for “NM Express Card”, registered Jun. 18, 1996, 1 page. |
| Omni 480/490 Programmer's Guide, VeriFone Part No. 12924—Revision A, Manual Revision 1.0, Oct. 1993, 228 pages. |
| One Company's Diversification Shakes up Peripherals Market, Chain Store Age, Jun. 1996, 3 pages. |
| O'Keefe, Michael, Portable POS Debit Terminal Mean Greater Convenience, Bank Systems & Technology, Nov. 1994, 2 pages. |
| POS Terminal Can Handle Direct Debits, ABA Banking Journal, Sep. 1984, 2 pages. |
| Racal Corp. Advertisement, POS Terminal Eliminates Credit Card Vouchers, ABA Banking Journal, Nov. 1985, 2 pages. |
| Szabo, Joan C., The Changing World of Financial Services, Nation's Business, Oct. 1994, 7 pages. |
| VeriFone Everest Advertisement, Stores, May 1995, 2 pages. |
| VeriFone Folio (TM) Brings Credit and Debit Card Payment to the Restaurant Table, PR Newswire, May 16, 1994, 3 pages. |
| David B. Barnes, VeriFone Introduces Everest (TM) Customer Activated Payment System to Multi-Lane Retail Market, PR Newswire, Feb. 20, 1995, 2 pages. |
| VeriFone Introduces Pinpad (TM) 1000 to Point-of-Sale Debit Market, M2 Presswire, Apr. 21, 1995, 1 page. |
| VeriFone TCL Terminal Control Language Programmer's Manual, VeriFone Part No. 00368-01, Revision G, Manual Revision 8.0, Aug. 1992, 362 pages. |
| VeriFone Tranz 330 Reference Manual, Verifone Part No. 00483—Revision D, Manual Revision 3.01, Apr. 1990, 144 pages. |
| MicroTrax Ltd. Omni 490M (and 490ML) Operation Manual for Integrated and Non-Integrated Configurations, 1994, 60 pages. |
| MicroTrax Electronic Payment Systems: The MicroTrax Pinstripe Lane Equipment Users Guide, MicroTrax Ltd., Newport Beach, CA 1991, 54 pages. |
| IBM 4680-4690 Supermarket Application—Electronic Funds Transfer Feature Enhancement: User's Guide, IBM Corp., Research Triangle Park, NC, Sep. 1995, 318 pages. |
| IBM 4680 General Sales Application Electronic Funds Transfer User's Guide, IBM Corp., Research Triangle Park, NC, Dec. 1990, 260 pages. |
| IBM 4680 General Sales Application Electronic Funds Transfer User's Guide, IBM Corp., Research Triangle Park, NC, Mar. 1991, 263 pages. |
| IBM 4680 General Sales Application: Guide to Operations, Research Triangle Park, NC, Jun. 1991, 429 pages. |
| Office Action dated Mar. 4, 2011, in co-pending U.S. Appl. No. 12/338,684. |
| Office Action dated Mar. 17, 2011, in co-pending U.S. Appl. No. 12/417,199. |
| Office Action dated Mar. 17, 2011, in co-pending U.S. Appl. No. 12/465,803. |
| Office Action dated Mar. 22, 2011, in co-pending U.S. Appl. No. 12/338,584. |
| Office Action dated Mar. 29, 2011, in co-pending U.S. Appl. No. 12/417,211. |
| Office Action dated Mar. 29, 2011, in co-pending U.S. Appl. No. 12/407,320. |
| Congressional Budget Office, “Emerging Electronic Methods for Making Payments” (Jun. 1996), CBO. |
| Coady et al., “Targeted anti-poverty intervention: A selected annotated bibliography” (Apr. 2002), World Bank. |
| Notice of Allowance from co-pending U.S. Appl. No. 12/609,896 dated Jan. 3, 2012. |
| Notice of Allowance from co-pending U.S. Appl. No. 13/233,268 dated Dec. 13, 2011. |
| Office Action from co-pending U.S. Appl. No. 12/367,187 dated Jan. 6, 2012. |
| Office Action from co-pending U.S. Appl. No. 12/731,852 dated Dec. 22, 2011. |
| Business Dateline, Q Comm Expands Calling Card Products with Best Telecom Point-of-Sale Activated Cards: All Q Comm VeriFone Merchants Can Now Deliver Durable Calling Cards (Dec. 6, 2010), Business Wire (Dec. 8, 2011). |
| Notice of Allowance from co-pending U.S. Appl. No. 12/465,803 dated Dec. 20, 2011. |
| MasterCard Electronic prepaid (Oct. 2003). The Nilson Report, (798), (Dec. 9, 2011), The Banking Source (Document ID 474833171). |
| Office Action for co-pending U.S. Appl. No. 12/607,780 dated Mar. 19, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/465,803 dated Mar. 20, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/562,331 dated Mar. 20, 2012. |
| Ex-parte Quayle Action for co-pending U.S. Appl. No. 12/700,681 dated Mar. 23, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/389,749 dated Mar. 29, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/731,852 dated Apr. 5, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/465,306 dated Apr. 11, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/349,423 dated Apr. 13, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/877,490 dated Apr. 18, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/892,847 dated Apr. 30, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/338,440 dated Jan. 19, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/465,306 dated Nov. 10, 2011. |
| Final Office Action for co-pending U.S. Appl. No. 12/338,540 dated Mar. 15, 2012. |
| Office Action from co-pending U.S. Appl. No. 12/626,349, dated Nov. 22, 2011. |
| Zubko, N., “An Automotic Connection Electronic Transaction Tools Help Manufacturers Connect With Suppliers to Streamline Sourcing Efforts”, Industry Week, Jul. 2008, pp. 26-27, vol. 257, No. 7. |
| Notice of Allowance from co-pending U.S. Appl. No. 12/609,896 dated Oct. 27, 2011. |
| Office Action from co-pending U.S. Appl. No. 12/465,277 dated Oct. 20, 2011. |
| Office Action from co-pending U.S. Appl. No. 12/562,331 dated Oct. 20, 2011. |
| Notice of Allowance from co-pending U.S. Appl. No. 12/407,320 dated Oct. 18, 2011. |
| Downes, How to avoid exchange charges Wasting Money A foreign currency bank account could be the answer, The Daily Telegraph, London (UK), Mar. 10, 2007. |
| Office Action for co-pending U.S. Appl. No. 13/232,405 dated Feb. 2, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/465,277 dated Feb. 28, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/417,182 dated Feb. 14, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/338,497 dated Mar. 1, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/877,524 dated Feb. 14, 2012. |
| Wolf, File History of US 2005/0278347. |
| Check Cashers Move Into Cards, Accounts (Cover Story), ATM & Debit News [serial online], Apr. 20, 2006, 6(24), pp. 1-3, available from Business Source Complete, Ipswich, MA. |
| Mango-Ward, K.; (Oct. 2009), Payday of Reckoning, Reason, 41(5), pp. 40-47, retrieved Jun. 15, 2012, from Research Library (Document ID:1861658171). |
| Wolf, Alan Steven, What to do when the Chain Breaks, Servicing Management, Feb. 1997, 3 pages. |
| 99Bill Launches Installment Credit Services, (Aug. 21, 2008), PR Newswire, 2 pages, retrieved Jul. 9, 2012, from Business Dateline (Document ID: 1536854041). |
| Intralinks, Inc. Begins European Rollout of Its Proven Electronic Solution for Loan Syndication, London (Business Wire), Oct. 8, 1997, 3 pages. |
| Final Office Action for co-pending U.S. Appl. No. 13/232,405 dated May 22, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/405,051 dated Jun. 6, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/877,524 dated Jun. 8, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/700,681 dated Jun. 11, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/365,982 dated Jun. 26, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/554,432 dated Jun. 29, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/349,290 dated Jul. 3, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/338,540 dated Jul. 9, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/282,186 dated Jul. 13, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/330,397 dated Jul. 18, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/367,187 dated Jul. 19, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 13/232,700 dated Jul. 19, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/877,490 dated Sep. 20, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/036,076 dated Jul. 24, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/481,950 dated Jul. 30, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/405,079 dated Aug. 6, 2012. |
| Notice of Allowance co-pending U.S. Appl. No. 13/474,519 dated Aug. 27, 2012. |
| Office Action for co-pending U.S. Appl. No. 12/889,281 dated Aug. 30, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/232,405 dated Sep. 4, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/338,497 dated Sep. 17, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/214,126 dated Oct. 4, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/607,780 dated Oct. 9, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 13/232,700 dated Oct. 12, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/284,524 dated Oct. 15, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/601,724 dated Oct. 18, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/417,162 dated Oct. 1, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 12/607,780 dated Oct. 9, 2012. |
| Office Action for co-pending U.S. Appl. No. 13/536,765 dated Nov. 30, 2012. |
| Notice of Allowance for co-pending U.S. Appl. No. 13/282,186 dated Dec. 17, 2012. |
| Final Office Action for co-pending U.S. Appl. No. 12/892,847 dated Aug. 12, 2014. |
| Hori et al. “Did the Shopping Coupon Program Stimulate Consumption? Evidence from Japanese Micro Data” ESRI Discussion Paper Series No. 12, Apr. 2002, 45 pages. |
| Office Action for co-pending U.S. Appl. No. 12/367,187 dated Sep. 24, 2014. |
| Office Action for co-pending U.S. Appl. No. 12/389,749 dated Oct. 3, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/287,725 dated Aug. 25, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/349,290 dated Oct. 22, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/782,550 dated Sep. 12, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/863,578 dated Sep. 30, 2014. |
| Final Office Action for co-pending U.S. Appl. No. 12/367,187 dated Feb. 12, 2014. |
| Final Office Action for co-pending U.S. Appl. No. 12/889,281 dated Apr. 8, 2013. |
| Final Office Action for co-pending U.S. Appl. No. 12/892,847 dated Mar. 29, 2013. |
| Final Office Action for co-pending U.S. Appl. No. 13/036,076 dated Apr. 8, 2013. |
| Final Office Action for co-pending U.S. Appl. No. 13/214,126 dated Aug. 1, 2013. |
| Final Office Action for co-pending U.S. Appl. No. 13/349,290 dated Mar. 14, 2013. |
| Garriss, J., (2004), Forging an ideal HSA, Workspan, 47(5), 18-25, Retrieved Sep. 3, 2013. |
| Office Action for co-pending U.S. Appl. No. 12/367,187 dated Aug. 1, 2013. |
| Office Action for co-pending U.S. Appl. No. 12/397,113 dated Oct. 15, 2013. |
| Office Action for co-pending U.S. Appl. No. 13/287,725 dated Jan. 17, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/450,617 dated May 12, 2014. |
| Final Office Action for co-pending U.S. Appl. No. 12/389,749 dated Dec. 11, 2014. |
| Health Savings Account (HSA): Horizon Blue Cross Blue Shield of New Jersey, Small Employer Guide, Jan. 2006, 18 pages. |
| Kent FOC Newsletter, retrieved at www.accesskent.com/Courts/FOC/pdfs/newsletter/022006.pdf, Feb. 2006, 1 page. |
| Office Action for co-pending U.S. Appl. No. 12/397,113 dated Nov. 3, 2014. |
| Office Action for co-pending U.S. Appl. No. 12/731,852 dated Nov. 10, 2014. |
| Office Action for co-pending U.S. Appl. No. 12/892,847 dated Nov. 5, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/287,725 dated Sep. 26, 2013. |
| Office Action for co-pending U.S. Appl. No. 13/450,617 dated Oct. 28, 2014. |
| Office Action for co-pending U.S. Appl. No. 13/036,076 dated Jan. 29, 2015. |
| Office Action for co-pending U.S. Appl. No. No. 13/232,700 dated Jan. 29, 2015. |
| Office Action for co-pending U.S. Appl. No. 13/782,550 dated Dec. 17, 2014. |
| Office Action for co-pending U.S. Appl. No. 14/071,386 dated Dec. 16, 2014. |
| Number | Date | Country | |
|---|---|---|---|
| 61118127 | Nov 2008 | US |
