HK1153295A - Systems and methods for providing vending network data management - Google Patents

Description

System and method for providing vending network data management

Trade mark

Is a registered trademark of Coca-Cola corporation of Atlanta, Georgia, USA. Other names used herein may be registered trademarks, trademarks or product names of Coca-Cola corporation or other companies.

Technical Field

The present invention relates to vending networks, and more particularly to systems and methods for providing vending network data management.

Background

In the vending industry, coins and banknotes are one way to pay for goods and services sold. In this regard, when the vending account is settled, coins and banknotes may be collected from the vending apparatus, and the coins and banknotes may be reconciled with the actual inventory to determine what was sold and how much money was received.

In recent years, cashless payments such as credit cards have become an option for payments. In this regard, users of vending apparatus may now be able to pay for goods and services sold using cashless payment in addition to coin and banknote payments. In the case of cashless payments, cashless payments may typically be processed by third party servers. An Electronic Funds Transfer (EFT) may then remit the received cashless payment to the operator of the vending apparatus, eliminating transaction processing fees and/or other fees. Nonetheless, in some cases, the EFT may not reconcile actual vending events with associated actual cashless transactions. More complicated, because fees may be deducted from the cashless funds, the sales of the vends may not match the EFT amount, and in general, the EFT transactions may represent aggregated batches or a pile of transactions, thus obscuring each individual vend transaction.

The process of cashless transactions may present a number of problems for processors handling cashless transactions, vendors that supply goods and/or services that receive cashless transactions through vending machines, and others involved in the cashless transaction process. For example, during a settlement process, coins, banknotes and cashless transactions may not be timely reconciled with inventory as many cashless transactions may also be stored in a vending machine or other associated data storage device. In other cases, cashless transactions may still be routed to a third party server without having been settled but and/or aggregated with little or no transaction level details. Typically, only after vend settlement is initiated, the relevant EFT transactions occur, which may further frustrate the settlement process due to the aggregate nature of EFTs.

Additionally, the routing of cashless transactions to one or more third party servers may also create accountability issues. In some cases, multiple items may be sold from vending machines, and one or more customers may attempt to pay in a cashless manner, such as a credit or debit card. However, in such a case, there is no guarantee that the vending apparatus operator will always see the funds to pay for the vending in a cashless transaction, and further, that the customer will pay for the goods and/or services sold correctly. Thus, there may be little or no accountability as to when a sale occurred or what the customer paid. In addition, there may be little or no accountability as to whether the customer paid for the sale in a timely or correct manner, and little or no assurance that the vending apparatus operator received the correct funds for the sale in a timely manner through a cashless transaction.

Additionally, there are problems in auditing third party services to verify the accuracy and/or correctness of cashless transactions. In this regard, cashless transactional vending may lack the ability to supervise, accountable, audit control, and control how the devices in the vending apparatus operate and how data is communicated with or between various servers or other data processing devices.

Another problem arises when a person working on a route attempts to reconcile transaction amounts and inventory at the vending apparatus location. In some cases, the amount of bills, coins, cashless goods and inventory should be known at the same point in time. When cashless transactions are involved, this means that the value of each transaction without any charge deduction is known, which cashless transaction has been settled is known, and it is also known which settled cashless transaction has a corresponding EFT record indicating that the operator of the vending apparatus has been paid for the cashless transaction. Without this level of detail, it may be unlikely that vending apparatus settlement will be performed across multiple vending apparatus locations accurately or timely, without error. For vending apparatuses in a global location, the settlement process may not be performed efficiently.

Accordingly, there is a need for a system and method for providing vending network data management.

Summary of the invention

Some or all of the above needs may be addressed by various embodiments of the invention. Embodiments of the present invention may provide systems and methods for providing vending network data management.

In one embodiment, a system for vending network data management is provided. The system may include a vend settlement manager program module operable to receive a plurality of electronic transactions from at least one transaction-type device. The vend settlement manager program module may also be operable to reconcile a plurality of electronic transactions. In addition, the vend settlement manager program module may be operable to communicate response data for each electronic transaction to the at least one server.

