Method for processing payments and issuing electronic receipts via near field communication

Abstract

Computing devices, computer-implemented methods, and non-transitory computer-readable media are provided for issuing an electronic receipt at a point of sale and using near field communication (NFC) technology.SOLUTION: The method receives 1110 transaction information, transmits 1120 the transaction information to a transfer rail of transaction information, generates 1130 a unique transaction identifier using date and time information and / or a unique device identifier using a hash function applied to the transaction information, generates 1140 a uniform resource locator (URL) based on at least a portion of the unique transaction identifier and / or a plurality of receipt elements, receives 1150 a confirmation of successful completion of the transfer card transaction from said transfer rail, and transmits 1160 the URL to an NFC tag controller.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is a continuation of U.S. Provisional Patent Application No. 63 / 477,69, filed December 29, 2022. Issue 0, "Method for payment processing and issuing electronic receipts using near-field communication," 2022 PCT patent application No. PCT / KR2022 / 014622, filed on September 29, entitled "Electronic "Method for issuing receipts," Korean Patent Application No. 10-2022 filed on March 25, 2022 -0037255 "Method for issuing electronic receipts" and the application filed on March 25, 2022 Priority of Korean Patent Application No. 10-2022-0003963 "Method for issuing electronic receipts" The entire contents of which are incorporated herein by reference in their entirety. PCT patent application no. 0220 ... It is also a continuation-in-part of PCT / KR2022 / 014622, and will be filed on March 25, 2022. Korean patent application number 10-2022-003 entitled "Method for issuing electronic receipts" filed 7255, and a patent application entitled "Method for issuing electronic receipts" filed on January 11, 2022. Priority is claimed to Korean Patent Application No. 10-2022-0003963.

[0002] Exemplary embodiments include providing electronic receipts (electronic receipts or receipts), e.g., and providing electronic receipts using near field communication (NFC) technology. [Background technology]

[0003] When a consumer completes a transaction related to the purchase of a product or the use of a service, the consumer receives a receipt. In traditional systems, point-of-sale (POS) terminals issue paper receipts. It will issue receipts instantly and may provide electronic receipts to consumers in the future. Disadvantages include the risk of personal information leakage, the challenge of efficient receipt management, and the difficulty of printing receipts. The costs of creating electronic receipts are high, as they guarantee personal information, are easy to store and manage, and are easy to create. It is generally preferred because it is cheaper to produce and environmentally friendly. It provides timely electronic receipts. What is needed is an efficient computing device and method for performing the same. To provide timely electronic receipts, the system requires that the user device display electronic receipts. For example, a trading partner may need to be "ready" to You can pre-install apps or use the camera on the user device to scan QR codes. or exchange email addresses and phone numbers with an e-receipt provider These circumstances may require the timely issuance of electronic receipts. For example, a business partner may be carrying a user device, The user device may not have the necessary applications installed. This is the case, for example, when the user device is new or when a business partner This can happen if you are not familiar with the device. Existing receipt and payment systems In some cases, you may need to register your device to receive electronic receipts. This includes personal information such as email addresses, phone numbers, payment method numbers, and account information. As a result, electronic certificates can be used at the time of a transaction without personal information or prior registration. What is desired is a computing device and method for providing book collection.

[0004] To provide timely electronic receipts, the POS terminal at the transaction location must have internet access. Although a connection may also be required, in many cases an internet connection may not be available. For example, many transactions take place in subway terminals, on airplanes, during network outages, etc. and other situations where an Internet connection is not available. A computing device and method that provides electronic receipts for transactions even when there is no connectivity Laws are also required.

[0005] summary The examples described herein are intended to allow merchants to receive electronic receipts immediately. , a computing device and method for issuing electronic receipts may be provided. The electronic receipt may be received, for example, at a user device.

[0006] The examples described herein may be used to allow a computing device to run even in the absence of a web connection. It may be possible to issue electronic receipts.

[0007] In accordance with the examples described herein, a trading partner may access a web browser application immediately after a transaction has occurred. The user can then use the application to receive and view the corresponding electronic receipt. By way of an example described in the subsection, a trading partner may send a corresponding electronic receipt to a user immediately after a transaction has occurred. can be received and viewed on the user device.

[0008] Traditionally, issuing electronic receipts required a specific application on a consumer's smartphone. However, in some implementations, The electronic receipts provided by the example can be viewed in the form of a web page via a browser, allowing the consumer to Consumers can pre-install separate applications or sign up to websites. You can receive an electronic receipt without having to log in to a website or tap the payment button. Summary of the Invention [Means for solving the problem]

[0009] An example embodiment includes a communication module, a processor, and at least one a computing device comprising: The instructions stored in the memory, when executed by the processor, provide one or more Multiple receipts containing date and time information corresponding to transactions including the above purchases and payments receiving transaction information including a factor, transmitting the transaction information to a transfer rail, and applying the factor to the transaction information; Using a hash function, and / or using date and time information, and / or uses the unique device identifier to generate a unique transaction identifier, and Generate a Uniform Resource Locator (URL) containing the transfer information from the rail The URL is sent to the NFC tag controller to receive a confirmation of the successful completion of the corresponding transfer card transaction. Send it to the

[0010] In an example embodiment of any of the above computing devices, the URL may include a , one of several receipt elements including the transaction date, one or more purchase identifiers, or the total amount paid. Further includes at least a portion.

[0011] In an example embodiment of any of the above computing devices, the processor further comprises: When the computing device determines that it does not have an internet connection, Sending the URL to the user device via the NFC tag controller the user device parses the URL to identify URLs on the Internet, The URL is multiple so that you can generate a transaction receipt without having to access L The receipt element includes at least a portion of the receipt element.

[0012] In an example embodiment of any of the above computing devices, the transmitting includes: NFC data transfer, including sending a URL to the user device via the C-tag controller The Data Exchange Format (NDEF) message contains a URL as a payload.

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

[0014] In an example embodiment of any of the above computing devices, the processor may Before receiving confirmation of a successful card transaction, the computing device further determines that there is no Internet connection.

[0015] In an example embodiment of any of the above computing devices, the processor may and before receiving confirmation of successful completion of the transfer card transaction corresponding to the information, the communication module The transaction information and URL are sent to the server via the email, and the URL corresponds to the transaction receipt. Identifies a web resource.

[0016] In an example embodiment of any of the above computing devices, the processor may Before sending the transaction information to the server, the transfer card data is also received from the card reader (CR). The CR device contains an NFC tag controller and transfers card data to the transfer rail. The unique device identifier is that of the CR device.

[0017] In an example embodiment of any of the above computing devices, The device further comprises an NFC tag controller, the processor further comprising: Generate an NDEF message via the controller containing a URL as the payload. , emits an NFC signal corresponding to the NDEF message via the NFC tag controller ( emit).

[0018] In an example embodiment of any of the above computing devices, The device may further include an NFC tag reader, and prior to generating the URL, may further include Furthermore, the transfer card data is received via the NFC tag reader, and the transfer card is inserted into the transfer rail. The URL further includes a unique device identifier to allow the unique device to be accessed. The device identifier is that of the computing device.

[0019] In an example embodiment of any of the above computing devices, The device supports contactless PIN entry on commercial off-the-shelf (CPoC) devices, Software-based PIN entry on off-the-shelf devices or commercial off-the-shelf Mobile Payments on Shelf Devices (MPoC).

[0020] Another example embodiment includes a communication module, a processor, and at least one a computing device comprising: The instructions stored in memory, when executed by the processor, provide the processor with Receive transaction information containing multiple receipt elements corresponding to a transaction involving one or more purchases and payments. send transaction information to the transfer rail and determine that no internet connection exists and determines that there is no internet connection, the trader's name, the date of the transaction, and one or more A user ID containing at least a portion of a plurality of receipt elements including an identification of the purchase or a total amount paid. Generates a Uniform Resource Locator (URL) and sends it to the user via the NFC tag controller. The user device receives the NFC Data Exchange Format (NDE) containing the URL as a payload. F) Send a message, where the URL is a URL that the user device parses and interprets. Format so that transaction receipts can be generated without accessing a URL on the Internet. It will be matted.

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

[0022] Another example embodiment includes a processor; at least one memory coupled to the processor; and a user device having instructions stored in at least one memory, the instructions comprising: When executed by the processor, the web resource corresponding to the transaction is transmitted to the user device. The Uniform Resource Locator (URL) that identifies the Analyze multiple components and check that at least two of the components are Determine the association with each receipt element identifier, and A second receipt is generated that includes at least two of the items.

[0023] In any example embodiment of the user device described above, the user device further comprises: The receipt is stored in a first location.

[0024] In any example embodiment of the user device described above, the user device further comprises: accessing a web resource corresponding to a first receipt of a transaction identified by L; The receipts will be kept in a first location.

[0025] In an example embodiment of any of the above user devices, the user device may include a second receipt. receiving a selection of a desired receipt element identifier before generating the second receipt; At least two of the receipt element identifiers correspond to a desired receipt element identifier selection. .

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

[0027] In any example embodiment of the user device described above, the URL may include a unique transaction identifier and At a minimum, include the name of the person making the transaction, the date of the transaction, and one or more purchase identifiers or total amount paid. .

[0028] In any example embodiment of the user device described above, the unique transaction identifier is stored in the transaction information. using an applied hash function and / or date information and associated with the transaction The device may be generated using the device ID and time information and / or a unique device identifier.

[0029] Another example embodiment is a computer-implemented method that includes one or more purchases and payments. Receive transaction information that includes multiple receipt elements, including date and time information, corresponding to a transaction that includes and transmitting the transaction information to a transfer rail. The hash function applied to the transaction information is using the date and time information associated with the transaction, and / or generating a unique transaction identifier using a unique device identifier and a unique transaction identifier and at least one of the following: the name of the transaction party, the date of the transaction, one or more identifying details of the purchase; specifies a uniform resource locator (URL) that contains a receipt element that includes the total amount paid. Generate and confirm the successful completion of transfer card transactions corresponding to transaction information from the transfer rail and sending the URL to the NFC tag controller.

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

[0031] In one example embodiment of any of the above computer-implemented methods, the transaction information is sent to a transfer rail. Before transmitting the NFC tag, the method further comprises: Receives transferred card data from the device and confirms that the unique device identifier is that of the CR device. and transmitting the transfer card data to the transfer rail.

[0032] In an example embodiment of any of the above computer-implemented methods, the computer-implemented method further comprises: Furthermore, NFC data containing a URL as a payload is sent via the NFC tag controller. Generates NFC tag exchange format (NDEF) messages and and emitting an NFC signal corresponding to the NDEF message via the NFC interface.

[0033] In an example embodiment of any of the above computer-implemented methods, before generating the URL, the method The method also allows card data to be transferred via an NFC tag reader and transferred to a and transmitting the transfer card data.

[0034] Another example embodiment is a non-transitory computer-readable medium, executable by a processor. Once received, you will provide the processor with a daily transaction corresponding to a transaction that includes one or more purchases and payments. and receiving transaction information including a plurality of receipt elements including date information and time information, and transmitting the transaction information to a transfer level. and / or by sending the transaction to using date and time information associated with the transaction and / or unique device generating a unique transaction identifier using the transaction identifier, and Receipt elements that include the name of the transactor, the date of the transaction, one or more purchase identifiers, or the total amount paid Generate a uniform resource locator (URL) containing the transaction information from the transfer rail. The URL is sent to the NFC tag controller. The controller executes the process by transmitting the process to the processor of the computing device. It is a non-transitory computer-readable medium containing instructions to cause the

[0035] Another example embodiment is a non-transitory computer-readable medium executable by a processor. When executed, it tells the processor to convert a Uniform Resource Locator (URL) into a string. The URL identifies the web resource corresponding to the transaction, and the string is then split into multiple components. component and analyze it to identify at least two of the components and their respective receipts. and determining an association between at least two of each receipt element identifier. Generate a second receipt containing:

[0036] Another example embodiment is a computer-implemented method for providing a web resource corresponding to a transaction. Receive the Uniform Resource Locator (URL) that identifies the URL as a string, and Parsing a string into multiple components and selecting at least one of the multiple components determining the association between the two and each receipt element identifier; and generating a second receipt including at least two of the element identifiers.

[0037] Another example embodiment includes an NFC tag controller, a communication module, a processor, and a processor. at least one memory connected to a processor. wherein the instructions stored in the at least one memory are executed by a processor. and to a processor via a communication module, including one or more purchases and payments. receiving transaction information including a plurality of receipt elements, including date information and time information, corresponding to the transaction; , using a hash function applied to the transaction information, and / or date and time information and / or a unique device identifier to generate a unique transaction identifier. The transaction information and URL are then sent to the server. Then, via the NFC tag controller, NFC data exchange including the URL as a payload is performed. Generates a NDEF format message and sends it to the NFC tag controller. The user device emits an NFC signal corresponding to the DEF message, and the URL is A receipt identifies a web resource on a server that corresponds to the receipt, the receipt including transaction information and the user device receives the NFC signal. Email addresses, text messages, or preloaded or preinstalled The web page or application corresponding to the URL is displayed without executing the application. View your receipt instantly through the application page.

