Electronic wallet payment method using near-field communication

Abstract

To provide a method of a computing device which facilitates electronic wallet payment using near field communication (NFC).SOLUTION: A method of a computing device receives transaction information corresponding to transaction, and identification information on an electronic wallet payment application of an electronic wallet payment server, from a point of sales terminal, transmits the transaction information and the identification information on the electronic wallet payment application to a server, addresses the server, establishes an URL for identifying a first web resource activating the electronic wallet payment application, generates an NDEF message including the URL as a payload through an NFC tag controller, and sends an NFC signal corresponding to the NDEF message through the NFC tag controller.SELECTED DRAWING: Figure 13

Description

Technical Field

[0005] , ,

[0001] Cross - reference to Related Applications None.

[0002] The exemplary embodiments relate to near - field communication (NFC) technology, for example, to facilitate payments of an electronic wallet using NFC technology.

Background Art

[0003] In conventional electronic wallet systems, a quick response (QR) code may be required to execute payments at a point of sales (POS). For example, the transactionee (transactee: e.g., consumer / shopper) or the transactor (e.g., seller, etc.) may display a QR code for scanning. Other transactionees or transactors may capture (image - scan) the image of the QR code to complete the transaction via an application. In some examples of such processes, the transactor presents a QR code or the corresponding electronic wallet payment application needs to be manually launched to image - scan a static QR code of a seller / retailer. In another example of such a process, the camera application / camera function may need to be manually launched in the electronic wallet payment application for the camera to capture the image of the QR code. Such processes are cumbersome and may require the use of the camera application and the on - board camera on the transactionee side.

[0004] Typically, conventional electronic wallet systems provide a confirmation or e - receipt that includes only the amount and the transactor. Such conventional electronic wallet systems may not include the identification and itemization of specific goods and services for a transaction at a POS terminal.

[0005] There is a need for computing devices and methods for transactions using existing QR-based electronic wallet payment applications without using cameras or image scanning.

[0006] A computing device and method is desired that works with existing payment applications and does not require an NFC device, POS terminal, or electronic receipt server to know the financial qualifications of the transaction recipient.

[0007] When a consumer completes a transaction related to the purchase of goods or the use of services, they receive a receipt. In traditional payment systems, point-of-sale (POS) terminals quickly issue paper receipts and may provide consumers with electronic receipts in the future. Disadvantages of paper receipts include the risk of personal information leakage, challenges in efficient receipt management, and the cost of producing printed receipts. Electronic receipts are generally preferred because they offer assurance of personal information protection, are easy to store and manage, are inexpensive to produce, and are environmentally friendly.

[0008] There is a need for computing devices and methods to provide electronic receipts conveniently and seamlessly. Some existing payment systems or servers may require user devices to register in order to obtain electronic receipts. This registration may include personal information such as email addresses, phone numbers, payment method numbers, and account information. [Overview of the project] [Means for solving the problem]

[0009] The examples described here can provide computing devices and methods for facilitating payments, such as e-wallet payments, using near-field communication (NFC). E-wallet payments are for transactions made by user devices accessing a payment application associated with a payment server. In some examples, the payment server handles the transactions and payments.

[0010] For example, a computing device could include an NFC device equipped with an NFC tag controller. In one example transaction, the NFC device sends an NFC Data Interchange Format (NDEF) message containing a Uniform Resource Locator (URL) as a payload to the user device. The NDEF message is received by the user device. When the URL is accessed by the user device, it automatically launches the payment application on the payment server on the user device to complete the transaction.

[0011] In one example, an NFC device communicates with a server.

[0012] In one example, the server and the NFC device do not communicate and do not send data to the payment server.

[0013] In one example, the server and NFC device are third parties to the payment server.

[0014] For example, the payment server is an e-wallet-based e-wallet payment server. For example, the payment server does not process credit cards and is non-credit card based. For example, the e-wallet payment server is debit-based. For example, an e-wallet account is loaded into the e-wallet payment server using a client device or another device.

[0015] For example, there is no need to transfer card information or financial credentials to an NFC device, POS terminal, or server.

[0016] In one example, the payment server is the type that is activated or addressed using a traditional method involving a QR code.

[0017] In some of the examples described herein, after a transaction has occurred, the recipient may be able to receive and view the corresponding electronic receipt using a web browser application or an e-wallet payment application. In some of the examples described here, after a transaction occurs, the recipient can receive and view the corresponding electronic receipt on their user device.

[0018] An exemplary embodiment is a method implemented on a computer, comprising: receiving transaction information corresponding to a transaction and identification information of an electronic wallet payment application on an electronic wallet payment server from a point of sales (POS) terminal; transmitting the transaction information and the identification information of the electronic wallet payment application to the server; establishing a Uniform Resource Locator (URL) that identifies a first web resource that addresses the server and launches the electronic wallet payment application, wherein the URL includes a unique transaction identifier, the unique transaction identifier includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier; generating an NFC Data Interchange Format (NDEF) message containing the URL as a payload via a Near Field Communication (NFC) tag controller; and emitting an NFC signal corresponding to the NDEF message via the NFC tag controller.

[0019] Another example embodiment of any of the methods implemented in the computer described above further includes receiving confirmation of successful completion of a transaction from a POS terminal and sending the confirmation to a server.

[0020] In another embodiment of one of the methods implemented on the computer described above, once the transaction is successfully completed, a URL identifies a second web resource for displaying an electronic receipt (e-receipt) of the transaction.

[0021] In another example embodiment of any of the methods implemented on the computer described above, the electronic receipt includes a unique transaction identifier.

[0022] In another example embodiment of any of the methods implemented on the computer described above, the server includes account information of an electronic wallet payment application associated with the POS terminal.

[0023] In another example embodiment of any of the methods implemented on the computer described above, the account information of the electronic wallet payment application associated with the POS terminal includes a quick response (QR) code of the electronic wallet payment application unique to the POS terminal.

[0024] In another example embodiment of any of the methods implemented on the computer described above, the URL includes identification information of the electronic wallet payment application.

[0025] In another example embodiment of any of the methods implemented on the computer described above, the URL is a deep link, and in the URL, the identification information of the electronic wallet payment application is nested from the unique transaction identifier.

[0026] In another example embodiment of any of the methods implemented on the computer described above, establishing includes receiving a URL and further includes sending the URL to a server.

[0027] In another example embodiment of any of the methods implemented on the computer described above, establishing includes receiving the URL.

[0028] In another example embodiment of any of the methods implemented on the computer described above, receiving transaction information is from a point of sales (POS) terminal, where the method implemented on the computer is executed by an NFC device, which is a device separate from the POS terminal.

[0029] In another example embodiment of any of the above computer-implemented methods, the computer-implemented method is implemented by an NFC device that is a third party and does not communicate with the electronic wallet payment server, as claimed in claim 1.

[0030] In another example embodiment of any of the above computer-implemented methods, the unique device identifier is the identifier of the POS terminal.

[0031] In another example embodiment of any of the above computer-implemented methods, the first web resource automatically inputs at least a part of the transaction information into the electronic wallet payment application.

[0032] In another example embodiment of any of the above computer-implemented methods, the first web resource automatically inputs the payment amount into the electronic wallet payment application.

[0033] In another example embodiment of any of the above computer-implemented methods, the first web resource is a progressive web application, a responsive web application, a rich internet application, a single page application, or a multi-page application.

[0034] In another example embodiment of any of the above computer-implemented methods, receiving the transaction information and transmitting the transaction information do not include financial authentication information.

[0035] In another example embodiment of any of the above computer-implemented methods, the NDEF message contains only a URL as the payload and no other payload.

[0036] In another example embodiment of any of the methods implemented on the computer described above, the e-wallet payment server and e-wallet payment application are debit-based.

[0037] Another example embodiment is a computing device comprising an NFC tag controller, a communication module, a processor, and at least one storage unit that, when executed by the processor, stores instructions causing the processor to perform one of the computer implementations described above.

[0038] In another embodiment of one of the computing devices described above, the transaction information is from a point-of-sale (POS) terminal, and the computing device is an NFC device separate from the POS terminal.

[0039] Another example embodiment is a method implemented on a computer, which is executed on a user device, and includes receiving an NFC Data Interchange Format (NDEF) message via a Near Field Communication (NFC) tag reader, the NDEF message having a URL as a payload, wherein the URL addresses a server, the URL includes a unique transaction identifier, the unique transaction identifier includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier; accessing the URL; receiving a first web resource of the URL that, in response to accessing the URL, launches an e-wallet payment application on the user device; and launching an e-wallet payment application to complete a transaction using an e-wallet payment server.

[0040] In another example embodiment of any of the methods implemented on the computer described above, the NDEF message is received from an NFC device, and the NFC device is a third-party electronic wallet payment server.

[0041] In another example embodiment of any of the methods implemented on the computer described above, the first web resource automatically inputs at least a portion of the transaction information into the e-wallet payment application.

[0042] In another example embodiment of any of the methods implemented on the computer described above, the first web resource automatically enters the payment amount into the e-wallet payment application.

[0043] In another example embodiment of any of the methods implemented on the computer described above, the computer-implemented method further includes receiving confirmation of the successful completion of a transaction, accessing a second web resource at a URL, and, in response to accessing the second web resource, displaying an electronic receipt (e-receipt) for the transaction.

[0044] In another example embodiment of any of the methods implemented on the computer described above, the electronic receipt includes a unique transaction identifier.

[0045] In another example embodiment of any of the methods implemented on the computer described above, displaying includes displaying an electronic receipt via a web page, application page, or e-wallet payment application.

[0046] Another example embodiment of any of the methods implemented on the computer described above further includes receiving confirmation of successful completion of a transaction, displaying an electronic receipt (e-receipt) of the transaction based on the transaction information in response to the confirmation of successful completion of the transaction, and displaying the electronic receipt.