In another embodiment, a method for providing vending network data management may be provided. The method may include receiving a plurality of electronic transactions from at least one transaction type device. Additionally, the method may include reconciling the plurality of electronic transactions. Additionally, the method may include communicating response data for each electronic transaction to at least one server switch.

In yet another embodiment, a computer readable medium comprising program instructions may be provided. The program instructions may be operable to receive a plurality of electronic transactions from at least one transaction type device. Additionally, the program instructions may be operable to reconcile a plurality of electronic transactions. Additionally, the program instructions may be operable to communicate response data for each electronic transaction to the at least one server.

Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the features and aspects of embodiments of the invention, reference is made to the description and to the drawings.

Brief description of the drawings

The foregoing and other features and aspects of the present invention are apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an exemplary vending network data management system consistent with embodiments of the present invention.

FIG. 2 illustrates an exemplary system for providing vending network data management, consistent with embodiments of the present invention.

FIG. 3 illustrates an exemplary program module or set of computer readable instructions operable to effect vend settlement of at least one vending machine, consistent with embodiments of the invention.

FIG. 4 illustrates an exemplary method of settling a transaction associated with a vending apparatus consistent with embodiments of the invention

Detailed description of embodiments of the invention

The term "transaction" as used herein may refer to a cash or cashless payment associated with the purchase of goods and/or services. Embodiments of the present invention are intended to cover any combination of cash and/or cashless payments or transactions as well as payments or transactions relating to any combination of goods and/or services.

As used herein, the terms "server switch" and "server" may be used interchangeably. Embodiments of the invention are intended to cover any combination of servers, server switches, or other processing devices with similar functionality to the servers or server switches.

As used herein, the terms "reconciliation token" and "unique identifier" are used interchangeably. Embodiments of the present invention are intended to cover any type of unique identifier including, but not limited to, a tie-out mark or any other device, code, or identification instrument with similar functionality.

Referring now to FIG. 1, an example of a system, such as a vending network data management system 100, consistent with embodiments of the present invention is shown. Embodiments of the present invention may provide systems and methods for vending network data management. In general, embodiments of the present invention, such as the vending network data management system 100, may track or otherwise tag any number of transactions processed by the system 100 during communication between at least one server switch and one or more third party servers and/or settlement engines, such as a vending settlement server or vending settlement server program module, using one or more reconciliation tags. Other embodiments of the system are described in fig. 2 and 3, and related articles and methods are described in fig. 4.

In the embodiment illustrated in FIG. 1, the vending network data management system 100 may include one or more transaction devices 102A-N associated with respective vending devices 104A-N. Some or all of the transaction type devices 102A-N may communicate with one or more server switches, e.g., 108A-N, over at least one network, e.g., 106. In one embodiment, one or more transaction type devices 102A-N may communicate with each other over one or more networks, e.g., 106.

The transaction type devices 102A-N may be any processor type device and may be referred to individually as data processing devices. Some or all of the transaction type devices 102A-N may be operable to receive and transmit data associated with at least one cash and/or cashless transaction or consumer. Such data may be referred to as transaction data. The transaction data may include, but is not limited to, vending equipment batch-to-batch settlement (also known as fill-to-fill) information, vending transaction matching and reconciliation processing data, Electronic Funds Transaction (EFT) reconciliation data, cash vending transactions, cashless transaction data, cash transaction data, transaction records, DEX data, MDB data, transaction refund (also known as reverse) data, accounting data, audit data, electronic funds return data, routing management data, business transaction data, and the likeAdministrative data, and other types of data associated with vending apparatus transactions or consumers. Examples of transaction type devices may include, but are not limited to, cash transaction readers, cashless transaction readers, combined cash and cashless transaction readers, RFID readers, biometric readers, Energy Management System (EMS) type devices, Vending Machine Controllers (VMCs), and any other type of payment transaction device. In some cases, the transaction device may be comprised of an HP^TM、DELL^TM、IBM/LENOVO^TMAnd GATEWAY^TMManufactured and can be run by MICROSOFT^TMAnd LINUX^TMThe software provided.

In one embodiment, the transaction-type device, e.g., 102A, may be a payment device operable to receive cash and/or cashless payments from consumers, and may also be operable to facilitate the dispensing of goods and/or services from an associated vending device, e.g., 104A. In another embodiment, the transaction-type device, e.g., 102A, may be a vending apparatus controller operable to facilitate operation of an associated vending apparatus, e.g., 104A.

