Method of electronic wallet payment 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]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS none.

[0002] The illustrated embodiment relates to near field communication (NFC) technology, for example facilitating electronic wallet payments using NFC technology. [Background technology]

[0003] Traditional e-wallet systems may require a quick response (QR) code to effect a payment at the Point of Sales (POS). For example, a transactee (e.g., consumer / shopper) or transactor (e.g., merchant) may display a QR code for scanning. Another transactee or transactor may capture an image of the QR code (image scan) to complete the transaction via the application. Some examples of such a process may require the transactor to manually launch the applicable e-wallet payment application to present the QR code or image scan the merchant / retailer's static QR code. Another example of such a process may require the transactor to manually launch a camera application / camera function in the e-wallet payment application for the camera to capture an image of the QR code. Such a process may be cumbersome and may require the use of a camera application and an on-board camera at the transactee's 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 identification and itemization of the specific goods and services transacted at the POS terminal.

[0005] What is desired is a computing device and method for transacting with existing QR-based electronic wallet payment applications without the use of a camera or image scanning.

[0006] What is desired is a computing device and method that works with existing payment applications and does not require an NFC device, a POS terminal, or an electronic receipt server to learn a transactee's financial entitlements.

[0007] When a consumer completes a transaction related to the purchase of a good or use of a service, the consumer receives a receipt. In a traditional payment system, a point-of-sale (POS) terminal may issue a paper receipt immediately and provide an electronic receipt to the consumer at a future time. Disadvantages of paper receipts include the risk of personal information leakage, challenges in efficient receipt management, and the cost of generating printed receipts. Electronic receipts are generally preferred because they provide an assurance of personal information, are easy to retain and manage, are inexpensive to produce, and are environmentally friendly.

[0008] A computing device and method for convenient and seamless provision of electronic receipts is desired. Some existing payment systems or servers may require a user device to register in order to obtain an electronic receipt. This registration may include registering personal information such as an email address, phone number, payment instrument number, account information, etc. Summary of the Invention [Means for solving the problem]

[0009] Examples described herein may provide computing devices and methods for facilitating payments, such as electronic wallet payments, using near field communication (NFC). Electronic wallet payments are for transactions by a user device accessing a payment application associated with a payment server. In some examples, the payment server processes the transactions and payments.

[0010] For example, the computing device may include an NFC device with an NFC tag controller. In one example transaction, the NFC device sends an NFC Data Exchange Format (NDEF) message that includes a Uniform Resource Locator (URL) as a payload to a user device. The NDEF message is received by the user device. The URL, when accessed by the user device, automatically launches a payment application of a payment server on the user device to complete the transaction.

[0011] In one example, the 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 the NFC device are third parties to a payment server.

[0014] In one 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, the client device or another device is used to load an e-wallet account into the e-wallet payment server.

[0015] For example, the transfer of card information or financial entitlements does not require presentation to an NFC device, a POS terminal, or a server.

[0016] In one example, the payment server is of the type that is activated or addressed in the conventional manner using a QR code.

[0017] In some examples described herein, after a transaction has occurred, the recipient may be able to receive and view a corresponding electronic receipt using a web browser application or an electronic wallet payment application. In some examples described herein, after a transaction has occurred, a corresponding electronic receipt may be received and displayed on the transacted party's user device.

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

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

[0020] In another example embodiment of any of the computer-implemented methods described above, upon successful completion of the transaction, the URL identifies a second web resource for displaying an e-receipt for the transaction.

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

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

[0023] In another example embodiment of any of the computer-implemented methods 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 computer-implemented methods above, the URL includes an identification of an electronic wallet payment application.

[0025] In another example embodiment of any of the computer-implemented methods above, the URL is a deep link, in which 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 computer-implemented methods described above, the establishing includes receiving a URL, and further includes sending the URL to a server.

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

[0028] In another example embodiment of any of the computer-implemented methods above, receiving the transaction information is from a point-of-sale (POS) terminal, where the computer-implemented method is performed by an NFC device that is a separate device from the POS terminal.

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

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

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

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

[0033] In another example embodiment of any of the computer-implemented methods above, 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 computer-implemented methods described above, receiving the transaction information and sending the transaction information do not include financial authentication information.

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

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

[0037] Another example embodiment is a computing device comprising an NFC tag controller, a communications module, a processor, and at least one memory storing instructions that, when executed by the processor, cause the processor to perform any of the computer-implemented methods described above.

[0038] In another example embodiment of any of the above computing devices, 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 computer-implemented method executed by a user device, the method including: receiving, via a Near Field Communication (NFC) tag reader, an NFC Data Exchange Format (NDEF) message including a URL as a payload, the URL addressing a server, the URL including a unique transaction identifier, the unique transaction identifier including a hash function applied to the transaction information, and / or transaction date and time information, and / or a unique device identifier; accessing the URL; and in response to accessing the URL, receiving a first web resource at the URL that launches an electronic wallet payment application on the user device; and launching the electronic wallet payment application to complete the transaction using the electronic wallet payment server.

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

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

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

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

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

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

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

[0047] Another example embodiment is a computing device comprising an NFC tag reader, a communications module, a processor, and at least one memory storing instructions that, when executed by the processor, cause the processor to perform any of the computer-implemented methods described above.

[0048] Another example embodiment is a computer-implemented method executed by a server, the method comprising: receiving transaction information corresponding to a transaction and an identification of an electronic wallet payment application of an electronic wallet payment server; receiving a Uniform Resource Locator (URL) addressing the server, the URL including a unique transaction identifier, the unique transaction identifier including 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 that launches the electronic wallet payment application; receiving access to the URL in response to an NFC Data Interchange Format (NDEF) message including the URL as a payload; providing the first web resource through the access to the URL; receiving confirmation of successful completion of the transaction; generating a second web resource associated with the URL for displaying an e-receipt for the transaction; and providing the second web resource through the second access to the URL.

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

[0050] In another example embodiment of any of the computer-implemented methods above, receiving the confirmation is from an NFC device or a point-of-sale terminal.

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

[0052] In another example embodiment of any of the computer-implemented methods 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.

[0053] In another example embodiment of any of the computer-implemented methods above, the URL includes an identification of an electronic wallet payment application.

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

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

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

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

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

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

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

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

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

[0063] In another example embodiment of any of the computer-implemented methods described above, the first web resource and the second web resource are each 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 computer-implemented methods described above, the NDEF message contains only the URL as a payload and no other payload.

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