[0047] Another example embodiment is a computing device comprising an NFC tag reader, a communication module, a processor, and at least one storage unit that, when executed by the processor, stores instructions causing the processor to perform one of the computer implementations described above.

[0048] Another example embodiment is a method implemented on a computer running on a server, which includes receiving transaction information corresponding to a transaction and identification information of an e-wallet payment application on an e-wallet payment server, receiving a Uniform Resource Locator (URL) addressing the server, wherein the URL includes a unique transaction identifier, the unique transaction identifier includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier, generating a first web resource associated with the URL to launch an e-wallet payment application, receiving access to the URL in response to an NFC Data Interchange Format (NDEF) message containing the URL as a payload, providing the first web resource through access to the URL, receiving confirmation of successful completion of the transaction, generating a second web resource associated with the URL for displaying an electronic receipt (e-receipt) of the transaction, and providing the second web resource through second access to the URL.

[0049] In another example embodiment of any of the methods implemented in the computer described above, the receipt of transaction information is from an NFC device or a point-of-sale terminal.

[0050] In another example embodiment of any of the methods implemented in the computer described above, the confirmation is received from an NFC device or a point of sales terminal.

[0051] In another example embodiment of any of the methods implemented on the computer described above, the server holds account information for an electronic wallet payment application associated with a POS terminal.

[0052] In another example embodiment of any of the methods implemented on the computer described above, the account information for the electronic wallet payment application associated with the POS terminal includes a quick response (QR) code for the electronic wallet payment application specific to the POS terminal.

[0053] In another example embodiment of any of the methods implemented on the computer described above, the URL includes identification information for the electronic wallet payment application.

[0054] In another example embodiment of any of the methods implemented on the computer described above, the URL is a deep link, and in the URL, the identification information of the e-wallet payment application is nested from a unique transaction identifier.

[0055] In another example embodiment of any of the methods implemented on the computer described above, receiving transaction information does not include financial authentication information.

[0056] In another example embodiment of any of the methods implemented on the computer described above, the server is a third-party electronic receipt server (e-server) of the electronic wallet payment application and does not communicate with the electronic wallet payment server.

[0057] In another example embodiment of any of the methods implemented on the computer described above, establishing includes generating a URL.

[0058] In another example embodiment of any of the methods implemented on the computer described above, establishing includes receiving a URL.

[0059] In another example embodiment of any of the methods implemented on the computer described above, the method implemented by the computer further includes registered account information for an electronic wallet payment application associated with a POS terminal.

[0060] In another example embodiment of any of the methods implemented on the computer described above, the account information includes a quick response (QR) code for an electronic wallet payment application specific to the POS terminal.

[0061] In another example embodiment of any of the methods implemented in the computer described above, transaction information is received from an NFC device, which is a separate device from the point of sale (POS) terminal.

[0062] In another example embodiment of any of the methods implemented in the computer described above, the unique device identifier is the identifier of the POS terminal.

[0063] In another example embodiment of any of the methods implemented on the computer described above, the first web resource and the second web resource are, respectively, a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application.

[0064] In another example embodiment of any of the methods implemented on the computer described above, the NDEF message contains only a URL as its payload and no other payload.

[0065] In another example embodiment of any of the methods implemented on the computer described above, the e-wallet payment server and e-wallet payment application are debit-based.

[0066] Another example embodiment is a computer device comprising a communication module, a processor, and a storage unit paired with at least one processor that, when executed by the processor, stores instructions causing the processor to perform the computer implementation described above.

[0067] In another example embodiment of any of the computer devices described above, the communication module includes an NFC tag controller.

[0068] Another example of an embodiment is a non-temporary computer-readable medium that, when executed by a processor, stores instructions causing the computer to perform one of the methods described above. [Brief explanation of the drawing]

[0069] The exemplary embodiments are described in detail below with reference to the following drawings.

[0070] Figure 1 is a schematic diagram showing a payment system according to an exemplary embodiment.

[0071] Figure 2 is a block diagram showing an example of the internal configuration of the NFC device shown in Figure 1, according to an exemplary embodiment.

[0072] Figure 3 is a block diagram showing an example of the internal configuration of the server shown in Figure 1, according to the illustrated embodiment.

[0073] Figure 4 is a block diagram showing an example of the internal configuration of the user device shown in Figure 1, according to the illustrated embodiment.

[0074] Figure 5 is a schematic diagram showing an example of a payment system according to the illustrated embodiment.

[0075] Figure 6 is a flowchart of an example method for facilitating electronic wallet payments according to an illustrated embodiment.

[0076] Figure 7 is a flowchart of another example method for facilitating electronic wallet payments according to the illustrated embodiment.

[0077] Figure 8 is a flowchart of another example method for facilitating electronic wallet payments according to the illustrated embodiment.

[0078] Figure 9 shows an example of how an electronic receipt is displayed on a user device according to the illustrated embodiment.

[0079] Figure 10 is a schematic diagram showing a payment system according to an exemplary embodiment.

[0080] Figure 11 is a schematic diagram illustrating another payment system according to an exemplary embodiment.

[0081] Figure 12 is a schematic diagram illustrating another payment system according to an illustrated embodiment.

[0082] Figure 13 is a flowchart of an example method performed by an NFC device for electronic wallet payments according to an illustrated embodiment.

[0083] Figure 14 is a flowchart of an example method performed by a user device for electronic wallet payment according to an illustrated embodiment.

[0084] Figure 15 is a flowchart of an example method performed by the server for electronic wallet payments according to the illustrated embodiment.

[0085] Similar reference numerals may be used in drawings to indicate similar elements or features. [Modes for carrying out the invention]

[0086] At least some of the exemplary embodiments include electronic wallet payment methods and the issuance of electronic receipts (e-receipts or receipts). This allows users to conveniently use NFC via their smartphones instead of scanning quick response (QR) codes.

[0087] Because the exemplary embodiments may have various modifications and thus various embodiments, specific embodiments are shown in the drawings and described in detail in the detailed description. However, this is not intended to limit to any particular practical mode, and all modifications, equivalents, and substitutes that do not deviate from the technical scope of the exemplary embodiments will be understood. In the detailed description, certain detailed descriptions of the relevant technology are omitted where it is considered that this may unnecessarily obscure the clarity of the exemplary embodiments.

[0088] An exemplary embodiment is a method implemented on a computer, comprising: receiving transaction information corresponding to a transaction and identification information of an electronic wallet payment application on an electronic wallet payment server from a point of sales (POS) terminal; transmitting the transaction information and the identification information of the electronic wallet payment application to the server; establishing a Uniform Resource Locator (URL) that identifies a first web resource that addresses the server and launches the electronic wallet payment application, wherein the URL includes a unique transaction identifier, the unique transaction identifier includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier; generating an NFC Data Interchange Format (NDEF) message containing the URL as a payload via a Near Field Communication (NFC) tag controller; and emitting an NFC signal corresponding to the NDEF message via the NFC tag controller.

[0089] Another example embodiment is a method implemented on a computer, which is executed on a user device, and includes: receiving an NFC Data Interchange Format (NDEF) message via a Near Field Communication (NFC) tag reader, the NFC message containing a URL as a payload, wherein the NFC message addresses a server, the NFC message contains a unique transaction identifier, the unique transaction identifier contains a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier; accessing the NFC message; receiving a first web resource of the NFC message that, in response to accessing the NFC message, launches an e-wallet payment application on the user device; and launching the e-wallet payment application to complete a transaction using an e-wallet payment server.

[0090] Another example embodiment is a method implemented on a computer running on a server, which includes: receiving transaction information corresponding to a transaction and identification information of an e-wallet payment application on an e-wallet payment server; receiving a Uniform Resource Locator (URL) addressing the server, wherein the URL includes a unique transaction identifier, the unique transaction identifier includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier; generating a first web resource associated with the URL to launch an e-wallet payment application; receiving access to the URL in response to an NFC Data Interchange Format (NDEF) message containing the URL as a payload; providing the first web resource through access to the URL; receiving confirmation of successful completion of the transaction; generating a second web resource associated with the URL for displaying an electronic receipt (e-receipt) of the transaction; and providing the second web resource through second access to the URL.

[0091] Another example embodiment is a computer device comprising a communication module, a processor, and a storage unit paired with at least one processor that, when executed by the processor, stores instructions causing the processor to perform the computer implementation described above.

[0092] Another example of an embodiment is a non-temporary computer-readable medium that, when executed by a processor, stores instructions causing the computer to perform one of the methods described above.

[0093] Figures 10, 11, and 12 illustrate an example embodiment of the payment system 1000 according to the illustrated embodiment. In the example of the payment system 1000 in Figure 10, the NFC device 2000, rather than the POS terminal 100, communicates with the server 300. In the example of the payment system 1000 in Figure 11, both the POS terminal 100 and the NFC device 2000 communicate with the server 300. In the example of the payment system 1000 in Figure 12, the POS terminal 100, rather than the NFC device 2000, communicates with the server 300. Similar reference numerals may be used in Figures 10, 11, and 12 to indicate similar elements and features.

[0094] Referring to Figure 10, in some examples, a payment system 1000 is used to facilitate payments using NFC. For example, the payment system 1000 can be used to facilitate electronic wallet payments. In some examples, the payment system 1000 is used to issue and manage electronic receipts for payments facilitated through the payment system 1000 (e.g., electronic wallet payments). Referring to Figure 10, the payment system 1000 is shown, which includes a POS terminal 100, an NFC device 2000, a server 300, a payment server 1010, and a user device 400. The NFC device 2000 is a computing device.

[0095] The POS terminal 100, server 300, NFC device 2000, payment server 1010, and user device 400 may communicate via a network (not shown), such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the POS terminal 100, server 300, NFC device 2000, payment server 1010, and user device 400 may connect to the Internet via Wi-Fi technology. The user device 400 may include an NFC tag reader 480 (Figure 4). In other words, the user device 400 may include NFC reading or background NFC tag reading functionality.

