Processing payment receipts using receipt bank. RU patent 2511622.

FIELD: physics, computer technology.

SUBSTANCE: invention relates to means of processing payment receipts using a receipt bank. Electronic payment receipts created in any type of transaction are delivered to said receipt bank. A customer subscribes to a specific receipt bank which will be used as storage for payment receipts of that customer. The customer has a device which is used to transmit payment information to the reader of the device upon making a purchase, which identifies the receipt bank of the customer. The business enterprise receiving the payment from the customer creates an electronic payment receipt and delivers it to the receipt bank indicated by the device of the customer, or the enterprise can also deliver the payment receipt to a user device which forwards the payment receipt to the receipt bank.

EFFECT: high reliability of electronic transactions.

17 cl, 11 dwg

THE LEVEL OF TECHNOLOGY

Transaction (commercial transaction, such as rent, reservation of rooms in the hotel, charitable donation) is often remembered as a payment receipt. Traditionally, the payment receipt is issued on paper. With the advent of e-Commerce transactions made through the Internet (for example, various purchases through web-site), have generated electronic payment receipt. When a transaction takes place on the Internet, the buyer usually informs the e-mail address as part of the transaction, and electronic payment receipt is sent to this e-mail address.

E-Commerce has gone beyond purchases through the web site. Modern cash registers are often performed with the use of application software. Many items such as airfare, music recordings, made to order sandwiches, etc. are sold through the retail kiosks, who, like modern cash registers, also performed with use of applied programs. The increasing use of computer systems for performance of the functions of retail trade creates the possibility of issuing electronic payment receipts in cases where it has traditionally used a paper receipt.

The problem arising from the issue of electronic payment receipts outside the transaction related to purchase via the website, is that it may not be clear where to deliver a payment receipt. Buyers normally advised e-mail address when performing transactions over the Internet, so it is logical to send a receipt to the buyer via e-mail. However, buyers usually do not report e-mail address, when you perform a transaction in person. Moreover, even if the buyer informs the e-mail address, can be more convenient to give him payment receipt in hand, than to send it to the buyer via e-mail. The practice of sending a receipt by e-mail may be a legacy of the period of the birth of e-Commerce, when sending to the buyer payment receipt via e-mail was the only practical way to deliver electronic payment receipt. Payment receipt can be delivered in other ways that lead to the use of more sophisticated infrastructure, more powerful mobile devices and more advanced communication capabilities.

SUMMARY OF THE INVENTION

Electronic payment receipt may be established on the basis of the transaction, and that the receipt of the payment can be delivered to the Bank receipts. Bank receipts can be created in the form of a cloud server, and payment receipt can be sent to the cloud to be delivered to the Bank receipts. Then the buyer will be able to access their payment receipts through the Bank receipts.

Commercial institution (for example, a retail store, hotel, etc) can be equipped with a component of point of sale (such as a cash register)associated with a reader device. The buyer may have a device that stores the profile for this customer. The profile may include payment information (such as credit card or other account number) and can also include contact information specifying the location of the Bank receipts, which must be sent receipt of the buyer. Reader device can read the profile information of the device of the buyer. The receipt of the payment can be sent to the Bank receipts specified in the customer profile.

Make a payment receipt can be done in different ways. For example, a cash register or another component of point of sale can send payment receipt to the cloud for delivery in particular, the Bank receipt of the buyer. Or reader device can create and/or to send payment receipt in the Bank receipts through the cloud. As another option, the reader device can engage in two-way communication with the device of the buyer and can provide direct delivery receipt in this device. The device can then send the payment receipt to the cloud for delivery to the Bank of receipt of the buyer, leaving at the same time, the device buyer a copy of the payment receipt, which was created during the time of the transaction.

The receipt of the payment can contain any information about the transaction. For example, in certain credit card transactions progressive provided detailed information about the transaction for the credit card issuing Bank, and the availability of these data can be effectively used for the issuance of a very detailed payment receipt to the buyer. Then the buyer can access such a detailed level of information through the Bank receipts.