The vending devices 104A-N may include, but are not limited to, product or beverage dispensers, vending machines, snack food dispensers, devices capable of dispensing or providing consumable food or beverage items, devices capable of dispensing or providing non-consumable items, or devices capable of facilitating the purchase of goods and/or services. The vending apparatus, such as 104A, may also be referred to individually as a vending machine. In some embodiments, the vending apparatus 104A-N may comply with vending industry standards including, but not limited to, the national automatic commerce Association (NAMA) MDB Specification, and the European Vending Association (EVA) DEX Specification. In one embodiment, the vending apparatus 104A-N may include a vending industry standard type multidrop bus (MDB) interface, and/or a Data Exchange (DEX) interface.

In one embodiment, multidrop bus (MDB) data may be collected from vending apparatus, such as 104A-N, and the collected MDB data used to form a transaction data record. In this regard, the MDB data may include, but is not limited to, inventory, product pricing, and other data that may be combined with a payment ID (e.g., PIN number or credit card number) to form a transaction record during a vending event. Additionally, MDB data may be collected during non-vending events and used to form transaction records such as service requests, energy management records, and other types of transaction records.

In the embodiment shown in fig. 1, the network 106 may be a wired or wireless type network, and may be more than one network to facilitate wired and wireless type communications between system components. The network 106 shown in fig. 1 is shown by way of example. Examples of network 106 may include, but are not limited to, a Local Area Network (LAN), a Wide Area Network (WAN), the Internet, a global network, a wireless network, a wired network, and any combination thereof. Wireless network communication may be achieved, for example, by: GSM, GPRS, CDMA2000, 1XRTT, EDGE, 802.11 types and categories including, but not limited to, 'a', 'b', 'G', 'n', 900MHz, 2.4GHz, 5GHz, spread spectrum, open wireless standards, proprietary wireless technologies, 3G, 3.5G, 4G technologies ('G' stands for generation), and any other wireless type communication device, standard, or method. Wired network communications may be implemented by way of, for example, ethernet, Firewire, serial communications, USB, RS 232, and any other wired type of communication device, standard, or method. In one embodiment, the network may be the internet, which may be referred to as a global network.

In the illustrated embodiment, server switch 108A may be a processor-based platform such as a server. In one embodiment, the server switch 108A may be operable to store a copy of some or all of the transaction data received from one or more of the transaction devices 102A-N. Server switch 108A may store some or all of the transaction data in an associated database or data storage device, e.g., 110, 112, or 114. In another embodiment, a server switch, such as 108A, may be operable to generate a unique identifier, such as a tie-out mark, and associate or otherwise add the unique identifier or mark to the transaction record. In some implementations, the server switch, e.g., 108A, can generate a unique identifier or tie-out indicia and associate the unique identifier or tie-out indicia with some or all transactions that can be sent by the system 100 over a network, e.g., 106.

As shown in fig. 1, the system 100 may also facilitate communication with one or more servers 116, 118, 122 and/or third parties 120. In the illustrated embodiment, some or all of the transaction type devices 102A-N may communicate with at least one of: a vend settlement server 116, a data services server 118, a financial institution 120, a third party server 122, and/or any device associated with a third party. In this embodiment, the transaction type device, e.g., 102A, may send data to the server switch, e.g., 108A, over the network, e.g., 106. Server switch 108A may selectively send some or all of the received data to another transaction type device, e.g., 102N; another server switch such as 108N; a vending settlement server such as 116; data service servers such as 118; financial institutions such as 120; third party servers such as 122; or any other device associated with a third party. The data received by the vend settlement server 116, the data services server 118, the financial institution 120, and/or the third party server 122 may be stored in an associated database, such as 109, or other data storage device.

