Method for processing payments and issuing electronic receipts via near-field communications

Abstract

A computing device and method for issuing electronic receipts. Once transaction information is received, it may be sent to a transfer rail. A unique transaction identifier may be generated using a hash function applied to the transaction information, and / or using date and time information, and / or a unique device identifier. A Uniform Resource Locator (URL) may be generated based at least in part on the unique transaction identifier and / or the plurality of receipt elements. A confirmation of successful completion of the transfer card transaction may be received from the transfer rail. The URL may be sent to an NFC tag controller.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 477,690, filed December 29, 2022, entitled "Method for processing payments and issuing electronic receipts via near-field communication," PCT Patent Application No. PCT / KR2022 / 014622, filed September 29, 2022, entitled "Method for issuing electronic receipts," Korean Patent Application No. 10-2022-0037255, filed March 25, 2022, entitled "Method for issuing electronic receipts," and Korean Patent Application No. 10-2022-0003963, filed March 25, 2022, entitled "Method for issuing electronic receipts," the entire contents of which are incorporated herein by reference. This application is also a continuation-in-part of PCT patent application number PCT / KR2022 / 014622, entitled "Method for issuing electronic receipts," filed on September 29, 2022, and claims priority to Korean patent application number 10-2022-0037255, entitled "Method for issuing electronic receipts," filed on March 25, 2022, and Korean patent application number 10-2022-0003963, entitled "Method for issuing electronic receipts," filed on January 11, 2022.

[0002] Exemplary embodiments relate to providing electronic receipts (electronic receipts or invoices), for example, providing electronic receipts at the point of sale and using near field communication (NFC) technology. [Background technology]

[0003] When a consumer completes a transaction related to the purchase of a good or the use of a service, the consumer receives a receipt. In conventional systems, point-of-sale (POS) terminals instantly issue paper receipts, and in the future, electronic receipts may be provided to consumers. Disadvantages of paper receipts include the risk of personal information leakage, challenges in efficient receipt management, and the cost of producing printed receipts. Electronic receipts are generally preferred because they guarantee personal information, are easy to store and manage, are inexpensive to produce, and are environmentally friendly. Efficient computing devices and methods for providing electronic receipts in a timely manner are desirable. In conventional systems, providing electronic receipts in a timely manner may require the user device to be "ready" to display the electronic receipt. For example, a merchant may be required to pre-install an application, activate the user device's camera to scan a QR code, or exchange an email address or phone number with the electronic receipt provider. These circumstances make it difficult to issue electronic receipts in a timely manner. For example, a merchant may have a user device on their person, but the required application may not be installed on the user device. This may occur, for example, when the user device is new or when the merchant is unfamiliar with their user device. Existing receipt and payment systems may require registration of the user device in order to obtain an electronic receipt. This registration may include providing personal information such as an email address, telephone number, payment instrument number, account information, etc. As a result, there is a need for computing devices and methods that provide electronic receipts at the time of a transaction without requiring personal information or prior registration.

[0004] Providing an electronic receipt in a timely manner may also require an internet connection by the point-of-sale terminal at the transaction location, which may not be available in many cases. For example, many transactions occur in subway terminals, on airplanes, during network outages, and other situations where internet connectivity is unavailable. As a result, there is also a need for computing devices and methods that provide an electronic receipt at the time of a transaction even in the absence of a web connection.

[0005] summary The examples described herein can provide a computing device and method for issuing an electronic receipt so that a merchant can immediately receive the electronic receipt, which may be received, for example, at a user device.

[0006] The examples described herein may enable a computing device to generate electronic receipts even in the absence of a web connection.

[0007] Examples described herein allow a merchant to receive and view a corresponding electronic receipt using a web browser application immediately after a transaction has occurred. Examples described herein allow a merchant to receive and view a corresponding electronic receipt on a user device immediately after a transaction has occurred.

[0008] Conventionally, issuing an electronic receipt requires a consumer to install a specific application on their smartphone or log in. However, since the electronic receipt according to some example embodiments can be viewed in the form of a web page via a browser, consumers can receive the electronic receipt without having to pre-install a separate application, sign up for a website, or log in to a website. Summary of the Invention [Means for solving the problem]

[0009] An example embodiment is a computing device comprising a communications module, a processor, and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the processor to receive transaction information, the transaction information including a plurality of receipt elements including date information and time information, corresponding to a transaction including one or more purchases and payments; transmit the transaction information to a transfer rail; generate a unique transaction identifier using a hash function applied to the transaction information and / or using the date information and time information and / or using a unique device identifier; generate a uniform resource locator (URL) including the unique transaction identifier; receive from the transfer rail confirmation of successful completion of the transfer card transaction corresponding to the transaction information; and transmit the URL to an NFC tag controller.

[0010] In example embodiments of any of the above computing devices, the URL further includes at least some of a plurality of receipt elements, including the name of the transactor, the date of the transaction, one or more identification information of the purchase, or the total amount paid.

[0011] In an example embodiment of any of the above computing devices, the processor further determines that an internet connection is not present at the computing device, and the transmitting includes transmitting a URL to the user device via the NFC tag controller, the URL including at least a portion of the plurality of receipt elements such that the user device can generate a receipt for the transaction by parsing the URL without accessing the URL on the internet.

[0012] In an example embodiment of any of the above computing devices, sending includes sending the URL to the user device via the NFC tag controller, wherein an NFC Data Exchange Format (NDEF) message includes the URL as a payload.

[0013] In any example embodiment of the computing device described above, the computing device is a PIN Transaction Service Point of Interaction (PTS POI) device, and the unique device identifier is a unique device identifier of the PTS POI device.

[0014] An example embodiment of any of the above computing devices further causes the processor to determine that no internet connection exists at the computing device before receiving confirmation of successful completion of the transfer card transaction.

[0015] In an example embodiment of any of the above computing devices, the processor, prior to receiving confirmation of successful completion of the transfer card transaction corresponding to the transaction information, further causes the processor to transmit, via the communications module, the transaction information and a URL to the server, the URL identifying a web resource corresponding to a receipt for the transaction.

[0016] In any example embodiment of the above computing device, the processor, before transmitting the transaction information to the transfer rail, further receives transfer card data from a card reader (CR), the CR device including an NFC tag controller and transmitting the transfer card data to the transfer rail, and the unique device identifier is that of the CR device.

[0017] In an example embodiment of any of the above computing devices, the computing device further includes an NFC tag controller, and further causes the processor to generate, via the NFC tag controller, an NDEF message including the URL as a payload, and emit, via the NFC tag controller, an NFC signal corresponding to the NDEF message.

[0018] In an example embodiment of any of the above computing devices, the computing device further has an NFC tag reader, and before generating the URL, the processor further receives transfer card data via the NFC tag reader and transmits the transfer card data to the transfer rail, and the URL further includes a unique device identifier, the unique device identifier being that of the computing device.

[0019] In an example embodiment of any of the above computing devices, the computing device is a contactless PIN entry on a commercial off-the-shelf (CPoC) device, a software-based PIN entry on a commercial off-the-shelf device, or a mobile payment on a commercial off-the-shelf (MPoC) device.

[0020] Another example embodiment is a computing device comprising a communications module, a processor, and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the processor to receive transaction information including a plurality of receipt elements corresponding to a transaction including one or more purchases and payments, transmit the transaction information to a transfer rail, determine that an internet connection does not exist, and upon determining that an internet connection does not exist, generate a uniform resource locator (URL) including at least a portion of the plurality of receipt elements, including a transactor name, a transaction date, identification information of one or more purchases, or a total payment amount, and send an NFC Data Exchange Format (NDEF) message including the URL as a payload to a user device via an NFC tag controller, wherein the URL is formatted such that the user device can parse the URL and generate a receipt for the transaction without accessing the URL on the internet.

[0021] In an example embodiment of any of the above computing devices, the processor is further caused to determine that an internet connection exists and to transmit, via the communications module, a URL identifying a web resource corresponding to the transaction information and a second receipt for the transaction to the server.

[0022] Another example embodiment is a user device having a processor and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the user device to receive a uniform resource locator (URL) identifying a web resource corresponding to a transaction as a string, parse the string into a plurality of components, determine an association between at least two of the plurality of components and respective receipt element identifiers, and generate a second receipt including at least two of the respective receipt element identifiers.

[0023] In any example embodiment of the user device described above, the user device further causes the second receipt to be stored in the first location.

[0024] In any example embodiment of the user device described above, the user device further causes a web resource corresponding to a first receipt of the transaction identified by the URL to be accessed and the first receipt to be stored in a first location.

[0025] In an example embodiment of any of the above user devices, the user device receives a selection of desired receipt element identifiers before generating the second receipt, and at least two of the respective receipt element identifiers in the second receipt correspond to the selection of desired receipt element identifiers.

[0026] In any example embodiment of the user device described above, the selection of the desired receipt element identifier is received via a graphical user interface.

[0027] In any example embodiment of the user device described above, the URL includes a unique transaction identifier and at least the name of the transactor, the date of the transaction, one or more identifications of the purchase, or the total amount paid.

[0028] In any of the example embodiments of the user device described above, the unique transaction identifier is generated using a hash function applied to the transaction information, and / or using date and time information associated with the transaction, and / or using the unique device identifier.

[0029] Another example embodiment is a computer-implemented method including: receiving transaction information, the transaction information including a plurality of receipt elements including date and time information, corresponding to a transaction including one or more purchases and payments; transmitting the transaction information to a transfer rail; generating a unique transaction identifier using a hash function applied to the transaction information and / or using the date and time information associated with the transaction and / or using a unique device identifier; generating a uniform resource locator (URL) including the unique transaction identifier and receipt elements including at least a transactor name, a transaction date, identification information for one or more purchases, or a total payment amount; receiving from the transfer rail confirmation of successful completion of the transfer card transaction corresponding to the transaction information; and transmitting the URL to an NFC tag controller.

[0030] In any example embodiment of the computer-implemented method described above, before receiving confirmation of successful completion of the transfer card transaction corresponding to the transaction information, the method further includes sending the transaction information and a URL to the server, the URL identifying a web resource corresponding to a receipt for the transaction.

[0031] In any example embodiment of the computer-implemented method described above, before transmitting the transaction information to the transfer rail, the method further includes receiving transfer card data from a card reader (CR) device including an NFC tag controller, and transmitting the transfer card data, the unique device identifier of which is that of the CR device, to the transfer rail.

[0032] In any example embodiment of the computer-implemented method described above, the computer-implemented method further includes generating, via the NFC tag controller, an NFC Data Exchange Format (NDEF) message that includes the URL as a payload, and emitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message.

[0033] In any example embodiment of the computer-implemented method described above, before generating the URL, the method further includes transferring the card data via an NFC tag reader and sending the transferred card data to a transfer rail.

[0034] Another example embodiment is a non-transitory computer-readable medium comprising instructions that, when executed by a processor, cause the processor to receive transaction information, the transaction including a plurality of receipt elements including date and time information, corresponding to a transaction including one or more purchases and payments; transmit the transaction information to a transfer rail; generate a unique transaction identifier using a hash function applied to the transaction information and / or using the date and time information associated with the transaction and / or using a unique device identifier; generate a uniform resource locator (URL) including the unique transaction identifier and receipt elements including at least a transactor name, a transaction date, identification information of one or more purchases, or a total payment amount; receive from the transfer rail confirmation of successful completion of the transfer card transaction corresponding to the transaction information; and transmit the URL to an NFC tag controller.

[0035] Another example embodiment is a non-transitory computer-readable medium that, when executed by a processor, causes the processor to receive a uniform resource locator (URL) as a string, the URL identifying a web resource corresponding to a transaction, parse the string into a plurality of components, determine an association between at least two of the plurality of components and a respective receipt element identifier, and generate a second receipt including at least two of the respective receipt element identifiers.

[0036] Another example embodiment is a computer-implemented method that includes receiving a uniform resource locator (URL) identifying a web resource corresponding to a transaction as a string, parsing the string into a plurality of components, determining an association between at least two of the plurality of components and respective receipt element identifiers, and generating a second receipt that includes at least two of the respective receipt element identifiers.

[0037] Another example embodiment is a computing device comprising an NFC tag controller, a communications module, a processor, and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the processor to receive, via the communications module, transaction information corresponding to a transaction including one or more purchases and payments, the transaction information including a plurality of receipt elements including date information and time information; generate a unique transaction identifier using a hash function applied to the transaction information, and / or using the date information and time information, and / or using a unique device identifier; generate a URL including the unique transaction identifier; send the transaction information and the URL to a server; generate, via the NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and issue, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, the URL identifying a web resource on the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information; and upon receiving the NFC signal, the user device immediately displays the receipt via a web page or application page corresponding to the URL without requiring an email address, a text message, or the execution of a pre-loaded or pre-installed application.

[0038] Another example embodiment is a computer-implemented method including: receiving transaction information corresponding to a transaction including one or more purchases and payments, the transaction information including a plurality of receipt elements including date information and time information; generating a unique transaction identifier using a hash function applied to the transaction information, and / or using the date information and time information, and / or using a unique device identifier; generating a URL including the unique transaction identifier; transmitting the transaction information and the URL to a server; generating, via an NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and issuing, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, the URL identifying a web resource on the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information;

[0039] Another example embodiment is a non-transitory computer-readable medium that, when executed by a processor, causes the processor to receive, via a communications module, transaction information corresponding to a transaction including one or more purchases and payments, the transaction information including a plurality of receipt elements including date information and time information; generate a unique transaction identifier using a hash function applied to the transaction information, and / or using the date information and time information, and / or using a unique device identifier; generate a URL including the unique transaction identifier; send the transaction information and the URL to a server; generate, via an NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and emit, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, the URL identifying a web resource on the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information; and upon receiving the NFC signal, the user device immediately displays the receipt through a web page or application page corresponding to the URL without requiring an email address, a text message, or the execution of a pre-loaded or pre-installed application. [Brief explanation of the drawings]

[0040] Exemplary embodiments are described in detail below with reference to the following drawings:

[0041] [Figure 1] FIG. 1 is a schematic diagram illustrating an electronic receipt issuing computer system according to an example embodiment.