The present description of the invention is intended for presentation in a simplified form selection of concepts which will set out below in the section "Detailed description". This description of the invention is not intended neither to the definition of key attributes or essential features of the claimed subject matter, nor to use to limit the scope of the claimed subject matter.

BRIEF DESCRIPTION OF DRAWINGS

Figure 1-3 - flowcharts cited as examples of systems in which payment receipt can be created and delivered to the Bank receipts.

Figure 4 - the sequence of the process, cited as an example, in which is made the transaction with the buyer and sent the receipt of the payment in the Bank receipts.

Figure 5 - the sequence of the process, cited as an example, in which is made the transaction is created and the receipt of the payment or part payment receipt.

6-8 sequence of operations in some cited as an example of how to continue the process depicted in figure 5, on the basis of which the component sends the payment slip to the Bank receipts.

Fig.9 - block diagram of some cited as an example of actions that can be performed in respect of the Bank receipt.

Figure 10 is a block diagram is shown as an example of the device.

11 is a block diagram cited as an example of the components that can be used in connection with the implementations described in this description of the subject matter.

DETAILED DESCRIPTION

The receipt of the payment and other types of records of transactions traditionally produced in paper form. With the advent of e-Commerce many payment receipts for transactions online became available in electronic form. When making transactions online, the buyer must inform your e-mail address, so naturally to send a payment receipt for online transaction on the electronic address of the buyer. However, the model collect e-mail addresses of customers and making payment receipts for these e-mail addresses may not be well distributed transactions committed on the Internet. In addition, the hardware and software that are used to support personally produced transaction, usually not suitable for creating a payment receipts and send them by e-mail to customers.

Moreover, the reception on the e-mail receipt, sent to the address of the buyer used for General correspondence, may not be particularly convenient way to receive a receipt. Mailing receipt buyers via e-mail may be a relic preserved from the early epoch of electronic Commerce, and can be used modern technology to deliver a receipt in other ways. The development of the cloud computing model offers the ways in which electronic payment receipts could be sent to the buyer without having to send them by e-mail in the mailbox of the buyer for normal incoming correspondence. For example, the buyer may have a device that can transmit payment information of the buyer in the payment device in a retail setting, such as a restaurant, a music store, a cashier selling tickets etc. The device may be it a mobile phone or a PDA. This device can store the credit card number of the buyer, which will be used for payment and the buyer can pay after this device in front of the reader device. In such a scenario, sending a receipt by e-mail to the address of the buyer for normal incoming correspondence seems awkward and somewhat discordant with the personal nature of the transaction. Described in this description of the subject of the invention provides various mechanisms that could be used to deliver the payment receipts or other records of transactions in various destinations, such as the Bank receipts. The buyer could access their payment receipts through the Bank receipts, and could have access to any level of detailed information about transactions (for example, to a line listing the value of what he bought). Such mechanisms can be applied to produce personally transactions, but can also be used as a delivery method of payment receipts and with regard to transactions on the Internet or other online transactions.

Let us turn now to the drawings. Figure 1 shows an example of the system 100, in which the receipt of the payment can be created and sent to the Bank receipts. The buyer 102 is the buyer who shall enter into the transaction. For example, the buyer 102 can buy a product or service in a retail setting, where the customer is physically located. Can mean any type of product or service. For example, the buyer 102 can buy groceries at the supermarket, video equipment in the electronics store, the music at the reception in the cafe, food, medical services at the doctor's office, etc. Other types of transaction may include the reservation of a hotel room or rent a car donation to charity, etc. these are just examples, although it can be any type of transaction.

The buyer 102 may have or may in any other way be associated with the device 104. The device 104 may contain electronically profile buyer 102. The profile may include a variety of information, which the buyer 102 can use to start a transaction. For example, a device 104 may contain credit card information or other information about account that the buyer 102 uses to pay for the purchase. The device 104 can be on the phone, personal digital organizer, smart card or device of any other type. The device 104 may have components that memorizes the information listed above, and may also have components, which forward the information to the reader device corresponding type. Examples of unit components 104 and examples of information that can contain device 104, shown in figure 10 and will be discussed below in connection with this drawing.

