Payment method, system and related device

Abstract

The invention discloses a payment method, system and related device, the method is applied to an electronic device, and the method comprises the steps: after entering a radio frequency field of a collection device of a first merchant, receiving a first payment request sent by the collection device, the first payment request comprising a first identifier and a first amount of money of the first merchant; determining one or more preferential activities of the first merchant based on the first payment request; determining one or more payment modes supported by collection equipment based on the first payment request; determining a first payment mode from payment modes supported by one or more collection devices based on one or more preferential activities of the first merchant; payment is completed through the first payment mode. In this way, the user overhead can be reduced.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a payment method, system and related apparatus. Background Technology

[0002] With the continuous development of communication technology, communication plays an increasingly important role in daily life. For example, in daily consumption scenarios, users can use communication technology to make payments.

[0003] In everyday consumption scenarios, merchants offer various promotional activities to boost sales, such as discounts on specific items or discounts on purchases exceeding a certain amount. When shopping at a merchant, if the selected items meet the conditions of the promotion, users can enjoy the corresponding discount.

[0004] When users complete payments using their existing payment methods, they may not be able to access merchant promotions, which could lead to increased spending. Summary of the Invention

[0005] This application provides a payment method, system, and related device that allows users to obtain merchant promotions before making a payment and complete the payment based on the promotions, thereby reducing unnecessary expenses for users.

[0006] In a first aspect, this application provides a payment method applied to an electronic device, the method comprising: after entering the radio frequency field of a first merchant's receiving device, receiving a first payment request sent by the receiving device, the first payment request including a first identifier of the first merchant and a first amount; determining one or more promotional activities of the first merchant based on the first payment request; determining one or more payment methods supported by the receiving device based on the first payment request; determining a first payment method from the one or more payment methods supported by the receiving device based on the one or more promotional activities of the first merchant; and completing payment through the first payment method.

[0007] In this way, electronic devices can determine the final payment method (i.e., the primary payment method) based on the merchant's promotional activities and complete the payment using that method. When purchasing the same product, users will spend less money compared to not taking advantage of merchant promotions, thus reducing unnecessary expenses.

[0008] In one possible implementation, determining one or more promotional activities of the first merchant based on the first payment request specifically includes: sending a first identifier to the first server; and receiving one or more promotional activities of the first merchant sent by the first server.

[0009] In this way, electronic devices can obtain promotional offers from a first merchant based on the first merchant's first identifier from a first server. The first server can store promotional offers from one or more merchants.

[0010] In one possible implementation, the first payment request may also include one or more promotional offers from the first merchant.

[0011] In this way, when the electronic device interacts with the payment device, it can receive promotional offers from the first merchant sent by the payment device, without needing to obtain them from the first server. Furthermore, the promotional offers sent by the payment device are real-time offers from the first merchant, eliminating the possibility of any delays.

[0012] In one possible implementation, before entering the radio frequency field of the first merchant's payment device, the method further includes: receiving first promotional information sent by a first server, the first promotional information including promotional activities of one or more merchants; determining one or more promotional activities of the first merchant based on a first payment request, specifically including: determining one or more promotional activities of the first merchant from the first promotional information based on a first identifier.

[0013] In this way, before a user makes a purchase, the electronic device can obtain promotional offers from one or more merchants from a first server. When the user pays through the electronic device, the first merchant's promotional offer is determined from these offers, and the payment is completed. By obtaining promotional offers from multiple merchants in advance, there is no need to retrieve the first merchant's offer during the payment process, which shortens the interaction steps and improves payment efficiency.

[0014] In one possible implementation, before receiving the first offer information sent by the first server, the method further includes: when the electronic device enters the first geofence, sending a first request to the first server, the first request carrying an identifier of the first geofence, the first request being used to request the first server to send the first offer information, one or more merchants being located within the first geofence.

[0015] When an electronic device enters the first geofence, it can obtain the first set of promotional information for that geofence. This information can include promotional activities from one or more merchants within the first geofence. This allows users to see real-time promotional offers from nearby merchants and decide whether to go shopping.

[0016] In one possible implementation, after receiving the first offer information sent by the first server, the method further includes: displaying the first offer information.

[0017] In this way, after obtaining the initial offer information, electronic devices can push the offer to users, who can then decide whether to shop at the designated merchant based on this information. Furthermore, pushing initial offer information can also bring customer traffic to merchants.

[0018] In one possible implementation, determining one or more payment methods supported by the payment device based on the first payment request specifically includes: obtaining one or more payment methods supported by the payment device based on the first identifier.

[0019] In this way, one or more payment methods supported by the payment device can be obtained based on the first identifier of the first merchant. For example, one or more payment methods supported by the payment device can be obtained from the first server (or other server) based on the first identifier.

[0020] In one possible implementation, the first payment request may also include an identifier of one or more payment methods supported by the receiving device.

[0021] In this way, one or more payment methods supported by a payment device can be determined based on the identifiers of the payment methods supported by one or more payment devices carried in the first payment request.

[0022] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a first payment response to a receiving device. The first payment response includes a first payment credential, which indicates a first payment account for the first payment method.

[0023] In this way, the electronic device can send a payment credential to the receiving device, which then sends the payment credential to a second server, which completes the payment.

[0024] In one possible implementation, the first payment request further includes a first receiving account; completing the payment through a first payment method specifically includes: determining a second amount corresponding to the first payment method based on a first amount and one or more promotional activities of the first merchant; sending a second payment response to a second server, the second payment response including a first payment credential, a second amount, and a first receiving account, the first payment credential being used to indicate the first payment account of the first payment method.

[0025] When an electronic device interacts with a payment device, the electronic device can receive the payment account information sent by the payment device. Furthermore, the electronic device can determine the payment method, payment account, and actual payment amount (i.e., the second amount) based on the merchant's promotional activities. In this case, the electronic device can interact with a second server, sending information such as the payment account, actual payment amount, and payment voucher to the second server to complete the payment. In this way, the electronic device no longer needs to interact with the second server through the payment device.

[0026] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a third payment response to a second server. The third payment response includes a first payment credential, which indicates a first payment account for the first payment method.

[0027] In this scenario, the electronic device can send a first payment credential to the second server via a communication connection; additionally, the receiving device can also send a receiving account to the second server, which will then complete the payment based on the information sent by the electronic device and the receiving device.

[0028] In one possible implementation, the first payment credential is also used to indicate the first payment method.

[0029] In this way, the first payment receipt can inform the receiving device or electronic device of the final payment method.

[0030] In one possible implementation, the first payment response also includes an identifier of the first payment method.

[0031] In this way, the payment method identifier can inform the receiving device of the final payment method used by the electronic device.

[0032] In one possible implementation, determining a first payment method from one or more payment methods based on one or more promotional activities of a first merchant specifically includes: determining the discount amount for each of the one or more payment methods based on one or more promotional activities of the first merchant; displaying one or more payment options, the one or more payment options including a first option corresponding to the first payment method, the first option including an identifier of the first payment method and the discount amount of the first payment method; receiving and responding to the user's operation on the first option, and determining the first payment method.

[0033] In this way, electronic devices can display the discount amount (or actual payment amount) for one or more payment methods based on the merchant's promotional activities, so that users can choose the appropriate payment method to complete the payment.

[0034] In one possible implementation, a first payment method is determined from one or more payment methods based on one or more promotional activities of the first merchant. Specifically, this includes: determining the discount amount for each of the one or more payment methods based on one or more promotional activities of the first merchant; and determining the first payment method based on the discount amount for each of the one or more payment methods, wherein the first payment method is the payment method with the largest discount amount among the one or more payment methods.

[0035] In this scenario, the electronic device can determine the payment method with the largest discount (or smallest actual payment) after identifying the discount amount and / or actual payment amount for each payment method supported by the receiving device, and complete the payment based on that method. This eliminates the need for the user to make any additional selection and ensures that the user receives the maximum discount.

[0036] In one possible implementation, the method further includes: receiving a first notification sent by a second server, the first notification being used to notify the electronic device that the payment was successful.

[0037] In this way, the electronic device can determine whether the payment was successful based on the first notification sent by the second server.

[0038] In one possible implementation, the method further includes: receiving a first notification sent by the receiving device, the first notification being used to notify the electronic device that the payment was successful.

[0039] In this way, electronic devices can determine whether the payment was successful based on the first notification sent by the receiving device.

[0040] In one possible implementation, the method further includes: determining a first promotional activity from one or more promotional activities of a first merchant based on a first payment method; after completing payment using the first payment method through a first payment account, the method further includes: sending a first crowdsourcing to a first server, the first crowdsourcing including the location information of the electronic device, a first identifier of the first merchant, and the first promotional activity.

[0041] In this way, after the electronic device determines the final payment method, it can report the payment crowdsourcing to the first server. The payment crowdsourcing is used to instruct the first server to update the first merchant's promotional activities stored on the first server based on the payment crowdsourcing.

[0042] In one possible implementation, the first notification includes a first amount and / or a second amount, the first amount being the amount received by the receiving device and the second amount being the amount paid by the electronic device; the first crowdsourcing also includes the first amount and / or the second amount.

[0043] The payment crowdsourcing reported by electronic devices may also include the actual amount paid and / or the amount received, so that the first server can confirm the specific discount details of the first merchant's promotional activities.

[0044] In one possible implementation, after determining the first promotional activity from one or more promotional activities of the first merchant based on the first payment method, the method further includes: sending the first promotional activity to the receiving device.

[0045] This way, once the promotional offer is determined, it can be sent to the payment device so that the device can check whether the offer is still valid.

[0046] In one possible implementation, after entering the radio frequency field of the receiving device, the method further includes: receiving a probe frame sent by the receiving device, the probe frame indicating that the receiving device supports a specified NFC protocol; sending a probe ACK frame to the receiving device, the probe ACK frame indicating that the electronic device supports the specified NFC protocol; receiving a pick frame sent by the receiving device, the pick frame carrying device characteristic information of the receiving device, the device characteristic information including a service identifier and a device organization identifier, wherein the service identifier indicates the type of NFC service supported by the receiving device, and the device organization identifier indicates the manufacturer using the receiving device to provide NFC services; determining, based on the device characteristic information of the receiving device, that the type of NFC service of the receiving device is codeless payment; and sending a pick ACK frame to the receiving device, the pick ACK frame indicating that the electronic device has determined the NFC service type of the receiving device.

[0047] In this way, electronic devices can interact with the receiving device through the first protocol based on NFC technology to determine the NFC service type of the receiving device.

[0048] Secondly, this application provides a payment method applied to an electronic device, the method comprising: upon entering the radio frequency field of a first merchant's receiving device, receiving a first payment request sent by the receiving device, the first payment request including a first identifier of the first merchant and a first amount; determining one or more promotional activities of the first merchant based on the first payment request; determining identifiers of one or more payment methods supported by the receiving device based on the first payment request; determining a first payment method from one or more payment methods based on the one or more promotional activities of the first merchant; determining a first promotional activity from the one or more promotional activities based on the first payment method; sending a fourth payment response to the receiving device, the fourth payment response including a first payment credential of the first payment method and the first promotional activity, the first payment credential indicating a first payment account of the first payment method; receiving second promotional information sent by the receiving device, the second promotional information including one or more promotional activities of the first merchant; determining a second payment method and a second promotional activity based on the second promotional information; and completing payment through the second payment method.

[0049] Using this payment method, if the first promotional offer that the electronic device was about to enjoy expires, the electronic device can receive a second promotional offer from the receiving device. This second offer is the real-time promotional offer from the first merchant. The electronic device can then redetermine the payment method based on this second offer (i.e., the second payment method) and complete the payment using it. This avoids payment failures caused by the electronic device paying based on an expired promotional offer.

[0050] In one possible implementation, the payment is completed via a second payment method, which further includes sending a second crowdsourcing package to a first server. The second crowdsourcing package includes the location information of the electronic device, a first identifier of the first merchant, and second promotional information.

[0051] Upon receiving a second discount information from the payment receiving device, the electronic device can include this second discount information when reporting to the payment crowdsourcing platform. This allows the first server to update the first merchant's promotional activities stored on the first server based on the second discount information. In this way, when other users subsequently shop at the first merchant, they can access the merchant's real-time promotional activities instead of receiving expired ones.

[0052] Thirdly, this application provides a payment method applied to an electronic device. The method includes: receiving first promotional information sent by a first server, the first promotional information including promotional activities of one or more merchants within a first geofence, the one or more merchants including the first merchant; receiving a first merchant identifier sent by a payment receiving device; determining second promotional information from the first promotional information based on the first merchant identifier; sending a first response to the payment receiving device, the first response indicating that the electronic device has successfully received the first merchant identifier; receiving a first selection command sent by the payment receiving device of the first merchant; sending a first selection response to the payment receiving device, the first selection response including identifiers of one or more payment applications supported by the electronic device and the second promotional information; receiving a second selection command sent by the payment receiving device, the second selection command including the identifier of the first payment application; sending a second selection response to the payment receiving device, the second selection response indicating that the first payment application has been successfully selected; and completing the payment through the first payment application.

[0053] In this way, electronic devices can filter out secondary promotional information based on the merchant to which the payment device belongs, and send this information to the payment device so that it can choose the final payment application (i.e., the primary payment application). When purchasing the same goods, users will spend less money compared to not enjoying merchant promotions, thus reducing unnecessary expenses.

[0054] In one possible implementation, the method further includes: when an electronic device enters a first geofence, sending a first request to a first server, the first request carrying an identifier of the first geofence, the first request being used to request the first server to send first promotional information; receiving the first promotional information sent by the first server, specifically including: receiving a first response sent by the first server, the first response including the first promotional information.

[0055] In this way, once the electronic device enters the first geofence, it can obtain the first offer information.

[0056] In one possible implementation, receiving the first merchant identifier sent by the payment device specifically includes: receiving device feature information sent by the payment device, wherein the device feature information of the payment device includes a service identifier and a device organization identifier, wherein the service identifier is used to indicate the type of NFC service supported by the payment device, and the device organization identifier is used to indicate the first merchant identifier.

[0057] In this way, electronic devices can identify the first merchant based on the device organization identifier in the device feature information of the receiving device.

[0058] In one possible implementation, the method further includes: receiving a probe frame sent by a receiving device, the probe frame indicating that the receiving device supports a specified NFC protocol; sending a probe ACK frame to the receiving device, the probe ACK frame indicating that the electronic device supports the specified NFC protocol; receiving device feature information sent by the receiving device, specifically including: receiving a notification frame sent by the receiving device, the notification frame carrying the device feature information of the receiving device; the method further includes: determining that the type of NFC service of the receiving device is codeless payment based on the device feature information of the receiving device; sending a first response to the receiving device, specifically including: sending a notification ACK frame to the receiving device, the notification ACK frame indicating that the notification frame was successfully received; the method further includes: receiving a parameter negotiation command sent by the receiving device; in response to the parameter negotiation command, sending a parameter negotiation response to the receiving device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between the application layer of the receiving device and the electronic device.

[0059] In this way, data transmission parameters between the electronic device's application layer and the receiving device can be negotiated through the NFC protocol, facilitating subsequent data transmission.

[0060] In one possible implementation, the method also includes: displaying the first offer information.

[0061] This allows users to see the first offer information, making it easier for them to choose which merchant to shop at based on that offer.

[0062] In one possible implementation, payment is completed through a first payment application, specifically including: receiving a first order command sent by a receiving device, the first order command including a first order identifier and a first payment amount; sending a first order response to the receiving device, the first order response indicating successful receipt of the first order command; receiving a first initialization transaction command from the receiving device, the first initialization transaction command being used to obtain a first payment credential from the first payment application; and sending a first initialization transaction response to the receiving device, the first initialization transaction response carrying the first payment credential.

[0063] In this way, electronic devices and payment devices can send the first payment credential corresponding to the first payment application to the payment device via order commands, order responses, initial transaction commands, and initial transaction responses. The payment device then interacts with the server corresponding to the first payment application to complete the payment.

[0064] In one possible implementation, the method further includes: receiving a first payment notification sent by a payment receiving device, the first payment notification indicating whether the payment was successful or failed; and / or receiving a second payment notification sent by a second server, the second payment notification indicating whether the payment was successful or failed.

[0065] In this way, electronic devices can determine whether the payment was successful through the payment notification sent by the receiving device (or the server corresponding to the first payment application).

[0066] Fourthly, this application provides an electronic device including one or more processors and one or more memories; wherein the one or more memories are coupled to one or more processors, and the one or more memories are used to store computer instructions, which, when the one or more processors execute the computer instructions, implement the payment method in any possible implementation of any of the above aspects.

[0067] Fifthly, this application provides a chip system comprising: a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the payment method in any possible implementation of any of the above aspects.

[0068] Sixthly, this application provides a readable storage medium storing computer instructions that, when executed by a processor, implement the payment method in any possible implementation of any of the above aspects.

[0069] In a seventh aspect, this application provides a computer program product, including computer instructions, which, when executed by a processor, implement the payment method in any possible implementation of any of the above aspects.

[0070] The beneficial effects of aspects four through seven can be referenced from the beneficial effects of aspects one through three mentioned above. Attached Figure Description

[0071] Figure 1 This is a schematic diagram illustrating the working principle of NFC as provided in an embodiment of this application;

[0072] Figure 2A This application provides a schematic diagram of the system architecture of a payment system.

[0073] Figure 2B This application provides a schematic diagram of the communication interaction between an electronic device and a payment cloud server.

[0074] Figure 2C This is a schematic diagram of the device configuration of an electronic device provided in an embodiment of this application;

[0075] Figure 2D This is a schematic diagram of the device configuration of a payment collection device provided in an embodiment of this application;

[0076] Figure 2E A schematic diagram illustrating the positional relationship between an electronic device and a payment device based on NFC technology, provided as an embodiment of this application.

[0077] Figure 3A This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0078] Figure 3B This is a schematic diagram of a layered architecture of an NFC protocol stack provided in an embodiment of this application;

[0079] Figures 4A-4C An interface for pushing promotional information to users after a group of electronic devices enters a geofence, as provided in this application embodiment;

[0080] Figure 4D-Figure 4G A schematic diagram of an interface for an electronic device to perform a payment method, provided in an embodiment of this application;

[0081] Figure 5 A schematic diagram illustrating a payment method provided in an embodiment of this application;

[0082] Figure 6 This application provides a schematic diagram of a process for an electronic device to obtain merchant discount information.

[0083] Figure 7 A schematic diagram illustrating a payment account deduction process provided for an embodiment of this application;

[0084] Figure 8 This application provides a schematic diagram of a payment process after the payment method is determined.

[0085] Figure 9 A schematic diagram illustrating a payment method provided in an embodiment of this application;

[0086] Figure 10 A flowchart illustrating another payment method provided in an embodiment of this application;

[0087] Figure 11 A flowchart illustrating another payment method provided in an embodiment of this application;

[0088] Figure 12A This is a schematic diagram of the functional modules of a payment cloud server provided in an embodiment of this application;

[0089] Figure 12B A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0090] Figures 13-16 A schematic diagram of a set of communication devices provided in the embodiments of this application;

[0091] Figure 17 A flowchart illustrating a payment method provided in an embodiment of this application;

[0092] Figure 18 A flowchart illustrating another payment method provided in this application embodiment;

[0093] Figure 19 This is a flowchart illustrating a payment method provided in an embodiment of this application. Detailed Implementation

[0094] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0095] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0096] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0097] The working principle of near field communication (NFC) technology in the embodiments of this application is described below.

[0098] Figure 1 A schematic diagram illustrating the working principle of NFC provided in an embodiment of this application is shown.

[0099] like Figure 1 The two parties communicating using NFC technology can include a proximity coupling device (PCD) (also known as an NFC reader) and a proximity integrated circuit card (PICC). The PCD can achieve contactless communication with the PICC in close proximity. The PCD and PICC can allow near-field communication at specific data rates (e.g., 106, 212, 424, or 848 kilobits per second (kbps)) and specific frequencies (e.g., 13.56 MHz). Communication between the PCD and PICC can occur at close range, for example, within a range of approximately 2 to 4 centimeters.

[0100] The PCD (Polymer Capacitor) can generate high-frequency alternating current to produce a radio frequency (RF) field of a specified frequency (e.g., 13.56 MHz), and transmit data to the PICC (Peripherally Input Cell) via this RF field. When the PICC is near the PCD, it can sense the RF field emitted by the PCD. Upon entering the RF field, the PICC can obtain energy from the PCD's RF field through electromagnetic induction, and use this energy to generate electricity to drive the internal circuitry of the PICC, thus enabling data transmission from the PCD to the PICC. Alternatively, the PICC can also transmit data to the PCD by modulating the RF field with a load, achieving data transmission from the PICC to the PCD.

[0101] In the embodiments of this application, the PICC can be a physical NFC tag card. Some NFC devices (e.g., mobile phones, tablets, smartwatches, and other electronic devices) can also simulate themselves as PICCs that conform to NFC-related standards through the data of NFC emulation cards to realize the functions of PICCs and communicate with the PCD based on NFC technology.

[0102] The following describes the system architecture of a payment system 10 provided in an embodiment of this application.

[0103] Figure 2A A schematic diagram of the system architecture of a payment system 10 provided in an embodiment of this application is shown.

[0104] like Figure 2A As shown, the payment system 10 may include an electronic device 100, a payment receiving device 200, and a payment cloud server 300. The electronic device 100 and the payment receiving device 200 may have NFC functionality. When the electronic device 100 enters the radio frequency field of the payment receiving device 200, the electronic device 100 can communicate with the payment receiving device 200 based on NFC technology. The electronic device 100 can also establish a wireless communication connection with the payment cloud server 300, and the payment receiving device 200 can also establish a communication connection with the payment cloud server 300.

[0105] When electronic device 100 enters the radio frequency field of payment receiving device 200 (e.g., by touching payment receiving device 200), electronic device 100 can communicate with payment receiving device 200 based on NFC technology to determine one or more payment methods supported by payment receiving device 200, and optionally, also determine the payment amount. Electronic device 100 can also obtain promotional information corresponding to the geofence where electronic device 100 is located from payment cloud server 300. This promotional information may include promotional activities from one or more merchants within the geofence. Based on the promotional information, the user's selection, or the communication with payment receiving device 200, electronic device 100 can determine the final payment method to be used and send the payment account corresponding to that payment method to payment receiving device 200.

[0106] The payment receiving device 200 can determine the final payment method based on communication with the electronic device 100. The payment receiving device 200 can also receive the payment account corresponding to the payment method from the electronic device 100. After determining the final payment method and corresponding payment account, the payment receiving device 200 can send the payment account to the payment cloud server 300 based on the payment method.

[0107] The payment cloud server 300 can be a server cluster, which may include one or more servers (or server modules). The communication and interaction methods between the various servers in the payment cloud server 300 and the electronic device 100 can be referred to the following: Figure 2B The relevant descriptions in the illustrated embodiments are not detailed here. The payment cloud server 300 can receive and respond to a request from the electronic device 100 for obtaining promotional information carrying a geofence identifier, and send promotional information specifying the geofence to the electronic device 100. The payment cloud server 300 can also deduct funds from the payment account and transfer the payable amount to the payment account based on the amount due, payment account, and receiving account sent by the payment device 200. In some embodiments, before deducting funds from the payment account, the payment cloud server 300 can also initiate payment verification with the electronic device 100 based on the communication connection with the electronic device 100, and perform the deduction operation only after successful verification.