[0066] Another example embodiment is a computing device comprising a communications module, a processor, and a memory associated with at least one processor that stores instructions that, when executed by the processor, cause the processor to perform the computer-implemented method described above.

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

[0068] Another example embodiment is a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the device to perform any of the computer-implemented methods described above. [Brief description of the drawings]

[0069] Illustrative embodiments are described in detail below with reference to the following drawings:

[0070] FIG. 1 is a schematic diagram illustrating a payment system, according to an illustrated embodiment.

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

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

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

[0074] FIG. 5 is a schematic diagram illustrating an example of a payment system, according to an illustrated embodiment.

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

[0076] FIG. 7 is a flowchart of another example method for facilitating electronic wallet payments, according to illustrated embodiments.

[0077] FIG. 8 is a flowchart of another example method for facilitating electronic wallet payments, according to illustrated embodiments.

[0078] FIG. 9 is a diagram of an example display of an electronic receipt on a user device, according to an illustrated embodiment.

[0079] FIG. 10 is a schematic diagram illustrating a payment system, according to an illustrative embodiment.

[0080] FIG. 11 is a schematic diagram illustrating another payment system, according to an illustrative embodiment.

[0081] FIG. 12 is a schematic diagram illustrating another payment system, according to an illustrative embodiment.

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

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

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

[0085] Like reference numbers may be used in the drawings to denote like elements or features. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0086] At least some exemplary embodiments include electronic wallet payment methods and issuance of electronic receipts (e-receipts or receipts) so that users can conveniently use NFC via their smartphones rather than scanning Quick Response (QR) codes.

[0087] Since the illustrated embodiment may apply various modifications and have various embodiments, specific embodiments are shown in the drawings and described in detail in the detailed description. However, this is not intended to be limited to a specific practical mode, and all modifications, equivalents, and substitutions that do not depart from the technical scope of the illustrated embodiment will be understood. In the detailed description, specific details of related art are omitted if it is believed that they may unnecessarily obscure the clarity of the illustrated embodiment.

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

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

[0090] Another example embodiment is a computer-implemented method executed by a server, the method including: receiving transaction information corresponding to a transaction and an identification of an electronic wallet payment application of an electronic wallet payment server; receiving a Uniform Resource Locator (URL) addressing the server, where the URL includes a unique transaction identifier, the unique transaction identifier including 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 that launches the electronic wallet payment application; receiving access to the URL in response to an NFC Data Interchange Format (NDEF) message including the URL as a payload; providing the first web resource through the access to the URL; receiving confirmation of successful completion of the transaction; generating a second web resource associated with the URL for displaying an e-receipt for the transaction; and providing the second web resource through the second access to the URL.

[0091] Another example embodiment is a computing device comprising a communications module, a processor, and a memory associated with at least one processor that stores instructions that, when executed by the processor, cause the processor to perform the computer-implemented method described above.

[0092] Another example embodiment is a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the device to perform any of the computer-implemented methods described above.

[0093] Figures 10, 11 and 12 show an example embodiment of a payment system 1000, according to an illustrated embodiment. In the example payment system 1000 of Figure 10, an NFC device 2000, rather than a POS terminal 100, is in communication with a server 300. In the example payment system 1000 of Figure 11, both the POS terminal 100 and the NFC device 2000 are in communication with a server 300. In the example payment system 1000 of Figure 12, the POS terminal 100, rather than the NFC device 2000, is in communication with a server 300. Like reference numbers may be used in Figures 10, 11 and 12 to indicate like elements or 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 e-wallet payments. In some examples, the payment system 1000 is used to issue and manage electronic receipts for payments (e.g., e-wallet payments) facilitated via the payment system 1000. Referring to Figure 10, a payment system 1000 is shown that 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, the server 300, the NFC device 2000, the payment server 1010, and the user device 400 may be in communication over a network (not shown), such as, for example, a wireless network. In some implementations, the wireless network may be the Internet. In some implementations, the POS terminal 100, the server 300, the NFC device 2000, the payment server 1010, and the user device 400 may connect to the Internet via Wi-Fi technology. The user device 400 may include an NFC tag reader 480 (FIG. 4). In other words, the user device 400 may include NFC reading or background NFC tag reading functionality.

[0096] As shown, the POS terminal 100 may communicate with an NFC device 2000 operable to facilitate payment and generate an electronic receipt. Such communication may occur over a wired connection, such as, for example, a USB connection. Such communication may occur over a wireless connection, such as, for example, Bluetooth.

[0097] The NFC device 2000 may communicate with a payment server 1010. Such communication may occur 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 allows electronic funds transfers to occur between a transactor and a transactee. In some examples, funds transfers can occur regardless of country, currency, digital payment method, or whether the payer or payee is a business or consumer. Each payment server 1010 differs in how it performs this process based on payment type, speed, technology, or geographic location. In some examples, the payment server 1010 is an e-wallet payment server that can be accessed with an e-wallet payment application. Examples of the payment server 1010 as an e-wallet payment server include PayPay®, RPay®, LinePay® in Japan, NaverPay® in South Korea, KakaoPay® in South Korea, Paytm®, 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, the server 300 stores, registers, or pre-registers account information for electronic wallet payment applications associated with the POS terminal 100 or transactee (or merchant). In one example, multiple account information associated with the POS terminals 100 of multiple electronic wallet payment servers 1010 can be stored, registered, or pre-registered on the server 300.

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

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

[0101] The POS terminal 100 may be located at a location associated with a transactor, such as a merchant. By way of example, a merchant may be a store, a restaurant, a gym, etc. An acquirer may be a merchant bank that accepts deposits associated with transactions made at the POS terminal 100 and facilitates the settlement of those deposits and the deposit of the funds to an account associated with the transactor. In some examples, the POS terminal 100 may also issue electronic receipts for fiat (cash) transactions.

[0102] 10, in an example, the POS terminal 100 and / or 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 via the payment application to the payment server 1010. The message may be transmitted over a network. The message may include transaction information, including a monetary value representing the amount of value to be transferred to complete the transaction.

[0104] The payment server 1010 then determines whether the transaction is approved or denied based on predefined rules. For example, the rules may take into account one or more of whether the user account of the user device 400 has available funds, whether the transactor or merchant is of an authorized type, whether the transaction violates spending limits, etc.

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