Reader 106 device is a component that is used to read information that passes the device 104. For example, the reader 106 device can read information from devices that meet the requirements of the standard 14443 International organization for standardization (ISO) on the card remote sensing or with devices that use the technology standard near field communication (NFC). In one example, the device 104 is a mobile phone buyer 102, which are equipped with NFC technology, and the buyer 102 "holds" phone at a distance of a few inches from the reader 106 device so that the reader 106 device can read information from the device 104. However, the above are just examples, and the reader 106 device can read from any type of device, using any type of technology or communication mechanism.

Profile information 108 information is recorded by the device 104. Profile information may include the name of the buyer 102, credit card number or any other information. Specific examples of such information are discussed below with reference figure 10. The device 104 passes relevant information 108 reader 106 device.

In the example scenario, the transaction purchase is done through many different components, including the reader 106 device and component 110, point of sale (POS). POS component 110 can be a cash register, a kiosk retail trade, computer or device or any other type that can be used to facilitate the sale. Usually POS component 110 is used for transactions where the buyer is physically present at the place where the transaction, for example, a shop that serves its clients in the office, in a restaurant etc. The script physical presence is opposed to the scenario of electronic purchases through the Internet or another scenario in which remote transaction is carried out through the network. So, figure 1 shows one example, when all the various elements are in the same physical location 160 (dashed). For example, if POS component 110 is a cash register, the items that can be purchased/sold, and prices of these items must be entered in POS component 110. The input can be made via the keyboard, barcode scanner, or any other type of mechanism. If POS component 110 is a kiosk retail POS component can be used to select music, and perhaps to send the selected music plays music system buyer 102. (The device 104 can be reproducing music buyer 102, for example, in the case when the device 104 is an MP3 player or some other device that can play music). In one example, the reader 106 device and POS component 110 are separate components, which are attached to each other. In another example, the reader 106 device built into the POS component 110.

Figure 1 shows the component 110, receiving instructions 111 on items 112, which is bought and sold, and/or on the price 114 on these subjects. Instructions on the items 112 and prices 114 can be taken POS component 114 in any way. (In the example, the "objects" can be goods, services, food and drinks in the restaurant menu or anything else that may be the object of transaction). For example, POS component 110 can be linked to a database that contains a catalog of items available for sale, and prices of these items. Thus, the guidance about the subjects, which are to be sold, can be entered from the keyboard, scanner, touchscreen display, etc., and prices may be found in the database. Or example, when POS component is 110 cash-device, the cashier can enter rates 114 in the cash register. POS component 110 may adopt guidelines on the subject 112 subject to purchase and sale, and/or on the price 114, and all of the above is just examples of how POS component 110 can't take this information.

When POS component 110 completes the transaction, it creates a payment receipt 116. (As discussed below with reference to figure 2 and 3, POS component 110 may also create a partial payment receipt with the addition of payment data reader 106 device on collection of payment from the buyer 102). The receipt of the payment 116 may include, for example, information about the purchased items 152, price (prices) 154 on these items, the total cost 156 purchased items, payment information 158 (for example, how much is paid for the purchase and what is the form of payment), or any other type of information.

The receipt of the payment 116 may be sent to the Bank 118 receipts. Access to the Bank 118 receipts can be accessed through a network, such as the Internet. Moreover, the Bank 118 receipts can be provided through the cloud computing model in which the Bank 118 receipts is a service, reachable through the cloud 120. In the usual sense of the cloud 120 applies to the collection of functions and/or services that are provided by remote devices and software and are delivered through a network. The Bank 118 receipts can accept payment receipt and can perform different actions in relation to the payment receipt 116. Examples of actions that can be performed in relation to the payment receipt 116, are discussed below with reference to the Fig.9.