[0108] It is understandable that the above Figure 2A The embodiments shown are merely examples. In the embodiments of this application, the payment system 10 may also include more, fewer, or different electronic devices than those in the above embodiments, such as merchant back-end servers. The merchant back-end server may undertake some of the functions of the payment collection device 200 in the above embodiments, and this application does not limit it here.

[0109] The following describes the communication interaction between various applications in an electronic device 100 and various servers (or server modules) in a payment cloud server 300, as provided in an embodiment of this application.

[0110] For example, Figure 2B This illustration shows a communication interaction diagram between an electronic device 100 and a payment cloud server 300, as provided in an embodiment of this application.

[0111] like Figure 2BAs shown, the electronic device 100 may have one or more payment applications installed, such as payment application A and payment application B. Each payment application may include one or more payment mini-programs, and each payment mini-program may correspond to a payment method. For example, payment application A may include payment methods such as bank card C1 and balance C2, while payment application B may include payment methods such as membership card C3.

[0112] The payment cloud server 300 may include one or more servers, such as server 310, server 320, and server 330. Each server may also include one or more sub-servers; for example, server 310 may include sub-server 311 and sub-server 312, etc.

[0113] Server 310 can be the server of payment application A, and electronic device 100 can interact with server 310 through payment application A. Specifically, sub-server 311 in server 310 can interact with the payment mini-program corresponding to bank card C1 in payment application A, and sub-server 312 can interact with the payment mini-program corresponding to balance C2 in payment application A. Furthermore, server 330 can be the server of the bank corresponding to bank card C1. When electronic device 100 interacts with sub-server 311 through the payment mini-program corresponding to bank card C1 in payment application A, it can also interact with server 330 through sub-server 311. Server 320 can be the server of payment application B. Electronic device 100 can interact with server 320 through payment application B.

[0114] Understandable, Figure 2B The embodiments shown are merely illustrative. The electronic device 100 can communicate with the server (or server module) corresponding to the payment application installed on it. In this application embodiment, the electronic device 100 may also have more, fewer, or different payment applications than those in the above embodiments. The payment cloud server 300 may also include more, fewer, or different servers than those in the above embodiments. This application does not limit the scope of the embodiments.

[0115] The following describes the device configuration of electronic device 100 and payment device 200, as well as their positional relationship when communicating based on NFC technology.

[0116] Figure 2C This illustration shows a schematic diagram of the device configuration of an electronic device 100 provided in an embodiment of this application.

[0117] like Figure 2CAs shown, the electronic device 100 may include a front and a back. The front of the electronic device 100 may have a display screen 11. Optionally, the front of the electronic device 100 may also have one or more of the following: a front-facing camera 12, an earpiece 13, etc. The back of the electronic device 100 may include an NFC area 14. Optionally, the back of the electronic device 100 may also include one or more of the following: a rear-facing camera 15, a flashlight 16, etc. When the electronic device 100 touches the payment receiving device 200, the NFC area 14 is used to make contact with the payment receiving device 200 to facilitate NFC-based communication between the electronic device 100 and the payment receiving device 200.

[0118] Understandable, Figure 2C The illustrated embodiment is merely an example. In this application embodiment, the NFC area of ​​the electronic device 100 may also be located in other locations on the electronic device 100, and this application does not limit the scope of the application. Furthermore, the electronic device 100 may be a mobile phone, a tablet computer, a wearable device, or other electronic devices, and this application does not limit the scope of the application.

[0119] Figure 2D This paper shows a schematic diagram of the device configuration of a payment collection device 200 provided in an embodiment of this application.

[0120] like Figure 2D As shown, the payment receiving device 200 can be a POS machine. The payment receiving device may include a card swiping area 201 and a display screen 202. Optionally, the payment receiving device 200 may also include a button 203. When the electronic device 100 touches or approaches the card swiping area 201 of the payment receiving device 200, NFC-based communication between the electronic device 100 and the payment receiving device 200 can be established. The display screen 202 can be used to display the amount due and to display payment success notifications, etc. In some embodiments, the areas where the card swiping area 201 and the display screen 202 are located may partially or completely overlap. The button 203 can be used for user interaction, such as outputting the amount due to the payment receiving device 200. In some embodiments, the payment receiving device 200 may not have physical buttons, but instead achieve interaction between the payment receiving device 200 and the user through touch screen operation of the display screen 202.

[0121] It is understandable that the above Figure 2D The illustrated embodiment is merely an example; in the embodiments of this application, the payment receiving device 200 may be as described above. Figure 2D The POS machine shown may also be a different device form from the above embodiments, for example, including those described above. Figure 2D The embodiments shown may contain more or fewer devices than those described above, and this application is not limited thereto.

[0122] Figure 2EThis illustration shows the positional relationship of an electronic device 100 and a payment device 200 based on NFC technology, according to an embodiment of this application.

[0123] like Figure 2E As shown, a user can touch the NFC area 14 on the back of the electronic device 100 to the card swiping area 201 of the payment device 200 to complete the contact between the electronic device 100 and the payment device 200. In this way, the electronic device 100 and the payment device 200 can communicate based on NFC technology to complete the payment.

[0124] Understandable, Figure 2E The illustrated embodiments are merely examples illustrating the positional relationship between the electronic device 100 and the payment device 200 when they are touched. In this application embodiment, if the position of the NFC area 14 or the card swiping area 201 is different from that in the above embodiments, the electronic device 100 and the payment device 200 may also communicate based on NFC technology using a different positional relationship than that in the above embodiments. This application does not limit this.

[0125] The following is a schematic diagram of the structure of an electronic device 100 provided in the embodiments of this application.

[0126] Figure 3A A schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application is shown.

[0127] like Figure 3A As shown, the electronic device 100 may include a processor 101 and an NFC module 102. The processor 101 may run one or more applications. These applications may include one or more of the following: a wallet application, one or more host-based card emulation (HCE) applications, etc. Optionally, the electronic device 100 may also include a secure element (SE) 103 and / or a subscriber identity module (SIM) card. The processor 101 may be connected to the NFC module 102, the SE 103, and the SIM card 104, respectively. The NFC module 102 may also be connected to the SE 103 and the SIM card 104.

[0128] NFC module 102 may include an NFC controller ( Figure 3A (not shown in the image), NFC transceiver ( Figure 3A (not shown in the image) and NFC memory ( Figure 3A (Not shown in the image). The NFC controller can be connected to the processor 101, and can also be connected to the NFC transceiver and the NFC memory respectively.

[0129] The NFC controller is primarily used for modulation and demodulation of contactless communication signals, controlling the input and output of data in the NFC memory, and interacting with the processor 101. The NFC transceiver is used to transmit and receive NFC signals (e.g., 13.56MHz radio frequency signals), and may include an electromagnetic compatibility (EMC) filter circuit, a matching circuit, a receiving circuit, and an NFC antenna, where the NFC antenna may be a loop antenna, used to enable proximity-based contactless communication capabilities of the NFC module 102. The NFC memory can be used to store data sent by the NFC module 102 to the payment device 200, as well as data received from the payment device 200. In some embodiments, the NFC memory can be a shared memory that can be used by the various components in the NFC module 102; for example, some data in the NFC memory can be accessed by the NFC controller, while other data can be accessed by the SE 103.

[0130] In other embodiments, the NFC memory may be a collection of multiple memories. For example, the NFC controller may include a first memory among these multiple memories. The first memory may include instructions or data that the NFC controller has used or reused. If the NFC controller needs to use the instruction or data again, it can directly retrieve it from the first memory, thus reducing the waiting time of the NFC controller. SE103 may include a second memory among these multiple memories. The second memory may include card information such as that of the NFC emulator based on the secure element. Thus, if SE103 needs to read the card information of the NFC emulator, it can read the card information of the NFC emulator from the second memory in SE103. SIM card 104 may include a third memory among these multiple memories. The third memory may include card information such as that of the NFC emulator based on the SIM card. Thus, if SIM card 104 needs to read the card information of the NFC emulator, it can read the card information of the NFC emulator from the third memory in SIM card 104.

[0131] In some embodiments, the NFC memory described above may also store routing information. In some embodiments, this routing information may be controlled or managed by the NFC controller, and may include a routing table consisting of a list of routing rules. Each routing rule contains an applet identifier (AID) and a destination; the destination is the location where the applet used to implement the business logic of the NFC emulator card runs. The destination may include an HCE application running in the processor 101 of the electronic device 100, or an SE 103 or SIM card 104 connected to the NFC controller.

[0132] The SE103 and NFC module 102 can be two separate chips. Alternatively, the SE103 and NFC module 102 can be packaged into a single chip.

[0133] Electronic device 100 can activate one or more NFC emulator cards in an application based on user input, thereby enabling electronic device 100 to support one or more NFC services. The specific business processing logic of the NFC emulator card in electronic device 100 is implemented by an applet. The applet can be stored and run in the corresponding hardware device or software module (e.g., HCE application, SIM card, SE, etc.) of the NFC emulator card.

[0134] The card emulation modes of electronic device 100 can be divided into hardware-based virtual card mode and software-based HCE mode. Among them,

[0135] 1. In hardware-based virtual card mode, electronic device 100 can provide the operating environment for the Applet corresponding to the NFC emulator card, as well as the storage and processing of the NFC emulator card's business data, through SE103 or SIM card 104. NFC module 102, as the front end of contactless communication, receives commands from the external PCD and forwards them to SE103 or SIM card 104. The Applet in SE103 or SIM card 104 then processes the commands and sends response data to the external PCD via NFC module 102. Users can activate one or more NFC emulator cards in a wallet application, which can write the Applets and card data of one or more NFC emulator cards into SE103. Alternatively, users can activate one or more NFC emulator cards in a SIM card application, which can write the Applets and card data of one or more NFC emulator cards into SIM card 104 for storage.

[0136] 2. In software-based HCE mode, the HCE application running in processor 101 can provide the operating environment for the Applet corresponding to the NFC emulator card, as well as the storage and processing of the NFC emulator card's business data. After receiving a command from an external PCD, NFC module 102 can send the command to the HCE application. The HCE application can process the command received by the NFC module through the Applet running in the HCE application or a cloud server, and generate response data for the PCD. The HCE application can then send the response data to NFC module 102. NFC module 102 can then send the response data to the external PCD. Users can activate one or more NFC emulator cards in the HCE application. The HCE application can run one or more NFC emulator card Applets and store the NFC emulator card data on the local memory of electronic device 100 or on a cloud server.

[0137] Optionally, the processor 101 can also run an NFC basic service module. The NFC basic service module can be used to provide common management functions for one or more NFC services. These common management functions may include file management, card activation, security management, service routing management, and other functions.

[0138] For example, in the card emulation scenario described above, the electronic device 100 has a native NFC-related application installed, and users can also download and install third-party applications from app stores. Generally, the native application can use a hardware-based virtual card solution, while the third-party application can use an HCE solution. The native application can be a wallet application, etc., and the third-party application can be, for example, a ticketing application, a payment application, etc. The above examples are merely for explaining this application and should not be construed as limiting it.

[0139] The following describes an NFC protocol stack provided in an embodiment of this application.

[0140] Figure 3B This illustration shows a layered architecture diagram of an NFC protocol stack provided in an embodiment of this application.

[0141] like Figure 3B As shown, the NFC protocol stack can include a physical layer, a radio frequency layer, an access layer, a transport layer, and an application layer.

[0142] The physical layer can be used to implement the physical characteristics of NFC technology communication.

[0143] The radio frequency (RF) layer can be used to implement RF specifications for NFC technology communication, such as data rate and RF signal frequency.

[0144] The access layer can be used to implement functions such as polling and device discovery, service result notification, card conflict management, transmission protocol negotiation, timeout and retransmission mechanism, PICC / PCD mode switching, and converged card selection.

[0145] The transport layer includes a high-speed data transmission protocol, which enables data transmission between the PCD and PICC at the application layer.

[0146] The application layer can be used to implement one or more NFC services and one or more service management policies. The one or more NFC services may include codeless payment, electronic tickets, access control, digital ID cards, all-scenario contactless payment, and short-range data transmission. The one or more service management policies may include any one or more of the following: file management, card long-term activation, security management, and service routing management. The processing logic of the NFC services can be executed by Applets. In one possible implementation, the processing logic of the service management policies can be executed by the NFC basic service module.

[0147] In the embodiments of this application, the above Figure 3B The NFC protocol stack shown can be referred to as the first protocol stack.

[0148] This application provides a payment method whereby, when an electronic device 100 enters a geofence A1, it can obtain merchant discount information 1 for geofence A1 from a payment cloud server 300. Merchant discount information 1 includes promotional activities from one or more merchants within geofence A1. The electronic device 100 can output merchant discount information 1 to allow users to check nearby merchants' promotional activities in real time. If a user makes a purchase at one of these merchants, during the payment process, the electronic device 100 can communicate with a payment receiving device 200 based on NFC technology to determine the payment method and the actual payment amount based on the merchant discount information 1, thus completing the payment.

[0149] In this way, users can check the promotional activities of nearby merchants in real time, and complete the payment based on the merchants' promotions, saving users money and increasing the merchants' customer traffic.

[0150] The following describes the interface for pushing promotional information to users after a set of electronic devices 100 enters the geofence A1, as provided in this application embodiment.

[0151] In some application scenarios, after electronic device 100 enters geofence A1, it can display promotional activities of one or more merchants within geofence A1 when the user views the negative one screen (or other designated interface). This allows users to proactively obtain promotional information from nearby merchants and decide whether to shop at the corresponding merchants based on these promotions, while also increasing merchant exposure and customer traffic.

[0152] For example, electronic device 100 can display as follows Figure 4A The desktop 400 is shown. Desktop 400 displays a page with application icons, including multiple application icons (e.g., weather app icon, settings app icon, browser app icon, etc.). Below the page with application icons, a page indicator 402 is displayed to indicate the total number of pages on the desktop and the positional relationship between the currently displayed page and other pages. For example, desktop 400 may include three pages; the black dot in the page indicator, located at the first position from the left, indicates that the currently displayed page is the first page from the left among the three pages. Optionally, a status bar 401 is displayed above the page with application icons, which may include information such as signal strength indicator, battery level, and time. Further optionally, a tray area 403 may be present below the page indicator, which may include one or more tray icons (e.g., dialer app icon, messaging app icon, contacts app icon, camera app icon, etc.). These tray icons may remain visible when switching pages.

[0153] Electronic device 100 can receive and respond to a user's right swipe operation on desktop 400. After detecting that electronic device 100 has entered geofence A1, electronic device 100 can display as follows: Figure 4B The negative one screen interface 410 is shown.

[0154] like Figure 4BAs shown, the negative one screen interface 410 can include one or more nearby recommendation options, such as AAA Convenience Store option 411, BBB Mall option 412, and CCC Supermarket option 413, etc. Each nearby recommendation option corresponds to a merchant's promotional activities within the geofence (i.e., geofence A1) where the electronic device 100 is located. For example, AAA Convenience Store option 411 can display promotional activities of AAA Convenience Store within geofence A1. AAA Convenience Store's promotional activities can include discounted items and discount rules. Discounted items can be PP1 products, and the discount rule can be "20% off for two items". Optionally, AAA Convenience Store option 411 can also display the distance between AAA Convenience Store and electronic device 100, i.e., "distance 786m". Similarly, BBB Mall option 412 can display promotional activities of BBB Mall within geofence A1. BBB Mall's promotional activities can include discount rules, such as "10% off everything". Optionally, BBB Mall option 412 can also display the distance between BBB Mall and electronic device 100, i.e., "distance 502m". For example, the CCC Supermarket option 413 can display promotional activities for the CCC Supermarket within the geofence A1. These promotions can include a payment method identifier (e.g., "Payment Application A") and a discount rule (e.g., "5 off for every 50 yuan spent"). Optionally, the CCC Supermarket option 413 can also display the distance between the CCC Supermarket and the electronic device 100, i.e., "distance 823m". Optionally, the negative one screen interface 410 can also include a quick function bar 414 and a search bar 415. The quick function bar 414 can include one or more quick function controls, which can be used to trigger the electronic device 100 to launch corresponding quick functions, such as scanning, payment, or memo functions. The search bar 415 can be used to trigger the electronic device 100 to initiate a search based on user input.

[0155] In other application scenarios, after electronic device 100 enters geofence A1, it pushes promotional notifications to inform the user that one or more merchants nearby are offering discounts. Electronic device 100 can receive and respond to the user's actions regarding the notifications, displaying the promotional activities of one or more merchants within geofence A1. In this way, when electronic device 100 enters geofence A1, it can push promotional activities to the user, allowing the user to decide whether to shop at the corresponding merchant based on the promotion, and also increasing the merchant's exposure and customer traffic.

[0156] For example, when electronic device 100 enters geofence A1, electronic device 100 may display as follows: Figure 4C The promotional notification interface shown is 420.

[0157] like Figure 4C As shown, the promotion notification interface 420 may include a promotion notification 421, which can be used to notify the user that there are one or more promotional activities within the geofence A1 where the electronic device 100 is currently located. For example, the promotion notification 421 may include the text "One or more promotional activities are nearby". Optionally, the promotion notification 421 may also include the operation instruction text "Click to view", which can be used to guide the user to view the specific content of the promotional activities.

[0158] Electronic device 100 can receive and respond to a user's click on the offer notification 421, displaying one or more offers within the geofence A1, such as displaying... Figure 4B The negative one screen interface 410 is shown.

[0159] It is understandable that the above Figures 4A-4C The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 may also display the discount information on other interfaces. In addition, the electronic device 100 may also display the discount information in a different manner than the embodiments described above. This application does not limit this.

[0160] Figure 4D-Figure 4G This paper illustrates a schematic diagram of the interface of a set of electronic devices 100 performing a payment method according to an embodiment of this application.

[0161] For example, such as Figure 4D As shown, the electronic device 100 can be in a screen-off state or a screen-on state. When the electronic device 100 enters the radio frequency field of the payment device 200, the electronic device 100 can display as shown in the image. Figure 4E The payment method selection interface 430 shown includes one or more payment options.

[0162] like Figure 4EAs shown, the payment method selection interface 430 can include one or more payment options. These options can be displayed in the interface according to the amount of the discount, for example, from top to bottom, options such as AA Bank Card 431, Payment Application A 432, and Payment Application B 433. This allows users to easily determine the most favorable payment option based on the order of the options. Each payment option can correspond to one payment method; for example, AA Bank Card option 431 corresponds to payment via AA Bank Card, Payment Application A option 432 corresponds to payment via Payment Application A, and Payment Application B option 433 corresponds to payment via Payment Application B. Each payment option can include an amount prompt, which can be used to indicate the actual payment amount and / or discount amount corresponding to that payment option to the user. For example, option 431 (AA Bank Card) may include an amount prompt 431a, which indicates to the user that the actual payment amount when using AA Bank Card is 45 yuan, with a discount of 5 yuan. Option 432 (Payment Application A) may include an amount prompt 432a, which indicates to the user that the actual payment amount when using Payment Application A is 48 yuan, with a discount of 2 yuan. Option 433 (Payment Application B) may include an amount prompt 433a, which indicates to the user that the actual payment amount when using Payment Application B is 49 yuan, with a discount of 1 yuan. Furthermore, each payment option may include a selection indicator; for example, option 431 (AA Bank Card) includes a selection indicator 431b, option 432 (Payment Application A) includes a selection indicator 432b, and option 433 (Payment Application B) includes a selection indicator 433b. Each selection indicator includes a selected state and an unselected state, indicating whether the corresponding payment option is selected. The selection indicator may have two states: selected and unselected. In some embodiments, the electronic device 100 can indicate the two states of the selection indicator through different display colors. For example, selection indicator 431b is filled with black, while other selection indicators are not filled, indicating that the AA bank card option 431 is selected and the other options are not selected. It is understood that in this embodiment, different selection indicators than those described above can also be used to indicate whether an option is selected, and this application does not limit this. The payment method selection interface 430 may also include a payment confirmation control 434, which can be used to trigger the electronic device 100 to complete payment based on the currently selected payment option.

[0163] In some embodiments, the electronic device 100 may receive and respond to a user's click on the payment confirmation control 434, displaying, for example... Figure 4F The payment verification prompt shown is 440.

[0164] like Figure 4F As shown, payment verification prompt 440 can be used to prompt users to perform payment verification. Payment verification prompt 440 may include payee 442, amount due 443, actual amount paid 444, payment method 445, and fingerprint verification prompt 446. Payee 442 can be used to prompt the user about the payee's account (e.g., the payee's account number), making it easier for the user to verify the payee's identity. Amount due 443 indicates the amount due. Actual amount paid 444 indicates the amount actually paid. Payment method 445 indicates the current payment method, such as "AA Bank Savings Card". Furthermore, before performing payment verification, the user can check whether the information displayed in payment verification prompt 440, such as payee 442, amount due 443, actual amount paid 444, and payment method 445, is correct. Fingerprint verification prompt 446 can be used to prompt the user to complete payment verification via fingerprint verification. Optionally, the payment verification prompt 440 may also include one or more of the following: a payment method switching control 447 and a verification method switching control 441. The payment method switching control 447 can be used to trigger the electronic device 100 to switch the current payment method. The verification method switching control 441 can be used to trigger the electronic device 100 to switch the current payment verification method.

[0165] In some embodiments, after detecting that a user has completed fingerprint verification in the fingerprint recognition area, the electronic device 100, such as Figure 4G As shown, electronic device 100 can display a payment success message 450.

[0166] like Figure 4G As shown, the payment success notification 450 can be used to notify the user that the payment has been successful. The payment success notification 450 may include one or more of the following: payee 452, amount due 453, actual payment amount 454, discount amount 455, payment method 456, completion control 451, etc. Among them, payee 452 can be used to notify the user of the payee's account (e.g., the payee's account number), which facilitates the user's verification of the payee's correctness. Amount due 453 is used to notify the user of the amount due. Actual payment amount 454 is used to notify the user of the amount actually paid. Discount amount 455 is used to notify the user of the discount amount; the sum of the discount amount and the actual payment amount is the amount due. Optionally, discount amount 455 can also indicate the user of specific promotional activities, such as "XX Bank offers a discount of 5 yuan off for purchases over 45 yuan." Payment method 456 can be used to indicate the currently used payment method, such as "AA Bank savings card," etc. In some embodiments, the completion control 451 is used to trigger the electronic device 100 to stop displaying the payment success notification 450.

[0167] It should be noted that, in some embodiments, when the electronic device 100 enters the radio frequency field of the payment device 200, the electronic device 100 can also directly determine the most favorable payment method based on the merchant's promotional activities and display it as shown below. Figure 4F The payment verification prompt 440 is shown. In some other embodiments, if the electronic device 100 has enabled the password-free payment function, the electronic device 100 may not display the payment verification prompt again, but may directly display something like... Figure 4G The payment success message shown is 450.

[0168] It is understandable that the above Figure 4D-Figure 4G The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 may also complete the payment in a different manner than the above embodiments, such as displaying different payment options, displaying different payment verification prompts or payment success prompts, etc. This application does not limit this.

[0169] The following describes the specific process of a payment method provided in an embodiment of this application.

[0170] Figure 5 A flowchart illustrating a payment method provided in an embodiment of this application is shown.

[0171] like Figure 5 As shown, the specific process of a payment method provided in this application embodiment may include the following steps:

[0172] S501. Electronic device 100 obtains merchant discount information 1.

[0173] Merchant promotion information 1 can include promotional activities from one or more merchants.

[0174] In some embodiments, merchant discount information 1 may include discount activities of one or more merchants within a specific area (e.g., geofence A1), and the specific details of the discount activities of the one or more merchants can be found in the relevant descriptions in the embodiments shown in Table 2 below.

[0175] In other embodiments, merchant offer information 1 may also include promotional activities of one or more merchants within multiple adjacent geofences.

[0176] In one possible implementation, the electronic device 100 can obtain merchant discount information 1 when entering a designated area (e.g., geofence A1). For example, taking the example that merchant discount information A1 includes promotional activities of one or more merchants within geofence A1, the specific method by which the electronic device 100 obtains merchant discount information 1 can be referred to below. Figure 6 The relevant descriptions in the illustrated embodiments will not be detailed here.

[0177] In another possible implementation, the electronic device 100 may also obtain merchant discount information 1 during the interaction with the payment device 200.

[0178] S502. Electronic device 100 enters the radio frequency field of receiving device 200.

[0179] S503. The receiving device 200 sends a probe frame to the electronic device 100.

[0180] The Probe frame can be used to indicate that the receiving device 200 supports a specified NFC protocol, such as the first protocol. In some embodiments, the receiving device 200 may periodically send Probe frames.

[0181] S504. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0182] The Probe ACK can be used to indicate that the electronic device 100 supports the specified NFC protocol (e.g., the first protocol) indicated by the Probe frame.

