Method for processing payment and issuing electronic receipt through near field communication

Abstract

A computing device and method for issuing an electronic receipt. Transaction information may be received and sent to a transfer channel. The 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 on at least some of 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 channel. The URL may be sent to an NFC tag controller.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 477,690, filed on December 29, 2022, entitled “METHOD OF PROCESSING PAYMENTS AND ISSUING ELECTRONIC RECEIPTS OVER NEAR FIELD COMMUNICATION,” PCT Patent Application No. PCT / KR2022 / 014622, filed on September 29, 2022, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS,” Korean Patent Application No. 10-2022-0037255, filed on March 25, 2022, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS,” and Korean Patent Application No. 10-2022-0037255, filed on March 25, 2022, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS,” and Korean Patent Application No. 10-2022-0037255, filed on January 11, 2022, entitled “METHOD OF ISSUING ELECTRONIC The present application is also a continuation-in-part of PCT Patent Application No. PCT / KR2022 / 014622, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS”, filed on September 29, 2022, which claims the benefit of priority of Korean Patent Application No. 10-2022-0037255, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS”, filed on March 25, 2022, and Korean Patent Application No. 10-2022-0003963, entitled “METHOD OF ISSUING ELECTRONIC RECEIPTS”, filed on January 11, 2022. Technical Field

[0003] Example embodiments relate to providing an electronic receipt (e-receipt or receipt), for example, using near field communication (NFC) technology to provide an electronic receipt at the time of sale. Background Art

[0004] When a consumer completes a transaction associated with the purchase of goods or the use of services, the consumer receives a receipt. In conventional systems, a point of sale (POS) terminal can quickly issue a paper receipt, and an electronic receipt can be provided to the consumer in the future. The disadvantages of paper receipts include the risk of personal information leakage, the challenge of receipt management efficiency, and the cost of generating printed receipts. Electronic receipts are generally preferred because electronic receipts provide assurance of personal information, are easier to retain and manage, have low production costs, and are environmentally friendly. An efficient computing device and method for providing electronic receipts in a timely manner is desired. In conventional systems, providing electronic receipts in a timely manner may require that the user device is "ready" to display the electronic receipt. For example, the transaction recipient may need to pre-install an application, activate the user device camera to scan an OR code, and / or exchange an email address or phone number with the electronic receipt provider. These conditions create obstacles to the timely issuance of electronic receipts. For example, the transaction recipient may carry a user device with him, but the user device may not have the necessary applications installed. For example, this may occur when the user device is new or the transaction recipient is unfamiliar with its user device. In existing receipt and payment systems, user device registration may be required to obtain an electronic receipt. This registration may include providing personal information, such as an email address, phone number, payment instrument number, or account information. Therefore, a computing device and method that provides an electronic receipt at the time of a transaction without personal information or prior registration is desired.

[0005] Prompt provision of electronic receipts may also require that the POS terminal at the transaction location has an Internet connection, which in many cases may not be available. For example, many transactions occur at subway terminals, on airline flights, during network failures, and other situations where Internet connections are unavailable. Therefore, computing devices and methods that provide electronic receipts at the time of a transaction without a network connection are also desired. Summary of the invention

[0006] Examples described herein can provide a computing device and method for issuing an electronic receipt so that a transaction recipient can immediately receive the electronic receipt. For example, the electronic receipt can be received at a user device.

[0007] Examples described herein may allow a computing device to issue an electronic receipt without a network connection.

[0008] Examples described herein may allow a transaction recipient to use a web browser application to receive and view a corresponding electronic receipt immediately after a transaction occurs. Examples described herein may allow a transaction recipient to receive and view a corresponding electronic receipt on a user device immediately after a transaction occurs.

[0009] Conventionally, issuing an electronic receipt requires pre-installation of a specific application on the consumer's smartphone, or requires logging in. However, since the electronic receipt according to some example embodiments can be checked in the form of a web page through a browser, the consumer does not need to pre-install a separate application, register on a website, or log in to receive the electronic receipt.

[0010] An example embodiment is a computing device comprising: a communication module; a processor; and at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receive transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; send 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 a confirmation of successful completion of a debit card transaction corresponding to the transaction information from the transfer rail; and send the URL to an NFC tag controller.

[0011] In an example embodiment of any of the computing devices above, the URL also includes at least some of a plurality of receipt elements, the at least some of the plurality of receipt elements including names of transaction parties, a transaction date, identification of one or more purchases, or a total payment amount.

[0012] In an example embodiment of any of the computing devices described above, the processor is further caused to: determine that there is no Internet connection at the computing device; wherein sending includes sending a URL to the user device via the NFC tag controller; wherein the URL includes at least some of the plurality of receipt elements, enabling the user device to generate a receipt for the transaction by parsing the URL without accessing the URL on the Internet.

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

[0014] In an example embodiment of any of the computing devices 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.

[0015] In an example embodiment of any of the computing devices above, prior to receiving confirmation of successful completion of the debit card transaction, the processor is further caused to: determine that an internet connection is not present at the computing device.

[0016] In an example embodiment of any of the computing devices above, prior to receiving confirmation of successful completion of the debit card transaction corresponding to the transaction information, the processor is further caused to: send the transaction information and a URL to a server via the communication module, wherein the URL identifies a network resource corresponding to a receipt for the transaction.

[0017] In an example embodiment of any of the computing devices above, before sending the transaction information to the transmission channel, the processor is further caused to: receive debit card data from a card reader (CR) device, the CR device including an NFC tag controller; and send the debit card data to the transmission channel, wherein the unique device identifier is a unique device identifier of the CR device.

[0018] In an example embodiment of any of the computing devices described above, the computing device further includes: an NFC tag controller, wherein the processor is further caused to: generate, via the NFC tag controller, an NFC Data Exchange Format (NDEF) message including a URL as a payload; and transmit, via the NFC tag controller, an NFC signal corresponding to the NDEF message.

[0019] In an example embodiment of any of the computing devices above, the computing device further comprises: an NFC tag reader; wherein, prior to generating the URL, the processor is further caused to: receive debit card data via the NFC tag reader; and send the debit card data to the transmission channel, wherein the URL further comprises a unique device identifier, wherein the unique device identifier is a unique device identifier of the computing device.

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

[0021] Another example embodiment is a computing device comprising: a communication module; a processor; and at least one memory, the at least one memory being coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receive transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising multiple receipt elements; determine that there is no Internet connection; as a result of determining that there is no Internet connection, generate a uniform resource locator (URL), the uniform resource locator comprising at least some of the multiple receipt elements, the at least some comprising transaction party names, transaction date, identification 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 so that the user device can generate a receipt for the transaction by parsing the URL without accessing the URL on the Internet.

[0022] In an example embodiment of any of the computing devices above, the processor is further caused to: determine that an Internet connection exists; and send the transaction information and a URL to the server via the communication module, wherein the URL identifies a network resource corresponding to a second receipt of the transaction.

[0023] Another example embodiment is a user device comprising: a processor; and at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the user device to: receive a uniform resource locator (URL) as a string that identifies a network 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 corresponding receipt element identifiers; and generate a second receipt containing at least two of the corresponding receipt element identifiers.

[0024] In any of the above example embodiments of the user device, the user device is further caused to: store the second receipt at the first location.

[0025] In any of the above example embodiments of the user device, the user device is further caused to: access a network resource corresponding to a first receipt for the transaction identified by the URL; and store the first receipt at the first location.

[0026] In an example embodiment of any of the user devices above, the user device is further caused to: receive a selection of desired receipt element identifiers prior to generating the second receipt, wherein at least two of the corresponding receipt element identifiers in the second receipt correspond to the selection of desired receipt element identifiers.

[0027] In an example embodiment of any of the user devices above, a selection of a desired receipt element identifier is received via a graphical user interface.

[0028] In an example embodiment of any of the user devices above, the URL includes a unique transaction identifier and at least the names of the transaction parties, a transaction date, an identification of one or more purchases, or a total payment amount.

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

[0030] Another example embodiment is a computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and a payment, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; sending the transaction information to a delivery channel; 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 uniform resource locator (URL) comprising the unique transaction identifier and at least some of the plurality of receipt elements, at least some of the plurality of receipt elements comprising names of transaction parties, a date of the transaction, identification of one or more purchases, or a total payment amount; receiving a confirmation of successful completion of a debit card transaction corresponding to the transaction information from the delivery channel; and sending the URL to an NFC tag controller.

[0031] In an example embodiment of any of the computer implemented methods above, prior to receiving confirmation of successful completion of the debit card transaction corresponding to the transaction information, the method further comprises: sending the transaction information and a URL to a server, wherein the URL identifies a network resource corresponding to a receipt for the transaction.

[0032] In an example embodiment of any of the computer-implemented methods above, before sending the transaction information to the transmission channel, the method further includes: receiving debit card data from a card reader (CR) device, the CR device including an NFC tag controller; and sending the debit card data to the transmission channel, wherein the unique device identifier is a unique device identifier of the CR device.

[0033] In an example embodiment of any of the computer-implemented methods above, the computer-implemented method further comprises: generating, via the NFC tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message.

[0034] In an example embodiment of any of the computer-implemented methods above, prior to generating the URL, the method further comprises: receiving debit card data via an NFC tag reader; and sending the debit card data to the transmission channel.

[0035] Another example embodiment is a non-transitory computer-readable medium containing instructions that, when executed by a processor, cause the processor to: receive transaction information corresponding to a transaction, the transaction including one or more purchases and a payment, the transaction information including a plurality of receipt elements, the plurality of receipt elements including date information and time information; send the transaction information to a delivery channel; 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 and at least some of the plurality of receipt elements, at least some of the plurality of receipt elements including names of transaction parties, a date of the transaction, identification of one or more purchases, or a total payment amount; receive a confirmation of successful completion of a debit card transaction corresponding to the transaction information from the delivery channel; and send the URL to an NFC tag controller.

[0036] Another example embodiment is a non-transitory computer-readable medium containing instructions that, when executed by a processor, cause the processor to: receive a uniform resource locator (URL) as a string that identifies a network 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 corresponding receipt element identifiers; and generate a second receipt containing at least two of the corresponding receipt element identifiers.

[0037] Another example embodiment is a computer-implemented method comprising: receiving a uniform resource locator (URL) as a string that identifies a network resource corresponding to a transaction; parsing the string into a plurality of components; determining an association between at least two of the plurality of components and corresponding receipt element identifiers; and generating a second receipt containing at least two of the corresponding receipt element identifiers.

[0038] Another example embodiment is a computing device comprising: an NFC tag controller; a communication module; a processor; and at least one memory, the at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receive, via the communication module, transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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; transmit, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and wherein the user device, upon receiving the NFC signal, immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, a text message, or execution of a preloaded or preinstalled application.

[0039] Another example embodiment is a computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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 comprising the unique transaction identifier; sending the transaction information and the URL to a server; generating, via an NFC tag controller, an NFC Data Exchange Format (NDEF) message comprising the URL as a payload; transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and wherein the user device, upon receiving the NFC signal, immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, a text message, or execution of a preloaded or preinstalled application.

[0040] Another example embodiment is a non-transitory computer-readable medium containing instructions that, when executed by a processor, cause the processor to: receive, via a communication module, transaction information corresponding to a transaction, the transaction including one or more purchases and payments, the transaction information including multiple receipt elements, the multiple 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; transmit, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and wherein the user device, upon receiving the NFC signal, immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, a text message, or execution of a preloaded or preinstalled application. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Example embodiments are described in detail below with reference to the accompanying drawings:

[0042] Figure 1 is a schematic diagram illustrating an electronic receipt issuance computing system according to an example embodiment;

[0043] Figure 2 is a diagram showing how the Figure 1 A block diagram showing an example of the internal configuration of an electronic receipt generator;

[0044] Figure 3 is a diagram showing how the Figure 1 A block diagram showing an example of the internal configuration of a server;

[0045] Figure 4 is a diagram showing how the Figure 1 A block diagram showing an example of an internal configuration of a user device;

[0046] Figure 5 is a schematic diagram illustrating an example of an electronic receipt issuing computing system according to an example embodiment;

[0047] Figure 6 is a flow chart of an example method of issuing an electronic receipt according to an example embodiment;

[0048] Figure 7 is a diagram of an example display of an electronic receipt on a user device according to an example embodiment;