System component 100 can send payment receipt 116 in the cloud 120 to deliver it to the Bank 118 receipts. (Make a payment receipt via the cloud 120 shown as an example, although the receipt of the payment 116 may also be sent to the Bank 118 receipts so that does not use the cloud 120). The receipt of the payment 116 may be sent to the Bank 118 receipts various components of the system 100. Figure 1 shows an example where POS component 110 sends a payment receipt 116 in the Bank 118 receipts. However, the receipt of the payment 116 may be sent to other system components 100. Figure 2 and 3 are examples in which the receipt of the payment 116 is sent to the Bank 118 receipts other system components 100.

Figure 2 and 3 are examples in which system components are 100 different from POS component 110, used to make a payment receipt from the Bank receipts. (Figure 2 and 3 rooms 100, 102, 104, 106, 108, 110, 111, 112, 114, 116, 118, 120 and 160 refer to the same elements as in figure 1. Figure 2 and 3 of the payment receipt 116 may have the same items, as shown in the example in figure 1, is marked with the numbers 152, 154, 156 and 158, although for ease of presentation these items are not repeated in figure 2 and 3). Figure 2 POS component 110 creates a partial payment receipt 122. Partial payment receipt 122 may include the information contained in receipt 116 figure 1, but no payment information. Payment information may be entered by the reader 106 device to display made by buyer 102 payment after POS component 110 found that it is bought and how much should be paid. Partial payment receipt 122 may be in the form of a receipt omitted billing information, or it can be some other way presents purchased items and the total amount that can then be used by the reader 106 device for creation of receipt in the appropriate form after reception of payment. (Payment receipt can also be created in a different time, for example, to receive payment). Reader 106 device accepts partial receipt 122 on payment and then creates a payment receipt 116. After you create a payment receipt 116 reader 106 device sends a payment receipt 116 in the Bank 118 receipts (possibly through the cloud 120, as in figure 1). (From the point of view of terminology, as partial payment receipt 122, and the receipt of the payment 116 are examples of content that is relevant to the transaction).

Figure 3 POS component 110 also receives/sends a partial payment receipt 122 reader 106 device. Reader 106 device can then add billing information in partial payment receipt 102 to create a payment receipt 116. Reader 106 device can also send payment receipt. 116 in the device 104 of the buyer. The device 104 buyer can be configured to send payment receipt 116 in the Bank 118 receipts (again, possibly through the cloud 120, as figures 1 and 2). Examples of processes that are created and sent payment receipt in these different scenarios, shown in figure 5-8 and discussed below. (Link to partial payment receipt 122 during the discussion of figure 3 is given merely as an example; instead of creating a payment receipt stages, POS component 110 can create full payment receipt).

The parcel receipt 116 in the Bank 118 receipts from various other system components 100 supports a variety of other technology and business model. For example, in some cases, POS component 110 may collect the list of purchased items and calculate the total amount of the sale, but he can't create a complete payment receipt, because it makes no payment information. Moreover, some POS components (for example, some cash registers) use their own proprietary technology and/or closed platform, so it is difficult to modify regard to the software, which should be used to create a receipt in the appropriate format and send this payment receipts to the Bank 118 receipts in the cloud 120. For these reasons, it may be appropriate to send a payment receipt 116 in the Bank 118 receipts reader 106 device or device 104 the buyer, not POS component 110. (Business model, in which readers devices embedded and distributed, can be more measurable improvements to ensure compatibility with appropriate software to create and send a receipt).

On the other hand, in some cases, POS component 110 has access to billing information and can be compatible with the corresponding software to send the payment slip to the Bank receipts. For example, a large retail network of trade can use and manage their own POS system and can provide this POS system, access to a back-end system that collects payments from customers. In this case the POS system can be paired with software to send payment receipt in the Bank 118 receipts, and should have access to your payment information. So in this case, POS component 110 can create a payment receipt 116 and send it to the Bank 118 receipts.