[0096] As shown in the figure, the POS terminal 100 may communicate with an NFC device 2000 that can perform operations to facilitate payment and generate an electronic receipt. Such communication may be performed via a wired connection, such as a USB connection. Such communication may also be performed via a wireless connection, such as Bluetooth®.

[0097] The NFC device 2000 may communicate with the payment server 1010. Such communication may take place over a network, such as a wireless network. In some examples, the payment server 1010 is a payment processor, platform, server, or network infrastructure that enables electronic money transfers between a transactional party and a recipient. In some examples, transfers can be made regardless of country, currency, digital payment method, or whether the payer or recipient is a business or a consumer. Each payment server 1010 differs in how it performs this process based on the payment type, speed, technology, or geographical location. In some examples, the payment server 1010 is an e-wallet payment server accessible by an e-wallet payment application. Examples of payment servers 1010 as e-wallet payment servers include PayPay®, RPay®, LinePay® in Japan, NaverPay® in South Korea, KakaoPay® in South Korea, Paytm®, UPI®, Alipay®, BHARATQR®, SGQR®, GrabPay® in Southeast Asia, Gopay® in Southeast Asia, Paymongo® in the Philippines, GPAY® in the Philippines, QR code-based payment servers, and other non-credit card payment servers.

[0098] In one example, server 300 stores, registers, or pre-registers account information for an electronic wallet payment application associated with a POS terminal 100 or a transaction recipient (or seller). In another example, server 300 can store, register, or pre-register multiple account information associated with POS terminals 100 of multiple electronic wallet payment servers 1010.

[0099] For example, the account information for the electronic wallet payment application associated with POS terminal 100 includes a QR code or QR code information specific to the electronic wallet payment application for POS terminal 100. In some examples, a transaction may have a single QR code unique to each electronic wallet payment server 1010. This is used for any number of POS terminals 100 owned and managed by the transaction.

[0100] In one example, the e-wallet payment server 1010 and the e-wallet payment application are debit-based.

[0101] The POS terminal 100 may be located in a place associated with a transaction, such as a seller. For example, the seller may be a shop, restaurant, gym, etc. The recipient may be a merchant bank that accepts deposits related to transactions made at the POS terminal 100 and facilitates the settlement of those deposits and deposits into accounts associated with the transaction. In some examples, the POS terminal 100 can also issue electronic receipts for fiat currency (cash) transactions.

[0102] A single payment server 1010 is shown in Figure 10, but in this example, a POS terminal 100 and / or an NFC device 2000 may communicate with multiple payment servers 1010. Other types of payment servers 1010 and payment applications may also be used.

[0103] After the payment server 1010 (payment application) is identified, the user device 400 sends a message to the payment server 1010 via the payment application. The message may be sent over the network. The message may include transaction information, including an amount value representing the amount of value to be transferred to complete the transaction.

[0104] Next, the payment server 1010 determines whether the transaction is approved or rejected based on predefined rules. For example, the rules may consider one or more factors, such as whether the user account on user device 400 has available funds, whether the trader or seller is of an permitted type, and whether the transaction violates spending limits.

[0105] Once the payment server 1010 decides whether to approve or reject the transaction, it sends a message to the POS terminal 100 and / or NFC device 2000 indicating the result of this decision. The result may then be displayed or, otherwise, output to the POS terminal 100.

[0106] Figure 2 is a block diagram showing an example of the internal configuration of the NFC device 2000 shown in Figures 1 and 10. Referring to Figure 2, the NFC device 2000 may include various components. These various components include, as shown, a network interface 2010, a communication module 2020, a storage unit 2030, program storage 2040, a controller 2050, an address generator 2060, and an NFC tag controller 2070. In one example, the NFC device 2000 can facilitate electronic wallet payments by transmitting addresses (e.g., URLs) via NFC. In another example, the NFC device 2000 is or includes an electronic receipt generator where addresses can access electronic receipts.

[0107] Examples of NFC devices include PIPOS® devices, existing PCI Commercial Off-Shelf (SPOC) devices, PCI PIN Transaction Service Point of Interaction (PCI PTS POI) devices, or non-PCI certified payment devices. For example, PCI certification is not used in some countries such as South Korea and Japan.

[0108] In some embodiments, two or more functionally connected components of the NFC device 2000 may be combined with each other to exist as a single component. In some embodiments, one component may be divided into multiple components according to one or more functions of one component.

[0109] The network interface 2010, when combined with a communication network, provides an interface for sending addresses such as URLs and transaction information corresponding to those URLs to the server 300.

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

[0111] The memory unit 2030 temporarily stores data processed by the controller 2050 and / or transaction information to be sent to the NFC device 2000.

[0112] The program storage 2040 stores control software for performing tasks such as sending data to the server 300, receiving data from the POS terminal 100, generating addresses corresponding to transaction information, and generating messages corresponding to addresses and programming messages for NFC tags. In some embodiments, the program storage may form part of the storage unit 2030. In some embodiments, some or all of the control software stored in the program storage may form at least part of one or more applications within the storage unit 2030.

[0113] The controller 2050 is a type of central processing unit (CPU) that can use the NFC device 2000 to control processes related to payment transactions (such as e-wallet payment transactions) and the generation of electronic receipts. In some examples, the controller 2050 can perform various services, such as executing control software stored in program storage 2040.

[0114] The address generator 2060 can generate unique addresses in response to received transaction information. In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, but the exemplary embodiments are not limited to such embodiments.

[0115] The address generator 2060 can generate unique addresses by including a unique transaction identifier corresponding to the transaction information. For example, the address may be a deep link, a deferred deep link, or a nested link. For example, in some implementations, the address may include the format "www.domain / mobileapp / unique transaction identifier". In such implementations, the format of the unique transaction identifier may include various lengths and may be based on a combination of letters, numbers, and special characters, but the exemplary embodiments are not limited thereto.

[0116] According to the embodiments, the NFC device 2000 can generate an identifier (a unique transaction identifier) ​​based on transaction-related information. For example, in some embodiments, the identifier may be generated based on information about the NFC device 2000, and may be generated based on the transaction date and time. According to another embodiment, the NFC device 2000 may generate an identifier using hashing techniques. Hashing techniques are referred to as methods for obtaining one result value corresponding to one input value using a hash function. In some such embodiments, the identifier may be a result value obtained via a hashing technique using transaction information as input values. However, the methods by which identifiers are generated by the exemplary embodiments are not limited thereto.

[0117] The NFC tag controller 2070 generates a message corresponding to an address and transmits the message as an NFC signal by controlling the NFC tag. According to the embodiment, the message may be in a specific format used for NFC. In some implementations, the specific format may refer to a format that allows a user device 400 receiving the corresponding message to immediately perform a predetermined action. For example, the NFC tag controller 2070 may generate and transmit an NDEF message containing information to be sent to the user device 400. In some implementations, the address is included as the payload of the NDEF message. In such implementations, the user device 400 may perform a predetermined operation upon receiving the NDEF message. The predetermined operation may be, for example, opening a web page linked to the address via a web browser application.

[0118] Figure 3 is a block diagram showing an example of the internal configuration of server 300 as shown in Figures 1 and 10. Referring to Figure 3, server 300 may include various components. These components may include, as illustrated, a communication module 310, a storage unit 320, program storage 330, a controller 340, a database 350, and an electronic receipt application programming interface (API) 360. In some examples, server 300 is or includes a receipt server or an electronic receipt server.

[0119] The communication module 310 enables the server 300 to communicate with other computers or computing devices and / or various communication networks. For example, the communication module 310 may enable the server 300 to transmit or receive communication signals. Communication signals may be transmitted or received according to one or more protocols or one or more standardization techniques. For example, the communication module 310 may enable the server 300 to communicate over a cellular data network according to one or more standardization techniques such as Global Computing Device (GSM) for mobile communications, Code Division Multiple Access (CDMA), Evolution Data Optimize (EVDO), or Long-Term Evolution (LTE). Furthermore, the communication module 310 may enable the server 300 to communicate using NFC, via Wi-Fi®, via Bluetooth®, or via a combination of one or more networks or protocols. In some embodiments, all or part of the communication module 310 can be integrated into the components of the server 300. For example, the communication module 310 may be integrated into a communication chipset.

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

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

[0122] The program storage 330 can store one or more programs consisting of instructions that direct one or more processes executed by the controller, as will be further described below. In some embodiments, the program storage 330 may form part of the storage unit 320. In some embodiments, one or more programs stored in the program storage may form part of one or more applications in the storage unit 2030.

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

[0124] In some embodiments, the controller 340 may include multiple types of data-processing devices, such as one or more processors. In the exemplary embodiments, “processor” refers, for example, to a data processing device embedded in hardware, which may be physically configured to perform functions represented by instructions from computing code and / or a computer program.

[0125] Database 350 can store address information and transaction information. Address information may include addresses (such as URLs), corresponding identifiers, and other information related to the addresses. Database 350 can store communications between address information and transaction information. In this way, server 300 can easily determine transaction information using information related to addresses.

[0126] In some examples, database 350 can store registration information between a transaction and one or more payment applications specific to that transaction (associated with one or more payment servers 1010 (Figure 10)). In one example, the payment application is an electronic wallet payment application. In another example, the registration information is typically a QR code presented at a POS or POS terminal 100 (Figures 1 and 10). Other registration information related to the payment application can be stored in database 350. In some examples, the registration information and / or QR code contains information that allows the user device 400 to launch the corresponding electronic wallet payment application to complete a transaction with payment server 1010.

[0127] In some cases, the Electronic Receipts API 360 provides an interface for converting transaction information into electronic receipt format through various applications. The Electronic Receipts API 360 also provides an interface for displaying the generated electronic receipts in the form of web pages linked to an address.

