# Patent

## Title
Transferring digital receipt data to mobile devices

## Abstract

The present invention extends to methods, systems, and computer program products for transferring digital receipt data to mobile devices. A point-of-sale (“POS”) system generates digital receipt data as part of a sales transaction. The point-of-sale (“POS”) system and a mobile device, possibly also along with a receipt data server, interoperate with one another to transfer digital receipt data generated to the mobile device. In some embodiments, the point-of-sale (“POS”) system transfers digital receipt data for a sales transaction to the receipt data server. An identifier, such as, for example, an application identifier or transaction identifier, is stored along with the digital receipt data to match the digital receipt data with the mobile device. The mobile device subsequently uses the identifier to access the digital receipt data from the receipt data server. In other embodiments, the point-of-sale (“POS”) system transfers digital receipt data directly to the mobile device.

## Background
RELATED APPLICATIONS
This application is related to U.S. application Ser. No. 13/556,011, filed Jul. 23, 2012 and U.S. application Ser. No. 13/556,056, filed Jul. 23, 2012.
BACKGROUND
Field of the Invention
This invention relates generally to the field of electronic sales transactions, and, more particularly, to transferring digital receipts to mobile devices.
Related Art
In a variety of transactions, consumers or buyers of goods or services typically receive receipts from their respective merchants or service providers as proof of existence of conducted transactions. Generally, receipts are issued by merchants and service providers for a number of reasons including, for example, regulatory or tax reasons and convenience purposes. A receipt provides information about a corresponding transaction for the purpose of providing all participants with a trace or record of the transaction. Receipts can later be used by a consumer for various purposes including, for example, proving participation in a transaction for tax reporting purpose, product returns, use as a claim ticket for a further transaction, provisioning warranties, etc. For in-store purchases, consumers generally obtain a paper receipt at the point-of-sale. Accordingly, consumers frequently retain paper receipts for some amount of time after a transaction. Saved paper receipts can then be used by consumers later to return merchandise, to track expenses for budgeting purposes, or to substantiate tax, reimbursement, or warranty claims, among many other uses.
However, these later uses may be distant in time relative to when a transaction occurred. Weeks, months, or even years may pass before a consumer needs to use an old paper receipt. For example, one consumer may need to submit all receipts associated with business expenses to an employer at the end of a month for reimbursement purposes. Another consumer may need to submit all receipts related to charitable contributions to her accountant at the end of the tax year for income deduction purposes. In either of these instances, or the countless other instances in which a consumer has a need to retrieve old paper receipts, the consumer must rely on their past diligence in storing and organizing the paper receipts (and making sure the paper receipts do not become worn or damaged) in order to achieve her intended goal. For the average consumer, it is a time-consuming endeavor to locate the particular paper receipt(s) needed, and it may in fact prove to be impossible. Paper receipts are easily misplaced and difficult to organize—not only do they come in all different shapes and sizes, but they may only be categorized at the highest level in one manner, for example, by date or by subject matter.
Indeed, the high-level categorization initially chosen for organizational purposes may not be altered without a great deal of work, which is problematic when a particular paper receipt would be located most easily through a category other than the one chosen. As such, typically methods of saving paper receipts have at least a number of limitations. At best, these limitations cost consumers their time and sanity as they wade through old receipts to find what they need; at worst, they cost consumers much more—the inability to obtain a refund, a tax deduction, a reimbursement, etc.
Although receipts for telephone or online purchases may be delivered to a customer in digital format, this does not relieve, and in some environments may compound, organizational difficulties associated with paper receipts. For example, for telephone or online purchases, consumers may wait for a paper receipt to arrive in the mail, or may obtain an electronic receipt that they print to generate a paper receipt. These paper receipts must then be retained and organized with other paper receipts. Further, some consumers may never print the electronic receipts they obtain, and instead retain those receipts in electronic form, for example, in their email accounts. As such, consumers may store old receipts in one or more locations, both physical and electronic, and the stored receipts are only as organized as the particular consumer's efforts dictate.
Another drawback to the use of paper receipts is that, unlike credit/debit transactions, individual cash transactions are not stored in conventional point-of-sale (“POS”) systems. Customers can read their own credit/debit transaction data at the websites of their banks or credit card companies. However, since the cash transactions are not stored, the paper receipts are the only record of these cash transactions.
A conventional POS system typically includes a POS terminal, one or more peripheral devices (display monitor, receipt printer, barcode scanner, weigh scale, electronic signature pad) and a payment processor with pin pad (for credit and debit cards). The data for sales transactions is usually stored in a storage device of the POS terminal, which may be uploaded to one of the remote transaction authorization server or another remote server of the credit/debit card companies. Although POS systems are well equipped for merchants to monitor and collect transaction data from the POS system, the ability of the customer to input or extract useful information from the POS system is typically limited to pinpad interactions (entering tip amounts, obtaining additional cash back, etc.), and obtaining printed receipts, the format and content of which has been pre-determined by the merchant.
Further, POS systems are typically sold with a proprietary on-board software system that may be specific to the merchant's business. The merchant is able to make minor programming adjustments to add discount codes and other special offers, but has limited ability to add functionality to the POS system.



BRIEF DESCRIPTION OF THE DRAWINGS
The specific features, aspects and advantages of the present invention will become better understood with regard to the following description and accompanying drawings where:
FIG. 1 illustrates an example block diagram of a computing device.
FIG. 2 illustrates an example computer architecture that facilitates transferring digital receipt data to mobile devices.
FIGS. 3A and 3B illustrates a flow chart of an example method for transferring digital receipt data to mobile devices.
FIG. 4 illustrates another example computer architecture that facilitates transferring digital receipt data to mobile devices.
FIGS. 5A and 5B illustrates another flow chart of an example method for transferring digital receipt data to mobile devices.
FIG. 6 illustrates a further example computer architecture that facilitates transferring digital receipt data to mobile devices.
FIG. 7 illustrates further flow chart of an example method for transferring digital receipt data to mobile devices.
FIG. 8 illustrates an example schematic block diagram of a point-of-sale (“POS”) system.
FIG. 9 illustrates an example schematic block diagram of a network of point-of-sale (“POS”) systems.