When POS component 110 is not a feature that is used to make a payment receipt from 116 to the Bank 118 receipts, payment receipt may be sent by the reader 106 device or device 104 of the buyer. In scenario 3 the reader 106 device represents a payment receipt 116 device 104 buyer, which then sends a payment receipt 116 in the Bank 118 receipts. In this scenario the device 104 buyer receives payment receipt 116, thereby ensuring the availability payment receipt 116 device 104 buyer during the transaction. The device 104 buyer can then send the payment slip 116 in the Bank 118 receipts when the network communication available for the device 104 of the buyer. Since the buyer 102 can use the device 104 as a normal storage device for personal and business information, it may be convenient for the buyer 102 to have a copy of payment receipt 116 device 104. However, the provision of payment receipt device buyer at the time of committing transactions usually occurs within two communication between reader 106 device and the device 104 user: one to collect relevant information 108 for execution of payment, and the other for receiving payment receipt 116 after this payment receipt 116 will be created. In practice, these two session usually require twice-repeated "for" device 104 102 user before the reader device. If the reader 106 device sends a payment receipt 116 in the Bank 118 receipts (as in scenario 2), second conduct is cancelled. The receipt of the payment 116 may be later transferred from the Bank 118 receipts in the device 104 using regular communication through the network that are available for the device 104. However, in this scenario the buyer 102 may be forced to wait for an appointment slips 116 on payment up until it can be delivered from the Bank 118 receipts, which will require time, for example, if the network is not available for the device of 104 at the time of the transaction.

Figure 4-8 shows the different processes. Before proceeding to the description figure 4-8, note that the block diagram of the sequence of operations is shown in these drawings, describes, as an example, with reference to the components shown in figure 1-3, while these processes can run on any system and not be limited to the script, shown in figure 1-3. In addition, each of the flowchart in figure 4-8 shows an example in which the stages of the process are performed in a certain order, as shown by the lines connecting these stages, however, the various stages shown in these diagrams can be run in any order or in any combination or podrozetniki.

At the stage 502 buyer uses the device to send the relevant information from the device to the reader. For example, customer name, account number, contact information, etc. can be stored on a handheld wireless phone buyer. This information may be transferred to the reader. Transmission may occur with use of any type of data transmission technologies, such as NFC technology, WiFi, Bluetooth, optical bar code, etc.

At the stage 504 reader accepts profile information sent by the device. Then the reader passes relevant information POS component (at the stage 506). For example, the reader can be firmly connected to the POS component and can act as an interface that transmits information between your device and POS component. Thus, if the reader takes profile information from the device of the customer, the reader may provide this information POS component.

At the stage 508 POS component takes profile information. At the stage 510 POS component receives instructions on the items purchased by the buyer, the price that must be paid, or other sales data. For example, POS component can be a cash register, which receives instructions on the items that are to be procured through the bar-code scanner, and finds prices for these items in the database. Or a cash register can receive the total amount that must be paid (as may occur in the restaurant, where the cashier enters the amount of the final draft at the cash register). In another example POS component can be a kiosk that sells musical recordings, air tickets or anything else, and in this case, the kiosk can receive guidance on purchased items directly from the buyer during the transaction. The above are some examples of how POS component can accept the guidance on purchased items, their prices and/or other sales data, although this information may be taken any other way.

At the stage 512 POS component creates a payment receipt or partial payment receipt with respect to the transaction. As noted above, depending on the situation, which has the POS component, this POS component can create a complete payment receipt for the transaction. Or it may to create a partial payment receipt containing some information to be used in the receipts for payment (partial payment receipt may, for example, contain information which is used in payment receipt, with the exception of the payment of information collected through reader device).

The process depicted in figure 5, may last for 6, 7 or 8, depending on how the payment receipt shall be delivered to the Bank receipts.

Figure 6 shows an example of a stage, which can be performed if the payment receipt shall be sent to the Bank receipts from POS component. Since the receipt of the payment was created POS component on the stage 602 payment receipt simply transferred from POS component in the Bank receipts in the cloud.