[0106] FIG. 2 is a block diagram illustrating an example of the internal configuration of the NFC device 2000 shown in FIGS. 1 and 10. Referring to FIG. 2, the NFC device 2000 may include various components, including a network interface 2010, a communication module 2020, a memory unit 2030, a program storage 2040, a controller 2050, an address generator 2060, and an NFC tag controller 2070, as shown. In one example, the NFC device 2000 can facilitate an e-wallet payment by transmitting an address (e.g., a URL) via NFC. In one example, the NFC device 2000 is or includes an e-receipt generator, where the address can access an e-receipt.

[0107] Examples of NFC devices 2000 include PIPOS® devices, existing Payment Card Industry (PCI) PIN Transaction Service Point of Interaction (PTS POI) devices, which may include 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 NFC device 2000 may be combined together and present as a single component. In some embodiments, a component may be divided into multiple components according to one or more functions of the component.

[0109] The network interface 2010 is coupled to a communications network and provides an interface for transmitting an address, such as a URL, and transaction information corresponding to the URL 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. The 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 enable the NFC device 2000 to communicate over a cellular data network according to one or more standard technologies, such as, for example, Global Computing Device for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communication module 2020 may enable the NFC device 2000 to communicate using NFC, via Wi-Fi, using Bluetooth, or via a combination of one or more networks or protocols. In some embodiments, all or a portion of the communication module 2020 may be integrated into the components of the NFC device 2000. For example, the communication module 2020 may be integrated into a 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 temporarily stores transaction information 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 an address corresponding to the transaction information, generating a message corresponding to the address and programming the message into the NFC tag, etc. In some embodiments, the program storage may form part of the memory 2030. In some embodiments, some or all of the control software stored in the program storage may form at least a portion of one or more applications in the memory 2030.

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

[0114] The address generator 2060 can generate a unique address corresponding to the received transaction information. In some embodiments, the address refers to a URL for accessing a website or web page on the Internet, although the illustrated embodiments are not limited to such aspects.

[0115] The address generator 2060 can generate a unique address by including a unique transaction identifier that corresponds to the transaction information. For example, the address is a deep link, a deferred deep link, or a nested link. For example, in some implementations, the address may include the format "www.domain / mobile app / unique transaction identifier." In such implementations, the format of the unique transaction identifier may include a variety of lengths and may be based on a combination of letters, numbers, and special characters, although the illustrated embodiment is not limited thereto.

[0116] According to an embodiment, the NFC device 2000 can generate an identifier (unique transaction identifier) ​​based on transaction-related information. For example, in some embodiments, the identifier is generated based on information about the NFC device 2000, and may be generated based on the transaction date and transaction time. According to another embodiment, the NFC device 2000 may generate the identifier using a hashing technique. A hashing technique is referred to as a technique for using a hash function to obtain a result value corresponding to an input value. In some such embodiments, the identifier may be a result value obtained through a hashing technique using transaction information as an input value. However, the manner in which the identifier is generated according to the illustrated embodiment is not limited thereto.

[0117] The NFC tag controller 2070 generates a message corresponding to the address and emits the message as an NFC signal by controlling the NFC tag. According to an embodiment, the message may be in a specific format used for NFC. In some implementations, the specific format may refer to a format that allows the user device 400 receiving the corresponding message to immediately perform a predetermined action. For example, the NFC tag controller 2070 may generate and emit an NDEF message that includes information to be sent to the user device 400. In some implementations, the address is included as a 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 illustrating an example of the internal configuration of the server 300 shown in Figures 1 and 10. With reference to Figure 3, the server 300 may include various components. These components may include, for example, a communications module 310, a memory unit 320, a program storage 330, a controller 340, a database 350, and an e-receipt application programming interface (API) 360, as shown. In some examples, the server 300 is or includes a receipt server or an e-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. The communication signals may be transmitted or received according to one or more protocols or one or more standardized technologies. For example, the communication module 310 may enable the server 300 to communicate over a cellular data network according to one or more standardized technologies, such as Global Computing Devices for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communication module 310 may enable the server 300 to communicate using NFC, via Wi-Fi, using Bluetooth, or via a combination of one or more networks or protocols. In some embodiments, all or a portion of the communication module 310 may be integrated into a component of the server 300. For example, the communication module 310 may be integrated into a communication chipset.

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

[0121] The memory unit 320 may perform the function of temporarily or permanently storing data processed by the controller 340. In some implementations, the memory unit 320 may include a magnetic storage medium and / or a flash storage medium, although the illustrated embodiment is not limited thereto.

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

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

[0124] In some embodiments, controller 340 may include multiple types of devices capable of processing data, such as one or more processors. In the illustrated embodiment, a "processor" may refer to a data processing device, for example, embedded in hardware, that may physically configure circuitry to perform functions represented by computing code and / or computer program instructions.

[0125] The database 350 can store address information and transaction information. The address information may include an address (such as a URL), a corresponding identifier, and other information associated with the address. The database 350 can store a correspondence between the address information and the transaction information. In this manner, the server 300 can easily determine the transaction information using the information associated with the address.

[0126] In some examples, the database 350 can store registration information between a transactor and one or more payment applications specific to the transactor that are associated with one or more payment servers 1010 (FIG. 10). In one example, the payment application is an e-wallet payment application. In one example, the registration information is a QR code that is typically presented at a POS or POS terminal 100 (FIGS. 1 and 10). Other registration information related to the payment application can be stored in the database 350. In some examples, the registration information and / or the QR code includes information for launching the corresponding e-wallet payment application by the user device 400 to complete the transaction with the payment server 1010.

[0127] In some examples, the e-receipt API 360 provides an interface for converting transaction information into the form of an e-receipt via various applications. The e-receipt API 360 also provides an interface for displaying the generated e-receipt in the form of a web page linked to an address.

[0128] In some examples, the e-receipt API 360 is configured to provide an interface for providing a web resource that launches an e-wallet payment application. In some examples, the e-receipt API 360 is used to facilitate transactions such as e-wallet payments facilitated via NFC.

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

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

[0131] The network interface 410 can provide an interface for coupling with a communications network to receive electronic receipts.