In one embodiment, the transaction type device, e.g., 102A, may send data to the vend settlement server, e.g., 116, via the network, e.g., 106, and the server switch, e.g., 108A. Data initially received or otherwise collected by transaction type device 102A may be sent to server switch 108A in the form of, for example, data packet 124. The data may include, but is not limited to, vending apparatus batch-to-batch settlement (also referred to as fill-up or settlement) information, vending transaction matching and reconciliation processing data, Electronic Funds Transaction (EFT) reconciliation data, cash vending transactions, cashless transaction data, cash transaction data, transaction records, DEX data, MDB data, transaction refund (also referred to as reversal) data, accounting data, audit data, electronic funds return data, routing management data, business management data, and/or any other type of data associated with a vending apparatus transaction or consumer. Finally, some or all of the data may be sent by the server switch, e.g., 108A, to the vend settlement server, e.g., 116.

In one embodiment, the one or more reconciliation indicia may facilitate auditing some or all of the transaction data processed by the one or more vend settlement servers 116 and/or the third-party server 122. For example, the server switch, e.g., 108A, may communicate at least one tie-out token with each transaction to the vend settlement server 116 and/or the third party server 122 and receive transaction data from the vend settlement server 116 and/or the third party server 122 in response to each tie-out token. In this example, the server switch 108A can send at least one reconciliation token to the vend settlement server 116 and/or the third party server 122 in the data packet 126. In response to receiving the one or more reconciliation indicia, the vend settlement server 116 and/or the third-party server 122 can send a data packet 128 to the server switch 108A with response data that includes the one or more reconciliation indicia. This response data may be compared to previously sent transaction data or other data previously stored in a database, e.g., 110, 112, or 114, or other data storage device associated with server switch 108A. In one embodiment, the vend settlement server, e.g., 116, may be referred to as a third party server and may be audited in a similar manner as described above.

Additionally, in one embodiment, a server switch, such as 108A, may be operable to transfer or otherwise communicate one or more transaction records between various target servers. For example, transaction data stored in a particular server may be transmitted to another server by way of a server switch, such as 108A. Additionally, server switch 108A may be operable to distribute data packet 130 with one or more reconciliation indicia in response to transaction data received or sent by server switch 108A. Additionally, the server switch 108A may be operable to maintain at least one transaction database for storing transaction data, such as a plurality of databases including the KO database 110, the tie-out database 112, and the device database 114.

In one embodiment, the server switch, e.g., 108A, may be operable to control access to the network, e.g., 106, by examining each transaction received at the server switch 108A. For example, prior to transmitting transaction data from the transaction type device, e.g., 102A, to the destination location, server switch 108A may check a database, e.g., device database 114, to ensure that the transaction type device, e.g., 102A, from which the transaction is received is allowed to use network 106. If the transaction type device 102A is not allowed to use the network 106, the transaction data is not transmitted to the target location and, optionally, the transaction type device 102A may be notified by the server switch 108A that access to the network 106 is denied.

In another embodiment, a server switch, e.g., 108A, may be operable to control the types or categories of transactions that a particular transaction type device, e.g., 102A, is allowed to send over a network, e.g., 106. In this regard, the server switch 108A may examine the types or categories of transactions sent, compare each transaction type or category to the types or categories of one or more allowed transactions stored in a database, such as the device database 114, and determine whether such transactions are allowed from a device 102A for a particular transaction type. For example, if transaction type device 102A is deployed to receive a particular type of transaction, such as a hotel room key card, server switch and 108A may prevent or otherwise restrict all other transactions, such as non-hotel room key cards, from being used.

As shown in FIG. 1, the vend settlement server, such as 116, may include a vend settlement manager program module 132. The vend settlement manager program module 132 may be a set of computer-executable instructions stored in a processor or memory associated with the vend settlement server 116. The vend settlement manager program module 132 may be operable to receive one or more electronic transactions from at least one transaction-type device, such as 102A-N. In addition, the vend settlement manager program module 132 may be operable to reconcile one or more electronic transactions. In addition, the vend settlement manager program module 132 may be operable to communicate response data for each electronic transaction to at least one server switch, such as 108A. In some embodiments, the vend settlement manager program module may be stored in other computer-readable media, such as memory or data storage devices associated with other servers, databases, or other processor-based or memory-based devices including, but not limited to, 108A-N, 109, 110, 112, 114, 118, 120, 122, 134. In this manner, the system, e.g., 100, can facilitate providing vending network data management in accordance with embodiments of the present invention described herein.