[0042] [Figure 2] 2 is a block diagram illustrating an example of the internal configuration of the electronic receipt generator shown in FIG. 1 according to an example embodiment.

[0043] [Figure 3] 2 is a block diagram illustrating an example of the internal configuration of the server shown in FIG. 1 according to an example embodiment.

[0044] [Figure 4] 2 is a block diagram illustrating an example of the internal configuration of the user device shown in FIG. 1 according to an example embodiment.

[0045] [Figure 5] FIG. 1 is a schematic diagram illustrating an example of an electronic receipting computing system, according to an example embodiment.

[0046] [Figure 6] 1 is a flowchart of an exemplary method for issuing an electronic receipt, according to an example embodiment.

[0047] [Figure 7] FIG. 1 illustrates an example display of an electronic receipt on a user device, according to an example embodiment.

[0048] [Figure 8] 1 is a flowchart of an exemplary method for issuing an electronic receipt, according to an example embodiment.

[0049] [Figure 9] FIG. 1 illustrates an exemplary display of a pending process on a user device, according to an example embodiment.

[0050] [Figure 10] FIG. 1 is a schematic diagram illustrating components of an electronic receipting computing system, according to an example embodiment.

[0051] [Figure 11] 1 is a flowchart of an exemplary method for generating an electronic receipt, according to an example embodiment.

[0052] [Figure 12] FIG. 1 is a schematic diagram illustrating components of an electronic receipting computing system, according to an example embodiment.

[0053] [Figure 13]1 is a flowchart of an exemplary method for generating an electronic receipt, according to an example embodiment.

[0054] [Figure 14] FIG. 1 is a schematic diagram illustrating components of an electronic receipting computing system, according to an example embodiment.

[0055] [Figure 15] 10 is a flowchart of an exemplary method for generating a second electronic receipt, according to an example embodiment.

[0056] [Figure 16] 10A-10C illustrate exemplary display screens of a receipt management user interface, according to an example embodiment.

[0057] [Figure 17] FIG. 15 illustrates an exemplary display screen 1500 of a second electronic receipt, according to an example embodiment.

[0058] In the drawings, like reference numbers may be used to denote like elements and features. DETAILED DESCRIPTION OF THE INVENTION

[0059] At least some example embodiments include a method for generating electronic receipts (electronic receipts or receipts) for users to conveniently view on their smartphones, so businesses can use the method.

[0060] Since the exemplary embodiments can be applied to various modifications and can have various embodiments, specific embodiments are shown in the drawings and described in detail in the detailed description. However, this is not intended to be limited to the specific embodiments, and all modifications, equivalents, and alternatives that do not depart from the technical scope of the exemplary embodiments should be understood. In the detailed description of the present invention, specific details regarding related art will be omitted if it is determined that they may unnecessarily obscure the clarity of the exemplary embodiments.

[0061] An example embodiment is a computer-implemented method that includes receiving transaction information, the transaction information including a plurality of receipt elements including date and time information, corresponding to a transaction including one or more purchases and payments; transmitting the transaction information to a transfer rail; generating a unique transaction identifier using a hash function applied to the transaction information and / or using the date and time information associated with the transaction and / or using a unique device identifier; generating a uniform resource locator (URL) including the unique transaction identifier and receipt elements including at least a transactor name, a transaction date, identification information of one or more purchases, or a total payment amount; receiving from the transfer rail confirmation of successful completion of the transfer card transaction corresponding to the transaction information; and transmitting the URL to an NFC tag controller.

[0062] Another example embodiment is a computer-implemented method that includes receiving a uniform resource locator (URL) identifying a web resource corresponding to a transaction as a string, parsing the string into a plurality of components, determining an association between at least two of the plurality of components and respective receipt element identifiers, and generating a second receipt that includes at least two of the respective receipt element identifiers.

[0063] Another example embodiment is a computing device comprising an NFC tag controller, a communications module, a processor, and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the processor to receive, via the communications module, transaction information corresponding to a transaction including one or more purchases and payments, the transaction information including a plurality of receipt elements including date information and time information; generate a unique transaction identifier using a hash function applied to the transaction information, and / or using the date information and time information, and / or using a unique device identifier; generate a URL including the unique transaction identifier; send the transaction information and the URL to a server; generate, via the NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and emit, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, the URL identifying a web resource on the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information; and upon receiving the NFC signal, the user device immediately displays the receipt via a web page or application page corresponding to the URL without requiring an email address, a text message, or the execution of a preloaded or pre-installed application.

[0064] Another example embodiment is a computer-implemented method including: receiving transaction information corresponding to a transaction including one or more purchases and payments, the transaction information including a plurality of receipt elements including date information and time information; generating a unique transaction identifier using a hash function applied to the transaction information, and / or using the date information and time information, and / or using a unique device identifier; generating a URL including the unique transaction identifier; transmitting the transaction information and the URL to a server; generating, via an NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and issuing, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, the URL identifying a web resource on the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information;

[0065] Another example embodiment is a method for issuing an electronic receipt, the method including receiving transaction information related to a transaction, generating an address corresponding to the transaction information, storing the transaction information on a server in response to the address, transmitting the generated address to a user device via wireless communication technology, and displaying, by the user device, the electronic receipt generated in response to the transaction information via the transmitted address.

[0066] Another example embodiment is a computing device having a processor and at least one memory coupled to the processor, wherein instructions stored in the at least one memory, when executed by the processor, cause the processor to perform any of the methods described herein.

[0067] Another example embodiment is a non-transitory computer-readable medium that contains instructions that, when executed by a processor, cause the processor to perform any of the methods described herein.

[0068] 10 is a diagram illustrating an electronic receipt-issuing computing system 1000 according to an example embodiment. Referring to FIG. 10, the electronic receipt-issuing computing system 1000 is shown including a POS terminal 100, an electronic receipt generator 2000, a server 300, a transfer rail 1010, an issuer computing device 1020, and a user device 400. The electronic receipt generator 2000 is a computing device. In the example illustrated by FIG. 10, the electronic receipt generator 2000 can operate as a PIN Transaction Service Point of Interaction (PTS POI) device.

[0069] The POS terminal 100, the server 300, the electronic receipt generator 2000, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can communicate via a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the POS terminal 100, the server 300, the electronic receipt generator 2000, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can connect to the Internet via Wi-Fi technology. The user device 400 may include an NFC tag reader. In other words, the user device 400 may include an NFC reading function or background NFC tag reading capability.

[0070] As shown, the POS terminal 100 can communicate with an electronic receipt generator 2000 that operates to generate an electronic receipt. Such communication can be via a wired connection, such as a USB connection. Such communication can also be via a wireless connection, such as Bluetooth. The POS terminal 100 can also include a physical token reader, which is sometimes referred to as an NFC tag reader.

[0071] The electronic receipt generator 2000 can communicate with a transfer rail 1010, which relays the transaction data to the appropriate issuer computing device 1020. Such communication can occur over a network, such as a wireless network. The transfer rail 1010 is sometimes referred to as a payment rail. In examples, the transfer rail 1010 is a payment processor, platform, server, or network infrastructure that enables electronic money transfers to occur between payers and payees. In examples, transfers can occur regardless of country, currency, digital payment method, or whether the payer or payee is a business or consumer. Each payment rail differs in how it performs this process based on payment type, speed, technology, and geographic location. Examples of transfer rails 1010 include Automated Clearing House (ACH), Mastercard, VISA (and other major credit card providers), PayPal, the RTP network, blockchain, SWIFT, and SEPA.

[0072] The POS terminal 100 and / or the electronic receipt generator 2000 may be associated with an acquirer, and communication between the POS terminal 100 and / or the electronic receipt generator 2000 and the transfer rail 1310 may be via a back-end acquiring computing device. The POS terminal 100 may be located at a location associated with a transactor, such as a merchant. By way of example, a merchant may be a store, restaurant, gym, etc. An acquirer may be a merchant bank that accepts deposits associated with transactions made at the POS terminal 100 and facilitates the settlement and crediting of those deposits to an account associated with the merchant. In some examples, the POS terminal 100 may also issue electronic receipts for fiat (cash) transactions.

[0073] Although a single transfer rail 1010 is shown in FIG. 10 , in practice, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1010 may include any one or combination of Amex®, Visa®, and / or Mastercard®. Other transfer rails may also be used. After the POS terminal 100, the electronic receipt generator 2000, and / or a back-end acquiring computing device in communication with the POS terminal 100 and / or the electronic receipt generator 2000 acquire data from the physical token, price transfer card, or user device 400 having a representation of a payment card engaged with a physical token reader provided on the POS terminal 100, determines which transfer rail is to be used. For example, the POS terminal / acquiring computing device may determine that the physical token is associated with Visa® and select the Visa® payment rail accordingly, or alternatively, may determine that the physical token is associated with Mastercard® and select the Mastercard® payment rail.

[0074] After the transfer rail 1010 is identified, the POS terminal / electronic receipt generator / acquiring computing device sends a message to the transfer rail 1010. The message may be transmitted over a network. The message may include a value representing the amount of value to be transferred to complete the transaction and physical token data, such as a primary account number (PAN) associated with the physical token. The transfer rail 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transfer rail 1010 routes the message received from the POS terminal 100 and / or electronic receipt generator 2000 to the issuer computing device 1020 of the identified issuer. The issuer computing device 1020 then determines whether the transaction is approved or denied based on predefined rules. The rules may consider one or more of, for example, whether the cardholder has available funds, whether the merchant is of an authorized type, whether the transaction violates spending limits, etc.

[0075] Once the issuer computing device 1020 decides whether to approve or deny the transaction, it sends a message indicating the outcome of this decision to the POS terminal 100 and / or the electronic receipt generator via the transfer rail 1010. The outcome may then be displayed or printed on the POS terminal 100.

[0076] Figure 2 is a block diagram showing an example of the internal configuration of the electronic receipt generator 2000 shown in Figures 1 and 10. Referring to Figure 2, the electronic receipt generator 2000 may include various components. As shown, the various components may include, for example, a network interface 2010, a communication module 2020, a memory 2030, a program storage 2040, a controller 2050, an address generator 2060, and an NFC tag controller 2070.

[0077] In some embodiments, two or more functionally connected components 2010, 2020, 2030, 2040, 2050, 2060, and 2070 may be combined together and exist as a single component. In some embodiments, a component may be divided into multiple components according to one or more functions of the component.

[0078] The network interface 2010 provides an interface for transmitting an address, such as a URL, and corresponding transaction information to the server 300 in cooperation with a communication network.

[0079] The communications module 2020 enables the electronic receipt generator 2000 to communicate with other computers or computing devices and / or various communications networks. For example, the communications module 2020 may enable the electronic receipt generator 2000 to transmit or receive communications signals. The communications signals may be transmitted or received according to one or more protocols or according to one or more standards. For example, the communications module 2020 may enable the electronic receipt generator 2000 to communicate over a cellular data network according to one or more standardized technologies, such as Global Computing Device for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communications module 2020 may enable the electronic receipt generator 2000 to communicate using NFC, via Wi-Fi, using Bluetooth, or via some combination of one or more networks or protocols. In some embodiments, all or part of the communication module 2020 may be integrated into the components of the electronic receipt generator 2000. For example, the communication module 2020 may be integrated into a communication chipset. The communication module may include a communication interface for receiving transaction information from the POS terminal 100.

[0080] The memory 2030 temporarily stores data processed by the controller 2050 and / or temporarily stores transaction information sent to the electronic receipt generator 2000 .

[0081] The program storage 2040 stores control software for performing tasks such as transmitting data to the server 300, receiving data from the POS terminal 100, generating an address corresponding to the transaction information, generating a message corresponding to the transaction information, generating a message corresponding to the address and programming the message into the NFC tag, etc. In some embodiments, the program storage may form part of the memory 2030. In some embodiments, some or all of the control software stored in the program storage may form at least a portion of one or more applications in the memory 2030.

[0082] The controller 2050 is a type of central processing unit (CPU) and can control processing related to the generation of electronic receipts in the electronic receipt generator 2000. In other words, the controller 2050 can perform various services, such as executing control software stored in the program storage 2040.

[0083] Address generator 2060 may generate a unique address corresponding to the received transaction information. In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, although example embodiments are not limited in this respect.

[0084] The address generator 2060 may generate a unique address including a unique transaction identifier corresponding to the transaction information. For example, in some implementations, the address may have the format "www.domain / unique transaction identifier / receipt element." The "receipt element" of the URL may be associated with the transaction information. In some such implementations, the format of the unique transaction identifier may include various lengths and may be based on a combination of letters, numbers, and special characters, although example embodiments are not limited thereto.

[0085] According to one embodiment, the electronic receipt generator 2000 can generate an identifier (a unique transaction identifier) ​​based on transaction-related information. For example, in some embodiments, the identifier may be generated based on information about the electronic receipt generator 2000 and / or based on the transaction date and time. According to another embodiment, the electronic receipt generator 2000 can generate the identifier using hashing techniques. Hash techniques refer to techniques that use a hash function to obtain a result value corresponding to an input value. In some such embodiments, the identifier may be a result value obtained through hashing techniques that use transaction information as input values. However, the method of generating an identifier according to example embodiments is not limited thereto.

[0086] The NFC tag controller 2070 controls the NFC tag to generate a message corresponding to the address and emit it as an NFC signal. According to one embodiment, the message may be in a specific format used for NFC. In some implementations, the specific format may refer to a format that allows the user device 400, which receives the corresponding message, to immediately perform a predetermined action. For example, the NFC tag controller 2070 may generate and emit an NDEF message containing information to be transmitted to the user device 400. In some implementations, the address is included as the payload of the NDEF message. In such an implementation, the user device 400 can perform a predetermined action upon receiving the NDEF message. The predetermined action may be, for example, opening a web page linked to the address via a web browser application.

[0087] Fig. 3 is a block diagram showing an example of the internal configuration of the server 300 shown in Fig. 1 and Fig. 10. Referring to Fig. 3, the server 300 may include various components. As shown, these components may include, for example, a communication module 310, a memory 320, a program storage 330, a controller 340, a database 350, and an electronic receipt application programming interface (API) 360.