[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. The communication signals may be transmitted or received according to one or more protocols or one or more standardized technologies. For example, the communication module 420 may enable the user device 400 to communicate over a cellular data network according to one or more standardized technologies, such as Global Computing Device for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Evolution Data Optimized (EVDO), Long Term Evolution (LTE), etc. Additionally or alternatively, the communication module 420 may enable the user device 400 to communicate using NFC, via Wi-Fi, using Bluetooth, or via a combination of one or more networks or protocols. In some embodiments, all or a portion of the communication module 420 may be integrated into a component of the user device 400. For example, the communication module 420 may be integrated into a communication chipset.

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

[0134] The memory unit 430 may 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 touch-sensitive display controller or as another input / output controller. In some examples where the I / O module is operating as a touch-sensitive display controller, the touch-sensitive display controller may provide an output interface and an input interface between the device and a user. In some implementations, the touch-sensitive display controller may send electrical signals to and receive electrical signals from the controller 460. In some implementations, the touch-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, for example, an organic light emitting display (OLED) or a liquid crystal display (LCD), capable of recognizing touch 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 electronic wallet payment application via an application or an electronic mobile payment application.

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

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

[0138] Referring to FIG. 10, a payment system 1000 is used to facilitate payments, such as electronic wallet payments using NFC. The electronic wallet payments are associated with a payment server 1010. In some examples, a 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 (as the payload of the first web resource or as extracted from the 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 the unique transaction identifier from the URL address itself, such as, for example, a "unique transaction identifier" in the format "www.domain / mobile app / unique transaction identifier".

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

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

[0141] Referring to FIG. 12, in an example payment system 1000 , a POS terminal 100 rather than an NFC device 2000 is in communication with a server 300 .

[0142]

[0046] Referring now to Figure 13, there is shown a flowchart of an example method 1300 for facilitating electronic wallet payments according to an illustrated embodiment. The example method 1300 may be performed by a computing device such as the NFC device 2000 (Figure 2). The example method 1300 may be performed in particular by a processor of the controller 2050 (Figure 2) of the NFC device 2000 (Figure 2). The 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] At operation 1302 , the NFC device 2000 receives from the POS terminal 100 transaction information corresponding to the transaction and an identification of the electronic wallet payment application of the electronic wallet payment server 1010 .

[0144] In operation 1304, the NFC device 2000 performs transmission of the transaction information and the identification information of the electronic wallet payment application to the server 300.

[0145] In operation 1306, the NFC device 2000 establishes a Uniform Resource Locator (URL) that identifies a first web resource that addresses the server 300 and launches the electronic wallet payment application. In one example, the URL includes 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 performs generation of an NFC Data Exchange Format (NDEF) message, via a Near Field Communication (NFC) tag controller, that includes the URL as a payload.

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

[0148] In one example of operations 1300, the NFC device 2000 performs receiving confirmation of successful completion of the transaction from the POS terminal 100 and transmitting that confirmation to the server.

[0149] In one example of operation 1300, upon successful completion of the transaction, the server 300 generates a second web resource associated with a URL (same as the URL of operation 1306 for launching an electronic wallet payment application), where the second web resource is for displaying an electronic receipt of the transaction on the 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, the user device 400 may access the same URL as operation 1306 to access the second web resource.

[0150] In another example of method 1300, upon successful completion of the transaction, the server 300 provides an electronic receipt via the first web resource. In one example, the server 300 generates and transmits the electronic receipt to the user device 400. In another example, the server 300 provides information, such as at least the transaction information, for generating the electronic receipt via the first web resource for the user device 400.

[0151] In one example of method 1300, the URL is in the format "www.domain / mobile app / unique transaction identifier." In one example, the URL includes the mobile app, which is an identity of an electronic wallet payment application. In the example URL, the identity of the electronic wallet payment application is nested from the unique transaction identifier.

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

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

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

[0155] In one example of the 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 the 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 an electronic wallet payment application of the user device 400. In one example, the first web resource automatically enters (at least) the payment amount into an electronic wallet payment application of the user device 400.

[0158] In one example, 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.

[0159] In one example, the second web resource is 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, at operation 1302, the receipt of the transaction information does not include financial authentication information of the user device 400 or the recipient of the transaction. In one example of method 1300, at operation 1304, the transmission of the transaction information does not include financial authentication information of the user device 400 or the recipient of the transaction.

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

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

[0163] The transaction information may include a monetary amount representing the amount of value to be transferred to complete the transaction and an identification of the payment application.

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

[0165] The unique URL may be based on the unique transaction identifier. The unique URL may identify a corresponding web resource for launching a payment application. The unique URL may identify a web resource corresponding to an electronic receipt for the transaction. The web resource may reside on server 300. The unique URL may be of the format "www.domain / mobile app / 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. In one example, an electronic receipt in the form of a canceled or incomplete transaction can be issued in a similar manner to an electronic receipt generated according to 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 with, for example, an Apple® Universal Link URL. Alternatively, in some embodiments, the NDEF formatted NFC tag may be an NDEF formatted tag with, for example, an Apple® Application Clip Link URL. Alternatively, in some embodiments, the NDEF formatted NFC tag may be an NDEF formatted tag with, 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, the mini application may be used as an intermediate application to allow the user device 400 to select a particular e-wallet payment application. In another example, the mini application may be used as an intermediate application to allow the user device 400 to become a standalone e-receipt manager or application that may have additional functionality that may 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] Once the NFC signal is emitted, it can be received by the user device 400 (FIG. 10). For example, a shopper can tap the user device 400 (FIG. 10) on the NFC device 2000 and receive a URL via the NFC signal. The user device 400 (FIG. 10) can receive the NFC signal with the URL as the payload via the NFC tag reader 480 (FIG. 4). The user device 400 may include devices, applications, and / or application programming interfaces (APIs) that support or aid in supporting NFC functionality. In some embodiments, the user device 400 can receive an NDEF message with an address as the payload by approaching the NFC device 2000 within a few tens of centimeters, or in some examples, less than two centimeters.

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

[0170] In some embodiments, when the user device 400 (FIG. 10) receives the 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 / mobile app / unique transaction identifier." In one example, the web resource may launch an identified wallet payment application on the user device 400.

[0171] A web resource may be initiated or launched, for example, via a progressive web application, via a responsive web application (e.g., a JavaScript web application), via a rich internet application, via a single page application, or via a multi-page application.

[0172] In some embodiments, the user device 400 (FIG. 10) may include an application for receipt storage and display or an electronic mobile payment application. The electronic receipt may be displayed by the application in a format determined by the transactor 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 (FIG. 10) may launch a web browser application that renders an output at the location of the unique URL that includes the electronic receipt. The format of the electronic receipt may be a format determined by the transactor associated with the electronic receipt. The electronic receipt may be generated using the transaction data and displayed by the user device 400 using an application. The 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]

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

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