Referring to FIG. 2, an exemplary system 200 for providing vending network data management consistent with embodiments of the present invention is shown. The system 200 may be implemented using some or all of the system components shown in FIG. 1, and in this example, some of the system components of the system 100 are used.

In the embodiment illustrated in FIG. 2, the vend settlement server, e.g., 116, may provide some or all of the operational and financial data processing for an associated operator server, e.g., 134. The operations server may be operable to manage vending apparatus, such as 104A-N, and/or one or more associated vending routes. The vending settlement server 116 may be operable to coordinate reconciliation of coins, banknotes, cashless transactions, and other types of inventory management data. As shown, the vend settlement server 116 may be in communication with an operator server 134. Using the data provided by the vend settlement server 116, the operator server 134 may provide routing management for the vending apparatus, e.g., 104A-N, including but not limited to reporting, routing management, accountability, services, financial management, business analysis, asset management, product inventory management, and data processing. In this regard, the vending settlement server, e.g., 116, may be operable to reconcile money, a prior cashless settlement process (to determine taxes that should be generated for the cashless transaction), a post-settlement process (to determine taxes actually received from the cashless transaction process-as an example of an EFT), and to collate the delivery of funds, inventory, and other vending equipment data into an associated operator server, e.g., 134.

In operation, the operator server 134 may communicate with the vend settlement server 116. Initially, transaction data from one or more transaction type devices, e.g., 102A, and associated vending devices, e.g., 104A, may be received or otherwise collected by the server switch 108A. The server switch 108A may also communicate with data service servers, e.g., 118, and/or third parties, e.g., financial institutions 120, as needed or desired. As previously discussed, the transaction data may be communicated to the vend settlement server 116 through the server switch 108 for processing and/or storage. Alternatively, the vend settlement server, e.g., 116, may use one or more databases to store data, e.g., database 109, as may be needed or desired. In any case, the vend settlement server 116 may communicate with the operator server 134 to handle some or all of the following operations: reconciliation of coins, banknotes, cashless transactions and other types of inventory management data; reporting; managing the route; transaction accountability; service and financial management; a commercial analysis; asset management; managing product inventory; processing data; checking accounts of money; prior cashless settlement processing (determining taxes that should be generated for cashless transactions), post-settlement processing (determining taxes actually received from cashless transaction processing-as an example of EFT), and collating funds delivery, inventory, and other vending equipment data.

In this manner, reconciliation of bills, coins, and cashless transactions may be synchronized with products or inventory that are filled or otherwise refilled in the vending apparatus by the routing operator. Delays in processing certain types of cashless transactions, such as credit card transactions, can result in 100% accountability of payment details (banknotes, coins and cashless taxes) not being achieved when the vending apparatus is refilled by the routing operator. Thus, the ability to determine what has been sold and paid for at any given time, and especially if cashless transactions are delayed by processing, such as during waiting for an Electronic Funds Transfer (EFT), can be difficult to determine. In addition, the inability to accurately determine what has been purchased from the vending apparatus may result in personnel operating on a route incorrectly selecting a refill product to load onto a delivery vehicle (route truck) before driving to the vending apparatus location, which may result in too much or too little refill product being carried on the way for subsequent refilling.

Referring to FIG. 3, an exemplary article of manufacture including at least one program module 132 or set of computer-readable instructions operable to effect vend settlement of at least one vending machine consistent with embodiments of the present invention is illustrated. In one embodiment, an article of manufacture or at least one program module 132 may be implemented by a vending settlement server, such as 116, or other suitable processor-based, computing, or client-type device.

In one embodiment, an article of manufacture may be a program module or a set of computer readable instructions embodied in a computer readable medium, such as software. For example, an article of manufacture may be a program module such as the vend settlement manager program module 132 operable to be executed by at least one vend settlement server such as 116. In this embodiment, the vend settlement manager program module 132 may receive, reconcile, and/or generate transaction data from one or more data sources, including but not limited to vending machines, financial institutions, and/or other data processing resources or servers. In one embodiment, the transaction data may be stored from being obtained or otherwise used for subsequent retrieval in any number of data storage devices or databases, such as 109, 110, 112, and 114 shown in FIG. 3, which may be accessed via the network 106 or in direct communication with an associated vend settlement server 116. The vend settlement manager program module 132 may process transaction data and may communicate with an operator server, such as 134, to allow a user access to one or all of the transaction data and/or to effect vend settlement for one or more vending machines through one or more data processing devices 136A-C. Such data processing devices may include, but are not limited to, Personal Data Assistants (PDAs), client-type devices, computers, laptops, servers, wireless telephones, and/or other types or kinds of data processing devices. Such data processing devices 136A-C may communicate directly with operator servers, such as 134, and/or over networks, such as 106 or the internet.