[0128] In some examples, the Electronic Receipt API 360 is configured to provide an interface for offering web resources that launch e-wallet payment applications. In some examples, the Electronic Receipt API 360 is used to facilitate transactions such as e-wallet payments facilitated via NFC, for example.

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

[0130] Figure 4 is a block diagram showing an example of the internal configuration of user device 400 (Figures 1 and 10). Referring to Figure 4, user device 400 includes various components. These various components include, as shown, a network interface 410, a communication module 420, a storage unit 430, an input / output module 440, program storage 450, a controller 460, and a display controller 470.

[0131] The network interface 410 can provide an interface for receiving electronic receipts in combination with a communication network.

[0132] The communication module 420 enables the user device 400 to communicate with other computers or computing devices and / or various communication networks. For example, the communication module 420 may enable the user device 400 to transmit or receive communication signals. Communication signals can be transmitted or received according to one or more protocols or one or more standardization techniques. For example, the communication module 420 may enable the user device 400 to communicate over a cellular data network according to one or more standardization techniques, such as Global Computing Device (GSM) for mobile communications, Code Division Multiple Access (CDMA), Evolution Data Optimize (EVDO), or Long-Term Evolution (LTE). Furthermore, the communication module 420 may enable the user device 400 to communicate using NFC, via Wi-Fi®, via Bluetooth®, or via a combination of one or more networks or protocols. In some embodiments, all or part of the communication module 420 can be integrated into the components of the user device 400. For example, the communication module 420 may be integrated into a communication chipset.

[0133] The communication module 420 can provide an interface for receiving data from the NFC device 2000 via NFC technology. The user device 400 may include an NFC tag reader 480. In other words, the user device 400 may include NFC reading or background NFC tag reading functionality. In some examples, the NFC tag reader 480 may be part of the communication module 420 or in a separate module.

[0134] The storage unit 430 can temporarily store data processed by the controller 460 and / or temporarily store addresses (such as URLs) received from the NFC device 2000.

[0135] The I / O (input / output) module 440 can be configured to operate as a contact-sensitive display controller or as another input / output controller. In some examples where the I / O module operates as a contact-sensitive display controller, the contact-sensitive display controller may provide output and input interfaces between the device and the user. In some implementations, the contact-sensitive display controller may transmit electrical signals to and receive electrical signals from the controller 460. In some implementations, the contact-sensitive display controller may display visual output to the user, which may include text, graphics, images, video, and combinations thereof. In some embodiments, the I / O module 440 is a specific display member, such as an organic light-emitting display (OLED) or liquid crystal display (LCD), which is capable of recognizing contact input. The I / O module 440 can display an electronic receipt for a web page accessed based on a received address via a web browser application. The I / O module 440 can display an electronic receipt for an application page or an e-wallet payment application via an application or an e-mobile payment application.

[0136] The program storage 450 can store control software for performing tasks such as receiving messages from the NFC device 2000, checking the format of received messages, and, if the received message is an NDEF message, accessing addresses contained in the NDEF message via a web browser application as a predetermined action.

[0137] The controller 460 may be a CPU and can control processes related to the execution of payment transactions and the display of electronic receipts via the user device 400. For example, the controller 460 can perform various services, such as executing control software stored in the program storage 450.

[0138] Referring to Figure 10, the payment system 1000 is used to facilitate payments, such as electronic wallet payments using NFC. Electronic wallet payments are associated with the payment server 1010. In some examples, the user device 400 accesses the payment server 1010 to form a transaction (e.g., a payment). In some examples, the user device 400 accesses the server 300 to obtain an electronic receipt for the transaction. In some other examples, the user device 400 has already received transaction information from the server 300 (either as the payload of a first web resource or extracted from a URL address), and at least the transaction information is used by the user device 400 to generate an electronic receipt for the transaction. In one example, the user device 400 can extract or parse a unique transaction identifier from the URL address itself, for example, as a "unique transaction identifier" in the format "www.domain / mobileapp / unique transaction identifier".

[0139] In one example transaction, the NFC device 2000 sends an NDEF message containing a URL as a payload to the user device 400. In one example, the URL is uniquely generated or established for each transaction. The NDEF message is received by the user device 400. The URL addresses the server 300. The URL contains a web resource that, when accessed by the user device 400, automatically launches the payment application on the user device 400 for the payment server 1010 to authorize and complete the transaction. In one example, after confirming that the transaction has been successfully completed, the e-wallet payment application can generate an electronic receipt of the transaction for access and viewing by the user device 400 based on the transaction information. In another example, after confirming that the transaction has been successfully completed, the same URL addressing the server 300 can provide an electronic receipt of the transaction for access and viewing by the user device 400.

[0140] Referring to Figure 11, in the example of payment system 1000, both the POS terminal 100 and the NFC device 2000 communicate with the server 300.

[0141] Referring to Figure 12, in the example of payment system 1000, the POS terminal 100, not the NFC device 2000, communicates with the server 300.

[0142] Referring here to Figure 13, a flowchart of an example method 1300 for facilitating electronic wallet payments according to an illustrated embodiment is shown. An example method 1300 may be performed by a computing device such as an NFC device 2000 (Figure 2). An example method 1300 may be performed in particular by the processor of the controller 2050 (Figure 2) of the NFC device 2000 (Figure 2). A particular example method 1300 may be applied to one or all of the example payment systems 1000 shown in Figures 10, 11, and 12, where applicable.

[0143] In operation 1302, the NFC device 2000 receives transaction information from the POS terminal 100 that corresponds to the transaction and the identification information of the electronic wallet payment application of the electronic wallet payment server 1010.

[0144] In operation 1304, the NFC device 2000 sends transaction information and identification information for the e-wallet payment application to the server 300.

[0145] In operation 1306, the NFC device 2000 establishes a Uniform Resource Locator (URL) that addresses the server 300 and identifies a first web resource that launches an e-wallet payment application. For example, the URL may include a unique transaction identifier that includes a hash function applied to the transaction information, and / or date and time information of the transaction, and / or a unique device identifier.

[0146] In operation 1308, the NFC device 2000 generates an NFC Data Interchange Format (NDEF) message containing a URL as a payload via the Near Field Communication (NFC) tag controller.

[0147] In operation 1310, the NFC device 2000 sends an NFC signal corresponding to the NDEF message via the NFC tag controller 2070 (Figure 2).

[0148] In one example of operation 1300, the NFC device 2000 receives confirmation from the POS terminal 100 that the transaction has been successfully completed, and sends that confirmation to the server.

[0149] In one example of operation 1300, upon successful completion of the transaction, server 300 generates a second web resource associated with the URL (the same URL as operation 1306, which launches the e-wallet payment application). Here, the second web resource is for displaying an electronic receipt of the transaction on user device 400. Thus, the same URL, which may be a deep link or a deferred deep link, is reused for multiple functions and purposes. For example, user device 400 can access the same URL as operation 1306 to access the second web resource.

[0150] In another example of Method 1300, once the transaction is successfully completed, the server 300 provides an electronic receipt via a first web resource. In one example, the server 300 generates an electronic receipt and sends it to the user device 400. In another example, the server 300 provides information for the user device 400 to generate an electronic receipt via the first web resource, such as, for example, transaction information.

[0151] In one example of Method 1300, the URL is in the format "www.domain / mobileapp / unique transaction identifier". In this example, the URL includes the mobile application, which is the identifier for the e-wallet payment application. In this example URL, the identifier for the e-wallet payment application is nested within the unique transaction identifier.

[0152] In one example of method 1300, operation 1306 includes generating a URL to establish. In one example, the NFC device 2000 also performs the task of sending the URL to the server 300.

[0153] In one example of method 1300, operation 1306 includes receiving a URL to establish. For example, the URL is received from server 300 or POS terminal 100.

[0154] In one example of method 1300, in operation 1302, the transaction information is received from the POS terminal 100.

[0155] In one example of Method 1300, the NFC device 2000 is a third party and does not communicate with the electronic wallet payment server 1010.

[0156] In one example of Method 1300, the unique device identifier is the identifier of the POS terminal 100.

[0157] In one example, the first web resource automatically enters transaction information into the e-wallet payment application on user device 400. In another example, the first web resource automatically enters (at least) the payment amount into the e-wallet payment application on user device 400.

[0158] For example, the first web resource could be a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application.

[0159] For example, the second web resource could be a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application.

[0160] In one example of Method 1300, operation 1302 does not include user device 400 or the financial authentication information of the recipient of the transaction information. In another example of Method 1300, operation 1304 does not include user device 400 or the financial authentication information of the recipient of the transaction information.

[0161] In one example of Method 1300, the NDEF message contains only a URL as its payload and no other payloads.

[0162] For example, a transaction may include one or more items and payments. Transaction information may include multiple receipt elements, which may include date and time information. Transaction information may be in text-based flat file formats such as Extensible Markup Language (XML), JavaScript® Object Notation (JSON), or delimited text files.

[0163] Transaction information may include an amount representing the value transferred to complete the transaction, and identification information for the payment application.

[0164] In some examples, a unique transaction identifier can be generated using a hash function applied to the transaction information. Alternatively, in some examples, a unique transaction identifier can be generated using a unique device identifier and / or date and time information associated with the transaction. In one example, the unique device identifier is that of NFC device 2000. In another example, the unique device identifier is that of POS terminal 100. In yet another example, the unique device identifier is a serial number, ID number, International Mobile Device ID (IMEI), or the Media Access Control (MAC) address of NFC device 2000 or POS terminal 100. In some examples, a unique transaction identifier can be generated using a combination (concatenation) of date information, time information, and a unique device identifier.

[0165] The unique URL may be based on a unique transaction identifier. The unique URL may identify the corresponding web resource for launching the payment application. The unique URL may identify the web resource corresponding to the electronic receipt for the transaction. The web resource may reside on server 300. The unique URL may be in the format "www.domain / mobileapp / unique transaction identifier".