[0183] If the electronic device 100 does not support the specified NFC protocol indicated by the Probe frame (e.g., the first protocol), the electronic device 100 may not send a Probe ACK frame.

[0184] S505. After receiving the Probe ACK frame, the payment device 200 sends a Pick frame. The Pick frame carries the device characteristic information of the payment device 200, which is used to indicate that the service type of the payment device 200 is codeless payment.

[0185] The device characteristic information may include the service identifier (SID) and the device organization identifier (also known as the NFC device organization unique identifier (ND_OUI)).

[0186] Optionally, device characteristic information may include Service Identifier (SID), Device Organization Identifier (ND_OUI), and Device Group Identifier (also known as NFC Device Group Identifier (ND_GID)).

[0187] 1. The Service Identifier (SID) can be used to indicate the type of NFC service supported by the payment device 200 on the basis of NFC functionality.

[0188] In one possible implementation, the NFC service type may include a primary service type and a sub-service type. Therefore, the service identifier may include a primary service identifier and a sub-service identifier. The primary service identifier can be used to indicate the primary service type supported by the payment device 200, and the sub-service identifier can be used to indicate the sub-service types supported by the payment device 200 under a certain primary service type. The primary service type may include code-free payment; optionally, the primary service type may also include one or more of the following: access control, keys, transportation, banking, digital currency, digital certificates, electronic tickets, wireless charging, contactless payment, multi-function cards, etc. The sub-service types corresponding to code-free payment may include general services, membership card discount services, payment institution discount services, etc.

[0189] The main service identifier can occupy 1 byte, and the sub-service identifier can occupy 1 byte. For example, Table 1 shows the correspondence between the device main service identifier, the device sub-service identifier, and the sub-service type when the main service type is codeless payment, according to an embodiment of this application.

[0190] Table 1

[0191]

[0192] As shown in Table 1, when the main service type is codeless payment, the device main service identifier can be 0x07; if the sub-service type is general service, the device sub-identifier can be 0x01; if the sub-service type is payment discount service (including payment institution discount service and / or membership card discount service), the device sub-identifier can be 0x02; if a new sub-service type needs to be added, an unused identifier can be selected from the reserved identifiers, namely 0x00, 0x03 to 0xFF, as the device sub-service identifier corresponding to the new sub-service type.

[0193] It is understood that the embodiments shown in Table 1 are only examples. In the embodiments of this application, the device service identifier may also adopt a different identifier than the above embodiments. In addition, code-free payment may also include more, fewer or different sub-service types and device sub-service identifiers than the above embodiments. This application does not limit this.

[0194] As can be seen from the above embodiments, in this application embodiment, the Pick frame sent by the payment receiving device 200 may carry a device service identifier for indicating codeless payment, such as 0x07 as shown in Table 1 above. Optionally, it may also carry a device sub-service identifier for indicating the sub-service type of the payment receiving device 200. Since in step S505, the device feature information is used to indicate that the service type of the payment receiving device 200 is codeless payment, the device main service identifier that can be carried in the Pick frame may be 0x07 as shown in Table 1 above. In this way, the service type of the payment receiving device 200 can be indicated by the device service identifier in the device feature information.

[0195] 2. The Device Organization Identifier (ND_OUI) can be used to indicate the manufacturer providing NFC services using the payment device 200, such as Merchant A, Convenience Store B, Vending Machine C, etc. The NFC protocol standards organization's registration management agency can assign different Device Organization Identifiers to different manufacturers.

[0196] 3. The Device Group Identifier (ND_GID) can be used to indicate the group to which the NFC services provided by the payment device 200 belong. The Device Group Identifier can be assigned based on the purpose and location of the payment device 200. Different NFC services can be assigned to different groups.

[0197] S506. Electronic device 100 determines the service type as codeless payment based on the device feature information of payment device 200.

[0198] In some embodiments, electronic device 100 may determine that the service type of payment device 200 is codeless payment based on the device service identifier of payment device 200.

[0199] S507. Electronic device 100 sends a Pick ACK frame.

[0200] In some embodiments, after determining the service type of the receiving device 200, the electronic device 100 may send a Pick ACK frame to the receiving device 200. The Pick ACK frame can be used to indicate that the electronic device 100 has determined the NFC service type of the receiving device 200.

[0201] S508. The payment device 200 sends a payment request 1, which includes the amount due, the merchant ID, and / or an identifier of one or more payment methods supported by the payment device 200.

[0202] The amount payable refers to the amount that the merchant should collect, as determined by the payment collection device 200 based on the actual goods purchased by the user.

[0203] In some embodiments, the merchant ID can be used to obtain the payment methods supported by the payment device 200.

[0204] S509. Electronic device 100 determines one or more promotional activities of merchant 1 from merchant promotional information 1 based on merchant ID, where merchant 1 is the merchant to which the payment receiving device 200 belongs.

[0205] S510. Electronic device 100 determines payment method 1 from one or more payment methods supported by one or more payment collection devices 200 based on one or more promotional activities of merchant 1.

[0206] When the service type of the receiving device 200 is determined to be a general service in codeless payment, the electronic device 100 can accept and respond to the payment request 1, determine one or more payment methods supported by both the electronic device 100 and the receiving device 200 from among the payment methods supported by one or more receiving devices 200, and determine the payment method with the highest priority from among the payment methods supported by one or more electronic devices 100 and the receiving device 200 based on the priority of the payment methods preset by the electronic device 100. The payment method with the highest priority is payment method 1.

[0207] S511. Electronic device 100 determines the payment voucher 1, the actual amount paid 1, and the payment authorization 1 for payment method 1, wherein the payment voucher 1 is used to instruct the payment account 1 for payment method 1.