Figure 7 shows an example of the steps that can be performed if the payment receipt must be sent from the reader device in the Bank receipts. At the stage 702 partial payment receipt is created POS component that is transmitted over the reader device. At the stage 704 reader device takes partial payment receipt from POS component. At the stage 706 reader device adds billing information and/or other information in partial payment receipt, to create a complete payment receipt. At the stage 708 reader device transmits the payment slip to the Bank receipts in the cloud. The stages in figure 7 can be performed using POS component and reader devices as specified, but can also be performed using other and/or additional components, such as a receipt printer can be connected to one or more of the above components. The printer payment receipts can be printed on paper with a payment receipt, and may also be able to send a payment receipt to the cloud (regardless of prints whether it hard copies of these receipts). Moreover, a separate device can make payment receipts to the cloud regardless of whether this device is also a print device on paper.

On Fig provides examples of steps that can be performed if the payment receipt must be sent from the device of the buyer (for example, from the phone customer) to the Bank receipts. At the stage 802 POS component 110 passes partial payment receipt reader 106 device. At the stage 804 reader takes partial payment receipt. At the stage 806 reader device adds billing information and/or other information in partial payment receipt, to create a complete payment receipt. At the stage 808 reader device transmits payment receipt in the device of the buyer. At the stage 810 device 104 buyer receives a payment receipt. At the stage 812 device buyer can remember a copy of payment receipt in its own memory or storage device. At the stage 814 device buyer transfers the payment receipt to the Bank receipts in the cloud. To send a payment receipt from the buyer to the Bank receipts can be used by any mechanism. For example, if the device buyer is in the phone, then the receipt of the payment can be transmitted using different technologies that exist for the transmission of information in phone or from the phone, for example, 3G 816, WiFi 818, the standard GSM with increased speed data (EDGE 820), short message service (SMS), or any other mechanism.

The Bank 116 receipts can be a repository that stores receipt of the buyer 102. (Bank 116 receipts and buyer 102 shown in figures 1-3). Can be implemented various actions to establish the Bank receipts for the buyer and/or use a payment receipt from the Bank. Figure 9 shows some examples of actions 900, which may be made in respect of the Bank receipt.

One of the actions that can be performed, is the agreement of the provider with a particular buyer to act as a Bank receipts for the buyer (phase 902). For example, an independent online service provider may offer the Bank receipts as a cloud service to which you may subscribe to the buyer. Then the buyer can sign up for the service, then the service provider must agree to maintain the Bank receipt of the buyer. The provider may (on stage 904), provide the buyer contact information (such as e-mail address, instant messaging (IM), the uniform resource locator (URL), phone number, SMS ID, a random string of data, which the Bank associated with a particular buyer, but that does not respond the transcript for the General public, for example, for people who distribute spam, and the like), which the buyer can use to direct to the Bank payment receipt. This contact information is received by the purchaser from the provider of the Bank receipts, can be saved in the device 104 buyer (as shown in figures 1-3). This contact information can serve as a form of identity of the buyer that may be imposed or otherwise connected with payment receipt; contact information may identify the customer in the sense that the buyer may be associated with a specific contact information, which is used to make a payment receipts to the Bank of receipt of the buyer. (However, other types of contact information can be included in the payment slip).

Although the Bank receipts described above as a service to a third party, the buyer can provide your own Bank receipts, for example, running the Bank related receipts software on your private network-connected computer so that the receipts for payment can be accepted and run on your own computer buyer.

Another action that can be performed, is the message to the buyer of data based on payment receipt (phase 912). The extracted facts and/or conclusions are examples of data that can be based on a payment receipt. Themselves payment receipt are examples of such data. For example, the provider of the Bank receipts may have software of some type that displays the extracted facts and/or conclusions in the form of an information panel (or the other way represents or transmits these extracted facts and/or conclusions person). The software may allow the provider to conduct surveys on certain types of facts and conclusions (for example, "what is the most popular song was bought in, Seattle in the last month people aged 18 to 24 years?" or "what the restaurant is very popular among the employees of XYZ?").