[0088] The communications module 310 enables the server 300 to communicate with other computers or computing devices and / or various communications networks. For example, the communications module 310 may enable the server 300 to transmit or receive communications signals. The communications signals may be transmitted or received according to one or more protocols or according to one or more standards. For example, the communications module 310 may enable the server 300 to communicate over a cellular data network according to one or more standardized technologies, such as Global Computing Device for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communications module 310 may enable the server 300 to communicate using NFC, via Wi-Fi, using Bluetooth, or via some combination of one or more networks or protocols. In some embodiments, all or a portion of the communications module 310 may be integrated into components of the server 300. For example, the communications module 310 may be integrated into a communications chipset.

[0089] The communications module 310 may provide an interface for communications between the server 300 and the user device 400, and between the server 300 and the electronic receipt generator 2000. In some embodiments, the communications module 310 may include hardware and software for sending and receiving control or data signals over a wireless connection with another network device.

[0090] Memory 320 may perform the function of temporarily or permanently storing data processed by controller 340. In some embodiments, memory 320 may include magnetic storage media and / or flash storage media, although example embodiments are not limited thereto.

[0091] The program storage 330 may store one or more programs comprised of commands that instruct one or more processes to be executed by the controller, as described further below. In some embodiments, the program storage 330 may form part of the memory 320. In some embodiments, one or more programs stored in the program storage may form at least a portion of one or more applications in the memory 2030.

[0092] The controller 340 is a type of CPU, and can control processes related to the issuance of electronic receipts, such as receiving data from the electronic receipt generator 2000 and providing electronic receipts to the user device 400. In other words, the controller 340 can execute control software stored in the program storage 330 and control each component of the server 300 to perform one or more functions related to providing electronic receipts.

[0093] In some embodiments, controller 340 may include multiple types of devices capable of processing data, such as one or more processors. In example embodiments, a "processor" may refer to a hardened data processing device having circuitry physically structured to perform functions represented by computing code and / or computer program instructions, for example.

[0094] The database 350 can store address information and transaction information. The address information may include an address (e.g., a URL), a corresponding identifier, and other information related to the address. The database 350 may store a correspondence between the address information and the transaction information. In this manner, the server 300 can easily determine the transaction information using information about the address.

[0095] The e-receipt API 360 provides an interface for converting transaction information into an e-receipt format through various applications. The e-receipt API 360 also provides an interface for displaying the generated e-receipt in the form of a web page linked to an address.

[0096] These components are merely examples, and the example embodiments are not limited to these. In other words, server 300 may further include additional components, or some of the above-described components may be omitted, as needed.

[0097] 4 is a block diagram showing an example of the internal configuration of a user device 400 (FIGS. 1 and 10). Referring to FIG. 4, the user device 400 includes various components. As shown, the various components may include, for example, a network interface 410, a communication module 420, a memory 430, an input / output module 440, a program storage 450, a controller 460, and a display controller 470.

[0098] The network interface 410 can provide an interface for interfacing with a communication network to receive electronic receipts.

[0099] The communications module 420 enables the user device 400 to communicate with other computers or computing devices and / or various communications networks. For example, the communications module 420 may enable the user device 400 to transmit or receive communications signals. The communications signals may be transmitted or received according to one or more protocols or according to one or more standardized technologies. For example, the communications module 420 may enable the user device 400 to communicate over a cellular data network according to one or more standardized technologies, such as Global Computing Device for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communications module 420 may enable the user device 400 to communicate using NFC, via Wi-Fi, using Bluetooth, or via some combination of one or more networks or protocols. In some embodiments, all or a portion of the communications module 420 may be integrated into components of the user device 400. For example, the communications module 420 may be integrated into a communications chipset.

[0100] The communication module 420 may provide an interface for receiving data from the electronic receipt generator 2000 through NFC technology. The user device 400 may include an NFC tag reader. In other words, the user device 400 may include an NFC reading function or background NFC tag reading capability.

[0101] The memory 430 may temporarily store data processed by the controller 460 and / or may temporarily store addresses (eg, URLs) received from the electronic receipt generator 2000.

[0102] The I / O (input / output) module 440 may be configured to operate as a touch-sensitive display controller or another input / output controller. In some examples where the I / O module operates as a touch-sensitive display controller, the touch-sensitive display controller may provide an output interface and an input interface between the device and a user. In some implementations, the touch-sensitive display controller can send electrical signals to and receive electrical signals from the controller 460. In some embodiments, the touch-sensitive display controller can display visual output to the user, which may include text, graphics, images, video, and combinations thereof. In some embodiments, the I / O module 440 is a specific display element, such as an organic light-emitting display (OLED) or liquid crystal display (LCD), that can recognize touch input. The I / O module 440 can display the electronic receipt on a web page accessed based on a received address via a web browser application.

[0103] The program storage 450 stores software that performs tasks such as receiving a message from the electronic receipt generator 2000, checking the format of the received message, and, if the received message is an NDEF message, obtaining the address contained in the NDEF message via a web browser application as a predetermined action.

[0104] The controller 460 may be a CPU and may control processes related to the display of electronic receipts via the user device 400. In other words, the controller 460 may perform various services, such as executing control software stored in the program storage 450.

[0105] Reference is now made to Figure 11, which illustrates a flowchart of an exemplary method 1100 for issuing an electronic receipt, according to an example embodiment. The exemplary method 1100 may be performed by a computing device such as the electronic receipt generator 2000 (Figure 10), which may operate as a PTS POI device. When operating as a PTS POI device, the electronic receipt generator may include a PCI-certified payment module resident within the memory of the PTS POI device.

[0106] The example method 1100 may be specifically performed by a processor of the controller 340 (FIG. 3) of the electronic receipt generator 2000 (FIG. 10).

[0107] At operation 1110, the computing device receives transaction information corresponding to a transaction. The transaction information may be received, for example, from POS terminal 100 (FIG. 10). The transaction may include one or more items and a payment. The transaction information may include multiple receipt elements including date and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), Java Script® Object Notation (JSON), or a delimited text file.

[0108] At operation 1120, the computing device transmits transaction information to the transfer rail 1010 (FIG. 10). The transaction information may be transmitted via a module, such as a PCI-certified payment module, which may reside in the memory of the computing device. The transfer rail 1010 (FIG. 10) may simultaneously receive transfer card data from the POS terminal 100 (FIG. 10). The transfer card data may include a price amount representing the amount of price to be transferred to complete the transaction and physical token data, such as a primary account number (PAN) associated with the physical token.

[0109] At operation 1130, the computing device generates a unique transaction identifier. In some examples, the unique transaction identifier may be generated using a hash function applied to the transaction information. Alternatively, in some examples, the unique transaction identifier may be generated using a unique device identifier and / or date and time information associated with the transaction. In embodiments where the electronic receipt generator 2000 (FIG. 10) is a PTS POI device, the unique device identifier may be the unique device identifier of the PTS POI device. In one example, the unique device identifier is that of the computing device. In one example, the unique device identifier is the serial number, ID number, International Mobile Equipment Identity (IMEI), or Media Access Control (MAC) address of the computing device or PTS POI device. In an example, the unique transaction identifier may be generated using a combination (concatenation) of the date information, time information, and the unique device identifier.

[0110] At operation 1140, the computing device generates a unique URL. The unique URL may be based on the unique transaction identifier. The unique URL may identify a web resource that corresponds to an electronic receipt for the transaction. The web resource may reside on a server. The unique URL may be in the format "www.domain / uniquetransactionidentifier / receiptelement." The "receiptelement" of the URL may be related to transaction information.

[0111] In some embodiments, the computing device can transmit the transaction information to the server 300 (FIG. 10) via the communication module. The server 300 (FIG. 10) can then generate a first electronic receipt at a web resource associated with the URL. In some embodiments, the computing device may be unable to communicate with the server 300 due to, for example, a lack of internet connectivity. In such embodiments, the computing device can process the information transmitted to the server when communication between the computing device and the server is restored.

[0112] At operation 1150, the computing device receives confirmation of successful completion of the transfer card transaction corresponding to the transaction information from the transfer rail 1010 (FIG. 10). The confirmation may be received via a module, such as a PCI certified payment module, which may reside in the memory of the computing device. The computing device sends confirmation of successful completion of the transfer card transaction corresponding to the transaction information to the NFC tag controller 2070. The confirmation may be included in an NDEF message. If the transaction is rejected by the transfer rail 1010, the computing device sends a rejection of the transfer card transaction corresponding to the transaction information to the NFC tag controller 2070.

[0113] At operation 1160, the computing device may send the URL to NFC tag controller 2070. In some embodiments, NFC tag controller 2070 may be integral with the PTS POI device, such as when the computing device is a PTS POI device. Alternatively, in some embodiments, NFC tag controller 2070 may be external to the computing device.

[0114] Following receipt of the URL, the NFC tag controller 2070 can generate an NDEF message that includes the URL as a payload, and the NFC tag controller 2070 can emit an NFC signal that has the URL as a payload.

[0115] In some embodiments, the NFC signal may be an NDEF-formatted NFC tag having a URL as a payload. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Apple® Universal Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Apple™ AppClips Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Android® App Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Android® Instant App URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, a Mini App Link URL. In some embodiments, the payload may be a Progressive Web App-based URL. Examples include Apple's (registered trademark) "AppClips," Google's (registered trademark) "InstantApps," and Snapchat's (registered trademark) "SnapMini."

[0116] Once the NFC signal is emitted, it can be received by the user device 400 (FIG. 10). For example, a shopper can tap the user device 400 (FIG. 10) on a computing device, such as a PTS POI device, and receive a URL via the NFC signal. The user device 400 (FIG. 10) can receive the NFC signal containing the URL as a payload via an NFC tag reader.

[0117] Following operation 1160, once the NFC signal is emitted, it may be received by the user device 400 (FIG. 10). For example, a shopper may tap the user device 400 (FIG. 10) on the electronic receipt generator 2000 (FIG. 10) and receive a URL via the NFC signal. The user device 400 (FIG. 10) may receive the NFC signal containing the URL as a payload via an NFC tag reader.

[0118] In some embodiments, when the user device 400 (FIG. 10) receives the NFC signal, the NFC tag can launch a web browser application or other application. The web browser application or other application can display a web resource associated with a URL. As previously described, the URL may be in the format "www.domain / unique transaction identifier / receipt element." The "receipt element" of the URL may be associated with transaction information. The web resource may include a first electronic receipt.

[0119] Web resources can be launched, for example, via a progressive web app, a responsive web app (such as a web app that uses JavaScript), a rich internet app, a single-page app, or a multi-page app.

[0120] In some embodiments, the user device 400 ( FIG. 10 ) may include an application for receipt storage and display. In some such embodiments, the user device 400 ( FIG. 10 ) may be an iOS® phone that includes Apple™ Universal Link. In such embodiments, when the user device 400 ( FIG. 10 ) receives an NFC signal, the Apple® Universal Link may cause the first electronic receipt to be displayed and / or saved in the receipt storage and display application. In some such embodiments, the user device ( FIG. 10 ) may not be an iOS® phone but may include a deep link (e.g., an Android® App Link). In such embodiments, when the user device 400 ( FIG. 10 ) receives an NFC signal, the deep link may cause the first electronic receipt to be displayed and / or saved in the receipt storage and display application. The first electronic receipt may be displayed by the application in a format determined by the transactor associated with the transaction.

[0121] In some embodiments, the user device 400 ( FIG. 10 ) may not include an application for storing and displaying receipts. In some such embodiments, if the user device 400 ( FIG. 10 ) is an iOS® phone that includes an Apple® Universal Link, the Apple® Universal Link can direct the user to the Apple® App Store to download the application for storing and displaying receipts. In some such embodiments, if the user device 400 ( FIG. 10 ) is not an iOS® phone, a deep link (e.g., an Android® App Link) can direct the user to a mobile app store to download the application for storing and displaying receipts. In some such embodiments, if the user device 400 ( FIG. 10 ) is an iOS® phone, the user device 400 ( FIG. 10 ) can receive an Apple® App Clip link and launch an App Clip. In some such embodiments, if the user device is a non-iOS® phone, the user device 400 ( FIG. 10 ) can receive an Instant App link and launch an Instant App. In some such embodiments, the user device 400 (FIG. 10) can receive the mini-app link and launch the mini-app.

[0122] In some embodiments, a web NFC framework can be used to provide one or more receipts to a user device 400 (FIG. 10).

[0123] In some embodiments, the user device 400 (FIG. 10) can launch a web browser application that renders output at a unique URL location containing the first electronic receipt. The format of the first electronic receipt can be a format determined by the transactor associated with the first electronic receipt. The first electronic receipt can be generated using the transaction data and displayed by the user device using an application. The application can be, for example, a progressive web app, a responsive web app (e.g., a JavaScript-based web app), a rich internet app, a single-page app, or a multi-page app. The first electronic receipt can be saved to a first location by the corresponding application.

[0124] In some embodiments, as described above, the application may be launched by an Apple® Universal Link or an associated non-iOS® mobile or web application. If the application is launched by an associated non-iOS® application, the application may be launched via a deep link or an Android® App Link. In such embodiments, the application may display the first electronic receipt in a format determined by the transactor in association with the first electronic receipt. The first electronic receipt may be saved to a first location by the corresponding application.

[0125] Referring now to FIG. 12, FIG. 12 illustrates an electronic receipt-issuing computing system 1200 according to an example embodiment. Referring to FIG. 12, the electronic receipt-issuing computing system 1200 is shown to include a computing device operating as the POS terminal 100 and the functionality of the electronic receipt generator 2000 (FIG. 10). The electronic receipt-issuing computing system is also shown to include a server 300, a card reader (CR) device 1210, a transfer rail 1010, an issuer computing device 1020, and a user device 400. In some embodiments, the CR device 1210 of the electronic receipt-issuing computing system 1200 may be referred to as a Commercial Off-the-Shelf Card Reader (SPoC) device that implements PCI software-based PIN entry. The computing device operating as the POS terminal 100 may be referred to as an SPoC device and / or a Commercial Off-the-Shelf (COTS) device.