DETAILED DESCRIPTION
The present invention extends to methods, systems, and computer program products for transferring digital receipt data to mobile devices. In the following description of the present invention, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention is may be practiced. It is understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.
Embodiments of the present invention may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments within the scope of the present invention also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments of the invention can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media.
Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.
A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (devices) (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a “NIC”), and then eventually transferred to computer system RAM and/or to less volatile computer storage media (devices) at a computer system. RAM can also include solid state drives (SSDs or PCIx based real time memory tiered Storage, such as FusionIO). Thus, it should be understood that computer storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.
Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
Those skilled in the art will appreciate that the invention may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, various storage devices, and the like. The invention may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.
Embodiments of the invention can also be implemented in cloud computing environments. In this description and the following claims, “cloud computing” is defined as a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned via virtualization and released with minimal management effort or service provider interaction, and then scaled accordingly. A cloud model can be composed of various characteristics (e.g., on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, etc.), service models (e.g., Software as a Service (“SaaS”), Platform as a Service (“PaaS”), Infrastructure as a Service (“IaaS”), and deployment models (e.g., private cloud, community cloud, public cloud, hybrid cloud, etc.).
It is further noted that, where feasible, functions described herein can be performed in one or more of: hardware, software, firmware, digital components, or analog components. For example, one or more application specific integrated circuits (“ASICs”) can be programmed to carry out one or more of the systems and procedures described herein. Certain terms are used throughout the following description and Claims to refer to particular system components. As one skilled in the art will appreciate, components may be referred to by different names. This document does not intend to distinguish between components that differ in name, but not function
In general, embodiments of the invention are directed to transferring digital receipt data to mobile devices. A point-of-sale (“POS”) system generates digital receipt data as part of a sales transaction. The point-of-sale (“POS”) system and a mobile device, possibly also along with a receipt data server, interoperate with one another to transfer digital receipt data generated to the mobile device.
In some embodiments, the point-of-sale (“POS”) system transfers digital receipt data for a sales transaction to the receipt data server. An identifier, such as, for example, an application identifier or transaction identifier, is stored along with the digital receipt data to match the digital receipt data with the mobile device. The mobile device subsequently uses the identifier to access the digital receipt data from the receipt data server. In other embodiments, the point-of-sale (“POS”) system transfers digital receipt data directly to the mobile device.
FIG. 1 illustrates an example block diagram of a computing device 100. Computing device 100 can be used to perform various procedures, such as those discussed herein. Computing device 100 can function as a server, a client, or any other computing entity. Computing device 100 can perform various communication and data transfer functions as described herein and can execute one or more application programs, such as the application programs described herein. Computing device 100 can be any of a wide variety of computing devices, such as a mobile telephone or other mobile device, a desktop computer, a notebook computer, a server computer, a handheld computer, tablet computer and the like.
Computing device 100 includes one or more processor(s) 102, one or more memory device(s) 104, one or more interface(s) 106, one or more mass storage device(s) 108, one or more Input/Output (I/O) device(s) 110, and a display device 130 all of which are coupled to a bus 112. Processor(s) 102 include one or more processors or controllers that execute instructions stored in memory device(s) 104 and/or mass storage device(s) 108. Processor(s) 102 may also include various types of computer-readable media, such as cache memory.
Memory device(s) 104 include various computer-readable media, such as volatile memory (e.g., random access memory (“RAM”) 114) and/or nonvolatile memory (e.g., read-only memory (“ROM”) 116). Memory device(s) 104 may also include rewritable ROM, such as Flash memory.
Mass storage device(s) 108 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid state memory (e.g., Flash memory), and so forth. As shown in FIG. 1, a particular mass storage device is a hard disk drive 124. Various drives may also be included in mass storage device(s) 108 to enable reading from and/or writing to the various computer readable media. Mass storage device(s) 108 include removable media 126 and/or non-removable media.
I/O device(s) 110 include various devices that allow data and/or other information to be input to or retrieved from computing device 100. Example I/O device(s) 110 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, cameras, lenses, CCDs or other image capture devices, and the like.
Display device 130 includes any type of device capable of displaying information to one or more users of computing device 100. Examples of display device 130 include a monitor, display terminal, video projection device, and the like.
Interface(s) 106 include various interfaces that allow computing device 100 to interact with other systems, devices, or computing environments. Example interface(s) 106 can include any number of different network interfaces 120, such as interfaces to personal area networks (“PANs”), local area networks (“LANs”), wide area networks (“WANs”), wireless networks (e.g., near field communication (“NFC”), Bluetooth, Wi-Fi, etc. networks), and the Internet. Other interfaces include user interface 118 and peripheral device interface 122.
Bus 112 allows processor(s) 102, memory device(s) 104, interface(s) 106, mass storage device(s) 108, and I/O device(s) 110 to communicate with one another, as well as other devices or components coupled to bus 112. Bus 112 represents one or more of several types of bus structures, such as a system bus, PCI bus, IEEE 1394 bus, USB bus, and so forth.
FIG. 2 illustrates an example computer architecture 200 that facilitates transferring digital receipt data to mobile devices. Referring to FIG. 2, computer architecture 200 includes mobile device 201, POS system 211, and receipt data server 221. Each of the depicted components can be connected to one another over (or be part of) a network, such as, for example, a PAN, a LAN, a WAN, and even the Internet. Accordingly, each of the depicted components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., near field communication (“NFC”) payloads, Bluetooth packets, Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the network.
As depicted, mobile device 201 (e.g., a smartphone) further includes receipt management application 202, network adapter 203, and NFC module 204. Generally, receipt management application 202 is configured to manage receipt data for a user of mobile device 201. Receipt management application 202 can be used to perform receipt related operations, such as, for example, sorting receipt data, searching receipt data, itemizing receipt data, etc. in response to user-entered commands. Receipt management application 202 is also associated with application ID 231. Application ID 231 can be a unique ID used to distinguish receipt management application 202 (and thus also mobile device 201) from other receipt management applications (and thus also from other mobile devices).
Network adapter 203 can be a wireless network adapter for connecting mobile device 201 with a wireless network, such as, for example, Wi-Fi and/or a cellular network (e.g., CDMA, GSM, iDen, etc.) that facilitates a further connection to network 251 (e.g., the Internet). NFC module 204 is configured to connect mobile device 201 with other systems and devices using Near Field Communication.
As depicted, POS system 211 includes transaction processor 212, network adapter 213, NFC module 214, and I/O peripherals 216. POS 211 can be physically located at a checkout lane in a store. Generally, transaction processor 212 is configured to manage sales transactions for POS system 211. Transaction processor 212 can receive input from I/O peripherals 216 to open a sales transaction, collect digital receipt data (e.g., date, time, item, and cost data, etc.) for a sales transaction, and close a sales transaction. Digital receipt data for an item (e.g. item description and item cost) can be retrieved from an item database in response to scanning a barcode on (or otherwise identifying) the item. I/O peripherals 216 can include one or more of: a monitor (e.g., a cashier-facing monitor), one or more input devices (e.g., scanners, keyboards, scales, or the like), one or more payment devices (e.g., cash drawers, card readers, etc.) for receiving or returning payments, and one or more output devices (e.g., customer-facing display or monitor, receipt printer, etc.).
Network adapter 213 can be a wired or wireless network adapter for connecting POS system 211 with a network, such as, for example, a Wi-Fi and/or wired Ethernet network, that facilitates a further connection to network 251 (e.g., the Internet). NFC module 214 is configured to connect POS system 211 with other systems and devices using Near Field Communication.
Generally, receipt data server 221 is configured to receive and store receipt data from POS system 211 (and possibly also one or more other POS systems). Receipt data server 221 is also connected to network 251. In some embodiments, receipt data server 221 is part of a backend system that receives receipt data from a plurality of POS systems distributed throughout different geographic locations. The plurality of POS systems and the backend system can be part of a commonly owned and/or controlled corporate network infrastructure.
FIGS. 3A and 3B illustrate a flow chart 300 of an example method for transferring digital receipt data to mobile devices. Method 300 will be described with respect to the components and data of computer architecture 200.
Method 300 includes opening a sales transaction associated with a mobile device (301). A user of mobile device 201 can make one or more items they wish to purchase available to a cashier. The cashier can then process (e.g., scan) each of the items as part of a checkout procedure. Alternately, the user of mobile device 201 can process (e.g., scan) each of the one or more items himself or herself as part of a self-checkout procedure. As part of the checkout process, a cashier or the user of mobile device 201 can enter commands at I/O peripherals 216 to start a new sales transaction. In response, I/O peripherals 216 can send open transaction message 232 to transaction processor 212. Transaction processor 212 can receive open transaction message 232 from I/O peripherals 216. In response to open transaction message 232, transaction processor 212 can open a sales transaction to process the one or more items for the user of mobile device 201.
Method 300 includes in response to opening the sales transaction, collecting digital receipt data for the sales transaction (302). For example, in response to opening the sales transaction, transaction processor 212 can collect digital receipt data 233 for each of the one or more items that is processed (e.g., scanned) during the sales transaction.
Method 300 includes transmitting a Near Field Communication (NFC) tag payload within a Radio Frequency (RF) field range of the point-of-sale (POS) system, the Near Field Communication (NFC) tag payload encoding a unique customer identifier, the unique customer identifier corresponding to a receipt management application resident at the mobile device (303). For example, NFC module 204 can access application ID 231 from receipt management application 202. NFC module 204 can transmit NFC tag payload 238 within a RF field range of POS system 211. NFC tag payload 238 encodes application ID 231, a unique ID for receipt management application 202.
Method 300 includes receiving the Near Field Communication (NFC) tag payload from the mobile device (304). For example, NFC module 214 can receive NFC tag payload 238 from NFC module 204. NFC module 214 can decode application ID 231 from NFC tag payload 238 and send application ID 231 to transaction processor 212.
In these embodiments, mobile device 201 can function as an NFC tag and POS system 211 can function as an NFC reader. Mobile device 201 can be moved within a sufficient proximity of POS system 211 so that POS system 211 can receive NFC tag payload 238.
Method 300 includes closing the sales transaction (305). For example, when each of the one or more items has been processed (e.g., scanned), a cashier or the user of mobile device 201 can enter commands at I/O peripherals 216 to end the sales transaction. In response, I/O peripherals 216 can send close transaction message 234 to transaction processor 212. Transaction processor 212 can receive close transaction message 234 from I/O peripherals 216. In response to close transaction message 234, transaction processor 212 can close the sales transaction processing the one or more items for the user of mobile device 201.
Method 300 includes, in response to closing the sales transaction, using the unique customer identifier to mark the digital receipt data for the sales transaction as corresponding to the receipt management application (306). For example, transaction processor 212 can use application ID 231 to mark digital receipt data 233 as corresponding to receipt management application 202.
Method 300 includes, also in response to closing the sales transaction, sending the marked digital receipt data for the sales transaction to a receipt data server for subsequent retrieval by the mobile device (307). For example, network adapter 213 can access digital receipt data 233 marked with application ID 231 from transaction processor 212. Network adapter 213 can send digital receipt data 233 marked with application ID 231 to receipt data server 221.
Receipt data server can store digital receipt data 233 and retain the marking with application ID 231.
Method 300 includes receiving a push notification, the push notification notifying the mobile device that digital receipt data for the sales transaction is available at the receipt data server (308). For example, receipt data server 221 can send push notification 237 to mobile device 201. Alternately, POS system 211 can send push notification 237 to mobile device 201. Mobile device 201 can receive push notification 237 from receipt data server 221 (or alternately from POS system 211). Push notification 237 notifies mobile device 201 that digital receipt data 233 is available at receipt data server 221.
Method 300 includes requesting digital receipt data corresponding to the unique customer identifier from the receipt data server (309). For example, network adapter 203 can send request 239, containing application ID 231, to receipt data server 221. Request 239 requests any digital receipt data for receipt management application 202. Receipt data server 221 can receive request 239. Receipt data server 221 can use application ID 231 to match request 239 to digital receipt data 233. Receipt data server 221 can return digital receipt data 233 to mobile device 201.
Method 300 includes receiving the digital receipt data for the sales transaction from the receipt data server in response to the request (310). For example, network adapter 203 can receive digital receipt data 233 from data receipt data server 221. Method 300 includes delivering the electronic receipt data for the sales transaction to the receipt management application (act 311). For example, network adapter 203 can deliver digital receipt data 233 to receipt management application 202. Receipt management application 202 can then process digital receipt data 233 to sort digital receipt data 233, search digital receipt data 233, itemize digital receipt data 233, etc. in response to user-entered commands.
FIG. 4 illustrates an example computer architecture 400 that facilitates transferring digital receipt data to mobile devices. Referring to FIG. 4, computer architecture 400 includes mobile device 401, POS system 411, and receipt data server 421. Each of the depicted components can be connected to one another over (or be part of) a network, such as, for example, a PAN, a LAN, a WAN, and even the Internet. Accordingly, each of the depicted components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., near field communication (“NFC”) payloads, Bluetooth packets, Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the network.
As depicted, mobile device 401 (e.g., a smartphone) further includes receipt management application 402, network adapter 403, and NFC module 404. Generally, receipt management application 402 is configured to manage receipt data for a user of mobile device 401. Receipt management application 402 can be used to perform receipt related operations, such as, for example, sorting receipt data, searching receipt data, itemizing receipt data, etc. in response to user-entered commands. However, receipt management application 402 is not associated with a unique ID. As such, receipt management application 402 may be incapable of unique identification relative to other receipt management applications interacting with POS system 411 or requesting digital receipt data from receipt data server 421.
Network adapter 403 can be a wireless network adapter for connecting mobile device 401 with a wireless network, such as, for example, Wi-Fi and/or a cellular network (e.g., CDMA, GSM, iDen, etc.) that facilitates a further connection to network 451 (e.g., the Internet). NFC module 404 is configured to connect mobile device 401 with other systems and devices using Near Field Communication.
As depicted, POS system 411 includes transaction processor 412, network adapter 413, NFC module 414, and I/O peripherals 416. POS 411 can be physically located at a checkout lane in a store. Generally, transaction processor 412 is configured to manage sales transactions for POS 411. Transaction processor 412 can receive input from I/O peripherals 416 to open a sales transaction, collect digital receipt data (e.g., date, time, item, and cost data, etc.) for a sales transaction, and close a sales transaction. Digital receipt data for an item (e.g. item description and item cost) can be retrieved from an item database in response to scanning a barcode on (or otherwise identifying) the item. I/O peripherals 416 can include one or more of: a monitor (e.g., a cashier-facing monitor), one or more input devices (e.g., scanners, keyboards, scales, or the like), one or more payment devices (e.g., cash drawers, card readers, etc.) for receiving or returning payments, and one or more output devices (e.g., customer-facing display or monitor, receipt printer, etc.).
Network adapter 413 can be a wired or wireless network adapter for connecting mobile phone 401 with a network, such as, for example, a Wi-Fi and/or wired Ethernet network, that facilitates a further connection to network 451 (e.g., the Internet). NFC module 414 is configured to connect POS system 411 with other systems and devices using Near Field Communication.
Generally, receipt data server 421 is configured to receive and store receipt data from POS system 411 (and possibly also one or more other POS systems). Receipt data server 421 is also connected to network 451. In some embodiments, receipt data server 421 is part of a backend system that receives receipt data from a plurality of POS systems distributed throughout different geographic locations. The plurality of POS systems and the backend system can be part of a commonly owned and/or controlled corporate network infrastructure.
FIGS. 5A and 5B illustrate a flow chart of an example method 500 for transferring digital receipt data to mobile devices. Method 500 will be described with respect to the components and data of computer architecture 400.
Method 500 includes beginning a sales transaction associated with a mobile device (501). A user of mobile device 401 can make one or more items they wish to purchase available to a cashier. The cashier can then process (e.g., scan) each of the items as part of a checkout procedure. Alternately, the user of mobile device 401 can process (e.g., scan) each of the one or more items himself or herself as part of a self-checkout procedure. As part of the checkout process, a cashier or the user of mobile device 401 can enter commands at I/O peripherals 416 to start a new sales transaction. In response, I/O peripherals 416 can send open transaction message 432 to transaction processor 412. Transaction processor 412 can receive open transaction message 432 from I/O peripherals 416. In response to open transaction message 432, transaction processor 412 can open a sales transaction to process the one or more items for the user of mobile device 401.
Method 500 includes, in response to opening the sales transaction, collecting digital receipt data for the sales transaction (502). For example, in response to opening the sales transaction, transaction processor 412 can collect digital receipt data 433 for each of the one or more items that is processed (e.g., scanned) during the sales transaction.
Method 500 includes, also in response to opening the sales transaction, formulating a transaction identifier for the sales transaction (503). For example, in response to opening the sales transaction, transaction processor 412 can formulate transaction identifier 413 for the sales transaction. Transaction identifier 431 can be a unique transaction identifier relative to other transactions occurring at POS system 411 and to other transactions at other POS systems in communication with receipt data server 421.
Method 500 includes, also in response to opening the sales transaction, transmitting a Near Field Communication (NFC) tag payload within a Radio Frequency (RF) field range of the mobile device, the Near Field Communication (NFC) tag payload encoding the transaction identifier for the sales transaction (504). For example, in response to opening the sales transaction, NFC module 414 can access transaction ID 431 from transaction processor 412. NFC module 414 can transmit NFC tag payload 438 within a RF field range of mobile device 401. NFC tag payload 438 encodes transaction ID 431, a unique ID for the transaction.
Method 500 includes receiving the Near Field Communication (NFC) tag payload from the point-of-sale (POS) system (505). For example, NFC module 404 can receive NFC tag payload 438 from NFC module 414. NFC module 404 can decode transaction ID 431 from NFC tag payload 438 and send transaction ID 431 to receipt management application 402.
In these embodiments, mobile device 401 can function as an NFC reader and POS system 411 can function as an NFC tag. Mobile device 401 can be moved within a sufficient proximity of POS system 411 so that mobile device 401 can receive NFC tag payload 438.
Method 500 includes closing the sales transaction at the point-of-sale (POS) system (506). For example, when each of the one or more items has been processed (e.g., scanned), a cashier or the user of mobile device 401 can enter commands at I/O peripherals 416 to end the sales transaction. In response, I/O peripherals 416 can send close transaction message 434 to transaction processor 412. Transaction processor 412 can receive close transaction message 434 from I/O peripherals 416. In response to close transaction message 434, transaction processor 412 can close the sales transaction processing the one or more items for the user of mobile device 401.
Method 500 includes, in response to closing the sales transaction, using the transaction identifier to mark the digital receipt data for the sales transaction (507). For example, transaction processor 412 can use transaction ID 431 to mark digital receipt data 433 as corresponding to the transaction with mobile device 401.
Method 500 includes, also in response to closing the sales transaction, sending the marked digital receipt data for the sales transaction to a receipt data server for subsequent retrieval by the mobile device (508). For example, network adapter 413 can access digital receipt data 433 marked with transaction ID 431 from transaction processor 412. Network adapter 413 can send digital receipt data 433 marked with transaction ID 431 to receipt data server 421.
Method 500 includes receiving the push notification, the push notification notifying the mobile device that digital receipt data for the sales transaction is available at the receipt data server (509). For example, receipt data server 421 can send push notification 437 to mobile device 401. Alternately, POS system 411 can send push notification 437 to mobile device 401. Mobile device 401 can receive push notification 437 from receipt data server 421 (or alternately from POS system 411). Push notification 437 notifies mobile device 401 that digital receipt data 433 is available at receipt data server 421
Method 500 includes requesting digital receipt data corresponding to the transaction identifier from the receipt data server (510). For example, network adapter 403 can send request 439, containing transaction ID 431, to receipt data server 421. Request 439 requests any digital receipt data corresponding to the transaction associated with transaction ID 431. Receipt data server 421 can receive request 439. Receipt data server 421 can use transaction ID 431 to match request 439 to digital receipt data 433. Receipt data server 421 can return digital receipt data 433 to mobile device 401.
Method 500 includes receiving the digital receipt data for the sales transaction from the receipt data server in response to the request (511). For example, network adapter 403 can receive digital receipt data 433 from data receipt data server 421. Method 500 includes delivering the electronic receipt data for the sales transaction to a receipt management application at the mobile device (512). For example, network adapter 403 can deliver digital receipt data 433 to receipt management application 402. Receipt management application 402 can then process digital receipt data 433 to sort digital receipt data 433, search digital receipt data 433, itemize digital receipt data 433, etc. in response to user-entered commands.
FIG. 6 illustrates an example computer architecture 600 that facilitates transferring digital receipt data to mobile devices. Referring to FIG. 6, computer architecture 600 includes mobile device 601 and POS system 611. Each of the depicted components can be connected to one another over (or be part of) a network, such as, for example, a Personal Area Network (“PAN”), a Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even the Internet. Accordingly, each of the depicted components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., near field communication (NFC) payloads, Bluetooth packets, Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the network.
As depicted, mobile device 601 (e.g., a smartphone) further includes receipt management application 602, communication module 603, and NFC module 604. Generally, receipt management application 602 is configured to manage receipt data for a user of mobile device 601. Receipt management application 602 can be used to perform receipt related operations, such as, for example, sorting receipt data, searching receipt data, itemizing receipt data, etc. in response to user-entered commands. Receipt management application 602 is also associated with application ID 631. Application ID 631 can be a unique ID used to distinguish receipt management application 602 (and thus also mobile device 601) from other receipt management applications (and thus also from other mobile devices).
Communication module 603 can be a wireless network adapter for connecting mobile device 601 with a local wireless network, such as, for example, using Bluetooth and/or Wi-Fi. NFC module 604 is configured to connect mobile device 601 with other systems and devices using Near Field Communication.
As depicted, POS system 611 includes transaction processor 612, communication module 613, NFC module 614, and I/O peripherals 616. POS 611 can be physically located at a checkout lane in a store. Generally, transaction processor 612 is configured to manage sales transactions for POS 611. Transaction processor 612 can receive input from I/O peripherals 616 to open a sales transaction, collect digital receipt data (e.g., date, time, item, and cost data, etc.) for a sales transaction, and close a sales transaction. Digital receipt data for an item (e.g. item description and item cost) can be retrieved from an item database in response to scanning a barcode on (or otherwise identifying) the item. I/O peripherals 616 can include one or more of: a monitor (e.g., a cashier-facing monitor), one or more input devices (e.g., scanners, keyboards, scales, or the like), one or more payment devices (e.g., cash drawers, card readers, etc.) for receiving or returning payments, and one or more output devices (e.g., customer-facing display or monitor, receipt printer, etc.).
Communication module 613 can be a wireless network adapter for connecting POS system 611 with a local wireless network, such as, for example, using Bluetooth and/or Wi-Fi. NFC module 604 is configured to connect mobile device 601 with other systems and devices using Near Field Communication.
FIG. 7 illustrates a flow chart of an example method 700 for transferring digital receipt data to mobile devices. Method 700 will be described with respect to the components and data of computer architecture 600.
Method 700 includes opening a sales transaction associated with a mobile device (701). A user of mobile device 601 can make one or more items they wish to purchase available to a cashier. The cashier can then process (e.g., scan) each of the items as part of a checkout procedure. Alternately, the user of mobile device 601 can process (e.g., scan) each of the one or more items himself or herself as part of a self-checkout procedure. As part of the checkout process, a cashier or the user of mobile device 601 can enter commands at I/O peripherals 616 to open a new sales transaction. In response, I/O peripherals 616 can send open transaction message 632 to transaction processor 612. Transaction processor 612 can receive open transaction message 632 from I/O peripherals 616. In response to open transaction message 632, transaction processor 612 can open a sales transaction to process the one or more items for the user of mobile device 601.
Method 700 includes, in response to opening the sales transaction, collecting digital receipt data for the sales transaction (702). For example, in response to opening the sales transaction, transaction processor 612 can collect digital receipt data 633 for each of the one or more items that is processed (e.g., scanned) during the sales transaction.
Method 700 includes transmitting a Near Field Communication (NFC) tag payload within a generated Radio Frequency (RF) field surrounding the mobile device, the tag payload encoding a unique customer identifier, the unique customer identifier corresponding to a receipt management application resident at the mobile device (703). For example, NFC module 604 can access application ID 631 from receipt management application 602. NFC module 604 can transmit NFC tag payload 638 within a RF field range of POS system 611. NFC tag payload 638 encodes application ID 631, a unique ID for receipt management application 602.
Method 700 includes receiving the Near Field Communication (NFC) tag payload from the mobile device (704). For example, NFC module 614 can receive NFC tag payload 638 from NFC module 604. NFC module 614 can decode application ID 631 from NFC tag payload 638 and send application ID 631 to transaction processor 612.
Method 700 includes establishing a communication pairing between the point-of-sale (POS) system and the mobile device upon acceptance of the unique customer identifier (705). Method 700 includes establishing the communication pairing between the mobile device and the point-of-sale (POS) system, establishment of the communication pairing indicative of the point-of-sale (POS) system accepting the unique customer identifier (706). For example, upon POS system 611 accepting application ID 631 from mobile device 601, mobile device 601 and POS system 611 can establish communication pairing 652.
In some embodiments, communication pairing 652 is an NFC peer-to-peer data connection. For example, NFC module 604 and NFC module 614 can establish an NFC peer-to-peer data connection between mobile device 601 and POS system 611. In other embodiments, communication pairing 652 is a different longer range wireless communication protocol pairing, such as, Bluetooth or Wi-Fi. For example, based on provided functionality, communication module 603 and communication module 613 can establish a Bluetooth or a Wi-Fi connection between mobile device 601 and POS system 611.
Method 700 includes closing the sales transaction at the point-of-sale (POS) system (707). For example, when each of the one or more items has been processed (e.g., scanned), a cashier or the user of mobile device 601 can enter commands at I/O peripherals 616 to end the sales transaction. In response, I/O peripherals 616 can send close transaction message 634 to transaction processor 612. Transaction processor 612 can receive close transaction message 634 from I/O peripherals 616. In response to close transaction message 634, transaction processor 612 can close the sales transaction processing the one or more items for the user of mobile device 601.
Method 700 includes in response to closing the sales transaction, sending the collected digital receipt data to the mobile device over the established communication pairing (708). For example, in response to closing the sales transaction, POS system 611 can send digital receipt data 633 to mobile device 601 over communication pairing 652. When communication pairing 652 is a NFC peer-to-peer data connection, NFC module 614 can send digital receipt data 633 to NFC module 604. When communications pairing 652 is a Bluetooth or a Wi-Fi connection, communication module 613 can send digital receipt data 633 to communication module 603.
Method 700 includes receiving the collected digital receipt data for the sales transaction from the Point-Of-Sale (POS) system over the communication pairing (709). For example, mobile device 601 can receive digital receipt data 633 from POS system 611 over communication pairing 652. When communication pairing 652 is a NFC peer-to-peer data connection, NFC module 604 can receive digital receipt data 633 from NFC module 614. When communications pairing 652 is a Bluetooth or a Wi-Fi connection, communication module 603 can receive digital receipt data 633 from communication module 613.
Establishing a communication pairing for a different longer range wireless communication protocol can allow a user of mobile device 601 to move mobile device 601 further away from POS system 601 physically and still receive digital receipt data 633. For example, mobile device 601 can function as an NFC tag. POS system 611 can function as an NFC reader. Mobile device 601 can be moved within a sufficient proximity of POS system 611 so that POS system 611 can receive NFC tag payload 638. After NFC tag payload 638 is received, the user may desire to put mobile device 601 back in a pocket, purse, etc. NFC communication can be used to bootstrap a Bluetooth or Wi-Fi connection. Establishing communication pairing 652 as a Bluetooth or Wi-Fi connection can permit the user to “put away” a mobile device and remain within communication range of POS system 611.
Method 700 includes delivering the collected digital receipt data to the receipt management application (710). For example, as appropriate, NFC module 604 or communication module 603 can deliver digital receipt data 633 to receipt management application 602. Receipt management application 602 can then process digital receipt data 633 to sort digital receipt data 633, search digital receipt data 633, itemize digital receipt data 633, etc. in response to user-entered commands.
FIG. 8 illustrates an example schematic block diagram of a point-of-sale (POS) system 800. In some embodiments, the hardware, software, or hardware and software of POS system 800 may be configured to implement one or more methods in accordance with the present invention. For example, POS system 800 may be manufactured, programmed, modified, or upgraded to support transferring digital receipt data to mobile devices. Any of POS systems 211, 411, and 611 can be a POS system similar to POS system 800.
POS system 800 can include various components. In some embodiments, POS system 800 includes a central or primary computer 812, a monitor 814 (e.g., a cashier-facing monitor 814), one or more input devices 816 (e.g., scanners 816a, keyboards 816b, scales, or the like), one or more payment devices 818 (e.g., cash drawers 818a, card readers 818b) for receiving or returning payments, one or more output devices 820 (e.g., customer-facing display 820a or monitor 820a, receipt printer 820b), or the like or combinations or sub-combinations thereof, and NFC module 822, such as, for example, an NFC dongle.
Computer 812 may form the backbone of POS system 800. Other components 816, 818, 820, 822 forming part of a POS system 800 can communicate with computer 812. Input devices 816 and certain payment devices 818 can feed data and commands to computer 812 for processing or implementation. For example, scanner 816a can pass data communicating the identity of one or more items to be purchased, returned, or the like to a computer 812. Similarly, card reader 818b can pass payment information to computer 812.
On the other hand, output devices 820 and certain payment devices 818 can follow or implement commands issued by computer 812. For example, cash drawer 818a may open in accordance with the commands of computer 812. Similarly, customer-facing display 820a and receipt printer 820b can display or output data or information as instructed by computer 812.
In some embodiments, in addition to handling consumer transactions (e.g., purchases, returns), POS system 800 can provide or support certain “back office” functionality. For example, POS system 800 can provide or support inventory control, purchasing, receiving and transferring products, or the like. POS system 800 can also store sales and customer information for reporting purposes, marketing purposes, receivables management, trend analysis, cost analysis, price analysis, profit analysis, or the like. If desired or necessary, POS system 800 can include an accounting interface to pass certain information to one or more in-house or independent accounting applications.
In some embodiments, POS system 800 operates substantially independently, as a stand-alone unit. Alternately, POS system 800 may be one of several POS systems 800 forming the front line of a larger system. FIG. 9 illustrates an example schematic block diagram of a network 900 of point-of-sale (POS) systems 800. For example, multiple POS systems 800 may operate at a particular location 922 (e.g., within a retail, brick-and-mortar store). In such embodiments, the various POS systems 800 may be interconnected via LAN 924. LAN 924 may also connect the POS systems 800 to a local server 926.
Local server 926 can support the operation of the associated POS systems 800. For example, a server 926 may provide a central repository from which certain data needed by the associated POS systems 800 may be stored, indexed, accessed, or the like. Server 926 can serve certain software to one or more POS systems 800. In certain embodiments, a POS system 800 can offload certain tasks, computations, verifications, or the like to server 926.
Alternatively, or in addition thereto, server 926 can support certain back office functionality. For example, server 926 can receive and compile (e.g., within an associated database 928) data from the various associated POS systems 800 to provide or support inventory control, purchasing, receiving and transferring products, or the like. Server 926 can also receive and compile sales and customer information for reporting purposes, marketing purposes, receivables management, trend analysis, cost analysis, price analysis, profit analysis, or the like.
In some embodiments, one or more POS systems 800 and/or servers 926 corresponding to a particular location 922 can communicate with or access one or more remote computers or resources via one or more network devices 930. For example, a network device 930 can enable a POS system 800 to contact outside resources and verify the payment credentials (e.g., credit card information) provided by a customer. A network device 930 can comprise a modem, router, or the like.
In selected embodiments, POS systems 800 operate within an enterprise-wide system 931 comprising multiple locations 922 (e.g., branches 922 or stores 922). In such embodiments, each location 922 may have one or more POS systems 800, local servers 926, local databases 928, network devices 930, or the like or combinations or sub-combinations thereof connected by a computer network (e.g., a LAN 924). It may be that any of data receipt servers 221, 421, and 621 are included in and/or include the functionality of a local server 926.
Additionally, each such location 922 may be configured to interact with one or more supervisory systems 932. For example, multiple branch locations 922 may report to an associated “headquarters” location or system. It may be that any of data receipt servers 221, 421, and 621 are included in and/or include the functionality of a supervisory system 932.
A supervisory system 932 can include one or more supervisory servers 934, databases 936, workstations 938, network devices 940, or the like or combinations or sub-combinations thereof. The various components of a supervisory system 932 can be interconnected via a computer network (e.g., a LAN 942). In selected embodiments, a supervisory system 932 includes one or more supervisory servers 934 providing a central repository from which certain data needed by the one or more POS systems 800 or local servers 926 may be stored, indexed, accessed, or the like.
Alternatively, or in addition thereto, a supervisory server 934 can receive and compile (e.g., within an associated database 936) data from the various associated POS systems 800 or local servers 926 to provide or support inventory control, purchasing, receiving and transferring products, or the like. A supervisory server 934 may also receive and compile sales and customer information for reporting purposes, marketing purposes, receivables management, trend analysis, cost analysis, price analysis, profit analysis, or the like.
A supervisory system 932 can be connected to one or more associated locations 922 or branches 922 in via any suitable computer network 944 (e.g., WAN 944). For example, in selected embodiments, one or more locations 922 can connect to a supervisor system 932 via the Internet. Communication over such a network 944 can follow any suitable protocol or security scheme. For example, communication may utilize the File Transfer Protocol (FTP), a virtual private network (VPN), intranet, or the like.
Although the components and modules illustrated herein are shown and described in a particular arrangement, the arrangement of components and modules may be altered to process data in a different manner. In other embodiments, one or more additional components or modules may be added to the described systems, and one or more components or modules may be removed from the described systems. Alternate embodiments may combine two or more of the described components or modules into a single component or module.
The foregoing description has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. Further, it should be noted that any or all of the aforementioned alternate embodiments may be used in any combination desired to form additional hybrid embodiments of the invention.
Further, although specific embodiments of the invention have been described and illustrated, the invention is not to be limited to the specific forms or arrangements of parts so described and illustrated. The scope of the invention is to be defined by the claims appended hereto, any future claims submitted here and in different applications, and their equivalents.

## Claims

1. A method for transferring digital receipt data from a computer system of a retailer to a mobile device of a customer of the retailer, the computer system comprising a Point-Of-Sale (POS) terminal including one or more processors and system memory, the POS terminal also including a Near Field Communication (NFC) module, the method comprising:
opening a sales transaction at the POS terminal;
in response to opening the sales transaction:
collecting digital receipt data for the sales transaction;
formulating, by the computer system of the retailer, a transaction identifier for the sales transaction; and
the Near Field Communication (NFC) module transmitting to the mobile device a NFC tag payload within a Radio Frequency (RF) field range of the mobile device, the NFC tag payload encoding the transaction identifier for the sales transaction, wherein the NFC module establishes a first communication pairing between the POS terminal and the mobile device;

closing the sales transaction at the POS terminal; in response to closing the sales transaction:
linking the transaction identifier to the digital receipt data documenting the sales transaction;
storing the digital receipt data in combination with the transaction identifier corresponding thereto within a receipt data server forming part of the computer system for subsequent retrieval by the mobile device; and
establishing a second communication pairing between the POS terminal and the mobile device using the first communication pairing when the mobile device is moved away from the POS terminal outside a range of the NFC module, wherein the second communication pairing is one of Bluetooth or Wi-Fi;

sending a push notification from the receipt data server to the mobile device indicating that the digital receipt data for the sales transaction is available for retrieval from the receipt data server, wherein the push notification is able to be received by the mobile device outside the range of the NFC module;
receiving, by the computer system from the mobile device after the closing, a request containing the transaction identifier and requesting the digital receipt data; and
transmitting the digital receipt data to the mobile device through the second communication pairing.

2. The method of claim 1, wherein the opening the sales transaction at the POS terminal comprises receiving an indication from an I/O peripheral that the sales transaction is to be opened.

3. The method of claim 1, wherein the collecting the digital receipt data for the sales transaction, comprises for each of one or more items included in the sales transaction:
receiving an item identifier from a scanned bar code; and
referring to a product database to access item description data and item cost data for the item.

4. The method of claim 1, wherein the closing the sales transaction at the POS terminal comprises receiving an indication from an I/O peripheral that the sales transaction is to be closed.

5. The method of claim 1, wherein the storing the digital receipt data for the sales transaction within the receipt data server comprises sending the digital receipt data to a local server that stores receipt data for the POS terminal along with one or other more POS terminals co-located with the POS terminal.

6. The method of claim 1, wherein the storing the digital receipt data for the sales transaction within the receipt data server comprises sending the digital receipt data to a supervisory system that stores receipt data for a location of the POS terminal and for one or other locations of POS terminals.

7. A method for a mobile device to receive digital receipt data from a computer system of a retailer, the mobile device including one or more processors and system memory, the mobile device also including a Near Field Communication (NFC) module, the method comprising:
the NFC module receiving a NFC tag payload from a Point-Of-Sale (POS) terminal forming part of the computer system of the retailer, the POS terminal handling a sales transaction associated with the mobile device, the NFC tag payload encoding a transaction identifier generated by the computer system of the retailer for the sales transaction, wherein the NFC module establishes a first communication pairing between the POS terminal and the mobile device;
establishing a second communication pairing between the POS terminal and the mobile device using the first communication pairing when the mobile device is moved away from the POS terminal outside a range of the NFC module, wherein the second communication pairing is one of Bluetooth or Wi-Fi;
sending a push notification from a receipt data server to the mobile device indicating that the digital receipt data for the sales transaction is available for retrieval from the receipt data server, wherein the push notification is able to be received by the mobile device outside the range of the NFC module;
requesting, by the mobile device subsequent to completion of the sales transaction, digital receipt data from the receipt data server forming part of the computer system of the retailer, the computer system of the retailer, the requesting comprising sending a request containing the transaction identifier to the receipt data server; and
receiving, by the mobile device, the digital receipt data for the sales transaction from the receipt data server through the second communication pairing in response to the request.

8. The method of claim 7, wherein the requesting the digital receipt data from the receipt data server comprises requesting the digital receipt data from a local server that stores receipt data for the POS terminal along with one or more other POS terminals co-located with the POS terminal.

9. The method of claim 8, wherein the receiving the digital receipt data for the sales transaction from the receipt data server comprises receiving the digital receipt data for the sales transaction from the local server.

10. The method of claim 7, wherein the requesting the digital receipt data from the receipt data server comprises requesting the digital receipt data from a supervisory system that stores receipt data for a location of the POS terminal and for one or more other locations of POS terminals.

11. The method of claim 10, wherein the receiving the digital receipt data for the sales transaction from the receipt data server comprises receiving the digital receipt data for the sales transaction from the supervisory system.

12. A method for transferring receipt data from a computer system of a retailer to a mobile device of a customer, the method comprising:
initiating, by a point of sale (POS) terminal of the computer system, a sales transaction;
collecting, by the POS terminal, the receipt data for the sales transaction;
generating, by the computer system, a transaction identifier identifying the sales transaction;
establishing, by the POS terminal, a first communication pairing between the POS terminal and the mobile device using a near-field communication (NFC) module of the POS terminal
delivering, by the NFC module, an NFC payload to the mobile device, the NFC payload encoding the transaction identifier;
completing, by the POS terminal, the sales transaction;
associating, by the computer system in memory thereof, the receipt data with the transaction identifier;
establishing, by the POS terminal, a second communication pairing between the POS terminal and the mobile device using the first communication pairing when the mobile device is moved away from the POS terminal outside a range of the NFC module, wherein the second communication pairing is one of Bluetooth or Wi-Fi;
sending, by a receipt data server, a push notification to the mobile device indicating that the receipt data for the sales transaction is available for retrieval from the receipt data server, wherein the push notification is able to be received by the mobile device outside a range of the NFC module;
receiving, by the computer system from the mobile device after the completing, the transaction identifier in a request for the receipt data corresponding to the transaction identifier; and
delivering, by the computer system in response to the request, the receipt data to the mobile device through the second communication pairing.