Another action that can be performed, is the issue of commercial proposals based on the extracted facts and/or conclusions (phase 914). For example, if a buyer purchased item at a specific store, then that buyer may be sent coupon or discount as an incentive to loyalty to this store. Or, if the purchase of the buyer reflect his interest in skiing, the coupon can be sent to the buyer to visit the ski shop that will be happy to deal with that buyer.

As noted above, the device 104 buyer (see Fig.1-3) can be stored, and may be able to transfer, various relevant information about the buyer. Figure 10 shows an example of a device 104 buyer with different cited as an example of profile information 108 and components that can be used to store and/or transmit this information.

The device 104 buyer may be, for example, in the phone, pocket PC, smart card or any other type of device. The device 104 can have a storage component, such as flash memory, persistent storage device, volatile memory, disk, etc. The device 104 can also be connected component 1004 that the device 104 can use to log in one-way or two-way communication with external to the device 104 world. For example, the coherent component 1004 can include wired or wireless interface, serial or parallel port, antenna, or any other type of cohesive component (components), either in the singular or in combination with each other. The device 104 can also contain CPU 1006 that the device 104 uses to execute commands. Commands can be saved in the memory component 1002 and/or accepted via the communication component 1004.

Profile information 108 can be saved in the memory component 1002. Figure 10 shows examples of various types of information that can be included in the profile information 108. Specific information shown in figure 10, is given as an example, but relevant information 108 can contain any type of information. Moreover, when the device 104 reports relevant information 108 reported information may include all relevant information that the device 104 stores for a buyer, or may be some subset of this information (or convolution information, such as a hash).

Profile information 108 may include the name 1008 buyer, contact information 1010 and information about 1012 payment account. The name may be represented as a text string (for example, "John A. Smith"). Contact information 1010 may include any type of contact information, such as room 1014 phone (for example, the phone number of the device 104, if the device 104 works as a phone), IM address 1016, e-mail address 1018, ID 1019 buyer in the Bank receipt or any other type of contact information. One or more fragments contact information can identify locations that you will be sent a payment receipt from the buyer. For example, if the customer subscribes to the service of the Bank receipts and this service informs the buyer that the place you will be sent a payment slip for example, e-mail address (or IM address, SMS, address, URL, etc), then this is the place can be entered in the contact information 1010. In one example, the location to which to send payment receipt, identified contact information 1010, may be a place different from the mailbox a buyer for normal use, which the buyer uses for receiving mail. (It may happen that correspondence will be randomly sent to the Bank of receipts; the fact that such correspondence can be directed to the Bank receipts, makes the Bank receipts for such communications, but does not make the Bank receipts in regular mailbox for incoming correspondence buyer).

Computer 1100 includes one or more processors 1102 and one or more components 1104 storing data. The processor(s) are usually microprocessors, such that present in desktop or portable computer, a server, a handheld computer or computing device of another type. Component(s) 1104 storing data are components that can save the data for a short or long time. Examples of components 1104 storing data include hard disks, removable drives (including optical and magnetic disks), volatile and non-volatile random access memory (RAM), permanent memory (ROM), flash memory, magnetic tapes, etc. Components of storing data are examples of computer-readable media. Computer 1100 may contain or may be associated with the device 1112 display, which can be a monitor on a cathode ray tube (CRT), liquid crystal display (LCD) or monitor any other type.

The software can be remembered in the component (components) 1104 storing data and can run on one or more processors 1102. An example of such software is software 1106 for the processing of payment receipts, which may implement some or all of the functionality described above in connection with figure 1-10, although it can be used software of any type. Software 1106 can be implemented, for example, through one or more components that can be components in a distributed system, separate files, private functions, separate lines of code, etc. Personal computer where the program is stored on the hard disk that is loaded into RAM and executed on the processor (CPU) of the computer is a typical representative of the scenario depicted on 11, although described here the subject of the invention is not limited to these examples.