[0126] The computing device operating as the POS terminal 100, the server 300, the CR device 1210, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can communicate over a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the computing device operating as the POS terminal 100, the server 300, the CR device 1210, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can connect to the Internet via Wi-Fi technology. The user device 400 may include an NFC tag reader. In other words, the user device 400 may include an NFC reading function or background NFC tag reading capability.

[0127] As shown, the CR device 1210 can communicate with a computing device operating as a POS terminal 100, which can operate to generate electronic receipts. Such communication can be via a wired connection, such as a USB connection. Such communication can also be via a wireless connection, such as Bluetooth.

[0128] A computing device operating as a POS terminal 100 can communicate with a transfer rail 1010, which relays transaction data to the appropriate issuer computing device 1020. Such communication can occur over a network, such as a wireless network. The transfer rail 1010 is sometimes referred to as a payment rail.

[0129] A computing device operating as a POS terminal 100 may be associated with an acquirer, and communications between the computing device operating as a POS terminal 100 and the transfer rail 1010 may be via a back-end acquirer computing device. A computing device operating as a POS terminal 100 may be located at a location associated with a merchant. By way of example, a merchant may be a store, restaurant, gym, etc. An acquirer may be a merchant bank that accepts deposits related to transactions made on a computing device operating as a POS terminal 100 and facilitates the settlement and crediting of those deposits to accounts associated with the transactors.

[0130] Although a single transfer rail 1010 is shown in FIG. 12 , in practice, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1010 may include any one or combination of Amex®, Visa®, and / or Mastercard®. Other transfer rails may also be used. The computing device operating as the POS terminal 100 and / or a back-end acquiring computing device in communication with the computing device operating as the POS terminal 100 determines which transfer rail to use after acquiring data from a physical token, such as a balance transfer card or mobile device bearing a representation of a payment card, engaged with the CR device 1210 provided on the POS terminal 100. For example, the POS terminal / acquirer computing device may determine that the physical token is associated with Visa® and accordingly select the Visa® payment rail, or alternatively, may determine that the physical token is associated with Mastercard® and accordingly select the Mastercard® payment rail.

[0131] After the transfer rail 1010 is identified, the POS terminal 100 / computing device acting as the acquirer computing device sends a message to the transfer rail 1010. The message may be transmitted over a network. The message may include a price amount representing the amount of price to be transferred to complete the transaction and physical token data, such as a primary account number (PAN) associated with the physical token. The transfer rail 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transfer rail 1010 routes the message received from the computing device acting as the POS terminal 100 to the issuer computing device 1020 of the identified issuer. The issuer computing device 1020 then determines whether the transaction is approved or denied based on predefined rules. The rules may consider one or more of, for example, whether the cardholder has available funds, whether the merchant is of an authorized type, or whether the transaction violates spending limits.

[0132] Once the issuer computing device 1020 has decided whether to approve or deny the transaction, it sends a message indicating the outcome of this decision via the transfer rail 1010 to the computing device acting as the POS terminal 100. The outcome may then be displayed or output on the POS terminal 100.

[0133] The computing device operating as the POS terminal 100 may be a commercial off-the-shelf (CTOS) device and may include a PCI certified payment module. The computing device operating as the POS terminal 100 may be, for example, a laptop, a tablet, a smartphone, etc. In the embodiment of the electronic receipt issuing computing system 1200 shown in FIG. 12, the computing device operating as the POS terminal 100 includes the functionality of the electronic receipt generator 2000 (FIG. 10).

[0134] The user device 400 may include a mobile wallet that stores a representation of a payment card. A physical token may be connected to one or more accounts (e.g., bank accounts) that store data and / or resources accessible to the cardholder. As an example, a physical token may be associated with a bank account and / or a credit card account. A physical token may function as a credit card or debit card. A physical token may be used to make purchases at a point-of-sale terminal. Such physical tokens may be configured for tap-style payments, where the physical token is placed within communication range of a physical token reader, such as the CR device 1210, allowing physical token data to be read from the physical token.

[0135] The user device 400 may be configured for near field communication (NFC) payment processing, or for another type of wireless communication based payment processing.

[0136] The CR device 1210 communicates with a computing device operating as the POS terminal 100. The CR device 1210 may be configured to read a physical token, such as a transfer card or a mobile device on which a representation of the transfer card is stored. In this manner, the CR device 1210 may be configured to receive transfer card data. The physical token reader may be or include a card slot that facilitates communication with the physical token through physical contact, and / or a contactless reader, such as a near-field communication (NFC) reader that facilitates communication with the physical token through a communication protocol that does not rely on physical contact with the physical token. The CR device 1210 may include an NFC tag controller 2070.

[0137] Reference is now made to FIG. 13, which illustrates a flowchart of an exemplary method 1300 for issuing an electronic receipt, according to an example embodiment. The exemplary method 1300 may be performed by a computing device, such as a computing device operating as a POS terminal 100 (FIG. 12). The computing device operating as a POS terminal 100 (FIG. 12) may include a PCI-certified payment module that may reside within the memory of the computing device. In some embodiments, the computing device operating as a POS terminal 100 (FIG. 12) may be a CPoC device and / or a SPoC device.

[0138] The exemplary method 1300 may be specifically performed by a processor of the controller 340 (FIG. 3) of a computing device operating as the POS terminal 100 (FIG. 12).

[0139] The example method 1300 differs from the example method 1100 of FIG. 11 in that the example method 1300 includes two additional operations 1112, 1114 between operations 1110 and 1120 of the example method 1100 of FIG.

[0140] At operation 1110, a computing device receives transaction information corresponding to a transaction. The transaction may include one or more items and a payment. The transaction information may include multiple receipt elements including date and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), JavaScript Object Notation, or a delimited text file.

[0141] In some embodiments, after operation 1110, the computing device may activate the CR device 1210 (FIG. 12) to obtain the transfer card data.

[0142] At operation 1112, the computing device receives the transfer card data from the CR device 1210 (FIG. 12). The transfer card data may be received via a wired connection, such as a USB connection. The transfer card data may be received via a wireless connection, such as Bluetooth.

[0143] As described above, the CR device 1210 (FIG. 12) may include an NFC tag controller 2070. The CR device 1210 (FIG. 12) may be configured to read a physical token, such as a transfer card or a mobile device on which a representation of the transfer card is stored. In this manner, the CR device 1210 (FIG. 12) may be configured to receive transfer card data. The physical token reader may be or include a card slot that facilitates communication with the physical token through physical contact and / or a contactless reader, such as a near-field communication (NFC) reader that facilitates communication with the physical token via a communication protocol that does not rely on physical contact with the physical token. The CR device 1210 (FIG. 12) may then be operable to communicate the transfer card data to a computing device.

[0144] At operation 1114, the computing device transmits the transfer card data to the transfer rail 1010 (FIG. 12). The transfer card data may be transmitted via a module, such as a PCI certified payment module, which may reside in the memory of the computing device. The transfer card data may be transmitted over a network. The transfer card data may include a value representing the amount of value to be transferred to complete the transaction and physical token data, such as a primary account number (PAN) associated with the physical token.

[0145] At operation 1120, the computing device transmits the transaction information to the transfer rail 1010 (FIG. 10). The transaction information may include multiple receipt elements, including date and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), Java Script® Object Notation (JSON), or a delimited text file.

[0146] In some embodiments, operations 1114 and 1120 may be performed in reverse order, for example, operation 1120 may precede operation 1114. In some embodiments, operations 1114 and 1120 may be performed simultaneously.

[0147] At operation 1130, the computing device generates a unique transaction identifier. In some examples, the unique transaction identifier may be generated using a hash function applied to the transaction information. Alternatively, in some examples, the unique transaction identifier may be generated using a unique device identifier and / or date and time information associated with the transaction. In some embodiments, the unique device identifier may be a unique device identifier of the computing device or CR device 1210 (FIG. 12). In one example, the unique device identifier is a serial number, ID number, International Mobile Equipment Identity (IMEI), or Media Access Control (MAC) address of the computing device or CR device 1210 (FIG. 12).

[0148] At operation 1140, the computing device generates a unique URL. The unique URL may be based on the unique transaction identifier. The unique URL may identify a web resource that corresponds to an electronic receipt for the transaction. The web resource may reside on server 300 (FIG. 12). The unique URL may be in the format "www.domain / unique transaction identifier / receipt element." The "receipt element" of the URL may be related to transaction information.

[0149] In some embodiments, the computing device may send the transaction information to the server via the communications module. The server 300 (FIG. 12) may then generate a first electronic receipt at a web resource associated with the URL. In some embodiments, the computing device may be unable to communicate with the server, for example, due to a lack of Internet connectivity. In such embodiments, the computing device may queue the transaction information to be sent to the server when communications between the computing device and the server 300 (FIG. 12) are restored.

[0150] At operation 1150, the computing device receives from the transfer rail a confirmation of successful completion of the transfer card transaction corresponding to the transaction information. The confirmation may be received via a module, such as a PCI certified payment module, which may reside in the memory of the computing device. The computing device sends the confirmation of successful completion of the transfer card transaction corresponding to the transaction information to the NFC tag controller 2070. The confirmation may be included in an NDEF message. If the transaction is rejected by the transfer rail 1010, the computing device sends a rejection of the transfer card transaction corresponding to the transaction information to the NFC tag controller 2070.

[0151] At act 1160, the computing device may transmit the unique URL to the NFC tag controller 2070. In some embodiments, the NFC tag controller 2070 may be integral with the CR device 1210 (FIG. 12). In some such embodiments, the computing device may transmit the unique URL to the CR device 1210 (FIG. 12).

[0152] Following receipt of the URL, the NFC tag controller 2070 can generate an NDEF message that includes the URL as a payload. The NFC tag controller 2070 can then emit an NFC signal that has the URL as a payload. In some embodiments, the CR device 1210 (FIG. 12) can emit an NFC signal that has the URL as a payload.

[0153] In some embodiments, the NFC signal may be an NDEF-formatted NFC tag having a URL as a payload. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Apple® Universal Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Apple™ App Clip Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Android® App Clips Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, an Android® Instant App Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag having, for example, a Mini App Link URL. In some embodiments, the payload may be a Progressive Web App-based URL.

[0154] 14, which illustrates an electronic receipt-issuing computing system 1400 according to an example embodiment. Referring to FIG. 14, the electronic receipt-issuing computing system 1400 is shown to include a computing device operating as a POS terminal 100 and including the functionality of the electronic receipt generator 2000 (FIG. 10). The electronic receipt-issuing computing system is also shown to include a server 300, a transfer rail 1010, an issuer computing device 1020, and a user device 400. In some embodiments, the computing device operating as the POS terminal 100 of the electronic receipt-issuing computing system 1400 may also be described as a PCI contactless payment commercial off-the-shelf (CPoC) device, a mobile payment on commercial off-the-shelf (MPoC) device, a tap-to-phone device, and / or a tap-on-phone device.

[0155] The computing device operating as the POS terminal 100, the server 300, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can communicate over a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the computing device operating as the POS terminal 100, the server 300, the transfer rail 1010, the issuer computing device 1020, and the user device 400 can connect to the Internet via Wi-Fi technology. The user device 400 may include an NFC tag reader. In other words, the user device 400 may include an NFC reading function or a background NFC tag reading capability.

[0156] A computing device operating as a POS terminal 100 may be configured to operate as a physical token reader, sometimes referred to as an NFC tag reader. That is, a computing device operating as a POS terminal 100 may operate to read a physical token, such as a transfer card or a user device 400 on which a representation of a transfer card is stored. In this manner, a computing device operating as a POS terminal 100 may be configured to receive transfer card data. A physical token reader may be a contactless card reader, such as a near-field communication (NFC) reader, that facilitates communication with a physical token via a communication protocol that does not rely on physical contact with the physical token. A computing device operating as a POS terminal 100 may include an NFC tag controller.

[0157] The computing device is operable to operate as a POS terminal 100 and to generate electronic receipts.

[0158] A computing device operating as a POS terminal 100 may communicate with a transfer rail 1010 that relays transaction data to the appropriate issuer computing device 1020. Such communication may occur over a network, such as a wireless network. The transfer rail 1010 may also be referred to as a payment rail.

[0159] A computing device operating as a POS terminal 100 may be associated with an acquirer, and communication between the computing device operating as a POS terminal 100 and the transfer rail 1010 may be via a back-end acquirer computing device. A computing device operating as a POS terminal 100 may be located at a location associated with a transactor, such as a merchant. By way of example, a merchant may be a store, restaurant, gym, etc. An acquirer may also be a merchant bank that accepts deposits related to transactions made on a computing device operating as a POS terminal 100 and facilitates the settlement and crediting of those deposits to an account associated with the merchant.

[0160] Although a single transfer rail 1010 is shown in FIG. 14 , in practice, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1310 may include any one or combination of Amex®, Visa®, and / or Mastercard®. Other transfer rails may also be used. After the computing device operating as the POS terminal 100 and / or a back-end acquirer computing device communicating with the computing device operating as the POS terminal 100 acquires data from a physical token, such as a price transfer card or mobile device, the device having a representation of the payment card engaged with the computing device operating as the POS terminal 100 determines which transfer rail should be used. For example, the POS terminal / acquirer computing device may determine that the physical token is associated with Visa® and accordingly select the Visa® payment rail, or alternatively, may determine that the physical token is associated with Mastercard® and accordingly select the Mastercard® payment rail.

[0161] After the transfer rail is identified, the POS terminal 100 / computing device acting as the acquirer computing device sends a message to the transfer rail. The message may be transmitted over a network. The message may include a price amount representing the amount of price to be transferred to complete the transaction and physical token data, such as a primary account number (PAN) associated with the physical token. The transfer rail 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transfer rail 1010 routes the message received from the computing device acting as the POS terminal 100 to the issuer computing device 1020 of the identified issuer. The issuer computing device 1020 then determines whether the transaction is approved or denied based on predefined rules. The rules may consider one or more of, for example, whether the cardholder has available funds, whether the merchant is of an authorized type, or whether the transaction violates spending limits.

[0162] Once the issuer computing device 1020 has decided whether to approve or deny the transaction, it sends a message indicating the outcome of this decision via the transfer rail 1010 to the computing device acting as the POS terminal 100. The outcome may then be displayed or output on the POS terminal 100.