[0208] In this embodiment, the payment authorization may include a password-free payment authorization and a verification payment authorization. The password-free payment authorization is used to authorize the receiving end to deduct funds from a designated payment account in a password-free payment scenario. The verification payment authorization is used to authorize the receiving end to deduct funds from a designated payment account in a non-password-free payment scenario. The verification payment authorization can be obtained after the electronic device 100 detects that the user has completed payment verification (i.e., the user's identity verification is successful).

[0209] In step S511, payment permission 1 can be either a password-free payment permission or a verification payment permission. If payment permission 1 is a verification payment permission, the electronic device 100 can obtain payment permission 1 after detecting that the user has completed payment verification (i.e., the user's identity verification is successful).

[0210] S512. Electronic device 100 sends payment response 1, which includes payment credential 1 and payment authorization 1.

[0211] In one possible implementation, the electronic device 100 may send a payment response 1 carrying the payment credential 1 and payment authorization 1 to the receiving device 200 after obtaining the payment credential 1 and payment authorization 1.

[0212] In another possible implementation, electronic device 100 can send payment credential 1 to receiving device 200 after obtaining payment credential 1; and then send payment authorization 1 to receiving device 200 after obtaining payment authorization 1. That is, electronic device 100 can also send payment response 1 through multiple communications. For example, in the case of non-password-free payment, electronic device 100 can first send payment credential 1 to receiving device 200 based on NFC technology. If electronic device 100 leaves the radio frequency field of receiving device 200 when the user completes payment verification, then after detecting that the user has completed payment verification, electronic device 100 can re-enter the radio frequency field of receiving device 200 and send payment authorization 1 to receiving device 200 based on NFC technology.

[0213] Optionally, payment response 1 may also include the actual amount paid.

[0214] S513. The receiving device 200 deducts funds from the payment account 1 based on the payment voucher 1 and the payment license 1, and the deduction amount is the actual payment amount 1.

[0215] The specific method by which the payment device 200 deducts funds from the payment account 1 based on payment voucher 1 and payment license 1 can be found below. Figure 7 or Figure 8 The relevant steps in the illustrated embodiment will not be described in detail here.

[0216] Understandable, Figure 5 The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 and the payment device 200 may use different interaction steps than those in the above embodiments to complete the payment. This application does not limit the scope of the embodiments.

[0217] The payment method provided in this application can simplify the payment process and improve payment efficiency.

[0218] In some embodiments, merchant offer information 1 may include promotional activities of one or more merchants within geofence A1. Electronic device 100 may obtain merchant offer information 1 when entering geofence A1.

[0219] For example, Figure 6 This illustration shows a flowchart of an electronic device 100 obtaining merchant discount information 1 according to an embodiment of this application.

[0220] like Figure 6 As shown in the figure, the specific process of an electronic device 100 obtaining merchant discount information 1 provided in this application embodiment may include the following steps:

[0221] S601. Electronic device 100 detected entry into geofence A1.

[0222] Electronic device 100 has a positioning function, through which it can obtain either fuzzy or precise positioning. Precise positioning has higher accuracy than fuzzy positioning. Based on the obtained fuzzy / precise positioning, electronic device 100 can determine whether it has entered the geofence A1.

[0223] In this embodiment, a geofence is a virtual boundary created around an area using a Global Positioning System (GPS) satellite network and / or local radio frequency identifiers (such as Wi-Fi nodes or Bluetooth beacons). A geofence can be paired with a designated hardware / software application that can respond to the boundary in a certain way according to program parameters. For example, when electronic device 100 crosses the virtual boundary of geofence A1 and enters the area enclosed by geofence A1, the application can detect that electronic device 100 has entered geofence A1; when electronic device 100 crosses the virtual boundary of geofence A1 and leaves the area enclosed by geofence A1, the application can detect that electronic device 100 has left geofence A1.

[0224] S602. Electronic device 100 determines the precise location of electronic device 100 as position 1.

[0225] Step S602 is an optional step.

[0226] In some embodiments, after the electronic device 100 obtains the fuzzy location of the electronic device 100 and determines that the electronic device 100 has entered the geofence A1 based on the fuzzy location, the electronic device 100 can execute step S602.

[0227] After obtaining the precise location of electronic device 100 (i.e., location 1), electronic device 100 may optionally determine whether it has entered geofence A1 based on location 1. If location 1 is within the area enclosed by geofence A1, then electronic device 100 has entered geofence A1; if location 1 is not within the area enclosed by geofence A1, then electronic device 100 has not entered geofence A1. This allows for a more accurate determination of whether electronic device 100 has entered geofence A1, improving the accuracy of the determination and avoiding misjudgments.

[0228] S603. Electronic device 100 sends a discount information request 1 to payment cloud server 300, the discount information request 1 including location 1 and / or geofence A1.

[0229] The "Promotion Information Request 1" can be used to request the payment cloud server 300 to send merchant promotion information 1 corresponding to geofence A1. Merchant promotion information 1 can include promotional activities of one or more merchants within geofence A1. For details of the promotional activities, please refer to the relevant description in step S604 below.

[0230] S604. The payment cloud server 300 sends merchant discount information 1 to the electronic device 100. Merchant discount information 1 includes discount activities of one or more merchants within the geofence A1.

[0231] The payment cloud server 300 can store one or more geofences and corresponding merchant discount information. The merchant discount information for each geofence can include promotional activities from one or more merchants within that geofence. The merchant discount information can include a merchant identifier (ID) and a discount activity. In some embodiments, the discount activity can include discount rules; optionally, the discount activity can also include one or more of the following: product identifier and payment method identifier. Each merchant can include one or more discount activities, which can be used to determine the discount amount. The discount amount of the discount activity can be related to the payment method, the merchant, or the purchased goods and their quantity; this application does not limit this.

[0232] For example, Table 2 shows the correspondence between geofences and discount information stored in a payment cloud server 300 provided in an embodiment of this application.

[0233] Table 2

[0234]

[0235] As shown in Table 2, the payment cloud server 300 can store one or more geofences and corresponding promotional information. Promotional information may include merchant IDs and promotional activities. Promotional activities may include product identifiers, payment method identifiers, and one or more discount rules. For example, the payment cloud server 300 can store promotional information for geofence A1 and geofence A2. According to Table 2, the promotional information for geofence A1 may include promotional activities for merchant NO.1 and merchant NO.2. Merchant NO.1's promotional activities may include two activities. The first activity may include the product identifier "Product P1" and the discount rule "Buy two, get 20% off," meaning that if product P1 is purchased in quantities of 2 or more, the price of product P1 will be discounted by 20% regardless of the payment method. The second activity may include the payment method identifier "Payment Method 1" and the discount rule "Spend 50, get 5 off," meaning that if payment method 1 is used, regardless of the product purchased, a discount of 5 yuan will be applied for every 50 yuan of the total price. Merchant NO.2's promotional activities may include the product label "Product P2", the payment method label "Payment Method 2", and the discount rule "¥5 off for every ¥20 spent". This means that if you purchase Product P2 and use Payment Method 2, you can get a ¥5 discount for every ¥20 spent on Product P2. Geofencing A2's promotional information may include Merchant NO.3's promotional activities. Merchant NO.3's promotional activities may include the discount rule "10% off everything", indicating that regardless of the product purchased or the payment method used, as long as the purchase is made at Merchant NO.3, the total price of the product will be discounted by 10%.

[0236] It is understood that the embodiments shown in Table 2 above are only examples. In the embodiments of this application, the payment cloud server 300 may also store more, fewer, or different geofences and corresponding discount information than the above embodiments, and the discount information may also be different from the above embodiments. This application does not limit this.

[0237] In one possible implementation, after receiving the discount information acquisition request 1, the payment cloud server 300 can determine the geofence where the electronic device 100 is located as geofence A1 based on the location 1 and / or geofence A1 in the discount information acquisition request 1, and determine the merchant discount information 1 corresponding to geofence A1 based on geofence A1.

[0238] After determining the merchant discount information 1 corresponding to geofence A1, the payment cloud server 300 can send the merchant discount information 1 to the electronic device 100.

[0239] S605. Electronic device 100 displays merchant discount information 1.

[0240] Step S605 is an optional step.

[0241] In some embodiments, after receiving merchant discount information 1, the electronic device 100 may display merchant discount information 1.

[0242] For example, the interface on which the electronic device 100 displays merchant discount information 1 can refer to the above. Figure 4B The negative one screen interface 410 in the illustrated embodiment.

[0243] In this way, the electronic device 100 can obtain and display the merchant's promotional information corresponding to the geofence when it enters the geofence, making it easier for users to choose whether to make a purchase and increasing customer traffic for merchants. Furthermore, users can make payments based on the merchant's promotional information, saving on shopping expenses.

[0244] It should be noted that after receiving the payment credential sent by the electronic device 100, the payment receiving device 200 can deduct funds from the payment account indicated by the payment credential through the payment cloud server 300. When deducting funds based on the payment credential, the payment cloud server 300 also needs to obtain the payment authorization corresponding to the payment account. The payment authorization can include password-free payment authorization and verification payment authorization; the specific functions of these two types of authorization can be found above. Figure 5 The relevant descriptions in the illustrated embodiments.

[0245] In some application scenarios, the payment cloud server 300 can determine whether to obtain payment verification permission from the electronic device 100 based on whether the current payment account can use password-free payment in this payment. The specific interaction process is as follows. Figure 7 The relevant descriptions in the illustrated embodiments.

[0246] Figure 7 This illustration shows a flowchart of a payment account deduction process provided by an embodiment of this application.

[0247] like Figure 7 As shown, electronic device 100 may include payment application set 11, and the specific process of payment device 200 deducting funds from the payment account indicated by the payment credential sent by electronic device 100 may include the following steps:

[0248] S701. The receiving device 200 sends payment information 1 to the payment cloud server 300. The payment information 1 includes the payment amount, payment voucher and receiving account.

[0249] After receiving the payment credential sent by the electronic device 100, the receiving device 200 can send payment information 1 to the server (or server module) in the payment cloud server 300 corresponding to the payment method corresponding to the payment credential, based on the payment method corresponding to the payment credential. The payment information 1 may include the payment credential, the payment amount, and the receiving account. Optionally, the payment information 1 may also include an identifier of the payment method.

[0250] The payment voucher indicates the payment account for which payment is made. The receiving account is the account used by the merchant of the POS device 200 to receive payments. The payment amount may include the amount due and / or the amount actually paid, and optionally, a discount amount. The amount due refers to the amount the receiving account should receive, the amount actually paid refers to the amount deducted from the payment account, and the discount amount may be the difference between the amount due and the amount actually paid.

[0251] S702. Payment Cloud Server 300 determines whether the payment account indicated by the payment credential has enabled password-free payment.

[0252] If the payment account has enabled password-free payment, the payment cloud server 300 can perform the following step S703.

[0253] If the payment account has not enabled password-free payment, the payment cloud server 300 can perform the following step S704.

[0254] S703. Payment cloud server 300 determines whether the actual payment amount is greater than the preset password-free payment amount.

[0255] The payment cloud server 300 can determine the actual payment amount of the payment account based on the payment amount in payment information 1.

[0256] If the actual payment amount is greater than the amount of the password-free payment, the payment cloud server 300 can execute the following step S704.

[0257] If the actual payment amount is less than or equal to the amount of the password-free payment, the payment cloud server 300 can execute the following step S706.

[0258] S704. Payment cloud server 300 sends a payment verification request to payment application set 11.

[0259] It should be noted that, in this embodiment of the application, the payment application set 11 may include one or more applications with payment functions (also called payment applications), and each payment application may manage one or more mini programs with payment functions (also called payment mini programs), and each payment mini program may be regarded as a payment method.

[0260] In some embodiments, a payment verification request is used to request a user to perform payment verification. In other embodiments, a payment verification request may also be used to request the electronic device 100 to send a payment authorization verification message to the payment cloud server 300.

[0261] In this way, the security of users' assets can be improved in scenarios where payment is not made without a password, or in scenarios where the payment amount is greater than the amount for a password-free payment.

[0262] S705. Payment Application Set 11 receives and responds to the user's payment verification operation, and sends a verification payment permission to the payment cloud server 300.

[0263] Users can complete payment verification through one or more methods such as facial recognition, fingerprint, and password.

[0264] The payment verification license is used to authorize the payment cloud server 300 to deduct funds from the payment account indicated by the payment credential.

[0265] S706. The payment cloud server 300 deducts funds from the payment account indicated by the payment voucher based on payment information 1, and the deducted amount is the actual amount paid.

[0266] In scenarios involving password-free payments where the actual payment amount is less than or equal to the password-free payment amount, the payment cloud server 300 can directly deduct the payment based on the payment information. This allows payments to be completed even when the electronic device 100 is offline.

[0267] In non-password-free payment scenarios, and in scenarios where the actual payment amount is greater than the password-free payment amount, the payment cloud server 300 can receive and respond to the payment permission sent by the payment application set 11, and deduct the amount based on the payment information.

[0268] After executing step S706, the payment cloud server 300 can execute steps S707 and S709 in parallel, or execute steps S707 and S709 sequentially. This application embodiment does not limit the execution order of steps S707 and S709.

[0269] S707. Payment cloud server 300 transfers funds to the receiving account. The receiving amount includes the actual payment amount and the discount amount.

[0270] In some embodiments, the payment cloud server 300 can determine the promotional activity corresponding to the current payment method based on the payment method, and then determine the discount amount.

[0271] In other embodiments, payment information 1 may contain a discount amount, or it may contain both the amount due and the amount actually paid. In this case, payment cloud server 300 can determine the discount amount based on payment information 1. Optionally, before transferring funds to the receiving account, payment cloud server 300 may verify the discount amount based on the discount activities for this payment method stored in its own database, and only transfer funds to the receiving account after confirming that the verification is correct.

[0272] S708. Payment cloud server 300 sends payment notification 1 to payment receiving device 200.

[0273] Payment Notification 1 is used to notify the payment device 200 that the receiving account has received a specified amount of money. Payment Notification 1 may include the amount received, and optionally, may also include any one or more of the following: payment account, receiving account, arrival time, actual payment amount, discount amount, etc.

[0274] S709. Payment cloud server 300 sends payment notification 1 to payment application set 11.

[0275] After executing step S706, the payment cloud server 300 can then execute step S709.

[0276] Payment notification 1 is used to notify electronic device 100 that payment has been deducted.

[0277] Payment notification 1 may include the actual amount paid, and optionally, may also include one or more of the following: amount due, discount amount, receiving account, payment time, etc.

[0278] In this way, the payment receiving device 200 can interact with the payment cloud server 300 based on the payment credentials to complete the payment.

[0279] It is understandable that the above Figure 7 The embodiment shown is only an example. In this application embodiment, the payment receiving device 200 can also complete the payment in other ways, such as through the merchant back-end server and the payment cloud server 300 to complete the above-mentioned interaction process. This application does not limit it here.

[0280] In some application scenarios, after identifying the payment account, the electronic device 100 can also determine the method and timing for sending payment authorization to the payment cloud server 300 based on whether the payment account can use password-free payment in this payment. In the case of password-free payment, the electronic device 100 can send payment credentials and password-free payment authorization to the payment cloud server 300 through the receiving device 200. In the case of non-password-free payment, the electronic device 100 can send a verification payment authorization to the payment cloud server 300. Specific interaction methods are as follows. Figure 8 The illustrated embodiment.

[0281] For example, taking payment application A as the payment application corresponding to a specific payment method, Figure 8 This illustration shows a payment process diagram after the payment method is determined, according to an embodiment of this application.

[0282] like Figure 8 As shown, the electronic device 100 may include an NFC service module 12 and a payment application A. An embodiment of this application provides a payment process after determining the payment method, which may include the following steps:

[0283] S801.NFC service module 12 sends a payment notification to payment application A, which includes the identifier of the payment method and the actual amount paid.

[0284] In this embodiment of the application, the NFC service module 12 may include the above-mentioned Figure 3A The NFC module 102 and NFC basic service module in the illustrated embodiment, etc. The NFC service module 12 may also refer to the aforementioned... Figure 3B The NFC protocol stack in the illustrated embodiment. In some embodiments, step S1104, and step S1106 below, can be derived from the above... Figure 3B The access layer in the NFC protocol stack shown is responsible for executing the data received and controlling the data sent.

[0285] In one possible implementation, after the NFC service module 12 determines the payment method to be used, the NFC service module 12 can send the identifier of the payment method and the actual amount paid to the payment application (e.g., payment application A) corresponding to the payment method.

[0286] In another possible implementation, after the NFC service module 12 determines the payment method to be used, it can also send the identifier of the payment method and the amount due to the payment application (e.g., payment application A) to the payment application corresponding to that payment method. In this case, payment application A needs to determine the actual payment amount based on the identifier of the payment method and the amount due.

[0287] In another possible implementation, if payment application A has only one payment method, the NFC service module 12 may not send the identifier of the payment method.

[0288] S802. Payment application A determines whether the payment account has enabled password-free payment.

[0289] If the payment account has enabled password-free payment, payment application A can perform the following step S803.

[0290] If the payment account has not enabled password-free payment, payment application A can perform the following step S814.

[0291] S803. Payment application A determines whether the actual payment amount is greater than the preset password-free payment amount.

[0292] If the actual payment amount is less than or equal to the preset password-free payment amount, payment application A can execute the following step S804.

[0293] If the actual payment amount is greater than the preset password-free payment amount, payment application A can execute the following step S814.

[0294] S804. Payment application A sends a password-free payment authorization to NFC service module 12.

[0295] When the payment method allows for password-free payment, payment application A can send a password-free payment authorization to NFC service module 12. The password-free payment authorization is used to authorize payment cloud server 300 to deduct funds from the designated payment account, and the deduction amount is less than the preset password-free payment amount.

[0296] In some embodiments, payment application A may also send the payment account and / or actual payment amount corresponding to the payment method to NFC service module 12.

[0297] The S805.NFC service module 12 sends a payment credential and a passwordless payment authorization to the receiving device 200. The payment credential is used to indicate the payment account.

[0298] In some embodiments, the NFC service module 12 can determine the payment credentials before sending a payment notification. Optionally, it can also determine the actual amount paid.

[0299] In other embodiments, the NFC service module 12 may also receive payment credentials and / or actual payment amount sent by the payment application A after sending a payment notification.

[0300] After identifying the payment credential corresponding to the payment method and receiving the passwordless payment authorization, the NFC service module 12 can send the payment credential and the passwordless payment authorization to the receiving device 200. Optionally, the NFC service module 12 can also send the identifier of the payment method and / or the actual payment amount.

[0301] S806. The receiving device 200 sends payment information 2 to the payment cloud server 300. The payment information 2 includes the payment amount, payment voucher, receiving account, and password-free payment permission.

[0302] In this embodiment, the payment amount may include the actual amount paid and / or the amount due. The amount due is the amount that the payment receiving device 200 should collect.

[0303] S807. Payment Cloud Server 300 deducts funds from the payment account based on payment information 2, and the deducted amount is the actual amount paid.

[0304] S808. Payment cloud server 300 transfers funds to the receiving account. The receiving amount includes the actual payment amount and the discount amount.

[0305] S809. Payment cloud server 300 sends a payment notification 2 to payment receiving device 200.

[0306] The specific details of steps S807 to S809 can be found above. Figure 7 The relevant descriptions of steps S706 to S708 in the illustrated embodiment will not be repeated here.

[0307] S810. The payment device 200 sends a payment notification 2 to the payment application A via the NFC service module 12.

[0308] After receiving the payment notification 2, the payment device 200 can send the payment notification 2 to the payment application A through the NFC service module 12. The specific content and function description of the payment notification 2 can be found above. Figure 7 The following is a description of payment notification 1 in the illustrated embodiment.

[0309] S811.NFC service module 12 sends a payment credential to the receiving device 200, the payment credential being used to indicate the payment account.

[0310] In some embodiments, the NFC service module 12 may execute step S811 if it detects that no payment permission has been received within a preset time period after executing step S801.

[0311] In other embodiments, if password-free payment is not possible, payment application A may also send a non-password-free payment notification to NFC service module 12. The non-password-free payment notification indicates that password-free payment is not possible for the current payment. NFC service module 12 can receive and respond to the non-password-free payment notification, and execute step S811.

[0312] In other embodiments, the NFC service module 12 may also perform step S811 when it detects that the electronic device 100 is far away from the receiving device 200, even if payment authorization is not received.

[0313] S812. The receiving device 200 sends payment information 3 to the payment cloud server 300. The payment information 3 includes the payment amount, payment voucher and receiving account.

[0314] The difference between payment information 3 and payment information 2 is that payment information 3 does not include password-free payment permission.

[0315] S813. Payment cloud server 300 sends a payment license request to payment application A. The payment license request is used to request payment license.

[0316] Step S813 is an optional step.

[0317] In some embodiments, after receiving payment information 3, the payment cloud server 300 may execute step S813.

[0318] S814. Payment application A outputs a payment verification prompt, reminding the user to complete the payment verification.

[0319] In some embodiments, payment application A may output a payment verification prompt if it detects that the payment credentials do not support password-free payment or that the actual payment amount is greater than the password-free payment amount.

[0320] In other embodiments, payment application A may also receive and respond to a payment authorization request sent by payment cloud server 300 and output a payment verification prompt.

[0321] S815. Payment application A receives the user's payment verification operation.

[0322] S816. Payment application A sends a payment authorization verification message to payment cloud server 300.

[0323] After detecting that the user has completed the payment verification operation, i.e., the user's identity verification is successful, payment application A can establish a communication connection with payment cloud server 300. Payment application A can send a payment verification authorization to payment cloud server 300 through this communication connection. The payment verification authorization is used to authorize the payment cloud server to deduct funds from the designated payment account.

[0324] In some embodiments, payment application A may execute step S816 in response to a user's payment verification operation.

[0325] In other embodiments, payment application A may also respond to a payment permission request sent by payment cloud server 300 and execute step S816.

[0326] S817. Payment Cloud Server 300 deducts funds from the payment account based on payment information 3, and the deducted amount is the actual amount paid.

[0327] S818. Payment cloud server 300 transfers funds to the receiving account. The receiving amount includes the actual payment amount and the discount amount.

[0328] S819. Payment cloud server 300 sends a payment notification 3 to payment receiving device 200.

[0329] The specific details of steps S817 to S819 can be found in the descriptions of steps S807 to S809 above, and will not be repeated here.

[0330] S820. Payment cloud server 300 sends payment notification 3 to payment application A.

[0331] The relevant content and functional description of payment notification 3 can be found in the description of payment notification 2 in step S810 above.

[0332] Understandable, Figure 8 The illustrated embodiment is merely an example. In this application embodiment, the payment application corresponding to the payment method determined by the electronic device 100 can also be the same as described above. Figure 8 The different payment applications shown in the embodiments are not limited to those described herein.

[0333] In another possible implementation, if the electronic device 100 does not leave the radio frequency field of the receiving device 200 during the user's payment verification operation, the electronic device 100 can also send a verification payment permission to the receiving device 200 through the NFC service module 12 after the user completes the payment verification operation, and the receiving device 200 and the payment cloud server 300 can interact to complete the payment. This application does not limit this.

[0334] In another possible implementation, the electronic device 100 may also prompt the user to complete payment verification if it detects that the currently used payment method cannot be used for password-free payment (e.g., password-free payment is not supported, or the payment amount is greater than the password-free payment amount). If the electronic device 100 leaves the radio frequency field of the receiving device 200 during the user's payment verification process, the electronic device 100 can re-enter the radio frequency field of the receiving device 200 after the user has completed payment verification and identity verification is successful. It can then touch the receiving device 200 and send the verification payment permission to the receiving device 200 based on NFC technology, which in turn sends it to the payment cloud server 300. This application does not impose any limitations on this.

[0335] In this way, electronic device 100 can complete the payment by touching payment device 200 twice.

[0336] In some application scenarios, after electronic device 100 completes the payment, electronic device 100 can also send a payment crowdsourcing message to payment cloud server 300, and payment cloud server 300 can update the merchant discount information it stores based on the payment crowdsourcing message.

[0337] For example, Figure 9 A flowchart illustrating a payment method provided in an embodiment of this application is shown.

[0338] like Figure 9 As shown, the specific process of a payment method may include the following steps:

[0339] S901. Electronic device 100 detected entry into geofence A1.

[0340] S902. Electronic device 100 determines the precise location of electronic device 100 as position 1.

[0341] S903. Electronic device 100 sends a discount information request 1 to payment cloud server 300, the discount information request 1 including location 1 and / or geofence A1.

[0342] S904. The payment cloud server 300 sends merchant discount information 1 to the electronic device 100. Merchant discount information 1 includes discount activities of one or more merchants within the geofence A1.

[0343] S905. Electronic device 100 displays merchant discount information 1.

[0344] The specific details of steps S901 to S905 can be found above. Figure 6 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0345] S906. Electronic device 100 enters the radio frequency field of receiving device 200.

[0346] S907. The receiving device 200 sends a probe frame to the electronic device 100.

[0347] S908. Electronic device 100 sends a probe ACK frame to receiving device 200.

[0348] S909. The receiving device 200 sends a pick frame to the electronic device 100. The pick frame carries device characteristic information of the receiving device 200.

[0349] S910. Electronic device 100 determines that the service type of payment receiving device 200 is codeless payment based on the device feature information of payment receiving device 200.

[0350] S911. Electronic device 100 sends a PickACK frame to receiving device 200.

[0351] The specific details of steps S906 to S911 can be found above. Figure 5 The relevant steps in the illustrated embodiment will not be repeated here.

[0352] S912. The receiving device 200 sends a payment request 2 to the electronic device 100. The payment request 2 includes a merchant ID and the amount payable, and optionally, also includes an identifier of the payment method supported by the receiving device 200.

[0353] After receiving PickACK, the receiving device 200 can send a payment request 2 to the electronic device 100.

[0354] S913. Electronic device 100 determines promotional activity 1 based on merchant ID and merchant promotional information 1. Promotional activity 1 includes one or more promotional activities of the merchant corresponding to payment device 200.

[0355] After receiving payment request 2, electronic device 100 can determine the promotional activity 1 corresponding to the merchant ID from the merchant promotional information 1 based on the merchant ID. Promotional activity 1 may include one or more promotional activities corresponding to the merchant ID.

[0356] In some embodiments, the merchant ID in payment request 2 can also be used to obtain one or more payment methods supported by the payment receiving device 200.

[0357] S914. Electronic device 100 determines and displays the discount amount for one or more payment methods based on promotional activity 1.

[0358] Electronic device 100 can determine the payment method supported by payment device 200 based on the identifier of the payment method supported by payment device 200 in payment request 2.

[0359] The electronic device 100 can also obtain the payment methods supported by the electronic device 100 based on the payment applications and payment mini-programs installed on the electronic device 100. It should be noted that, in this embodiment of the application, the electronic device 100 may have one or more payment applications installed, and each payment application may include one or more payment mini-programs, which can be used to implement payment functions. Each payment mini-program can be regarded as a payment method.

[0360] In some embodiments, electronic device 100 may determine the discount amount for one or more payment methods based on promotional activity 1, payment methods supported by payment device 200, and payment methods supported by electronic device 100. The one or more payment methods are payment methods supported by electronic device 100 and payment device 200.

[0361] After determining the discount amount for one or more payment methods, the electronic device 100 can display the discount amount for one or more payment methods. In one possible implementation, the electronic device 100 can display one or more payment options, each payment option corresponding to a payment method, and each payment option can include the discount amount and / or the actual payment amount for that payment method. The actual payment amount for each payment method can be determined based on the amount due and the discount amount for that payment method; that is, the actual payment amount is the difference between the amount due and the discount amount. In this way, the electronic device 100 can prompt the user with the discount amount for one or more payment methods so that the user can choose the appropriate payment method.

[0362] S915. Electronic device 100 receives and responds to the user's operation of selecting payment method 1, and determines the enjoyment of promotional activity 2, actual payment amount 1 and payment voucher 1, the payment voucher 1 being used to indicate the payment account 1 of payment method 1.

[0363] Electronic device 100 can receive and respond to the user's selection of payment method 1, and determine the actual payment amount 1 of payment method 1 based on the discount amount and / or actual payment amount of payment method 1. Electronic device 100 can also determine the discount activity 2 enjoyed in this payment based on the user's selection of payment method 1. Discount activity 2 is a part of discount activity 1, and discount activity 2 can be used to determine the actual payment amount 1.

[0364] The electronic device 100 can also receive and respond to the user's selection of payment method 1, and determine the payment credential 1 for payment method 1, which is used to instruct payment account 1.

[0365] S916. Electronic device 100 sends a payment response 2 to receiving device 200, the payment response 2 including payment voucher 1, and optionally, also including actual payment amount 1 and promotional activity 2.

[0366] Alternatively, payment response 2 may also carry an identifier of payment method 1, which can be used to indicate the payment method adopted by electronic device 100. In other embodiments, payment credential 1 may also be used to indicate payment method 1, in which case payment response 2 may not include the identifier of payment method 1.

[0367] It should be noted that when performing steps S914 to S916, the electronic device 100 needs to ensure that it is within the radio frequency field of the receiving device 200, so that the electronic device 100 can send a payment response 2 to the receiving device 200 based on NFC technology.

[0368] In another possible implementation, if the electronic device 100 leaves the radio frequency field of the receiving device 200 before determining the payment method, then after determining payment method 1, the electronic device 100 can also send payment account 1 to the payment cloud server 300 through the communication connection with the payment cloud server 300. Optionally, it can also send information such as promotional activity 2 and actual payment amount 1 to the payment cloud server 300. In this case, the receiving device 200 can send the receiving account and the amount due to the payment cloud server 300, which will then complete the payment based on the receiving account, payment account 1, and the amount due. The specific process of the payment cloud server 300 completing the payment based on the receiving account, payment voucher 1, and the amount due can also refer to the above. Figure 7 or Figure 8 The relevant steps in the illustrated embodiment will not be repeated here.

[0369] S917. Payment device 200 determines whether the merchant's current promotional activities include promotional activities 2.

[0370] Step S917 is an optional step.

[0371] In one possible implementation, after receiving payment response 2, the receiving device 200 may execute step S918 to deduct funds from the payment account 1 indicated by payment voucher 1, thus completing the payment. In this case, steps S917 and steps S923 to S931 are not executed.

[0372] In another possible implementation, after receiving the payment response 2, the payment device 200 can determine whether the promotional activity 2 carried in the payment response 2 is valid, and determine the subsequent execution steps based on the determination result.

[0373] In some embodiments, the merchant's promotional activities may not be synchronized to the payment cloud server 300 in real time. Therefore, the promotional activities obtained by the electronic device 100 from the payment cloud server 300 may differ from the merchant's current actual promotional activities. Thus, the payment receiving device 200 can further determine whether the promotional activity 2 currently enjoyed by the electronic device 100 is valid.

[0374] If the merchant's current promotional activities include promotion 2, then the payment device 200 can perform the following step S918.

[0375] If the merchant's current promotional activities do not include promotional activity 2, then the payment device 200 can perform the following step S923.

[0376] S918. The receiving device 200 deducts funds based on payment account 1, and the deduction amount is the actual payment amount 1.

[0377] For example, the specific process of the payment device 200 deducting funds from payment account 1 can be referred to the above. Figure 7 or Figure 8 The relevant steps in the illustrated embodiment will not be described in detail here.

[0378] S919. The receiving device 200 sends a payment success notification 1 to the electronic device 100.

[0379] After the payment is successfully deducted, the receiving device 200 can send a payment success notification 1 to the electronic device 100. The payment success notification 1 is used to notify the electronic device 100 that the payment has been completed.

[0380] In some embodiments, the payment success notification 1 may include the amount due, the discount amount, the actual amount paid 1, the identifier of payment method 1, the discount activity actually enjoyed (i.e. discount activity 2), etc. Optionally, the payment success notification 1 may also include the payment time, etc.

[0381] S920. Electronic device 100 outputs payment success message 1.

[0382] The electronic device 100 can output a payment success message 1 using one or more methods such as display screen, voice broadcast, vibration, and indicator light flashing.

[0383] Payment success notification 1 is used to notify the user that their electronic device has successfully made the payment.

[0384] For example, payment success notification 1 could be as described above. Figure 4G The payment success message 450 in the illustrated embodiment.

[0385] S921. Electronic device 100 sends payment crowdsourcing 1 to payment cloud server 300. Payment crowdsourcing 1 includes geofence A1, merchant ID, identifier of payment method 1, amount due, actual payment amount 1, and promotional activity 2.

[0386] Optionally, in some embodiments, if the electronic device 100 is connected to Wi-Fi, the payment crowdsourcing 1 may also include a Wi-Fi fingerprint, which can be used to indicate the current location information of the electronic device 100. For example, the Wi-Fi fingerprint may be a device identifier of the Wi-Fi signal access point (AP).

[0387] S922. Payment Cloud Server 300 updates merchant discount information based on payment crowdsourcing 1.

[0388] The payment cloud server 300 can store merchant discount information corresponding to one or more geofences (e.g., merchant discount information 1 corresponding to geofence A1). The specific storage content and method can be referred to the relevant description in the embodiment shown in Table 1 above.

[0389] It should be noted that, in some embodiments, when storing merchant discount information corresponding to geofences, the payment cloud server 300 may also store the validity period of each discount activity in the discount information. Before the expiration of the discount activity, if the payment cloud server 300 receives a payment crowdsourcing service indicating that the discount activity has been enjoyed, the payment cloud server 300 may update the validity period of the discount activity, for example, by extending the validity period to a specific time (e.g., 24 hours or 3 days after the current time); if the payment cloud server 300 does not receive a payment crowdsourcing service indicating that the discount activity has been enjoyed before the expiration of the discount activity, the payment cloud server 300 may delete the discount activity.

[0390] For example, taking the update of merchant discount information 1 corresponding to geofence A1 by payment cloud server 300 based on payment crowdsourcing 1 as an example, after receiving payment crowdsourcing 1, payment cloud server 300 can determine one or more discount activities (also referred to as discount activity 1) of the merchant stored by payment cloud server 300 based on geofence A1 and merchant ID. Payment cloud server 300 can determine whether discount activity 1 includes discount activity 2. As can be seen from the above embodiment, discount activity 1 includes discount activity 2. At this time, payment cloud server 300 can refresh the validity period of discount activity 2, for example, refresh the validity period of discount activity 2 to a specific time period after the current time (e.g., 24 hours or 3 days after the current time). It should be noted that if the payment cloud server 300 receives a new payment crowdsourcing application carrying promotional activity 2 before the expiration of promotional activity 2, the payment cloud server 300 can refresh the expiration of promotional activity 2; if the payment cloud server 300 does not receive a new payment crowdsourcing application carrying promotional activity 2 before the expiration of promotional activity 2, the payment cloud server 300 can delete promotional activity 2 from merchant promotional information 1.

[0391] It is understood that the above embodiments are only examples. In the embodiments of this application, other promotional activities in merchant promotional information 1, or promotional activities in other geofence-related promotional information, can also refresh their validity period or delete invalid promotional activities in a similar manner to the above embodiments.

[0392] In this way, based on payment crowdsourcing reported by multiple electronic devices, the discount information stored in different geofences in the payment cloud server 300 can be updated in real time, enhancing the timeliness of the discount information.

[0393] Furthermore, it should be noted that in some other embodiments, if the payment crowdsourcing sent by the electronic device 100 indicates that the electronic device 100 enjoys a promotional activity not stored in the payment cloud server 300, the payment cloud server 300 can also add the promotional activity to the corresponding promotional information. Specific examples of this situation can be found in the relevant content of step S931 below.

[0394] S923. The payment receiving device 200 sends merchant promotion information 2 to the electronic device 100, the merchant promotion information 2 including one or more promotional activities of the merchant corresponding to the payment receiving device 200.

[0395] If the promotional activity obtained by the electronic device 100 is determined to be invalid, the payment device 200 can obtain the latest merchant promotional information 2 from the merchant and send the merchant promotional information 2 to the electronic device 100. In some embodiments, the payment device 200 may store the merchant promotional information 2; in other embodiments, the payment device 200 may obtain the latest merchant promotional information 2 from the merchant's backend server.

[0396] S924. Electronic device 100 determines and displays the discount amount for one or more payment methods based on merchant discount information 2.

[0397] S925. Electronic device 100 receives and responds to the user's selection of payment method 2, determines payment voucher 2 and actual payment amount 2, the payment voucher 2 being used to instruct payment account 2.

[0398] The details of steps S924 and S925 can be found in the descriptions of steps S914 and S915 above, and will not be repeated here.

[0399] S926. Electronic device 100 sends payment voucher 2 to receiving device 200, optionally including actual payment amount 2.

[0400] It should be noted that when performing steps S924 to S926, the electronic device 100 needs to ensure that it is within the radio frequency field of the receiving device 200. In this way, the electronic device 100 can send the payment voucher 2 and the actual payment amount 2 to the receiving device 200 based on NFC technology.

[0401] In another possible implementation, if the electronic device 100 leaves the radio frequency field of the receiving device 200 before determining the payment method, then after determining to use payment method 2, the electronic device 100 can also send payment account 2 to the payment cloud server 300 through the communication connection with the payment cloud server 300. Optionally, it can also send merchant discount information 2, actual payment amount 2, and other information to the payment cloud server 300. In this case, the receiving device 200 can send the receiving account and the amount due to the payment cloud server 300, which will then complete the payment based on the receiving account, payment account 1, and the amount due. The specific process of the payment cloud server 300 completing the payment based on the receiving account, payment account 2, and the amount due can be referred to the following. Figure 6 The relevant steps in the illustrated embodiment will not be repeated here.

[0402] S927. The receiving device 200 deducts funds based on payment account 2, and the deduction amount is the actual payment amount 2.

[0403] S928. The receiving device 200 sends a payment success notification 2 to the electronic device 100.

[0404] S929. Electronic device 100 outputs payment success message 2.

[0405] S930. Electronic device 100 sends payment crowdsourcing 2 to payment cloud server 300. Payment crowdsourcing 2 includes geofence A1, merchant ID, identifier of payment method 2, amount due, actual payment amount 2, and merchant discount information 2.

[0406] The specific details of steps S927 to S930 can be found in the descriptions of steps S918 to S921 above, and will not be repeated here.

[0407] S931. Payment Cloud Server 300 updates merchant discount information based on Payment Crowdsourcing 2 1.

[0408] After receiving Payment Crowdsourcing 2, Payment Cloud Server 300 can determine one or more promotional activities (also referred to as Promotional Activity 1) of the merchant stored by Payment Cloud Server 300 based on geofence A1 and merchant ID. Payment Cloud Server 300 can determine whether Merchant Promotional Information 1 includes all promotional activities in Merchant Promotional Information 2. As can be seen from the above embodiment, Merchant Promotional Information 1 does not include all promotional activities in Merchant Promotional Information 2. In this case, Payment Cloud Server 300 can add Merchant Promotional Information 2 to Merchant Promotional Information 1, that is, add it to the promotional activities corresponding to the merchant ID.

[0409] Other related content in step S931 can also refer to the relevant description in step S922 above, and will not be repeated here.

[0410] Understandable, Figure 9 The embodiments shown are merely examples. In the embodiments of this application, when the electronic device 100 performs the payment method, it may also perform more, fewer, or different steps than the above embodiments. This application does not limit the scope of the embodiments.

[0411] The payment method provided in this application allows for the acquisition and display of promotional information corresponding to a geofence upon entry, enabling users to choose whether to make a purchase and increasing customer traffic for merchants. Furthermore, users can make payments based on these promotional information, saving on shopping expenses.

[0412] It should be noted that in some embodiments, after step S917, if the payment device 200 determines that the promotional activity 2 is invalid, the payment device 200 may also send an invalidation notification to the payment cloud server 300. This invalidation notification informs the payment cloud server 300 that the promotional activity 2 has expired. The payment device 200 may send the invalidation notification directly to the payment cloud server 300, or it may send it through the electronic device 100, or through a merchant backend server, etc. The payment cloud server 300 may receive and respond to the invalidation notification, removing the promotional activity 2 from the merchant promotional information 1.

[0413] In this way, the payment cloud server 300 can also delete invalid promotional activities in real time based on the invalid notifications received.

[0414] In another possible implementation, when electronic device 100 first enters region 1 (region 1 includes multiple geofences, including geofence A1), it can obtain the discount information of all geofences in region 1 (e.g., merchant discount information 1 for geofence A1) from payment cloud server 300. Subsequently, upon detecting that electronic device 100 has entered geofence A1, electronic device 100 can determine merchant discount information 1 for geofence A1 from the discount information of region 1 based on geofence A1. In this way, when electronic device 100 enters geofence A1, it can determine merchant discount information 1 from the locally pre-stored discount information of region 1 without further interaction with payment cloud server 300, thus shortening the time spent determining merchant discount information 1 and improving efficiency.

[0415] In another possible implementation, after receiving the payment information, the electronic device 100 can also determine the most favorable payment method (i.e., the payment method with the largest discount) based on the merchant's discount information 1, and complete the payment using the most favorable payment method. In this way, the user does not need to select a payment method; the electronic device 100 can directly select the most favorable payment method to complete the payment, simplifying the payment process and improving payment efficiency.

[0416] In another possible implementation, when a user makes a payment to the receiving device 200 via the electronic device 100, the receiving device 200 can also send one or more promotional offers to the electronic device 100. These promotional offers are from the merchant to which the receiving device 200 belongs. The electronic device 100 can then determine the final payment method based on these promotional offers and complete the payment accordingly. It should be noted that in this case, the electronic device 100 does not need to obtain the merchant promotional information 1 for geofence A1 from the payment cloud server 300; that is, the electronic device 100, the receiving device 200, and the payment cloud server 300 do not need to perform the aforementioned steps. Figure 9 The steps S901 to S905 and steps S913 to S922 shown are as follows.

[0417] In this way, electronic device 100 can directly obtain merchant 1's promotional activities through payment device 200 without having to obtain merchant promotional information from payment cloud server 300. This not only shortens the interaction time but also ensures that the merchant's promotional activities are obtained in real time.

[0418] In another possible implementation, Figure 9 In step S912, the payment request 2 sent by the receiving device 200 to the electronic device 100 may also include the receiving account. In this case, after determining the final payment method 1, the corresponding payment account 1, and the actual payment amount 1, the electronic device 100 can send the payment account 1, the receiving account 1, and the amount due and / or the actual payment amount 1 to the payment cloud server 300 through the communication connection with the payment cloud server 300, and the payment cloud server 300 will complete the payment.

[0419] In this way, regardless of whether the electronic device 100 requires user operation to determine the final payment method, the electronic device 100 does not need to remain within the radio frequency field of the receiving device 200, but can complete the payment through interaction with the payment cloud server 300.

[0420] In some application scenarios, when the electronic device 100 interacts with the payment receiving device 200, it can also obtain preferential payment methods and corresponding platform discount information from the payment cloud server 300. The platform discount information includes promotional activities offered by the payment platform for one or more payment methods (also known as platform promotional activities). In this case, the electronic device 100 can determine the final payment method to be used from the preferential payment methods supported by both the electronic device 100 and the payment receiving device 200 based on the obtained merchant discount information and platform discount information, and complete the payment.

[0421] For example, Figure 10 A flowchart illustrating another payment method provided in an embodiment of this application is shown.

[0422] like Figure 10 As shown, the specific process of the payment method may include the following steps:

[0423] S1001. Electronic device 100 Obtain merchant discount information 1.

[0424] S1002. Electronic device 100 enters the radio frequency field of receiving device 200.

[0425] S1003. The receiving device 200 sends a probe frame to the electronic device 100.

[0426] S1004. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0427] S1005. After receiving the Probe ACK frame, the payment receiving device 200 sends a Pick frame. The Pick frame carries the device characteristic information of the payment receiving device 200. The device characteristic information is used to indicate that the service type of the payment receiving device 200 is the payment discount service in codeless payment.