[0049] Figure 8 is a flow chart of an example method of issuing an electronic receipt according to an example embodiment;

[0050] Fig. 9 is a diagram illustrating an example display of a waiting room on a user device according to an example embodiment;

[0051] Fig.10 is a schematic diagram illustrating components of an electronic receipt issuance computing system according to an example embodiment;

[0052] Fig.11 is a flow chart of an example method for generating an electronic receipt according to an example embodiment;

[0053] Fig.12 is a schematic diagram illustrating components of an electronic receipt issuance computing system according to an example embodiment;

[0054] Fig.13 is a flow chart of an example method for generating an electronic receipt according to an example embodiment;

[0055] Fig.14 is a schematic diagram illustrating components of an electronic receipt issuance computing system according to an example embodiment;

[0056] Fig.15 is a flow chart of an example method for generating a second electronic receipt according to an example embodiment;

[0057] Fig.16 shows an example display screen of a receipt management user interface according to an example embodiment; and

[0058] Fig.17 An example display screen 1500 of a second electronic receipt is shown according to an example embodiment.

[0059] The same reference numerals may be used throughout the drawings to represent the same elements and features. DETAILED DESCRIPTION

[0060] At least some example embodiments include a method of issuing an electronic receipt (e-receipt or receipt) so that a user can conveniently view the electronic receipt on a smartphone and thus a business operator can use the method.

[0061] Since the example embodiments can be applied with various variations and 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 a specific mode of practice, and all changes, equivalents, and substitutes that do not depart from the technical scope of the example embodiments should be recognized. In the detailed description, when it is considered that some detailed explanations of the related art may unnecessarily obscure the clarity of the example embodiments, these explanations will be omitted.

[0062] An example embodiment is a computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and a payment, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; sending 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 information and time information, and / or using a unique device identifier; generating a uniform resource locator (URL) comprising the unique transaction identifier and at least some of the plurality of receipt elements, at least some of the plurality of receipt elements comprising names of transaction parties, a date of the transaction, identification of one or more purchases, or a total payment amount; receiving a confirmation of successful completion of a debit card transaction corresponding to the transaction information from the transfer rail; and sending the URL to an NFC tag controller.

[0063] Another example embodiment is a computer-implemented method comprising: receiving a uniform resource locator (URL) as a string that identifies a network resource corresponding to a transaction; parsing the string into a plurality of components; determining an association between at least two of the plurality of components and corresponding receipt element identifiers; and generating a second receipt containing at least two of the corresponding receipt element identifiers.

[0064] Another example embodiment is a computing device comprising: an NFC tag controller; a communication module; a processor; and at least one memory, the at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receive, via the communication module, transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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 the 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; transmit, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and wherein the user device, upon receiving the NFC signal, immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, a text message, or execution of a preloaded or preinstalled application.

[0065] Another example embodiment is a computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising multiple receipt elements, the multiple receipt elements comprising 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 comprising the unique transaction identifier; sending the transaction information and the URL to a server; generating, via an NFC tag controller, an NFC Data Exchange Format (NDEF) message comprising the URL as a payload; transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and wherein the user device, upon receiving the NFC signal, immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, a text message, or execution of a preloaded or preinstalled application.

[0066] Another example embodiment is a method for issuing an electronic receipt, the method comprising: receiving transaction information related to a transaction, generating an address corresponding to the transaction information, storing the transaction information in 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, an electronic receipt generated in response to the transaction information via the transmitted address.

[0067] Another example embodiment is a computing device comprising: a communication module; a processor; and at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to perform any of the methods described herein.

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

[0069] Fig.10 is a diagram illustrating an electronic receipt issuing computing system 1000 according to an example embodiment. Fig.10 , the electronic receipt issuing computing system 1000 shown includes a POS terminal 100, an electronic receipt generator 2000, a server 300, a transmission channel 1010, an issuing computing device 1020, and a user device 400. The electronic receipt generator 2000 is a computing device. Fig.10 In the example shown, the electronic receipt generator 2000 may operate as a PIN Transaction Service Point of Interaction (PTS POI) device.

[0070] POS terminal 100, server 300, electronic receipt generator 2000, transmission channel 1010, issuer computing device 1020 and user device 400 can communicate through a network (not shown) (e.g., a wireless network). In some implementations, the wireless network can be the Internet. In some implementations, POS terminal 100, server 300, electronic receipt generator 2000, transmission channel 1010, issuer computing device 1020 and user device 400 can be connected to the Internet via Wi-Fi technology. User device 400 may include an NFC tag reader. In other words, user device 400 may include NFC reading or background NFC tag reading capabilities.

[0071] As shown, the POS terminal 100 can communicate with an electronic receipt generator 2000, which can be operated to generate an electronic receipt. Such communication can be via a wired connection (e.g., such as a USB connection). Such communication can be via a wireless connection (e.g., such as Bluetooth TM ). The POS terminal 100 may include a physical token reader. The physical token reader may be described as an NFC tag reader.

[0072] The electronic receipt generator 2000 can communicate with a transmission channel 1010, which relays transaction data to an appropriate sender computing device 1020. This communication can be via a network (e.g., a wireless network). The transmission channel 1010 can also be referred to as a payment channel. In an example, the transmission channel 1010 is a payment processor, platform, server, or network infrastructure that allows electronic money transfers between a payer and a payee. In an example, transfers can be made regardless of country, currency, digital payment methods, or whether the payer or payee is a business or consumer. Each payment channel differs in how it performs the process based on payment type, speed, technology, or geographic location. Examples of transmission channels 1010 include automated clearing houses (ACH), MasterCard, Visa (VISA) (and other major credit card providers), PayPal, RTP networks, blockchains, SWIFT, and SEPA.

[0073] The POS terminal 100 and / or the electronic receipt generator 2000 may be associated with an acquirer, and the communication between the POS terminal 100 and / or the electronic receipt generator 2000 and the transmission channel 1310 may be performed through a back-end acquirer computing device. The POS terminal 100 may be located at a location associated with a transaction party (e.g., a merchant). For example, a merchant may be a store, a restaurant, a gym, etc. The acquirer may be a commercial bank that accepts deposits associated with transactions conducted at the POS terminal 100 and facilitates the settlement of these deposits and deposits into an account associated with the merchant. In some examples, the POS terminal 100 may also issue an electronic receipt for a legal tender (cash) transaction.

[0074] Although Fig.10 1010, but in practice the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transmission channels. For example, the transmission channel 1010 may include Amex TM Visa TM and / or Mastercard TM Any one or a combination of. Other transmission channels may also be used. The POS terminal 100, the electronic receipt generator 2000, and / or a back-end acquirer computing device in communication with the POS terminal 100 and / or the electronic receipt generator 2000 may determine which transmission channel to use after obtaining data from a physical token (e.g., a value transfer card or a user device 400 having a representation of a payment card that has been engaged with a physical token reader provided at the POS terminal 100). For example, the POS terminal / acquirer computing device may determine whether the physical token is associated with a Visa TM associated, and in response, can select Visa TM Payment gateway, or it can instead determine the physical token with Mastercard TM Link and select Mastercard TM Payment channel.

[0075] After identifying the transmission channel 1010, the POS terminal / electronic receipt generator / acquirer computing device sends a message to the transmission channel 1010. The message can be sent over the network. The message may include a value amount representing the amount of value to be transferred to complete the transaction, and physical token data, for example, a primary account number (PAN) associated with the physical token. The transmission channel 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transmission channel 1010 routes the message received from the POS terminal 100 and / or the 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 rejected based on predefined rules. For example, the rules may consider any one or more of the following: whether the cardholder has available funds, whether the merchant is of an allowed type, whether the transaction violates any spending restrictions, etc.

[0076] When the issuer computing device 1020 determines whether to approve or deny the transaction, the issuer computing device 1020 sends a message indicating the result of the determination to the POS terminal 100 and / or the electronic receipt generator via the transmission channel 1010. The result may then be displayed or otherwise output at the POS terminal 100.

[0077] Figure 2 It is shown Figure 1 and Fig.10 2 is a block diagram of an example of the internal configuration of the electronic receipt generator 2000 shown in FIG. 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.

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

[0079] The network interface 2010 provides an interface for transmitting an address (eg, URL) and its corresponding transaction information to the server 300 in conjunction with a communication network.