[0163] A computing device operating as a POS terminal 100 may be referred to as a PCI PoC device, an MPoC device, a tap-to-phone device, and / or a tap-on-phone device and may include a PCI certified payment module. A computing device operating as a POS terminal 100 may be, for example, a laptop, a tablet, a smartphone, etc. In the embodiment of an electronic receipt issuing computing system 1400 shown in FIG. 14, the computing device operating as a POS terminal 100 includes the functionality of an electronic receipt generator 2000 (FIG. 10).

[0164] The user device 400 may include a mobile wallet that stores a representation of a payment card. A physical token may be connected to one or more accounts (e.g., bank accounts) that store data and / or resources accessible to the cardholder. As an example, a physical token may be associated with a bank account and / or a credit card account. A physical token may function as a credit card or debit card. A physical token may be used to make purchases at a POS terminal. Such physical tokens may be configured for tap-style payments, where the physical token is placed within communication range of a physical token reader, such as a computing device operating as the POS terminal 100, allowing physical token data to be read from the physical token.

[0165] The user device 400 may be configured for near field communication (NFC) payment processing, or for another type of wireless communication based payment processing.

[0166] The method 1300 (FIG. 13) may be performed by an electronic receipting computing system 1400.

[0167] The difference between the electronic receipt issuing computing system 1400 and the electronic receipt issuing computing system 1200 (FIG. 12) is that the computing device operating as the POS terminal 100 in FIG. 14 is configured to operate as a physical token reader. A physical token reader is also called an NFC tag reader.

[0168] As a result, when performing method 1300 (FIG. 13), the computing device operating as POS terminal 100 (FIG. 14) can receive the transferred card data directly at operation 1112 (FIG. 13), as described with reference to electronic receipt issuing computing system 1200 (FIG. 12), rather than via a separate card.

[0169] 13 , at operation 1130, the computing device generates a unique transaction identifier. As previously mentioned, in some examples, the unique transaction identifier may be generated using a hash function applied to the transaction information. As further noted, alternatively, in some examples, the unique transaction identifier may be generated using a unique device identifier and / or date and time information associated with the transaction.

[0170] At operation 1130, the computing device operating as the POS terminal 100 (FIG. 14) uses the unique device identifier (e.g., PCI CPoC device, MPoC device, tap-to-phone device, and / or tap-on-phone device) of the computing device operating as the POS terminal 100 (FIG. 14) as the unique device identifier.

[0171] Following operation 1160, once the NFC signal is emitted, it may be received by the user device 400 (FIGS. 12, 14). For example, a shopper may tap the user device 400 (FIGS. 12, 14) on the POS terminal 100 (FIGS. 12, 14) and receive a URL via the NFC signal. The user device 400 (FIGS. 12, 14) may receive the NFC signal containing the URL as a payload via an NFC tag reader.

[0172] When the user device 400 (FIGS. 12, 14) receives the NFC signal, the NFC tag can launch a web browser application. The web browser application may display a web resource associated with the URL. As previously described, the URL may be in the format "www.domain / unique transaction identifier / receipt element." The "receipt element" of the URL may be associated with transaction information. The web resource may include a first electronic receipt.

[0173] Web resources can be launched, for example, via a progressive web app, a responsive web app (such as a web app that uses JavaScript), a rich internet app, a single-page app, or a multi-page app.

[0174] In some embodiments, the user device 400 (FIGS. 12, 14) may include an application for receipt storage and display. In some such embodiments, the user device 400 (FIGS. 12, 14) may be an iOS® phone that includes the Apple™ Universal Link. In such embodiments, when the user device 400 (FIGS. 12, 14) receives an NFC signal, the Apple™ Universal Link may cause the first electronic receipt to be displayed and / or saved in the receipt storage and display application. In some such embodiments, the user device (FIGS. 12, 14) may not be an iOS® phone but may include a deep link (e.g., an Android® App Link). In such embodiments, when the user device 400 (FIGS. 12, 14) receives an NFC signal, the deep link may cause the first electronic receipt to be displayed and / or saved in the receipt storage and display application. The first electronic receipt may be displayed by the application in a format determined by the transactor associated with the transaction.

[0175] In some embodiments, the user device 400 (FIGS. 12, 14) may not include an application for saving and displaying receipts. In some such embodiments, if the user device 400 (FIGS. 12, 14) is an iOS® phone that includes an Apple® Universal Link, the Apple® Universal Link can direct the user to the Apple® App Store to download the application for saving and displaying receipts. In some such embodiments, if the user device 400 (FIGS. 12, 14) is not an iOS® phone, a deep link (e.g., an Android® App Link) directs the user to a mobile app store to download the application for displaying and saving receipts. In some such embodiments, if the user device 400 (FIGS. 12, 14) is an iOS® phone, the user device 400 (FIGS. 12, 14) can receive the Apple® App Clip Link and launch the App Clip. In some such embodiments, if the user device is a non-iOS® phone, the user device 400 (FIGS. 12, 14) can receive an instant app link and launch an instant app. In some such embodiments, the user device 400 (FIGS. 12, 14) can receive a mini app link and launch a mini app.

[0176] In some embodiments, a web NFC framework can be used to provide one or more receipts to the user device 400 (FIGS. 12, 14).

[0177] In some embodiments, the user device 400 (FIGS. 12 and 14) can launch a web browser application that renders output at the location of the unique URL. The rendered output may include a first electronic receipt. The format of the first electronic receipt may be a format determined by the transactor associated with the first electronic receipt. The first electronic receipt may be generated using transaction data and displayed by the user device using an application. The application may be, for example, a progressive web app, a responsive web app (e.g., a JavaScript-based web app), a rich internet app, a single-page app, or a multi-page app. The first electronic receipt may be saved to a first location by the corresponding application. The first location may be, for example, within the memory 430 (FIG. 4) of the user device 400 (FIGS. 12 and 14).

[0178] In some embodiments, as described above, the application may be launched by an Apple™ Universal Link or an associated non-iOS® mobile or web application. If the application is launched by an associated non-iOS® application, the application may be launched via a deep link or an Android® app link. In such embodiments, the application may display the first electronic receipt in a format determined by the transactor in association with the first electronic receipt. The first electronic receipt may be stored in a first location by the corresponding application. The first location may be, for example, within memory 430 (FIG. 4) of user device 400 (FIGS. 12 and 14).

[0179] In some implementations, there may be no communication between the POS terminal 100 (FIGS. 12 and 14) and the server 300 (FIGS. 12 and 14). In some such embodiments, the POS terminal 100 generates a URL that allows the user device 400 to generate a second electronic receipt for the transaction without accessing the URL on the Internet by parsing the URL. In some examples, the second electronic receipt may also be used as a temporary electronic receipt that eventually replaces the first electronic receipt. For example, when an Internet connection is present by the computing device 300, the POS terminal 100 uploads the transaction information of the first electronic receipt (or, in the alternative, the first electronic receipt itself) to the server 300. The server 300 associates a URL with the first electronic receipt. The first electronic receipt can then be retrieved by the user device 400. In some examples, the second electronic receipt becomes the first receipt. For example, if there is an internet connection by the computing device 300, only a URL is generated that contains enough information to allow the user device 400 to parse the URL and generate a second electronic receipt for the transaction without accessing the URL on the internet.

[0180] The second electronic receipt may be generated by the user device 400 (FIGS. 12 and 14) based on a URL received by the user device 400, for example, by parsing. As previously described, the URL may be in the format "www.domain / unique transaction identifier / receipt element," where the "receipt element" of the URL may be related to transaction information. The second electronic receipt may be generated by an application on the user device 400 using information contained in the URL (FIGS. 12 and 14). The application may be, for example, an App Clip, an Instant App, a Mini App, or the like. For example, the application may not need to be pre-installed or pre-loaded.

[0181] In some embodiments, the second electronic receipt may be stored in a first location, which may be memory 430 (FIG. 4) of user device 400 (FIGS. 12, 14).

[0182] In some embodiments, the user can choose to keep the second electronic receipt and refrain from using the first electronic receipt. In some implementations, the user can temporarily refer to the second electronic receipt and retrieve and use the first electronic receipt when it becomes available (e.g., when communication or internet connectivity between the POS terminal 100 (FIGS. 12 and 14) and the server 300 (FIGS. 12 and 14) is restored). In some embodiments, when the user device 400 receives the first electronic receipt, the first electronic receipt can be stored by the user device 400 in a first location. In this way, the second electronic receipt, also referred to in this example as a provisional electronic receipt, can replace the first electronic receipt in the first location.

[0183] 15, which is a flowchart of an example method 1500 for generating a second electronic receipt, according to some embodiments. The second electronic receipt may also be referred to as an interim electronic receipt. The operations may be performed by the user device 400 (FIG. 1), and more specifically, by a processor of the controller 460 (FIG. 4) of the user device 400. For example, processor-executable instructions stored in the memory 430 (FIG. 4) of the user device 400, when executed by one or more processors of the controller 460 (FIG. 4), may configure the user device 400 to perform the example method 1300, or a portion thereof.

[0184] The example method 1500 of FIG. 15 can operate to instantly generate a second electronic receipt for a transaction, also referred to as an interim electronic receipt. The second electronic receipt can be generated and displayed under various conditions, including conditions in which the user device is not traditionally "prepared" to display electronic receipts. The example method 1500 is an application that does not require, for example, a user to prior install, register an account, activate the user device's camera, and / or exchange an email address or phone number with the electronic receipt provider. The example method 1500 does not require an internet connection on the user device.

[0185] The example method 1500 of FIG. 15 can operate to instantly generate a second electronic receipt for a transaction under conditions where the user device 400 (FIG. 1) does not include a web browser application.

[0186] The example method 1500 of FIG. 15 can operate to instantly generate a second electronic receipt if an internet connection and / or a web browser application is available.

[0187] In some embodiments, the second electronic receipt may be stored in a first location, which may be memory 430 (FIG. 4) of user device 400 (FIG. 1).

[0188] In some embodiments, the user can choose to keep the second electronic receipt and forgo using the first electronic receipt. In some implementations, the user can temporarily refer to the second electronic receipt and retrieve and use the first electronic receipt when it becomes available (e.g., when an Internet connection is made available by the POS terminal 100). In some implementations, upon receiving the first electronic receipt, the first electronic receipt can be stored in a first location. In this manner, the second electronic receipt, also referred to in this example as a provisional electronic receipt, can replace the first electronic receipt in the first location.

[0189] At operation 1502, the user device 400 (FIG. 1) receives a URL as a string. For example, the URL may be in the format "www.domain / unique transaction identifier / receipt element." For example, an example URL may appear as follows: web address / unique transaction identifier / 764983309-22.12.13-1107-CC-xxxxxxxx1234-KimsConvenience-26.75-3

[0190] At operation 1504, the user device 400 (FIG. 1) parses the string into multiple components that represent individual receipt elements. In some embodiments, the user device 400 (FIG. 1) may parse the string into tokens according to defined rules. For example, in some implementations, after receiving the URL, the user device 400 (FIG. 1) may ignore the first group of characters up to and including the second slash. In other words, in the context of the example URL above, the user device 400 (FIG. 1) can ignore the first group of characters: “www.domain / unique transaction identifier / receipt element.”

[0191] In some implementations, after ignoring the first group of characters, the user device 400 (FIG. 1) can divide the remaining characters into multiple components that represent individual receipt elements. For example, the user device 400 (FIG. 1) may divide the remaining characters into components at each instance of a hyphen. In other words, in the context of the URL example above, the user device 400 (FIG. 1) can divide the remaining characters into the following components: 764983309; 22.12.13; 1107; CC; xxxxxxxx1234; KimsConvenience; 26.75; 3

[0192] At operation 1506, the user device 400 (FIG. 1) determines an association between each of the plurality of components and a receipt element identifier from the plurality of receipt element identifiers. For example, in some embodiments, the user device 400 (FIG. 1) can store an ordered list of the plurality of receipt item identifiers. In some examples, the ordered list of the plurality of receipt element identifiers may include one or more of a receipt authorization number, a transaction date, a transaction time, a payment type, a payment amount, a number of items, a subtotal amount, a tax amount, a discount amount, a transactor name, a transactor number (e.g., a company number), a transactor address, a transactor phone number, a transaction number, etc.

[0193] In some implementations, the user device 400 (FIG. 1) may determine an association between each of a plurality of components representing individual receipt elements and a receipt element identifier among the plurality of receipt identifiers. The user device may determine the association by associating a first component of the plurality of components with a first electronic receipt element identifier, a second component of the plurality of components with a second electronic receipt element identifier, a third component of the plurality of components with a third receipt element identifier, etc. However, as will be appreciated by those skilled in the art, any number of methods for determining an association between a plurality of components and a receipt element identifier may be used.

[0194] In some implementations, the ordered list of receipt elements can include elements that meet legal requirements for receipts (eg, IRS requirements).

[0195] In some implementations, the ordered list of receipt element identifiers may be customizable by a user. For example, in a particular implementation, the ordered list may include a receipt authorization number, a transaction date, a transaction time, a payment type, a payment amount, a number of items, a subtotal, a tax amount, a discount amount, a transactor name, a transactor number (e.g., a company number), a transactor address, a transactor phone number, or a transaction number.

[0196] At operation 1508, the user device 400 (FIG. 1) generates a second electronic receipt that includes at least two of the respective receipt element identifiers. The second electronic receipt may be displayed via a graphical user interface (GUI) on a display of the user device 400. In some embodiments, the second electronic receipt may include an association between the at least two receipt element identifiers and the respective components.

[0197] In some embodiments, the user device 400 may be operable to customize the second electronic receipt.

[0198] 16, an exemplary display screen 1600 of a receipt management user interface is shown, according to an example embodiment. The receipt management user interface may be displayed on a user device 400. The exemplary display screen 1600 includes a first heading 1630 that reads, "Receipt Element Selection - Offline Version." The exemplary display screen 1600 further includes a first ordered list 1610 of a plurality of receipt element identifiers. The first ordered list 1610 of receipt element identifiers is displayed in a left column of the display screen 1600. In the example of FIG. 16, the first ordered list of receipt element identifiers is: receipt authorization number, transaction date, transaction time, payment type, payment amount, number of items, subtotal, tax amount, discount amount, transactor name, transactor number, transactor address, transactor phone, and transaction number.