[0177] In operation 1404, the user device 400 accesses the URL.

[0178] At operation 1406, in response to accessing the URL, the user device 400 performs access to a first web resource of the URL. The first web resource launches an electronic wallet payment application on the user device 400. In some examples, the electronic wallet payment application is associated with the electronic wallet payment server 1010.

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

[0180] At operation 1408, the user device 400 executes an invocation of an electronic wallet payment application to complete the transaction with the electronic wallet payment server 1010.

[0181] In one example of the method 1400, at operation 1402, an NDEF message is received from an NFC device 2000 that is a third party to the electronic wallet payment server 1010.

[0182] At operation 1410, the user device 400 receives confirmation that the transaction was successfully completed. At operation 1412, the user device 400 performs a URL access of a second web resource on the server 300. For example, the user device 400 can access the same URL of operation 1404 to access the second web resource.

[0183] At operation 1414, the user device 400 performs a display of an electronic receipt for the transaction in response to accessing the second web resource. In one example, the display includes displaying the electronic receipt via a web page, an application page, or an electronic mobile payment application corresponding to the URL.

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

[0185] In one example of the method 1400, in operation 1414, displaying the electronic receipt is performed by the user device 400 without the use of an email address, a text message, or an exchange of financial authentication information with the server 300.

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

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

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

[0189] In operation 1506 , the server 300 performs generation of a first web resource associated with a URL that launches an electronic wallet payment application at the electronic wallet payment server 1010 .

[0190] In operation 1508, the server 300 performs a reception of access to the URL, for example, in response to an NFC Data Exchange Format (NDEF) message that includes the URL as a payload.

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

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

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

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

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

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

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

[0198] In one example of the method 1500 , at operation 1512 , the confirmation is received from the NFC device 2000 or the 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 the electronic wallet payment application associated with the POS terminal 100 includes a Quick Response (QR) code for the electronic wallet payment application that is unique to the POS terminal 100.

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

[0201] In one example of the method 1500 , the server 300 is a third party to an electronic wallet payment application and is an electronic receipt server that does not communicate with the electronic wallet payment server 1010 .

[0202] In one example of the method 1500, in act 1504, the establishment includes the server 300 generating a URL.

[0203] In one example of the method 1500, at act 1504, the establishing includes receiving a URL from the NFC device 2000 or the POS terminal 100.

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

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

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

[0207] Reference is now made to Figure 1, which illustrates a payment system 1000 according to an example embodiment. Referring to Figure 1, the payment system 1000 according to an example 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, the NFC device 2000, the server 300, and the 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, the NFC device, the server 300, and the user device 400 may connect to the Internet via Wi-Fi technology.

[0209] The POS terminal 100, according to some illustrated embodiments, is a device that may process transactions. A transaction may correspond to one or more purchases (one or more items and / or one or more services) and a payment. The illustrated embodiments may be described herein in the context of purchasing an item, with the understanding that services as well as charitable donations and goodwill apply as well. For example, a transaction may correspond to an 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 a transaction, 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 an entity (not shown), such as a merchant or acquirer.

[0211] In some embodiments, as shown, 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 illustrated embodiment is not so limited.

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

[0213] 1 shows the POS terminal 100 as a single device, the illustrated embodiments are not so limited and the POS terminal 100 may be comprised of multiple devices that may be in communication with the NFC device 2000.

[0214] The NFC device 2000 is a computing device that enables a transactee (consumer) to automatically launch an electronic wallet payment application, in contrast to a traditional electronic wallet payment application that is typically initiated by the transactee on a user device 400, followed by a QR code scan after launching the traditional electronic wallet payment application.

[0215] The NFC device 2000 may transmit and / or exchange data to / with the user device 400 using NFC wireless connection technology. According to an embodiment, the NFC device 2000 may generate or include an NFC tag and may communicate using NFC standardized technologies, although illustrated embodiments are not so limited, and the NFC device 2000 may additionally or alternatively use standardized technologies such as Bluetooth, Radio Frequency Identification (RFID), Magnetic Secure Transmission (MST), Beacons, Zigbee, etc.

[0216] The NFC device 2000 may communicate with the server 300 via a communications network (not shown). In some implementations, the communications network may be the Internet, and the NFC device 2000 may communicate with the server 300 to send and receive data via the Internet, although example embodiments 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, although example embodiments are not limited thereto.

[0217] Server 300 may be, for example, a dedicated server or a cloud server, although the illustrated embodiment is not limited thereto.

[0218] The server 300 may be connected to the NFC device 2000 via a communication network (not shown). The server 300 may receive data from the NFC device 2000 and store the data in a database. The server 300 may be connected to the user device 400 via a communication network (not shown) and may transmit data to the user device 400. Here, the communication network may be the Internet, but the illustrated embodiment is not limited thereto. The user device 400 may access the Internet via Wi-Fi or a mobile network to access the server 300, but the illustrated embodiment is not limited thereto.

[0219] The user device 400 is a device on which a user, the subject of a transaction, performs electronic wallet transactions and displays electronic receipts. The user device 400 may include a smartphone, a smart watch, a smart device, a personal digital assistant (PDA), a wireless communication terminal, wearable technology (e.g., smart watch, smart glasses), etc., although the illustrated embodiment is not so limited.

[0220] The user device 400 is a device that supports NFC technology for wirelessly communicating with the NFC device 2000. According to an embodiment, the user device 400 may support the NFC standardized technology, although the illustrated embodiment is not so limited, and in addition or instead, the user device 400 may support standardized technologies such as Bluetooth, Radio Frequency Identification (RFID), Magnetic Secure Transmission (MST), Beacon, Zigbee, etc.

[0221] Reference is now made to Figure 5, which is a diagram illustrating a payment system 1000 according to an example embodiment. Referring to Figure 5, there is shown a payment system 1000 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 functionality of an NFC device 2000 and is capable of interacting with the NFC device 2000 in a manner similar to that according to the examples described herein.

[0222] The payment system 1000 of Figure 5 is similar to the payment system 1000 of Figure 1. However, according to the example embodiment of 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 stored on a recording medium accessible to the POS terminal 100. In some examples, the NFC device 2000 is implemented in the form of one or more applications stored in a memory unit of the POS terminal 100. Thus, according to the example of Figure 5, the POS terminal 100 includes the functionality of the NFC device 2000 and is capable of interactive operation in a manner similar to the NFC device 2000 according to the examples described herein.