[0428] Since in step S1005, the device feature information is used to indicate that the service type of the receiving device 200 is a payment discount service in codeless payment, the device main service identifier that can be carried in the Pick frame can be 0x07 as shown in Table 1 above, and the device sub-service identifier can be 0x02 as shown in Table 1 above. In this way, the service type of the receiving device 200 can be indicated by the device service identifier in the device feature information.

[0429] S1006. Electronic device 100 determines the service type as payment discount service in codeless payment based on the device feature information of payment receiving device 200.

[0430] S1007. Electronic device 100 sends a Pick ACK frame.

[0431] S1008. The payment device 200 sends a payment request 3, which includes the amount due and the merchant ID, and optionally, also includes an identifier of one or more payment methods supported by the payment device 200.

[0432] S1009. Electronic device 100 determines one or more promotional activities of merchant 1 from merchant promotional information 1 based on merchant ID, where merchant 1 is the merchant to which the payment receiving device 200 belongs.

[0433] The specific details of steps S1001 to S1009 can be found above. Figure 5 The relevant descriptions in the illustrated embodiments.

[0434] S1010. Electronic device 100 acquires one or more preferential payment methods supported by both electronic device 100 and payment device 200.

[0435] Preferential payment methods refer to payment methods offered by the payment platform that include discounts or promotions, where the actual amount paid under the preferential payment method is less than the amount due.

[0436] In some embodiments, the merchant discount information may include promotional activities of the payment platform. The electronic device 100 may determine one or more discounted payment methods supported by both the electronic device 100 and the payment receiving device 200 from the payment methods supported by both the electronic device 100 and the payment receiving device 200 based on the merchant discount information.

[0437] In other embodiments, after receiving the payment request 3, the electronic device 100 can obtain from the payment cloud server 300 one or more preferential payment methods supported by both the electronic device 100 and the payment device 200, as well as platform preferential information, based on the merchant ID and / or the identifier of the payment method supported by the payment device 200 carried in the payment request 3. The platform preferential information may include the preferential activities provided by the payment platform corresponding to one or more payment methods.

[0438] S1011. Electronic device 100 determines payment method 3 from one or more preferential payment methods supported by both electronic device 100 and payment device 200 based on one or more promotional activities of merchant 1.

[0439] In one possible implementation, electronic device 100 can determine the discount amount and / or actual payment amount for each of the discounted payment methods supported by both electronic device 100 and payment device 200 based on one or more promotional activities of merchant 1, and determine the discounted payment method with the largest discount amount (or smallest actual payment amount) as payment method 3. In other embodiments, if electronic device 100 also obtains platform discount information, electronic device 100 can also determine the discount amount and / or actual payment amount for each discounted payment method based on one or more promotional activities of merchant 1 and platform discount information, and determine the discounted payment method with the largest discount amount (or smallest actual payment amount) as payment method 3.

[0440] In another possible implementation, electronic device 100 may display one or more payment options based on one or more promotional activities of merchant 1, each payment option corresponding to a discounted payment method supported by both electronic device 100 and payment receiving device 200. Each payment option may include an identifier of the discounted payment method, and may also include the discounted amount and / or the actual payment amount of the discounted payment option. Electronic device 100 may determine the discounted payment method corresponding to the payment option selected by the user as payment method 3 based on the user's selection operation. In some other embodiments, if electronic device 100 also obtains platform discount information, electronic device 100 may also display one or more payment options based on one or more promotional activities of merchant 1 and platform discount information, and determine payment method 3 based on the user's selection operation.

[0441] S1012. Electronic device 100 determines the payment voucher 3, the actual amount paid 3, and the payment authorization 3 for payment method 3, wherein the payment voucher 3 is used to instruct the payment account 3 for payment method 3.

[0442] Payment license 3 is used to authorize the receiving end to deduct funds from payment account 3.

[0443] For details regarding Payment Voucher 3 and Payment Method 3, please refer to the above. Figure 5 The descriptions of payment credential 1 and payment license 1 in the illustrated embodiment will not be repeated here.

[0444] Electronic device 100 can determine the actual payment amount 3 corresponding to payment method 3 based on platform promotional information, merchant 1's promotional activities, and payment method 3. The actual payment amount 3 is the amount that electronic device 100 actually needs to pay when using payment method 3. The actual payment amount 3 is less than or equal to the amount due.

[0445] S1013. Electronic device 100 sends a payment response 3, which includes a payment voucher 3, the amount paid 3, and a payment authorization 3.

[0446] Electronic device 100 can send payment response 3 to payment device 200 via a single communication or via multiple communications. For details, please refer to the above. Figure 5 The relevant descriptions in step S512 shown will not be repeated here.

[0447] S1014. The receiving device 200 deducts funds from the payment account 3 based on the payment voucher 3 and the payment license 3, and the deducted amount is the actual payment amount 3.

[0448] The details of step S1014 can be found above. Figure 5 The relevant descriptions in step S513 shown will not be repeated here.

[0449] Understandable, Figure 10 The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 and the payment device 200 may use different interaction steps than those in the above embodiments to complete the payment. This application does not limit the scope of the embodiments.

[0450] The payment method provided in this application not only simplifies the payment process and improves payment efficiency, but also allows users to obtain merchant and platform discount information, thereby reducing their expenses.

[0451] In some application scenarios, when the electronic device 100 has a membership card designated by the payment device 200, the electronic device 100 can prioritize using the membership card payment method to complete the payment. In other embodiments, the electronic device 100 can also use the membership card payment method as a preferential payment method, determining the final payment method based on the discount amount of each preferential payment method and / or the user's selection of the payment method, and then completing the payment.

[0452] For example, Figure 11 A flowchart illustrating another payment method provided in an embodiment of this application is shown.

[0453] like Figure 11 As shown, the specific process of the payment method may include the following steps:

[0454] S1101. Electronic device 100 Obtain merchant discount information 1.

[0455] S1102. Electronic device 100 enters the radio frequency field of receiving device 200.

[0456] S1103. The receiving device 200 sends a probe frame to the electronic device 100.

[0457] After receiving a probe frame, the S1104.NFC service module 12 sends a probe ACK frame.

[0458] NFC service module 12 may include the above Figure 3A The NFC module 102 and NFC basic service module in the illustrated embodiment, etc. The NFC service module 12 may also refer to the aforementioned... Figure 3B The NFC protocol stack in the illustrated embodiment. In some embodiments, step S1104, and step S1106 below, can be derived from the above... Figure 3B The access layer in the NFC protocol stack shown is responsible for executing the data received and controlling the data sent.

[0459] S1105. After receiving the Probe ACK frame, the payment device 200 sends a Pick frame. The Pick frame carries the device characteristic information of the payment device 200, which is used to indicate that the service type of the payment device 200 is codeless payment.

[0460] S1106.NFC service module 12 determines the service type as codeless payment based on the device feature information of the receiving device 200.

[0461] After determining the service type, in the above Figure 3B In the NFC protocol stack shown, the transport layer can report the service type of the payment device 200 to the application layer. The service type can be used to instruct the application layer to select one or more payment applications (also called payment application set 11) with payment functions based on the service type of the payment device 200 and the routing rule list. Then, the payment application set 11 can communicate with the payment device 200 based on NFC technology through the NFC service module 12.

[0462] It should be noted that, in this embodiment of the application, the payment application set 11 may include one or more applications with payment functions (also called payment applications), and each payment application may manage one or more mini programs with payment functions (also called payment mini programs), and each payment mini program may be regarded as a payment method.

[0463] S1107.NFC service module 12 sends a Pick ACK frame.

[0464] For details on steps S1101 to S1107, please refer to the above. Figure 5 The relevant descriptions of steps S501 to S507 are shown below.

[0465] S1108. The payment device 200 sends a discount capability inquiry request to the payment application set 11 via the NFC service module 12. The discount capability inquiry request includes the merchant ID.

[0466] A request to inquire about payment options supported by an electronic device can be used to ask about the payment options supported by the device. The specific definitions of payment options can be found above. Figure 10 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0467] In some embodiments, the offer capability inquiry request may include a merchant identification (ID). The merchant ID can be used to identify the merchant, and also to identify the merchant's membership card. In other embodiments, the merchant ID can also be used to obtain one or more payment methods supported by the payment device 200.

[0468] Optionally, the discount capability inquiry request may also include identifiers of one or more payment methods supported by the payment receiving device 200. Alternatively, the payment application set 11 may obtain the one or more payment methods supported by the payment receiving device 200 from the payment cloud server 300 based on the merchant ID. In this case, the discount capability inquiry request can also be used to inquire whether there is a discounted payment method supported by both the electronic device 100 and the payment receiving device 200 among the one or more payment methods supported by the payment receiving device 200. In this embodiment, if the payment receiving device 200 supports membership card payment, the aforementioned discounted payment method may also include membership card payment.

[0469] S1109. Payment application set 11 sends a discount capability response 1 or discount capability response 2 to the receiving device 200 via NFC service module 12. Discount capability response 1 includes an identifier of one or more discount payment methods, and discount capability response 2 is used to indicate that no discount payment method exists.

[0470] The payment application set 11 can determine one or more payment methods supported by electronic devices 100 based on all payment applications in the payment application set 11 and the payment mini-programs included in each payment application.

[0471] For example, payment methods may include, but are not limited to, any one or more of the following: C1 bank card, membership card, balance in payment application A, C2 bank card in payment application B, etc. It is understood that the embodiments described here are merely examples, and in the embodiments of this application, payment methods may include more, fewer, or different payment methods than those described above; this application does not impose any limitations on these methods.

[0472] In one possible implementation, after receiving a discount capability inquiry request, each payment application in the payment application set 11 can determine whether one or more payment methods in the payment application have a discount payment method. If a discount payment method exists, the payment application can send a discount capability response 1 to the receiving device 200 through the NFC service module 12. The discount capability response 1 may include the identifier of one or more discount payment methods. If no discount payment method exists, the payment application can send a discount capability response 2 to the receiving device 200 through the NFC service module 12. The discount capability response 2 may carry the identifier of the payment application and can be used to indicate that no discount payment method exists in the payment application.

[0473] In another possible implementation, after receiving a discount capability response 1 or discount capability response 2 from each payment application in the payment application set 11, the NFC service module 12 can determine whether the electronic device 100 has a discount payment method. If the electronic device 100 has at least one discount payment method, the NFC service module 12 can send a discount capability response 3 to the receiving device 200, which may include identifiers of one or more discount payment methods; if the electronic device 100 does not have a discount payment method, the NFC service module 12 can send a discount capability response 4 to the receiving device 200, which can be used to indicate that the electronic device 100 does not have a discount payment method.

[0474] In some embodiments, the payment application set 11 can determine whether the electronic device 100 supports the membership card payment method corresponding to the merchant ID based on the merchant ID, etc. After determining the preferential payment method, the payment application set 11 can send the identifier of the preferential payment method to the receiving device 200.

[0475] In another possible implementation, after receiving a discount capability inquiry request, the payment application set 11 can determine the discounted payment method from one or more payment methods supported by both the electronic device 100 and the receiving device 200. It should be noted that in some embodiments, the payment application set 11 can determine the payment methods supported by the receiving device 200 based on the identifiers of one or more payment methods supported by the receiving device 200 carried in the discount capability inquiry request. In other embodiments, the payment application set 11 can obtain the payment methods supported by the receiving device 200 based on the merchant ID; for example, the payment application set 11 can obtain the payment methods supported by the receiving device 200 from the payment cloud server 300 based on the merchant ID, etc. After determining the payment methods supported by the receiving device 200, the payment application set 11 can determine the discounted payment method from one or more payment methods supported by both the electronic device 100 and the receiving device 200. Then, the payment application set 11 can send a discount capability response 1 or a discount capability response 2 to the receiving device 200 based on whether a discounted payment method exists.

[0476] S1110. The receiving device 200 determines whether the receiving device 200 has a preferential payment method.

[0477] After receiving either the discount capability response 1 or the discount capability response 2, the payment device 200 can determine whether a discount payment method exists among the one or more discount payment methods supported by the payment device 200.

[0478] If the payment device 200 receives the preferential capability response 2, it can determine that there is no preferential payment method among the payment methods supported by the payment device 200.

[0479] If a discount capability response 1 is received, and the discount capability response 1 includes the identifier of one or more discount payment methods, then the receiving device 200 can determine whether there is a discount payment method supported by the receiving device 200 among the one or more discount payment methods. In some embodiments, if the discount payment method carried in the discount capability response 1 in step S1109 is determined by the payment application set 11 from the payment methods supported by both the electronic device 100 and the receiving device 200, then as long as the discount capability response carries the identifier of at least one payment method, the receiving device 200 can determine that there is a discount payment method supported by the receiving device 200.

[0480] When there is no preferential payment method among the payment methods supported by the payment receiving device 200, the payment receiving device 200 can perform the following steps S1111.

[0481] When a preferential payment method is available among the payment methods supported by the payment receiving device 200, the payment receiving device 200 can perform the following step S1117.

[0482] S1111. The receiving device 200 sends a payment request 4, which includes the amount due.

[0483] If the receiving device 200 does not offer a preferential payment method, it can send a payment request 4 to the NFC service module 12. The payment request 4 can be used to request the electronic device 100 to provide a payment credential, which can be used to indicate the payment account. The payment request 4 may include the amount due. The amount due refers to the amount that the receiving device 200 should receive.

[0484] Optionally, the payment request 4 may also include an identifier of one or more payment methods supported by the payment device 200.

[0485] S1112.NFC service module 12 determines the payment method 4 from one or more payment methods supported by the payment device 200 based on merchant discount information 1.

[0486] In some embodiments, the NFC service module 12 can determine the payment methods supported by the receiving device 200 based on the identifiers of one or more payment methods supported by the receiving device 200 carried in the payment request 4. In other embodiments, the NFC service module 12 can also determine the payment methods supported by the receiving device 200 based on the preferential capability inquiry request in step S1108 above. The specific determination method can be referred to the relevant description in step S1109 above, and will not be repeated here.

[0487] In one possible implementation, after receiving payment request 4, NFC service module 12 can sort the payment methods based on merchant discount information 1 and the user's default payment methods, and determine the payment method 4 with the highest priority among one or more payment methods with the smallest actual payment amount as the final payment method.

[0488] In another possible implementation, after receiving payment request 4, NFC service module 12 can display one or more payment options based on merchant offer information 1, allowing the user to choose a payment method. NFC service module 12 can receive and respond to the user's selection of a payment method, determining the selected payment method 4 as the final payment method.

[0489] It should be noted that, in this scenario, if the electronic device 100 does not leave the radio frequency field of the receiving device 200 during the user's selection of a payment method, the electronic device 100 can execute step S1113 after determining payment method 4 based on the user's operation. In other embodiments, if the electronic device 100 leaves the radio frequency field of the receiving device 200 during the user's selection of a payment method, the electronic device 100 can send the payment voucher 4 corresponding to payment method 4 to the payment cloud server 300 through the communication connection with the payment cloud server 300. The payment voucher 4 can be used to indicate the payment account for payment method 4. Furthermore, the receiving device 200 can send other payment information such as the receiving account and payment amount to the payment cloud server 300. In other embodiments, the electronic device 100 may also assume that the user may leave the radio frequency field of the receiving device 200 during the selection of a payment method. In this case, both the electronic device 100 and the receiving device 200 can send the aforementioned information to the payment cloud server 300 to complete the payment.

[0490] It is understood that the above embodiments are just two examples. In the embodiments of this application, the payment application set 11 may also use a different method than the above embodiments to determine the final payment method from one or more payment methods supported by the payment device 200. This application does not limit this.

[0491] S1113. NFC service module 12 sends a payment response 4 to the receiving device 200. The payment response 4 includes a payment credential 4, which indicates the payment account 4 of the payment method 4.

[0492] After determining that payment method 4 will be used for payment, the NFC service module 12 sends a payment response 4 to the receiving device 200. The payment response 4 may include the payment credential 4 of payment method 4, wherein the payment credential 4 may be used to indicate the payment account 4 of payment method 4.

[0493] Optionally, the payment response 4 may also include one or more of the following: identifiers for payment authorization 4 and payment method 4. Payment authorization 4 is used to authorize the receiving end to deduct funds from the designated payment account 4. Other specific functions of payment authorization 4 can be found above. Figure 5 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0494] It should be noted that in some embodiments, the payment credential 4 can also be used to indicate that the electronic device 100 uses payment method 4. In this case, the payment response 4 may not include the identifier of payment method 4.

[0495] In some embodiments, the NFC service module 12 may store payment accounts for one or more payment methods supported by the electronic device 100, such as payment account 4 for payment method 4. In this case, when it is determined that payment method 4 will be used, the NFC service module 12 may determine the payment credential 4 corresponding to payment method 4 and send the payment credential 4 to the receiving device 200.

[0496] In other embodiments, when the NFC service module 12 determines that payment method 4 is to be used, it can obtain the payment credential 4 of payment method 4 from the payment application corresponding to payment method 4 in the payment application set 11 and send the payment credential 4 to the receiving device 200.

[0497] S1114. The receiving device 200 deducts funds based on payment account 4, and the deducted amount is the amount payable.

[0498] Upon receiving payment voucher 4, the receiving device 200 can initiate a deduction from the payment account 4 indicated by payment voucher 4 to the payment cloud server 300, with the deduction amount being the amount due.

[0499] The specific process for deducting payments from payment account 4 using the payment receiving device 200 can be found above. Figure 7 or Figure 8 The relevant steps in the illustrated embodiment will not be repeated here.