[0166] If the transaction is rejected by the payment server 1010, the NFC device 2000 receives the rejection from the POS terminal 100. For example, an electronic receipt in the form of a canceled or incomplete transaction can be issued in a similar manner to the electronic receipt generated by the illustrated embodiment.

[0167] In some embodiments, the NFC signal may be an NDEF-formatted NFC tag with a URL as a payload. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag using, for example, an Apple® Universal Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag using, for example, an Apple® Application Clip Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag using, for example, an Android® App Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag with, for example, an Android® Instant App Link URL. Alternatively, in some embodiments, the NDEF-formatted NFC tag may be an NDEF-formatted tag with, for example, a Mini App (Mini Application) Link URL. In one example, a mini application can be used as an intermediate application to allow the user device 400 to select a specific e-wallet payment application. In another example, the mini application can be used as an intermediate application to allow the user device 400 to become a standalone electronic receipt manager or application that may have additional functionality that would not be considered an e-wallet payment application. In some embodiments, the payload may be a progressive web application-based URL. Some examples include Apple's App Clips, Google's Instant Apps, and Snapchat's Snap Minis.

[0168] When an NFC signal is emitted, the NFC signal can be received by the user device 400 (Figure 10). For example, a shopper can tap the user device 400 (Figure 10) on the NFC device 2000 and receive a URL via the NFC signal. The user device 400 (Figure 10) can receive an NFC signal with the URL as the payload via the NFC tag reader 480 (Figure 4). The user device 400 may include devices, applications, and / or application programming interfaces (APIs) that support or help support NFC functionality. In some embodiments, the user device 400 can receive an NDEF message containing an address as the payload by approaching the NFC device 2000 within tens of centimeters or, in some cases, less than 2 centimeters.

[0169] Following operation 1310, when an NFC signal is emitted, the NFC signal can be received by the user device 400 (Figure 10). For example, a shopper can tap the user device 400 (Figure 10) on the NFC device 2000 (Figure 10) and receive a URL via the NFC signal. The user device 400 (Figure 10) can receive the NFC signal with the URL as the payload via the NFC tag reader 480 (Figure 4).

[0170] In some embodiments, when a user device 400 (Figure 10) receives an NFC signal, the NFC tag can launch a web browser application. The web browser application can launch a web resource associated with a URL. As previously mentioned, the URL may be in the format "www.domain / mobileapp / unique transaction identifier". In one example, the web resource may launch an identified wallet payment application on the user device 400.

[0171] Web resources may be started or launched, for example, through a progressive web application, a responsive web application (for example, a JavaScript® web application), a rich internet application, a single-page application, or a multi-page application.

[0172] In some embodiments, the user device 400 (Figure 10) may include an application for storing and displaying receipts or an electronic mobile payment application. The electronic receipt may be displayed by the application in a format determined by the transactional party associated with the transaction.

[0173] In some embodiments, a web NFC framework may be used to provide NFC signals corresponding to NDEF messages.

[0174] In some embodiments, the user device 400 (Figure 10) may launch a web browser application that renders the output at a unique URL location containing the electronic receipt. The format of the electronic receipt may be a format determined by the transaction party in relation to the electronic receipt. The electronic receipt may be generated using transaction data and may be displayed by the user device 400 using an application. This application may be, for example, a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application.

[0175] Referring here to Figure 14, a flowchart of an example method 1400 for facilitating electronic wallet payments and issuing electronic receipts according to an illustrated embodiment is shown. The example method 1400 may be performed on a computing device such as a user device 400 (Figure 4). In particular, the example method 1400 can be performed by the processor of the controller 460 (Figure 4) of the user device 400 (Figure 4). The specific example method 1400 can be applied to one or all of the examples of payment systems 1000 shown in Figures 10, 11, and 12, where applicable.

[0176] In operation 1402, the user device 400 receives an NDEF message containing a URL as a payload via the NFC tag reader 480. For example, the URL addresses the server 300. For example, the URL contains a unique transaction identifier that includes a hash function applied to the transaction information of the transaction, and / or the date and time information of the transaction, and / or a unique device identifier.

[0177] In operation 1404, user device 400 performs access to the URL.

[0178] In operation 1406, user device 400 accesses the first web resource at the URL in response to the URL access. The first web resource launches the e-wallet payment application on user device 400. In some examples, the e-wallet payment application is associated with the e-wallet payment server 1010.

[0179] In one example, in operation 1406, the first web resource also automatically establishes an e-wallet payment application on user device 400 using at least some or all of the transaction information. In one example, the transaction information to be entered includes the payment amount. In one example, the e-wallet payment application is already installed on user device 400.

[0180] In operation 1408, user device 400 launches the e-wallet payment application to complete a transaction with e-wallet payment server 1010.

[0181] In one example of method 1400, operation 1402, the receipt of the NDEF message is from an NFC device 2000 which is a third party of the e-wallet payment server 1010.

[0182] In operation 1410, user device 400 receives confirmation that the transaction was successfully completed. In operation 1412, user device 400 accesses a second web resource at the server 300 via the URL. For example, user device 400 can access the same URL as in operation 1404 to access the second web resource.

[0183] In operation 1414, the user device 400 performs the display of an electronic receipt for a transaction in response to access to a second web resource. For example, the display may include showing the electronic receipt via a web page, application page, or e-mobile payment application corresponding to a URL.

[0184] In another example of operation 1414, the mobile payment application on user device 400 uses transaction information received from, for example, server 300 to generate an electronic receipt in a format determined by the transactional party (seller).

[0185] In one example of Method 1400, Operation 1414 performs the display of an electronic receipt by the user device 400 without using the exchange of email addresses, text messages, or financial authentication information with the server 300.

[0186] Referring now to Figure 15, a flowchart of Method 1500 for facilitating electronic wallet payments according to an illustrated embodiment is shown. Method 1500 in this example may be executed by a computing device such as a server 300 (Figure 3). In particular, Method 1500 in one example can be executed by the processor of the controller 340 (Figure 3) of the server 300 (Figure 3). Method 1500 in a particular example may be applied to one or all of the example payment systems 1000 shown in Figures 10, 11 and 12, if applicable.

[0187] In operation 1502, server 300 receives transaction information corresponding to the transaction and identifies the electronic wallet payment application of electronic wallet payment server 1010.

[0188] In operation 1504, server 300 performs the task of establishing a URL that addresses server 300. In some examples, the URL includes a hash function applied to the transaction information, and / or a unique transaction identifier that includes the date and time information of the transaction, and / or a unique device identifier.

[0189] In operation 1506, server 300 generates a first web resource associated with a URL that launches the e-wallet payment application on e-wallet payment server 1010.

[0190] In operation 1508, server 300 performs the receiving of access to a URL. For example, the access is in response to an NFC Data Interchange Format (NDEF) message that contains a URL as its payload.

[0191] In operation 1510, server 300 performs the provision of the first web resource through access to the URL.

[0192] In operation 1512, server 300 performs the task of receiving confirmation that the transaction was successfully completed.

[0193] In operation 1514, server 300 performs the generation of a second web resource associated with a URL. In this URL, the second web resource is for displaying an electronic receipt for a transaction. For example, the electronic receipt is generated using transaction information. In one example, the electronic receipt is generated using previously stored registration information or a previously stored POS terminal 100 or transaction recipient's QR code. In another example, financial authentication information is not known to server 300 and is therefore not included in the electronic receipt.

[0194] In operation 1516, server 300 provides a second web resource through a second access to the URL. For example, server 300 receives a second access to the same URL as in operation 1508. For instance, server 300 provides the second web resource to user device 400.

[0195] In one example of method 1500, in operation 1502, the receipt of transaction information is from an NFC device 2000 generator or a POS terminal 100.

[0196] In one example of method 1500, in operation 1502, the receipt of transaction information is from an NFC device 2000, which is another device of the POS terminal 100.

[0197] In one example of method 1500, operation 1502 does not include financial authentication information when receiving transaction information.

[0198] In one example of method 1500, operation 1512 is performed when the confirmation is received from an NFC device 2000 or a POS terminal 100.

[0199] In one example of Method 1500, the server 300 stores, registers, or pre-registers account information for an electronic wallet payment application associated with the POS terminal 100. For example, the account information for an electronic wallet payment application associated with the POS terminal 100 includes a quick response (QR) code for the electronic wallet payment application specific to the POS terminal 100.

[0200] In one example, prior to operation 1502, the server 300 performs the registration of account information for the electronic wallet payment application associated with the POS terminal 100.

[0201] In one example of Method 1500, Server 300 is a third-party electronic receipt server that is part of the e-wallet payment application and does not communicate with the e-wallet payment server 1010.

[0202] In one example of method 1500, operation 1504 includes server 300 that generates the URL for establishment.

[0203] In one example of method 1500, operation 1504 involves receiving a URL from an NFC device 2000 or a POS terminal 100 to establish a connection.

[0204] In one example of method 1500, in operation 1504, the unique device identifier is the identifier of the POS terminal 100.

[0205] In one example of Method 1500, the first and second web resources are a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application, respectively.

[0206] In one example of Method 1500, the NDEF message contains only a URL as its payload, and no other payloads.

[0207] Referring now to Figure 1, this shows a payment system 1000 according to an example of an embodiment. Referring to Figure 1, the payment system 1000 according to an example of an embodiment includes a point of sale (POS) terminal 100, an NFC device 2000, a server 300, and a user device 400.

[0208] The POS terminal 100, NFC device 2000, server 300, and user device 400 may communicate over a network, such as a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the POS terminal 100, NFC device, server 300, and user device 400 may connect to the Internet via Wi-Fi technology.