[0223] Figure 6 illustrates a method 600 for facilitating electronic wallet payments according to an example embodiment. Method 600 is illustrated as a message conversation diagram. Figure 7 is a flow chart of another example method 700 for facilitating electronic wallet payments according to an example embodiment. Figure 8 is also a flow chart of another example method 800 for facilitating electronic wallet payments according to an example embodiment.

[0224] In the example method 600 of Figure 6, the NFC device 2000, rather than the POS terminal 100, is in communication with the server 300. An embodiment of the method 600 of Figure 6 may be performed by the payment system 1000 shown in Figure 10. In the example method 700 of Figure 7, both the POS terminal 100 and the NFC device 2000 are in communication with the server 300. An embodiment of the method 700 of Figure 7 may be performed by the payment system 1000 shown in Figure 11. In the example method 800 of Figure 8, the POS terminal 100, rather than the NFC device 2000, is in communication with the server 300. An embodiment of the method 800 of Figure 8 may be performed by the payment system 1000 shown in Figure 12. Similar reference numbers may be used in Figures 6, 8 and 9 to indicate similar elements or features.

[0225] For example, at the start of method 600 of FIG. 6, at operation 602, the transaction has not yet been completed. For example, at 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 a time after one or more items have been scanned or entered at POS terminal 100. For example, all items have been scanned or entered into POS terminal 100, but no expenditure has yet been provided. In some examples, discounts and purchase points have been applied, if applicable.

[0226] At operation 604 , transaction information corresponding to the transaction and an identification of the electronic wallet payment application of the electronic wallet payment server 1010 are transmitted by the POS terminal 100 and received by the NFC device 2000 .

[0227] In operation 606, the NFC device 2000 performs transmission of the transaction information and the identification information of the electronic wallet payment application to the server 300.

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

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

[0230] As another 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 unique transaction identifier that includes a hash function applied to the transaction information, and / or date and time information for the transaction, and / or a unique device identifier. The server 300 associates the URL with the first web resource.

[0232] In operation 612, the NFC device 2000 generates and emits, via a near field communication (NFC) tag controller, an NFC Data Exchange Format (NDEF) message that includes a URL as a payload.

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

[0234] In operation 622, the user device 400 launches an electronic wallet payment application and accesses the electronic wallet payment server 1010. In one example, the electronic wallet payment application of the user device 400 is automatically populated with transaction information as triggered by the 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 similar or identical information as a QR code stored on the server 300. For example, the QR code is for an electronic wallet payment application specific to the POS terminal 100 or the transactor (merchant). In conventional systems, the QR code is used to manually execute a transaction using the camera of the user device 400, where scanning the QR code launches the payment application and accesses the payment server 1010.

[0236] At operation 624, the payment server 1010 authorizes the transaction. For example, information such as a password or biometrics can be sent to the payment server 1010 via the user device 400.

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

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

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

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

[0241] In another example of operation 638, the server 300 generates an electronic receipt in a format determined by the transactor (merchant) using the transaction information and transmits the electronic receipt to the user device 400 for display using a mobile application or an electronic mobile payment application.

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