[0500] In some embodiments, after the receiving device 200 receives the amount due from the payment account 4, the receiving device 200 may perform the following step S1115.

[0501] S1115. Payment receiving device 200 sends payment success notification 3.

[0502] Payment success notification 3 can be used to notify electronic devices that payment has been successfully completed.

[0503] In some embodiments, the payment success notification 3 may include, but is not limited to, any one or more of the following: the identifier of payment method 4, the actual amount paid (in this embodiment, the amount payable in step S1114 above), the payee, the payment time, etc.

[0504] In one possible implementation, the receiving device 200 can send a payment success notification 3 to the payment application corresponding to payment method 4 in the payment application set 11 via the NFC module 12, and the payment application can then perform the following steps S1116 to output a payment success message 3.

[0505] In another possible implementation, the receiving device 200 may also send a payment success notification 3 to the NFC service module 12, and the NFC service module 12 shall perform the following steps S1116 to output a payment success message 3.

[0506] S1116. Payment application set 11 can output a payment success message 3.

[0507] In some embodiments, after receiving payment success notification 3, payment application set 11 can output payment success prompt 3. Payment success prompt 3 can be used to notify the user that the payment was successful. Payment success prompt 3 may include, but is not limited to, any one or more of the following: the identifier of payment method 4, the actual amount paid (in this embodiment, the amount payable in step S1114 above), the payee, the payment time, etc.

[0508] Payment application set 11 can output payment success prompts through one or more methods such as display screen, voice broadcast, vibration, and indicator light flashing.

[0509] S1117. Payment device 200 determines whether the payment device 200 supports preferential payment methods including membership card payment.

[0510] Steps S1117 to S1122 are optional steps.

[0511] It should be noted that, in one possible implementation, if it is determined that the payment receiving device 200 supports membership card payment, the payment receiving device 200 and the electronic device 100 can prioritize membership card payment. That is, after executing step S1110 and determining that the payment receiving device 200 supports preferential payment methods, the payment receiving device 200 and the electronic device 100 can execute steps S1117 to S1122 to determine the subsequent payment process based on whether the payment receiving device 200 supports membership card payment.

[0512] In another possible implementation, if it is determined that the payment receiving device 200 has a preferential payment method, the payment receiving device 200 may also use membership card payment as one of the preferential payment methods, and determine the final preferential payment method to be adopted based on the discount amount of each preferential method and the user's selection operation. In this case, the payment receiving device 200 and the electronic device 100 may execute step S1123 and subsequent steps after performing step S1110 and determining that the payment receiving device 200 has a preferential payment method, instead of executing steps S1117 to S1122.

[0513] If the payment device 200 supports membership cards as a preferred payment method, then the payment device 200 can perform the following step S1118.

[0514] If the payment method supported by the payment device 200 does not include membership cards, the payment device 200 can perform the following step S1123.

[0515] S1118. The payment device 200 sends a member payment request, which includes the member payment amount.

[0516] The payment device 200 can determine the member's payment amount based on the merchant's discount information 1. The member's payment amount can be less than or equal to the amount payable in step S1114 above.

[0517] After determining the member's payment amount, the payment receiving device 200 can send a member payment request to the payment application set 11, which includes the member's payment amount. The member payment request can be used to request the payment application set 11 to complete the payment using a membership card payment method.

[0518] S1119. Payment application set 11 sends a member payment response, which includes member payment credentials that are used to indicate the member account.

[0519] Payment application set 11 can receive and respond to member payment requests by sending a member payment response to the receiving device 200. The member payment response includes a member payment credential, which indicates the member account. Optionally, the member payment response may also include a member payment authorization, which authorizes the receiving end to deduct funds from the specified member account.

[0520] S1120. Payment device 200 deducts funds based on the member's account, with the deduction amount being the amount paid by the member.

[0521] In some embodiments, the specific process of the payment device 200 deducting payment based on a member's account can also refer to the above. Figure 7 or Figure 8 The deduction process in the illustrated embodiment will not be described in detail here.

[0522] In other embodiments, while completing the deduction, the payment device 200 can also award points to the member's account based on the member's payment amount, etc.

[0523] S1121. Payment receiving device 200 sends payment success notification 4.

[0524] Payment success notification 4 can be used to notify electronic devices that payment has been successfully made via membership card.

[0525] In some embodiments, the payment success notification 4 may include, but is not limited to, any one or more of the following: the identifier of the actual payment method used (which may be the identifier of the membership card), the amount actually paid (in this embodiment, the member payment amount in step S1120 above), the payee, the payment time, etc.

[0526] For details on how the receiving device 200 sends the payment success notification 4, please refer to the relevant description of step S1115 above.

[0527] S1122. Payment application set 11 can output a payment success message 4.

[0528] The details of step S1122 can be found in the description of step S1116 above, and will not be repeated here.

[0529] S1123. The receiving device 200 sends a payment request 5, which includes an identifier of the preferred payment method supported by the receiving device 200 and the amount payable.

[0530] Payment request 5 can be used to request electronic device 100 to determine the final payment method among the payment receiving device 200 and the preferential payment methods supported by electronic device 100.

[0531] Payment request 5 may include the amount due and an identifier of the preferred payment method supported by the payment device 200.

[0532] In some embodiments, if in step S1108 above, the electronic device 100 determines the payment method supported by the receiving device 200 based on the preferential capability inquiry request, then the payment request 5 may not include the identifier of the preferential payment method supported by the receiving device 200.

[0533] It should be noted that if the receiving device 200 does not execute step S1117, the identifier of the preferential payment method in payment request 5 may include the identifier of membership card payment. In this case, the electronic device 100 can consider membership card payment as an alternative preferential payment method, and select the final preferential payment method after obtaining the discount amount of other preferential payment methods. If the receiving device 200 executes step S1117, the identifier of the preferential payment method in payment request 5 may not include the identifier of membership card payment; that is, the payment application set 11 may select the final payment method based on one or more other preferential payment methods.

[0534] S1124. The payment application set 11 sends platform promotion information to the NFC service module 12, which includes promotional activities for the payment methods supported by the payment device 200.

[0535] For details on platform promotions, please refer to the above. Figure 10 The relevant descriptions in the illustrated embodiments.

[0536] In some embodiments, the payment application set 11 may, in response to the payment request 5, obtain platform discount information from the payment cloud server 300 and send the platform discount information to the NFC service module 12.

[0537] For example, Table 3 shows the composition of a platform discount information provided in an embodiment of this application.

[0538] Table 3

[0539] payment applications Payment methods Platform promotional activities Payment application A AA Bank Card Platform promotion N1 Payment application A Balance Platform promotion N2 Payment application B any method Platform promotion N3

[0540] As shown in Table 3, the promotional information may include platform promotional activities corresponding to one or more payment methods. For example, payment application A may include two payment methods: AA bank card and balance. The platform promotional activity for AA bank card payment is platform promotional activity N1 (e.g., 5 RMB off for purchases over 50 RMB), and the promotional activity for balance payment is platform promotional activity N2. The platform promotional activity for any payment method in payment application B is platform promotional activity N3.

[0541] It is understood that the embodiments shown in Table 3 are only examples. In the embodiments of this application, the platform discount information may also include more, fewer, or different platform discount activities than those in the above embodiments. This application does not limit this.

[0542] S1125.NFC service module 12 displays platform discount information and merchant discount information 1.

[0543] In some embodiments, the NFC service module 12 can display platform discount information and merchant discount information 1 to facilitate users in choosing a suitable payment method.

[0544] In other embodiments, the NFC service module 12 may also determine and display the discount amount and / or the actual payment amount of the preferential payment methods supported by both the payment receiving device 200 and the electronic device 100 based on the platform discount information and the merchant discount information 1, so that the user can quickly select the appropriate payment method.

[0545] S1126. NFC service module 12 receives and responds to the user's selection of payment method 5, and determines the actual payment amount 5 of payment method 5 based on the discount information.

[0546] NFC service module 12 can determine to complete the payment using payment method 5 based on the user's selection of payment method 5.

[0547] After determining that payment method 5 is to be used, the NFC service module 12 can determine the actual payment amount (i.e., the actual payment amount 5) of payment method 5 based on the amount payable, platform discount information, and merchant discount information 1.

[0548] S1127. NFC service module 12 sends a payment response 5 to the receiving device. The payment response 5 includes a payment credential 5, which indicates the payment account 5 of the payment method 5.

[0549] Optionally, the payment response 4 may also include one or more of the following: payment authorization 2, an identifier of payment method 5, and the actual amount 1 of payment method 5. Payment authorization 2 is used to authorize the receiving end to deduct funds from the designated payment account 5.

[0550] The specific method by which the NFC service module 12 obtains the payment credential 5 can be referred to the relevant description in step S1113 above, and will not be repeated here.

[0551] S1128. The receiving device 200 deducts funds based on payment account 5, and the deduction amount is the actual payment amount 5.

[0552] In some embodiments, the specific process of step S1128 can also refer to the above. Figure 7 or Figure 8 The relevant descriptions in the illustrated embodiments will not be repeated here.

[0553] S1129. Payment receiving device 200 sends payment success notification 5.

[0554] The specific content of payment success notification 5 can be compared with the relevant description of payment success notification 5 in step S1115 above, and will not be repeated here.

[0555] S1130. Payment application set 11 outputs payment success message 5.

[0556] The details of step S1130 can be found in the relevant content of step S1116 above, and will not be repeated here.

[0557] In this way, electronic device 100 can complete the payment by touching the card reader area of ​​payment device 200, simplifying the payment operation, making it fast and convenient, and improving payment efficiency.

[0558] Understandable, Figure 11 The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 and the payment device 200 may also use different interaction processes to complete the payment, which is not limited here.

[0559] The following describes the functional modules of a payment cloud server 300 provided in an embodiment of this application.

[0560] Figure 12A The diagram shows a functional module schematic of a payment cloud server 300 provided in an embodiment of this application.

[0561] like Figure 12A As shown, the payment cloud server 300 may include a discount information module 1210 and a payment module 1220.

[0562] The discount information module 1210 can store discount information for different geofences. The discount information module 1210 can also receive geofence identifiers (or location information) sent by the electronic device 100, and send the discount information corresponding to the geofence identifier (or location information) to the electronic device 100. The discount information module 1210 can also update the discount information in real time based on payment crowdsourcing reported by different electronic devices 100. For example, in the above... Figure 6 In the illustrated embodiment, the payment cloud server 300 may refer to the discount information module 1210.

[0563] The payment module 1220 can interact with one or more of the electronic device 100 and the payment receiving device 200 to complete the payment. For example, in the above... Figures 7 to 8 In the illustrated embodiment, the payment cloud server 300 may refer to the payment module 1220.

[0564] Understandable, Figure 12A The illustrated embodiment is merely an example. In this application embodiment, the payment cloud server 300 may also include more, fewer, or different functional modules than those in the above embodiment, and this application does not limit the scope of the invention. Furthermore, in one possible implementation, the discount information module 1210 and the payment module 1220 may also be different servers within the payment cloud server 300, and this application does not limit the scope of the invention.

[0565] The following describes another hardware structure of an electronic device 100 provided in the embodiments of this application.

[0566] Figure 12B This illustration shows a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application.

[0567] The following description uses electronic device 100 as an example to illustrate the embodiment. It should be understood that... Figure 12B The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 12B The more or fewer components shown can be combined into two or more components, or they can have different component configurations. The various components shown in the figure can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0568] Electronic device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include one or more of the following: pressure sensor 180A, gyroscope sensor 180B, barometric pressure sensor 180C, magnetic sensor 180D, accelerometer sensor 180E, distance sensor 180F, proximity sensor 180G, fingerprint sensor 180H, temperature sensor 180J, touch sensor 180K, ambient light sensor 180L, bone conduction sensor 180M, etc.

[0569] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0570] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. Processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that processor 110 has just used or is recurring. If processor 110 needs to reuse the instruction or data, it can directly retrieve it from the memory. This avoids repeated access, reduces the waiting time of processor 110, and thus improves system efficiency.

[0571] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0572] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0573] The charging management module 140 receives charging input from the charger. The power management module 141 connects to the battery 142, and the charging management module 140 connects to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

[0574] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0575] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0576] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0577] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0578] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0579] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD). The display panel can also be manufactured using organic light-emitting diodes (OLEDs), active-matrix organic light-emitting diodes (AMOLEDs), flexible light-emitting diodes (FLEDs), miniled, microled, micro-OLEDs, quantum dot light-emitting diodes (QLEDs), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0580] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0581] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The internal memory 121 can be used to store computer-executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, phonebook, etc.). Furthermore, the internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0582] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0583] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. Gyroscope sensor 180B can be used to determine the motion posture of electronic device 100. Barometric pressure sensor 180C is used to measure air pressure. Magnetic sensor 180D includes a Hall sensor. Accelerometer sensor 180E can detect the magnitude of acceleration of electronic device 100 in various directions (generally three axes). Distance sensor 180F is used to measure distance. Proximity sensor 180G may include, for example, a light-emitting diode (LED) and a photodetector, such as a photodiode. Ambient light sensor 180L is used to sense ambient light intensity. Fingerprint sensor 180H is used to collect fingerprints. Temperature sensor 180J is used to detect temperature. Touch sensor 180K, also called a "touch panel". Touch sensor 180K can be set on display screen 194, and touch sensor 180K and display screen 194 form a touch screen, also called a "touch screen". Touch sensor 180K is used to detect touch operations applied to or near it. A touch sensor can transmit detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operation can be provided via display screen 194. In some embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194. Bone conduction sensor 180M can acquire vibration signals. Buttons 190 include a power button, volume buttons, etc. Motor 191 can generate vibration cues. Indicator 192 may be an indicator light, used to indicate charging status, battery level changes, or to indicate messages, missed calls, notifications, etc.

[0584] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0585] In some embodiments, the wireless communication module 160 can specifically be used to establish a short-range wireless communication link with the payment device 200, so that the two can perform short-range wireless data transmission with each other. Exemplarily, the aforementioned short-range wireless communication link can be a Bluetooth link, a Wi-Fi link, an NFC link, etc. Therefore, the wireless communication module 160 can specifically include a Bluetooth communication module, a Wi-Fi communication module, or an NFC module. The NFC module can include any suitable components for enabling proximity-based contactless communication between the electronic device 100 and the payment device 200, thereby providing NFC functionality to the electronic device 100. A description of the NFC module can be found above. Figure 3A The embodiments shown are not described in detail here.

[0586] The foregoing details the method provided in this application. In order to facilitate better implementation of the above-described solutions in the embodiments of this application, the embodiments of this application also provide corresponding devices or equipment.

[0587] This application embodiment can divide the electronic device 100 and the payment device 200 into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0588] The following will combine Figures 13 to 16 The communication device of the embodiments of this application is described in detail.

[0589] In the case of using integrated units, see Figure 13 , Figure 13 This is a schematic diagram of the structure of the communication device 1300 provided in an embodiment of this application. The communication device 1300 can be the electronic device 100 in the above embodiments. Optionally, the communication device 1300 can be a chip / chip system, such as an NFC chip. Figure 13 As shown, the communication device 1300 may include a transceiver unit 1310 and a processing unit 1320.

[0590] The transceiver unit 1310 can also be used to perform NFC sending and NFC receiving functions performed by the electronic device 100 in the above embodiments of this application.

[0591] Optionally, the processing unit 1320 can also be used to perform functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow, and display, which are performed by the electronic device 100 in the above embodiments of this application.

[0592] It should be understood that the communication device 1300 in this design can perform the method steps executed by the electronic device 100 in the aforementioned embodiments, and for the sake of brevity, it will not be described again here.

[0593] In the case of using integrated units, see Figure 14 , Figure 14 This is a schematic diagram of the structure of the communication device 1400 provided in an embodiment of this application. The communication device 1400 can be the payment receiving device 200 in the above embodiments. Optionally, the communication device 1400 can be the payment receiving device 200. For example... Figure 14 As shown, the communication device 1400 may include a transceiver unit 1410 and a processing unit 1420.

[0594] Optionally, the transceiver unit 1410 can also be used to perform NFC sending and NFC receiving functions performed by the payment device 200 in the above embodiments of this application.

[0595] Optionally, the processing unit 1420 can also be used to execute the functional steps related to NFC protocol parsing and encapsulation, and NFC service processing flow executed by the payment receiving device 200 in the above embodiments of this application.

[0596] It should be understood that the communication device 1400 in this design can perform the method steps executed by the payment device 200 in the aforementioned embodiment, and for the sake of brevity, it will not be described in detail here.

[0597] The above describes the electronic device 100 and the payment device 200 according to embodiments of this application. It should be understood that any device possessing the above-described features... Figure 13 Any product of any form that possesses the functions of the aforementioned electronic device 100, but whichever possesses the above-mentioned... Figure 14 Any form of the payment device 200 that performs the functions described herein falls within the protection scope of the embodiments of this application.

[0598] As one possible product form, the electronic device 100 described in this application embodiment can be implemented using a general bus architecture.

[0599] See Figure 15 , Figure 15 This is a schematic diagram of the structure of the communication device 1500 provided in an embodiment of this application. The communication device 1500 may be an electronic device 100, or a device therein. Figure 15As shown, the communication device 1500 includes a processor 1501 and a transceiver 1502 internally connected and communicating with the processor 1501. The processor 1501 can be a general-purpose processor or a dedicated processor, such as a central processing unit and / or an NFC controller. The transceiver 1502, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1502 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function, such as an NFC receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function, such as an NFC transmitting function. Optionally, the communication device 1500 may also include an antenna 1503 and / or a radio frequency unit (RF unit). Figure 15 (Not shown in the image), for example, an NFC antenna, where the NFC antenna can be a coil-type antenna. The antenna 1503 and / or the radio frequency unit can be located inside the communication device 1500 or separate from the communication device 1500, that is, the antenna 1503 and / or the radio frequency unit can be remotely or distributedly deployed.

[0600] Optionally, the communication device 1500 may include one or more memories 1504, which may store instructions, which may be computer programs, that can be executed on the communication device 1500 to cause the communication device 1500 to perform the method steps described in the above embodiments of this application. Optionally, the memory 1504 may also store data. The communication device 1500 and the memory 1504 may be provided separately or integrated together.

[0601] The processor 1501, transceiver 1502, and memory 1504 can be connected via a communication bus.

[0602] In one design, the communication device 1500 can be used to perform the functions of the electronic device 100 in the foregoing embodiments: the processor 1501 can be used to perform the functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow and display performed by the electronic device 100 in the foregoing embodiments of this application and / or other processes used in the technology described herein; the transceiver 1502 can be used to perform the functional steps related to NFC sending and NFC receiving performed by the electronic device 100 in the foregoing embodiments of this application and / or other processes used in the technology described herein.

[0603] In any of the above designs, the processor 1501 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0604] In any of the above designs, the processor 1501 may store instructions, which may be computer programs. These computer programs, running on the processor 1501, cause the communication device 1500 to execute the method steps performed by the electronic device 100 in the above embodiments of this application. The computer program may be embedded in the processor 1501; in this case, the processor 1501 may be implemented in hardware.

[0605] In one implementation, the communication device 1500 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide-semiconductor (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0606] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 15 The communication device 1500 may be a standalone device or part of a larger device. For example, the communication device 1500 may be:

[0607] (1) A standalone integrated circuit IC, or chip, or chip system or subsystem; (2) A collection of one or more ICs, optionally including storage components for storing data or computer programs; (3) An ASIC, such as an NFC chip; (4) A module that can be embedded in other devices; (5) A receiver, terminal, smart terminal, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) Others, etc.

[0608] As one possible product form, the payment device 200 described in this application embodiment can be implemented using a general bus architecture.

[0609] See Figure 16 , Figure 16 This is a schematic diagram of the communication device 1600 provided in an embodiment of this application. The communication device 1600 may be a payment receiving device 200, or a device thereof. Figure 16 As shown, the communication device 1600 includes a processor 1601 and a transceiver 1602 internally connected and communicating with the processor 1601. The processor 1601 can be a general-purpose processor or a dedicated processor, such as an NFC controller. The transceiver 1602, also known as a transceiver unit, transceiver, or transceiver circuit, is used to implement transceiver functions. The transceiver 1602 may include a receiver and a transmitter. The receiver, also known as a receiver circuit, is used to implement a receiving function; the transmitter, also known as a transmitter or transmitting circuit, is used to implement a transmitting function. Optionally, the communication device 1600 may also include an antenna 1603 and / or a radio frequency unit (not shown in the figure). The antenna 1603 and / or the radio frequency unit may be located inside the communication device 1600 or separate from it; that is, the antenna 1603 and / or the radio frequency unit may be remotely or distributedly deployed.

[0610] Optionally, the communication device 1600 may include one or more memories 1604, which may store instructions, which may be computer programs, that can be executed on the communication device 1600 to cause the communication device 1600 to perform the method steps described in the above embodiments of this application. Optionally, the memory 1604 may also store data. The communication device 1600 and the memory 1604 may be provided separately or integrated together.

[0611] The processor 1601, transceiver 1602, and memory 1604 can be connected via a communication bus.

[0612] In one design, the communication device 1600 can be used to perform the functions of the payment receiving device 200 in the aforementioned embodiments: the processor 1601 can be used to perform the above-mentioned functions. Figure 16 The payment device 200 in the illustrated embodiment performs functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow, and / or other processes used in the technology described herein; the transceiver 1602 can be used to perform the above. Figure 16 The payment device 200 in the illustrated embodiment performs functional steps related to NFC sending and NFC receiving, and / or other processes used in the technology described herein.

[0613] In any of the above designs, the processor 1601 may include a transceiver for implementing receive and transmit functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receive and transmit functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0614] In any of the above designs, the processor 1601 may store instructions, which may be computer programs. These computer programs, running on the processor 1601, cause the communication device 1600 to execute the method steps performed by the receiving device 200 in the above method embodiments. The computer program may be embedded in the processor 1601; in this case, the processor 1601 may be implemented in hardware.

[0615] Figure 17 A flowchart illustrating a payment method provided in an embodiment of this application is shown.

[0616] like Figure 17 As shown, the specific process of a payment method provided in this application embodiment may include the following steps:

[0617] S1701. After entering the radio frequency field of the first merchant's payment device, the electronic device receives a first payment request sent by the payment device. The first payment request includes the first identifier of the first merchant and a first amount.

[0618] The electronic device can be the electronic device 100 in the above embodiments, and the payment device can be the payment device 200 in the above embodiments.

[0619] For example, the first identifier of the first merchant can be a merchant ID, and the first amount can refer to the amount payable, i.e., the amount that the payment receiving device should collect. The first payment request can be as described above. Figure 5 The payment request 1 in the illustrated embodiment can also be the one described above. Figure 9 The payment request 2 in the illustrated embodiment can also be the one described above. Figure 10 The payment request 3, etc., in the illustrated embodiment will not be described again here.

[0620] S1702. The electronic device determines one or more promotional activities of the first merchant based on the first payment request.