[0209] The POS terminal 100 is a device capable of processing transactions, according to several exemplary embodiments. A transaction may correspond to one or more purchases (one or more items and / or one or more services) and payments. Embodiments exemplifying the purchase of items can be described herein with the understanding that services, as well as charitable donations and goodwill, are equally applicable. For example, a transaction may correspond to the exchange of one or more items, such as one or more goods and / or one or more services, for a payment amount. In some embodiments, a transaction may correspond to the purchase of one or more items. In addition to processing transactions, the POS terminal 100 may determine the outcome of the transaction and manage information related to the transaction.

[0210] POS terminal 100 may refer to one of various commercial types of POS terminals known to those skilled in the art. Point of sale (POS) terminal 100 may be associated with entities (not shown) such as sellers or buyers.

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

[0212] In some embodiments, the POS terminal 100 and the NFC device 2000 may reside on the same device.

[0213] In some embodiments, Figure 1 shows the POS terminal 100 as a single device, but the embodiments described are not limited thereto, and the POS terminal 100 may consist of multiple devices. The multiple devices may communicate with the NFC device 2000.

[0214] The NFC device 2000 is a computing device that allows the recipient (consumer) to automatically launch an electronic wallet payment application. This is in contrast to conventional electronic wallet payment applications, which are typically initiated by the recipient on the user device 400, and then a QR code scan is performed after the conventional electronic wallet payment application is launched.

[0215] The NFC device 2000 may transmit and / or exchange data to and from the user device 400 using NFC wireless connectivity technology. According to the embodiment, the NFC device 2000 may generate or include NFC tags and communicate using NFC standardization techniques. However, the exemplary embodiments are not limited thereto, and the NFC device 2000 may further or alternatively use standardization techniques such as Bluetooth, radio frequency identification (RFID), magnetic secure transmission (MST), beacons, and Zigbee.

[0216] The NFC device 2000 may communicate with the server 300 via a communication network (not shown). In some implementations, the communication network may be the Internet, and the NFC device 2000 may communicate with the server 300 to send and receive data over the Internet. However, the embodiments described are not limited thereto. In some implementations, the NFC device 2000 may communicate with the server 300 by connecting to the Internet via Wi-Fi, but the embodiments are not limited thereto.

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

[0218] Server 300 may be connected to NFC device 2000 via a communication network (not shown). Server 300 may receive data from NFC device 2000 and store the data in a database. Server 300 may also be connected to user device 400 via a communication network (not shown) and may transmit data to user device 400. Here, the communication network may be the Internet, but the exemplary embodiments are not limited thereto. User device 400 may access server 300 by accessing the Internet via Wi-Fi or a mobile network, but the exemplary embodiments are not limited thereto.

[0219] The user device 400 is a device on which the user, who is the subject of the transaction, executes an electronic wallet transaction and displays an electronic receipt. The user device 400 may include, but is not limited to, a smartphone, a smartwatch, a smart device, a personal digital assistant (PDA), a wireless communication terminal, or wearable technology (e.g., a smartwatch, smart glasses).

[0220] User device 400 is a device that supports NFC technology for wireless communication with NFC device 2000. According to the embodiment, user device 400 may support NFC standardization technology. However, the exemplary embodiments are not limited thereto, and further or alternatively, user device 400 may support standardization technologies such as Bluetooth, radio frequency identification (RFID), magnetic secure transmission (MST), beacons, and Zigbee.

[0221] Referring now to Figure 5, this figure shows a payment system 1000 according to an example of an embodiment. Referring to Figure 5, the payment system 1000 is shown including a POS terminal 100, a server 300, and a user device 400. In the embodiment of the payment system 1000 shown in Figure 5, the POS terminal 100 includes the functionality of an NFC device 2000 and can operate bidirectionally with the NFC device 2000 in a manner similar to that described herein.

[0222] The payment system 1000 in Figure 5 is similar to the payment system 1000 in Figure 1. However, according to the embodiment of the example in Figure 5, the NFC device 2000 is not implemented as a separate device from the POS terminal 100, but rather in the form of a computer program recorded on a recording medium available to the POS terminal 100. In some examples, the NFC device 2000 is implemented in the form of one or more applications stored in the memory of the POS terminal 100. Therefore, according to the example in Figure 5, the POS terminal 100 includes the functionality of the NFC device 2000 and can operate bidirectionally in the same manner as the NFC device 2000 in the examples described herein.

[0223] Figure 6 shows a method 600 for facilitating electronic wallet payments according to an example of an embodiment. Method 600 is shown as a diagram of a message conversation. Figure 7 is a flowchart of another example of method 700 for facilitating electronic wallet payments according to an exemplary embodiment. Figure 8 is also a flowchart of yet another example of method 800 for facilitating electronic wallet payments according to an exemplary embodiment.

[0224] In the example of method 600 in Figure 6, the NFC device 2000, not the POS terminal 100, communicates with the server 300. An embodiment of method 600 in Figure 6 can be implemented by the payment system 1000 shown in Figure 10. In the example of method 700 in Figure 7, both the POS terminal 100 and the NFC device 2000 communicate with the server 300. An embodiment of method 700 in Figure 7 can be implemented by the payment system 1000 shown in Figure 11. In the example of method 800 in Figure 8, the POS terminal 100, not the NFC device 2000, communicates with the server 300. An embodiment of method 800 in Figure 8 can be implemented by the payment system 1000 shown in Figure 12. In Figures 6, 8, and 9, similar reference numerals can be used to indicate similar elements and features.

[0225] For example, at the start of method 600 in Figure 6, operation 602 indicates that the transaction is not yet complete. For example, in operation 602, the user has not yet provided payment for one or more items associated with the transaction. For example, operation 602 may correspond to the time after one or more items have been scanned or entered into the POS terminal 100. For example, all items have been scanned or entered into the POS terminal 100, but the payment has not yet been made. In some examples, discounts and purchase points are applied as appropriate.

[0226] In operation 604, the POS terminal 100 transmits transaction information corresponding to the transaction and identification information of the electronic wallet payment application of the electronic wallet payment server 1010, and the NFC device 2000 receives them.

[0227] In operation 606, the NFC device 2000 transmits transaction information and identification information for the e-wallet payment application to the server 300.

[0228] In operation 608, server 300 generates a first web resource that launches the e-wallet payment application.

[0229] In operation 610, the NFC device 2000 addresses the server 300 and performs the generation of a Uniform Resource Locator (URL) that identifies the first web resource. Since the URL can be in a standard format as described herein, the server 300 may also recognize or independently generate the same URL using transaction information and e-wallet payment application identification information.

[0230] As an example of operation 610 not described herein, the server 300 generates a URL and sends the URL to the NFC device 2000.

[0231] In one example, the URL includes a hash function applied to the transaction information, and / or a unique transaction identifier that includes the date and time information of the transaction, and / or a unique device identifier. Server 300 associates the URL with the first web resource.

[0232] In operation 612, the NFC device 2000 generates and sends an NFC Data Interchange Format (NDEF) message containing a URL as a payload via a Near Field Communication (NFC) tag controller.

[0233] In operation 614, user device 400 receives a URL (address) by tapping NFC device 2000. In operation 616, user device 400 accesses the URL of server 300. In operation 618, user device 400 receives a first web resource. In operation 620, the first web resource launches the electronic wallet payment application identified by user device 400.

[0234] In operation 622, user device 400 launches an e-wallet payment application and accesses the e-wallet payment server 1010. For example, transaction information is automatically populated into the e-wallet payment application on user device 400, as triggered by a first web resource. For example, the first address may be a deep link or a deferred deep link.

[0235] In one example, the first web resource contains information similar to or identical to a QR code stored on server 300. For instance, the QR code is for a POS terminal 100 or an electronic wallet payment application specific to the trader (seller). In a conventional system, the QR code is used to manually execute a transaction using the camera on a user device 400; scanning the QR code launches the payment application and accesses the payment server 1010.

[0236] In operation 624, the payment server 1010 approves the transaction. For example, information such as passwords and biometric authentication can be sent to the payment server 1010 via the user device 400.

[0237] In operation 626, the payment server 1010 sends a confirmation to the user device 400 that the transaction was successfully completed. In operation 628, the payment server 1010 sends the confirmation to the POS terminal 100. In operation 630, the POS terminal 100 sends the confirmation to the NFC device 2000. In operation 632, the NFC device 2000 sends the confirmation to the server 300.

[0238] In operation 634, server 300 creates a second web resource, and in operation 610, associates the second web resource, which has the same URL, with an address (URL).

[0239] In operation 636, an electronic receipt is sent from server 300 to user device 400 based on a second web resource. For example, user device 400 accesses the same URL again as in operation 616. Then, in operation 638, user device 400 can view the corresponding electronic receipt, including the corresponding transaction information, via the second web resource on user device 400. In one example, the electronic receipt is displayed on a web page corresponding to the address. In another example, the electronic receipt can be displayed on a web page using a standard web browser application.

[0240] In another example of operation 638, a mobile application or mobile payment application on user device 400 uses transaction information received from, for example, server 300 to generate an electronic receipt in a format determined by the transaction party (seller).

[0241] In another example of operation 638, the server 300 uses transaction information to generate an electronic receipt in a format determined by the trader (seller) and sends the electronic receipt to the user device 400 for display using a mobile application or an e-mobile payment application.

[0242] In some examples of operations 604 and 606, transaction information may be a set of information relating to a transaction for which payment was received. For example, transaction information may include the date and time of the transaction, identification information for one or more items corresponding to the transaction (e.g., the names of one or more goods and / or services), the payment amount for each of the one or more items, the payment amount for all of the one or more items, the quantity of the one or more items, the total payment amount, the tax amount, the payment type (e.g., identification of the e-wallet payment server 1010), the receipt authentication number, the discount amount, the name of the transactionor, the name of the transactionor (e.g., the business number), the address of the transactionor, the telephone number of the transactionor, the transaction number, etc. However, the exemplary embodiments are not limited thereto.