Program modules such as the vend settlement manager program module 132 may be encoded in various computer languages including, but not limited to, JAVA, PERL, PHP, PYTHON, C #, C + +, vb. Program modules may be referred to, individually or in combination, as software, computer code, data, files, objects files, or assembly code applications and may be embodied on any suitable computer readable medium. The computer readable medium may include, but is not limited to, CDROMs, DVDs, hard drives, microdrives, flash memory, disk drives, networking devices, data processing resources, and other types of computer readable media. In one embodiment, various functions or code associated with program modules, such as the vend settlement manager program module 132, may be distributed between multiple processing devices, such as the vend settlement server 116 and another server, or may exist in a single processing device, such as 116.

In one embodiment, the informational data processed by the vend settlement manager program module 132 may include, for example, cashless transaction data, Electronic Funds Transfer (EFT), DEX data, MDB data, service alert data, coin transactions, ticket transactions, other types of transaction data, and other desired or required data. Coin transactions and ticket transactions may be referred to individually or in combination as cashless transactions.

In at least one embodiment, the vend settlement manager program module, e.g., 132, may be implemented in a separate server. In another embodiment, the vend settlement manager program module, e.g., 132, may be incorporated into a back-end server in communication with one or more other servers, e.g., the third-party server 122. In yet another embodiment, a vend settlement manager program module, such as 132, may be incorporated into the operator server, such as 134, to manage transaction data and/or operational data and provide various results to other functions of the operator server 134. In yet another embodiment, the vend settlement manager program module, e.g., 132, may be incorporated into a wired or wireless handheld data processing device, and may be incorporated into other types of processor-based or client-type platforms as needed and/or desired.

For example, in one embodiment, the vend settlement manager program module, e.g., 132, may coordinate reconciliation between the full ready-to-settle transaction information, cashless vending transactions, and electronic funds transfers communicated from the vending apparatus and other data processing resources, e.g., financial institutions. The fill-and-settle transaction may be generated when a service person or other user refills or refills the vending apparatus, e.g., 104A-N. Generally, at that time, the knowing that the vending apparatus is refilled and full, i.e., the settlement transaction, may be generated to timely indicate the particular situation in which the knowing vending apparatus is relatively full.

In this embodiment, one or more products from the vending apparatus 104A-N may be sold and a cashless transaction may be generated. When vend settlement (reconciliation inventory and money) is performed, the vend settlement manager program module, e.g., 132, may coordinate fill-i-settle transactions with cashless transaction data to determine when the associated vending apparatus is refilled. The vend settlement manager program module, e.g., 132, may also determine which transaction occurred after the refill. In addition, the vend settlement manager program module, such as 132, may determine any fees associated with one or more cashless transactions and/or cashless transaction processing. The vending settlement manager program module, such as 132, may also determine which wireless cash transaction, if any, received an Electronic Funds Transfer (EFT). The resulting transaction data may be transmitted by the vending settlement manager program module, e.g., 132, to an operator server, e.g., 136, or other suitable data processing device, to determine the remaining inventory and collected money, thus settling some or all of the transactions associated with the vending apparatus.