[0080] The communication module 2020 allows the electronic receipt generator 2000 to communicate with other computers or computing devices and / or various communication networks. For example, the communication module 2020 may allow the electronic receipt generator 2000 to send or receive communication signals. The communication signals may be sent or received according to one or more protocols or according to one or more standards. For example, the communication module 2020 may allow the electronic receipt generator 2000 to communicate via a cellular data network, for example, according to one or more standards (such as, Global Mobile Communications Computing Device (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimization (EVDO), Long Term Evolution (LTE), etc.). Additionally or alternatively, the communication module 2020 may allow the electronic receipt generator 2000 to communicate using NFC, via Wi-Fi (TM), using Bluetooth (TM), 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 a component 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 .

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

[0082] 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 transaction information, generating a message corresponding to the address and programming the message to 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 part of one or more application programs within the memory 2030.

[0083] The controller 2050 is a central processing unit (CPU) and can control processes related to generating an electronic receipt 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.

[0084] The 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, but example embodiments are not limited thereto.

[0085] The address generator 2060 may generate the unique address by including therein a unique transaction identifier corresponding to the transaction information. For example, in some implementations, the address may have a format of "www.domain / unique_transactionidentifier / receipt elements". The "receipt elements" 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, but example embodiments are not limited thereto.

[0086] According to an embodiment, the electronic receipt generator 2000 may generate an identifier (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 transaction time. According to another embodiment, the electronic receipt generator 2000 may generate the identifier using a hashing technique. A hashing technique refers to a technique for obtaining a result value corresponding to an input value using a hash function. In some such embodiments, the identifier may be a result value obtained by a hashing technique using the transaction information as an input value. However, the method of generating an identifier according to an example embodiment is not limited thereto.

[0087] The NFC tag controller 2070 generates a message corresponding to the address and transmits the message as an NFC signal by controlling the NFC tag. According to an embodiment, the message may be in a specific format for NFC. In some implementations, the specific format may refer to a format that enables the user device 400 that receives the corresponding message to immediately perform a predetermined action. For example, the NFC tag controller 2070 may generate and transmit an NDEF message including information to be transmitted to the user device 400. In some implementations, the address is included in the NDEF message as a payload. In such an implementation, the user device 400 may perform a predetermined operation upon receiving the NDEF message. For example, the predetermined operation may be to open a web page linked to the address through a web browser application.

[0088] Figure 3 It is shown Figure 1 and Fig.10 3 is a block diagram of an example of the internal configuration of the server 300 shown in FIG. Figure 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.

[0089] The communication module 310 allows the server 300 to communicate with other computers or computing devices and / or various communication networks. For example, the communication module 310 may allow the server 300 to send or receive communication signals. Communication signals may be sent or received according to one or more protocols or according to one or more standards. For example, the communication module 310 may allow the server 300 to communicate via a cellular data network, for example, according to one or more standards (such as, global mobile communication computing device (GSM), code division multiple access (CDMA), evolution data optimization (EVDO), long term evolution (LTE), etc.). Additionally or alternatively, the communication module 310 may allow the server 300 to communicate using NFC, via Wi-Fi (TM), using Bluetooth (TM) or via some combination of one or more networks or protocols. In some embodiments, all or part of the communication module 310 may be integrated into a component of the server 300. For example, the communication module 310 may be integrated into a communication chipset.

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

[0091] The memory 320 may perform a function of temporarily or permanently storing data processed by the controller 340. In some implementations, the memory 320 may include a magnetic storage medium and / or a flash memory medium, but example embodiments are not limited thereto.

[0092] Program storage 330 may store one or more programs consisting of commands that instruct the controller to perform one or more processes, as will be discussed further below. In some embodiments, program storage 330 may form part of memory 320. In some embodiments, one or more programs stored in program storage may form at least a part of one or more application programs within memory 2030.

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

[0094] In some embodiments, the controller 340 may include various types of devices capable of processing data, such as one or more processors. In an example embodiment, a "processor" may refer to a data processing device, such as embedded in hardware, having a physically constructed circuit to perform functions represented by computing code and / or computer program instructions.

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

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

[0097] These components are merely examples, and example embodiments are not limited thereto. In other words, the server 300 may further include additional components, or some of the above components may be omitted, as required.

[0098] Figure 4 is a diagram showing a user device 400 ( Figure 1 and Fig.10 ) is a block diagram of an example of the internal configuration of Figure 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.

[0099] The network interface 410 may provide an interface for receiving electronic receipts in conjunction with a communications network.

[0100] The communication module 420 allows the user device 400 to communicate with other computers or computing devices and / or various communication networks. For example, the communication module 420 may allow the user device 400 to send or receive communication signals. Communication signals may be sent or received according to one or more protocols or according to one or more standards. For example, the communication module 420 may allow the user device 400 to communicate via a cellular data network, for example, according to one or more standards (such as, global mobile communication computing device (GSM), code division multiple access (CDMA), evolution data optimization (EVDO), long term evolution (LTE), etc.). Additionally or alternatively, the communication module 420 may allow the user device 400 to communicate using NFC, via Wi-Fi (TM), using Bluetooth (TM) or via some combination of one or more networks or protocols. In some embodiments, all or part of the communication module 420 may be integrated into a component of the user device 400. For example, the communication module 420 may be integrated into a communication chipset.

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

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

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

[0104] Program storage 450 may store control software for performing tasks such as receiving a message from electronic receipt generator 2000, checking the format of the received message, and accessing an address included in the NDEF message through a web browser application as a predetermined action when the received message is an NDEF message.

[0105] The controller 460 may be a CPU, and may control processes related to displaying an electronic receipt 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.

[0106] Reference now Fig.11 , which shows a flow chart of an example method 1100 for issuing an electronic receipt according to an example embodiment. The example method 1100 may be performed by a computing device (eg, an electronic receipt generator 2000 ( ) that may operate as a PTS POI device). Fig.10 When operating as a PTS POI device, the electronic receipt generator may include a PCI-certified payment module, which may reside in the memory of the PTS POI device.

[0107] Specifically, the example method 1100 may be performed by the electronic receipt generator 2000 ( Fig.10 ) of the controller 340( Figure 3 ) processor to execute.

[0108] At operation 1110, the computing device receives transaction information corresponding to the transaction. For example, the transaction information may be received from the POS terminal 100 ( Fig.10 ) receives transaction information. The transaction may include one or more items and a payment. The transaction information may include multiple receipt elements, which may include date information and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), JavaScript TM Object Notation (JSON), delimited text files, etc.

[0109] At operation 1120, the computing device sends a signal to the transmission channel 1010 ( Fig.10 ) to send the transaction information. The transaction information may be sent via a module (e.g., a PCI-certified payment module that may reside in a memory of a computing device). Transmission channel 1010 ( Fig.10 ) can be simultaneously from the POS terminal 100 ( Fig.10 ) receives debit card data. The debit card data may include a value amount representing an amount of value to be transferred to complete the transaction, and physical token data (e.g., a primary account number (PAN) associated with the physical token).

[0110] 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 information and time information associated with the transaction. In the electronic receipt generator 2000 ( Fig.10 ) is a PTS POI device, the unique device identifier may be a unique device identifier of the PTS POI device. In an example, the unique device identifier is a unique device identifier of the computing device. In an example, the unique device identifier is a serial number, an ID number, an International Mobile Equipment Identity (IMEI), or a Media Access Control (MAC) address of the computing device or the PTS POI device. In an example, a combination (concatenation) of date information, time information, and the unique device identifier may be used to generate a unique transaction identifier.

[0111] At operation 1140, the computing device generates a unique URL. The unique URL may be based on a unique transaction identifier. The unique URL may identify a network resource corresponding to an electronic receipt for the transaction. The network resource may reside on a server. The unique URL may be in the form of: "www.domain / unique transaction identifier / receiptelements". The "receipt elements" of the URL may be associated with transaction information.

[0112] In some embodiments, the computing device may send the transaction information to the server 300 via the communication module. Fig.10 Then, the server 300 ( Fig.10 ) can generate a first electronic receipt at a network resource associated with the URL. In some embodiments, the computing device may be unable to communicate with the server 300, for example, due to lack of Internet connection. In such embodiments, when communication between the computing device and the server is restored, the computing device can send transaction information to the server.

[0113] At operation 1150, the computing device receives the data from the transmission channel 1010 ( Fig.10 ) receives confirmation of successful completion of the debit card transaction corresponding to the transaction information. The confirmation can be received via a module (e.g., a PCI-certified payment module that can reside in a memory of the computing device). The computing device sends a confirmation of successful completion of the debit card transaction corresponding to the transaction information to NFC tag controller 2070. The confirmation can be included in an NDEF message. If delivery channel 1010 rejects the transaction, the computing device sends a rejection of the debit card transaction corresponding to the transaction information to NFC tag controller 2070.

[0114] At operation 1160, the computing device may send the URL to the NFC tag controller 2070. In some embodiments, such as when the computing device is a PTS POI device, the NFC tag controller 2070 may be integrated into the PTS POI device. Alternatively, in some embodiments, the NFC tag controller 2070 may be located outside the computing device.

[0115] After receiving the URL, the NFC tag controller 2070 may generate an NDEF message including the URL as a payload. Then, the NFC tag controller 2070 may transmit an NFC signal having the URL as a payload.

[0116] In some embodiments, the NFC signal may be an NDEF formatted NFC tag with a URL as a payload. Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Apple TM Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Apple TM The NDEF formatted tag contains the URL of the App Clip link. Alternatively, in some embodiments, the NDEF formatted NFC tag can be, for example, an Android TM Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Android TM Instant App Links URL. Alternatively, in some embodiments, the NDEF formatted NFC tag can be, for example, an NDEF formatted tag with a mini App Links URL. In some embodiments, the payload can be a URL based on a progressive web app. Examples include Apple TM "AppClips", Google TM “Instant Apps” and Snapchat TM “Snap Minis”.

[0117] Once the NFC signal is transmitted, the user device 400 ( Fig.10 ) can receive the NFC signal. For example, the shopper can touch the user device 400 ( Fig.10 ), and receives the URL via the NFC signal. The user device 400 ( Fig.10 ) can receive an NFC signal with a URL as payload via an NFC tag reader.

[0118] After operation 1160, once the NFC signal is transmitted, the user device 400 ( Fig.10 ) can receive the NFC signal. For example, the shopper can touch the electronic receipt generator 2000 ( Fig.10 ) on the user device 400 ( Fig.10 ), and receives the URL via the NFC signal. The user device 400 ( Fig.10 ) can receive an NFC signal with a URL as payload via an NFC tag reader.

[0119] In some embodiments, once 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 network resource associated with the URL. As described, the URL can be in the following form: "www.domain / unique transactionidentifier / receipt elements". The "receipt elements" of the URL can be related to the transaction information. The network resource can include the first electronic receipt.

[0120] For example, you can use progressive web applications, responsive web applications (e.g., JavaScript TM Driven web applications), via rich internet applications, via single page applications, or through multi-page applications.

[0121] In some embodiments, the user device 400 ( Fig.10 ) may include an application for storing and displaying receipts. In some such embodiments, the user device 400 ( Fig.10 ) can include Apple TM Universal Links for iOS TM In such an embodiment, once the user device 400 ( Fig.10 ) receives the NFC signal, Apple TM The universal link may cause the first electronic receipt to be displayed and / or stored in an application for storing and displaying receipts. Fig.10 ) Probably not iOS TM Mobile phones can include deep links (e.g., Android TM Application Link). In such an embodiment, once the user device 400 ( Fig.10) receives the NFC signal, the deep link can cause the first electronic receipt to be displayed and / or stored in an application for storing and displaying receipts. The application can display the first electronic receipt in a format determined by the transaction party associated with the transaction.

[0122] In some embodiments, the user device 400 ( Fig.10 ) may not include an application for storing and displaying receipts. In some such embodiments, on the user device 400 ( Fig.10 ) includes Apple TM Universal Links for iOS TM In the case of mobile phones, Apple TM Universal links can direct users to Apple TM App Store to download an application for storing and displaying receipts. In some such embodiments, on the user device 400 ( Fig.10 ) is not iOS TM In the case of mobile phones, deep linking (e.g., Android TM The application link) can direct the user to a mobile application store to download an application for storing and displaying receipts. Fig.10 ) is iOS TM In some of these embodiments of mobile phones, the user device 400 ( Fig.10 ) can receive Apple TM In some such embodiments, when the user device is a non-iOS TM In the case of a mobile phone, the user device 400 ( Fig.10 ) can receive an instant application link and can launch the instant application. In some such embodiments, the user device 400 ( Fig.10 ) can receive mini-app links and can launch mini-apps.

[0123] In some embodiments, the network NFC framework can be used to send a message to the user device 400 ( Fig.10 ) provide one or more receipts.

[0124] In some embodiments, the user device 400 ( Fig.10 ) can launch a web browser application to present an output including a first electronic receipt at the location of the unique URL. The format of the first electronic receipt can be a format determined by the transaction parties regarding the first electronic receipt. The first electronic receipt can be generated using the transaction data and can be displayed by the user device using an application. For example, the application can be a progressive web application, a responsive web application (e.g., a JavaScript TMThe first electronic receipt may be saved by the corresponding application to the first location.

[0125] In some embodiments, as described, the application may be provided by Apple TM Universal links or related non-iOS TM Mobile application or web application launch. TM In the case of application launch, the application can be launched via deep link or through Android TM The application link is launched. In such an embodiment, the application can display the first electronic receipt in a format determined by the transaction party with respect to the first electronic receipt. The first electronic receipt can be saved to the first location by the corresponding application.

[0126] Reference now Fig.12 , which is a diagram illustrating an electronic receipt issuing computing system 1200 according to an example embodiment. Fig.12 , the electronic receipt issuing computing system 1200 shown includes a computing device operating as a POS terminal 100, and includes an electronic receipt generator 2000 ( Fig.10 ) function. The illustrated electronic receipt issuing computing system further includes a server 300, a card reader (CR) device 1210, a transmission channel 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 NFC-based PCI software-based PIN entry (SPoC) device reader. 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.

[0127] The computing device, server 300, CR device 1210, transmission channel 1010, issuing computing device 1020 and user device 400 operating as POS terminal 100 can communicate through a network (not shown) (e.g., a wireless network). In some implementations, the wireless network can be the Internet. In some implementations, the computing device, server 300, CR device 1210, transmission channel 1010, issuing computing device 1020 and user device 400 operating as POS terminal 100 can be connected to the Internet via Wi-Fi technology. User device 400 may include an NFC tag reader. In other words, user device 400 may include NFC reading or background NFC tag reading capabilities.

[0128] As shown, the CR device 1210 can communicate with a computing device operating as a POS terminal 100, which can be operated to generate an electronic receipt. Such communication can be via a wired connection (e.g., such as a USB connection). Such communication can be via a wireless connection (e.g., such as a Bluetooth connection). TM )conduct.

[0129] A computing device operating as a POS terminal 100 may communicate with a transmission channel 1010, which relays transaction data to an appropriate issuer computing device 1020. Such communication may be via a network (e.g., a wireless network). The transmission channel 1010 may also be referred to as a payment channel.

[0130] The computing device operating as the POS terminal 100 may be associated with an acquirer, and the communication between the computing device operating as the POS terminal 100 and the transmission channel 1010 may be conducted through the backend acquirer computing device. The computing device operating as the POS terminal 100 may be located at a location associated with a merchant. For example, the merchant may be a store, a restaurant, a gym, etc. The acquirer may be a commercial bank that accepts deposits associated with transactions conducted at the computing device operating as the POS terminal 100 and facilitates the settlement of these deposits and deposits them into an account associated with the merchant.

[0131] Although Fig.12 1010, but in practice the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transmission channels. For example, the transmission channel 1010 may include Amex TM Visa TM and / or Mastercard TM Any one or a combination of. Other transmission channels may also be used. A computing device operating as a POS terminal 100 and / or a back-end acquirer computing device communicating with a computing device operating as a POS terminal 100 may determine which transmission channel to use after obtaining data from a physical token (e.g., a value transfer card or a mobile device having a representation of a payment card that has been engaged with a CR device 1210 provided at the POS terminal 100). For example, the POS terminal / acquirer computing device may determine whether the physical token is associated with a Visa TM associated, and in response, can select Visa TM Payment gateway, or it can instead determine the physical token with Mastercard TM Link and select Mastercard TM Payment channel.