[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, such as, for example, "unique transaction identifier" in the format "www.domain / mobile app / unique transaction identifier".

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

[0245] In some instances, the transaction information does not include financial authentication information, which is often sensitive personal information and, in some cases, prohibited by financial regulations from being sent to the server 300, even though in some instances the server 300 may be a third party to the payment server 1010.

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

[0247] The electronic receipt may include an identification and itemization of the specific goods and services of the transaction at the POS terminal 100. In some examples, the electronic receipt may include specific identifying information of the transaction so that the electronic receipt can be used for audit purposes. The electronic receipt may include a unique transaction identifier (the same unique transaction identifier that was in the URL). The electronic receipt may include any information used in the unique transaction identifier, such as, for example, a hash function applied to the transaction information, and / or date and time information for the transaction, and / or a unique device identifier.

[0248] In some instances, the electronic receipt may include certain unique identifying information for the transaction so that the electronic receipt can be used 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 the server 300.

[0250] According to example embodiments, the use of an identifier when generating an address (e.g., a URL) and then transmitting the address via NFC to the user device 400 can ensure the following: In some examples, a particular electronic receipt may be provided for issuance to only one user. Other users receive different URLs with their own (unique) identifiers. A particular electronic receipt ensures one-to-one uniqueness of the electronic receipt based on the use of the (unique) identifier or a hash thereof. In some examples, a particular electronic receipt is deleted by the server 300 after retrieval by the user device 400.

[0251] In some instances, as a result, an address (URL) may be visited by, for example, one user only by one user device 400. If another user subsequently attempts to access the same address (URL), the address may be deleted by the server 300 and therefore may become non-functional after retrieval on the user device 400, thus maintaining the user's personal privacy and security.

[0252] In some examples, the server 300 may store transaction information corresponding to the 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 web page linked to the address. As a result, the user device 400 can display the electronic receipt by accessing the web page linked to the address via the user device 400.

[0253] In one example, the user device 400 displays an electronic receipt from a web page that corresponds to a web page URL or an application page.

[0254] For example, user device 400 may operate without activating a camera to scan a QR code, exchanging an email address or phone number, or exchanging sensitive financial credentials with server 300. Rather, a web resource may be loaded as part of an NFC proximity operation between user device 400 and NFC tag controller 2070 via a URL to communicate an address and initiate an e-wallet payment application on user device 400.

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

[0256] An e-receipt is a type of electronic document in which transaction information is displayed based on a set of rules according to a format determined by a provider. The provider may be the transactor associated with the e-receipt. For example, the provider may be a seller or retailer, but the illustrated embodiment is not so limited. The provider is distinct from the transacted party (e.g., consumer, user, customer, etc.).

[0257] FIG. 9 illustrates an example of an electronic receipt 900 according to an illustrated embodiment. As shown in FIG. 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 transaction date and time, an identification of one or more items associated with the transaction (e.g., the name of one or more goods and / or services associated with the transaction), the payment amount associated with each of the one or more items, the quantity of the one or more items, the total payment amount, the tax amount, the payment type, a receipt authorization number, the transactor name, the transactor number (e.g., a corporate number, etc.), the transactor address, the transactor telephone number, the transaction number, etc. As previously discussed, 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 transactor and / or user using a web browser, application, or wallet payment application of the user device 400. Traditionally, in order to view an electronic receipt, one must often complete a login process via the user device 400. Illustrated 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 electronic wallet payment application of the user device 400.

[0259] In some embodiments, the consumer can receive and check the electronic receipt 900 on the user device 400. Thus, a URL may be sent to the user device 400 via an NDEF message according to the illustrated embodiment, so that the user device 400 can execute the URL directly using a pre-configured command in the NDEF message. In this manner, the user device 400 may initiate an electronic 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 instances, the exchange of URLs via NDEF messages uses far fewer resources than the web resources themselves.

[0261] In some embodiments, the consumer may be provided with the electronic receipt 900 via the user device 400 without providing financial authentication information to the server 300. As a result, according to the illustrated embodiment, unnecessary disclosure 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 more conveniently displayed on the user device 400.

[0262] In some embodiments, the user may be provided with an electronic receipt 900 that includes multiple transaction information. Traditionally, when an electronic receipt is issued after a transaction through an associated application or short message service (SMS), only limited transaction information may be displayed on the electronic receipt. For example, in some traditional situations, only the total payment amount is displayed, and detailed transaction information (e.g., identification information of one or more items associated with the transaction, the quantity of the one or more items, the payment amount associated with each item, and 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 that includes multiple transaction information.

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

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

[0265] In one example, financial authentication information of the transactor and the user device 400 is not included in the electronic receipt 900 because it is not known to the server 300 .

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

[0267] In some embodiments of the deep link URL address or the 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 electronic wallet payment application or display an electronic receipt. For example, the user device 400 may execute an application and access a mobile application page or a web application page linked to the received address. The user device 400 may receive the address via an NDEF message and, as a predetermined action, execute an associated mobile application and access a web page linked to the address.

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

[0269] 7, both the POS terminal 100 and the NFC device 2000 are in communication with the server 300. An embodiment of the method 700 of FIG. 7 may be performed by the payment system 1000 shown in FIG.

[0270] Operation 702 is the same as or similar to operation 602 .

[0271] At operation 704 , transaction information corresponding to the transaction, an identification of the electronic wallet payment application on the electronic wallet payment server 1010 is sent by the POS terminal 100 and received by the server 300 .

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

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

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

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

[0276] Referring now to the example 800 of Figure 8, in which a POS terminal 100 rather than an NFC device 2000 is in communication with the server 300. An embodiment of the method 800 of Figure 8 may be performed by a payment system 1000 shown in Figure 12.

[0277] Operation 802 is the same as or similar to operation 602 .

[0278] At operation 804 , transaction information corresponding to the transaction and an identification of the electronic wallet payment application of the electronic wallet payment server 1010 are sent by the POS terminal 100 and received by the server 300 .

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

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

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

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

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

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

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

[0286] In exemplary embodiments, unless expressly stated to the contrary, variations such as "comprises" or "comprising" are understood to be meant to imply the inclusion of the specified elements without excluding other elements.

[0287] In the illustrated embodiment, a "module" is a hardware component, such as a processor or circuitry, and / or a software component executing on hardware, such as a processor.

[0288] In the illustrated embodiment, 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, application specific integrated circuits (ASICs), etc., and may be implemented separately from each other or combined together to implement 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, and may be located in one location or distributed across multiple network modules. Some or all of the modules may be selected according to actual requirements to achieve the objectives of the solutions of the embodiments.

[0290] Furthermore, the functional modules of the illustrated 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 alone.

[0291] When the function is implemented in the form of a software function module and sold or used as an independent product, the function may be stored in a computer-readable recording medium (non-transitory). Based on such understanding, the technical solution of the illustrated embodiment may be implemented in the form of a software product. The software product is stored in a recording medium and includes some instructions for instructing a computer device (such as a personal computer, a server, or a network device) to execute all or part of the methods described in the illustrated embodiment. The aforementioned storage medium includes a Universal Serial Bus (USB) flash drive, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, etc.

[0292] In the described methods or block diagrams, the boxes may represent events, operations, steps, functions, processes, modules, messages, and / or state-based operations, etc. Although some illustrated embodiments are described as occurring in a particular order, some of the steps or processes may be performed in a different order, so long as the result of reordering a particular step does not prevent or impair the occurrence of a subsequent step. Furthermore, some of the messages or steps described herein may be eliminated or combined in other embodiments, and some of the messages or steps described herein may be separated into multiple sub-messages or sub-steps in other embodiments. Furthermore, some or all of the steps may be repeated, as appropriate. Elements described as methods or steps apply to computing devices or subcomponents as well. References to terms such as "send" or "receive" may be interchanged depending on the perspective of a particular device.

[0293] The described embodiments are considered to be exemplary and not limiting, and the illustrated embodiments shown as methods apply equally to computing devices or devices.

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

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

Claims

1. receiving, from a point-of-sale (POS) terminal, transaction information corresponding to the transaction and an identification of an electronic wallet payment application at an electronic wallet payment server; sending the transaction information and the identification information of the electronic wallet payment application to a server; establishing a Uniform Resource Locator (URL) that addresses the server and identifies a first web resource that launches the electronic wallet payment application, the URL including a unique transaction identifier, the unique transaction identifier including a hash function applied to the transaction information, and / or date and time information for the transaction, and / or a unique device identifier; generating, via a Near Field Communication (NFC) tag controller, an NFC Data Exchange Format (NDEF) message including the URL as a payload; and transmitting, via the NFC tag controller, an NFC signal corresponding to the NDEF message.

2. The computer-implemented method of claim 1 , further comprising receiving, from the POS terminal, a confirmation of successful completion of the transaction and transmitting the confirmation to the server.

3. The computer-implemented method of claim 1 , wherein the URL identifies a second web resource for displaying an electronic receipt for the transaction upon successful completion of the transaction.

4. The computer-implemented method of claim 3 , wherein the electronic receipt includes the unique transaction identifier.

5. The computer-implemented method of claim 1 , wherein the server contains account information for the electronic wallet payment application associated with the POS terminal.

6. 6. The computer-implemented method of claim 5, wherein 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 that is unique to the POS terminal.

7. The computer-implemented method of claim 1 , wherein the URL includes an identification of the electronic wallet payment application.

8. 8. The computer-implemented method of claim 7, wherein the URL is a deep link, in which an identification of the electronic wallet payment application is nested from the unique transaction identifier.

9. The computer-implemented method of claim 1 , wherein the establishing comprises generating the URL and further comprises sending the URL to the server.

10. The computer-implemented method of claim 1 , wherein the establishing comprises receiving the URL.

11. 2. The computer-implemented method of claim 1, wherein receiving the transaction information is from the point-of-sale (POS) terminal, and wherein the computer-implemented method is performed by an NFC device that is a device separate from the POS terminal.

12. 10. The computer-implemented method of claim 1, wherein the computer-implemented method is performed by an NFC device that is a third party and does not communicate with the electronic wallet payment server.

13. The computer-implemented method of claim 1 , wherein the unique device identifier is an identifier of the POS terminal.

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

15. The computer-implemented method of claim 1 , wherein the first web resource automatically enters a payment amount into the electronic wallet payment application.

16. 10. The computer-implemented method of 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 computer-implemented method of claim 1 , wherein the receiving transaction information and the transmitting transaction information do not include financial authentication information.

18. The computer-implemented method of claim 1 , wherein the NDEF message contains only the URL as a payload and no other payload.

19. The computer-implemented method of claim 1 , wherein the electronic wallet payment server and the electronic wallet payment application are debit-based.

20. an NFC tag controller; A communication module; A processor; 20. A computing device comprising: at least one memory storing instructions that, when executed by the processor, cause the processor to perform the computer-implemented method of any one of claims 1 to 19.

21. 21. The computing device of claim 20, wherein the transaction information is from the point-of-sale (POS) terminal, and the computing device is an NFC device separate from the POS terminal.

22. 1. A computer-implemented method executed by a user device, comprising: receiving, via a Near Field Communication (NFC) tag reader, an NFC Data Exchange Format (NDEF) message including a URL as a payload, the URL addressing a server, the URL including a unique transaction identifier, the unique transaction identifier including a hash function applied to 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 at the URL that launches an electronic wallet payment application on the user device in response to accessing the URL; and initiating the electronic wallet payment application to complete the transaction using an electronic wallet payment server.

23. 23. The computer-implemented method of claim 22, wherein receiving the NDEF message is from an NFC device, the NFC device being a third party to the electronic wallet payment server.

24. 23. The computer-implemented method of claim 22, wherein the first web resource automatically populates at least a portion of the transaction information into the electronic wallet payment application.

25. 23. The computer-implemented method of claim 22, wherein the first web resource automatically enters a payment amount into the electronic wallet payment application.

26. receiving confirmation of successful completion of said transaction; accessing a second web resource at the URL; 23. The computer-implemented method of claim 22, further comprising: in response to accessing the second web resource, displaying an electronic receipt for the transaction.

27. 27. The computer-implemented method of claim 26, wherein the electronic receipt includes the unique transaction identifier.

28. 27. The computer-implemented method of claim 26, wherein the displaying comprises displaying the electronic receipt via a web page, an application page, or an electronic wallet payment application.

29. receiving confirmation of successful completion of said transaction; responsive to confirmation of successful completion of the transaction, displaying an electronic receipt for the transaction based on the transaction information; 23. The computer-implemented method of claim 22, further comprising: displaying the electronic receipt.

30. An NFC tag reader; A communication module; A processor; 30. A computing device comprising: at least one memory storing instructions that, when executed by the processor, cause the processor to perform the computer-implemented method of any one of claims 20 to 29.

31. 1. A computer-implemented method executed by a server, comprising: receiving transaction information corresponding to the transaction and an identification of an electronic wallet payment application at an electronic wallet payment server; receiving a Uniform Resource Locator (URL) addressing a server, the URL including a unique transaction identifier, the unique transaction identifier including a hash function applied to the transaction information, and / or date and time information for the transaction, and / or a unique device identifier; generating a first web resource associated with the URL that launches the electronic wallet payment application; receiving access to the URL in response to an NFC Data Exchange Format (NDEF) message including the URL as a payload; providing the first web resource through said access to said URL; receiving confirmation of successful completion of said transaction; generating a second web resource associated with the URL for displaying an electronic receipt for the transaction; providing the second web resource through a second access to the URL.

32. 32. The computer-implemented method of claim 31, wherein receiving the transaction information is from an NFC device or a point-of-sale terminal.

33. 32. The computer-implemented method of claim 31, wherein receiving the confirmation is from an NFC device or a point of sale terminal.

34. 32. The computer-implemented method of claim 31, wherein the server has account information for the electronic wallet payment application associated with a POS terminal.

35. 35. The computer-implemented method of claim 34, wherein 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 that is unique to the POS terminal.

36. 32. The computer-implemented method of claim 31, wherein the URL includes an identification of the electronic wallet payment application.

37. 37. The computer-implemented method of claim 36, wherein the URL is a deep link, in which an identification of the electronic wallet payment application is nested from the unique transaction identifier.

38. 32. The computer-implemented method of claim 31, wherein receiving the transaction information does not include financial authentication information.

39. 32. The computer-implemented method of claim 31, wherein the server is an electronic receipt server that is a third party to the electronic wallet payment application and does not communicate with the electronic wallet payment server.

40. 32. The computer-implemented method of claim 31, wherein the establishing comprises generating the URL.

41. 32. The computer-implemented method of claim 31, wherein the establishing comprises receiving the URL.

42. 32. The computer-implemented method of claim 31, further comprising registering account information for the electronic wallet payment application associated with a POS terminal.

43. 43. The computer-implemented method of claim 42, wherein the account information includes a quick response (QR) code of the electronic wallet payment application that is unique to the POS terminal.

44. 32. The computer-implemented method of claim 31, wherein receiving the transaction information is from an NFC device that is a device separate from a point-of-sale (POS) terminal.

45. 45. The computer-implemented method of claim 44, wherein the unique device identifier is a POS terminal identifier.

46. 32. The computer-implemented method of claim 31, wherein the first web resource and the second web resource are each a progressive web application, a responsive web application, a rich internet application, a single page application, or a multi-page application.

47. 32. The computer-implemented method of claim 31, wherein the NDEF message includes only a URL as the payload and no other payload.

48. 32. The computer-implemented method of claim 31, wherein the electronic wallet payment server and the electronic wallet payment application are debit-based.

49. A communication module; A processor; 50. A server comprising at least one memory storing instructions that, when executed by the processor, cause the processor to perform the computer-implemented method of any one of claims 31 to 48.

50. 50. The server of claim 49, wherein the server is an electronic receipt server that is a third party to the electronic wallet payment application and does not communicate with the electronic wallet payment server.

51. A non-transitory computer readable medium storing instructions that, when executed by a processor, cause the processor to perform a computer-implemented method according to any one of claims 1 to 19, 22 to 29, and 31 to 48.

Images