This subject matter can be implemented as software that is stored in one or more components 1104 storage of data and can be performed on one or more processors 1102. In another example, the subject matter can be implemented as software has the command to execute one or more actions of the way in which commands are remembered on one or more machine-readable media. Commands to perform actions can be stored in one format or can be distributed in many media, so that commands may appear together on one or more machine-readable carriers regardless of whether all commands on the same media.

In one example of computing the computer 1100 communication can be associated with one or more other devices through the network 1108. Computer 1110, which can be similar in structure to the computer 1100, is an example of a device that can be connected to the computer 1100, although you can also connect other types of devices.

Although the subject matter was described using the language-specific structural characteristics and/or methodological action, it should be clear that the subject-matter of the invention, as defined in the attached claims, not necessarily limited to specific characteristics or actions described above. On the contrary, the specific characteristics and actions described above are given as examples of implementation of the claims.

1. The way to ensure payment receipt containing: enter using the buyer in the transaction sales point at which the specified customer physically present at the place where the transaction occurs, and this transaction does not go through the commercial the system, which facilitates remote transactions through the network; reception from the device, which runs the specified buyer, profile information, which is saved to the specified device and which includes contact information identifying the place where should be sent to the specified payment receipt via e-mail address, instant messaging (IM), the uniform resource locator (URL), a phone number or identifier of the short message service (SMS), and the specified profile information is taken reader device that communicates with the specified device and communications connected with a component of sales and which is separate from the specified component of the point of sales; creation of the indicated receipt on the basis of the specified transaction through the creation, in the specified component of the point of sales, partial payment receipts, which does not include the amount paid by the purchaser for the transaction, and does not include the payment form, used for the specified transaction, and by passing the specified partial payment receipt to the specified reader device with the specified reader the device creates the specified payment receipt from the specified partial payment receipt by the fact that the reader device adds the specified amount paid and the specified form of payment specified in partial payment receipt; and initiation make specified payments receipts through the network to the Bank receipt, identified the specified contact information, and the Bank receipt is remote from the specified location in which the specified transaction.

2. The method according to claim 1 in which the specified profile information is received by the specified reader devices, and in which the specified initiation contains: the transmission of such payment receipt from the specified component of the sales point at the specified Bank receipts without the transfer of this receipt at the specified reader device.

3. The method according to claim 1 in which the specified initiation contains: the transfer of the indicated receipt in the Bank receipts from the specified reader device.

4. The method according to claim 1, further comprising: the transmission of such payment receipt from the specified reader device at the specified device, and this initiation contains: the transfer of the indicated receipt in the Bank receipts from the specified device.

5. The method according to claim 4, additionally contains: save a copy of the indicated receipt in the given device.

6. The method according to claim 1, wherein said the Bank receipts is implemented as a service in the cloud and in which the specified initiation contains: the making of the specified payment receipt specified in the cloud.

7. The method of claim 6, additionally contains: reception of the specified payment receipt from the specified device from the specified clouds.

8. The method according to claim 1, wherein said the buyer has the relationship on the basis of a subscription to use the specified Bank receipts and which specified the buyer receives the specified contact information as part of the formation of relations on a subscription basis.

9. The method according to claim 1, additionally contain: identification, on the basis of a receipt of the specified buyer in the specified Bank receipts, the first of the goods or the first services that you are interested specified by the buyer; and identification, on the basis of a receipt of the specified buyer in the specified Bank receipts and on the basis of the payment receipts other buyers in the specified Bank receipts, the level of popularity of the second goods or other services.

10. The method of claim 9, additionally contains: provision specified buyer coupon for the first goods or the first service.

16. The system of claim 11, and this system identifies, on the basis of a receipt of the specified buyer in the specified Bank receipts, the first item or the first service that you are interested specified by the buyer, and with this system identifies, on the basis payment receipts specified buyer in the specified Bank receipts and based payment receipts other buyers in the specified Bank receipts, the level of popularity of the second goods or other services.

17. The system under article 16, and this system provides the specified buyer coupon on the first item or the first service.