[0038] Another exemplary embodiment is a computer-implemented method, the method comprising one or more purchase and payment steps. Transaction information including multiple receipt elements containing date and time information corresponding to a transaction involving a payment and using a hash function applied to the transaction information and / or date Use your personal information and time information and / or a unique device identifier to identify your unique transaction. generating a transaction identifier; generating a URL including the unique transaction identifier; and and URL to the server, and the URL is transmitted to the Generate an NFC Data Exchange Format (NDEF) message that contains the and sends an NFC signal corresponding to the NDEF message to the user via the NFC tag controller. and issuing to the user device a URL to a website on the server corresponding to a receipt for the transaction. The receipt identifies the web resource and is generated by the server upon receipt of the transaction information. When the user device receives the NFC signal, it will send an email address, text, Messages or running preloaded or preinstalled applications immediately through the web page or application page corresponding to the URL without View receipts.

[0039] Another example embodiment is a non-transitory computer-readable medium executable by a processor. Upon execution, the processor is notified via the communications module of one or more purchase and payment transactions. Transaction information including multiple receipt elements including date and time information corresponding to transactions including and uses a hash function applied to the transaction information and / or date and time information. unique transaction identifiers using transaction information and / or unique device identifiers Generate a URL including a unique transaction identifier, and transmit the transaction information and URL to the server. and sends the NFC tag containing the URL as a payload via the NFC tag controller. Generates a Data Exchange Format (NDEF) message and sends it via the NFC tag controller. and instructions to cause the user device to emit NFC signals corresponding to the NDEF message. The URL identifies a web resource on the server that corresponds to the transaction receipt. The receipt is generated by the server in response to receipt of the transaction information, and the user device receives the receipt from the NF When a C signal is received, the email address, text message, or preloaded or does not run the pre-installed application, but instead launches the web page corresponding to the URL. View your receipt instantly through the app or page. [Brief explanation of the drawings]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0059] At least some example embodiments allow users to conveniently check on their smartphones. This includes a method for issuing electronic receipts (electronic receipts or receipts) to That method can be used.

[0060] The exemplary embodiment may be modified in various ways and may have various embodiments. For this reason, specific embodiments are shown in the drawings and are described in detail in the detailed description. It is not intended to be limiting to any particular embodiment, but rather to provide an understanding of the scope of the example embodiments. All modifications, equivalents, and alternatives not departing from the scope of the present invention should be understood. In the detailed description, specific details regarding the related art may be omitted to obscure the example embodiments. It may be omitted if it is judged that there is a possibility of making the matter unclear.

[0061] An example embodiment is a computer-implemented method for performing a transaction involving one or more purchases and payments. receiving transaction information including multiple receipt elements, including date and time information, corresponding to the transaction; and sending the transaction information to a transfer rail and using a hash function applied to the transaction information. and / or using date and time information associated with the transaction, and and / or a unique device identifier to generate a unique transaction identifier and Transaction identifier and at least one of the following: name of the transaction party, transaction date, one or more purchase identifiers, or Generates a uniform resource locator (URL) containing a receipt element containing the total payment amount. and receive confirmation from the transfer rail that the transfer card transaction corresponding to the transaction information has been successfully completed. and sending the URL to the NFC tag controller.

[0062] Another example embodiment is a computer-implemented method for providing a web resource corresponding to a transaction. Receive the Uniform Resource Locator (URL) that identifies the URL as a string, and Parsing a string into multiple components and selecting at least one of the multiple components determining the association between the two and each receipt element identifier; and generating a second receipt including at least two of the element identifiers.

[0063] Another example embodiment includes an NFC tag controller, a communication module, a processor, and a processor. at least one memory connected to a processor. wherein the instructions stored in the at least one memory are executed by a processor. and to a processor via a communication module, including one or more purchases and payments. receiving transaction information including a plurality of receipt elements, including date information and time information, corresponding to the transaction; , using a hash function applied to the transaction information, and / or date and time information and / or a unique device identifier to generate a unique transaction identifier. The transaction information and URL are then sent to the server. Then, via the NFC tag controller, NFC data exchange including the URL as a payload is performed. Generates a NDEF format message and sends it to the NFC tag controller. The user device emits an NFC signal corresponding to the DEF message, and the URL is , identifying a web resource on a server corresponding to a transaction receipt, the receipt being The user device receives an NFC signal generated by the server in response to receiving transaction information. You can then enter your email address, text message, or preloaded or preinstalled The web page or application corresponding to the URL is displayed without executing the installed application. View your receipt instantly through the application page.

[0064] Another exemplary embodiment is a computer-implemented method, the method comprising one or more purchase and payment steps. Transaction information including multiple receipt elements containing date and time information corresponding to a transaction involving a payment and using a hash function applied to the transaction information and / or date Use your personal information and time information and / or a unique device identifier to identify your unique transaction. generating a transaction identifier; generating a URL including the unique transaction identifier; and and URL to the server, and the URL is transmitted to the Generate an NFC Data Exchange Format (NDEF) message that contains the and sends an NFC signal corresponding to the NDEF message to the user via the NFC tag controller. and issuing to the user device a URL to a website on the server corresponding to a receipt for the transaction. The receipt identifies the web resource and is generated by the server upon receipt of the transaction information. When the user device receives the NFC signal, it will send an email address, text, Messages or running preloaded or preinstalled applications immediately through the web page or application page corresponding to the URL without View receipts.

[0065] Another exemplary embodiment is a method of issuing an electronic receipt, the method comprising: receiving the information; generating an address corresponding to the transaction information; and The transaction information is stored on the server, and the generated address is sent to the user via wireless communication technology. The device will receive the transaction information and the generated email will be sent to the address sent. and displaying the child receipt by the user device.

[0066] Another example embodiment is a computing device, The processor has a processor and at least one memory connected to the processor, and The instructions stored in another memory, when executed by the processor, give the processor Any of the methods described herein may be carried out.

[0067] Another example embodiment is a non-transitory computer-readable medium, The data-readable medium contains instructions that, when executed by a processor, cause the processor to perform the functions described herein. The method may be:

[0068] FIG. 10 illustrates an electronic receipting computing system 1000 according to an example embodiment. Referring to FIG. 10, the POS terminal 100, the electronic receipt generator 2000, the server The server 300, the transfer rail 1010, the issuer computing device 1020, and the user 10 shows an electronic receipt issuing computing system 1000 including the device 400. The electronic receipt generator 2000 is a computing device. In the example shown, the electronic receipt generator 2000 provides PIN transaction services, interaction It can act as a Point of Interest (PTS POI) device.

[0069] POS terminal 100, server 300, electronic receipt generator 2000, transfer rail 1010, The issuer computing device 1020 and the user device 400 are connected to a network. Some of the devices may communicate over a network (not shown), for example, a wireless network. In some implementations, the wireless network may be the Internet. In this example, the POS terminal 100, the server 300, the electronic receipt generator 2000, and the transfer rail 101 are connected to the POS terminal 100. 0, the issuer computing device 1020, and the user device 400 are connected via a Wi-Fi The user device 400 can be connected to the Internet via Wi-Fi technology. In other words, the user device 400 may include an NFC tag reader. This may include background NFC tag reading capabilities.

[0070] As shown, the POS terminal 100 is an electronic receipt terminal that operates to generate electronic receipts. The device can communicate with the book collection generator 2000. Such communication can be achieved, for example, by a USB connection. Such communication may be via a wired connection, for example, a wireless connection such as Bluetooth®. The POS terminal 100 may be equipped with a physical token reader. A physical token reader may be called an NFC tag reader.

[0071] The electronic receipt generator 2000 can communicate with the transfer rail 1010. 1010 relays the transaction data to the appropriate issuer computing device 1020 Such communication may occur over a network, such as a wireless network. Transfer rail 1010 is sometimes referred to as a payment rail. 010 is a payment protocol that allows electronic money transfers to take place between payers and payees. processor, platform, server, or network infrastructure. In examples, money transfers can be made across countries, currencies, digital payment methods, or whether the payer or recipient is a business or consumer. Each payment rail offers different payment types, speeds, and technology. There are different ways to accomplish this process based on technology and geographic location. 10 examples include Automated Clearing House (ACH), Mastercard, VISA (and other major credit card providers), PayPal, RTP Network, Blockchain, SWI FT, and SEPA.

[0072] The POS terminal 100 and / or the electronic receipt generator 2000 are associated with the acquirer. The POS terminal 100 and / or the electronic receipt generator 2000 and the transfer rail 131 Communication between the PO and the PO may be via a back-end acquisition computing device. The S Terminal 100 may be located at a location associated with a transactor, such as a merchant. The seller is a store, restaurant, gym, etc. The acquirer is the person who receives the transaction made at the POS terminal 100. Accepting deposits related to purchases and clearing and depositing those deposits into accounts related to the merchant In some examples, the POS terminal 100 may be a merchant bank that facilitates can also issue electronic receipts for fiat currency (cash) transactions.

[0073] Although a single transfer rail 1010 is shown in FIG. 10, in reality, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1010 can accept Amex®, Visa®, and / or Mastercard®, or any combination thereof. Other transfer rails may also be used. 00, and / or in communication with the POS terminal 100 and / or the electronic receipt generator 2000 The back-end acquiring computing device acquires data from the physical token. After that, the price transfer card is engaged with a physical token reader provided on the POS terminal 100. The user device 400 having a display of the payment card will determine which transfer rail is being used. For example, a POS terminal / acquiring computing device may determines that the application is associated with Visa® and issues a Visa® You can also choose to use a Mastercard (registered trademark) payment rail, or alternatively, a physical token. ) and select the payment Mastercard® payment rail You can also do this.

[0074] After the transfer rail 1010 is identified, the POS terminal / electronic receipt generator / acquisition computer The network device sends a message to the transmission rail 1010. Messages may include any information forwarded to complete a transaction. The token contains a value representing the amount of the price to be paid and the Primary Account Number (PAN) associated with the physical token. It may contain physical token data such as the account number. The token identifies the associated issuer based on the physical token data, and the identified issuer More specifically, the transfer rail 1010 communicates with the POS terminal 1010 to process the transaction. 00 and / or the message received from the electronic receipt generator 2000 to the identified sender The transaction is then routed to the issuer computing device 1020 of the issuer. The computing device 1020 determines whether the transaction is authorized based on predefined rules. Rules determine whether a cardholder can use available funds or be denied access. whether the merchant has a spending limit, whether the transaction is within the permitted type, The court may take into account one or more of the following:

[0075] The issuer computing device 1020 decides whether to approve or deny the transaction. When the decision is made, a message indicating the result of this decision is transmitted to the POS terminal 10 via the transmission rail 1010. 0 and / or the electronic receipt generator. The results are then displayed on the POS terminal 100. The information may be displayed or output.

[0076] FIG. 2 shows an example of the internal configuration of the electronic receipt generator 2000 shown in FIGS. 1 and 10. Referring to FIG. 2, the electronic receipt generator 2000 includes various components. The various components may include, for example, a network a network interface 2010, a communication module 2020, a memory 2030, and a program Storage 2040, controller 2050, address generator 2060, and N An FC tag controller 2070 may be included.

[0077] In some embodiments, two or more operatively connected components 2010, 2012, 2014, 2016, 2018, 2019, 2020, 2021, 2022, 2023, 2024, 2025, 2026, 2027, 2028, 2029, 2030, 2031, 2032, 020, 2030, 2040, 2050, 2060, and 2070 are joined together, It can exist as a single component. In some embodiments, A component can consist of multiple components according to one or more functions of that component. It can be divided into

[0078] The network interface 2010 cooperates with the communication network to provide addresses, For example, an interface for transmitting a URL and corresponding transaction information to the server 300 Provides services.