[0199] A set of check boxes 1620 is displayed in the right column of display screen 1600. Each check box in the set of check boxes 1620 corresponds to one of the receipt element identifiers in first ordered list of receipt element identifiers 1610. In some embodiments, a user can customize the ordered list of receipt element identifiers by selecting the check box corresponding to the desired receipt element identifier.

[0200] For example, FIG. 16 shows the first seven checkboxes highlighted, indicating selection of the first seven corresponding receipt element identifiers. The desired receipt element identifiers in the example of FIG. 16 are transaction date, transaction time, payment type, payment amount, and number of items. This selection may be the result of a user selection or may be a default setting. Selecting the first seven receipt element identifiers as the desired receipt element identifiers may cause the corresponding intermediate receipt to display the desired receipt element identifiers and one or more associated components of the multiple components. Not selecting the remaining receipt element identifiers may cause the corresponding intermediate receipt to not display the remaining receipt element identifiers and associated components of the multiple components.

[0201] 17, an exemplary display screen 1700 of a second electronic receipt is shown, according to an example embodiment. The example display screen 1700 includes a heading 1730, e.g., "Receipt - Offline Version." The example display screen 1700 further includes a second ordered list 1710 of a plurality of receipt element identifiers on the left side of the display screen 1700. In the example of FIG. 17, the second ordered list of receipt element identifiers is: receipt authorization number, transaction date, transaction time, payment type, payment amount, and number of items. The second ordered list of receipt elements 1710 corresponds to a selection of the first seven receipt element identifiers shown by FIG. 16.

[0202] A list of components 1720 is displayed in the right column of display screen 1700. Each component in list of components 1720 is associated with one of the receipt elements in second ordered list of receipt elements 1710.

[0203] Display screen 1700 of FIG. 17 illustrates the following associations between receipt element identifiers and components: Receipt approval number: 764983309 Transaction date: 22.12.13 Trading time: 11:07 AM Payment type: CC-xxxxxxxx1234 Customer Name: KimsConvenience Amount paid: $26.75 Number of items: 3

[0204] As discussed above in connection with operation 1506 of FIG. 15 , in some implementations, the user device 400 (FIG. 1) can determine an association between each of a plurality of components and a receipt element identifier of the plurality of receipt identifiers. This determination can be made by associating a first component of the plurality of components with a first electronic receipt element identifier, a second component of the plurality of components with a second electronic receipt element identifier, a third component of the plurality of components with a third receipt element identifier, etc. However, as will be appreciated by those skilled in the art, any number of methods for determining an association between a receipt element identifier and a component can be used.

[0205] Following generation of the second electronic receipt, the user device 400 (FIG. 14) can access a web resource corresponding to the first electronic receipt for the transaction identified by a URL. For example, the POS terminal 100 could then upload the transaction information of the first electronic receipt (or, alternatively, the first electronic receipt itself) to the server 300 when an Internet connection is eventually detected (e.g., restored). In some embodiments, the first electronic receipt can be saved by the user device 400 to a first location.

[0206] In some embodiments, the user device 400 (FIG. 14) can display the second electronic receipt. The application can save the second electronic receipt to a first location. The application can then replace the second electronic receipt with the first electronic receipt by storing the first electronic receipt in the first location.

[0207] In some embodiments, the user device 400 may launch an associated mini-app mobile application to display the first electronic receipt. The format of the first electronic receipt may be a format determined by the transactor associated with the first electronic receipt. The first electronic receipt may be generated using transaction data. Examples of associated mini-apps include Apple® App Clips, Android® Instant Apps, etc. In examples, the mini-apps are not pre-installed or pre-loaded on the user device 400.

[0208] Referring now to Figure 1, Figure 1 is a diagram illustrating an electronic receipt-issuing computing system 10 according to an example embodiment. Referring to Figure 1, the electronic receipt-issuing computing system 10 according to an example embodiment includes a point-of-sale (POS) terminal 100, an electronic receipt generator 2000, a server 300, and a user device 400.

[0209] The POS terminal 100, the electronic receipt generator 2000, the server 300, and the user device 400 can communicate over a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the POS terminal 100, the electronic receipt generator, the server 300, and the user device 400 can connect to the Internet via Wi-Fi technology.

[0210] The POS terminal 100, according to some example embodiments, is a device capable of processing transactions. A transaction may correspond to one or more purchases (one or more items and / or one or more services) and payments. Example embodiments may be described herein with reference to the purchase of items, with the understanding that the transaction applies to services as well as charitable donations and goodwill. For example, a transaction may correspond to the exchange of one or more items, e.g., one or more goods and / or one or more services, for a payment amount. In some embodiments, a transaction may correspond to the purchase of one or more items. In addition to processing a transaction, the POS terminal 100 may determine the outcome of the transaction and manage information related to the transaction.

[0211] POS terminal 100 may refer to one of various commercial types of POS terminals known to those skilled in the art. Point of sale (POS) terminal 110 may be associated with an entity (not shown), such as a merchant or acquirer.

[0212] In some embodiments, as shown, the electronic receipt generator is a separate device from the POS terminal 100. In such embodiments, the POS terminal 100 and the electronic receipt generator 2000 can transmit and receive data via a communication computing device. For example, the communication computing device may include a wired communication computing device via a Universal Serial Bus (USB) cable, or a wireless communication computing device such as Wi-Fi or Bluetooth. However, example embodiments are not limited thereto.

[0213] In some example embodiments, the POS terminal 100 and the electronic receipt generator 2000 may reside on the same device.

[0214] 1 illustrates the POS terminal 100 as a single device, but is not limited to this and the POS terminal 100 may be comprised of multiple devices, which may be in communication with the electronic receipt generator 2000.

[0215] The electronic receipt generator 2000 is a medium through which a consumer can view an electronic receipt on their smartphone. The electronic receipt generator 2000 can transmit data to and / or exchange data with the user device 400 using NFC wireless connection technology. According to one embodiment, the electronic receipt generator 2000 can generate or include an NFC tag and communicate using the NFC standard. However, example embodiments are not limited thereto, and the electronic receipt generator 2000 can additionally or alternatively use standard technologies such as Bluetooth, radio frequency identification (RFID), magnetic secure transmission (MST), beacons, ZigBee, etc.

[0216] The electronic receipt generator 2000 may communicate with the server 300 via a communications network (not shown). In some embodiments, the communications network may be the Internet, such that the electronic receipt generator 2000 may communicate with the server 300 to send and receive data over the Internet. However, example embodiments are not limited in this regard. In some embodiments, the electronic receipt generator 2000 may communicate with the server 300 by connecting to the Internet via Wi-Fi, although example embodiments are not limited in this regard.

[0217] Server 300 may be, for example, a dedicated server or a cloud server, although example embodiments are not limited thereto.

[0218] The server 300 may be connected to the electronic receipt generator 2000 via a communications network (not shown). The server may receive data from the electronic receipt generator 2000 and store the data in a database. The server 300 may be connected to the user device 400 via a communications network (not shown) and transmit data to the user device 400. Here, the communications network may be the Internet, although example embodiments are not limited thereto. The user device 400 may access the server 300 by accessing the Internet via Wi-Fi or a mobile network, although example embodiments are not limited thereto.

[0219] The user device 400 is a device that allows a user, who is the subject of a transaction, to view an electronic receipt. The user device 400 may include a smartphone, a smart watch, a smart device, a personal digital assistant (PDA), a wireless communication terminal, or wearable technology (e.g., a smart watch, smart glasses, etc.). However, example embodiments are not limited thereto.

[0220] The user device 400 is a device that supports NFC technology and wirelessly communicates with the electronic receipt generator 2000. According to an example embodiment, the user device 400 may support NFC standard technology. However, example embodiments are not limited thereto, and additionally or alternatively, the user device 400 may support standard technologies such as Bluetooth, radio frequency identification (RFID), magnetic secure transmission (MST), beacon, ZigBee, etc.

[0221] Referring now to Figure 5, Figure 5 is a diagram illustrating an electronic receipt-issuing computing system 20 according to an example embodiment. Referring to Figure 5, there is shown an electronic receipt-issuing computing system 20 that includes a POS terminal 100, a server 300, and a user device 400. In the embodiment of the electronic receipt-issuing computing system 20 shown in Figure 5, the POS terminal 100 includes the functionality of the electronic receipt generator 2000 (Figure 1).

[0222] The electronic receipt issuing computing system 20 of Figure 5 is similar to the electronic receipt issuing computing system 10 of Figure 1. However, according to the embodiment of Figure 5, the electronic receipt generator is not implemented as a separate device, but rather in the form of a computer program recorded on a recording medium readable by the POS terminal. In some implementations, the electronic receipt generator is implemented in the form of one or more applications stored in the memory of the POS device. Thus, according to the embodiment of Figure 5, the POS terminal 100 includes the functionality of the electronic receipt generator.

[0223] 6 illustrates a method for issuing an electronic receipt according to an example embodiment. Referring to FIG. 6, in operation 101, a user completes a transaction. In some embodiments, a completed transaction refers to a state in which all items selected by the user have been scanned by the POS terminal 100, discounts and purchase points have been applied as needed, and payment for the selected items has been received via a payment method.

[0224] In some embodiments, once a transaction is completed, the POS terminal 100 obtains transaction information. The transaction information may be a set of all information related to the transaction for which payment was received. For example, the transaction information may include the date and time of the transaction, the identification of one or more items corresponding to the transaction (e.g., the names of one or more goods and / or services), and the payment amount associated with each. The transaction information may also include the payment amount associated with all of the one or more items, the quantity of the one or more items, the total payment amount, tax, the payment type (e.g., information related to the transaction method, such as credit card information or debit card information), receipt authorization number, discount amount, the name of the transactor, the transactor number (e.g., a business number), the transactor's address, the transactor's telephone number, and the transaction number. However, the present invention is not limited thereto.

[0225] In some embodiments, the transaction information may be data, for example, recorded in a text (TXT) file format, and may include some or all of the transaction information described above. In some embodiments, the format of the transaction information may include a rich text format (RTF) file format, an extensible markup language (XML) file format, a Java Script® object notation (JSON) file format, a comma-separated values ​​(CSV) file format, and / or a tab-separated values ​​(TSV) file format. However, example embodiments are not limited thereto.

[0226] In operation 102 , the POS terminal 100 transmits transaction information to the electronic receipt generator 2000 .

[0227] Referring again to FIG. 1, in some embodiments, the POS terminal 100 transmits transaction information to the electronic receipt generator 2000 via wired or wireless communication.

[0228] Referring again to FIG. 5, in some embodiments where the POS terminal and electronic receipt generator are integrated, the transaction information is transmitted internally.

[0229] Returning again to FIG. 6, in operation 103, the electronic receipt generator 2000 generates an address corresponding to the received transaction information.

[0230] In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, although example embodiments are not limited in this respect.

[0231] In some embodiments, the electronic receipt generator 2000 may generate a unique address corresponding to each transaction. Generating a unique address corresponding to each transaction avoids collisions that may occur when the same address corresponds to multiple transactions. In some embodiments, the electronic receipt generator 2000 may generate the unique address by including a unique transaction identifier corresponding to the particular corresponding transaction in the unique address. For example, in some implementations, the address may be a URL and have the format "web address / identifier." In such implementations, the format of the identifier may have various lengths based on a combination of letters, numbers, and special characters, although example embodiments are not limited thereto.

[0232] According to one embodiment, the electronic receipt generator 2000 can generate an identifier corresponding to a transaction based on transaction information associated with the transaction. For example, the identifier can be generated based on information about the electronic receipt generator 2000 and / or based on the transaction date and time. According to a further example, the electronic receipt generator 2000 can generate the identifier using a hashing technique. A hashing technique is a technique that uses a hash function to obtain a result value corresponding to an input value. In such an example, the identifier can be a result value obtained using the transaction information as input to the hashing function.

[0233] According to example embodiments, using an identifier when generating an address (e.g., a URL) and then transmitting the address to the user device 400 via NFC ensures the following: In examples, it can be ensured that a particular electronic receipt is issued to only one user. A particular electronic receipt ensures one-to-one uniqueness of the electronic receipt based on the use of a (unique) identifier or its hash. In some examples, a particular electronic receipt is deleted by the server 300 after retrieval by the user device 400.

[0234] In an example, the result can be that an address (URL) is guaranteed to be accessed by only one user device 400, e.g., one user. If another user subsequently attempts to access the same address (URL), the address will no longer work, thereby maintaining the user's personal privacy and security.

[0235] In operation 104, the electronic receipt generator 2000 transmits the transaction information and corresponding address information to the server 300. The electronic receipt generator may also transmit a corresponding unique transaction identifier to the server 300.

[0236] In some embodiments, the electronic receipt generator 2000 may send to the server the transaction information, the entire address corresponding to the transaction information including the identifier contained in the address, other information indicative of the address, a unique transaction identifier corresponding to the transaction, other information indicative of the identifier, etc., although example embodiments are not limited thereto.

[0237] In operation 105, the server 300 stores the transaction information and corresponding address information received from the electronic receipt generator 2000. The server 300 may also store the corresponding unique transaction identifier.

[0238] In operations 104 and 105, the electronic receipt generator 2000 transmits the transaction information and the corresponding address information to the server 300, which then stores this information. The user can then view the corresponding electronic receipt, including the corresponding transaction information, on a web page corresponding to the address via the user device. According to an example embodiment, the electronic receipt is viewed on the web page using a standard web browser application, so the user does not need to install an additional mobile application on the user device to view the electronic receipt.

[0239] In operation 106, the electronic receipt generator 2000 generates an NFC signal corresponding to the address.