[0132] After identifying the transmission channel 1010, the computing device / acquirer computing device operating as the POS terminal 100 sends a message to the transmission channel 1010. The message can be sent over the network. The message may include a value amount representing the amount of value to be transferred to complete the transaction and physical token data (e.g., a primary account number (PAN) associated with the physical token). The transmission channel 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transmission channel 1010 routes the message received from the computing device operating 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 rejected based on predefined rules. For example, the rules may consider any one or more of the following: whether the cardholder has available funds, whether the merchant is of an allowed type, whether the transaction violates any spending restrictions, etc.

[0133] When issuer computing device 1020 determines whether to approve or deny the transaction, issuer computing device 1020 sends a message indicating the result of the determination to the computing device operating as POS terminal 100 via transmission channel 1010. The result may then be displayed or otherwise output at POS terminal 100.

[0134] 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 computer, a smartphone, etc. Fig.12 In the embodiment of the electronic receipt issuing computing system 1200 shown, the computing device operating as the POS terminal 100 includes an electronic receipt generator 2000 ( Fig.10 ) function.

[0135] The user device 400 may include a mobile wallet that stores payment card representations. The physical token may be connected to one or more accounts (e.g., bank accounts) that store data and / or resources accessible to the cardholder. For example, the physical token may be associated with a bank account and / or a credit card account. The physical token may act as a credit or debit card. The physical token may be used to make purchases at a point-of-sale terminal. Such a physical token may be configured for touch-to-pay, where the physical token is placed within the communication range of a physical token reader (e.g., CR device 1210) to allow physical token data to be read from the physical token.

[0136] The user device 400 may be configured for near field communication (NFC) payment processing or for other types of wireless communication-based payment processing.

[0137] The CR device 1210 communicates with a computing device operating as a POS terminal 100. The CR device 1210 may be configured to read a physical token, such as a debit card or a mobile device having a representation of a debit card stored thereon. In this way, the CR device 1210 may be configured to receive debit card data. The physical token reader may be or may include a card slot that facilitates communication with a physical token through physical contact, and / or may be a contactless reader (e.g., a near field communication (NFC) reader) that facilitates communication with a 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.

[0138] Reference now Fig.13 , which shows a flow chart of an example method 1300 for issuing an electronic receipt according to an example embodiment. The example method 1300 can be performed by a computing device (e.g., a computing device ( Fig.12 )) is executed. A computing device ( Fig.12 ) may include a PCI-certified payment module, which may reside in the memory of the computing device. In some embodiments, the computing device ( Fig.12 ) can be a CPoC device and / or an SPoC device.

[0139] Specifically, the example method 1300 may be performed by a computing device ( Fig.12 ) of the controller 340( Figure 3 ) processor to execute.

[0140] Example method 1300 and Fig.11 The example method 1100 differs in that the example method 1300 Fig.11 The example method 1100 includes two additional operations 1112 and 1114 between operations 1110 and 1120.

[0141] At operation 1110, the 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 a plurality of receipt elements, which may include date information and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), JavaScript, or other formats. TM Object Notation (JSON), delimited text files, etc.

[0142] In some embodiments, after operation 1110, the computing device may activate the CR device 1210 ( Fig.12 ) to obtain debit card information.

[0143] In operation 1112, the computing device obtains the CR device 1210 ( Fig.12 ) to receive the debit card data. The debit card data may be received via a wired connection (e.g., such as a USB connection). The debit card data may be received via a wireless connection (e.g., such as a Bluetooth TM )take over.