[0243] In one example, the transaction information includes a unique transaction identifier as described in the embodiments illustrated herein. In one example, the unique transaction identifier can be sent to the user device 400 as part of the transaction information (payload by the first web resource). In one example, the unique transaction identifier is sent to the user device 400, where the user device 400 can extract or parse the unique transaction identifier from the URL address itself, for example, in the form of "www.domain / mobileapp / uniquetransactionidentifier".

[0244] In some embodiments, the transaction information is data, which may be recorded in a text (TXT) file format, for example, and may include some or all of the above transaction information. In some embodiments, the format of the transaction information may include a rich text format (RTF) file format, an extended markup language (XML) file format, a JavaScript™ object notation (JSON) file format, a comma-separated values ​​(CSV) file format, and / or a tab-separated values ​​(TSV) file format. However, the embodiments described are not limited to these.

[0245] In some cases, transaction information does not include financial authentication information. Financial authentication information is often highly sensitive personal information, and in some cases, although server 300 may be a third party of payment server 1010, it is prohibited by financial regulations from being transmitted to server 300.

[0246] Typically, conventional electronic wallet systems provide confirmation or electronic receipt that includes only the amount and the transactionor. Such conventional electronic wallet systems do not include the identification and itemization of specific goods and services in transactions at the POS terminal 100.

[0247] Electronic receipts can include identification and itemization of specific goods and services in a transaction at POS terminal 100. In some examples, electronic receipts can be used for auditing purposes because they can include specific identifying information of the transaction. Electronic receipts can include a unique transaction identifier (the same unique transaction identifier found in the URL). Electronic receipts can include any information used for the unique transaction identifier, such as a hash function applied to the transaction information, and / or the transaction date and time information, and / or a unique device identifier.

[0248] In some cases, electronic receipts can contain specific, unique identifying information for a transaction, making them usable for refund and chargeback purposes.

[0249] In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, such as a deep link or deferred deep link for addressing a web resource on server 300.

[0250] According to an example of the embodiment, the following points can be ensured by using an identifier when generating an address (e.g., a URL) and then transmitting the address to the user device 400 via NFC. In some examples, a particular electronic receipt may be provided for issuance to only one user. Other users receive different URLs, each with its own (unique) identifier. The particular electronic receipt ensures one-to-one uniqueness of the electronic receipt based on the use of its (unique) identifier or its hash. In some examples, the particular electronic receipt is deleted by the server 300 after being retrieved by the user device 400.

[0251] In some cases, as a result, an address (URL) may only be visited by one user device 400, for example, by one user. If another user subsequently attempts to access the same address (URL), the address may be deleted by the server 300, so it may no longer function after being searched on user device 400, thus preserving the user's personal privacy and security.

[0252] In some examples, the server 300 may store transaction information corresponding to an address. The server 300 may generate an electronic receipt by converting the transaction information into an electronic receipt format via an application. The server 300 may display the generated electronic receipt on a webpage linked to the address. As a result, the user device 400 can view the electronic receipt by accessing the webpage linked to the address via the user device 400.

[0253] In one example, user device 400 displays an electronic receipt from a webpage corresponding to a webpage URL or application page.

[0254] For example, user device 400 can operate without activating its camera to scan a QR code, exchanging email addresses or phone numbers, or exchanging sensitive financial authentication information with server 300. Rather, it can load web resources via a URL as part of the NFC proximity operation between user device 400 and NFC tag controller 2070 to communicate addresses and launch an e-wallet payment application on user device 400.

[0255] Electronic receipts may be generated by various types of applications, including, but are not limited to, progressive web applications, responsive web applications, rich internet applications, single-page applications, or multi-page applications.

[0256] An electronic receipt is a type of electronic document in which transaction information is displayed according to a set of rules, in a format determined by the provider. The provider may be the transaction party related to the electronic receipt. For example, the provider may be a seller or retailer, but the embodiments described are not limited to these. The provider is different from the transaction party (e.g., consumer, user, customer, etc.).

[0257] Figure 9 shows an example of an electronic receipt 900 according to an exemplary embodiment. As shown in Figure 9, the electronic receipt 900 may be displayed on a web page via a web browser application, such as on a user device 400. In some embodiments, the electronic receipt 900 may include the date and time of the transaction, identification of one or more items related to the transaction (e.g., the names of one or more goods and / or services related to the transaction), the payment amount related to each of the one or more items, the quantity of the one or more items, the total payment amount, the tax amount, the payment type, the receipt authentication number, the name of the transactionor, the transaction number (e.g., a corporate number), the address of the transactionor, the telephone number of the transactionor, the transaction number, and so on. As previously stated, the format of the electronic receipt 900 may be determined by the provider and is not limited to that shown.

[0258] In some embodiments, the user device 400 can display the electronic receipt 900 to the transaction and / or user using the user device 400's web browser, application, or wallet payment application. Conventionally, displaying an electronic receipt often requires completing a login process via the user device 400. Exemplary embodiments include a computing device and method for displaying the electronic receipt 900 on a web page via a conventional web browser application, application, or e-wallet payment application on the user device 400.

[0259] In some embodiments, a consumer can receive and check an electronic receipt 900 on a user device 400. Therefore, since a URL may be sent to the user device 400 via an NDEF message according to the illustrated embodiment, the user device 400 can directly execute the URL using a pre-configured command in the NDEF message. In this way, the user device 400 may launch an e-wallet payment application via a web browser application without further action as a result of a simple tapping action, and display the electronic receipt 900 upon completion.

[0260] In some cases, exchanging URLs via NDEF messages uses far fewer resources than the web resources themselves.

[0261] In some embodiments, consumers may be provided with an electronic receipt 900 via a user device 400 without providing financial authentication information to the server 300. As a result, according to the exemplary embodiments, unnecessary leakage of personal information during transaction processing is prevented, the time to issue the electronic receipt 900 is reduced, and the electronic receipt 900 may be displayed more conveniently on the user device 400.

[0262] In some embodiments, the user may be provided with an electronic receipt 900 containing multiple transaction details. Conventionally, when an electronic receipt is issued after a transaction via a related application or short message service (SMS), only limited transaction information may be displayed on the electronic receipt. For example, in some conventional situations, only the total payment amount is displayed, and detailed transaction information (e.g., identification information of one or more items related to the transaction, the quantity of one or more items, the payment amount related to each item, and the tax amount, etc.) is not displayed. In contrast, according to embodiments described herein, the user device 400 may be provided with an electronic receipt 900 containing multiple transaction details.

[0263] In some other examples, a user device 400 can receive an electronic receipt 900 from a payment server 1010 for display on the user device 400. For example, server 300 generates an electronic receipt and sends it to the user device 400. In one example, the format of the electronic receipt 900 is determined by the trader (seller).

[0264] In some other examples, the user device 400 generates an electronic receipt 900 using transaction information received from at least the server 300 for display on the user device 400. In one example, the format of the electronic receipt 900 is determined by the transaction party (seller).

[0265] For example, the financial authentication information of the trader and user device 400 is not known to the server 300 and therefore is not included in the electronic receipt 900.

[0266] Referring again to Figure 1, in some embodiments, the POS terminal 100 may transmit transaction information to the NFC device 2000 via a wired communication method or a wireless communication method. In an embodiment where the POS terminal and the electronic receipt issuer are integrated, as shown in Figure 5, transaction information is transmitted internally.

[0267] In some embodiments of a deep link URL address, or a deferred deep link URL, the user device 400 may directly access a specified mobile application page or a specified web application page based on the received address, and then launch an e-wallet payment application or view an electronic receipt. For example, the user device 400 may run an application and access a mobile application page or web application page linked to the received address. The user device 400 may receive an address via an NDEF message and, as a predetermined action, run the associated mobile application and access a web page linked to the address.

[0268] In some embodiments, if an application associated with the user device 400 has not yet been installed, the user device 400 may install the associated application and then access the mobile application page or web application page linked to the address. In some such embodiments, the user device 400 may receive the address via an NDEF message, install the associated application as a predetermined action, and then access the page linked to the address.

[0269] Referring to the example method 700 in Figure 7, both the POS terminal 100 and the NFC device 2000 communicate with the server 300. An embodiment of method 700 in Figure 7 can be implemented by the payment system 1000 shown in Figure 11.

[0270] Operation 702 is identical or similar to operation 602.

[0271] In operation 704, the POS terminal 100 transmits transaction information corresponding to the transaction and identification information of the electronic wallet payment application of the electronic wallet payment server 1010, and the server 300 receives them.

[0272] In operation 706, server 300 generates a first web resource that launches the e-wallet payment application.

[0273] In operation 708, server 300 addresses server 300 and generates a URL that identifies the first web resource.

[0274] In operation 710, server 300 sends a URL to NFC device 2000.

[0275] Operations 712, 714, 716, 718, 720, 722, 724, 726, 728, 730, 732, 734, 736, and 738 are identical or similar to operations 612, 614, 616, 618, 620, 622, 624, 626, 628, 630, 632, 634, 636, and 638, respectively.

[0276] Referring to Example 800 in Figure 8, here it is the POS terminal 100, not the NFC device 2000, that communicates with the server 300. The embodiment of Method 800 in Figure 8 can be implemented by the payment system 1000 shown in Figure 12.

[0277] Operation 802 is identical or similar to operation 602.

[0278] In operation 804, the POS terminal 100 transmits transaction information corresponding to the transaction, and identification information of the electronic wallet payment application of the electronic wallet payment server 1010, and the server 300 receives it.

[0279] In operation 806, server 300 generates a first web resource that launches the e-wallet payment application.

[0280] In operation 808, server 300 performs the generation of a URL that addresses server 300 and identifies the first web resource.

[0281] In operation 810, the server 300 sends a URL to the POS terminal 100.

[0282] In operation 811, the POS terminal sends a URL to the NFC device 2000 and instructs the NFC device 2000 to emit an NFC signal.