[0240] In some embodiments, the electronic receipt generator 2000 may transmit information to the user device 400 using NFC technology. In some embodiments, the electronic receipt generator 2000 may generate and issue a message in a specific format used for NFC. In some embodiments, the specific format may refer to a format that allows the user device 400 to receive a corresponding message containing instructions to immediately perform a predetermined action. For example, the electronic receipt generator 2000 may generate and issue an NDEF message. The NDEF message may include information to be sent to the user device 400. The NDEF message may include an address as a payload. The user device 400 may then perform a predetermined action upon receiving the NDEF message. The predetermined action may, for example, be opening a specific web page using a web browser application. The web page may be linked to the address.

[0241] 6 illustrates operation 106 as occurring after operation 105, example embodiments are not limited to this sequence of events. For example, in some embodiments, operation 105 and operation 106 may occur simultaneously. As a further example, in some embodiments, operation 105 may occur after operation 106.

[0242] In operation 107, the user device 400 receives the address by tapping the electronic receipt generator 200.

[0243] In some embodiments, the user device 400 may receive information from the electronic receipt generator 2000 via NFC. The user device 400 may include devices, applications, and / or APIs that support or facilitate supporting NFC functionality. In some embodiments, the user device 400 may receive an NDEF message that includes an address as a payload by approaching the electronic receipt generator 2000 within a few tens of centimeters.

[0244] In operation 107, once the electronic receipt generator 2000 transmits the address via NFC to the user device 400, the user device 400 can obtain information about the electronic receipt through the simple and quick action of tapping the electronic receipt generator 200. In such an embodiment, it may not be necessary to enter personal information into the POS terminal 100 to obtain the electronic receipt.

[0245] In operations 108 and 109, the user device 400 accesses the specified web page based on the received address and displays the electronic receipt.

[0246] In some embodiments, the user device 400 can access a web page linked to the received address on the Internet. The user device 400 can receive the address via an NDEF message and automatically access the web page linked to the address as a predetermined action. The server 300 may already store transaction information corresponding to the address. The server 300 can generate an electronic receipt by converting the transaction information into an electronic receipt format through a dedicated application. The server 300 can display the generated electronic receipt on the web page linked to the address. As a result, the user can view the electronic receipt by accessing the web page linked to the address via the user device 400.

[0247] In one example, upon receiving the NFC signal, the user device 400 immediately displays the electronic receipt via a web page or application page corresponding to the web page URL, without the need for an email address, text message, or pre-loaded or pre-installed application running. In one example, the user device 400 does not need to pre-install or pre-load an application. For example, the user device 400 can use, for example, a native browser, a progressive web app (PWA), or a mini-app. Mini-apps are described further below.

[0248] In examples, the user device 400 does not need to be "prepared" to receive and display electronic receipts. For example, the user device 400 can operate without having to pre-download, pre-install, or pre-load an application. For example, the user device 400 can operate without having to activate a camera to scan a QR code or exchange email addresses or phone numbers. Rather, a mini-app can be loaded as part of NFC proximity between the user device 400 and the NFC tag controller 2070.

[0249] The electronic receipt may be generated by various types of applications, such as, but not limited to, a progressive web application, a responsive web application, a rich internet application, a single page application, or a multi-page application.

[0250] An e-receipt is a type of electronic document in which transaction information is displayed based on a set of rules that follow a format defined by a provider. The provider may be the transactor associated with the e-receipt. For example, the provider may be a distributor or retailer, but example embodiments are not limited thereto. A provider is distinct from a merchant, consumer, user, or customer.

[0251] FIG. 7 illustrates an exemplary electronic receipt according to an example embodiment. As shown in FIG. 7, the electronic receipt may be displayed on a web page via a web browser application. In some embodiments, the electronic receipt may include the transaction date and time, identification information of one or more items associated with the transaction (e.g., the names of one or more goods and / or services associated with the transaction), the payment amount associated with each of the one or more items, the quantity of the one or more items, the total payment amount, tax, payment type (e.g., information regarding the transaction method, such as credit card information and / or debit card information), receipt authorization number, transactor name, transactor number (e.g., company number), transactor address, transactor telephone number, transaction number, etc. As previously mentioned, the format of the electronic receipt may be determined by the provider and is not limited to that shown in the drawings.

[0252] In some embodiments, a merchant and / or user can view an electronic receipt via a user device without installing a specific specialized application on the user device. Traditionally, viewing an electronic receipt via a user device often required installing a specific specialized application on the user device. Viewing the electronic receipt often required completing a login process via the user device. However, example embodiments include computing devices and methods for viewing an electronic receipt on a web page through a conventional web browser application without requiring the installation of a specific specialized application, registration with a website, or completion of a login process.

[0253] In some embodiments, a consumer can check the electronic receipt on the user device through a simple tap on the electronic receipt generator. Thus, according to example embodiments, a URL may be sent to the user device through an NDEF message, and the user device may directly execute the URL using a pre-defined command in the NDEF message. In this way, the user can view the electronic receipt through a web browser application as a result of a simple tap without any further action.

[0254] In some embodiments, an electronic receipt can be provided to a consumer via a user device without the consumer providing personal information such as an email address, phone number, etc. As a result, the present invention can prevent unnecessary leakage of personal information during a transaction, shorten the process and time required to issue an electronic receipt, and make it more convenient to view the electronic receipt on the screen of the user device.

[0255] In some embodiments, an electronic receipt may be provided to a user via a user device regardless of the corresponding transaction type. For example, traditionally, when a credit card company issues an electronic receipt, the user can only receive the electronic receipt if the payment was made using a credit card associated with the corresponding credit card company. However, according to example embodiments, the electronic receipt may be issued to a user device in conjunction with a POS terminal associated with the transaction, allowing the user to receive the electronic receipt regardless of the transaction type, including cash, debit card, credit card, digital wallet, etc.

[0256] In some embodiments, a user may be provided with an electronic receipt that includes multiple transaction information. Traditionally, when an electronic receipt is issued after a transaction through an associated application or via short message service (SMS), the electronic receipt may display only limited transaction information. For example, in some traditional scenarios, only the total payment amount is displayed, without detailed transaction information (e.g., identification of one or more items associated with the transaction, the quantity of the one or more items, the expenditure amount associated with each item, tax amounts, etc.). In contrast, however, according to embodiments described herein, a user may be provided with an electronic receipt that includes multiple transaction information.

[0257] 8 illustrates a method for issuing an electronic receipt according to another example embodiment. Referring to FIG. 8, in operation 201, a user has not yet initiated a transaction or the user has initiated at least a portion of a transaction.

[0258] In contrast to the method illustrated in Figure 5, at the start of the method of Figure 8 (e.g., at operation 201), the transaction has not yet been completed. At operation 201, the user has not yet paid for one or more items associated with the transaction. For example, operation 201 may correspond to a time before the first item is scanned at the POS terminal, a time when at least one item has been scanned into the POS terminal, or a time when all items have been scanned into the POS terminal but payment has not yet been made.

[0259] In operation 202 , the POS terminal 100 transmits transaction information to the electronic receipt generator 200 .

[0260] In some embodiments where the POS terminal and the electronic receipt generator are separate devices, as shown in Figure 1, the POS terminal 100 can transmit the intermediary transaction information to the electronic receipt generator 2000 via wired or wireless communication methods. In some embodiments where the POS terminal and the electronic receipt generator are integrated within the same device, as shown in Figure 5, the transaction information can be transmitted internally.

[0261] In some embodiments, interim transaction information is distinguished from completed transaction information. For example, interim transaction information may be the set of all information related to a transaction for which payment has not yet been received. For example, interim transaction information may include the date and time of the transaction, the identification of one or more items corresponding to the transaction, the payment amount associated with each of the one or more items, the quantity of the one or more items, the subtotal, the name of the transactor, the transactor number, the transactor address, the transactor telephone number, etc. However, interim transaction information may not include the total payment amount, the payment type, the amount of any promotions or discounts associated with the transaction, the total payment amount reflecting the discount, etc.

[0262] In some embodiments, the temporary transaction information may be data stored in a particular format, such as a text file containing the transaction information.

[0263] In operation 203, the electronic receipt generator 2000 generates an address corresponding to the received interim transaction information.

[0264] In some embodiments, the address may refer to a URL for accessing a website or web page on the Internet, although example embodiments are not limited in this respect.

[0265] In some embodiments, the electronic receipt generator 2000 can generate a unique address corresponding to the interim transaction information. This can avoid address collisions that may occur when the same address is generated in response to different transaction information. The electronic receipt generator 2000 can generate the unique address by including a unique transaction identifier corresponding to the interim transaction information in the address. For example, the address may have the format "web address / identifier." In such examples, the identifier format can have various lengths based on a combination of letters, numbers, and special characters, although example embodiments are not limited thereto.

[0266] In some embodiments, the electronic receipt generator 2000 can generate an identifier based on the intermediate transaction information. For example, the identifier can be generated based on information about the electronic receipt generator 2000 and the transaction date and time when the transaction information was generated. In some embodiments, the electronic receipt generator 2000 can generate the identifier using a hashing technique. In such embodiments, the hashing technique can be a technique that uses a hash function to obtain a result value corresponding to an input value. In such embodiments, the identifier can be a result value obtained through a hashing function that uses the intermediate transaction information as an input value.

[0267] In operation 204, the electronic receipt generator 2000 transmits the intermediate transaction information and the corresponding address information to the server 300.

[0268] In some embodiments, the electronic receipt generator 2000 may transmit to the server 300 the intermediate transaction information, the entire address including its corresponding identifier, other information related to the address, and other information related to the identifier, etc., although example embodiments are not limited thereto.

[0269] In operation 205, the server 300 stores the intermediate transaction information received from the electronic receipt generator 200 and information regarding the corresponding addresses.

[0270] In operation 206, the electronic receipt generator 2000 generates an NFC signal corresponding to the address.

[0271] In some embodiments, the electronic receipt generator 2000 can transmit information to the user device 400 via NFC. In some embodiments, the electronic receipt generator 2000 can generate and issue a message in a specific format used for NFC. The specific format may refer to a format that allows the user device 400, upon receiving the message, to immediately perform a predetermined action. For example, the electronic receipt generator 2000 can generate and issue an NDEF message. The NDEF message may include information to be sent to the user device 400. The NDEF message may include an address as a payload. The user device 400 can then perform a predetermined action upon receiving the NDEF message.

[0272] 8 shows operation 206 occurring after operation 205, example embodiments are not limited in this respect. For example, operation 205 and operation 206 may occur simultaneously, or operation 205 may occur after operation 206.

[0273] In operation 207, the user device 400 receives the address by tapping the electronic receipt generator 200.

[0274] In some embodiments, the user device 400 receives information from the electronic receipt generator 2000 via NFC. The user device 400 may include devices, applications, and / or application programming interfaces (APIs) that support or help support NFC functionality. In some embodiments, the user device 400 can receive an NDEF message that includes an address as a payload by coming within a few tens of centimeters of the electronic receipt generator 2000.

[0275] In operations 208 and 209, the user device 400 accesses the specified web page based on the received address and displays the provisional electronic receipt.

[0276] In some embodiments, the user device 400 can access a web page on the Internet linked to the received address. In some embodiments, the server 300 may already store intermediate transaction information corresponding to the address. The server 300 can then use an application to convert the intermediate transaction information into a provisional electronic receipt format. The server 300 can then display the generated provisional electronic receipt on the web page linked to the address. As a result, the user device 400 can view the provisional electronic receipt by accessing the web page linked to the address.

[0277] In some implementations, the provisional electronic receipt may be generated using one or more applications, such as, but not limited to, a progressive web application, a responsive web application, a rich internet application, a single-page application, and / or a multi-page application.

[0278] In some embodiments, as shown in FIG. 9, the user device 400 may not display a preliminary electronic receipt, but instead display a message such as "Receipt Preparing."

[0279] 8, at operation 210, the user completes the transaction. In some embodiments, once the transaction is completed, the POS terminal 100 may obtain completed transaction information. In some embodiments, the completed transaction information may be multiple pieces of information regarding the transaction for which payment was received.

[0280] In some embodiments, in addition to the transaction date and time, the identification of one or more items associated with the transaction, the payment amount associated with each of the one or more items, the quantity of the one or more items, the transactor name, the transactor number, the transactor address, the transactor telephone number, etc., the completed transaction information may further include information regarding the final payment amount, the final tax amount, and / or the payment type, etc.

[0281] In some embodiments, the completed transaction information may include multiple pieces of information regarding the transaction for which payment was received after discounts and / or promotions have been applied. In such embodiments, the completed transaction information may include, in addition to the other information described above, membership information, promotion information and amount, discount information and amount, final payment amount reflecting the discount amount, etc.

[0282] In some embodiments, like the preliminary transaction information, the completed transaction information may be data stored in a particular format, for example, the completed transaction information may be data that records the information in a text file format.

[0283] In operation 211 , the POS terminal 100 sends the completed transaction information to the electronic receipt generator 2000 .

[0284] 1, in some embodiments, the POS terminal 100 can transmit transaction information to the electronic receipt generator 2000 via wired or wireless communication. In embodiments where the POS terminal and the electronic receipt issuer are integrated with each other, as shown in FIG. 5, the transaction information is transmitted internally.

[0285] Referring again to FIG. 8, in operation 212, the electronic receipt generator 2000 sends the completed transaction information and corresponding address information to the server 300.

[0286] In some embodiments, the electronic receipt generator 2000 already has the intermediate transaction information and the corresponding address. In some such embodiments, the intermediate transaction information may be replaced or updated by the completed transaction information. As a result, the electronic receipt generator 2000 can use the address corresponding to the intermediate transaction information as the address corresponding to the completed transaction information. As a result, address collisions can be avoided. The electronic receipt generator 2000 can send the completed transaction information, the entire address already stored, an identifier included in the address, other information indicating the address, other information indicating the identifier, etc. to the server 300, but example embodiments are not limited thereto.

[0287] In operation 213, the server 300 updates the intermediate transaction information as completed transaction information using the information about the address sent from the electronic receipt generator 200.

[0288] At operations 214 and 215, the user device 400 accesses the specified web page based on the received address and displays the updated electronic receipt.