[0621] For example, one or more promotional activities of the first merchant can be as described above. Figure 9 Promotional activity 1 in the illustrated embodiment.

[0622] S1703. The electronic device determines one or more payment methods supported by the receiving device based on the first payment request.

[0623] Steps S1702 and S1703 can be executed simultaneously, or one can be executed first and then the other. This application does not limit the execution order of steps S1702 and S1703.

[0624] S1704. An electronic device determines a first payment method from one or more payment methods supported by a first merchant based on one or more promotional activities of the first merchant.

[0625] For example, the first payment method can be as described above. Figure 5 Payment method 1 in the illustrated embodiment can also be the one described above. Figure 9 Payment method 1 in the illustrated embodiment can also be the one described above. Figure 10 Payment method 3, etc., in the illustrated embodiment will not be described again here.

[0626] S1705. The electronic device completes payment via the first payment method.

[0627] In this way, electronic devices can determine the final payment method (i.e., the primary payment method) based on the merchant's promotional activities and complete the payment using that method. When purchasing the same product, users will spend less money compared to not taking advantage of merchant promotions, thus reducing unnecessary expenses.

[0628] In one possible implementation, determining one or more promotional activities of the first merchant based on the first payment request specifically includes: sending a first identifier to the first server; and receiving one or more promotional activities of the first merchant sent by the first server.

[0629] The first server may be the payment cloud server 300 in the above embodiments. In some embodiments, the first server may be the one described above. Figure 12A The example shown is the discount information module 1210 in the payment cloud server 300.

[0630] In this way, electronic devices can obtain promotional offers from a first merchant based on the first merchant's first identifier from a first server. The first server can store promotional offers from one or more merchants.

[0631] In one possible implementation, the first payment request may also include one or more promotional offers from the first merchant.

[0632] In this way, when the electronic device interacts with the payment device, it can receive promotional offers from the first merchant sent by the payment device, without needing to obtain them from the first server. Furthermore, the promotional offers sent by the payment device are real-time offers from the first merchant, eliminating the possibility of any delays.

[0633] In one possible implementation, before entering the radio frequency field of the first merchant's payment device, the method further includes: receiving first promotional information sent by a first server, the first promotional information including promotional activities of one or more merchants; determining one or more promotional activities of the first merchant based on a first payment request, specifically including: determining one or more promotional activities of the first merchant from the first promotional information based on a first identifier.

[0634] For example, the first discount information may be the merchant discount information 1 in the above embodiments.

[0635] In this way, before a user makes a purchase, the electronic device can obtain promotional offers from one or more merchants from a first server. When the user pays through the electronic device, the first merchant's promotional offer is determined from these offers, and the payment is completed. By obtaining promotional offers from multiple merchants in advance, there is no need to retrieve the first merchant's offer during the payment process, which shortens the interaction steps and improves payment efficiency.

[0636] In one possible implementation, before receiving the first offer information sent by the first server, the method further includes: when the electronic device enters the first geofence, sending a first request to the first server, the first request carrying an identifier of the first geofence, the first request being used to request the first server to send the first offer information, one or more merchants being located within the first geofence.

[0637] For example, the first geofence can be as described above. Figure 6 , Figure 9 Geofencing A1 in the embodiments.

[0638] When an electronic device enters the first geofence, it can obtain the first set of promotional information for that geofence. This information can include promotional activities from one or more merchants within the first geofence. This allows users to see real-time promotional offers from nearby merchants and decide whether to go shopping.

[0639] In one possible implementation, after receiving the first offer information sent by the first server, the method further includes: displaying the first offer information.

[0640] For example, the specific method by which an electronic device displays the first offer information can be referred to the above. Figure 6 The relevant descriptions in the illustrated embodiments.

[0641] In this way, after obtaining the initial offer information, electronic devices can push the offer to users, who can then decide whether to shop at the designated merchant based on this information. Furthermore, pushing initial offer information can also bring customer traffic to merchants.

[0642] In one possible implementation, determining one or more payment methods supported by the payment device based on the first payment request specifically includes: obtaining one or more payment methods supported by the payment device based on the first identifier.

[0643] In this way, one or more payment methods supported by the payment device can be obtained based on the first identifier of the first merchant. For example, one or more payment methods supported by the payment device can be obtained from the first server (or other server) based on the first identifier.

[0644] In one possible implementation, the first payment request may also include an identifier of one or more payment methods supported by the receiving device.

[0645] In this way, one or more payment methods supported by a payment device can be determined based on the identifiers of the payment methods supported by one or more payment devices carried in the first payment request.

[0646] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a first payment response to a receiving device. The first payment response includes a first payment credential, which indicates a first payment account for the first payment method.

[0647] For example, as described above Figure 5 In the illustrated embodiment, for example, the first payment response can be payment response 1, the first payment credential can be payment credential 1, and the first payment account can be payment account 1. Furthermore, exemplarily, using the above... Figure 9 In the illustrated embodiment, the first payment response can be payment response 2, the first payment credential can be payment credential 1, and the first payment account can be payment account 1. As another example, using the above... Figure 10 In the example shown, the first payment response can be payment response 3, the first payment credential can be payment credential 3, the first payment account can be payment account 3, etc., which will not be elaborated here.

[0648] In this way, the electronic device can send a payment credential to the receiving device, which then sends the payment credential to the second server, which completes the payment. The second server can be the payment cloud server 300 in the above embodiment, such as the one described above. Figure 12A The payment module 1220 in the payment cloud server 300 in the illustrated embodiment.

[0649] In one possible implementation, the first payment request further includes a first receiving account; completing the payment through a first payment method specifically includes: determining a second amount corresponding to the first payment method based on a first amount and one or more promotional activities of the first merchant; sending a second payment response to a second server, the second payment response including a first payment credential, a second amount, and a first receiving account, the first payment credential being used to indicate the first payment account of the first payment method.

[0650] The primary receiving account refers to the receiving account of the payment receiving device; for a detailed description of its functions, please refer to the above. Figure 7 or Figure 8 The relevant description in the illustrated embodiment. The second amount refers to the actual amount paid for the electronic device.

[0651] When an electronic device interacts with a payment device, the electronic device can receive the payment account information sent by the payment device. Furthermore, the electronic device can determine the payment method, payment account, and actual payment amount (i.e., the second amount) based on the merchant's promotional activities. In this case, the electronic device can interact with a second server, sending information such as the payment account, actual payment amount, and payment voucher to the second server to complete the payment. In this way, the electronic device no longer needs to interact with the second server through the payment device.

[0652] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a third payment response to a second server. The third payment response includes a first payment credential, which indicates a first payment account for the first payment method.

[0653] In this scenario, the electronic device can send a first payment credential to the second server via a communication connection; additionally, the receiving device can also send a receiving account to the second server, which will then complete the payment based on the information sent by the electronic device and the receiving device.

[0654] In one possible implementation, the first payment credential is also used to indicate the first payment method.

[0655] In this way, the first payment receipt can inform the receiving device or electronic device of the final payment method.

[0656] In one possible implementation, the first payment response also includes an identifier of the first payment method.

[0657] In this way, the payment method identifier can inform the receiving device of the final payment method used by the electronic device.

[0658] In one possible implementation, determining a first payment method from one or more payment methods based on one or more promotional activities of a first merchant specifically includes: determining the discount amount for each of the one or more payment methods based on one or more promotional activities of the first merchant; displaying one or more payment options, the one or more payment options including a first option corresponding to the first payment method, the first option including an identifier of the first payment method and the discount amount of the first payment method; receiving and responding to the user's operation on the first option, and determining the first payment method.

[0659] For example, the one or more payment options can be as described above. Figure 4E One or more payment options in the illustrated embodiment, such as AA bank card option 431, payment application A option 432, payment application B option 433, etc.

[0660] In this way, electronic devices can display the discount amount (or actual payment amount) for one or more payment methods based on the merchant's promotional activities, so that users can choose the appropriate payment method to complete the payment.

[0661] In one possible implementation, a first payment method is determined from one or more payment methods based on one or more promotional activities of the first merchant. Specifically, this includes: determining the discount amount for each of the one or more payment methods based on one or more promotional activities of the first merchant; and determining the first payment method based on the discount amount for each of the one or more payment methods, wherein the first payment method is the payment method with the largest discount amount among the one or more payment methods.

[0662] In this scenario, the electronic device can determine the payment method with the largest discount (or smallest actual payment) after identifying the discount amount and / or actual payment amount for each payment method supported by the receiving device, and complete the payment based on that method. This eliminates the need for the user to make any additional selection and ensures that the user receives the maximum discount.

[0663] In one possible implementation, the method further includes: receiving a first notification sent by a second server, the first notification being used to notify the electronic device of successful payment. The first notification may be a payment notification as described in the above embodiments (e.g., ...). Figure 7 Payment notification 1, etc., in the illustrated embodiment.

[0664] In this way, the electronic device can determine whether the payment was successful based on the first notification sent by the second server.

[0665] In one possible implementation, the method further includes: receiving a first notification sent by the receiving device, the first notification being used to notify the electronic device that the payment was successful. For example, the first notification may be as described above. Figure 9 The payment success notification 1 in the illustrated embodiment can also be the one described above. Figure 11 Payment success notification 3 in the illustrated embodiment, etc.

[0666] In this way, electronic devices can determine whether the payment was successful based on the first notification sent by the receiving device.

[0667] In one possible implementation, the method further includes: determining a first promotional activity from one or more promotional activities of a first merchant based on a first payment method; after completing payment using the first payment method through a first payment account, the method further includes: sending a first crowdsourcing to a first server, the first crowdsourcing including the location information of the electronic device, a first identifier of the first merchant, and the first promotional activity.

[0668] The first type of crowdsourcing can be the one mentioned above. Figure 9 Payment crowdsourcing 1 in the illustrated embodiment.

[0669] In this way, after the electronic device determines the final payment method, it can report the payment crowdsourcing to the first server. The payment crowdsourcing is used to instruct the first server to update the first merchant's promotional activities stored on the first server based on the payment crowdsourcing.

[0670] In one possible implementation, the first notification includes a first amount and / or a second amount, the first amount being the amount received by the receiving device and the second amount being the amount paid by the electronic device; the first crowdsourcing also includes the first amount and / or the second amount.

[0671] The payment crowdsourcing reported by electronic devices may also include the actual amount paid and / or the amount received, so that the first server can confirm the specific discount details of the first merchant's promotional activities.

[0672] In one possible implementation, after determining the first promotional activity from one or more promotional activities of the first merchant based on the first payment method, the method further includes: sending the first promotional activity to the receiving device.

[0673] For example, the first promotional activity could be as described above. Figure 9 Promotional activity 2 in the illustrated embodiment.

[0674] This way, once the promotional offer is determined, it can be sent to the payment device so that the device can check whether the offer is still valid.

[0675] In one possible implementation, after entering the radio frequency field of the receiving device, the method further includes: receiving a probe frame sent by the receiving device, the probe frame indicating that the receiving device supports a specified NFC protocol; sending a probe ACK frame to the receiving device, the probe ACK frame indicating that the electronic device supports the specified NFC protocol; receiving a pick frame sent by the receiving device, the pick frame carrying device characteristic information of the receiving device, the device characteristic information including a service identifier and a device organization identifier, wherein the service identifier indicates the type of NFC service supported by the receiving device, and the device organization identifier indicates the manufacturer using the receiving device to provide NFC services; determining, based on the device characteristic information of the receiving device, that the type of NFC service of the receiving device is codeless payment; and sending a pick ACK frame to the receiving device, the pick ACK frame indicating that the electronic device has determined the NFC service type of the receiving device.

[0676] In this way, electronic devices can interact with the receiving device through the first protocol based on NFC technology to determine the NFC service type of the receiving device.

[0677] Figure 18 A flowchart illustrating another payment method provided in an embodiment of this application is shown.

[0678] like Figure 18 As shown, the specific process of the payment method may include the following steps:

[0679] S1801. After entering the radio frequency field of the first merchant's payment device, the electronic device receives a first payment request sent by the payment device. The first payment request includes the first identifier of the first merchant and a first amount.

[0680] S1802. The electronic device determines one or more promotional activities of the first merchant based on the first payment request.

[0681] S1803. The electronic device determines, based on a first payment request, an identifier of one or more payment methods supported by the receiving device.

[0682] S1804. An electronic device determines a first payment method from one or more payment methods based on one or more promotional activities of a first merchant.

[0683] S1805. An electronic device determines a first promotional activity from one or more promotional activities based on a first payment method.

[0684] S1806. The electronic device sends a fourth payment response to the receiving device, the fourth payment response including a first payment credential and a first promotional offer, the first payment credential indicating a first payment account for a first payment method.

[0685] The specific details of steps S1801 to S1806 can also be found above. Figure 17 The relevant steps in the illustrated embodiment will not be repeated here.

[0686] S1807. An electronic device receives second promotional information sent by a payment receiving device, the second promotional information including one or more promotional activities of a first merchant.

[0687] For example, the second preferential information can be as described above. Figure 9 Merchant discount information 2 in the illustrated embodiment.

[0688] S1808. The electronic device determines the second payment method and the second promotional activity based on the second promotional information.

[0689] For example, the second payment method can be as described above. Figure 9 Payment method 2 in the illustrated embodiment.

[0690] The second promotional offer is a discount available when using a second payment method on electronic devices.

[0691] S1809. Electronic devices complete payment via a second payment method.

[0692] Using this payment method, if the first promotional offer that the electronic device was about to enjoy expires, the electronic device can receive a second promotional offer from the receiving device. This second offer is the real-time promotional offer from the first merchant. The electronic device can then redetermine the payment method based on this second offer (i.e., the second payment method) and complete the payment using it. This avoids payment failures caused by the electronic device paying based on an expired promotional offer.

[0693] In one possible implementation, the payment is completed via a second payment method, which further includes sending a second crowdsourcing package to a first server. The second crowdsourcing package includes the location information of the electronic device, a first identifier of the first merchant, and second promotional information.

[0694] Upon receiving a second discount information from the payment receiving device, the electronic device can include this second discount information when reporting to the payment crowdsourcing platform. This allows the first server to update the first merchant's promotional activities stored on the first server based on the second discount information. In this way, when other users subsequently shop at the first merchant, they can access the merchant's real-time promotional activities instead of receiving expired ones.

[0695] The following describes the specific process of a payment method provided in an embodiment of this application.

[0696] Figure 19A flowchart illustrating a payment method provided in an embodiment of this application is shown.

[0697] like Figure 19 As shown, the specific process of a payment method provided in this application embodiment may include the following steps:

[0698] S1901. Electronic device 100 Obtain merchant discount information 1.

[0699] In some embodiments, when an electronic device (also referred to as electronic device 100) enters a first geofence, it sends a first request to a first server. The first request carries an identifier of the first geofence and is used to request the first server to send first discount information (also referred to as merchant discount information 1). Receiving the first discount information sent by the first server specifically includes receiving a first response sent by the first server, the first response including the first discount information. The first server may be the payment cloud server 300 in the above embodiments, or the first server may be the aforementioned... Figure 12A The example shown is the discount information module 1210 in the payment cloud server 300.

[0700] S1902. Electronic device 100 enters the radio frequency field of receiving device 200.

[0701] S1903. The receiving device 200 sends a probe frame to the electronic device 100.

[0702] S1904. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0703] The details of steps S1901-S1904 can be found above. Figure 5 The relevant descriptions of steps S501-S504 shown are not repeated here.

[0704] S1905. After receiving the Probe ACK frame, the payment device 200 sends a Notify frame. The Notify frame carries the merchant ID and device characteristic information of the payment device 200. The device characteristic information is used to indicate that the service type of the payment device 200 is codeless payment.

[0705] In one possible implementation, the Notify frame may carry the merchant ID and device characteristic information of the receiving device 200.

[0706] In another possible implementation, the device characteristic information may include a device organization identifier (ND_OUI), which can be used to indicate the manufacturer providing NFC services using the payment device 200. In this case, since the device organization identifier can also be used to indicate the merchant ID, the Notify frame does not need to carry the merchant ID. The specific content of the device characteristic information can be found above. Figure 5 The relevant content in step S505 shown will not be repeated here.

[0707] In some embodiments, the electronic device 100 can determine the service type as codeless payment based on the device feature information of the payment device 200. For details, please refer to the above. Figure 5 The relevant description of step S506 shown will not be repeated here.

[0708] S1906. Electronic device 100 sends a Notify ACK frame.

[0709] In some embodiments, after determining the service type of the receiving device 200, the electronic device 100 may send a Notify ACK frame to the receiving device 200. The Notify ACK frame can be used to indicate that the electronic device 100 has determined the NFC service type of the receiving device 200.

[0710] In some embodiments, the Notify ACK frame can be used to inform the receiving device 200 that the electronic device 100 has received the Notify frame.

[0711] S1907. Payment device 200 sends parameter negotiation command.

[0712] In some embodiments, after receiving a Notify ACK frame, the receiving device 200 can send a parameter negotiation command to the electronic device 100 via NFC. The parameter negotiation command is used to negotiate the transmission parameters of the application layer with the electronic device 100.

[0713] In some embodiments, the frame type of the parameter negotiation command can be a command frame.

[0714] In some embodiments, data transmission parameters may include one or more of the following: maximum transmission rate and maximum data transmission length when performing application layer data transmission.

[0715] S1908. Electronic device 100 sends parameter negotiation response.

[0716] In some embodiments, the electronic device 100 may send a parameter negotiation response to the receiving device 200 via NFC in response to a parameter negotiation command. This parameter negotiation response can be used to negotiate data transmission parameters at the application layer with the receiving device 200. The specific content of the data transmission parameters can be found in the description of step S1907 above.

[0717] In some embodiments, the frame type of the parameter negotiation response can be a response frame.

[0718] In this way, the payment device 200 and the electronic device 100 can negotiate the transmission parameters at the application layer. Based on the negotiated transmission parameters, the payment device 200 can interact with the electronic device 100 at the application layer via NFC. That is, in step S1909 and subsequent steps, the payment device 200 can interact with the electronic device 100 at the application layer via NFC.

[0719] S1909. The receiving device 200 sends selection command 1, which is used to select a payment service.

[0720] The payment device 200 can send a selection command 1 (also known as the first selection command) to the electronic device 100 via NFC.

[0721] The electronic device 100 can support various NFC services. For example, it can support payment services, access control services, car key services, bank card services, electronic ticket services, and digital ID card services.

[0722] The receiving device 200 can use command 1 to instruct the electronic device 100 and the receiving device 200 to perform a payment transaction.

[0723] S1910. Electronic device 100 sends a selection response 1 based on the merchant ID, the selection response 1 carrying the identifier of one or more payment applications supported by electronic device 100.

[0724] After receiving the selection command 1, the electronic device 100 can send a selection response 1 (also known as the first selection response) to the payment device 200 via NFC.

[0725] In some embodiments, after receiving selection command 1, electronic device 100 can obtain the merchant ID of payment receiving device 200 based on the Notify frame, and determine the identifiers of one or more payment applications carried in selection response 1 based on the merchant ID and the payment applications installed on electronic device 100. For example, electronic device 100 can determine whether it has a membership card for that merchant based on the merchant ID, etc. If it is determined that electronic device 100 has a membership card for that merchant, the identifiers of one or more payment applications carried in selection response 1 may include identifiers for membership card payments. Optionally, selection response 1 may also carry capability information of one or more payment applications supported by electronic device 100. The capability information can be used to indicate the payment capabilities of the payment applications. The higher the payment capability, the higher the priority of the payment application being selected for use. In some embodiments, capability information may include priority and / or preferential information. Priority is used to indicate the priority level set by electronic device 100 for the payment applications. It should be noted that the priority can be a preset priority of the electronic device 100, or a priority updated by the electronic device 100 based on the merchant ID. For example, if the electronic device 100 has a membership card for that merchant, the priority of membership card payment can be set to the highest, and so on. In other embodiments, the electronic device 100 can also update the priority ranking of payment applications based on the merchant ID and discount information. For example, the priority of payment applications with higher discounts can be set to high priority, or the priority of membership card payment can be set to high priority, and so on. The receiving device 200 can determine the target payment application based on the capability information of one or more payment applications supported by the electronic device 100.

[0726] In one example, the identifiers of one or more payment applications supported by electronic device 100 in the selection response 1 can be sorted according to priority. Specifically, electronic device 100 can receive and respond to user input in advance to set the priority of the one or more payment applications supported by electronic device 100. The higher the priority of the payment application's identifier, the earlier it appears in the selection response 1. Optionally, electronic device 100 can also receive user input to set the one or more payment applications supported by electronic device 100.

[0727] In one example, the number of identifiers of one or more payment applications supported by electronic device 100 in response 1 can be a preset value (e.g., 5).

[0728] For example, electronic device 100 may support up to 10 payment applications. The user can assign these 10 payment applications a priority order from highest to lowest on electronic device 100: Payment Application A1, Payment Application A2, Payment Application A3, Payment Application A4, Payment Application A5, Payment Application A6, Payment Application A7, Payment Application A8, Payment Application A9, and Payment Application A10. Due to the data size limit in Select Response 1, electronic device 100 can select the identifiers of the top 5 payment applications from the 10 applications, from highest to lowest priority, to include in Select Response 1. Therefore, one or more payment applications supported by electronic device 100 in Select Response 1 may include Payment Application A1, Payment Application A2, Payment Application A3, Payment Application A4, and Payment Application A5.

[0729] In one example, the selected response 1 may include an application list field and a capability set field. The application list field may include identifiers of one or more payment applications supported by the electronic device 100. The capability set field may include a priority field and / or a discount information field. The priority field may include the priority of one or more payment applications supported by the electronic device 100. The discount information field may include discount information for one or more payment applications supported by the electronic device 100.

[0730] Alternatively, response 1 may also carry merchant offer information 1 (also known as the first offer information) or merchant offer information 2 (also known as the second offer information).

[0731] In some embodiments, merchant offer information 2 refers to offer information from the merchant to which the payment device 200 belongs. In one possible implementation, after determining the merchant ID based on the Notify frame, the electronic device 100 can filter out merchant offer information 2 from merchant offer information 1 based on the merchant ID.

[0732] In other embodiments, merchant discount information 2 may also refer to discount information filtered by electronic device 100 from merchant discount information 1 based on the discount activities of the payment application supported by electronic device 100 and the merchant ID. For example, electronic device 100 may first filter out the discount information of the merchant to which payment receiving device 200 belongs from merchant discount information 1 based on the merchant ID, and then filter out the intersection of the two from the discount information of the merchant to which payment receiving device 200 belongs based on the discount activities of the payment application supported by electronic device 100, that is, determine the discount activities that electronic device 100 can enjoy in this payment process.

[0733] S1911. The payment device 200 determines the target payment application 1 and the payment amount based on the payment application supported by the electronic device 100, the payment application supported by the payment device 200, and the merchant discount information 2.

[0734] In some embodiments, the payment applications supported by both electronic device 100 and payment device 200 may include one or more payment applications with promotional activities, where the actual payment amount is less than the amount due. In some embodiments, the payment applications supported by both electronic device 100 and payment device 200 may not include payment applications with promotional activities, in which case the actual payment amount equals the amount due.