In one embodiment, the vend settlement manager program module, e.g., 132, may receive transaction data from a plurality of data processing devices and/or data routed from the vending apparatus. The transaction data may include, but is not limited to, DEX data, cashless vending transaction data, cash vending transaction data, and electronic funds transfer data (EFT). The vend settlement manager program module, e.g., 132, may process some or all of the transaction data and may communicate some or all of the transaction data to an operator server, e.g., 134, to effect settlement of the associated vending apparatus. The processing of transaction data by the vend settlement manager program module, e.g., 132, may include, but is not limited to, forming cashless transactions, cash transactions, and other types of transactions using, in part, MDB data, DEX data, and/or other data. In this manner, the vend settlement manager program module, e.g., 132, may be operable to process different types of transaction data, convert the data into appropriate data that may be related to the settlement of vends for the associated vending apparatus. The converted data may be modeled into one or more appropriate formats that may be compatible with data that may have been processed by an operations server, such as 134, so that the vend settlement manager program module may convert non-consistent data from various sources into compatible and consistent data structures. The compatible and consistent data structure may be communicated to an operator server, such as 134, to effect settlement of the vends of the associated vending apparatus.

In at least one embodiment, the vend settlement manager program module, e.g., 132, may be executed by the vend settlement server, e.g., 116, which may be operable to perform various tasks to effect vend settlement of associated vending apparatus. In this manner, tasks may be performed that include, but are not limited to, reconciling fill-i.e., settlement transactions, cashless vending transactions, cash vending transactions, cashless transaction data, cash transaction data, refund transactions, reconciling other types of transactions and data, as well as communicating DEX data and/or transaction records formed in part using MDB data and/or DEX data, as well as communicating other types of data that may be needed and/or desired. Additionally, tasks may be performed that include, but are not limited to, processing service alerts, performing operational management of vending equipment, performing customer service functions, and/or processing and/or performing other types of tasks that may be needed and/or desired.

In one embodiment, one or more service alerts may be generated by vending equipment, such as 104A-N or an associated server. Each service alert may indicate that at least one service needs to be associated with the vending apparatus or related server. In this manner, processing service alerts is one example by which the relative proper operation of the vending apparatus or associated server may be monitored. Notification may be provided by way of a service alert when attention is required to a particular vending apparatus or associated server.

Referring to FIG. 4, an example of a method of settling a transaction associated with a vending apparatus is shown. The method 400 may be implemented using some or all of the system components shown in FIG. 1, and in this example, some of the system components of the system 100 are used.

The method 400 begins at block 402.

At block 402, transaction data associated with one or more transactions is received. In this embodiment, the transaction data may be sent to or otherwise collected or received by a vend settlement manager program module, such as 132. The transaction data may include, but is not limited to, data associated with a fill-to-settle transaction, cashless vending transactions, cash vending transactions, cashless transaction data, cash transaction data, refund transactions, service alerts, MDB data, DEX data, and other similar types of transactions and data associated with vending apparatus transactions or consumers.

Block 402 is followed by block 404, wherein the vend settlement manager program module reconciles the received transaction data. In this embodiment, the vend settlement manager program module, e.g., 132, may reconcile or otherwise process the received transaction data. Data processing may include, but is not limited to, reconciling transactions, converting transaction data to a different format, collating data, settling accounts, and/or formatting data as desired.

Block 404 is followed by block 406, wherein at least one result can be generated and transmitted based at least in part on the reconciled transaction data. In this embodiment, the vend settlement manager program module, e.g., 132, may generate and transmit at least one result based at least in part on the reconciled or otherwise processed transaction data. The results may include, but are not limited to, result data, transactions, and transaction data. The vend settlement manager program module, e.g., 132, may communicate at least one of the results to an operator server, e.g., 134, and/or other data processing resource or server, where vend settlement of the associated vending apparatus may occur. The method 400 ends after block 406.

The capabilities of various embodiments of the present invention can be implemented in software, firmware, hardware or some combination thereof.