[0289] In some embodiments, the user device 400 can access a web page on the Internet linked to the received address. The server 300 may already have updated completed transaction information corresponding to the address stored therein. The server 300 may use an application to convert the completed transaction information into an electronic receipt format. The server 300 can then display the generated and updated electronic receipt on the web page linked to the address. The updated electronic receipt can then be viewed by accessing the web page linked to the address via the user device 400.

[0290] In some embodiments, the updated electronic receipt may be generated using one or more of a variety of applications, such as, but not limited to, a progressive web application, a responsive web application, a rich internet application, a single-page application, and / or a multi-page application.

[0291] In some embodiments, such as that shown in Figure 6, a user can view the electronic receipt after the transaction is completed by tapping the user device on the electronic receipt generator. In some embodiments, such as that shown in Figure 8, even before the transaction is completed, the user device can receive the address of the relevant web page by tapping the electronic receipt generator, and after the transaction is completed, the final electronic receipt is automatically updated and the updated electronic receipt can be viewed from the user device.

[0292] Some example embodiments may differ from those described with reference to FIGS.

[0293] For example, in operation 103 of Figure 6 and operation 203 of Figure 8, the electronic receipt generator 2000 can generate an address corresponding to the received transaction information. The address can refer to a URL for accessing a website or web page on the Internet.

[0294] However, in some embodiments, the address may refer to a deep link URL for direct access to a mobile or web application page.

[0295] In some such embodiments, the deep link URL may be generated directly by the electronic receipt generator 2000 in response to receiving the transaction information. However, example embodiments are not limited in this respect, and the electronic receipt generator 2000 may first generate a URL in response to receiving the transaction information, and then derive the deep link URL therefrom.

[0296] In some embodiments, at operations 108 and 109 in FIG. 6 and operations 214 and 215 in FIG. 8, the user device 400 accesses a specified web page based on the received address and displays the electronic receipt.

[0297] In some embodiments where the address is included in the deep link URL, the user device 400 can directly access the specified mobile application page or the specified web application page based on the received address and then display the electronic receipt. For example, the user device 400 can execute an application and access the mobile application page or the web application page linked to the received address. The user device 400 can receive the address through the NDEF message and, as a predetermined action, execute the associated application and access the web page linked to the address.

[0298] In some embodiments, if the associated application is not already installed on the user device 400, the user device 400 can access the mobile or web application page linked to the address after installing the associated application. In some such embodiments, the user device 400 can receive the address through the NDEF message and, as a predetermined action, install the associated application and access the page linked to the address.

[0299] In the example embodiments, unless expressly stated to the contrary, the word "comprises" and variations such as "comprises" or "comprising" will be understood to imply the inclusion of the stated elements but not the exclusion of other elements.

[0300] In example embodiments, a "module" may be a hardware component, such as a processor or circuitry, and / or a software component running on hardware, such as a processor.

[0301] In example embodiments, each of the components, functional blocks, or means may include one or more subcomponents. The electrical, electronic, and mechanical functions performed by the components may be implemented by various well-known devices or mechanical elements, such as electronic circuits, integrated circuits, application-specific integrated circuits (ASICs), etc., and may be implemented separately from one another or by combining two or more of them together.

[0302] Modules described as separate parts may or may not be physically separated, and parts shown as modules may or may not be physical modules, and may be located in one location or distributed across multiple network modules. Some or all of the modules may be selected according to actual requirements to achieve the objectives of the solutions of the embodiments.

[0303] Furthermore, the functional modules in the example embodiments may be integrated into a single processing module, each module may exist physically alone, or two or more modules may be integrated into a single module.

[0304] When the functions are implemented in the form of software function modules and sold or used as an independent product, the functions may be stored in a computer-readable storage medium (which may be non-transitory). Based on this understanding, the technical solutions of the example embodiments may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in the example embodiments. The aforementioned storage medium includes any medium capable of storing program code, such as a universal serial bus (USB) flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0305] In the described methods or block diagrams, boxes may represent events, steps, acts, processes, modules, messages, and / or state-based operations, etc. Although some example embodiments are described as being performed in a particular order, some steps or processes may be performed in a different order as long as changing the order of a given step does not prevent or impair the occurrence of a subsequent step. Furthermore, some of the messages or steps described may be eliminated or combined in other embodiments, and some of the messages or steps described herein may be separated into several sub-messages or sub-steps in other embodiments. Furthermore, some or all of the steps may be repeated as needed. Elements described as methods or steps may equally apply to computing devices or subcomponents, and vice versa. References to words such as “send” and “receive” may be interchanged depending on the perspective of a particular device.

[0306] The described embodiments are considered to be exemplary and not limiting. Example embodiments described as methods may equally apply to computing devices or devices, and vice versa.

[0307] The various example embodiments are merely examples and are not intended to limit the scope of the examples and example embodiments in any way. Variations of the innovations described herein will be apparent to those of ordinary skill in the art, and such variations are within the intended scope. In particular, features from one or more example embodiments may be selected to create alternative embodiments consisting of subcombinations of features not expressly described. Furthermore, features from one or more of the described example embodiments may be selected and combined to create alternative example embodiments consisting of combinations of features not expressly described. Features suitable for such combinations and subcombinations will be readily apparent to those of ordinary skill in the art. The subject matter described herein is intended to cover all appropriate modifications in technology.

Claims

1. an NFC tag controller; a communication module; a processor; at least one memory coupled to the processor, The instructions stored in the at least one memory, when executed by the processor, cause the processor to: receiving transaction information including a plurality of receipt elements corresponding to a transaction including one or more purchases and payments; generating a unique transaction identifier based on information in the transaction information; generating a URL that includes the unique transaction identifier; issuing, via the NFC tag controller, an NFC signal to the user device corresponding to an NFC Data Exchange Format (NDEF) message containing the URL as a payload; The URL includes at least a portion of the plurality of receipt elements such that the user device can generate a receipt for the transaction by parsing the URL.

2. transmitting the transaction information to a server via the communication module; 10. The computing device of claim 1, wherein upon receiving the NFC signal, the user device updates the receipt through a web page or application page corresponding to the URL without using an email address, a text message, or running a preloaded or preinstalled application.

3. The computing device of claim 1, wherein parsing the URL includes splitting the URL string into the plurality of receipt elements.

4. 3. The computing device of claim 2, wherein the transaction information and the URL are sent to the server, the URL identifying a web resource on the server corresponding to the receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information.

5. The server is a transfer rail server, and the processor further comprises: The computing device of claim 2 , further configured to receive, from the server of the transfer rail, confirmation of successful completion of a transfer card transaction corresponding to the transaction information.

6. The processor further comprises: causing the NFC tag controller to send the NFC Data Exchange Format (NDEF) message containing a string including the URL as a payload; Before transmitting the URL to the NFC tag controller, The computing device of claim 5 , further comprising: causing the NFC tag controller to transmit the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information.

7. The computing device of claim 1 , wherein the URL further includes at least a portion of the plurality of receipt elements, including a transactor name, transaction date and time information, identification information for one or more purchases, or a total payment amount.

8. The processor further comprises: determining at the computing device that an internet connection is not present; The computing device of claim 1 , wherein the user device is capable of generating the receipt for the transaction in the absence of an internet connection at the computing device by parsing the URL.

9. The computing device of claim 1 , wherein the transaction information includes a hash function applied to the transaction information.

10. The computing device of claim 1 , wherein the transaction information includes a unique identifier of the computing device, and a hash function is applied to the unique identifier.

11. the processor, prior to receiving the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information, further determining at the computing device that an internet connection is not present; The computing device of claim 5 , wherein the user device is capable of generating the receipt for the transaction in the absence of an internet connection at the computing device by parsing the URL.

12. the processor, prior to receiving the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information, further transmitting the transaction information and the URL to a second server via the communication module; The computing device of claim 5 , wherein the URL identifies a web resource corresponding to the receipt for the transaction.

13. the processor, prior to transmitting the transaction information to the server via the transfer rail, further Receive transfer card data, The computing device of claim 5 , wherein the computing device causes the transfer card data to be transmitted to the server of the transfer rail.

14. 14. The computing device of claim 13, wherein the receipt of the transferred card data is from a card reader (CR) device of the computing device, the CR device including the NFC tag controller, and the transaction information includes a unique device identifier of the computing device, the unique device identifier being that of the CR device.

15. The computing device further comprises: It has an NFC tag reader, the processor, prior to generating the URL, further receiving transfer card data via the NFC tag reader; transmitting the transfer card data to the server of the transfer rail; The computing device of claim 5 , wherein the URL further includes a unique device identifier, the unique device identifier being for the computing device.

16. The URL is received by the user device as a string, and the user device: Parsing the string into components; determining an association between at least two of the plurality of components and respective receipt element identifiers; The computing device of claim 1 , configured to generate a second receipt that includes at least two of the respective receipt element identifiers.

17. the user device is configured to receive a selection of a desired receipt element identifier prior to generation of the second receipt; The computing device of claim 16 , wherein the at least two of the respective receipt element identifiers of the second receipt correspond to the selection of the desired receipt element identifier.

18. The computing device of claim 1 , wherein the computing device is a Payment Card Industry (PCI) certified payment device.

19. 1. A computer-implemented method executed by a computing device, the method comprising: receiving transaction information including a plurality of receipt elements corresponding to a transaction including one or more purchases and payments; generating a unique transaction identifier based on information in the transaction information; generating a URL that includes the unique transaction identifier; and issuing, via an NFC tag controller, an NFC signal corresponding to an NFC Data Exchange Format (NDEF) message to the user device, the NFC signal including the URL as a payload; The URL includes at least a portion of the plurality of receipt elements such that the user device can generate a receipt for the transaction by parsing the URL.

20. Further, the transaction information is transmitted to a server via a communication module, 20. The computer-implemented method of claim 19, wherein upon receiving the NFC signal, the user device updates the receipt through a web page or application page corresponding to the URL without using an email address, a text message, or running a preloaded or preinstalled application.

21. The computer-implemented method of claim 19, wherein parsing the URL includes splitting the URL string into the plurality of receipt elements.

22. 21. The computer-implemented method of claim 20, wherein the transaction information and the URL are sent to the server, the URL identifying a web resource on the server corresponding to the receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information.

23. The server is a transfer rail server, and the method includes:

21. The computer-implemented method of claim 20, including receiving confirmation from the server of the transfer rail of successful completion of a transfer card transaction corresponding to the transaction information.

24. The method comprises: sending the NFC Data Exchange Format (NDEF) message to the NFC tag controller, the message including a string containing the URL as a payload; Before transmitting the URL to the NFC tag controller, and transmitting the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information to the NFC tag controller.

25. 20. The computer-implemented method of claim 19, wherein the URL further includes at least a portion of the plurality of receipt elements, including a transactor name, transaction date and time information, identification of one or more purchases, or a total payment amount.

26. The method further includes determining at the computing device that an internet connection is not present; 20. The computer-implemented method of claim 19, wherein the user device can generate the receipt for the transaction in the absence of an internet connection at the computing device by parsing the URL.

27. 20. The computer-implemented method of claim 19, wherein the transaction information includes a hash function applied to the transaction information.

28. 20. The computer-implemented method of claim 19, wherein the transaction information includes a unique identifier of the computing device, and a hash function is applied to the unique identifier.

29. The computer-implemented method further comprises: prior to receipt of the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information; determining at the computing device that there is no internet connection; 24. The computer-implemented method of claim 23, wherein the user device generates the receipt for the transaction in the absence of an internet connection at the computing device by parsing the URL.

30. The computer-implemented method further comprises: prior to receipt of the confirmation of the successful completion of the transfer card transaction corresponding to the transaction information; transmitting the transaction information and the URL to a second server via the communication module; 24. The computer-implemented method of claim 23, wherein the URL identifies a web resource corresponding to the receipt for the transaction.

31. The computer-implemented method further comprises: before transmitting the transaction information to the server of the transfer rail; receiving transfer card data; and transmitting the transfer card data to the server of the transfer rail.

32. 32. The computer-implemented method of claim 31, wherein the receiving of the transferred card data is from a card reader (CR) device of the computing device, the CR device including the NFC tag controller, and the transaction information includes a unique device identifier of the computing device, the unique device identifier being that of the CR device.

33. The computer-implemented method further comprises: Before generating the URL, receiving transferred card data via an NFC tag reader; transmitting the transfer card data to the server of the transfer rail; 24. The computer-implemented method of claim 23, wherein the URL further includes a unique device identifier, the unique device identifier being for the computing device.

34. The URL is received by the user device as a string of characters, and the method further comprises: parsing the string into a plurality of components at the user device; determining an association between at least two of the plurality of components and respective receipt element identifiers; and generating, at the user device, a second receipt that includes at least two of the respective receipt element identifiers.

35. The computer-implemented method further comprises: receiving a selection of a desired receipt element identifier at the user device prior to generating the second receipt at the user device; 35. The computer-implemented method of claim 34, wherein the at least two of the respective receipt element identifiers in the second receipt correspond to a selection of the desired receipt element identifier.

36. 20. The computer-implemented method of claim 19, wherein the computing device is a Payment Card Industry (PCI) certified payment device.

37. The computing device an NFC tag controller; a communication module; a processor; at least one memory coupled to the processor for storing instructions that cause the processor to perform predetermined operations; a non-transitory computer-readable medium comprising instructions that, when loaded, are stored in the at least one memory, the instructions comprising: The instructions direct the processor to: receiving transaction information including a plurality of receipt elements corresponding to a transaction including one or more purchases and payments; generating a unique transaction identifier based on information in the transaction information; generating a URL that includes the unique transaction identifier; Emitting an NFC signal to a user device via the NFC tag controller, the NFC signal corresponding to an NFC Data Exchange Format (NDEF) message containing a URL as a payload; The URL includes at least a portion of a plurality of receipt elements such that the user device can generate a first receipt for the transaction by parsing the URL.

38. The instruction to the processor: transmitting the transaction information to a server via the communication module; 38. The non-transitory computer-readable medium of claim 37, wherein upon receiving the NFC signal, the user device updates the receipt through a web page or application page corresponding to the URL without using an email address, a text message, or running a preloaded or preinstalled application.

39. The non-transitory computer-readable medium of claim 37, wherein parsing the URL includes splitting a string of the URL into the plurality of receipt elements.

Images