[0079] The communication module 2020 enables the electronic receipt generator 2000 to communicate with other computers or to communicate with various computing devices and / or various communications networks For example, the communication module 2020 may be configured to allow the electronic receipt generator 2000 to send or receive communication signals. The communication signals may be transmitted or received according to one or more protocols. The communication module 2020 may transmit or receive signals according to one or more standards. The electronic receipt generator 2000 is, for example, a mobile communication (GSM), a code division multiple access (CD MA), Evolution Data Optimization (EVDO), Long-Term Evolution ( One or more standardized technologies, such as LTE (Long Term Evolution) for global computing devices In accordance with the present invention, communication over a cellular data network can be achieved. Additionally or alternatively, the communication module 2020 may be configured to enable the electronic receipt generator 2000 to communicate with an NFC via Wi-Fi, Bluetooth, and can communicate over one or more networks or any combination of protocols In some embodiments, all or part of the communication module 2020 may be integrated into the components of the electronic receipt generator 2000. For example, The communication module 2020 may be integrated into a communication chipset. The terminal 100 may include a communication interface for receiving transaction information.

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

[0081] The program storage 2040 executes the tasks of transmitting data to the server 300, A task to receive data from the terminal 100, a task to generate an address corresponding to the transaction information, Task to generate a message corresponding to the transaction information, generate a message corresponding to the address The control software performs tasks such as programming the message into an NFC tag. In some embodiments, the program storage is memory 2030. In some embodiments, the program may form part of Some or all of the control software may be stored in one or more applications in memory 2030. The ion implantation step may form at least a part of the ion implantation step.

[0082] The controller 2050 is a type of central processing unit (CPU) and controls the electronic receipt generator 2 In other words, the process of generating an electronic receipt can be controlled by the The controller 2050 uses the control software stored in the program storage 2040. It can perform a variety of services, such as

[0083] The address generator 2060 generates a unique address corresponding to the received transaction information. In some embodiments, the address can be generated from a web address on the Internet. This refers to the URL for accessing a website or web page, but in the example embodiment, However, it is not limited to the above.

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

[0085] According to one embodiment, the electronic receipt generator 2000 generates an identifier ( A unique transaction identifier (ID) may be generated. For example, in some embodiments, an ID based on information about the electronic receipt generator 2000 and / or the transaction date and According to another embodiment, the electronic receipt generator 2000 may generate an electronic receipt based on the time of purchase. The identifier may be generated using hashing techniques, which are generated using a hash function. , refers to a technique for obtaining a single result value corresponding to a single input value. In this form, the identifier is obtained through hashing techniques that use transaction information as input. However, the method of generating the identifier according to the embodiment is not limited to this. It is not something that can be done.

[0086] The NFC tag controller 2070 controls the NFC tag to identify the address. A corresponding message is generated and emitted as an NFC signal. The message may be in the specific format used for NFC. The format of the message is determined by the user device 400 receiving the corresponding message. It can also refer to a format that allows instantaneous execution of an action, e.g., an NFC tag The controller 2070 generates an NDEF message containing information to be sent to the user device 400. In some implementations, the address is In such an implementation, the user device 400 When a message is received, a predetermined operation can be performed. Open the web page linked to the address via your browser application. may be.

[0087] FIG. 3 is a block diagram showing an example of the internal configuration of the server 300 shown in FIGS. 1 and 10. Referring to Figure 3, a server 300 may include various components. These components include, for example, a communication module 310, a memory 311, and a 20, program storage 330, controller 340, database 350, and Includes e-receipt application programming interface (API) 360 obtain.

[0088] The communications module 310 allows the server 300 to communicate with other computers or computing to communicate with devices and / or various communication networks, e.g. The module 310 may enable the server 300 to transmit or receive communication signals. Communication signals may be transmitted according to one or more protocols or in accordance with one or more standards. For example, the communication module 310 may be configured to communicate with the server 300, e.g., Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimization (EV Global Computing for DO, Long Term Evolution (LTE), etc. over a cellular data network in accordance with one or more standardized technologies, such as a Additionally or alternatively, the communication module 310 may The server 300 uses NFC to communicate with the device via Wi-Fi (registered trademark) and Bluetooth ( registered trademark) or any combination of one or more networks or protocols In some embodiments, the communication module 310 may be integrated into the components of the server 300. For example, , the communication module 310 may be integrated into a communication chipset.

[0089] The communication module 310 communicates 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 communicate with another network device. Hardware and software for sending and receiving control or data signals over a wireless connection to a device and software.

[0090] The memory 320 stores data processed by the controller 340 either temporarily or permanently. In some embodiments, the memory 320 may perform functions such as storing data in a magnetic field. Although example embodiments may include electronic and / or flash storage media. Not limited to:

[0091] The program storage 330 is stored by the controller as further described below. One or more programs that consist of commands that instruct one or more processes to be run In some embodiments, the program storage 330 may store memory. In some embodiments, the program storage may form part of the library 320. The one or more programs stored in the memory 2030 may be used to control one or more applications. It may form at least a part of the

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

[0093] In some embodiments, the controller 340 may include one or more processors, In an example embodiment, a "processor" may include multiple types of devices capable of processing For example, by computing code and / or computer program instructions It is a hardware implementation having circuits physically structured to perform the functions represented. It may refer to an embedded data processing device.

[0094] The database 350 can store address information and transaction information. The information includes addresses (e.g., URLs), their corresponding identifiers, and The database 350 may contain address information, In this way, the server 300 may store the correspondence between the address and the transaction information. The information about the transaction can be used to easily determine the transaction information.

[0095] E-Receipt API360 converts transaction information into e-receipts through various applications. It provides an interface for converting data into a format. , for displaying the generated electronic receipt in the form of a web page linked to the address It also provides an interface.

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

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

[0098] The network interface 410 receives electronic receipts in cooperation with a communication network. It can provide an interface for trusting

[0099] The communications module 420 allows the user device 400 to communicate with other computers or to communicate with various computing devices and / or various communication networks. For example, the communication module 420 may be a module that allows the user device 400 to transmit or receive communication signals. The communication signals may be transmitted according to one or more protocols or in accordance with one or more For example, the communication module 420 may The device 400 may be, for example, a mobile communication system (GSM), a code division multiple access (CDMA), an Evo Solution Data Optimization (EVDO), Long Term Evolution (LTE), etc. According to one or more standardized technologies, such as global computing devices for and / or Instead, the communication module 420 enables the user device 400 to communicate with Wi-Fi using NFC. over Wi-Fi, using Bluetooth, or using one or more networks The network may communicate via any combination of networks or protocols. In some embodiments, all or part of the communication module 420 is a user device 4 For example, the communication module 420 may be integrated into a communication chip. may be integrated into a subset.

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

[0101] The memory 430 temporarily stores data processed by the controller 460. and / or the address received from the electronic receipt generator 2000 (e.g., RL) can be temporarily stored.

[0102] I / O (input / output) module 440 may be a touch-sensitive display controller or other The I / O module may be configured to operate as an input / output controller for a touch-sensing In some examples operating as a display controller, a touch-sensitive display controller The controller provides the output and input interfaces between the device and the user. In some implementations, the touch-sensitive display controller may The controller 460 can transmit electrical signals to the controller 460 and receive electrical signals from the controller 460. In some embodiments, the touch-sensitive display controller provides visual feedback to the user. Visual output can include text, graphics, images, and video. , and combinations thereof. In some embodiments, the I / O module 440 may be, for example, an organic light emitting display (OLED) or a liquid crystal display (LCD ) and other display components that can recognize touch input. 440 is accessed via a web browser application based on the address received. An electronic receipt can be displayed on the accessed web page.

[0103] The program storage 450 receives a message from the electronic receipt generator 2000, Checks the format of the received message and determines if the received message is an NDEF message. If the page is an NDE page, the expected behavior is to open the NDE page through a web browser application. Contains software that performs tasks such as retrieving addresses contained in F messages do.

[0104] The controller 460 may be a CPU and controls the electronic domain via the user device 400. In other words, the controller 460 may: It executes various services such as control software stored in the program storage 450. The service can be performed.

[0105] Next, a flow chart of an exemplary method 1100 for issuing an electronic receipt will be described, according to an example embodiment. 11, which illustrates a PTS POI device. The electronic receipt generator 2000 (FIG. 10) may generate a receipt. When operating as a PTS POI device, the electronic receipt generator may TS POI may include a PCI certified payment module resident in the device's memory. do.

[0106] The exemplary method 1100 specifically includes a control block for the electronic receipt generator 2000 (FIG. 10). This may be performed by a processor in the roller 340 (FIG. 3).

[0107] At operation 1110, a computing device receives transaction information corresponding to a transaction. The transaction information may be received, for example, from a POS terminal 100 (FIG. 10). Transaction information may include multiple items and payments, including date and time information. The transaction information may contain multiple receipt elements. Text formats such as JSON, delimited text files, etc. It may also be in a store-based flat file format.

[0108] In operation 1120, the computing device transmits the transaction information to the transfer rail 1010 (FIG. 10). The transaction information resides in the memory of the computing device. It can be transmitted via modules such as PCI certified payment modules. At the same time, the transfer rail 1010 (FIG. 10) transfers the card data from the POS terminal 100 (FIG. 10). The transferred card data can be used to receive the value transferred to complete the transaction. A price representing the value of the token and a physical token such as a Primary Account Number (PAN) associated with the physical token. It may also include token data.

[0109] At act 1130, the computing device generates a unique transaction identifier. In some instances, the unique transaction identifier is generated using a hash function applied to the transaction information. Alternatively, in some examples, the unique transaction identifier may be a unique device identifier and and / or may be generated using date and time information associated with the transaction. In an embodiment where the child receipt generator 2000 (FIG. 10) is a PTS POI device, The device identifier may be a unique device identifier of the PTS POI device. In one example, the unique device identifier is for the computing device. , a unique device identifier is stored on the computing device or PTS POI device serial number, ID number, International Mobile Equipment Identity (IMEI), or media access In the example, the unique transaction identifier includes date information, time information, and a unique device identifier.

[0110] At act 1140, the computing device generates a unique URL. L may be based on a unique transaction identifier. A unique URL corresponds to the electronic receipt for the transaction. A web resource may be a resource that identifies a web resource that resides on a server. The unique URL is in the format www.domain / unique transaction identifier / receipt element. The "receipt element" of the URL may be associated with transaction information.

[0111] In some embodiments, the computing device receives data via a communication module. The information can then be sent to the server 300 (FIG. 10). 0) generates the first electronic receipt for the web resource associated with the URL In some embodiments, for example, because there is no internet connection, In such cases, the computing device may not be able to communicate with the server 300. In an embodiment, the computing device comprises a computing device and a server. When communication between them is restored, the information sent to the server can be processed.

[0112] At operation 1150, the computing device is transferred from the transfer rail 1010 (FIG. 10) and receiving confirmation of successful completion of the transfer card transaction corresponding to the transaction information. The confirmation is modules, such as PCI-certified payment modules, that can reside in the memory of an operating device. The computing device may receive the transaction information via the A confirmation of successful completion of the corresponding transfer card transaction is sent to the NFC tag controller 2070. The confirmation can be included in the NDEF message. If the transaction is rejected by the transfer rail 1010 If rejected, the computing device rejects the transfer card transaction corresponding to the transaction information. The NFC tag controller 2070 transmits a "no" to the NFC tag controller 2070.

[0113] At operation 1160, the computing device transmits the URL to the NFC tag controller 2. 070. In some embodiments, the computing device is a PTS POI device, the NFC tag controller 2070 It may be integrated into the POI device. Alternatively, in some embodiments, the NFC tag may be The programming controller 2070 may be external to the computing device.

[0114] After receiving the URL, the NFC tag controller 2070 sends the URL as a payload. Then, the NFC tag controller 2 can generate an NDEF message containing the 070 can emit an NFC signal with a URL as the payload.

[0115] In some embodiments, the NFC signal is an NDEF file with a URL as a payload. Alternatively, in some embodiments, the tag may be in NDEF format. The formatted NFC tag is, for example, Apple's Universal Link U It may be an NDEF formatted tag with a URL. In the embodiment, the NFC tag in NDEF format is, for example, Apple's AppClips Link It may be an NDEF tag with a URL, or in some embodiments , NDEF format NFC tags, for example, Android (registered trademark) App Link It can be a tag in NDEF format with a URL. In terms of form, NFC tags in NDEF format are, for example, It can be an NDEF format tag with the URL of the target app. In some embodiments, the NFC tag in NDEF format is, for example, a mini-application The URL may be an NDEF format tag with the URL of the link. In this case, the payload may be a Progressive Web App-based URL. For example, Examples include Apple's (registered trademark) "AppClips" and Google's (registered trademark) "InstantApps" and Snapchat's (registered trademark) "SnapMini" are mentioned. can be done.

[0116] Once the NFC signal is emitted, it can be received by the user device 400 (FIG. 1 0). For example, a shopper may use a computing device, such as a PTS POI device, The user taps the user device 400 (Figure 10) on the device and receives the URL via the NFC signal. The user device 400 (FIG. 10) can read and write UR data via an NFC tag reader. It is possible to receive an NFC signal containing L as a payload.

[0117] Following operation 1160, when an NFC signal is emitted, it is detected by the user device 400. For example, the shopper may receive the receipt from the electronic receipt generator 2000 (FIG. 10). ) on the user device 400 (Figure 10) to receive the URL via the NFC signal. The user device 400 (FIG. 10) receives the URL from the payload via an NFC tag reader. It can receive NFC signals containing the card.

[0118] In some embodiments, when the user device 400 (FIG. 10) receives an NFC signal, , the NFC tag launches a web browser application or other application A web browser application or other application can access the URL As mentioned above, a URL can be a "www.domain" or a "web resource" that is associated with a The "receipt element" of the URL may be in the format " / unique transaction identifier / receipt element". The web resource may include a first electronic receipt and may be related to transaction information.

[0119] Web resources can be accessed, for example, via Progressive Web Apps, Responsive Web Apps (web apps using Java Script (registered trademark), etc.), Rich Internet Can be launched via a mobile app, a single-page app, or a multi-page app .

[0120] In some embodiments, the user device 400 (FIG. 10) stores and displays receipts. In some such embodiments, the application may include: The user device 400 (FIG. 10) includes an iOS device that includes Apple™ Universal Links. In such an embodiment, the user device 400 ( When the device (Figure 10) receives the NFC signal, it uses Apple® Universal Link to Display and / or store one electronic receipt in a receipt storage and display application. In some such embodiments, the user device (Figure 10) is not an iOS phone, but a deep link (e.g., Android In such an embodiment, the user device may include an AppLink. When the NFC signal is received by the device 400 (FIG. 10), the deep link sends the first electronic receipt to the device 400. Receipt storage and viewing applications can display and / or store receipts. The first electronic receipt may be in a format determined by the transactors involved in the transaction. It can be displayed by the application.

[0121] In some embodiments, the user device 400 (FIG. 10) stores and displays receipts. In some such embodiments, the application may not include a display application. The user device 400 (FIG. 10) receives an iOs file containing an Apple® Universal Link. If it's an S® phone, the Apple® Universal Link will be located on the receipt. Users must be registered with Apple to download applications for storage and viewing. In some such embodiments, users may be directed to a registered trademark (e.g., a registered trademark) app store. If the user device 400 (FIG. 10) is not an iOS phone, App Link (e.g., Android App Link) is a service for storing and displaying receipts. Directing users to a mobile app store to download the application In some cases where the user device 400 (FIG. 10) is an iOS® phone, In some such embodiments, the user device 400 (FIG. 10) is an Apple® ) App Clip link and launch the App Clip. In such an embodiment, if the user device is a non-iOS phone, The user device 400 (FIG. 10) receives the instant app link and In some such embodiments, the user device 40 0 (Fig. 10) can receive a Mini appli link and launch the Mini appli.

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

[0123] In some embodiments, the user device 400 (FIG. 10) includes a first electronic receipt. Launches a web browser application that renders output at a specific URL location. The format of the first electronic receipt may be used to process the transaction related to the first electronic receipt. The first electronic receipt may be in a format determined by the purchaser. and displayed by the user device using the application. Applications can be, for example, progressive web apps, Responsive web applications (web applications using Java Script (registered trademark)), whether it is a touch internet app, single page app, or multi-page app. The first electronic receipt may be stored in a first location by a corresponding application. obtain.

[0124] In some embodiments, as previously mentioned, the application may be an Apple® Universal Link, or related non-iOS mobile applications or It can be launched by a non-iOS or web application. When launched by an S® application, the application It may be launched via AppLink or by Android® App Link. In such an embodiment, the application may include a step of: The first electronic receipt can be displayed in a format determined by the first electronic receipt. The receipt may be stored in a first location by a corresponding application.

[0125] Referring now to FIG. 12, FIG. 12 illustrates an example of an electronic receipt issuing computer system according to an example embodiment. 12 is a diagram illustrating a system 1200 for a POS terminal 100. The computing device operating and the functions of the electronic receipt generator 2000 (FIG. 10) 12 shows an electronic receipt issuing computing system 1200 including: The issuing computing system includes a server 300, a card reader (CR) device 12, 10, a transfer rail 1010, an issuer computing device 1020, and a user In some embodiments, the electronic receipt issuing computer is also shown to include a device 400. The CR device 1210 of the computing system 1200 is a commercial off-the-shelf NFC-enabled device card reader with PCI software-based PIN entry The computer that operates as the POS terminal 100 is sometimes called SPoC. The operating device may be a SPoC device and / or a commercial off-the-shelf (COTS) device. It is sometimes called a chair.

[0126] A computing device operating as a POS terminal 100, a server 300, a CR device device 1210, transfer rail 1010, issuer computing device 1020, and The user device 400 communicates with a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the computer operating as the POS terminal 100 may be a communication device, a server 300, a CR device 1210, a transfer rail 1010, The traveler computing device 1020 and the user device 400 are connected via Wi-Fi The user device 400 can be connected to the Internet via NFC technology. In other words, the user device 400 may include an NFC reading function. Or it may include background NFC tag reading capability.

[0127] As shown in the figure, the CR device 1210 is a computer that operates as a POS terminal 100. The POS terminal 100 can communicate with the payment device and generate an electronic receipt. Such communication may be performed using a wired connection, such as a USB connection. Such communication may be via a wireless connection, such as Bluetooth®. You can do this.

[0128] The computing device operating as the POS terminal 100 is connected to a transfer rail 1010 The transfer rail 1010 can communicate with the appropriate issuer computer to transfer the transaction data. Such communication may be relayed to a receiving device 1020 via a network such as a wireless network. The transfer rail 1010 is also called the payment rail. There are also.

[0129] A computing device operating as a POS terminal 100 is associated with an acquirer. 10, a computing device operating as a POS terminal 100 and a transfer rail 1010 Communication between the POS and the acquirer may be via a back-end acquirer computing device. The computing device acting as the terminal 100 may be associated with a merchant. For example, a merchant may be a store, restaurant, gym, etc. relates to transactions conducted on a computing device operating as a POS terminal 100 accepts deposits from the relevant parties and facilitates the settlement and crediting of those deposits to the accounts associated with the parties; It may also be a merchant bank that facilitates

[0130] Although a single transfer rail 1010 is shown in FIG. 12, in reality, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1010 can accept Amex®, Visa®, and / or Mastercard®, or any combination thereof. Other transfer rails may be used. a computing device operating as a point-of-sale (POS) terminal 100; The back-end acquiring computing device that communicates with the acquiring device is the POS terminal 10. A balance transfer card having a representation of a payment card engaged with a CR device 1210 provided at After obtaining the data from a physical token such as a card or mobile device, Determines whether a POS terminal / acquirer computing device is used. The service determines that the physical token is associated with Visa® and accordingly You can choose to use Visa® payment rails, or alternatively, a physical token is MasterCard. and determine that the payment is associated with a Mastercard® payment account. You can also select a rule.

[0131] After the transfer rail 1010 is identified, the POS terminal 100 / acquirer computing device The computing device acting as a The message may be sent over a network. A price amount representing the amount of the price transferred to complete the transaction and a token associated with the physical token. May contain physical token data such as Primary Account Number (PAN). 10 identifies the relevant issuer based on the physical token data and communicates with the identified issuer. More specifically, the transfer rail 1010 functions as a POS terminal 100. a message received from a computing device operating in accordance with the routed to the issuer computing device 1020. The operating device 1020 approves or rejects the transaction based on predefined rules. The rules determine, for example, whether the cardholder has available funds. whether the merchant is an authorized type, whether the transaction violates spending limits, One or more factors may be considered, such as whether

[0132] The issuer computing device 1020 decides whether to approve or deny the transaction. When the decision is made, a message indicating the result of this decision is transmitted to the POS terminal 10 via the transmission rail 1010. The result is then sent to a computing device acting as a POS terminal. 100 may be displayed or output.

[0133] The computing device operating as the POS terminal 100 is 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. The electronic receipt issuing computer shown in FIG. In an embodiment of the computing system 1200, a computer operating as the POS terminal 100 The receiving device includes the functionality of an electronic receipt generator 2000 (FIG. 10).

[0134] The user device 400 may include a mobile wallet that stores a representation of a payment card. The physical token stores the data and / or resources that the cardholder has access to. One example is a physical token that can be connected to one or more accounts (such as a bank account) that store the tokens. The account may be linked to a bank account and / or a credit card account. A physical token may function as a credit or debit card. Kun can be used to make purchases at point-of-sale terminals. Such physical tokens are The physical token is placed within communication range of a physical token reader such as the CR device 1210. Configure for tap-style payments that allow you to read physical token data from the It is possible.

[0135] The user device 400 may be configured for Near Field Communication (NFC) payment transactions or for other types of payment. The device may be configured for wireless communication-based payment processing.

[0136] The CR device 1210 is a computing device that operates as the POS terminal 100. The CR device 1210 communicates with the transfer card, or a representation of the transfer card, stored therein. The device may be configured to read a physical token, such as a mobile device that is connected to the device. The CR device 1210 may be configured to receive the transferred card data. A physical token reader is a card slot that facilitates communication with a physical token through physical contact. via a communication protocol that does not rely on physical contact with the physical token. Contactless, such as near-field communication (NFC) readers that facilitate communication with physical tokens The CR device 1210 may be or include an NFC tag. The system may include a timing controller 2070.

[0137] Next, a flowchart of an exemplary method 1300 for issuing an electronic receipt will be described, according to an example embodiment. 13, which illustrates an example method 1300. Executed by a computing device, such as a computing device operating A computing device operating as a POS terminal 100 (FIG. 12) may A PCI certified payment module that can reside within the memory of a computing device. In some embodiments, a computer operating as a POS terminal 100 (FIG. 12) may be included. The computing device may be a CPoC device and / or a SPoC device. obtain.

[0138] The exemplary method 1300 specifically relates to a computer operating as a POS terminal 100 (FIG. 12). Executed by a processor in the controller 340 (FIG. 3) of the computing device. obtain.

[0139] The exemplary method 1300 is a modification of the exemplary method 1100 of FIG. in that it includes two additional operations 1112, 1114 between operations 1110 and 1120. , which differs from the exemplary method 1100 of FIG.

[0140] At operation 1110, a computing device receives transaction information corresponding to a transaction. A transaction may include one or more items and a payment. Transaction information includes date and time information. The transaction information may contain multiple receipt elements, including: , Java Script (registered trademark) object notation, delimited text files, and other text It may be in a flat file format based on the

[0141] In some embodiments, after operation 1110, the computing device The transfer card data can be acquired by starting the device 1210 (FIG. 12).

[0142] At operation 1112, the computing device receives a Transfer card data is received from a wired connection such as a USB connection. The transfer card data may be received via, for example, Bluetooth®. It may be received over a wireless connection.

[0143] As described above, the CR device 1210 (FIG. 12) includes an NFC tag controller 2070. The CR device 1210 (FIG. 12) may include a transfer card, or a representation of a transfer card. The authentication method may be configured to read a physical token, such as a mobile device, on which the authentication information is stored. In this way, the CR device 1210 (FIG. 12) is configured to receive the transferred card data. A physical token reader can be configured to facilitate communication with a physical token through physical contact. card slots to facilitate communication that does not rely on physical contact with a physical token Near Field Communication (NFC) link that facilitates communication with physical tokens via a protocol The reader may be or include a contactless reader such as a CR reader. Device 1210 (FIG. 12) communicates transfer card data to a computing device. The device may be operable to:

[0144] At operation 1114, the computing device is transferred to transfer rail 1010 (FIG. 12). The transmitted card data is stored in the memory of the computing device. Transmitted via modules such as PCI certified payment modules that can reside within The transfer card data may be transmitted over a network. The code data includes a price representing the amount of value transferred to complete the transaction and a physical token. It may include physical token data such as an associated primary account number (PAN).

[0145] In operation 1120, the computing device transmits the transaction information to the transfer rail 1010 (FIG. 10) The transaction information includes multiple receipt elements including date and time information. Transaction information is stored in Extensible Markup Language (XML), Java Script (registered trademark) objects, and Text-based flat files such as JSON (Object Notation) and delimited text files It may be in the file format.

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

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

[0148] At act 1140, the computing device generates a unique URL. L may be based on a unique transaction identifier. A unique URL corresponds to the electronic receipt for the transaction. The web resource may be a resource that identifies a web resource that is accessible from server 300 (see FIG. 1). 2) The unique URL may be located on the The "receipt element" of the URL may be related to transaction information. .

[0149] In some embodiments, the computing device receives data via a communication module. The server 300 (FIG. 12) may then send the reference information associated with the URL to the server. In some embodiments, the first electronic receipt may be generated at the selected web resource. For example, if a computing device is unable to access a service due to the absence of an internet connection. In such an embodiment, the computing device and When communication with the server 300 (FIG. 12) is restored, the computing device , may queue the transaction information to be sent to the server.

[0150] In operation 1150, the computing device receives from the transfer rail a transaction corresponding to the transaction information. and receiving confirmation of successful completion of the transfer card transaction. The confirmation may be received from the computing device. Payments can be received through modules such as PCI certified payment modules that can reside in memory. The computing device can transmit a transfer card transaction corresponding to the transaction information. The NFC tag controller 2070 receives a confirmation of successful completion of the request. If the transaction is rejected by the transfer rail 1010, The computing device may issue a denial of the transfer card transaction corresponding to the transaction information to the NFC tag computer. Send to Trolla 2070.

[0151] At act 1160, the computing device sends the unique URL to the NFC tag controller. In some embodiments, the NFC tag controller 2070 The laser 2070 may be integrated with the CR device 1210 (FIG. 12). In such an embodiment, the computing device may send the unique URL to the CR device 12. 10 (Figure 12).

[0152] After receiving the URL, the NFC tag controller 2070 sends the URL as a payload. Then, the NFC tag controller 2 can generate an NDEF message containing the 070 can emit NFC signals with a URL as the payload. In some embodiments, the CR device 1210 (FIG. 12) may send a URL as a payload. The NFC signal may be emitted.

[0153] In some embodiments, the NFC signal is an NDEF file with a URL as a payload. Alternatively, in some embodiments, the tag may be in NDEF format. The formatted NFC tag is, for example, the Apple® Universal Link U It may be an NDEF formatted tag with a URL. In an embodiment, the NFC tag in NDEF format is, for example, Apple™ AppClip Link. Alternatively, in some embodiments, the URL may be an NDEF tag containing the URL of the link. In this case, NFC tags in NDEF format are used, for example, in Android (registered trademark) AppClips Link. It can be a tag in NDEF format with the URL of the link. In this embodiment, the NFC tag in NDEF format is, for example, It can be a tag in NDEF format with the URL of the Instant App Link. Alternatively, in some embodiments, the NFC tag in NDEF format may be, for example, It can be a tag in NDEF format that contains the URL of the mini-app link. In some embodiments, the payload is a Progressive Web App-based URL. Good too.

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

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

[0156] The computing device operating as the POS terminal 100 is equipped with an NFC tag reader and The physical token reader may be configured to operate as what is sometimes called a physical token reader, i.e. The computing device operating as the POS terminal 100 may be a transfer card or The user device 400 may be configured to read a physical token such as a user device 400 on which a representation of the sending card is stored. In this way, the computer that operates as the POS terminal 100 can The physical token may be configured to receive the card data. The reader communicates with the physical token through a communication protocol that does not rely on physical contact with the physical token. Contactless cards, such as Near Field Communication (NFC) readers, that facilitate communication with the The computing device operating as the POS terminal 100 may be a reader. , may include an NFC tag controller.

[0157] The computing device operates as a POS terminal 100 and generates electronic receipts. It can operate like this.

[0158] The computing device operating as the POS terminal 100 stores the transaction data in an appropriate Communicating with a forwarding rail 1010 that relays to an issuer computing device 1020 Such communication may be carried out over a network such as a wireless network. The transfer rail 1010 may also be referred to as a payment rail.

[0159] A computing device operating as a POS terminal 100 is associated with an acquirer. 1. A computing device operating as a POS terminal 100 and a transfer rail 1 Communication between the 010 and the acquirer may be via a back-end acquirer computing device. The computing device operating as the POS terminal 100 is used to process transactions with merchants and the like. For example, a merchant may be located at a store, restaurant, gym, or other location associated with the merchant. The acquirer may use a computing device that operates as a POS terminal 100. Accepting deposits in connection with transactions made on the It may also be a merchant bank that facilitates deposits into the account.

[0160] Although a single transfer rail 1010 is shown in FIG. 14, in reality, the POS terminal 100 and / or the electronic receipt generator 2000 may communicate with multiple transfer rails. By way of example, the transfer rail 1310 can accept Amex®, Visa®, and / or Mastercard® Other transfer rails may be used. a computing device that operates as a POS terminal 100; A back-end acquirer computing device that communicates with the price transfer card or After acquiring data from a physical token such as a mobile device, the POS terminal 100 A device having a representation of a payment card engaged with an operating computing device. The system determines which transfer rail should be used. For example, the POS terminal / acquirer console The computing device is connected to a physical token associated with Visa®. and select the Visa® payment rail accordingly, or alternatively , determining that the physical token is associated with Mastercard®, and You can also choose to pay via the ® payment rail.

[0161] After the transfer rail is identified, the POS terminal 100 / acquirer computing device and A computing device operating in accordance with the rules sends a message to the transfer rail. A message may be sent over the network. The message may include a The price amount representing the amount of value to be transferred for the transaction and the primary account number associated with the physical token ( The transfer rail 1010 may include physical token data such as a personal information account (PAN). Identifying relevant issuers based on token data and communicating with the identified issuers to conduct transactions More specifically, the transfer rail 1010 is a computer that operates as a POS terminal 100. The message received from the identified issuer's computing device is forwarded to the issuer's computing device. The issuer computing device 1020 then routes the The device 1020 determines whether a transaction is approved or rejected based on predefined rules. Rules determine, for example, whether the cardholder has available funds. whether the merchant is an authorized type and whether the transaction violates spending limits. There may be more than one consideration, such as:

[0162] The issuer computing device 1020 decides whether to approve or deny the transaction. When the decision is made, a message indicating the result of this decision is transmitted to the POS terminal 10 via the transmission rail 1010. The result is then sent to a computing device acting as a POS terminal. 100 may be displayed or output.

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

[0164] The user device 400 may include a mobile wallet that stores a representation of a payment card. The physical token stores the data and / or resources that the cardholder has access to. One example is a physical token that can be connected to one or more accounts (such as a bank account) that store the tokens. The token may be associated with a bank account and / or a credit card account. may function as a credit or debit card. Such physical tokens can be used to make purchases on any OS device. 100. A tap that is placed within range and allows physical token data to be read from the physical token. Can be configured for style payments.

[0165] The user device 400 may be configured for Near Field Communication (NFC) payment transactions or for other types of payment. The device may be configured for wireless communication-based payment processing.

[0166] The method 1300 (FIG. 13) is performed by an electronic receipt issuing computing system 1400. This can be done.

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

[0168] As a result, when performing the method 1300 (FIG. 13), the POS terminal 100 (FIG. 14) The operating computing device may, in operation 1112 (FIG. 13), Instead, see the electronic receipt issuing computing system 1200 (FIG. 12). As explained above, transfer card data can be received directly.

[0169] Referring again to FIG. 13, at operation 1130, the computing device As previously mentioned, in some examples, the unique transaction identifier may be generated using the transaction information. It may be generated using a hash function applied to In some examples, the unique transaction identifier may be a unique device identifier and / or a transaction identifier. The time stamp may be generated using date and time information associated with the time stamp.

[0170] In operation 1130, a computing device operating as the POS terminal 100 (FIG. 14) The computing device operates as a POS terminal 100 (FIG. 14). Unique device identifier (e.g., PCI CPoC device, MPoC device, touch Tap-to-Phone devices and / or Tap-on-Phone devices) to their own devices. Used as the device identifier.

[0171] Following operation 1160, when an NFC signal is emitted, it is detected by the user device 400. For example, the shopper may receive the payment at the POS terminal 100 (FIGS. 12 and 14). 4) Touch the user device 400 (Fig. 12, 14) on the screen and send the URL via NFC signal. The user device 400 (FIGS. 12 and 14) is an NFC tag reader. can receive an NFC signal containing a URL as a payload via

[0172] When the user device 400 (FIGS. 12 and 14) receives the NFC signal, the NFC tag You can launch a web browser application. may display the web resource associated with the URL. The URL may be in the format "www.domain / unique transaction identifier / receipt element". The "receipt element" in the "Receipt" may be related to transaction information. A receipt may also be included.

[0173] Web resources can be accessed, for example, via Progressive Web Apps, Responsive Web Apps (web apps using Java Script (registered trademark), etc.), Rich Internet Can be launched via a mobile app, a single-page app, or a multi-page app .

[0174] In some embodiments, the user device 400 (FIGS. 12 and 14) stores and Some such embodiments may include applications for processing and displaying the In this example, the user device 400 (FIGS. 12 and 14) uses the Apple™ Universal Link. In such an embodiment, the user device may be an iOS® phone that includes When the NFC signal is received by the device 400 (Fig. 12, 14), it will The first electronic receipt is displayed and saved in the receipt storage and display application. In some such embodiments, the user The user device (Figures 12 and 14) is not an iOS phone, but a deep link (For example, App Link for Android®) So, when the user device 400 (FIGS. 12 and 14) receives an NFC signal, it The first electronic receipt is displayed and / or stored in a receipt storage and display application. The first electronic receipt may be stored or archived by the transactor associated with the transaction. It can be displayed by the application in a specified format.

[0175] In some embodiments, the user device 400 (FIGS. 12 and 14) stores and In some such embodiments, the application for displaying the image may not be included. In this example, the user device 400 (FIGS. 12 and 14) is an Apple® Universal Link If you have an iOS phone with Apple Universal Links, Allows users to download an application for saving and viewing receipts may be directed to the Apple® App Store. In some embodiments, the user device 400 (FIGS. 12 and 14) is not an iOS® phone. If a deep link (e.g., Android App Link) is used, the receipt will be displayed. and invite users to download applications for storage on mobile apps The user device 400 (FIGS. 12 and 14) is an iOS® phone. In some such embodiments, the user device 400 (FIGS. 12, 14) Able to receive Apple(R) App Clip links and launch App Clips. In some such embodiments, the user device may be a non-iOS® If so, the user device 400 (FIGS. 12 and 14) receives the instant app link. In some such embodiments, the instant app can be launched. The user device 400 (FIGS. 12 and 14) receives the mini-app link and downloads the mini-app. It can be started.

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

[0177] In some embodiments, the user device 400 (FIGS. 12 and 14) may access the unique URL You can launch a web browser application that renders the output at the location The rendered output may include a first electronic receipt. The receipt format shall be the format determined by the trader in connection with the first electronic receipt. The first electronic receipt may be generated using the transaction data, The application can be displayed by the user device. Applications include, for example, Progressive Web Apps, Responsive Web Apps (Java S Web applications using crypt (registered trademark), rich internet applications, The first electronic receipt may be a group-page app or a multi-page app. The first location may be stored in a first location by a corresponding application. The storage device 400 may be stored in the memory 430 (FIG. 4) of the user device 400 (FIGS. 12 and 14).

[0178] In some embodiments, as previously mentioned, the application may be an Apple™ Universal or any related non-iOS® mobile application or It can be launched by a web application. If launched by a .NET Framework application, the application will be deep linked. It may be launched via the Android App Link or by Android® App Link. In such an embodiment, the application may process a decision by the transactor in connection with the first electronic receipt. The first electronic receipt can be displayed in a predetermined format. , can be stored in a first location by a corresponding application. The first location can be, for example, , may be in memory 430 (FIG. 4) of user device 400 (FIGS. 12 and 14).

[0179] In some implementations, the POS terminal 100 (FIGS. 12 and 14) and the server 300 (FIG. 12) , 14). In some such embodiments, The POS terminal 100 receives the URL from the user device 400 by analyzing the URL. A URL that allows you to generate a second electronic receipt for a transaction without having to access the URL online In some instances, the second electronic receipt ultimately replaces the first electronic receipt. It can also be used as a temporary electronic receipt that can be exchanged for a computing device. If there is an Internet connection by the device 300, the POS terminal 100 Upload the transaction information of the receipt (or alternatively, the first electronic receipt itself) to the server 300. The server 300 associates the URL with the first electronic receipt. The electronic receipt can be retrieved by the user device 400. In some examples, The second electronic receipt becomes the first receipt. For example, If there is an internet connection via The URL is then sent to the user device 400, and the user device 400 is able to parse the URL and generate a second electronic receipt for the transaction. Only URLs containing this information are generated.

[0180] The second electronic receipt may be generated based on the URL received by the user device 400, e.g. For example, it may be generated by the user device 400 (FIGS. 12 and 14) by analysis. As mentioned above, the URL should be in the format "www.domain / unique transaction identifier / receipt element" The "receipt element" of the URL may relate to transaction information. generated by an application on the user device 400 using the information contained in L (Fig. 12, 14) The application can be, for example, App Clip, Instagram, For example, applications can be pre-installed. There may be cases where it is not necessary to load the

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

[0182] In some embodiments, the user keeps the second electronic receipt and the first electronic receipt. In some implementations, the user can choose to refrain from using the second You can temporarily view the electronic receipt and when the first electronic receipt becomes available ( For example, the communication between the POS terminal 100 (FIGS. 12 and 14) and the server 300 (FIGS. 12 and 14) Retrieve and use your first electronic receipt when your payment or internet connection is restored In some embodiments, the user device 400 receives the first electronic receipt. Upon receiving the first electronic receipt, the first electronic receipt may be stored in a first location by the user device 400. In this way, a second electronic receipt, also called a provisional electronic receipt in this example, is generated in addition to the first electronic receipt. It can be replaced with the first electronic receipt located at

[0183] Referring now to FIG. 15, this is a diagram illustrating how to generate a second electronic receipt, according to some embodiments. 15 is a flowchart of an example method 1500 for generating a second electronic receipt. The action may be more specifically performed by the user device 400 (FIG. 1). Specifically, the process is performed by a processor in the controller 460 (FIG. 4) of the user device 400. For example, a program stored in memory 430 (FIG. 4) of user device 400 may be executed. The processor-executable instructions are executed by one or more processors in controller 460 (FIG. 4). When executed, the user device 4 is configured to perform the exemplary method 1300 or a portion thereof. 00 can be configured.

[0184] The example method 1500 of FIG. 15 provides a second electronic receipt for a transaction, also referred to as a provisional electronic receipt. The second electronic receipt can be generated immediately. Various conditions exist, including conditions under which devices are not traditionally "prepared" to display electronic receipts. The exemplary method 1500 may be implemented, for example, by a user. prior installation, account registration, activation of the camera on the user device, and / or Applications that do not require exchanging email addresses or phone numbers with electronic receipt providers The exemplary method 1500 does not require an internet connection on the user device. Not necessary.

[0185] The example method 1500 of FIG. 15 is implemented when the user device 400 (FIG. 1) is Immediately generate a second electronic receipt for a transaction under conditions that do not include the application. It can operate like this.

[0186] The example method 1500 of FIG. 15 may be implemented using an internet connection and / or a web browser. The application operates to instantly generate a second electronic receipt when available. It is possible.

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

[0188] In some embodiments, the user keeps the second electronic receipt and the first electronic receipt. In some implementations, the user can choose to refrain from using the second You can temporarily view the electronic receipt and when the first electronic receipt becomes available ( For example, when an Internet connection is made available by the POS terminal 100, In some implementations, the first electronic receipt can be obtained and used. Upon receiving the receipt, the first electronic receipt may be stored in a first location. In this example, the second electronic receipt, also called a provisional electronic receipt, is sent to the first electronic receipt in the first location. It can be substituted for a receipt.

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

[0190] At operation 1504, the user device 400 (FIG. 1) parses the string to generate individual receipts. In some embodiments, the user device 40 0 (Figure 1) can parse a string into tokens according to defined rules. For example, In some implementations, after receiving the URL, the user device 400 (FIG. 1) The first group of characters up to and including the second slash may be ignored. In the context of the above example URL, the user device 400 (FIG. 1) You can ignore the first group: www.domain / unique transaction identifier / receipt elements .

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

[0192] At operation 1506, the user device 400 (FIG. 1) and a receipt element identifier among a plurality of receipt element identifiers. For example, in some embodiments, the user device 400 (FIG. 1) may include a plurality of receipt item identifications. An ordered list of children can be stored. In some cases, multiple receipt element identifiers can be used. The ordered list of children includes receipt authorization number, transaction date, transaction time, payment type, payment Payment amount, number of items, subtotal, tax amount, discount amount, trader name, trader number (e.g., company number), This may include one or more of the trader address, trader phone number, trader number, and the like.

[0193] In some implementations, the user device 400 (FIG. 1) displays individual receipt elements. Between each of the plurality of components and a receipt element identifier among the plurality of receipt identifiers The user device may determine the relevance of a first component of the plurality of components. Associating a component with a first electronic receipt element identifier and selecting a component from the plurality of components Associating the second component with a second electronic receipt element identifier, and with a third receipt element identifier, etc. However, as will be appreciated by those skilled in the art, multiple components may be used to determine the association. Any number of methods for determining the association between a component and a receipt element identifier may be used. There is a possibility.

[0194] In some implementations, the ordered list of multiple receipt elements may be used to determine the legal basis for the receipt. It may contain elements that meet requirements (e.g., IRS requirements).

[0195] In some implementations, the ordered list of receipt element identifiers is selected by a user. For example, in a particular implementation, an ordered list might have , Receipt approval number, Transaction date, Transaction time, Payment type, Payment amount, Number of items, Subtotal, Tax amount, Discount amount, trader name, trader number (e.g., company number), trader address, trader phone number, Or it may include a transaction number.

[0196] At operation 1508, the user device 400 (FIG. 1) generates a receipt element identifier for each receipt element. and generating a second electronic receipt including at least two of the first and second electronic receipts. The second electronic receipt is stored on the user device. Viewed via a graphical user interface (GUI) on 400 displays In some embodiments, the second electronic receipt may include at least two receipt elements. It may include an association between the principal identifier and each component.

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

[0198] Referring now to FIG. 16, an example of a receipt management user interface is shown, in accordance with an example embodiment. An exemplary display screen 1600 is shown. The receipt management user interface The exemplary display screen 1600 may be displayed on the device 400. 16. Exemplary display screen 1600 includes a first heading 1630 that reads, "Offline Version." further includes a first ordered list 1610 of a plurality of receipt element identifiers. A first ordered list of identifiers 1610 is displayed in the left column of display screen 1600 . In the example of FIG. 16, the first ordered list of receipt element identifiers is: receipt acknowledgement number, transaction date, transaction Payment time, payment type, payment amount, number of items, subtotal, tax amount, discount amount, trader name, trader number The details are the transaction number, the address of the trader, the telephone number of the trader, and the transaction number.

[0199] A set of check boxes 1620 are displayed in the right column of display screen 1600. Each checkbox in the set of checkboxes 1620 is a first order receipt element identifier. In some embodiments, the user The user can select multiple receipt element identifiers by selecting the check boxes corresponding to the desired receipt element identifiers. The ordered list of numeric receipt element identifiers can be customized.

[0200] For example, Figure 16 shows the first seven checkboxes highlighted, and the first seven 16 illustrates the selection of the corresponding receipt element identifier for the example of FIG. The options are transaction date, transaction time, payment type, payment amount, and number of items. This selection is based on the user's choice. This may be the result of a selection or may be the default setting. The first seven receipt element identifiers Selecting a suffix as the desired receipt element identifier will result in the desired receipt element being added to the corresponding intermediate receipt. Sheet element identifiers and associated components for one or more components are displayed. If you do not select the remaining receipt element identifiers, the corresponding intermediate receipt The remaining receipt element identifiers and related components of multiple components are displayed. This may not be possible.

[0201] Referring now to FIG. 17, an exemplary display screen of a second electronic receipt, according to an example embodiment. Example display 1700 is shown. Example display 1700 includes a heading 1730, e.g., "Receipt-O The exemplary display screen 1700 includes a "Flying Version" on the left side of the display screen 1700. It further includes a second ordered list 1710 of receipt element identifiers. The second ordered list of receipt element identifiers includes receipt acknowledgement number, transaction date, transaction time, payment The second ordered list of receipt elements 1710 is shown in FIG. This corresponds to the selection of the first seven receipt element identifiers indicated by 16.

[0202] A list of components 1720 is displayed in the right column of display screen 1700. Each component in the list of components 1720 is a second ordered list of receipt elements 1 710.

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

[0204] As discussed above in connection with operation 1506 of FIG. 15, in some implementations, The device 400 (FIG. 1) includes a plurality of components and a plurality of receipt identifiers. The association between the receipt element identifiers can be determined. and associating a first component of the electronic receipt element identifier with a first electronic receipt element identifier, Associating a second component of the number of components with a second electronic receipt element identifier. and the third component of the multiple components is the third receipt element identifier. However, as will be appreciated by those skilled in the art, Any number of methods may be used to determine the association between a receipt element identifier and a component, such as: It can be used.

[0205] Following generation of the second electronic receipt, the user device 400 (FIG. 14) may access the second electronic receipt by the URL. The web resource corresponding to the first electronic receipt for the transaction identified in the For example, the POS terminal 100 may then detect that an Internet connection has finally been established. (e.g., recovered), the transaction information of the first electronic receipt (or, in the alternative, the first In some embodiments, the first One electronic receipt may be stored by the user device 400 in a first location.

[0206] In some embodiments, the user device 400 (FIG. 14) displays the second electronic receipt. The application may store the second electronic receipt in the first location. The application can then store the first electronic receipt in a first location. The second electronic receipt can then be substituted for the first electronic receipt.

[0207] In some embodiments, the user device 400 may include an associated mini-app mobile app. The first electronic receipt may be displayed by launching the application. The receipt may be in a format determined by the transactor in connection with the first electronic receipt. A first electronic receipt can be generated using the transaction data. Related Mini-App Examples These include Apple® App Clip and Android® Instant App. In the example, the mini-app may be pre-installed or pre-installed on the user device 400. Not reloaded.

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

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

[0210] POS terminal 100, according to some example embodiments, is a device capable of processing transactions. A transaction consists of one or more purchases (one or more items and / or one or more services). ) and payments. This includes charitable donations and goodwill as well as services. The example embodiments will be described in relation to purchasing items, with the understanding that the same applies to For example, a transaction may involve one or more items, e.g., one or more commodities and / or A transaction may correspond to the exchange of one or more services for a payment amount. In some embodiments, the transaction may The POS terminal 100 may process the transaction and also process the The trading device may determine the outcome of the transaction and manage information related to the transaction.

[0211] POS terminal 100 may be one of various commercial types of POS terminals known to those skilled in the art. A point-of-sale (POS) terminal 110 may refer to a merchant or acquirer. It can be associated with any entity (not shown).

[0212] In some embodiments, as shown, the electronic receipt generator is a POS terminal 100 In such an embodiment, the POS terminal 100 and the electronic receipt are separate devices. The call generator 2000 may transmit and receive data via a communication computing device. For example, a communication computing device can communicate with a Universal Serial Bus (U SB) Wired communication computing devices via cable, or Wi-Fi or However, example embodiments may include wireless communication computing devices such as Bluetooth. is not limited to this.

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

[0214] Although FIG. 1 illustrates the POS terminal 100 as a single device, it is not limited to this. Instead, the POS terminal 100 may be configured with multiple devices. It may be in communication with an electronic receipt generator 2000 .

[0215] The electronic receipt generator 2000 is a medium that allows consumers to check electronic receipts on their smartphones. The electronic receipt generator 2000 uses NFC wireless connection technology to connect to the user device. 400 and / or exchanging data with the user device 400 According to one embodiment, the electronic receipt generator 2000 generates or and may communicate using the NFC standard. The electronic receipt generator 2000 may additionally or alternatively be configured with, but is not limited to, Bluetooth, wireless Standard technologies such as RFID, Magnetic Safety Transmission (MST), Beacon, ZigBee, etc. Techniques can be used.

[0216] The electronic receipt generator 2000 communicates with the server 300 via a communication network (not shown). In some embodiments, the communications network is the Internet. As a result, the electronic receipt generator 2000 can send data via the Internet. However, example embodiments are not limited to this. In some embodiments, the electronic receipt generator 2000 By connecting to the Internet via i-Fi, communication with the server 300 is possible. However, the example embodiments are not limited to this.

[0217] The server 300 may be, for example, a dedicated server or a cloud server. However, the example embodiments are not limited to this.

[0218] The server 300 is connected to the electronic receipt generator 2000 via a communication network (not shown). The server receives data from the electronic receipt generator 2000 and The server 300 may store the information in a database via a communication network (not shown). The wireless LAN may be connected to the user device 400 and may transmit data to the user device 400. Here, the communication network may be the Internet, but the embodiment is not limited to this. The user device 400 may be connected to a Wi-Fi or mobile network. The server 300 can be accessed by accessing the Internet via However, the example embodiments are not limited to this.

[0219] The user device 400 is a device for a user who is the subject of a transaction to check an electronic receipt. The user device 400 may be a smartphone, a smart watch, a smart device, or the like. devices, personal digital assistants (PDAs), wireless communication terminals, wearable technology (e.g., smartwatches), However, example embodiments are not limited thereto. It is not something that can be done.

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

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

[0222] The electronic receipt issuing computing system 20 of FIG. 5 is the same as the electronic receipt issuing computing system of FIG. However, according to the embodiment of FIG. 5, electronic receipts are The call generator is readable by the POS terminal rather than being implemented as a separate device. The present invention is implemented in the form of a computer program recorded on a recording medium. In this embodiment, the electronic receipt generator is implemented as one or more applications stored in the memory of the POS device. Therefore, according to the embodiment of FIG. 5, the POS terminal 100 contains the functionality of an electronic receipt generator.

[0223] FIG. 6 is a diagram illustrating a method for issuing an electronic receipt according to an example embodiment. Referring to FIG. In operation 101, a user completes a transaction. In some embodiments, completing a transaction means that the user All items selected by the user are scanned by the POS terminal 100 and discounts and purchases are Points will be applied as appropriate and payment for the selected items will be received via your payment method. It refers to the state of being taken away.

[0224] In some embodiments, once a transaction is completed, the POS terminal 100 captures transaction information. The transaction information may be the set of all information relating to the transaction for which the payment was received. For example, transaction information may include the date and time of the transaction, and the identification of one or more items corresponding to the transaction. (e.g., the name of one or more products and / or services), and the associated payment amount for each may include: one or more items, the amount of payment relating to all of one or more items; One or more items, including the quantity, total amount due, tax amount, and payment type (e.g., credit card information). information about the transaction method, such as receipt or debit card information), receipt authorization number, discount amount, transaction Name of the person, trader number (business number, etc.), trader's address, trader's phone number, trader's transaction number, etc. However, the present invention is not limited to these.

[0225] In some embodiments, the transaction information may be data, such as text (TXT ) file format and may contain some or all of the above transaction information. In some embodiments, the format of the transaction information is rich text format ( RTF file format, Extensible Markup Language (XML) file format , Java Script (registered trademark) Object Notation (JSON) file format, Separated Value (CSV) file format and / or Tab Separated Value (TSV) file format file formats, but example embodiments are not so limited.

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

[0227] Referring again to FIG. 1, in some embodiments, the POS terminal 100 may be configured to communicate via wired communication. The transaction information is transmitted to the electronic receipt generator 2000 by a method such as a credit card or a wireless communication method.

[0228] Referring again to Figure 5, some implementations of the POS terminal and electronic receipt generator are integrated. In an embodiment, the transaction information is transmitted internally.

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

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

[0231] In some embodiments, the electronic receipt generator 2000 generates a unique address corresponding to each transaction. If a unique address is generated for each transaction, the same address can be used multiple times. In some embodiments, this avoids conflicts that may arise when dealing with multiple transactions. The electronic receipt generator 2000 may generate a unique transaction identifier corresponding to a particular corresponding transaction. By including it in the address of a unique address, a unique address can be generated. For example, In some implementations, the address may be a URL, such as a "web address / identifier." In such an implementation, the format of the identifier may be the characters It can have various lengths based on the combination of characters, numbers, and special characters, but in practice The embodiment is not limited to this.

[0232] According to one embodiment, the electronic receipt generator 2000 generates a receipt based on transaction information associated with the transaction. For example, the identifier may be generated based on the electronic receipt. based on information about the call generator 2000 and / or based on the trading date and time According to a further example, the electronic receipt generator 2000 may use hashing techniques. Hashing techniques use a hash function to generate an identifier. In this example, the identifier is a The result may be obtained by using the information as input to a hash function.

[0233] According to an example embodiment, the identifier is used in generating an address (e.g., a URL), Then, by sending the address to the user device 400 via NFC, the following points are achieved: In the example, it can be guaranteed that a particular electronic receipt is issued to only one user. A particular electronic receipt is identified based on the use of a (unique) identifier or its hash. Ensures one-to-one uniqueness of receipts. In some instances, a particular electronic receipt may be unique to a user device. The data is deleted by the server 300 after being acquired by the device 400.

[0234] In the example, the resulting address (URL) is only available to one user device 400, e.g. If a user subsequently accesses the same If you try to access the URL, the address will no longer work and you will be The user's personal privacy and security can be maintained.

[0235] In operation 104, the electronic receipt generator 2000 generates the transaction information and the corresponding address. The electronic receipt generator sends the corresponding unique transaction identifier to the server 300. The information may be transmitted to the server 300.

[0236] In some embodiments, the electronic receipt generator 2000 may include the transaction information, address, The entire address corresponding to the transaction information, including the identifier, other information indicating the address, The corresponding unique transaction identifier, other information indicative of the identifier, etc. may be transmitted to the server. The example form is not limited to this.

[0237] In operation 105, the server 300 receives the transaction information from the electronic receipt generator 2000. The server 300 also stores the corresponding A unique transaction identifier may be stored.

[0238] In operations 104 and 105, the electronic receipt generator 2000 generates the transaction information and The server 300 then sends information about the address corresponding to the The user then stores the information of the address in the user device. A corresponding electronic receipt containing the corresponding transaction information can be viewed on the web page. According to an example embodiment, the electronic receipt is generated on the web using a standard web browser application. Since it is displayed on a webpage, users do not need to use an additional mobile application to view the electronic receipt. No application needs to be installed on the user device.

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

[0240] In some embodiments, the electronic receipt generator 2000 uses NFC technology to In some embodiments, the electronic receipt generator 2 may transmit the information to the device 400. 000 generates and emits messages in the specific format used for NFC. In some embodiments, the particular format may be such that the user device 400: to receive a corresponding message containing an instruction to immediately perform a given action. For example, the electronic receipt generator 2000 may refer to a format such as NDEF messages can be generated and sent. The NDEF message may contain information to be sent to the device 400. The user device 400 then sends an NDEF message Upon receiving the notification, a predetermined operation may be performed. The predetermined operation may be, for example, a web browser application. The application may be used to open a specific web page. It may be linked to an address.

[0241] Although FIG. 6 shows operation 106 occurring after operation 105, in the example embodiment This sequence of events is not limited to this. For example, in some embodiments, operations 105 and Operation 106 may be performed simultaneously. By way of further example, in some embodiments, operation 105 may be performed after operation 106.

[0242] In operation 107, the user device 400 taps the electronic receipt generator 200 to Thus, the address is received.

[0243] In some embodiments, the user device 400 communicates with an electronic receipt generator via NFC. 2000. The user device 400 supports NFC functionality. or devices, applications, and / or APIs that help support In some embodiments, the user device 400 may include an electronic receipt generator 20 By approaching within a few tens of centimeters of 00, the address will be included as a payload. NDEF messages can be received.

[0244] In operation 107, the electronic receipt generator 2000 transmits the address to the user device via NFC. When the receipt is sent to the user device 400, the user device 400 taps the electronic receipt generator 200. You can get information about your electronic receipt through a simple and quick action: In such an embodiment, personal information is entered into the POS terminal 100 in order to obtain an electronic receipt. You may not need to enter it.

[0245] In operations 108 and 109, the user device 400 sends the received address Based on the information, a designated web page is accessed and the electronic receipt is displayed.

[0246] In some embodiments, the user device 400 may receive and The user device 400 can access the web page linked to the address. receives an address via an NDEF message and, as a predefined action, links to the address. The server 300 can automatically access the accessed web page. The server 300 may already store transaction information corresponding to the dedicated application. The transaction information can be converted into an electronic receipt format through the service. The server 300 displays the generated electronic receipt on a web page linked to the address. As a result, the user can link to the address via the user device 400. The electronic receipt can be viewed by accessing the web page provided.

[0247] In one example, upon receiving the NFC signal, the user device 400 may Text messages or preloaded or preinstalled applications The web page or application corresponding to the web page URL can be accessed without the application running. In one example, the user device 400 may Applications do not need to be pre-installed or pre-loaded. The Vise 400 supports, for example, native browsers, Progressive Web Apps (PWAs), You can use apps, mini-apps, and more, which are explained further below. Reveal.

[0248] In the example, the user device 400 is "prepared" to receive and display an electronic receipt. For example, the user device 400 does not need to have the application pre-downloaded. It can operate without the need to be downloaded, pre-installed, or pre-loaded. For example, the user device 400 may activate a camera to scan a QR code, It works without the need to exchange email addresses or phone numbers. The NFC proximity detection between the user device 400 and the NFC tag controller 2070 It can be loaded as part of

[0249] Electronic receipts are a progressive web application, a responsive web application. Applications, Rich Internet Applications, Single Page Applications, or multi-page applications. However, example embodiments are not limited to these.

[0250] An electronic receipt displays transaction information based on a set of rules that follow a format defined by the provider. The provider may be a party to a transaction relating to an electronic receipt. For example, the provider may be a distributor or retailer, although example embodiments may A provider is distinct from a business partner, consumer, user, or customer.

[0251] 7 illustrates an exemplary electronic receipt according to an example embodiment. As shown in FIG. can be displayed on a web page via a web browser application. In an embodiment, the electronic receipt may include the date and time of the transaction, one or more items associated with the transaction, Identification information (e.g., the name of one or more products and / or services involved in the transaction) , the payment amount associated with each of one or more items, the quantity of one or more items, the total payment amount, Tax amount, payment type (e.g., credit card information and / or debit card information) Transaction method information, such as receipt confirmation number, transaction name, transaction number (e.g., It may include the company number, the address of the trader, the telephone number of the trader, the trade number, etc. Additionally, the format of the electronic receipt may be determined by the provider and is shown in the drawing. is not limited to:

[0252] In some embodiments, the business partner and / or user may assign a specific attribute to the user device. E-receipts can be sent via the user's device without the need to install any special applications. Conventionally, to view an electronic receipt via a user device, In many cases, specific dedicated applications must be installed on the user device. To view the electronic receipt, the user must complete the login process via their device. However, example embodiments may be used for specific specialized applications. without needing to install, register on a website, or complete a login process , viewing electronic receipts on web pages through traditional web browser applications. The present invention includes a computing device and method for

[0253] In some embodiments, the consumer simply taps the electronic receipt generator You can check the electronic receipt on your device via According to an embodiment, even if a URL is sent to a user device through an NDEF message, Therefore, the user device can use pre-defined commands in the NDEF message. A URL may be executed directly. In this way, the user can and view electronic receipts through your web browser application without further interaction. It can be displayed.

[0254] In some embodiments, without providing personal information such as email or phone number, An electronic receipt can be provided to the consumer via the user device. According to the company, it can prevent unnecessary leakage of personal information during the transaction process, and electronic receipts This can shorten the issuing procedure and time for issuing electronic receipts, and the electronic receipts can be sent to the user's device. It can be viewed more conveniently on the screen.

[0255] In some embodiments, electronic transactions may be made via a user device regardless of the corresponding transaction type. For example, traditionally, credit card companies provide electronic receipts. When issuing a receipt, the credit card number associated with the corresponding credit card company will be used. You can only receive an electronic receipt if the payment is made using a credit card. However, according to an example embodiment, the electronic receipt is generated in conjunction with a POS terminal associated with the transaction. It can be issued to a user device so that the user can use cash, debit cards, credit cards, Receive electronic receipts regardless of transaction type, including credit cards, digital wallets, etc. can.

[0256] In some embodiments, the user may be provided with an electronic receipt containing multiple transaction information. Traditionally, transactions are processed through related applications or short message services (SMS). If you issue an electronic receipt, the electronic receipt may only display limited transaction information. For example, in some previous situations, only the total payment amount was displayed, and detailed transaction information was not available. (e.g., identification of one or more items involved in a transaction, the quantity of one or more items, the However, in contrast, the According to an embodiment, a user may be provided with an electronic receipt that includes information about multiple transactions.

[0257] FIG. 8 illustrates a method for issuing an electronic receipt according to another example embodiment. Referring to FIG. In operation 201, the user has not yet initiated a transaction or the user has only a few transactions. At least some of it has already started.

[0258] In contrast to the method shown in FIG. 5, at the start of the method of FIG. 8 (e.g., operation 201), In operation 201, the user selects one or more items associated with the transaction, but the transaction is not yet complete. For example, action 201 indicates that the first item has been selected at the POS terminal. the time before the item is scanned, the time when at least one item is scanned into the POS terminal, or , the time when all items have been scanned into the POS terminal but payment has not yet been made. It can correspond to.

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

[0260] In some cases, the POS terminal and the electronic receipt generator are separate devices, as shown in Figure 1. In an embodiment, the POS terminal 100 may transmit intermediate transactions via wired or wireless communication methods. The information can be sent to the electronic receipt generator 2000. As shown in FIG. In some embodiments where the S-Terminal and the electronic receipt generator are integrated into the same device, the transaction information may be sent internally.

[0261] In some embodiments, intermediate transaction information is distinct from completed transaction information. For example, ,Intermediate transaction information is the set of all information about transactions for which payment has not yet been received. For example, the interim transaction information may include the transaction date and time, one or more the identification of the item, the payment amount associated with each of the one or more items, and the number of the one or more items This may include the amount, subtotal, trader name, trader number, trader address, trader phone number, etc. However, the interim transaction information includes the total payment amount, payment type, promotion amount associated with the transaction, discount The amount may not include the total amount paid, including the discount amount.

[0262] In some embodiments, the temporary transaction information is stored as data in a particular format. For example, the pre-transaction information may be stored in a format such as a text file. The data may be recorded in the above manner.

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

[0264] In some embodiments, the address is a website or web address on the Internet. It can refer to a URL for accessing a web page, but the embodiment is not limited to this. It will not be done.

[0265] In some embodiments, the electronic receipt generator 2000 generates a unique receipt corresponding to the interim transaction information. As a result, the same address can be generated depending on different transaction information. This can avoid address collisions that may occur when The child receipt generator 2000 includes a unique transaction identifier corresponding to the intermediate transaction information in the address. For example, the address can be "web In such cases, the identifier format is Bits can have various lengths based on the combination of letters, numbers, and special characters. However, example embodiments are not limited to this.

[0266] In some embodiments, the electronic receipt generator 2000 identifies the receipt based on the interim transaction information. For example, the identifier can be used to generate information about the electronic receipt generator 2000. In some implementations, the transaction information may be generated based on the transaction date and time the transaction was generated. In an embodiment, the electronic receipt generator 2000 uses hashing techniques to generate the identifier. In such an embodiment, the hashing technique uses a hash function to generate a single In such an embodiment, the technique may be a technique for obtaining one result value corresponding to the input value. The identifier is obtained through a hash function that uses the intermediate transaction information as input. It may also be a real value.

[0267] In operation 204, the electronic receipt generator 2000 generates the intermediate transaction information and the corresponding Information about the address is sent to the server 300.

[0268] In some embodiments, the electronic receipt generator 2000 generates the intermediate transaction information, the corresponding The entire address, including the identifier associated with it, other information associated with the address, and other information associated with the identifier The information can be transmitted to the server 300, but the embodiment is not limited to this. .

[0269] In operation 205, the server 300 receives the intermediate transaction data from the electronic receipt generator 200. The information and corresponding address information are stored.

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

[0271] In some embodiments, the electronic receipt generator 2000 may communicate with the user device via NFC. In some embodiments, the electronic receipt generator 2 may transmit the information to the electronic receipt generator 400. 000 generates and emits messages in the specific format used for NFC. The specific format is the format that the user device 400 that receives the message can use. It can refer to a format that allows a given action to be performed immediately. The receipt generator 2000 can generate and publish NDEF messages. The message may include information to be sent to the user device 400. The message may include the address as a payload. 00 can perform a predetermined action when it receives an NDEF message.

[0272] Although FIG. 8 shows operation 206 occurring after operation 205, the example embodiment For example, operations 205 and 206 may occur simultaneously or may occur separately. It is possible that 205 occurs after action 206.

[0273] In operation 207, the user device 400 taps the electronic receipt generator 200. Thus, the address is received.

[0274] In some embodiments, the user device 400 communicates with an electronic receipt generator via NFC. 2000. The user device 400 supports NFC functionality or or devices, applications, and / or applications that help support In some embodiments, the API may include an application programming interface (API). The user device 400 is located within a few tens of centimeters of the electronic receipt generator 2000. By using this method, it is possible to receive an NDEF message that contains an address as a payload. can be done.

[0275] In operations 208 and 209, the user device 400 selects a destination address based on the received address. Access the specified web page and view the provisional electronic receipt.

[0276] In some embodiments, the user device 400 may receive a In some embodiments, a web page on the Internet can be accessed. , the server 300 may already store intermediate transaction information corresponding to the address. The server 300 then uses the application to convert the intermediate transaction information into a provisional electronic receipt. The server 300 can then convert the address linked to the The user can then view the generated provisional electronic receipt on the web page. The user device 400 accesses the web page linked to the address. You can then view a temporary electronic receipt.

[0277] In some implementations, the provisional electronic receipt is generated through a progressive web application. , Responsive Web Applications, Rich Internet Applications, Thin Various applications, including group-page and / or multi-page applications The example embodiments may be generated using one or more applications such as, but not limited to, I can't.

[0278] In some embodiments, as shown in FIG. 9, the user device 400 receives a provisional electronic receipt. You can choose not to display the receipt and instead display a message such as "Receipt is being prepared." .

[0279] Returning again to Figure 8, at operation 210, the user completes the transaction. Once the transaction is completed, the POS terminal 100 may obtain the completed transaction information. In an embodiment, the completed transaction information is a plurality of pieces of information regarding a transaction for which payment was received. That's fine.

[0280] In some embodiments, the transaction date and time, one or more items associated with the transaction, the identity of the item, the payment amount associated with each of the one or more items, the quantity of the one or more items, In addition to the trader's name, trader number, trader address, trader phone number, etc., the completed trade information may contain additional information such as final payment amount, final tax amount, and / or payment type. It can be rare.

[0281] In some embodiments, the completed transaction information includes discount amounts and / or promotions. It can contain multiple pieces of information about the transaction for which payment was received after the limit amount was applied. In such an embodiment, the completed transaction information may include, in addition to the other information described above, membership information. Promotion information and amount, discount information and amount, final payment reflected discount amount It may also include the amount paid.

[0282] In some embodiments, completed transaction information, like preliminary transaction information, is stored in a specific form. For example, the completed transaction information may be stored on the The data may be recorded in a text file format.

[0283] In operation 211, the POS terminal 100 transmits the completed transaction information to the electronic receipt generator 20. Send to 00.

[0284] Referring again to FIG. 1, in some embodiments, the POS terminal 100 may be configured to communicate via wired communication. The transaction information can be transmitted to the electronic receipt generator 2000 via a digital signature or a wireless communication method. As shown in Figure 5, the POS terminal and the electronic receipt issuer are integrated with each other. In this embodiment, the transaction information is transmitted internally.

[0285] Referring again to FIG. 8, in operation 212, the electronic receipt generator 2000 generates a receipt for the completed transaction. The information and the corresponding address are sent to the server 300.

[0286] In some embodiments, the electronic receipt generator 2000 generates the intermediate transaction information and the corresponding In some such embodiments, the intermediary transaction information may be replaced or updated with completed transaction information. The document generator 2000 converts the address corresponding to the intermediate transaction information into the address corresponding to the completed transaction information. As a result, address collisions can be avoided. The electronic receipt generator 2000 collects the completed transaction information, the entire address already stored, The identifier contained in the address, other information indicating the address, other information indicating the identifier, etc. 300, but the example embodiment is not limited thereto.

[0287] In operation 213, the server 300 receives the address from the electronic receipt generator 200. The intermediate transaction information is updated as completed transaction information using the information obtained.

[0288] In operations 214 and 215, the user device 400 receives a directed The user accesses the specified web page and views the updated electronic receipt.

[0289] In some embodiments, the user device 400 may receive a The server 300 can access web pages on the Internet. The server 300 may already have updated completed transaction information corresponding to the transaction. , and convert the completed transaction information using the application into an electronic receipt format. Then, the server 300 generates and updates the web page linked to the address. As a result, the updated electronic receipt can be displayed to the user. By accessing the web page linked to the address via the device 400 You can view it here.

[0290] In some embodiments, the updated electronic receipt is provided to a Progressive Web Application. Applications, Responsive Web Applications, Rich Internet Applications , single-page applications, and / or multi-page applications, etc. , may be generated using one or more of a variety of applications, but example embodiments include Not limited.

[0291] In some embodiments, such as that shown in FIG. 6, the user may access the electronic wallet after completing the transaction. The user can view the electronic receipt by tapping the device on the receipt generator. In some embodiments, such as that shown in FIG. 8, the user may The device can then generate the receipt for the relevant web page by tapping on the electronic receipt generator. After the transaction is completed, the final electronic receipt will be automatically sent to you. The updated electronic receipt will be available for viewing on the user device.

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

[0293] For example, in operation 103 of FIG. 6 and operation 203 of FIG. 8, the electronic receipt generator 200 0 can generate an address corresponding to the received transaction information. It can refer to a URL that allows you to access a website or web page on the Internet. .

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

[0295] In some such embodiments, the deep link URL is generated in response to receiving the transaction information. and generated directly by the electronic receipt generator 2000. However, in the example embodiment, The electronic receipt generator 2000 may first generate a URL in response to receiving transaction information. From there, the deep link URL can be derived.

[0296] In some embodiments, operations 108 and 109 of FIG. 6 and operations 214 and 216 of FIG. 8 At 215, the user device 400 accesses the specified web page based on the received address. Visit the page to view your electronic receipt.

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

[0298] In some embodiments, the associated application may not yet be installed on the user device 400. If not installed, the user device 400 installs the associated application. After downloading, you will be redirected to the mobile application page or web application linked to the address. In some such embodiments, users can access the application page. The user device 400 receives the address through the NDEF message and performs a predetermined action. As an application, install the relevant application and click on the page linked to the address. can be accessed.

[0299] In the example embodiments, unless expressly stated to the contrary, the word "comprises" and variations such as "comprises" or "comprising" are intended to be used interchangeably with the terms "comprises" and "comprising" as used herein. It will be understood that the inclusion of an element does not imply the exclusion of other elements. .

[0300] In the example embodiment, a "module" is a hardware component such as a processor or circuitry. components, and / or software running on hardware, e.g., a processor It may also be a software component.

[0301] In the example embodiment, each of the components, functional blocks, or means may include one or more The electrical components performed by the components may include subcomponents of Electronic and mechanical functions are implemented as electronic circuits, integrated circuits, and application specific integrated circuits (ASICs). can be implemented by a variety of well-known devices or mechanical elements, such as They may be implemented individually, or two or more of them may be combined and implemented integrally.

[0302] Modules described as separate parts may or may not be physically separated. The part displayed as a module may or may not be a physical module. The network modules may be located in one location or distributed across multiple network modules. Some or all of the modules may be implemented in order to achieve the objectives of the solutions of the embodiments. may be selected according to the actual requirements for

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

[0304] The functionality is implemented in the form of software functional modules and sold or When used, the functions may be stored in a computer-readable storage medium (which may be non-transitory). Based on this understanding, the technical solutions of the example embodiments are provided in the form of software products. The software product may be stored in a storage medium and may be implemented as described in the example embodiments. A computing device adapted to perform all or part of the steps of the disclosed method. (which may be a personal computer, a server, or a network device) The storage medium includes a number of instructions for storing the data. USB flash drives, removable hard disks, read-only memory (RO M: Read-Only Memory), Random Access Memory (RAM), This includes any medium capable of storing program code, either magnetic or optical. .

[0305] In a described method or block diagram, boxes represent events, steps, actions, processes, It may represent a service, module, message, and / or state-based operation. Although some of the example embodiments are described as being performed in a particular order, the given sequence Changing the order of steps does not prevent or impair subsequent steps from occurring Insofar as some steps or processes may be performed in a different order. Some of the messages or steps shown may be omitted or combined in other embodiments. Some of the messages or steps described herein may be different in other embodiments. Further, if necessary, steps may be separated into sub-messages or sub-steps. Some or all of the steps may be repeated. The elements apply equally to computing devices or subcomponents, References to words such as "send" and "receive" are in terms of a particular device. It may be possible to replace it accordingly.

[0306] The described embodiments are considered to be illustrative and not restrictive. The example embodiments described as methods may be implemented on a computing device or devices alike. applies, and vice versa.

[0307] The various example embodiments are merely examples and are not intended to limit the scope of the examples and example embodiments in any way. Variations of the innovations described herein will be apparent to those skilled in the art and are not intended to be limiting. Such variations are within the intended scope. In particular, features from one or more of the example embodiments may be combined. Alternative embodiments may comprise subcombinations of features not expressly described in any selection. Furthermore, features from one or more of the example embodiments described may be combined. Select and combine alternative implementations consisting of combinations of features not explicitly described Examples of embodiments can be created. The features will be readily apparent to those skilled in the art. It is intended to cover all appropriate modifications.

Claims

1. A computer-implemented method for issuing an electronic receipt generated in response to transaction information, comprising: generating a unique identifier corresponding to the transaction information; generating a web identifier that includes the unique identifier; transmitting the transaction information and the web identifier to a server connected to the Internet and storing them; generating an NFC Data Exchange Format (NDEF) signal including the web identifier as a payload in a format that enables a terminal on a side receiving the electronic receipt to perform a preset operation after receiving the electronic receipt, generating the NDEF signal via NFC (Near-Field Communication) and transmitting the signal to the terminal on the side receiving the electronic receipt, and allowing the terminal on the side receiving the electronic receipt to display the electronic receipt via a web page corresponding to the web identifier after receiving the web identifier.

2. Prior to the completion of the transaction, the step of transmitting and storing the information on the server includes transmitting intermediate transaction information before the settlement is completed; If the recipient terminal accesses the web identifier before the transaction is completed, the server provides a provisional electronic receipt based on the intermediate transaction information; After the completion of the transaction, The intermediate transaction information stored in the server is updated to completed transaction information; The method for issuing an electronic receipt according to claim 1 , wherein when the recipient terminal accesses the web identifier after the transaction is completed, the server provides a final electronic receipt based on the completed transaction information.

3. 3. The method for issuing an electronic receipt according to claim 1, wherein the unique identifier is generated using hashing technology based on at least one of the transaction date and time, information about the terminal that provided the electronic receipt, and the transaction information.

4. The method for issuing an electronic receipt according to claim 3 , wherein a unique device identifier of the issuing device of the electronic receipt is used in generating the unique identifier.

5. 5. The method for issuing an electronic receipt according to claim 3, wherein the electronic receipt is displayed on the terminal of the recipient via a web browser or a mini-application on the terminal of the recipient.

6. an address generator that generates a unique identifier corresponding to the transaction information and generates a web identifier including the unique identifier; a first transmitting unit that transmits the transaction information and the web identifier to a server connected to the Internet and stores them; and a second transmitting unit that generates an NFC Data Exchange Format (NDEF) signal including the web identifier as a payload in a format that enables a terminal on a receiving side to perform a preset operation after receiving the electronic receipt, generates the NDEF signal via NFC (Near-Field Communication), transmits the signal to the terminal on the receiving side, and enables the terminal on the receiving side to display the electronic receipt via a web page or an application page that corresponds to the web identifier after receiving the web identifier.

7. An electronic receipt issuing system including: an issuing device for issuing an electronic receipt generated in accordance with transaction information; a server connectable to the Internet; and a terminal that is a recipient of the electronic receipt and that is connectable to the issuing device via short-range wireless communication, The issuing device generating a unique identifier corresponding to the transaction information and generating a web identifier including the unique identifier; transmitting the transaction information and the web identifier to the server for storage; An electronic receipt issuing system that generates an NFC Data Exchange Format (NDEF) signal including the web identifier as a payload in a format that enables the receiving terminal to perform a preset operation after receiving the signal, generates the NDEF signal via NFC (Near-Field Communication) and transmits the signal to the receiving terminal, and enables the receiving terminal to display the electronic receipt via a web page corresponding to the web identifier after receiving the web identifier.

Images