As one example, one or more aspects of embodiments of the present invention can be implemented in an article of manufacture (e.g., one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code means for providing and facilitating the capabilities of embodiments of the present invention. The article of manufacture can be included as a part of a computer system or sold separately.

Additionally, at least one program storage device readable by a machine tangibly embodying at least one program of instructions executable by the machine to perform the capabilities that the embodiments of the present invention can provide.

The flow diagrams depicted herein are just examples. Many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from its scope. For example, elements may be performed in a differing order, or elements may be added, deleted or modified. All of these variations are intended to be part of the claimed invention.

While various embodiments of the invention have been described, it will be understood by those skilled in the art that various modifications and improvements may be made both now and in the future which fall within the scope of the following claims. These claims should be construed to maintain the proper protection for the embodiments of the invention described herein.

Claims (21)

1. A system for vending network data management, comprising:

a vend settlement manager program module operable to:

receiving a plurality of electronic transactions from at least one transaction-type device;

reconciling the plurality of electronic transactions; and

the response data for each electronic transaction is communicated to at least one server.

2. The system of claim 1, wherein the vend settlement manager program module is further operable to:

receiving a respective unique identifier for each electronic transaction of the plurality of electronic transactions; and

transmitting respective transaction data for each of the plurality of electronic transactions based at least in part on the respective unique identifier.

3. The system of claim 1, wherein the electronic transaction comprises at least one of: fill-up, i.e., settlement transactions, cash-vending transactions, cashless transaction data, cash transaction data, refund transactions, DEX data, transaction records, MDB data, and any combination thereof.

4. The system of claim 1, wherein the vend settlement manager program module is further operable to:

electronic transactions from a plurality of transaction type devices are converted into at least one appropriate data processing format.

5. The system of claim 1, wherein the vend settlement manager program module is further operable to:

data associated with some or all of the electronic transactions is sent to at least one operator server, wherein settlement of vends for the electronic transactions may be facilitated.

6. The system of claim 1, wherein the vend settlement manager program module is further operable to:

at least one fee associated with a cash or cashless type of electronic transaction is determined.

7. The system of claim 1, wherein the vend settlement manager program module is further operable to:

at least one service alert is generated based at least in part on data associated with an electronic transaction of a particular transaction type device or vending apparatus.

8. A method for providing vending network data management, the method comprising:

receiving a plurality of electronic transactions from at least one transaction-type device;

reconciling the plurality of electronic transactions; and

the response data for each electronic transaction is communicated to at least one server.

9. The method of claim 8, further comprising:

receiving a respective unique identifier for each of the plurality of electronic transactions; and

transmitting respective transaction data for each of the plurality of electronic transactions based at least in part on the respective unique identifier.

10. The method of claim 8, wherein the electronic transaction comprises at least one of: fill-up, i.e., settlement transactions, cashless vending transactions, cash vending transactions, cashless transaction data, cash transaction data, refund transactions, DEX data, transaction records, MDB data, and any combination thereof.

11. The method of claim 8, further comprising:

electronic transactions from a plurality of transaction type devices are converted into at least one appropriate data processing format.

12. The method of claim 8, further comprising:

data associated with some or all electronic transactions is sent to at least one operator server, wherein settlement of vends for the electronic transactions may be facilitated.

13. The method of claim 8, further comprising:

at least one fee associated with a cash or cashless type of electronic transaction is determined.

14. The method of claim 8, further comprising:

at least one service alert is generated based at least in part on data associated with an electronic transaction of a particular transaction type device or vending apparatus.

15. A computer readable medium comprising program instructions operable to:

receiving a plurality of electronic transactions from at least one transaction-type device;

reconciling the plurality of electronic transactions; and

the response data for each electronic transaction is communicated to at least one server.

16. The computer readable medium of claim 15, wherein the program instructions are further operable to:

receiving a respective unique identifier for each of the plurality of electronic transactions; and

transmitting respective transaction data for each of the plurality of electronic transactions based at least in part on the respective tie-out indicia.

17. The computer-readable medium of claim 15, wherein the electronic transaction comprises at least one of: fill-up, i.e., settlement transactions, cashless vending transactions, cash vending transactions, cashless transaction data, cash transaction data, refund transactions, DEX data, transaction records, MDB data, and any combination thereof.

18. The computer readable medium of claim 15, wherein the program instructions are further operable to:

electronic transactions from a plurality of transaction type devices are converted into at least one appropriate data processing format.

19. The computer readable medium of claim 15, wherein the program instructions are further operable to:

data associated with some or all electronic transactions is sent to at least one operator server, wherein settlement of vends for the electronic transactions may be facilitated.

20. The computer readable medium of claim 15, wherein the program instructions are further operable to:

at least one fee associated with a cash or cashless type of electronic transaction is determined.

21. The computer readable medium of claim 15, wherein the program instructions are further operable to:

at least one service alert is generated based at least in part on data associated with an electronic transaction of a particular transaction type device or vending apparatus.