[0735] In one possible implementation, the receiving device 200 can receive the identifiers and promotional information of one or more payment applications supported by the electronic device 100. Then, based on the payment applications supported by the electronic device 100, the receiving device 200 determines one or more payment applications supported by both the receiving device 200 and the electronic device 100, and combines this with the merchant promotional information 2 to determine the actual payment amount for each of these payment applications. The receiving device 200 then selects the payment application with the lowest actual payment amount as the target payment application 1 (also called the first payment application), and the actual payment amount of the target payment application 1 becomes the final payment amount.

[0736] In other possible implementations, the receiving device 200 may also determine the final target payment application 1 based on the priority of each payment application, such as prioritizing membership card payments, which is not limited here. For example, both the receiving device 200 and the electronic device 100 support payment applications including payment application A1, payment application A2, and payment application A3. Among them, payment application A2 offers a greater discount than payment application A1, and payment application A1 offers a greater discount than payment application A3. Therefore, the receiving device 200 can choose payment application A2 as the final target payment application 1. As another example, both the receiving device 200 and the electronic device 100 support payment applications including payment application A1, payment application A2, and payment application A3. Among them, payment application A1 has a higher priority than payment application A2, and payment application A2 has a higher priority than payment application A3. Payment application A2 offers a greater discount than payment application A1, and payment application A1 offers a greater discount than payment application A3. The payment receiving device 200 can use payment application A1 as the target payment application. Alternatively, the payment receiving device 200 can use payment application A2 as the final target payment application 1. For example, both the payment receiving device 200 and the electronic device 100 support payment applications including payment application A1, payment application A2, and payment application A3. Payment application A1 has a higher priority than payment application A2, and payment application A2 has a higher priority than payment application A3. The discount offered by payment application A1 is the same as that of payment application A2, and the discount offered by payment applications A1 and A2 is greater than that of payment application A3. Therefore, the payment receiving device 200 can use payment application A1 as the final target payment application 1.

[0737] It is understood that the embodiments described here are just examples. In the embodiments of this application, the payment device 200 may also adopt a different approach than the above embodiments to select the final target payment application 1 from the payment applications supported by both the payment device 200 and the electronic device 100. This application does not limit this.

[0738] It should be noted that merchant discount information 2 can refer to the promotional activities of the merchant corresponding to the payment device 200 at the current moment (i.e., when the electronic device 100 enters the radio frequency field of the payment device 200). Merchant discount information 1 can include merchant discount information 2. In one possible implementation, the payment device 200 can pre-store merchant discount information 2. In another possible implementation, the payment device 200 can receive merchant discount information 1 sent by the electronic device 100, and then filter out merchant discount information 2 from merchant discount information 1 based on the merchant ID.

[0739] S1912. The receiving device 200 sends a selection command 2, which carries the identifier of the target payment application 1.

[0740] The payment device 200 can send a selection command 2 (also known as a second selection command) to the electronic device 100 via NFC.

[0741] Select command 2 is used to instruct the electronic device to select target payment application 1 for NFC transactions.

[0742] S1913. Electronic device 100 sends selection response 2, which indicates that electronic device 100 has successfully selected target payment application 1.

[0743] After receiving the selection command 2, the electronic device 100 can send a selection response 2 (also known as the second selection response) to the payment device 200 via NFC.

[0744] S1914. The receiving device 200 sends order command 1, which carries order information 1.

[0745] In some embodiments, after receiving the selection response 2, the payment device 200 can send an order command 1 (also known as the first order command) to the electronic device 100 via NFC.

[0746] The order information 1 may include the order identifier and payment amount of payment order 1. After receiving the selection response 2, the receiving device 200 can send an order request 1 to the server of the target payment application 1. Order request 1 requests the server of the target payment application 1 to generate payment order 1. Order request 1 may carry the identifier of the target receiving account logged into the target payment application 1 by the receiving device 200 and the payment amount. Upon receiving the order request, the server of the target payment application 1 can generate payment order 1 based on the identifier of the target receiving account logged into the target payment application 1 by the receiving device 200 and the payment amount. Payment order 1 includes an order identifier, the identifier of the target receiving account, and the payment amount. The server of the target payment application 1 can send the order identifier of payment order 1 to the receiving device 200.

[0747] The payment amount can be determined by the payment receiving device 200. The payment receiving device 200 can receive the payment amount entered by the merchant, or it can determine the payment amount based on the price information of the goods purchased by the user.

[0748] In one possible implementation, to prevent order information from being leaked, the payment device 200 can carry encrypted order information 1 in the order command 1. After receiving the order command 1, the electronic device 100 decrypts the order information 1.

[0749] S1915. Electronic device 100 sends order response 1, which indicates that electronic device 100 has received order command 1.

[0750] In some embodiments, after receiving order command 1, electronic device 100 can send order response 1 (also known as first order response) to payment device 200 via NFC, wherein order response 1 is used to indicate that electronic device 100 has received order command 1.

[0751] S1916. The receiving device 200 sends a transaction initialization command 1, which is used to obtain a payment voucher.

[0752] In some embodiments, after receiving the order response 1, the receiving device 200 can send a transaction initialization command 1 (also known as the first initialization transaction command) to the electronic device 100 via NFC. The transaction initialization command 1 is used to obtain the payment credential 1 of the target payment application 1.

[0753] In this context, different payment accounts in the target payment application 1 correspond to different payment vouchers. The server of the target payment application 1 needs to receive payment voucher 1 corresponding to the target payment account before it can deduct the payment amount from the target payment account and add the payment amount to the balance of the target receiving account.

[0754] S1917. Electronic device 100 sends transaction initialization response 1, which carries payment voucher 1.

[0755] Electronic device 100 sends transaction initialization response 1 (also known as first initialization transaction response) to payment device 200 via NFC, wherein transaction initialization response 1 carries payment voucher 1 (also known as first voucher).

[0756] Payment voucher 1 is the payment voucher corresponding to the target payment account logged in in the target payment application 1 of electronic device 100.

[0757] Among them, electronic device 100 can generate payment voucher 1 based on the target payment account logged in in the target payment application 1 of electronic device 100.

[0758] In one possible implementation, electronic device 100 can generate payment voucher 1 based on order information 1 and the target payment account logged in the target payment application 1 of electronic device 100. This allows different payment orders to have different payment vouchers, improving transaction security.

[0759] In one possible implementation, to prevent the payment voucher 1 corresponding to the target payment account from being stolen, the electronic device 100 may carry the encrypted payment voucher 1 in the transaction initialization response 1. After receiving the transaction initialization response 1, the receiving device 200 can decrypt the payment voucher 1 from the transaction initialization response 1.

[0760] In one possible implementation, if the target payment application 1 of the electronic device 100 has not enabled password-free payment, or if the payment amount exceeds the password-free amount threshold set by the target application 1, the electronic device 100 may display a payment verification interface before sending the aforementioned transaction initialization response 1 to the receiving device 200 via NFC. This payment verification interface prompts the user to complete the payment verification. After the user completes the payment verification (e.g., password verification, fingerprint verification, facial verification, etc.), the electronic device 100 then sends the aforementioned transaction initialization response 1 to the receiving device 200 via NFC.

[0761] S1918. The payment receiving device 200 initiates a payment receiving process to the server of the target payment application 1 based on the payment voucher 1 and the order information 1.

[0762] In some embodiments, after receiving the transaction initialization response 1, the payment device 200 initiates a payment process to the server of the target payment application 1 based on the payment voucher 1 and the order information 1.

[0763] The payment collection process may include: The payment collection device 200 sends a payment collection request to the server of the target payment application 1. This request may include a payment voucher 1 and order information 1. The request instructs the server of the target payment application 1 to deduct the payment amount from the balance of the target payment account corresponding to the first payment screen and to add the payment amount to the balance of the target receiving account corresponding to the order information 1. Upon receiving the payment voucher 1 and order information 1, the server of the target payment application 1 can determine the payment amount and the target receiving account from the payment order 1 based on the order information 1. The server of the target payment application 1 can verify the validity of the payment voucher 1 and, upon successful verification, determine the target payment account corresponding to the payment voucher 1. The server of the target payment application 1 can deduct the payment amount from the balance of the target payment account and add the payment amount to the balance of the target receiving account. After deducting the payment amount from the balance of the target payment account and adding the payment amount to the balance of the target receiving account, the server of the target payment application 1 can send a payment completion notification to the payment collection device 200 used by the merchant. The payment completion notification is used to indicate that payment for order 1 has been completed.

[0764] Optionally, the payment collection process may also include: after receiving the payment completion notification, the payment collection device 200 can output a payment completion prompt, which is used to inform the merchant that the payment amount has been successfully received. This payment completion prompt can be a text prompt, an audio prompt, an image prompt, a mechanical vibration prompt, or an indicator light prompt, etc.

[0765] If the server of the target payment application 1 fails to transfer the payment amount from the balance of the target payment account to the target receiving account, it can send a payment failure notification to the receiving device 200. Upon receiving the payment failure notification, the receiving device 200 can output a payment failure message to inform the merchant that the payment has failed. This message can be text-based, audio-based, image-based, mechanical vibration-based, or indicator light-based, etc.

[0766] In one possible implementation, after the server of the target payment application 1 deducts the payment amount from the balance of the target payment account and adds the payment amount to the balance of the target receiving account, it can also send a payment completion notification to the electronic device 100. The payment completion notification is used to indicate that payment for payment order 1 has been completed. Optionally, if the electronic device 100 does not receive a payment completion notification and a payment failure notification from the server of the target payment application 1 for a certain period of time, the electronic device 100 can send a first payment result retrieval request to the receiving device 200 through a first short-range communication technology, wherein the first payment result retrieval request is used to request the receiving device 200 to send a payment result to the electronic device 100. If the receiving device 200 has received a receiving completion notification from the server of the target payment application 1, the receiving device 200 can send a payment completion notification to the electronic device 100 through the first short-range communication technology after receiving the first payment result retrieval request. The first short-range communication technology may include any one or more of Bluetooth (including BLE or classic Bluetooth), Wi-Fi, UWB, etc.

[0767] After receiving a payment completion notification, the electronic device 100 can output a payment completion prompt to inform the user that the payment has been successfully made. This prompt can be text-based, audio-based, image-based, mechanical vibration-based, or indicator light-based, etc. For example, after receiving the payment completion notification, the electronic device 100 can display a payment completion page or a payment success message (e.g., as described above). Figure 4GThe payment success notification shown is 450. If the server of the target payment application 1 fails to transfer the payment amount from the balance of the target payment account to the target receiving account, it may send a payment failure notification to the electronic device 100. After receiving the payment failure notification, the electronic device 100 may display a payment failure page. This payment failure page includes a payment failure message to inform the user that the payment has failed.

[0768] In one possible implementation, if the receiving device 200 receives a payment completion notification, it can send a first transaction result command to the electronic device 100 via short-range communication technology. This first transaction result command may carry transaction success indication information, indicating that payment for the first transaction order has been completed. Upon receiving the first transaction result command, the electronic device 100 can send a first transaction result response to the receiving device 200 via short-range communication technology and display a payment success message. The first transaction result response indicates that the electronic device 100 has successfully received the first transaction result command.

[0769] If the payment receiving device 200 receives a payment failure notification, it can send a payment success notification to the electronic device 100 via a first communication technology. Upon receiving the payment success notification, the electronic device 100 can display a payment failure message. The first communication technology may include any one or more of NFC, Bluetooth, Wi-Fi, UWB, and cellular networks.

[0770] In this embodiment, if the first communication technology is NFC, the electronic device 100 can remain close to the payment receiving device 200 to ensure the transmission of the payment success notification via NFC. If the first communication technology is any one of Bluetooth, Wi-Fi, UWB, cellular, etc., after the electronic device 100 sends a transaction initialization response 1 to the payment receiving device 200 via NFC and begins displaying the payment page, the user can pick up the electronic device 100 and move it away from the payment receiving device 200. This way, the electronic device 100 does not need to be constantly close to the payment receiving device 200.

[0771] Understandable, Figure 19 The embodiments shown are merely examples. In the embodiments of this application, the electronic device 100 and the payment device 200 may use different interaction steps than those in the above embodiments to complete the payment. This application does not limit the scope of the embodiments.

[0772] The payment method provided in this application can simplify the payment process and improve payment efficiency.

[0773] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the electronic device 100 in the above-described method embodiments.

[0774] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the payment device 200 in the above-described method embodiments.

[0775] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the electronic device 100 in the above-described method embodiments.

[0776] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the payment receiving device 200 in the above-described method embodiments.

[0777] This application also provides a chip, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the electronic device 100 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0778] This application also provides a chip, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the payment receiving device 200 in any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0779] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A payment method applied to electronic devices, characterized in that, The method includes: After entering the radio frequency field of the first merchant's payment device, the system receives a first payment request sent by the payment device, the first payment request including the first merchant's first identifier and a first amount; Based on the first payment request, determine one or more promotional activities of the first merchant; Based on the first payment request, determine one or more payment methods supported by the receiving device; The first payment method is determined from one or more payment methods supported by the first merchant, based on one or more promotional activities of the first merchant; Complete the payment using the first payment method.

2. The method according to claim 1, characterized in that, The step of determining one or more promotional activities of the first merchant based on the first payment request specifically includes: Send the first identifier to the first server; Receive one or more promotional activities from the first merchant sent by the first server.

3. The method according to claim 1, characterized in that, The first payment request also includes one or more promotional offers from the first merchant.

4. The method according to claim 1, characterized in that, Before entering the radio frequency field of the first merchant's payment device, the method further includes: Receive first promotional information sent by a first server, the first promotional information including promotional activities of one or more merchants; The step of determining one or more promotional activities of the first merchant based on the first payment request specifically includes: Based on the first identifier, one or more promotional activities of the first merchant are determined from the first promotional information.

5. The method according to claim 4, characterized in that, Before receiving the first discount information sent by the first server, the method further includes: When the electronic device enters the first geofence, it sends a first request to the first server. The first request carries the identifier of the first geofence and is used to request the first server to send the first promotional information. The one or more merchants are located within the first geofence.

6. The method according to claim 4 or 5, characterized in that, After receiving the first discount information sent by the first server, the method further includes: Display the first offer information.

7. The method according to any one of claims 1-6, characterized in that, The step of determining one or more payment methods supported by the receiving device based on the first payment request specifically includes: Based on the first identifier, one or more payment methods supported by the receiving device can be obtained.

8. The method according to any one of claims 1-6, characterized in that, The first payment request also includes an identifier of one or more payment methods supported by the receiving device.

9. The method according to any one of claims 1-8, characterized in that, The payment is completed through the first payment method, specifically including: Send a first payment response to the receiving device, the first payment response including a first payment credential, the first payment credential being used to indicate a first payment account for the first payment method.

10. The method according to any one of claims 1-8, characterized in that, The first payment request also includes a first receiving account; The payment is completed through the first payment method, specifically including: The second amount corresponding to the first payment method is determined based on the first amount and one or more promotional activities of the first merchant; A second payment response is sent to a second server. The second payment response includes the first payment credential, the second amount, and the first receiving account. The first payment credential is used to indicate the first payment account of the first payment method.

11. The method according to any one of claims 1-8, characterized in that, The payment is completed through the first payment method, specifically including: A third payment response is sent to a second server, the third payment response including a first payment credential, the first payment credential being used to indicate a first payment account for the first payment method.

12. The method according to any one of claims 9-11, characterized in that, The first payment credential is also used to indicate the first payment method.

13. The method according to claim 9, characterized in that, The first payment response also includes an identifier of the first payment method.

14. The method according to any one of claims 1-13, characterized in that, The determination of the first payment method from one or more payment methods based on one or more promotional activities of the first merchant specifically includes: The discount amount for each of the one or more payment methods is determined based on one or more promotional activities offered by the first merchant; Display one or more payment options, the one or more payment options including a first option corresponding to the first payment method, the first option including the identifier of the first payment method and the discount amount of the first payment method; Receive and respond to the user's action on the first option, and determine the first payment method.

15. The method according to any one of claims 1-13, characterized in that, The determination of the first payment method from one or more payment methods based on one or more promotional activities of the first merchant specifically includes: The discount amount for each of the one or more payment methods is determined based on one or more promotional activities offered by the first merchant; The first payment method is determined based on the discount amount of each of the one or more payment methods, and the first payment method is the payment method with the largest discount amount among the one or more payment methods.

16. The method according to any one of claims 1-15, characterized in that, The method further includes: The device receives a first notification sent by a second server, which is used to notify the electronic device that the payment was successful.

17. The method according to any one of claims 1-15, characterized in that, The method further includes: The system receives a first notification from the payment device, which is used to notify the electronic device that the payment was successful.

18. The method according to claim 16 or 17, characterized in that, The method further includes: The first promotional activity is determined from one or more promotional activities of the first merchant based on the first payment method; After completing the payment using the first payment method through the first payment account, the method further includes: Send a first crowdsourcing message to a first server. The first crowdsourcing message includes the location information of the electronic device, the first identifier of the first merchant, and the first promotional activity.

19. The method according to claim 18, characterized in that, The first notification includes the first amount and / or the second amount, wherein the first amount is the amount received by the payment device and the second amount is the amount paid by the electronic device; The first crowdsourcing also includes the first amount and / or the second amount.

20. The method according to claim 18 or 19, characterized in that, After determining the first promotional activity from one or more promotional activities of the first merchant based on the first payment method, the method further includes: Send the first promotional offer to the payment receiving device.

21. The method according to any one of claims 1-20, characterized in that, After entering the radio frequency field of the payment device, the method further includes: The system receives a probe frame sent by the payment device, the probe frame being used to indicate that the payment device supports a specified NFC protocol; Send a Probe ACK frame to the receiving device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; The system receives a Pick frame sent by the payment device. The Pick frame carries the device feature information of the payment device, which includes a service identifier and a device organization identifier. The service identifier is used to indicate the type of NFC service supported by the payment device, and the device organization identifier is used to indicate the manufacturer that provides NFC services using the payment device. Based on the device feature information of the payment device, the type of NFC service of the payment device is determined to be codeless payment; Send a PickACK frame to the receiving device, the PickACK frame indicating that the electronic device has determined the NFC service type of the receiving device.

22. A payment method applied to electronic devices, characterized in that, The method includes: After entering the radio frequency field of the first merchant's payment device, the system receives a first payment request sent by the payment device, the first payment request including the first merchant's first identifier and a first amount; Based on the first payment request, determine one or more promotional activities of the first merchant; Based on the first payment request, identify one or more payment methods supported by the receiving device; The first payment method is determined from one or more payment methods based on one or more promotional activities offered by the first merchant; The first promotional activity is determined from the one or more promotional activities based on the first payment method; Send a fourth payment response to the receiving device, the fourth payment response including the first payment credential and the first promotional activity, the first payment credential being used to indicate the first payment account of the first payment method; Receive second discount information sent by the payment device, the second discount information including one or more promotional activities of the first merchant; Based on the second preferential information, the second payment method and the second preferential activity are determined; Complete the payment using the second payment method.

23. The method according to claim 22, characterized in that, The method further includes: (The text abruptly ends here, so the translation also ends here.) Send a second crowdsourcing message to the first server. The second crowdsourcing message includes the location information of the electronic device, the first identifier of the first merchant, and the second discount information.

24. A payment method applied to electronic devices, characterized in that, The method includes: Receive first promotional information sent by a first server, the first promotional information including promotional activities of one or more merchants within a first geofence, the one or more merchants including the first merchant; Receive the first merchant identifier sent by the payment device; The second discount information is determined from the first discount information based on the first merchant identifier; Send a first response to the payment device, the first response being used to indicate that the electronic device has successfully received the first merchant identifier; Receive the first selection command sent by the first merchant's payment device; Send a first selection response to the payment device, the first selection response including identifiers of one or more payment applications supported by the electronic device and the second offer information; Receive a second selection command sent by the payment device, the second selection command including the identifier of the first payment application; Send a second selection response to the payment device, the second selection response being used to indicate that the first payment application has successfully selected; Complete the payment through the first payment application.

25. The method according to claim 24, characterized in that, The method further includes: When the electronic device enters the first geofence, it sends a first request to the first server. The first request carries the identifier of the first geofence and is used to request the first server to send the first promotional information. The receipt of the first discount information sent by the first server specifically includes: Receive a first response sent by the first server, the first response including the first discount information.

26. The method according to claim 24 or 25, characterized in that, The first merchant identifier sent by the receiving device specifically includes: The system receives device feature information sent by a payment receiving device. The device feature information of the payment receiving device includes a service identifier and a device organization identifier. The service identifier is used to indicate the type of NFC service supported by the payment receiving device, and the device organization identifier is used to indicate the first merchant identifier.

27. The method according to claim 26, characterized in that, The method further includes: The system receives a probe frame sent by the payment device, the probe frame being used to indicate that the payment device supports a specified NFC protocol; Send a Probe ACK frame to the receiving device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; The device feature information received from the payment receiving device specifically includes: The system receives a Notify frame sent by the payment device, the Notify frame carrying the device characteristic information of the payment device; The method further includes: Based on the device feature information of the payment device, the type of NFC service of the payment device is determined to be codeless payment; Sending the first response to the payment receiving device specifically includes: A NotifyACK frame is sent to the payment device to confirm successful reception of the Notify frame. The method further includes: Received a parameter negotiation command sent by the payment device; In response to the parameter negotiation command, a parameter negotiation response is sent to the payment device. The parameter negotiation command and the parameter negotiation response are used to negotiate data transmission parameters between the application layer of the payment device and the electronic device.

28. The method according to any one of claims 24-27, characterized in that, The method further includes: Display the first offer information.

29. The method according to any one of claims 24-28, characterized in that, The payment process via the first payment application specifically includes: Receive a first order command sent by the payment device, the first order command including a first order identifier and a first payment amount; Send a first order response to the payment device, the first order response being used to indicate that the first order command has been successfully received; Receive a first initialization transaction command from the payment device, wherein the first initialization transaction command is used to obtain a first payment credential from the first payment application; Send a first initialization transaction response to the receiving device, the first initialization transaction response carrying the first payment voucher.

30. The method according to any one of claims 24-29, characterized in that, The method further includes: Receive a first payment notification sent by the payment device, the first payment notification being used to indicate whether the payment was successful or failed; And / or, Receive a second payment notification sent by a second server, the second payment notification being used to indicate whether the payment was successful or failed.

31. An electronic device, characterized in that, It includes one or more processors and one or more memories; wherein the one or more memories are coupled to one or more processors, and the one or more memories are used to store computer instructions, which, when the one or more processors execute the computer instructions, implement the payment method of any one of claims 1-30.

32. A chip system, characterized in that, The chip system includes a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to execute the code instructions to perform the payment method according to any one of claims 1-30.

33. A readable storage medium, characterized in that, The device stores computer instructions that, when executed by a processor, implement the payment method described in any one of claims 1-30.

34. A computer program product, characterized in that, It includes computer instructions, which, when executed by a processor, implement the payment method according to any one of claims 1-30.

Images