[0283] In operation 830, the POS terminal 100 sends a confirmation to the NFC device 2000. Operation 830 differs from operations 630 and 632 in method 600 of Figure 6, where the confirmation is sent via the NFC device 2000. Operation 830 differs from operations 730 and 732 in method 700 of Figure 7, where the confirmation is sent via the NFC device 2000.

[0284] Operations 812, 814, 816, 818, 820, 822, 824, 826, 828, 834, 836, and 838 are identical or similar to operations 612, 614, 616, 618, 620, 622, 624, 626, 628, 634, 636, and 638, respectively.

[0285] In some alternatively illustrated embodiments, any of the above examples that refer to a QR code may instead use other visually captureable or scannable codes, such as 1D (linear) barcodes or 2D barcodes.

[0286] In exemplary embodiments, unless explicitly stated otherwise, variations such as “comprises” or “comprising” are understood to imply that they include the specified elements without excluding other elements.

[0287] In the exemplary embodiments, the “module” is a hardware component such as a processor or circuit, and / or a software component that runs on the hardware, such as a processor.

[0288] In the exemplary embodiments, each component, functional block, or means may include one or more subcomponents. The electrical, electronic, and mechanical functions performed by the components may be implemented by various known devices or mechanical elements, such as electronic circuits, integrated circuits, and application-specific integrated circuits (ASICs), which may be implemented separately from each other or in combination of two or more.

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

[0290] Furthermore, the functional modules of the exemplary embodiments may be integrated into a single processing module, or two or more modules may be integrated into a single module, with each module existing physically independently.

[0291] If a function is implemented in the form of a software function module and sold or used as a standalone product, the function may be stored on a computer-readable (non-temporary) storage medium. Based on this understanding, the technical solutions of the exemplary embodiments may be implemented in the form of a software product. The software product is stored on a storage medium and includes several instructions for instructing a computer device (such as a personal computer, server, or network device) to perform all or part of the methods described in the exemplary embodiments. The aforementioned storage mediums include, but are not limited to, Universal Serial Bus (USB) flash drives, removable hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0292] In the methods or block diagrams described, boxes may represent events, operations, steps, functions, processes, modules, messages, and / or state-based operations, etc. While some exemplary embodiments are described as occurring in a specific order, some steps or processes may be executed in a different order, provided that the reordering of a particular step does not prevent or impair the occurrence of subsequent steps. Furthermore, some of the messages or steps described may be omitted or combined in other embodiments, and some of the messages or steps described herein may be separated into many sub-messages or sub-steps in other embodiments. Furthermore, some or all of the procedures may be repeated as needed. The elements described as methods or steps also apply to computing devices or subcomponents. References to terms such as “send” or “receive” may be interchangeable depending on the perspective of a particular device.

[0293] The embodiments described are illustrative and not limiting. The exemplary embodiments shown as methods are similarly applicable to computing devices or devices.

[0294] The various exemplary embodiments are merely examples and are not intended to limit the scope of the examples and exemplary embodiments. Modifications of the innovations described herein will be obvious to those skilled in the art, and such modifications are within the intended scope. In particular, features can be selected from one or more exemplary embodiments to create alternative embodiments consisting of subcombinations of features not explicitly described. Furthermore, features can be selected and combined from one or more of the described examples to create alternative exemplary embodiments consisting of combinations of features not explicitly described. Features suitable for such combinations and subcombinations will be readily apparent to those skilled in the art. The subject matter described herein is intended to cover all appropriate variations of the art.

[0295] As described above, the POS terminal 100 and the NFC device 2000 may be provided as an integrated unit or as separate devices. In some stores, a smartphone, tablet computer, or laptop containing an NFC device may be provided as a check cashier, and the smartphone, tablet computer, or personal computer may perform the computer implementation method 5 described in this disclosure.

Claims

1. Receiving transaction information corresponding to a transaction and identification information of an electronic wallet payment application installed on a user device, associated with an electronic wallet payment server, from a point of sale (POS) terminal. The transaction information and the identification information of the electronic wallet payment application are transmitted to the server. Based on the received transaction information, a unique transaction identifier is generated, and an address is generated as a deep link that includes the unique transaction identifier and identifies a first web resource that launches the electronic wallet payment application on the user device in response to access from the user device, To generate an NFC Data Interchange Format (NDEF) message containing the address as a payload via a Near Field Communication (NFC) tag controller, A method implemented on a computer, comprising: sending an NFC signal corresponding to the NDEF message to the user device via the NFC tag controller, wherein the NFC signal is configured such that the user device, upon receiving the NFC signal, accesses the address, retrieves the first web resource, and launches the electronic wallet payment application.

2. The first web resource launches the electronic wallet payment application to perform a payment on the electronic wallet payment server, a method implemented on a computer according to claim 1.

3. A method implemented in a computer according to claim 1, further comprising receiving confirmation of the successful completion of the transaction and transmitting the confirmation to the server.

4. A computer-implemented method according to claim 1, wherein, upon successful completion of the transaction, the address identifies a second web resource for displaying an electronic receipt for the transaction.

5. The method of implementing the computer according to claim 4, wherein the electronic receipt includes the transaction information and / or the date and time information of the transaction and / or the unique transaction identifier, which includes a hash function applied to the unique device identifier.

6. The computer-implemented method according to claim 1, wherein the POS terminal is configured to transmit the transaction information corresponding to the received transaction and the identification information of the received electronic wallet payment application, and the server includes account information of the electronic wallet payment application associated with the POS terminal.

7. The computer-implemented method according to claim 6, wherein the account information of the electronic wallet payment application associated with the POS terminal includes a quick response (QR) code for the electronic wallet payment application specific to the POS terminal.

8. The method implemented in a computer according to claim 1, wherein the address includes the identification information of the electronic wallet payment application.

9. The computer implementation method according to claim 8, wherein the address is a deep link, and in the address, the identification information of the electronic wallet payment application is nested from the unique transaction identifier.

10. The method implemented in a computer according to claim 1, wherein the generation further includes transmitting the address to the server.

11. The method implemented in a computer according to claim 1, wherein the generation includes receiving the address.

12. The method implemented on a computer according to claim 1, wherein the transaction information is received from a point of sales (POS) terminal, and the method implemented on the computer is performed by an NFC device which is a device separate from the POS terminal.

13. The method implemented on the computer according to claim 1, wherein the method implemented on the computer is performed by a third-party NFC device that does not communicate with the electronic wallet payment server.

14. The method implemented on a computer according to claim 1, wherein the first web resource automatically inputs at least a portion of the transaction information into the electronic wallet payment application.

15. The method implemented on a computer according to claim 1, wherein the first web resource automatically inputs the payment amount into the electronic wallet payment application.

16. The method implemented on a computer according to claim 1, wherein the first web resource is a progressive web application, a responsive web application, a rich internet application, a single-page application, or a multi-page application.

17. The method implemented in a computer according to claim 1, wherein the NDEF message includes only the address as a payload and does not include any other payload.

18. NFC tag controller and Communication module and Processor and A computing device comprising: at least one storage unit that, when executed by the processor, stores instructions causing the processor to perform a method implemented in a computer according to any one of claims 1 to 17.

19. A method implemented in a computer according to claim 1, The user device receives NFC Data Interchange format (NDEF) messages via the user device's near-field communication (NFC) tag reader, Accessing the address on the user device, In the user device, in response to accessing the address, access is made to a first web resource of the address that launches the electronic wallet payment application of the user device. A method implemented on a computer, comprising launching the electronic wallet payment application for completing the transaction using the electronic wallet payment server.

20. The user device receives confirmation of the successful completion of the transaction, The user device accesses the second web resource at the address, A computer-implemented method according to claim 19, further comprising displaying an electronic receipt for the transaction on the user device in response to access to the second web resource.

21. The computer-implemented method according to claim 20, wherein the display on the user device includes displaying the electronic receipt via a web page, an application page, or the electronic wallet payment application.

22. The user device receives confirmation of the successful completion of the transaction, In the user device, in response to the confirmation of the successful completion of the transaction, an electronic receipt for the transaction is displayed based on the transaction information. A computer-implemented method according to claim 19, further comprising displaying the electronic receipt on the user device.

23. NFC tag reader and Communication module and Processor and A computing device comprising: at least one storage unit that, when executed by the processor, stores instructions causing the processor to perform a method implemented in a computer according to any one of claims 19 to 22.

24. The server generates the first web resource associated with the address that launches the electronic wallet payment application, To provide the first web resource through a first access to the aforementioned address, The server generates the second web resource associated with the address for displaying the electronic receipt for the transaction, A method implemented on a computer according to claim 4, comprising providing the second web resource through a second access to the address.

25. The method implemented in a computer according to claim 24, wherein the reception of the transaction information in the server is from an NFC device or a point of sales terminal.

26. The method implemented in a computer according to claim 3, wherein the receipt of the confirmation of the successful completion of the transaction is from an NFC device or a point of sales terminal.

27. The method implemented in a computer according to claim 1, wherein the server is a third party of the electronic wallet payment application and is an electronic receipt server that does not communicate with the electronic wallet payment server.

28. Communication module and Processor and A server comprising: at least one storage unit that, when executed by the processor, stores instructions causing the processor to perform the computer-implemented method described in claim 24 or 25.

29. A non-temporary computer-readable medium that, when executed by a processor, stores instructions causing the processor to perform a computer-implemented method according to any one of claims 1 to 17, 19 to 22, 24, and 25.

30. The computer implementation method according to claim 19, wherein, if there are multiple electronic wallet payment servers, the method includes identifying one electronic wallet payment server and sending a message containing the transaction information from the user device to the identified electronic wallet payment server.

31. The computer implementation method according to claim 1, wherein the method includes determining whether the transaction is approved or rejected based on predefined rules.

32. The computer implementation method according to claim 31, wherein one of the predefined rules includes checking whether the transaction is of a type that the transactional party is permitted to approve or reject in the electronic wallet payment server.

Images