[0144] 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 debit card or a mobile device having a representation of a debit card stored thereon. Thus, the CR device 1210 ( Fig.12 ) may be configured to receive debit card data. The physical token reader may be or may include a card slot that facilitates communication with the physical token through physical contact, and / or may be a contactless reader (e.g., 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. Then, the CR device 1210 ( Fig.12 ) may be operable to communicate debit card data to a computing device.

[0145] At operation 1114, the computing device sends the debit card data to the transmission channel 1010 ( Fig.12 The debit card data may be sent via a module (e.g., a PCI-certified payment module that may reside in a memory of a computing device). The debit card data may be sent over a network. The debit card data may include a value amount representing an amount of value to be transferred to complete the transaction and physical token data (e.g., a primary account number (PAN) associated with the physical token).

[0146] At operation 1120, the computing device sends the transaction information to the transmission channel 1010 ( Fig.10 ). The transaction information may include multiple receipt elements, which may include date information and time information. The transaction information may be in a text-based flat file format, such as Extensible Markup Language (XML), JavaScript TM Object Notation (JSON), delimited text files, etc.

[0147] 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.

[0148] 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 information and time information associated with the transaction. In some embodiments, the unique device identifier may be a unique identifier of the computing device or the CR device 1210 ( Fig.12 ). In the example, the unique device identifier is a computing device or CR device 1210 ( Fig.12 )’s serial number, ID number, International Mobile Equipment Identity (IMEI), or Media Access Control (MAC) address.

[0149] At operation 1140, the computing device generates a unique URL. The unique URL may be based on a unique transaction identifier. The unique URL may identify a network resource corresponding to an electronic receipt for the transaction. The network resource may reside on server 300 ( Fig.12 ). The unique URL may be in the form of: "www.domain / unique transaction identifier / receiptelements". The "receipt elements" of the URL may be related to the transaction information.

[0150] In some embodiments, the computing device may send the transaction information to the server via the communication module. Then, the server 300 ( Fig.12 ) can generate a first electronic receipt at a network resource associated with the URL. In some embodiments, the computing device may be unable to communicate with the server, for example, due to lack of Internet connectivity. In such embodiments, the computing device may queue the transaction information to be sent between the computing device and the server 300 ( Fig.12 ) is restored.

[0151] At operation 1150, the computing device receives a confirmation of successful completion of the debit card transaction corresponding to the transaction information from the transmission channel. The confirmation can be received via a module (e.g., a PCI-certified payment module that can reside in a memory of the computing device). The computing device sends the confirmation of successful completion of the debit card transaction corresponding to the transaction information to the NFC tag controller 2070. The confirmation can be included in an NDEF message. If the transmission channel 1010 denies the transaction, the computing device sends a denial of the debit card transaction corresponding to the transaction information to the NFC tag controller 2070.

[0152] At operation 1160, the computing device may send the unique URL to the NFC tag controller 2070. In some embodiments, the NFC tag controller 2070 may be integrated into the CR device 1210 ( Fig.12 In some such embodiments, the computing device may send a unique URL to the CR device 1210 ( Fig.12 ).

[0153] After receiving the URL, the NFC tag controller 2070 may generate an NDEF message including the URL as a payload. Then, the NFC tag controller 2070 may transmit an NFC signal having the URL as a payload. In some embodiments, the CR device 1210 ( Fig.12 ) can transmit an NFC signal with a URL as payload.

[0154] In some embodiments, the NFC signal may be an NDEF formatted NFC tag with a URL as a payload. Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Apple TM Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Apple TM The NDEF formatted tag contains the URL of the application clip link. Alternatively, in some embodiments, the NDEF formatted NFC tag can be, for example, an Android TM Alternatively, in some embodiments, the NDEF formatted NFC tag may be, for example, an Android TM Instant App Link URL in NDEF formatted tag. Alternatively, in some embodiments, the NDEF formatted NFC tag can be, for example, an NDEF formatted tag with a mini App Link URL. In some embodiments, the payload can be a URL based on a progressive web app.

[0155] Reference now Fig.14 , which is a diagram illustrating an electronic receipt issuing computing system 1400 according to an example embodiment. Fig.14 , the electronic receipt issuing computing system 1400 shown includes a computing device operating as a POS terminal 100, and includes an electronic receipt generator 2000 ( Fig.10) function. The illustrated electronic receipt issuance computing system further includes a server 300, a transmission channel 1010, an issuer computing device 1020, and a user device 400. In some embodiments, the computing device of the electronic receipt issuance computing system 1400 operating as a POS terminal 100 may be described as a commercial off-the-shelf PCI contactless payment (CPoC) device, a commercial off-the-shelf mobile payment (MPoC) device, a tap to phone device, and / or a tap on phone device.

[0156] The computing device, server 300, transmission channel 1010, issuer computing device 1020, and user device 400 operating as POS terminal 100 can communicate through a network (not shown) (e.g., a wireless network). In some implementations, the wireless network can be the Internet. In some implementations, the computing device, server 300, transmission channel 1010, issuer computing device 1020, and user device 400 operating as POS terminal 100 can be connected to the Internet via Wi-Fi technology. User device 400 may include an NFC tag reader. In other words, user device 400 may include NFC reading or background NFC tag reading capabilities.

[0157] The computing device operating as the POS terminal 100 may be configured to operate as a physical token reader, which may be referred to as an NFC tag reader. That is, the computing device operating as the POS terminal 100 may be operated to read a physical token, such as a debit card or a user device 400 having a representation of a debit card stored thereon. Thus, the computing device operating as the POS terminal 100 may be configured to receive debit card data. The physical token reader may be a contactless card reader (e.g., 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. The computing device operating as the POS terminal 100 may include an NFC tag controller.

[0158] A computing device operating as POS terminal 100 may be operable to generate an electronic receipt.

[0159] A computing device operating as a POS terminal 100 may communicate with a transmission channel 1010, which relays transaction data to an appropriate issuer computing device 1020. Such communication may be via a network (e.g., a wireless network). The transmission channel 1010 may also be referred to as a payment channel.

[0160] The computing device operating as the POS terminal 100 may be associated with an acquirer, and the communication between the computing device operating as the POS terminal 100 and the transmission channel 1010 may be conducted through the backend acquirer computing device. The computing device operating as the POS terminal 100 may be located at a location associated with a transaction party (e.g., a merchant). For example, the merchant may be a store, a restaurant, a gym, etc. The acquirer may be a commercial bank that accepts deposits associated with transactions conducted at the computing device operating as the POS terminal 100 and facilitates the settlement of these deposits and deposits them into an account associated with the merchant.

[0161] Although Fig.14 1010, but in practice the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transmission channels. For example, the transmission channel 1310 may include Amex TM Visa TM and / or Mastercard TM Any one or a combination of. Other transmission channels may also be used. A computing device operating as a POS terminal 100 and / or a back-end acquirer computing device in communication with a computing device operating as a POS terminal 100 may determine which transmission channel to use after obtaining data from a physical token (e.g., a value transfer card or a mobile device having a payment card representation that has been engaged with the computing device operating as a POS terminal 100). For example, the POS terminal / acquirer computing device may determine whether the physical token is in correspondence with a Visa TM associated, and in response, can select Visa TM Payment gateway, or it can instead determine the physical token with Mastercard TM Link and select Mastercard TM Payment channel.

[0162] After identifying the transmission channel, the computing device / acquirer computing device operating as the POS terminal 100 sends a message to the transmission channel. The message can be sent over the network. The message may include a value amount representing the amount of value to be transferred to complete the transaction and physical token data (e.g., a primary account number (PAN) associated with the physical token). The transmission channel 1010 identifies the associated issuer based on the physical token data and communicates with the identified issuer to process the transaction. More specifically, the transmission channel 1010 routes the message received from the computing device operating as the POS terminal 100 to the issuer computing device 1020 of the identified issuer. Then, the issuer computing device 1020 determines whether the transaction is approved or rejected based on predefined rules. For example, the rules may consider any one or more of the following: whether the cardholder has available funds, whether the merchant is of an allowed type, whether the transaction violates any spending restrictions, etc.

[0163] When issuer computing device 1020 determines whether to approve or deny the transaction, issuer computing device 1020 sends a message indicating the result of the determination to the computing device operating as POS terminal 100 via transmission channel 1010. The result may then be displayed or otherwise output at POS terminal 100.

[0164] The computing device operating as the POS terminal 100 may be referred to as a PCI CPoC device, an MPoC device, a touch phone device, and / or a touch on phone device, and may include a PCI-certified payment module. For example, the computing device operating as the POS terminal 100 may be a laptop, a tablet computer, a smartphone, etc. Fig.14 In the embodiment of the electronic receipt issuing computing system 1400 shown, the computing device operating as the POS terminal 100 includes an electronic receipt generator 2000 ( Fig.10 ) function.

[0165] The user device 400 may include a mobile wallet storing a representation of a payment card. The physical token may be connected to one or more accounts (e.g., bank accounts) storing data and / or resources accessible to the cardholder. For example, the physical token may be associated with a bank account and / or a credit card account. The physical token may act as a credit card or debit card. The physical token may be used to make purchases at a point of sale terminal. Such a physical token may be configured for touch-to-pay, wherein the physical token is placed within the communication range of a physical token reader (e.g., a computing device operating as a POS terminal 100) to allow physical token data to be read from the physical token.

[0166] The user device 400 may be configured for near field communication (NFC) payment processing or for other types of wireless communication-based payment processing.

[0167] Method 1300( Fig.13 ) can be executed by the electronic receipt issuing computing system 1400.

[0168] It should be noted that the electronic receipt issuing computing system 1400 and the electronic receipt issuing computing system 1200 ( Fig.12 ) is that Fig.14 The computing device operating as the POS terminal 100 is configured to operate as a physical token reader. The physical token reader can also be described as an NFC tag reader.

[0169] Therefore, in executing method 1300 ( Fig.13 ), in operation 1112( Fig.13 ) at the POS terminal 100, as a computing device ( Fig.14 ) can directly receive debit card data, rather than via a separate card reader (such as reference electronic receipt issuing computing system 1200 ( Fig.12 ) described in the description.

[0170] Reference again Fig.13 At operation 1130, the computing device generates a unique transaction identifier. As previously described, in some examples, a hash function applied to the transaction information may be used to generate the unique transaction identifier. Alternatively, as further described, in some examples, a unique transaction identifier may be generated using a unique device identifier and / or date information and time information associated with the transaction.

[0171] At operation 1130, the computing device ( Fig.14 ) can use a computing device ( Fig.14 ) (e.g., a unique device identifier of a PCI CPoC device, an MPoC device, a touch phone device, and / or a touch on phone device) as the unique device identifier.

[0172] After operation 1160, once the NFC signal is transmitted, the user device 400 ( Fig.12 , Fig.14 ) can receive the NFC signal. For example, the shopper can touch the POS terminal 100 ( Fig.12 , Fig.14 ) on the user device 400 ( Fig.12 , Fig.14 ), and receives the URL via the NFC signal. The user device 400 ( Fig.12 , Fig.14 ) can receive an NFC signal with a URL as payload via an NFC tag reader.

[0173] Once the user device 400 ( Fig.12 , Fig.14 ) receives the NFC signal, the NFC tag can launch a web browser application. The web browser application can display a web resource associated with the URL. As described, the URL can be in the following form: "www.domain / unique transaction identifier / receipt elements". The "receiptelements" of the URL can be related to the transaction information. The web resource can include the first electronic receipt.

[0174] For example, you can use progressive web applications, responsive web applications (e.g., JavaScript TM Driven web applications), via rich internet applications, via single page applications, or via multi-page applications to launch network resources.

[0175] In some embodiments, the user device 400 ( Fig.12 , Fig.14 ) may include an application for storing and displaying receipts. In some such embodiments, the user device 400 ( Fig.12 , Fig.14 ) can include Apple TM Universal Links for iOS TM In such an embodiment, once the user device 400 ( Fig.12 , Fig.14 ) receives the NFC signal, Apple TM The universal link may cause the first electronic receipt to be displayed and / or stored in an application for storing and displaying receipts. Fig.12 , Fig.14 ) Probably not iOS TM mobile phones, and can include deep links (e.g., Android TM Application Link). In such an embodiment, once the user device 400 ( Fig.12 , Fig.14 ) receives the NFC signal, the deep link can cause the first electronic receipt to be displayed and / or stored in an application for storing and displaying receipts. The application can display the first electronic receipt in a format determined by the transaction party associated with the transaction.

[0176] In some embodiments, the user device 400 ( Fig.12 , Fig.14 ) may not include an application for storing and displaying receipts. In some such embodiments, on the user device 400 ( Fig.12 , Fig.14 ) includes Apple TM Universal Links for iOS TM In the case of mobile phones, Apple TM Universal links can direct users to Apple TM App Store to download an application for storing and displaying receipts. In some such embodiments, on the user device 400 ( Fig.12 , Fig.14 ) is not iOS TM In the case of mobile phones, deep linking (e.g., Android TM An application link) can direct the user to a mobile application store to download an application for storing and displaying receipts. In some such embodiments, on the user device 400 ( Fig.12 , Fig.14 ) is iOS TM In the case of a mobile phone, the user device 400 ( Fig.12 , Fig.14 ) can receive Apple TM In some such embodiments, when the user device is a non-iOS TM In the case of a mobile phone, the user device 400 ( Fig.12 , Fig.14 ) can receive an instant application link and can launch the instant application. In some such embodiments, the user device 400 ( Fig.12 , Fig.14 ) can receive mini-app links and can launch mini-apps.

[0177] In some embodiments, the network NFC framework can be used to send a message to the user device 400 ( Fig.12 , Fig.14 ) provide one or more receipts.

[0178] In some embodiments, the user device 400 ( Fig.12 , Fig.14 ) can launch a web browser application to render output at the location of the unique URL. The rendered output can include a first electronic receipt. The format of the first electronic receipt can be a format determined by the transaction parties regarding the first electronic receipt. The first electronic receipt can be generated using the transaction data and can be displayed by the user device using an application. For example, the application can be a progressive web application, a responsive web application (e.g., a JavaScript TMThe first electronic receipt may be saved by the corresponding application to a first location. For example, the first location may be on the user device 400 ( Fig.12 , Fig.14 ) of the memory 430( Figure 4 )middle.

[0179] In some embodiments, as described, the application may be provided by Apple TM Universal links or related non-iOS TM Mobile application or web application launch. TM In the case of application launch, the application can be launched via deep link or through Android TM The application link is launched. In such an embodiment, the application may display the first electronic receipt in a format determined by the transaction party with respect to the first electronic receipt. The first electronic receipt may be saved by the corresponding application to a first location. For example, the first location may be in the user device 400 ( Fig.12 , Fig.14 ) of the memory 430( Figure 4 )middle.

[0180] In some implementations, the POS terminal 100 ( Fig.12 , Fig.14 ) and server 300( Fig.12 , Fig.14 ) may not exist between the POS terminal 100 and the user device 400. In some such embodiments, the POS terminal 100 generates a URL, and the user device 400 is able to generate a second electronic receipt for the transaction by parsing the URL without accessing the URL on the Internet. In some examples, the second electronic receipt may also be used as a temporary electronic receipt, which is eventually replaced by the first electronic receipt. For example, when there is an Internet connection through the computing device 300, the POS terminal 100 uploads the transaction information of the first electronic receipt (or, in an alternative example, the first electronic receipt itself) to the server 300. The server 300 associates the URL with the first electronic receipt. Thereafter, the user device 400 can obtain the first electronic receipt. In some examples, the second electronic receipt is the final receipt. For example, when there is an Internet connection through the computing device 300, only a URL is generated, wherein the URL contains enough information so that the user device 400 can generate a second electronic receipt for the transaction by parsing the URL without accessing the URL on the Internet.

[0181] The second electronic receipt may be received by the user device 400 ( Fig.12 , Fig.14) is generated based on the URL received by the user device 400, for example, by parsing. As described, the URL may be in the form of: "www.domain / unique transaction identifier / receipt elements", and the "receipt elements" of the URL may be related to the transaction information. The second electronic receipt may be generated by the user device 400 ( Fig.12 , Fig.14 ) using the information contained in the URL. For example, the app can be an App Clip, an Instant App, or a Mini App. For example, the app may not need to be pre-installed or pre-loaded.

[0182] In some embodiments, the second electronic receipt may be stored at a first location. The first location may be the user device 400 ( Fig.12 , Fig.14 ) of the memory 430( Figure 4 ).

[0183] In some implementations, the user may choose to keep the second electronic receipt and abandon the use of the first electronic receipt. In some implementations, the user may temporarily refer to the second electronic receipt and may use the second electronic receipt when the first electronic receipt is available (e.g., when the POS terminal 100 ( Fig.12 , Fig.14 ) and server 300( Fig.12 , Fig.14 ) to obtain and use the first electronic receipt. In some implementations, when the user device 400 receives the first electronic receipt, the first electronic receipt can be stored in the first location by the user device 400. In this way, the second electronic receipt (which can also be represented as a temporary electronic receipt in this example) can be replaced by the first electronic receipt at the first location.

[0184] Reference now Fig.15 , which is a flow chart of an example method 1500 for generating a second electronic receipt according to some embodiments. The second electronic receipt may also be represented as a temporary electronic receipt. The operation may be performed by the user device 400 ( Figure 1 ) is executed, and more specifically, by the controller 460 ( Figure 4 ) is executed by a processor of the user device 400. For example, the memory 430 ( Figure 4 ) in the processor executable instructions in the controller 460 ( Figure 4 ) when executed by one or more processors of the device, the user device 400 can be configured to perform the example method 1300 or a portion thereof.

[0185] Fig.15The example method 1500 may be operable to immediately generate a second electronic receipt for a transaction, which may also be represented as a temporary electronic receipt for the transaction. The second electronic receipt may be generated and displayed in a variety of situations, including situations where the user device is not conventionally "ready" to display electronic receipts. For example, the example method 1500 does not require the user to pre-install an application, register an account, activate a user device camera, and / or exchange an email address or phone number with an electronic receipt provider. The example method 1500 does not require an Internet connection at the user device.

[0186] Fig.15 The example method 1500 may be operable to: Figure 1 ) immediately generates a second electronic receipt for the transaction without including a web browser application.

[0187] Fig.15 The example method 1500 may operate to generate a second electronic receipt immediately when an Internet connection and / or a web browser application is available.

[0188] In some embodiments, the second electronic receipt may be stored at a first location. The first location may be the user device 400 ( Figure 1 ) of the memory 430( Figure 4 ).

[0189] In some implementations, the user may choose to keep the second electronic receipt and abandon the use of the first electronic receipt. In some implementations, the user may temporarily reference the second electronic receipt and may obtain and use the first electronic receipt when the first electronic receipt is available (e.g., when an Internet connection is available to the POS terminal 100). In some implementations, upon receipt of the first electronic receipt, the first electronic receipt may be stored in the first location. In this way, the second electronic receipt (which may also be represented as a temporary electronic receipt in this example) may be replaced by the first electronic receipt at the first location.

[0190] At operation 1502, the user device 400 ( Figure 1 ) receives a URL as a string. For example, the URL can be of the form: "www.domain / unique transaction identifier / receipt elements". For example, an example URL can be represented by: web address / unique transaction identifier / 764983309-22.12.13-1107-CC-xxxxxxxx1234-KimsConvenience-26.75-3.

[0191] At operation 1504, the user device 400 ( Figure 1 ) parses the string into multiple components representing various receipt elements. In some embodiments, the user device 400 ( Figure 1 ) can parse the string into tokens according to the defined convention. For example, in some implementations, after receiving the URL, the user device 400 ( Figure 1 ) may ignore the first set of characters, such as the characters up to and including the second forward slash. In other words, in the context of the example URL above, the user device 400 ( Figure 1 ) The first set of characters "www.domain / unique transaction identifier / receipt elements" can be ignored.

[0192] In some implementations, after ignoring the first set of characters, the user device 400 ( Figure 1 ) can split the remaining characters into multiple components representing various receipt elements. For example, user device 400 ( Figure 1 ) can split the remaining characters into their components at each hyphen. In other words, in the context of the example URL above, the user device 400 ( Figure 1 ) can split the remaining characters into their components: 764983309; 22.12.13; 1107;

[0196] CC;

[0197] xxxxxxxx1234;

[0198] KimsConvenience; 26.75;

[0200] 3.

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

[0202] In some implementations, the user device 400 ( Figure 1 ) can determine an association between each of a plurality of components representing respective receipt elements and a receipt element identifier in a plurality of receipt identifiers. The user device can determine the association by associating a first component in the plurality of components with a first electronic receipt element identifier, associating a second component in the plurality of components with a second electronic receipt element identifier, associating a third component in the plurality of components with a third receipt element identifier, and so on. However, those skilled in the art will appreciate that any number of methods for determining associations between the plurality of components and the receipt element identifiers can be used.

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

[0204] In some implementations, the ordered list of multiple receipt element identifiers can be customized by the user. For example, in a particular implementation, the ordered list can include 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 transaction party name, a transaction party number (e.g., a business number), a transaction party address, a transaction party phone number, or a transaction number.

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

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

[0207] Reference now Fig.16 , which shows an example display screen 1600 of a receipt management user interface according to an example embodiment. The receipt management user interface can be displayed on the user device 400. The example display screen 1600 includes a first title 1630 titled "Receipt Element Selection - Offline Version". The example display screen 1600 also 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 column on the left side of the display screen 1600. Fig.16In the example, the first ordered list of receipt element identifiers is: receipt authorization number; transaction date; transaction time; payment type, payment amount, item quantity; subtotal amount, tax amount, discount amount, transaction party name, transaction party number; transaction party address, transaction party phone number; transaction number.

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

[0209] For example, Fig.16 The first seven check boxes are shown highlighted, indicating that the first seven corresponding receipt element identifiers are selected. Fig.16 Example desired receipt element identifiers are as follows: receipt authorization number; 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. Selection of the first seven receipt element identifiers as desired receipt element identifiers may cause the desired receipt element identifiers and their associated components in one or more components to be displayed in a corresponding provisional receipt. Not selecting the remaining receipt element identifiers may cause the remaining receipt element identifiers and their associated components in multiple components to not be displayed in a corresponding provisional receipt.

[0210] Reference now Fig.17 , which shows an example display screen 1700 of a second electronic receipt according to an example embodiment. The example display screen 1700 includes a title 1730 (e.g., "Receipt - Offline Version"). The example display screen 1700 also includes a second ordered list 1710 of multiple receipt element identifiers on the left side of the display screen 1700. Fig.17 In the example of , the second ordered list of receipt element identifiers is: receipt authorization number; transaction date; transaction time; payment type, payment amount, and item quantity. The second ordered list of receipt elements 1710 corresponds to Fig.16 Select the first seven receipt element identifiers shown.

[0211] Component list 1720 is displayed in a column on the right side of display screen 1700. Each component of component list 1720 is associated with a receipt element in second ordered list 1710 of receipt elements.

[0212] Fig.17 Display 1700 shows the following associations between receipt element identifiers and component parts:

[0213] Receipt Authorization Number: 764983309

[0214] Transaction date: 22.12.13

[0215] Trading time: 11:07am

[0216] Payment type: CCxxxx1234

[0217] Transaction recipient name: KimsConvenience

[0218] Payment amount: $26.75

[0219] Number of items: 3

[0220] As previously combined Fig.15 As explained in operation 1506 of FIG. 1 , in some implementations, the user device 400 ( Figure 1 ) can determine an association between each of the plurality of components and a receipt element identifier in the plurality of receipt identifiers. The determination can be made by associating a first component in the plurality of components with a first electronic receipt element identifier, associating a second component in the plurality of components with a second electronic receipt element identifier, associating a third component in the plurality of components with a third receipt element identifier, and so on. However, those skilled in the art will appreciate that any number of methods of determining associations between receipt element identifiers and components can be used.

[0221] After generating the second electronic receipt, the user device 400 ( Fig.14 ) can access a network resource corresponding to the first electronic receipt of the transaction identified by the URL. For example, when the Internet connection is finally detected (e.g., restored), the POS terminal 100 has subsequently uploaded the transaction information of the first electronic receipt (or, in an alternative example, the first electronic receipt itself) to the server 300. In some embodiments, the first electronic receipt can be stored by the user device 400 at the first location.

[0222] In some embodiments, the user device 400 ( Fig.14 ) may display the second electronic receipt. The application may store the second electronic receipt in the first location. Subsequently, the application may replace the second electronic receipt with the first electronic receipt by storing the first electronic receipt in the first location.

[0223] In some embodiments, the user device 400 may launch a related mini-application mobile application to display the first electronic receipt. The format of the first electronic receipt may be a format determined by the transaction party regarding the first electronic receipt. The first electronic receipt may be generated using the transaction data. Examples of related mini-applications may include AppleTM App Clip, Android TM Instant applications, etc. In an example, the mini-application is not pre-installed or pre-loaded on the user device 400.

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

[0225] The POS terminal 100, the electronic receipt generator 2000, the server 300, and the user device 400 can communicate via a network (not shown) (e.g., a wireless network). In some implementations, the wireless network can be the Internet. In some implementations, the POS terminal 100, the electronic receipt generator, the server 300, and the user device 400 can be connected to the Internet via Wi-Fi technology.

[0226] According to some example embodiments, POS terminal 100 is a device that can process transactions. A transaction can correspond to one or more purchases (one or more items and / or one or more services) and payments. In this article, example embodiments can be described with respect to the purchase of items, and it can be understood that services are also applicable, and charitable donations and goodwill are also applicable. For example, a transaction can correspond to exchanging a payment amount with one or more items (e.g., one or more goods and / or one or more services). In some embodiments, a transaction can correspond to the purchase of one or more items. In addition to processing transactions, POS terminal 100 can also determine its transaction results and can manage information related to transactions.

[0227] 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.

[0228] In some embodiments, as shown, the electronic receipt generator is a device separate from the POS terminal 100. In such an embodiment, the POS terminal 100 and the electronic receipt generator 2000 can send and receive data through a communication computing device. For example, the communication computing device may include a wired communication computing device through a universal serial bus (USB) cable or a wireless communication computing device such as Wi-Fi or Bluetooth. However, example embodiments are not limited to this.

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

[0230] In some embodiments, although Figure 1 The POS terminal 100 is shown as a single device, but example embodiments are not limited thereto, and the POS terminal 100 may include a plurality of devices that may communicate with the electronic receipt generator 2000 .

[0231] The electronic receipt generator 2000 is a medium that allows consumers to check electronic receipts using smartphones. The electronic receipt generator 2000 can use NFC wireless connection technology to transmit data to the user device 400 and / or exchange data with the user device 400. According to an embodiment, the electronic receipt generator 2000 can generate or include an NFC tag and can communicate using the NFC standard. However, example embodiments are not limited thereto, and the electronic receipt generator 2000 can additionally or alternatively use standards such as Bluetooth, radio frequency identification (RFID), magnetic secure transmission (MST), Beacon, Zigbee, etc.

[0232] The electronic receipt generator 2000 may communicate with the server 300 via a communication network (not shown). In some implementations, the communication network may be the Internet, so that the electronic receipt generator 2000 may communicate with the server 300 via the Internet to transmit and receive data. However, example embodiments are not limited thereto. In some implementations, the electronic receipt generator 2000 may communicate with the server 300 by connecting to the Internet via Wi-Fi, but example embodiments are not limited thereto.

[0233] For example, the server 300 may be a dedicated server or a cloud server. However, example embodiments are not limited thereto.

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

[0235] The user device 400 is a device through which a user who is a transaction subject can check an electronic receipt. The user device 400 may include a smart phone, a smart watch, a smart device, a personal digital assistant (PDA), a wireless communication terminal, wearable technology (e.g., a smart watch, smart glasses), etc. However, example embodiments are not limited thereto.

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

[0237] Reference now Figure 5 , which is a diagram illustrating an electronic receipt issuing computing system 20 according to an example embodiment. Figure 5 , the electronic receipt issuing computing system 20 shown includes a POS terminal 100, a server 300 and a user device 400. Figure 5 In the embodiment of the electronic receipt issuing computing system 20 shown, the POS terminal 100 includes an electronic receipt generator 2000 ( Figure 1 ) function.

[0238] Figure 5 The electronic receipt issuing computing system 20 and Figure 1 The electronic receipt issuing computing system 10 is similar. However, according to Figure 5 In some embodiments, the electronic receipt generator is not implemented as a separate device, but is implemented in the form of a computer program recorded on a recording medium that can be read by the POS terminal. In some implementations, the electronic receipt generator is implemented in the form of one or more application programs stored in the memory of the POS device. Figure 5 In the embodiment of the present invention, the POS terminal 100 includes the functionality of an electronic receipt generator.

[0239] Figure 6 is a diagram illustrating a method of issuing an electronic receipt according to an exemplary embodiment. Figure 6 At operation 101, the user completes the transaction. In some embodiments, the completion of the transaction refers to a state where all items selected by the user have been scanned by the POS terminal 100, discounts and purchase points have been appropriately applied, and payment for the selected items has been received by the payment method.

[0240] In some embodiments, when the transaction is completed, the POS terminal 100 obtains transaction information. The transaction information may be a collection of all information about the transaction for which payment has been received. For example, the transaction information may include the transaction date and transaction time, the identification of one or more items corresponding to the transaction (e.g., the name of one or more goods and / or services), the payment amount associated with each of the one or more items, the payment amount associated with all of the one or more items, the quantity of the one or more items, the total payment amount, the tax amount, the payment type (e.g., information about the transaction method, such as credit card information and / or debit card information, etc.), the receipt authorization number, the discount amount, the transaction party name, the transaction party number (e.g., business number), the transaction party address, the transaction party phone number, the transaction number, etc. However, the example embodiments are not limited thereto.

[0241] In some embodiments, the transaction information may be data and may be recorded, for example, in a text (TXT) file format and may include some or all of the above transaction information. 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 JavaScript TM Object Notation (JSON) file format, comma separated value (CSV) file format and / or tab separated value (TSV) file format. However, example embodiments are not limited thereto.

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

[0243] Reference again Figure 1 In some embodiments, the POS terminal 100 transmits the transaction information to the electronic receipt generator 2000 via a wired communication method or a wireless communication method.

[0244] Reference again Figure 5 In some embodiments where the POS terminal and electronic receipt generator are integrated, transaction information is transmitted internally.

[0245] Return again Figure 6 , at operation 103, the electronic receipt generator 2000 generates an address corresponding to the received transaction information.

[0246] In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, but example embodiments are not limited thereto.

[0247] 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 may avoid conflicts that may occur when the same address corresponds to more than one transaction. In some embodiments, the electronic receipt generator 2000 may generate a unique address by including a unique transaction identifier corresponding to a specific corresponding transaction in the unique address. For example, in some embodiments, the address may be a URL and may have the format "website address / identifier". In such an implementation, the format of the identifier may have various lengths based on a combination of letters, numbers, and special characters, but example embodiments are not limited thereto.

[0248] According to an embodiment, the electronic receipt generator 2000 may generate an identifier corresponding to the transaction based on transaction information associated with the transaction. For example, the identifier may be generated based on information about the electronic receipt generator 2000 and / or based on the transaction date and transaction time. According to another example, the electronic receipt generator 2000 may generate the identifier using a hashing technique. The hashing technique is a technique for obtaining a result value corresponding to an input value using a hash function. In such an example, the identifier may be a result value obtained using the transaction information as an input value of the hashing function.

[0249] According to an example embodiment, by using an identifier when generating an address (e.g., a URL) and then transmitting the address to the user device 400 via NFC, the following points can be ensured. In an example, it can be ensured that a specific electronic receipt is issued to only one user. The use of a specific electronic receipt based on a (unique) identifier or a hash value thereof ensures the one-to-one uniqueness of the electronic receipt. In some examples, the specific electronic receipt is deleted by the server 300 after being obtained by the user device 400.

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

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

[0252] In some embodiments, the electronic receipt generator 2000 can transmit transaction information to the server 300; the entire address corresponding thereto, including the identifier included in the address; other information indicating the address; a unique transaction identifier corresponding to the transaction, and other information indicating the identifier, etc., but the example embodiments are not limited to this.

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

[0254] At operations 104 and 105, the electronic receipt generator 2000 transmits the transaction information and information about the address corresponding thereto to the server 300. The server 300 then stores the information. Thereafter, the user can view the corresponding electronic receipt on the web page corresponding to the address via the user device, the electronic receipt including the corresponding transaction information. According to an exemplary embodiment, since the electronic receipt is viewed on the web page using a standard web browser application, the user does not need to install an additional mobile application on the user device to view the electronic receipt.

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

[0256] In some embodiments, the electronic receipt generator 2000 may use NFC technology to transmit information to the user device 400. In some embodiments, the electronic receipt generator 2000 may generate and send a message in a specific format for NFC. In some implementations, the specific format may refer to: a format that enables the user device 400 to receive a corresponding message including an instruction to immediately perform a predetermined action. For example, the electronic receipt generator 2000 may generate and send an NDEF message. The NDEF message may include information to be transmitted to the user device 400. The NDEF message may include an address as a payload. Thereafter, the user device 400 may perform a predetermined operation upon receiving the NDEF message. For example, the predetermined operation may be to open a specific web page using a web browser application. The web page may be linked to the address.

[0257] although Figure 6 Operation 106 is shown to occur after operation 105, but example embodiments are not limited to this order of events. For example, in some embodiments, operation 105 and operation 106 may occur simultaneously. As another example, in some embodiments, operation 105 may occur after operation 106.

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

[0259] In some embodiments, the user device 400 can receive information from the electronic receipt generator 2000 via NFC. The user device 400 may include a device, application, and / or API that supports or helps support NFC functionality. In some embodiments, the user device 400 can receive an NDEF message including an address as a payload by approaching the electronic receipt generator 2000 within tens of centimeters.

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

[0261] At operations 108 and 109, the user device 400 accesses a designated web page based on the received address and displays an electronic receipt.

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

[0263] In the 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 using an email address, text message, or executing a pre-loaded or pre-installed application. In the example, the user device 400 does not need to have a pre-installed or pre-loaded application. For example, the user device 400 can use, for example, a native browser, a progressive web application (PWA), or a mini application. The mini application will be further described below.

[0264] In an example, the user device 400 need not be "ready" to receive and display an electronic receipt. For example, the user device 400 may operate without having to pre-download, pre-install, or pre-load an application. For example, the user device 400 may operate without having to activate a camera to scan a QR code, exchange an email address, or phone number. Instead, the mini-application may be loaded as part of the NFC proximity between the user device 400 and the NFC tag controller 2070.

[0265] The electronic receipt may be generated by various types of applications (eg, a progressive web application, a responsive web application, a rich internet application, a single page application, or a multi-page application), but example embodiments are not limited thereto.

[0266] An electronic receipt is an electronic document in which transaction information is displayed according to a format determined by a provider based on a set of rules. A provider may be a transaction party associated with the electronic receipt. For example, a provider may be a merchant or a retailer, but example embodiments are not limited thereto. A provider is different from a transaction recipient, a consumer, a user, or a customer.

[0267] Figure 7 An example electronic receipt according to an example embodiment is shown. Figure 7 As shown, the electronic receipt can be displayed on a web page via a web browser application. In some embodiments, the electronic receipt may include the transaction date and transaction time, the identification of one or more items associated with the transaction (e.g., the name 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 one or more items, the total payment amount, the tax amount, the payment type (e.g., information about the transaction method, such as credit card information and / or debit card information), the receipt authorization number, the transaction party name, the transaction party number (e.g., business number), the transaction party address, the transaction party phone number, the transaction number, etc. As previously mentioned, the format of the electronic receipt can be determined by the provider and is not limited to the format shown in the figure.

[0268] In some embodiments, the transaction recipient and / or user can view the electronic receipt via the user device without installing a specific dedicated application on the user device. Conventionally, viewing the electronic receipt via the user device typically requires the installation of a specific dedicated application on the user device. It is also typically required to complete a login process via the user device in order to view the electronic receipt. However, example embodiments include a computing device and method for viewing an electronic receipt on a web page through a conventional web browser application without installing a specific dedicated application, registering on any website, or completing any login process.

[0269] In some embodiments, the consumer can check the electronic receipt on the user device via a simple action of tapping the electronic receipt generator. Since the URL can be transmitted to the user device via the NDEF message according to the example embodiment, the user device can directly execute the URL using the preset command in the NDEF message. In this way, due to the simple tap action, the user can view the electronic receipt through the web browser application without any further operation.

[0270] 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 or a phone number, etc. Therefore, according to example embodiments, unnecessary disclosure of personal information during a transaction can be prevented, the procedure and time for issuing an electronic receipt can be shortened, and the electronic receipt can be viewed more conveniently on a user device.

[0271] In some embodiments, an electronic receipt may be provided to a user via a user device regardless of the corresponding transaction type. For example, conventionally, when a credit card company issues an electronic receipt, the electronic receipt may be received only when payment is provided using a credit card associated with the corresponding credit card company. However, according to an example embodiment, since the electronic receipt may be issued to the user device in conjunction with a POS terminal associated with the transaction, the user may receive the electronic receipt regardless of the transaction type, which may include cash, debit card, credit card, digital wallet, etc.

[0272] In some embodiments, an electronic receipt including multiple transaction information may be provided to the user. Conventionally, when an electronic receipt is issued after a transaction through a related application or short message service (SMS), only limited transaction information may be displayed on the electronic receipt. For example, in some conventional cases, only the total payment amount is displayed, and detailed transaction information is not displayed, such as the identification of one or more items related to the transaction, the quantity of one or more items, the payment amount associated with each item, the tax amount, etc. However, in contrast, according to the embodiments described herein, an electronic receipt including multiple transaction information may be provided to the user.

[0273] Figure 8 A method for issuing an electronic receipt according to another exemplary embodiment is shown. Figure 8 , at operation 201 , the user has not yet started a transaction or the user has already started at least a portion of a transaction.

[0274] and Figure 5 In contrast to the method shown in Figure 8 When the method of claim 1 begins (e.g., at operation 201), the transaction has not yet been completed. At operation 201, the user has not yet provided payment 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 provided.

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

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

[0277] In some embodiments, the intermediate transaction information is different from the completed transaction information. For example, the intermediate transaction information may be a collection of all information about a transaction for which payment has not yet been received. For example, the intermediate transaction information may include the transaction date and transaction time, 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 amount, the transaction party name, the transaction party number, the transaction party address, the transaction party phone number, etc. However, the intermediate transaction information may not include the total payment amount, the payment type, the promotion amount associated with the transaction, the discount amount, and the total payment amount reflecting the discount amount, etc.

[0278] In some embodiments, the temporary transaction information may be data stored in a certain format. For example, the preliminary transaction information may be data recording the above transaction information in a text file format.

[0279] At operation 203, the electronic receipt generator 2000 generates an address corresponding to the received intermediate transaction information.

[0280] In some embodiments, the address may refer to a URL for accessing a website or web page on the Internet, but example embodiments are not limited thereto.

[0281] In some embodiments, the electronic receipt generator 2000 may generate a unique address corresponding to the intermediate transaction information. Thus, address conflicts that may occur, for example, when the same address is generated in response to different transaction information, may be avoided. The electronic receipt generator 2000 may generate a unique address by including a unique transaction identifier corresponding to the intermediate transaction information in the address. For example, the address may have the format "website / identifier". In such an example, the format of the identifier may have various lengths based on a combination of letters, numbers, and special characters, but example embodiments are not limited thereto.

[0282] In some embodiments, the electronic receipt generator 2000 may generate an identifier based on the intermediate transaction information. For example, the identifier may be generated based on information about the electronic receipt generator 2000 and the transaction date and transaction time at which the transaction information was generated. In some embodiments, the electronic receipt generator 2000 may generate the identifier using a hashing technique. In such embodiments, the hashing technique may be a technique for obtaining a result value corresponding to an input value using a hash function. In such embodiments, the identifier may be a result value obtained by a hashing function using the intermediate transaction information as an input value.

[0283] At operation 204 , the electronic receipt generator 2000 transmits the intermediate transaction information and information about an address corresponding thereto to the server 300 .

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

[0285] At operation 205 , the server 300 stores the intermediate transaction information received from the electronic receipt generator 200 and the information about the corresponding address.

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

[0287] In some embodiments, the electronic receipt generator 2000 may transmit information to the user device 400 via NFC. In some embodiments, the electronic receipt generator 2000 may generate and send a message in a specific format for NFC. The specific format may refer to a format that enables the user device 400 that receives the corresponding message to immediately perform a predetermined action. For example, the electronic receipt generator 2000 may generate and send an NDEF message. The NDEF message may include information to be transmitted to the user device 400. The NDEF message may include an address as a payload. Thereafter, the user device 400 may perform a predetermined operation upon receiving the NDEF message.

[0288] although Figure 8 Operation 206 is shown to occur after operation 205, but example embodiments are not limited thereto. For example, operation 205 and operation 206 may occur simultaneously, or operation 205 may occur after operation 206.

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

[0290] In some embodiments, the user device 400 receives information from the electronic receipt generator 2000 via NFC. The user device 400 may include a device, application, and / or application programming interface (API) that supports or helps support NFC functionality. In some embodiments, the user device 400 may receive an NDEF message including an address as a payload by approaching the electronic receipt generator 2000 within tens of centimeters.

[0291] At operations 208 and 209 , the user device 400 accesses a designated web page based on the received address and displays a preliminary electronic receipt.

[0292] In some embodiments, the user device 400 may access a web page on the Internet that is linked to the received address. In some embodiments, the server 300 may have stored the intermediate transaction information corresponding to the address. The server 300 may then use an application to convert the intermediate transaction information into a preliminary electronic receipt format. The server 300 may then display the generated preliminary electronic receipt on the web page linked to the address. Therefore, the user device 400 may view the preliminary electronic receipt by accessing the web page linked to the address.

[0293] In some implementations, the preliminary electronic receipt may be generated using various one or more applications (e.g., by using a progressive web application, a responsive web application, a rich internet application, a single page application, and / or a multi-page application), although example embodiments are not limited thereto.

[0294] In some embodiments, Fig. 9 As shown, instead of displaying a preliminary electronic receipt, user device 400 may display a message such as "Preparing your receipt."

[0295] Return again Figure 8 At operation 210, the user completes the transaction. In some embodiments, when the transaction is completed, the POS terminal 100 can obtain complete transaction information. In some embodiments, the complete transaction information can be a plurality of information about the transaction for which the payment has been received.

[0296] In some embodiments, in addition to the transaction date and transaction 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 one or more items, the transaction party name, the transaction party number, the transaction party address, the transaction party telephone number, etc., the complete transaction information may also include the final payment amount, the final tax amount and / or information about the payment type, etc.

[0297] In some embodiments, the complete transaction information may include multiple information about the transaction for which payment has been received after the discount amount and / or promotional amount has been applied. In such embodiments, in addition to the other information described above, the complete transaction information may also include membership information, promotional information and amount, discount information and amount, final payment amount reflecting the discount amount, etc.

[0298] In some embodiments, similar to the initial transaction information, the complete transaction information may be data stored in a certain format. For example, the complete transaction information may be data recording the above information in a text file format.

[0299] At operation 211 , the POS terminal 100 transmits the complete transaction information to the electronic receipt generator 200 .

[0300] Reference again Figure 1 In some embodiments, the POS terminal 100 can transmit the transaction information to the electronic receipt generator 2000 via a wired communication method or a wireless communication method. In an embodiment where the POS terminal and the electronic receipt issuer are integrated with each other, for example Figure 5 As shown, transaction information is transmitted internally.

[0301] Reference again Figure 8 At operation 212 , the electronic receipt generator 2000 transmits the complete transaction information and information about the address corresponding thereto to the server 300 .

[0302] In some embodiments, the electronic receipt generator 2000 already has the intermediate transaction information and the address corresponding thereto. In some such embodiments, the intermediate transaction information may be replaced or updated by the complete transaction information. Therefore, the electronic receipt generator 2000 may use the address corresponding to the intermediate transaction information as the address corresponding to the complete transaction information. Therefore, address conflicts may be avoided. The electronic receipt generator 2000 may transmit the complete transaction information, the complete address already stored therein, the identifier included in the address, other information indicating the address, and other information indicating the identifier, etc. to the server 300, but example embodiments are not limited thereto.

[0303] At operation 213 , the server 300 updates the intermediate transaction information to complete transaction information using the information about the address transmitted from the electronic receipt generator 200 .

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

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

[0306] In some embodiments, the updated electronic receipt may be generated by one or more applications (eg, a progressive web application, a responsive web application, a rich internet application, a single page application, or a multi-page application), although example embodiments are not limited thereto.

[0307] In some embodiments, for example Figure 6In the embodiment shown, the user can view the electronic receipt after the transaction is completed by tapping the user device on the electronic receipt generator. In some embodiments, for example Figure 8 In the illustrated embodiment, 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 can be automatically updated to allow the updated electronic receipt to be viewed via the user device.

[0308] Some example embodiments may be related to Figure 6 and Figure 8 The embodiments described are different.

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

[0310] However, in some embodiments, the address may refer to a deep link URL for directly accessing a mobile application page or a web application page.

[0311] In some such embodiments, the deep link URL may be directly generated by the electronic receipt generator 2000 in response to receiving the transaction information. However, example embodiments are not limited thereto, 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.

[0312] In some embodiments, Figure 6 Operations 108 and 109 and Figure 8 At operations 214 and 215, the user device 400 accesses a designated web page based on the received address and displays an electronic receipt.

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

[0314] In some embodiments, when the relevant application is not yet installed on the user device 400, the user device 400 can install the relevant application and then access the mobile application page or web application page linked to the address. In some such embodiments, the user device 400 can receive the address via an NDEF message, and as a predetermined action, can install the relevant application and can access the page linked to the address.

[0315] In example embodiments, unless explicitly described to the contrary, the word “comprise” and variations such as “comprises” or “comprising” will be understood to imply the inclusion of stated elements but not the exclusion of any other elements.

[0316] In example embodiments, a "module" may be a hardware component (eg, a processor or circuit), and / or a software component (eg, such as a processor) executed on hardware.

[0317] In an example embodiment, each of the components, functional blocks or devices may include one or more sub-components. The electrical, electronic and mechanical functions performed by the components may be implemented by various well-known devices or mechanical elements (e.g., electronic circuits, integrated circuits, application-specific integrated circuits (ASICs), etc.), and may be implemented independently of each other, or may be implemented as a whole in the form of a combination of two or more thereof.

[0318] Modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, may be located in one location, or may be distributed over multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

[0319] In addition, the functional modules in the exemplary embodiments may be integrated in one processing module, or each of the modules may exist physically separately, or two or more modules may be integrated in one module.

[0320] When functions are implemented in the form of software function modules and sold or used as independent products, these functions can be stored in a computer-readable storage medium (which can be non-temporary). Based on such an understanding, the technical solution of the exemplary embodiment can 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 can be a personal computer, a server or a network device) to perform all or part of the steps of the method described in the exemplary embodiment. The above-mentioned storage medium includes any medium that can store program code, such as a universal serial bus (USB) flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a disk, an optical disk, etc.

[0321] In the described method or block diagram, a frame can represent an event, step, function, process, module, message and / or state-based operation, etc. Although some example embodiments are described as occurring in a particular order, some steps or processes can be performed in different orders, as long as the result of the change order of any given step does not prevent or damage the occurrence of subsequent steps. In addition, in other embodiments, some messages or steps described can be removed or combined, and in other embodiments, some messages or steps described herein can be divided into multiple sub-messages or sub-steps. Even further, some or all steps can be repeated when necessary. The elements described as methods or steps are equally applicable to computing devices or sub-components, and vice versa. References to words such as "send" or "receive" can be interchanged according to the perspective of a specific device.

[0322] The described embodiments are to be considered in all respects illustrative and not restrictive.Example embodiments described as methods are equally applicable to computing devices or apparatuses, and vice versa.

[0323] The various example embodiments are merely examples and are therefore by no means intended to limit the scope of the examples and example embodiments. Variations of the innovations described herein will be apparent to those of ordinary skill in the art and are within the intended scope. In particular, features from one or more of the example embodiments may be selected to produce an alternative embodiment consisting of a subcombination of features that may not be explicitly described. In addition, features from one or more of the example embodiments may be selected and combined to produce an alternative example embodiment consisting of a combination of features that may not be explicitly described. Features suitable for such combinations and subcombinations will be readily understood by those skilled in the art. The subject matter described herein is intended to cover all appropriate changes in technology.

Claims

1. A computing device, comprising: Communication module; processor; as well as at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; Sending the transaction information to a transmission channel; 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 uniform resource locator (URL) including the unique transaction identifier; receiving from the transmission channel a confirmation of successful completion of the debit card transaction corresponding to the transaction information; as well as The URL is sent to the NFC tag controller.

2. The computing device according to claim 1, wherein: Before sending the URL to the NFC tag controller, the processor is further caused to: A confirmation of successful completion of the debit card transaction corresponding to the transaction information is sent to the NFC controller.

3. The computing device according to claim 1, wherein: The URL also includes at least some of the plurality of receipt elements, including names of transaction parties, a transaction date, identification of the one or more purchases, or a total payment amount.

4. The computing device according to claim 3, wherein: The processor is also caused to: determine that an Internet connection does not exist at the computing device; wherein the sending comprises sending the URL to a user device via the NFC tag controller; The URL includes at least some of the plurality of receipt elements, so that the user device can generate a receipt for the transaction by parsing the URL without accessing the URL on the Internet.

5. The computing device according to claim 1, wherein: The sending includes sending an NFC data exchange format NDEF message including the URL as a payload to a user device via the NFC tag controller.

6. The computing device according to claim 1, wherein: 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.

7. The computing device according to claim 1, wherein: Prior to receiving confirmation of successful completion of the debit card transaction, the processor is also caused to: determine that an Internet connection is not present at the computing device.

8. The computing device according to claim 1, wherein: Prior to receiving a confirmation of successful completion of the debit card transaction corresponding to the transaction information, the processor is further caused to: sending the transaction information and the URL to a server via the communication module, The URL identifies a network resource corresponding to a receipt for the transaction.

9. The computing device of claim 1, wherein: Before sending the transaction information to the transmission channel, the processor is further configured to: receiving debit card data from a card reader CR device, the CR device including the NFC tag controller; and sending the debit card data to the transmission channel, The unique device identifier is a unique device identifier of the CR device.

10. The computing device of claim 1, further comprising: the NFC tag controller, The processor is also configured to: generating, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload; and An NFC signal corresponding to the NDEF message is transmitted via the NFC tag controller.

11. The computing device of claim 8, further comprising: NFC tag reader; Before generating the URL, the processor is further configured to: receiving debit card data via the NFC tag reader; and sending the debit card data to the transmission channel, Wherein the URL further includes the unique device identifier, wherein the unique device identifier is a unique device identifier of the computing device.

12. The computing device of claim 11, wherein: The computing device is a commercial off-the-shelf contactless PIN entry CPoC device, a commercial off-the-shelf software-based PIN entry device, or a mobile payment on a commercial off-the-shelf device MPoC device.

13. A computing device comprising: Communication module; processor; as well as at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements; Make sure there is no internet connection; generating, as a result of determining that there is no internet connection, a uniform resource locator URL, the URL including at least some of the plurality of receipt elements, the at least some of the plurality of receipt elements including names of transaction parties, a transaction date, identification of the one or more purchases, or a total payment amount; as well as sending, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload to the user device, Wherein, the URL is formatted so that the user device can generate a receipt for the transaction by parsing the URL without accessing the URL on the Internet.

14. The computing device of claim 13, wherein: Also enables the processor to: determining that said internet connection exists; sending the transaction information and the URL to a server via the communication module, The URL identifies a network resource corresponding to a second receipt for the transaction.

15. A user device, comprising: processor; as well as at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the user device to: receiving a uniform resource locator (URL) as a string, the URL identifying a network resource corresponding to the transaction; parsing the string into its component parts; determining an association between at least two of the plurality of components and corresponding receipt element identifiers; as well as A second receipt is generated that includes at least two of the corresponding receipt element identifiers.

16. The user device according to claim 15, wherein: The user device is also caused to: store the second receipt at a first location.

17. The user device according to claim 16, wherein: Also causing the user device to: accessing a network resource corresponding to a first receipt for a transaction identified by the URL; and The first receipt is stored at the first location.

18. The user device according to claim 15, wherein: Also causing the user device to: prior to generating the second receipt, receiving a selection of a desired receipt element identifier, Wherein the at least two of the corresponding receipt element identifiers in the second receipt correspond to a selection of the desired receipt element identifier.

19. The user device according to claim 15, wherein: A selection of the desired receipt element identifier is received via a graphical user interface.

20. The user device according to claim 15, wherein: The URL includes a unique transaction identifier and at least the names of the transaction parties, the transaction date, and one or more identifications of the purchases or a total payment amount.

21. The user device according to claim 20, wherein: The unique transaction identifier is generated using a hash function applied to the transaction information, and / or using date information and time information associated with the transaction, and / or using a unique device identifier.

22. A computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; Sending the transaction information to a transmission channel; 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 uniform resource locator (URL) comprising the unique transaction identifier and at least some of the plurality of receipt elements, at least some of the plurality of receipt elements comprising names of transaction parties, a transaction date, identification of the one or more purchases, or a total payment amount; receiving from the transmission channel a confirmation of successful completion of the debit card transaction corresponding to the transaction information; and The URL is sent to the NFC tag controller.

23. The computer-implemented method of claim 22, wherein: Before sending the URL to the NFC tag controller, the method further includes: A confirmation of successful completion of the debit card transaction corresponding to the transaction information is sent to the NFC controller.

24. The computer-implemented method of claim 22, wherein: Prior to receiving a confirmation of successful completion of the debit card transaction corresponding to the transaction information, the method further comprises: sending the transaction information and the URL to a server, The URL identifies a network resource corresponding to a receipt for the transaction.

25. The computer-implemented method of claim 22, wherein: Before sending the transaction information to the transmission channel, the method further includes: receiving debit card data from a card reader CR device, the CR device including the NFC tag controller; and sending the debit card data to the transmission channel, The unique device identifier is a unique device identifier of the CR device.

26. The computer-implemented method of claim 22, further comprising: generating, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload; as well as An NFC signal corresponding to the NDEF message is transmitted via the NFC tag controller.

27. The computer-implemented method of claim 26, wherein: Before generating the URL, the method further includes: receiving debit card data via an NFC tag reader; and The debit card data is sent to the transmission channel.

28. A non-transitory computer readable medium comprising instructions which, when executed by a processor, cause the processor to: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising date information and time information; Sending the transaction information to a transmission channel; 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 uniform resource locator (URL) comprising the unique transaction identifier and at least some of the plurality of receipt elements, at least some of the plurality of receipt elements comprising names of transaction parties, a transaction date, identification of the one or more purchases, or a total payment amount; receiving from the transmission channel a confirmation of successful completion of the debit card transaction corresponding to the transaction information; and The URL is sent to the NFC tag controller.

29. A non-transitory computer readable medium comprising instructions which, when executed by a processor, cause the processor to: receiving a uniform resource locator (URL) as a string, the URL identifying a network resource corresponding to the transaction; parsing the string into its component parts; determining an association between at least two of the plurality of components and corresponding receipt element identifiers; as well as A second receipt is generated that includes at least two of the corresponding receipt element identifiers.

30. A computer-implemented method comprising: receiving a uniform resource locator (URL) as a string, the URL identifying a network resource corresponding to the transaction; parsing the string into its component parts; determining an association between at least two of the plurality of components and corresponding receipt element identifiers; as well as A second receipt is generated that includes at least two of the corresponding receipt element identifiers.

31. A computing device comprising: NFC tag controller; Communication module; processor; as well as at least one memory coupled to the processor and storing instructions that, when executed by the processor, cause the processor to: receiving, via the communication module, transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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; Sending the transaction information and the URL to a server; generating, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload; transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and Wherein, upon receiving the NFC signal, the user device immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, text message, or execution of a preloaded or preinstalled application.

32. A computer-implemented method comprising: receiving transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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; Sending the transaction information and the URL to a server; generating, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload; transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and Wherein, upon receiving the NFC signal, the user device immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, text message, or execution of a preloaded or preinstalled application.

33. A non-transitory computer readable medium comprising instructions which, when executed by a processor, cause the processor to: receiving, via the communication module, transaction information corresponding to a transaction, the transaction comprising one or more purchases and payments, the transaction information comprising a plurality of receipt elements, the plurality of receipt elements comprising 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; Sending the transaction information and the URL to a server; generating, via the NFC tag controller, an NFC data exchange format NDEF message including the URL as a payload; transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message to a user device, wherein the URL identifies a network resource at the server corresponding to a receipt for the transaction, the receipt being generated by the server in response to receiving the transaction information, and Wherein, upon receiving the NFC signal, the user device immediately displays the receipt via a web page or application page corresponding to the URL without using an email address, text message, or execution of a preloaded or preinstalled application.

Images