Payment method, system, and related apparatus

Abstract

The present application discloses a payment method, a system, and a related apparatus. The method is applied to an electronic device, and comprises: upon entering a radio frequency field of a payment collection device of a first merchant, receiving a first payment request sent by the payment collection device, the first payment request comprising a first identifier of the first merchant and a first amount; on the basis of the first payment request, determining one or more promotional activities of the first merchant; on the basis of the first payment request, determining one or more payment methods supported by the payment collection device; on the basis of the one or more promotional activities of the first merchant, determining a first payment method from among the one or more payment methods supported by the payment collection device; and completing payment by means of the first payment method. In this way, user spending can be reduced.

Description

Payment method, system and related device

[0001] The present application claims priority to the Chinese patent application No. 202411020325.6, filed on July 26, 2024, entitled "Payment method, system and related device", the priority of which is hereby claimed in the present application. The present application claims priority to the Chinese patent application No. 202510549848.8, filed on April 27, 2025, entitled "Payment method, system and related device", the priority of which is hereby claimed in the present application. The entire contents of the above applications are hereby incorporated by reference in the present application. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular, to a payment method, system and related device. BACKGROUND

[0003] 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 realize payment functions.

[0004] In daily consumption scenarios, merchants will provide various promotional activities in order to promote sales, such as enjoying a discount when purchasing a specified product, or enjoying a discount when purchasing a specified amount of products, etc. When shopping at a merchant, if the selected product meets the conditions of the promotional activity, the user can enjoy the discount corresponding to the promotional activity.

[0005] When the user completes payment using the existing payment method, the user may not be able to obtain the promotional activities of the merchant, which will result in an increase in the user's expenses. SUMMARY

[0006] The present application provides a payment method, system and related device, which can obtain the promotional activities of the merchant before payment and complete payment based on the promotional activities, thereby reducing unnecessary expenses of the user.

[0007] In a first aspect, the present application provides a payment method applied to an electronic device, the method comprising: receiving a first payment request sent by a collection device after entering a radio frequency field of the collection device of a first merchant, the first payment request comprising a first identifier and a first amount of the first merchant; 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 collection device based on the first payment request; determining a first payment method from the one or more payment methods supported by the collection device based on the one or more promotional activities of the first merchant; and completing payment through the first payment method.

[0008] In this way, the electronic device can determine the payment method (i.e., the first payment method) finally used based on the preferential activities of the merchant, and complete the payment based on the payment method. In the scenario of purchasing the same goods, the user can spend less money compared to the case where the user does not enjoy the preferential activities of the merchant, and unnecessary spending of the user can be reduced.

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

[0010] In this way, the electronic device can obtain the preferential activities of the first merchant from the first server based on the first identifier of the first merchant. The first server can store the preferential activities of one or more merchants.

[0011] In a possible implementation, the first payment request further includes the one or more preferential activities of the first merchant.

[0012] In this way, when the electronic device interacts with the payment device, the electronic device can receive the preferential activities of the first merchant sent by the payment device, and does not need to obtain the preferential activities of the first merchant from the first server again. In addition, the preferential activities sent by the payment device are real-time preferential activities of the first merchant, and there is no possibility of lag of the preferential activities.

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

[0014] In this way, before the user shops, the electronic device can obtain the preferential activities of one or more merchants from the first server, and when the user pays through the electronic device, the preferential activities of the first merchant are determined from the preferential activities of the one or more merchants based on the first merchant to which the payment device belongs, and the payment is completed. Obtaining the preferential activities of multiple merchants in advance, and not needing to obtain the preferential activities of the first merchant in the payment process can shorten the interaction steps in the payment process, and improve the payment efficiency.

[0015] In a possible implementation, before receiving the first preferential information sent by the first server, the method further includes: when the electronic device enters a first geographic fence, sending a first request to the first server, the first request carrying an identifier of the first geographic fence, the first request being used to request the first server to send the first preferential information, and one or more merchants being located in the first geographic fence.

[0016] When the electronic device enters the first geofence, the first preferential information of the first geofence can be acquired, and the first preferential information can include preferential activities of one or more merchants in the first geofence. In this way, the user can acquire the preferential activities of the nearby merchants in real time and determine whether to go shopping.

[0017] In a possible implementation, after receiving the first preferential information sent by the first server, the method further includes: displaying the first preferential information.

[0018] In this way, after acquiring the first preferential information, the electronic device can push the first preferential information to the user, and the user can determine whether to go shopping at the specified merchant based on the first preferential information. In addition, pushing the first preferential information can also bring customer flow to the merchant.

[0019] In a possible implementation, the payment method supported by the one or more collection devices is determined based on the first payment request, and specifically includes: acquiring the payment method supported by the one or more collection devices based on the first identifier.

[0020] In this way, the payment method supported by the one or more collection devices can be acquired based on the first identifier of the first merchant, for example, the payment method supported by the one or more collection devices is acquired from the first server (or other server) based on the first identifier.

[0021] In a possible implementation, the first payment request further includes an identifier of the payment method supported by the one or more collection devices.

[0022] In this way, the payment method supported by the one or more collection devices can be determined based on the identifier of the payment method supported by the one or more collection devices carried in the first payment request.

[0023] In a possible implementation, the payment is completed through the first payment method, and specifically includes: sending a first payment response to the collection device, the first payment response including a first payment credential, the first payment credential being used to indicate a first payment account of the first payment method.

[0024] In this way, the electronic device can send the payment credential to the collection device, and the payment credential is sent to the second server by the collection device, and the second server is used to complete the payment.

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

[0026] When the electronic device interacts with the payment device, the electronic device can receive the payment account sent by the payment device. In addition, the electronic device can also determine the payment method, the payment account and the actual payment amount (i.e., the second amount) based on the preferential activities of the merchant. In this case, the electronic device can interact with the second server, send the payment account, the actual payment amount, the payment credential and the like to the second server, and complete the payment. In this way, the electronic device no longer needs to interact with the second server through the payment device.

[0027] In a possible implementation, the payment is completed through the first payment method, and specifically includes: sending a third payment response to the second server, the third payment response including the first payment credential, the first payment credential being used to indicate the first payment account of the first payment method.

[0028] In this case, the electronic device can send the first payment credential to the second server through the communication connection between the electronic device and the second server; in addition, the payment device can also send the payment account to the second server, and the second server completes the payment based on the information sent by the electronic device and the payment device.

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

[0030] In this way, the payment method finally adopted by the electronic device can be informed to the payment device through the first payment credential.

[0031] In a possible implementation, the first payment response further includes an identifier of the first payment method.

[0032] In this way, the payment method finally adopted by the electronic device can be informed to the payment device through the identifier of the first payment method.

[0033] In a possible implementation, the first payment method is determined from one or more payment methods based on one or more preferential activities of the first merchant, and specifically includes: determining a preferential amount of each payment method in the one or more payment methods based on the one or more preferential 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 preferential amount of the first payment method; and receiving and responding to an operation of the user on the first option to determine the first payment method.

[0034] In this way, the electronic device can display the preferential amount (or the actual payment amount) of the one or more payment methods based on the preferential activities of the merchant, so as to facilitate the user to select a suitable payment method to complete the payment.

[0035] In a possible implementation, the first payment method is determined from the one or more payment methods based on the one or more preferential activities of the first merchant, specifically comprising: determining a preferential amount of each of the one or more payment methods based on the one or more preferential activities of the first merchant; and determining the first payment method based on the preferential amount of each of the one or more payment methods, the first payment method being the payment method with the largest preferential amount among the one or more payment methods.

[0036] In this case, the electronic device can determine the payment method with the largest preferential amount (or the smallest actual payment amount) after determining the preferential amount and / or the actual payment amount of each payment method supported by the payment device, and complete the payment based on the payment method. In this way, the user does not need to perform an additional selection operation, and the user can enjoy the largest preferential amount.

[0037] In a possible implementation, the method further includes receiving a first notification sent by the second server, the first notification being used to notify the electronic device of a successful payment.

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

[0039] In a possible implementation, the method further includes receiving a first notification sent by the payment device, the first notification being used to notify the electronic device of a successful payment.

[0040] In this way, the electronic device can determine whether the payment is successful based on the first notification sent by the payment device.

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

[0042] In this way, the electronic device can report the payment crowd source to the first server after determining the payment method finally used, and the payment crowd source is used to instruct the first server to update the preferential activities of the first merchant stored by the first server based on the payment crowd source.

[0043] In a possible implementation, the first notification includes a first amount and / or a second amount, the first amount being a payment amount of the payment device, and the second amount being a payment amount of the electronic device; and the first crowd source further includes the first amount and / or the second amount.

[0044] The payment crowdsourcing reported by the electronic device can further include the actual payment amount and / or the collection amount, so as to confirm the specific discount content of the preferential activity of the first merchant by the first server.

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

[0046] In this way, the collection device can be sent the preferential activity after the preferential activity is determined, so as to check whether the preferential activity is still valid.

[0047] In a possible implementation, after entering the radio frequency field of the collection device, the method further includes: receiving a probe frame sent by the collection device, the probe frame being used to indicate that the collection device supports a specified NFC protocol; sending a probe acknowledgement (Probe ACK) frame to the collection device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; receiving a pick frame sent by the collection device, the pick frame carrying device characteristic information of the collection device, the device characteristic information of the collection device including a service identifier and a device organization identifier, the service identifier being used to indicate the type of the NFC service supported by the collection device, and the device organization identifier being used to indicate the manufacturer that provides the NFC service by using the collection device; determining, based on the device characteristic information of the collection device, that the type of the NFC service of the collection device is non-coding payment; and sending a pick acknowledgement (Pick ACK) frame to the collection device, the Pick ACK frame being used to indicate that the electronic device has determined the type of the NFC service of the collection device.

[0048] In this way, the electronic device can interact with the collection device through the first protocol based on the NFC technology, and determine the type of the NFC service of the collection device.

[0049] In a second aspect, the present application provides a payment method applied to an electronic device, the method comprising: receiving a first payment request sent by a payment device after entering a radio frequency field of the payment device of a first merchant, the first payment request comprising a first identifier and a first amount of the first merchant; determining one or more preferential activities of the first merchant based on the first payment request; determining identifiers of one or more payment methods supported by the payment device based on the first payment request; determining a first payment method from the one or more payment methods based on the one or more preferential activities of the first merchant; determining a first preferential activity from the one or more preferential activities based on the first payment method; sending a fourth payment response to the payment device, the fourth payment response comprising a first payment credential of the first payment method and the first preferential activity, the first payment credential being used to indicate a first payment account of the first payment method; receiving second preferential information sent by the payment device, the second preferential information comprising the one or more preferential activities of the first merchant; determining a second payment method and a second preferential activity based on the second preferential information; and completing payment through the second payment method.

[0050] With the payment method, in the case that the first preferential activity to be enjoyed by the electronic device is invalid, the electronic device can receive the second preferential information sent by the payment device, the second preferential information being real-time preferential activities of the first merchant. The electronic device can determine a payment method (i.e., the second payment method) based on the second preferential information, and complete payment based on the second payment method. In this way, payment failure caused by payment based on the invalid preferential activity can be avoided.

[0051] In a possible implementation, in the case that payment is completed through the second payment method, the method further comprises: sending second crowdsourcing to the first server, the second crowdsourcing comprising location information of the electronic device, the first identifier of the first merchant, and the second preferential information.

[0052] In the case that the second preferential information sent by the payment device is received, the electronic device can carry the second preferential information when reporting payment crowdsourcing, so as to update the preferential activities of the first merchant stored by the first server based on the second preferential information. In this way, in the case that other users make purchases at the first merchant subsequently, real-time preferential activities of the first merchant can be obtained, and invalid preferential activities can not be obtained.

[0053] In a third aspect, the present application provides a payment method applied to an electronic device, the method comprising: receiving first discount information sent by a first server, the first discount information comprising discount activities of one or more merchants in a first geographic fence, the one or more merchants comprising a first merchant; receiving a first merchant identifier sent by a payment device; determining second discount information from the first discount information based on the first merchant identifier; sending a first response to the payment device, the first response being used to indicate that the electronic device successfully receives the first merchant identifier; receiving a first selection command sent by the payment device of the first merchant; sending a first selection response to the payment device, the first selection response comprising an identifier of one or more payment applications supported by the electronic device and the second discount information; receiving a second selection command sent by the payment device, the second selection command comprising an identifier of a first payment application; sending a second selection response to the payment device, the second selection response being used to indicate that the selection of the first payment application is successful; and completing payment through the first payment application.

[0054] In this way, the electronic device can filter out the second discount information based on the merchant to which the payment device belongs, and send the second discount information to the payment device, so as to facilitate the payment device to select the payment application (i.e., the first payment application) to be finally used. In the scenario of purchasing the same goods, the user will spend less money compared to the case where the user does not enjoy the discount activities of the merchant, and unnecessary expenses of the user can be reduced.

[0055] In a possible implementation, the method further comprises: when the electronic device enters the first geographic fence, sending a first request to the first server, the first request carrying an identifier of the first geographic fence, the first request being used to request the first server to send the first discount information; and receiving the first discount information sent by the first server, specifically comprising: receiving a first response sent by the first server, the first response comprising the first discount information.

[0056] In this way, after the electronic device enters the first geographic fence, the electronic device can obtain the first discount information.

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

[0058] In this way, the electronic device can determine the first merchant identifier based on the device organization identifier in the device characteristic information of the payment device.

[0059] In a possible implementation, the method further includes: receiving a probe frame sent by the payment device, the probe frame being used to indicate that the payment device supports the specified NFC protocol; sending a probe acknowledgement (Probe ACK) frame to the payment device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; and receiving device characteristic information sent by the payment device, specifically including: receiving a notification (Notify) frame sent by the payment device, the Notify frame carrying the device characteristic information of the payment device; the method further includes: determining, based on the device characteristic information of the payment device, that the type of the NFC service of the payment device is no-code payment; and sending a first response to the payment device, specifically including: sending a Notify ACK frame to the payment device, the Notify ACK frame being used to indicate that the Notify frame is successfully received; the method further includes: receiving a parameter negotiation command sent by the payment device; and in response to the parameter negotiation command, sending a parameter negotiation response to the payment device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between the application layer of the electronic device and the payment device.

[0060] In this way, the data transmission parameters between the application layer of the electronic device and the payment device can be negotiated through the NFC protocol, and subsequent data transmission is facilitated.

[0061] In a possible implementation, the method further includes: displaying the first preferential information.

[0062] In this way, the first preferential information can be displayed to the user, and the user can select a merchant for consumption according to the first preferential information.

[0063] In a possible implementation, the payment is completed through the first payment application, specifically including: receiving a first order command sent by the payment device, the first order command including a first order identifier and a first payment amount; sending a first order response to the payment device, the first order response being used to indicate that the first order command is successfully received; receiving a first initialization transaction command of the payment device, the first initialization transaction command being used to obtain a first payment credential of the first payment application; and sending a first initialization transaction response to the payment device, the first initialization transaction response carrying the first payment credential.

[0064] In this way, the electronic device and the payment device can send the first payment credential corresponding to the first payment application to the payment device through the order command, the order response, the initialization transaction command, and the initialization transaction response, and the payment device can interact with a server corresponding to the first payment application to complete the payment.

[0065] In a possible implementation, the method further includes: receiving a first payment notification sent by the payment device, the first payment notification being used to indicate payment success or payment failure; and / or, receiving a second payment notification sent by the second server, the second payment notification being used to indicate payment success or payment failure.

[0066] In this way, the electronic device can determine whether the payment is successful or not through the payment notification sent by the payment device (or the server corresponding to the first payment application).

[0067] In a fourth aspect, the present application provides an electronic device, including one or more processors, one or more memories; wherein the one or more memories are coupled with the one or more processors, and the one or more memories are used to store computer instructions, when the one or more processors execute the computer instructions, the payment method in any possible implementation of any one of the above aspects is implemented.

[0068] In a fifth aspect, the present application provides a chip system, including: processing circuitry and interface circuitry, the interface circuitry is used to receive code instructions and transmit to the processing circuitry, and the processing circuitry is used to run the code instructions to execute the payment method in any possible implementation of any one of the above aspects.

[0069] In a sixth aspect, the present application provides a readable storage medium, which stores computer instructions, when the computer instructions are executed by a processor, the payment method in any possible implementation of any one of the above aspects is implemented.

[0070] In a seventh aspect, the present application provides a computer program product, including computer instructions, when the computer program is executed by a processor, the payment method in any possible implementation of any one of the above aspects is implemented.

[0071] The beneficial effects of the fourth to seventh aspects can refer to the beneficial effects of the first to third aspects. BRIEF DESCRIPTION OF DRAWINGS

[0072] FIG. 1 is a schematic diagram of a NFC working principle provided in an embodiment of the present application;

[0073] FIG. 2A is a schematic diagram of a system architecture of a payment system provided in an embodiment of the present application;

[0074] FIG. 2B is a schematic diagram of communication interaction between an electronic device and a payment cloud server provided in an embodiment of the present application;

[0075] FIG. 2C is a schematic diagram of a device form of an electronic device provided in an embodiment of the present application;

[0076] FIG. 2D is a schematic diagram of a device form of a payment device provided in an embodiment of the present application;

[0077] FIG. 2E is a schematic diagram of a position relationship of an electronic device in communication with a payment device based on NFC technology according to an embodiment of the present application;

[0078] FIG. 3A is a schematic diagram of a structure of an electronic device according to an embodiment of the present application;

[0079] FIG. 3B is a schematic diagram of a layered architecture of an NFC protocol stack according to an embodiment of the present application;

[0080] FIGS. 4A-4C are interfaces for pushing discount information to a user after a group of electronic devices enter a geofence according to an embodiment of the present application;

[0081] FIGS. 4D-4G are schematic diagrams of interfaces for performing a payment method according to an embodiment of the present application;

[0082] FIG. 5 is a schematic diagram of a payment method according to an embodiment of the present application;

[0083] FIG. 6 is a schematic diagram of a process for an electronic device to obtain discount information of a merchant according to an embodiment of the present application;

[0084] FIG. 7 is a schematic diagram of a process for payment account deduction according to an embodiment of the present application;

[0085] FIG. 8 is a schematic diagram of a payment process after a payment method is determined according to an embodiment of the present application;

[0086] FIG. 9 is a schematic diagram of a payment method according to an embodiment of the present application;

[0087] FIG. 10 is a schematic diagram of another payment method according to an embodiment of the present application;

[0088] FIG. 11 is a schematic diagram of another payment method according to an embodiment of the present application;

[0089] FIG. 12A is a schematic diagram of functional modules of a payment cloud server according to an embodiment of the present application;

[0090] FIG. 12B is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application;

[0091] FIGS. 13-16 are schematic diagrams of a group of communication devices according to an embodiment of the present application;

[0092] FIG. 17 is a schematic diagram of a payment method according to an embodiment of the present application;

[0093] FIG. 18 is a schematic diagram of another payment method according to an embodiment of the present application;

[0094] FIG. 19 is a schematic diagram of a payment method according to an embodiment of the present application. DETAILED DESCRIPTION

[0095] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " represents the meaning of or, for example, A / B can represent A or B; the "and / or" in the text only describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent three cases of A alone, A and B together, and B alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0096] Hereinafter, the terms "first" and "second" are only used for description purposes, and cannot be understood as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more of the features, and in the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" is two or more than two.

[0097] The term "user interface (UI)" in the following embodiments of the present application is a medium interface for interaction and information exchange between an application program or an operating system and a user, which 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, extensible markup language (XML), etc. The interface source code is parsed, rendered, and finally presented as content that can be recognized by the user on the electronic device. The commonly used form of user interface is graphic user interface (GUI), which refers to a user interface related to computer operation displayed in a graphical manner. It can be a visual interface element such as text, icon, button, menu, tab, text box, dialog box, status bar, navigation bar, Widget, etc. displayed in the display screen of the electronic device.

[0098] The working principle of near field communication (NFC) technology in the embodiments of the present application will be introduced below.

[0099] FIG. 1 shows a schematic diagram of the working principle of NFC provided in the embodiments of the present application.

[0100] As shown in FIG. 1, 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 proximity contactless communication with the PICC. The PCD and the PICC can allow near field communication at a specific data rate (e.g., 106, 212, 424, or 848 kilobit per second (kbps)) and a specific frequency (e.g., 13.56 MHz). The communication between the PCD and the PICC can occur within a close distance, e.g., a range of about 2 to 4 centimeters, between the PCD and the PICC.

[0101] The PCD can generate high-frequency alternating current to generate a radio frequency field at a specified frequency (e.g., 13.56 MHz) and transmit data to the PICC through the radio frequency field. After the PICC is close to the PCD, the PICC can induct the radio frequency field emitted by the PCD. The PICC can obtain energy from the radio frequency field of the PCD by electromagnetic induction after entering the radio frequency field emitted by the PCD, and generate power by the obtained energy to drive the circuit inside the PICC, analyze the data transmitted by the PCD through the radio frequency field, and thus achieve data transmission from the PCD to the PICC. The PICC can also send data to the PCD by modulating the radio frequency field as a load, and thus achieve data transmission from the PICC to the PCD.

[0102] In the embodiments of the present application, the PICC can be a physical NFC tag card, and some NFC devices (e.g., mobile phones, tablets, smart watches, and other electronic devices) can also simulate themselves into a PICC conforming to NFC standards by using the data of an NFC simulation card to achieve the function of the PICC and communicate with the PCD based on NFC technology.

[0103] The system architecture of a payment system 10 provided in an embodiment of the present application is introduced below.

[0104] FIG. 2A shows a schematic diagram of the system architecture of the payment system 10 provided in an embodiment of the present application.

[0105] As shown in FIG. 2A, the payment system 10 can include an electronic device 100, a payment device 200, and a payment cloud server 300. The electronic device 100 and the payment device 200 can have NFC function, and when the electronic device 100 enters the radio frequency field of the payment device 200, the electronic device 100 can communicate with the payment device 200 based on NFC technology. The electronic device 100 can also establish wireless communication connection with the payment cloud server 300, and the payment device 200 can also establish communication connection with the payment cloud server 300.

[0106] When the electronic device 100 enters the radio frequency field of the payment device 200 (e.g., touches the payment device 200), the electronic device 100 can communicate with the payment device 200 based on NFC technology, determine one or more payment methods supported by the payment device 200, and optionally, determine the payment amount, etc. The electronic device 100 can also obtain the preferential information corresponding to the geofence in which the electronic device 100 is located from the payment cloud server 300. The preferential information can include preferential activities of one or more merchants in the geofence. The electronic device 100 can determine the final payment method to be used based on the preferential information, or based on the selection operation of the user, or based on the communication between the electronic device 100 and the payment device 200, and send the payment account corresponding to the payment method to the payment device 200.

[0107] The payment device 200 can determine the final payment method to be used based on the communication with the electronic device 100. The payment device 200 can also receive the payment account corresponding to the payment method sent by the electronic device 100. After determining the final payment method to be used and the corresponding payment account, the payment device 200 can send the payment account to the payment cloud server 300 based on the payment method.

[0108] The payment cloud server 300 can be a server cluster, which can include one or more servers (or server modules). The communication interaction mode between the servers in the payment cloud server 300 and the electronic device 100 can refer to the related description in the embodiment shown in FIG. 2B below, which is not described in detail here. The payment cloud server 300 can receive and respond to the preferential information obtaining request sent by the electronic device 100 carrying the identifier of the geofence, and send the preferential information of the specified geofence to the electronic device 100. The payment cloud server 300 can also deduct the payment amount from the payment account based on the payment amount, the payment account, and the payment account sent by the payment device 200, and transfer the payment amount to the payment account. In some embodiments, before deducting the payment amount from the payment account, the payment cloud server 300 can initiate payment verification to the electronic device 100 based on the communication connection with the electronic device 100, and after the verification is successful, perform the deduction operation.

[0109] It can be understood that the above-mentioned embodiment shown in FIG. 2A is only an example, and in the embodiments of the present application, the payment system 10 can further include more, less or different electronic devices than the above-mentioned embodiment, such as a merchant background server, etc., which can undertake part of the functions of the above-mentioned collection device 200, which is not limited herein.

[0110] Next, the communication interaction between each application in the electronic device 100 and each server (or server module) in the payment cloud server 300 provided by the embodiments of the present application is introduced.

[0111] For example, FIG. 2B shows a schematic diagram of the communication interaction between the electronic device 100 and the payment cloud server 300 provided by the embodiments of the present application.

[0112] As shown in FIG. 2B, the electronic device 100 can be installed with one or more payment applications, such as payment application A and payment application B, etc. Each payment application can include one or more payment applets, and each payment applet can correspond to a payment method. For example, the payment application A can include payment methods such as bank card C1 and balance C2, and the payment application B can include payment methods such as member card C3.

[0113] The payment cloud server 300 can include one or more servers, such as server 310, server 320 and server 330. Each server can further include one or more sub-servers, such as server 310 which can include sub-server 311 and sub-server 312, etc.

[0114] Among them, the server 310 can be the server of the payment application A, and the electronic device 100 can interact with the server 310 through the payment application A. Specifically, the sub-server 311 in the server 310 can interact with the payment applet corresponding to the bank card C1 in the payment application A, and the sub-server 312 can interact with the payment applet corresponding to the balance C2 in the payment application A. In addition, the server 330 can be the server of the bank corresponding to the bank card C1. When the electronic device 100 interacts with the sub-server 311 through the payment applet corresponding to the bank card C1 in the payment application A, it can also interact with the server 330 through the sub-server 311. The server 320 can be the server of the payment application B. The electronic device 100 can interact with the server 320 through the payment application B.

[0115] It can be understood that the embodiment shown in FIG. 2B is only illustrative, the electronic device 100 can communicate with the server (or server module) corresponding to the payment application installed thereon through the payment application, in the embodiment of the present application, the electronic device 100 can also be installed with more, less or different payment applications than the above-mentioned embodiments, and the payment cloud server 300 can also include more, less or different servers than the above-mentioned embodiments, which are not limited in the present application.

[0116] The device form of the electronic device 100 and the payment device 200 and the positional relationship between the electronic device 100 and the payment device 200 when they communicate based on the NFC technology will be introduced below.

[0117] FIG. 2C shows a device form of an electronic device 100 according to an embodiment of the present application.

[0118] As shown in FIG. 2C, the electronic device 100 can include a front side and a back side. The front side of the electronic device 100 can be provided with a display screen 11, and optionally, the front side of the electronic device 100 can also be provided with any one or more of the following: a front camera 12, a receiver 13, etc. The back side of the electronic device 100 can include an NFC area 14, and optionally, the back side of the electronic device 100 can also include any one or more of the following: a rear camera 15, a flashlight 16, etc. When the electronic device 100 touches the payment device 200, the NFC area 14 is used to contact the payment device 200, so as to realize the communication between the electronic device 100 and the payment device 200 based on the NFC technology.

[0119] It can be understood that the embodiment shown in FIG. 2C is only an example, and in the embodiment of the present application, the NFC area of the electronic device 100 can also be arranged at other positions of the electronic device 100, which are not limited in the present application. In addition, the electronic device 100 can be a mobile phone, and can also be a tablet computer, a wearable device or other electronic device, which are not limited in the present application.

[0120] FIG. 2D shows a device form of a payment device 200 according to an embodiment of the present application.

[0121] As shown in FIG. 2D, the payment device 200 can be a POS machine, and the payment device can include a card swiping area 201 and a display screen 202. Optionally, the payment device 200 can further include a button 203. When the electronic device 100 touches or approaches the card swiping area 201 of the payment device 200, the NFC-based communication between the electronic device 100 and the payment device 200 can be implemented. The display screen 202 can be used to display the payment amount, and can also be used to display a payment success prompt, etc. In some embodiments, the card swiping area 201 and the display screen 202 can have a partial or full overlapping area. The button 203 can be used to interact with the user, for example, to output the payment amount to the payment device 200, etc. In some embodiments, the payment device 200 can not have a physical button, and the interaction between the payment device 200 and the user can be implemented through the touch operation of the display screen 202.

[0122] It can be understood that the embodiment shown in FIG. 2D is only an example. In the embodiments of the present application, the payment device 200 can be the POS machine shown in FIG. 2D, or can be a device in a different form, for example, including more, fewer or different components than the embodiment shown in FIG. 2D, which is not limited in the present application.

[0123] FIG. 2E shows a schematic diagram of the position relationship between the electronic device 100 and the payment device 200 when the electronic device 100 communicates with the payment device 200 based on the NFC technology.

[0124] As shown in FIG. 2E, the user can contact the NFC area 14 on the back of the electronic device 100 with the card swiping area 201 of the payment device 200, so as 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 the NFC technology, and the payment can be completed.

[0125] It can be understood that the embodiment shown in FIG. 2E is only an example of the position relationship between the electronic device 100 and the payment device 200 when they are in contact. In the embodiments of the present application, if the positions of the NFC area 14 or the card swiping area 201 are different from those in the above embodiment, the electronic device 100 and the payment device 200 can also have a position relationship different from that in the above embodiment to communicate based on the NFC technology, which is not limited in the present application.

[0126] The structure of the electronic device 100 provided in the embodiments of the present application will be introduced below.

[0127] FIG. 3A shows a schematic diagram of the structure of the electronic device 100 provided in the embodiments of the present application.

[0128] As shown in FIG. 3A, the electronic device 100 can include a processor 101 and an NFC module 102. One or more applications can be run in the processor 101. The one or more applications can include one or more of a wallet application, one or more host-based card emulation (HCE) applications, and the like. Optionally, the electronic device 100 can further include a secure element (SE) 103 and / or a subscriber identity module (SIM) card. The processor 101 can be connected to the NFC module 102, the SE 103, and the SIM card 104, respectively. The NFC module 102 can be further connected to the SE 103 and the SIM card 104.

[0129] The NFC module 102 can include an NFC controller (not shown in FIG. 3A), an NFC transceiver (not shown in FIG. 3A), and an NFC memory (not shown in FIG. 3A). The NFC controller can be connected to the processor 101, and can be further connected to the NFC transceiver and the NFC memory, respectively.

[0130] The NFC controller is mainly used for modulation and demodulation of contactless communication signals, controls input and output of data in the NFC memory, and interacts with the processor 101. The NFC transceiver is used to implement transmission and reception of NFC signals (e.g., 13.56 MHz radio frequency signals), and can include an electromagnetic compatibility (EMC) filter circuit, a matching circuit, a receiving circuit, and an NFC antenna, etc. The NFC antenna can be a loop antenna, which is used to implement the proximity-based contactless communication capability of the NFC module 102. The NFC memory can be used to store data transmitted by the NFC module 102 to the payment device 200, and data received from the payment device 200. In some embodiments, the NFC memory can be one memory, which can be shared by the above components in the NFC module 102. For example, some data in the NFC memory can be invoked by the NFC controller, and other data can be invoked by the SE 103.

[0131] In some embodiments, the NFC memory can also store routing information. In some embodiments, the routing information can be controlled or managed by the NFC controller. The routing information can include a routing table, which is composed of a list of routing rules. Each routing rule can include an applet identifier (AID) and a destination. The destination can be where the applet that implements the business logic of the NFC emulation card is running. The destination can include a HCE application running in the processor 101 of the electronic device 100, or the SE 103 or the SIM card 104 connected to the NFC controller.

[0132] In some embodiments, the NFC memory described above can also store routing information. In some embodiments, the routing information can be controlled or managed by the NFC controller. The routing information can include a routing table, which is composed of a list of routing rules. Each routing rule can include an applet identifier (AID) and a destination. The destination can be where the applet that implements the business logic of the NFC emulation card is running. The destination can include a HCE application running in the processor 101 of the electronic device 100, or the SE 103 or the SIM card 104 connected to the NFC controller.

[0133] In some embodiments, the SE 103 and the NFC module 102 can be two independent chips. Alternatively, the SE 103 and the NFC module 102 can be packaged in one chip.

[0134] The electronic device 100 can open one or more NFC emulation cards in an application according to the user's input, so that the electronic device 100 supports one or more NFC services. The business processing logic of the NFC emulation card in the electronic device 100 is implemented by an applet. The applet can be stored and run in the hardware device or software module (e.g., HCE application, SIM card, SE, etc.) corresponding to the NFC emulation card.

[0135] The NFC emulation mode on the electronic device 100 can be divided into a hardware-based virtual card mode and a software-based HCE mode. Among them,

[0136] 1. In the hardware-based virtual card mode, the electronic device 100 can provide a running environment of an Applet corresponding to an NFC emulation card and storage and processing of service data of the NFC emulation card through the SE 103 or the SIM card 104. The NFC module 102, as a front end of contactless communication, forwards a command received from an external PCD to the SE 103 or the SIM card 104, and then the command is processed by an Applet in the SE 103 or the SIM card 104 and response data is sent to the external PCD through the NFC module 102. A user can open one or more NFC emulation cards in a wallet application, and the wallet application can write the Applet and card data of the one or more NFC emulation cards into the SE 103. Alternatively, the user can open one or more NFC emulation cards in a SIM card application. The SIM card application can write the Applet and card data of the one or more NFC emulation cards into the SIM card 104 for storage.

[0137] 2. In the software-based HCE mode, an HCE application running in the processor 101 can provide a running environment of an Applet corresponding to an NFC emulation card and storage and processing of service data of the NFC emulation card. After receiving a command sent by an external PCD, the NFC module 102 can send the command to the HCE application. The HCE application can process the command received by the NFC module through an Applet running in the HCE application or a cloud server, and generate response data for the PCD. The HCE application can send the response data to the NFC module 102. The NFC module 102 can send the response data to the external PCD. A user can open one or more NFC emulation cards in the HCE application, and the HCE application can run the Applet of the one or more NFC emulation cards and save the card data of the NFC emulation cards on a local storage of the electronic device 100 or on a cloud server.

[0138] 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. Among them, the common management functions can include file management, card long activation, security management, service routing management and the like.

[0139] Exemplarily, in the card emulation scenario described above, a native application related to NFC is installed in the electronic device 100, and in addition, a third-party application can also be downloaded and installed in the electronic device 100 by a user through an application store. Generally, the native application can adopt a hardware-based virtual card scheme, and the third-party application can adopt an HCE scheme. The native application can be a wallet application or the like, and the third-party application can be, for example, a ticket application, a payment application or the like. The above examples are merely used for explaining the present application, and should not be construed as limiting.

[0140] Next, a NFC protocol stack provided in an embodiment of the present application is introduced.

[0141] FIG. 3B shows a schematic diagram of a layered architecture of a NFC protocol stack provided in an embodiment of the present application.

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

[0143] The physical layer can be used to implement physical characteristics in NFC technology communication.

[0144] The radio frequency layer can be used to implement radio frequency specifications in NFC technology communication, for example, data rate, frequency of radio frequency signals and the like.

[0145] 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 fusion card selection.

[0146] The transport layer includes a high-speed data transmission protocol, through which data transmission between PCD and PICC in the application layer can be implemented.

[0147] The application layer can be used to implement one or more NFC services and one or more service management strategies. The one or more NFC services can include codeless payment, electronic ticket, access control, digital ID card, full-scene tap-to-tap, near field data transmission and the like. The one or more service management strategies can include any one or more of file management, card long activation, security management and service routing management. The processing logic of the NFC service can be executed by an Applet. In a possible implementation manner, the processing logic of the service management strategy can be executed by an NFC base service module.

[0148] In an embodiment of the present application, the NFC protocol stack shown in FIG. 3B can be referred to as a first protocol stack.

[0149] The application provides a payment method. When the electronic device 100 enters the geofence A1, the electronic device 100 can obtain the merchant preferential information 1 of the geofence A1 from the payment cloud server 300, and the merchant preferential information 1 comprises preferential activities of one or more merchants in the geofence A1. The electronic device 100 can output the merchant preferential information 1, so as to facilitate the user to query the preferential activities of the nearby merchants in real time. If the user shops in one of the merchants, the electronic device 100 can communicate with the payment device 200 based on the NFC technology during the payment of the user, determine the payment mode adopted and the actual payment amount of the payment mode based on the merchant preferential information 1, and complete the payment.

[0150] In this way, the user can query the preferential activities of the nearby merchants in real time, and can also complete the payment based on the preferential activities of the merchants, thereby saving the expenses of the user and increasing the customer flow of the merchants.

[0151] The following introduces a group of interfaces for pushing the preferential information to the user after the electronic device 100 enters the geofence A1 according to the embodiments of the application.

[0152] In some application scenarios, after the electronic device 100 enters the geofence A1, the electronic device 100 can display the preferential activities of one or more merchants in the geofence A1 when the user views the minus one screen (or other specified interface). In this way, the user can actively acquire the preferential activities of the nearby merchants, and can also determine whether to go to the corresponding merchant for shopping based on the preferential activities, thereby increasing the exposure of the merchants and increasing the customer flow of the merchants.

[0153] For example, the electronic device 100 can display a desktop 400 as shown in FIG. 4A. The desktop 400 displays a page with application icons, which includes a plurality of application icons (for example, a weather application icon, a settings application icon, a browser application icon, and the like). The page with application icons also displays a page indicator 402 below, to indicate the total number of pages on the desktop, and the positional relationship between the currently displayed page and other pages. For example, the desktop 400 can include three pages, and the black dot in the page indicator is located at the first position from the left, which can indicate that the currently displayed page is the first page from the left among the three pages. Optionally, the page with application icons also displays a status bar 401 above, which can include the strength indicator of the signal, the power value, the time, and the like. Further optionally, the page indicator can have a dock area 403 below, which can include one or more dock icons (for example, a dialing application icon, an information application icon, a contact application icon, a camera application icon, and the like), and the one or more dock icons in the dock area can remain displayed when the page is switched.

[0154] The electronic device 100 can receive and respond to a right swipe operation of the user for the desktop 400. After detecting that the electronic device 100 enters the geo-fence A1, the electronic device 100 can display the minus one screen interface 410 as shown in FIG. 4B.

[0155] As shown in FIG. 4B, the minus one screen interface 410 can include one or more nearby recommendation options, such as an AAA convenience store option 411, a BBB shopping mall option 412, and a CCC supermarket option 413, etc. Each of the nearby recommendation options can correspond to a promotional activity of a merchant within the geo-fence (i.e., the geo-fence A1) where the electronic device 100 is located. For example, the AAA convenience store option 411 can display a promotional activity of the AAA convenience store within the geo-fence A1. The promotional activity of the AAA convenience store can include a promotional item and a discount rule. The promotional item can be the PP1 item, and the discount rule can be “8 off for two items”. Optionally, the AAA convenience store option 411 can also display a distance between the AAA convenience store and the electronic device 100, i.e., “786 m”. For another example, the BBB shopping mall option 412 can display a promotional activity of the BBB shopping mall within the geo-fence A1. The promotional activity of the BBB shopping mall can include a discount rule, which can be “9 off for all items”. Optionally, the BBB shopping mall option 412 can also display a distance between the BBB shopping mall and the electronic device 100, i.e., “502 m”. For example, the CCC supermarket option 413 can display a promotional activity of the CCC supermarket within the geo-fence A1. The promotional activity of the CCC supermarket can include a payment method identifier and a discount rule. The payment method identifier can be “payment application A”, and the discount rule can be “50 off for 5 items”. Optionally, the CCC supermarket option 413 can also display a distance between the CCC supermarket and the electronic device 100, i.e., “823 m”. Optionally, the minus one screen interface 410 can also include a shortcut function bar 414 and a search bar 415. The shortcut function bar 414 can include one or more shortcut function controls. The shortcut function controls can be used to trigger the electronic device 100 to start a corresponding shortcut function, such as a code scanning function, a payment function, a memo function, etc. The search bar 415 can be used to trigger the electronic device 100 to initiate a search based on the user’s input.

[0156] In some application scenarios, after the electronic device 100 enters the geofence A1, the electronic device 100 pushes a discount notification, which is used to notify the user that there is one or more merchants with discount activities in the vicinity. The electronic device 100 can receive and respond to the operation of the user on the discount notification to display the discount activities of the one or more merchants in the geofence A1. In this way, when the electronic device 100 enters the geofence A1, the electronic device 100 can push the discount activities to the user, which facilitates the user to determine whether to go to the corresponding merchant for shopping based on the discount activities, and also increases the exposure of the merchant and the customer flow of the merchant.

[0157] For example, when the electronic device 100 enters the geofence A1, the electronic device 100 can display a discount notification interface 420 as shown in FIG. 4C.

[0158] As shown in FIG. 4C, the discount notification interface 420 can include a discount notification 421, which can be used to notify the user that there is one or more discount activities in the geofence A1 in which the electronic device 100 is currently located. For example, the discount notification 421 can include the text “There is one or more discount activities in the vicinity”, and optionally, the discount notification 421 can also include the operation instruction text “Click to view”, which can be used to guide the user to view the specific content of the discount activities.

[0159] The electronic device 100 can receive and respond to the click operation of the user on the discount notification 421 to display one or more discount activities in the geofence A1, for example, display the minus one screen interface 410 as shown in FIG. 4B.

[0160] It can be understood that the above-described embodiments shown in FIGS. 4A-4C are only a group of examples, and in the embodiments of the present application, the electronic device 100 can also display discount information in other interfaces, and in addition, the electronic device 100 can also display discount information in a manner different from the above-described embodiments, which is not limited herein.

[0161] FIGS. 4D-4G show a group of interface schematic diagrams of the electronic device 100 performing a payment method according to an embodiment of the present application.

[0162] For example, as shown in FIG. 4D, the electronic device 100 can be in a screen-off state or a screen-on state, and when the electronic device 100 enters the radio frequency field of the payment device 200, the electronic device 100 can display a payment method selection interface 430 as shown in FIG. 4E, which includes one or more payment options.

[0163] As shown in FIG. 4E, the payment method selection interface 430 can include one or more payment options, which can be displayed in the payment method selection interface 430 in the order of the size of the discount amount, for example, the AA bank card option 431, the payment application A option 432, the payment application B option 433, and the like are displayed in turn from top to bottom. In this way, the user can determine the most favorable payment option according to the arrangement order. Each payment option can correspond to a payment method, for example, the payment method corresponding to the AA bank card option 431 is to pay by AA bank card, the payment method corresponding to the payment application A option 432 is to pay by payment application A, and the payment method corresponding to the payment application B option 433 is to pay by payment application B. Each payment option can include an amount prompt, which can be used to prompt the user of the actual payment amount and / or the discount amount corresponding to the payment option. For example, the AA bank card option 431 can include an amount prompt 431a, which can be used to prompt the user that the actual payment amount is 45 yuan and the discount amount is 5 yuan when using the AA bank card to pay; the payment application A option 432 can include an amount prompt 432a, which can be used to prompt the user that the actual payment amount is 48 yuan and the discount amount is 2 yuan when using the payment application A to pay; the payment application B option 433 can include an amount prompt 433a, which can be used to prompt the user that the actual payment amount is 49 yuan and the discount amount is 1 yuan when using the payment application B to pay. In addition, each payment option can also include a selection identifier, for example, the AA bank card option 431 includes a selection identifier 431b, the payment application A option 432 includes a selection identifier 432b, and the payment application B option 433 includes a selection identifier 433b. Each selection identifier includes a selected state and an unselected state, and the selection identifier can be used to indicate whether the corresponding payment option is selected. The selection identifier can include two states, i.e., the selected state and the unselected state. In some embodiments, the electronic device 100 can indicate the two states of the selection identifier by different display colors, for example, the selection identifier 431b is filled with black color, and the other selection identifiers are not filled, which is used to indicate that the AA bank card option 431 is in the selected state, and the other options are not selected. It can be understood that in the embodiments of the present application, different selection identifiers can be used to indicate whether the option is selected, which is not limited in the present application. The payment method selection interface 430 can also include a payment confirmation control 434, which can be used to trigger the electronic device 100 to complete the payment based on the currently selected payment option.

[0164] In some embodiments, the electronic device 100 can receive and respond to the user's click operation on the payment confirmation control 434 to display the payment verification prompt 440 as shown in FIG. 4F.

[0165] As shown in FIG. 4F, the payment verification prompt 440 can be used to prompt the user to perform payment verification. The payment verification prompt 440 can include a payee 442, an amount to be paid 443, an actual payment amount 444, a payment method 445, and a fingerprint verification prompt 446. The payee 442 can be used to prompt the user to check the account of the payee (e.g., the account number of the payee, etc.), which can facilitate the user to check whether the payee is correct. The amount to be paid 443 can be used to prompt the user to pay the amount. The actual payment amount 444 can be used to prompt the user to pay the actual amount. The payment method 445 can be used to prompt the user to use the current payment method, such as "AA bank savings card", etc. In addition, the user can also determine whether the contents displayed in the payment verification prompt 440, such as the payee 442, the amount to be paid 443, the actual payment amount 444, the payment method 445, etc., are correct before performing payment verification. The fingerprint verification prompt 446 can be used to prompt the user to complete payment verification by fingerprint verification. Optionally, the payment verification prompt 440 can further include any 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.

[0166] In some embodiments, after detecting that the user completes fingerprint verification on the fingerprint recognition area, the electronic device 100 can display a payment success prompt 450, as shown in FIG. 4G.

[0167] As shown in FIG. 4G, the payment success prompt 450 can be used to prompt the user that the payment is successful. The payment success prompt 450 can include any one or more of the following: a payee 452, an amount to be paid 453, an actual payment amount 454, a discount amount 455, a payment method 456, and a completion control 451. The payee 452 can be used to prompt the user to check the account of the payee (e.g., the account number of the payee, etc.), which can facilitate the user to check whether the payee is correct. The amount to be paid 453 can be used to prompt the user to pay the amount. The actual payment amount 454 can be used to prompt the user to pay the actual amount. The discount amount 455 can be used to prompt the user to the discount amount, and the sum of the discount amount and the actual payment amount is the amount to be paid. Optionally, the discount amount 455 can also prompt the user to the specific discount activity, such as "XX bank payment of 45 yuan or more, 5 yuan off", etc. The payment method 456 can be used to prompt the user to use the current payment method, such as "AA bank savings card", etc. In some embodiments, the completion control 451 can be used to trigger the electronic device 100 to stop displaying the payment success prompt 450.

[0168] 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 determine the most preferential payment method based on the preferential activities of the merchant directly, and display the payment verification prompt 440 as shown in FIG. 4F. In other embodiments, if the electronic device 100 enables the password-free payment function, the electronic device 100 can no longer display the payment verification prompt, but can directly display the payment success prompt 450 as shown in FIG. 4G.

[0169] It can be understood that the above-mentioned embodiments shown in FIGS. 4D-4G are only some examples, and in the embodiments of the present application, the electronic device 100 can also complete payment in a manner different from the above-mentioned embodiments, for example, display payment options different from the above-mentioned embodiments, display payment verification prompts or payment success prompts different from the above-mentioned embodiments, and the like, which are not limited herein.

[0170] The specific flow of a payment method provided by the embodiments of the present application will be introduced below.

[0171] FIG. 5 shows a flow diagram of a payment method provided by the embodiments of the present application.

[0172] As shown in FIG. 5, the specific flow of a payment method provided by the embodiments of the present application can include the following steps:

[0173] S501. The electronic device 100 acquires merchant preferential information 1.

[0174] The merchant preferential information 1 can include preferential activities of one or more merchants.

[0175] In some embodiments, the merchant preferential information 1 can include preferential activities of one or more merchants in a specific area (for example, the geographic fence A1), and the specific content of the preferential activities of the one or more merchants can refer to the related description in the embodiments shown in Table 2 below.

[0176] In other embodiments, the merchant preferential information 1 can also include preferential activities of one or more merchants in a plurality of adjacent geographic fence ranges.

[0177] In a possible implementation manner, the electronic device 100 can acquire the merchant preferential information 1 when entering a specified area (for example, the geographic fence A1). For example, the electronic device 100 acquires the merchant preferential information 1 including preferential activities of one or more merchants in the geographic fence A1, and the specific manner of acquiring the merchant preferential information 1 can refer to the related description in the embodiments shown in FIG. 6 below, which is not described herein temporarily.

[0178] In another possible implementation manner, the electronic device 100 can also acquire the merchant preferential information 1 in the process of interacting with the payment device 200.

[0179] S502. The electronic device 100 enters the radio frequency field of the payment device 200.

[0180] S503. The payment device 200 sends a Probe frame to the electronic device 100.

[0181] The Probe frame can be used to indicate that the payment device 200 supports a specified NFC protocol, for example, a first protocol. In some embodiments, the payment device 200 can periodically send the Probe frame.

[0182] S504. After receiving the Probe frame, the electronic device 100 sends a Probe ACK frame.

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

[0184] If the electronic device 100 does not support the specified NFC protocol (for example, the first protocol) indicated by the Probe frame, the electronic device 100 can not send the Probe ACK frame.

[0185] S505. After receiving the Probe ACK frame, the payment device 200 sends a Pick frame, and the Pick frame carries device characteristic information of the payment device 200, and the device characteristic information is used to indicate that the service type of the payment device 200 is no-code payment.

[0186] The device characteristic information can include a device service identifier (SID) and a device organization identifier (also referred to as a NFC device organization unique identifier (ND_OUI)).

[0187] Optionally, the device characteristic information can include a device service identifier (SID), a device organization identifier (ND_OUI), and a device group identifier (also referred to as a NFC device group identifier (ND_GID)).

[0188] 1. The device service identifier (SID) can be used to indicate the type of NFC service supported by the payment device 200 on the basis of NFC function.

[0189] In a possible implementation, the type of the NFC service can include a main service type and a sub-service type. Therefore, the service identity can include a main service identity and a sub-service identity. The main service identity can be used to indicate the main service type supported by the payment device 200, and the sub-service identity can be used to indicate the sub-service type supported by the payment device 200 under a certain main service type. The main service type can include no-code payment, and optionally, the main service type can also include one or more of the following: one or more of access control, key, transportation, bank, digital currency, digital certificate, electronic ticket, wireless charging, tap-to-tap, and multi-functional card. The sub-service type corresponding to the no-code payment can include general service, member card preferential service, and payment institution preferential service.

[0190] The main service identity can occupy 1 byte (Byte), and the sub-service identity can occupy 1 byte (Byte). For example, Table 1 shows the correspondence between the device main service identity, the device sub-service identity, and the sub-service type when the main service type is no-code payment according to an embodiment of the present application.

[0191] Table 1

[0192] As shown in Table 1, when the main service type is no-code payment, the device main service identity can be 0x07; if the sub-service type is general service, the device sub-identity can be 0x01; if the sub-service type is payment preferential service (including payment institution preferential service and / or member card preferential service), the device sub-identity can be 0x02; if it is necessary to add a sub-service type, an unoccupied identity in the reserved multiple identities, i.e., 0x00, 0x03-0xFF, can be selected as the device sub-service identity corresponding to the added sub-service type.

[0193] It can be understood that the embodiment shown in Table 1 is only an example, and in the embodiments of the present application, the device service identity can also use different identities from the above-described embodiments. In addition, the no-code payment can also include more, fewer, or different sub-service types and device sub-service identities than the above-described embodiments, which are not limited in the present application.

[0194] According to the above embodiments, in the Pick frame sent by the payment device 200, the device service identifier for indicating the non-cash payment can be carried, for example, 0x07 shown in Table 1, and the like. Optionally, the device sub-service identifier can also be carried, for indicating the sub-service type of the payment device 200. Since the device characteristic information is used to indicate that the service type of the payment device 200 is the non-cash payment in step S505, the device main service identifier that can be carried in the Pick frame can be 0x07 shown in Table 1, so that the service type of the payment device 200 can be indicated by the device service identifier in the device characteristic information.

[0195] 2. The device organization identifier (ND_OUI) can be used to indicate the manufacturer that provides the NFC service by using the payment device 200, for example, the merchant A, the convenience store B, the self-service vending machine C, and the like. The registration management organization of the NFC protocol standard organization 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 service provided by the payment device 200 belongs. The device group identifier can be assigned according to the use and location of the payment device 200. Different NFC services can have different group divisions.

[0197] S506. The electronic device 100 determines that the service type of the payment device 200 is the non-cash payment based on the device characteristic information of the payment device 200.

[0198] In some embodiments, the electronic device 100 can determine that the service type of the payment device 200 is the non-cash payment based on the device service identifier of the payment device 200.

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

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

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

[0202] The amount to be paid refers to the amount that the merchant should collect based on the actual goods purchased by the user.

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

[0204] S509. The electronic device 100 determines one or more preferential activities of the merchant 1 from the merchant preferential information 1 based on the merchant ID, the merchant 1 being the merchant to which the payment device 200 belongs.

[0205] S510. The electronic device 100 determines the payment method 1 from the payment methods supported by the one or more payment devices 200 based on the one or more preferential activities of the merchant 1.

[0206] When the service type of the payment device 200 is determined to be the general service in the non-crypto 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 payment device 200 from the payment methods supported by the one or more payment devices 200, and determine the payment method 1 with the highest priority from the one or more payment methods supported by both the electronic device 100 and the payment device 200 based on the priority of the payment method preset by the electronic device 100.

[0207] S511. The electronic device 100 determines the payment credential 1 of the payment method 1, the actual payment amount 1, and the payment permission 1, the payment credential 1 being used to indicate the payment account 1 of the payment method 1.

[0208] In the embodiments of the present application, the payment permission can include a password-free payment permission and a verification payment permission. The password-free payment permission is used to authorize the receiving end to deduct from the specified payment account in the password-free payment scenario. The verification payment permission is used to authorize the receiving end to deduct from the specified payment account in the non-password-free payment scenario, and the verification payment permission can be obtained after the electronic device 100 detects that the user completes the payment verification (i.e., the user's identity verification is passed).

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

[0210] S512. The electronic device 100 sends the payment response 1, the payment response 1 including the payment credential 1 and the payment permission 1.

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

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

[0213] Optionally, the payment response 1 can further include the actual payment amount 1.

[0214] S513. The payment recipient device 200 deducts the payment account 1 based on the payment credential 1 and the payment permission 1, and the deduction amount is the actual payment amount 1.

[0215] The specific manner in which the payment recipient device 200 deducts the payment account 1 based on the payment credential 1 and the payment permission 1 can refer to the related steps in the embodiments shown in FIG. 7 or FIG. 8 below, which are not described here in detail.

[0216] It can be understood that the embodiment shown in FIG. 5 is only an example, and in the embodiments of the present application, the electronic device 100 and the payment recipient device 200 can complete payment by using different interaction steps from the above-described embodiments, which are not limited herein.

[0217] By using the payment method provided in the embodiments of the present application, the payment process can be simplified, and the payment efficiency can be improved.

[0218] In some embodiments, the merchant preferential information 1 can include preferential activities of one or more merchants in the geographic fence A1. The electronic device 100 can obtain the merchant preferential information 1 when entering the geographic fence A1.

[0219] For example, FIG. 6 shows a flowchart of an embodiment of the present application for an electronic device 100 to obtain merchant preferential information 1.

[0220] As shown in FIG. 6, the specific process of an embodiment of the present application for an electronic device 100 to obtain merchant preferential information 1 can include the following steps:

[0221] S601. The electronic device 100 detects that it enters the geographic fence A1.

[0222] The electronic device 100 has a positioning function, and the electronic device 100 can obtain a fuzzy position or a precise position of the electronic device 100 through the positioning function. The precision of the precise position is higher than that of the fuzzy position. The electronic device 100 can determine whether the electronic device 100 enters the geofence A1 based on the obtained fuzzy position / precise position.

[0223] In the embodiments of the present application, the 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). The geofence can be paired with a specified hardware / software application, which can respond to the boundary in a certain way according to the indication of the program parameters. For example, when the electronic device 100 crosses the virtual boundary of the geofence A1 and enters the area surrounded by the geofence A1, the application can detect that the electronic device 100 enters the geofence A1; when the electronic device 100 crosses the virtual boundary of the geofence A1 and leaves the area surrounded by the geofence A1, the application can detect that the electronic device 100 leaves the geofence A1.

[0224] S602. The electronic device 100 determines that the precise position of the electronic device 100 is the position 1.

[0225] Step S602 is an optional step.

[0226] In some embodiments, after the electronic device 100 obtains the fuzzy position of the electronic device 100 and determines that the electronic device 100 enters the geofence A1 based on the fuzzy position, the electronic device 100 can perform step S602.

[0227] After obtaining the precise position (i.e., the position 1) of the electronic device 100, the electronic device 100 can optionally determine whether the electronic device 100 enters the geofence A1 again based on the position 1. If the position 1 belongs to the area surrounded by the geofence A1, the electronic device 100 enters the geofence A1; if the position 1 does not belong to the area surrounded by the geofence A1, the electronic device 100 does not enter the geofence A1. In this way, it can be more accurately determined whether the electronic device 100 enters the geofence A1, the accuracy of the determination is improved, and misjudgment is avoided.

[0228] S603. The electronic device 100 sends a discount information request 1 to the payment cloud server 300, and the discount information request 1 includes the position 1 and / or the geofence A1.

[0229] The preferential information request 1 can be used to request the payment cloud server 300 to send the merchant preferential information 1 corresponding to the geographic fence A1, and the merchant preferential information 1 can include preferential activities of one or more merchants in the geographic fence A1. The specific content of the preferential activities can refer to the related description in the following step S604.

[0230] S604. The payment cloud server 300 sends the merchant preferential information 1 including preferential activities of one or more merchants in the geographic fence A1 to the electronic device 100.

[0231] The payment cloud server 300 can store one or more geographic fences and merchant preferential information corresponding to the geographic fences, and the merchant preferential information of each geographic fence can include preferential activities of one or more merchants in the corresponding geographic fence. The merchant preferential information can include a merchant identification (ID) and a preferential activity. In some embodiments, the preferential activity can include a discount rule, and optionally, the preferential activity can further include any one or more of the following: a product identification and an identification of a payment method. Each merchant can include one or more preferential activities, and the preferential activities can be used to determine a preferential amount. The preferential amount of the preferential activity can be related to a payment method, a merchant, a product to be purchased, and a number of products, which are not limited in the present application.

[0232] For example, Table 2 shows a corresponding relationship between a geographic fence and preferential information stored by the payment cloud server 300 according to an embodiment of the present application.

[0233] Table 2

[0234] As shown in Table 2, the payment cloud server 300 can store one or more geofences and corresponding discount information of the geofences. The discount information can include a merchant ID and a discount activity, and the discount activity can include any one or more of a product identifier, a payment method identifier, and a discount rule. For example, the payment cloud server 300 can store discount information of the geofence A1 and discount information of the geofence A2. According to Table 2, the discount information of the geofence A1 can include a discount activity of the merchant NO. 1 and a discount activity of the merchant NO. 2. The discount activity of the merchant NO. 1 can include two discount activities. The first discount activity of the merchant NO. 1 can include a product identifier “product P1” and a discount rule “two for eight”, indicating that if the product P1 is purchased and the number of the product P1 is greater than or equal to 2, the price of the product P1 can be discounted by 80% regardless of the payment method. The second discount activity of the merchant NO. 1 can include a payment method identifier “payment method 1” and a discount rule “50 yuan for 5 yuan”, indicating that if the payment method 1 is used, the total price of the product can be reduced by 5 yuan for every 50 yuan. The discount activity of the merchant NO. 2 can include a product identifier “product P2”, a payment method identifier “payment method 2”, and a discount rule “20 yuan for 5 yuan”, indicating that if the product P2 is purchased and the payment method 2 is used, the total price of the product P2 can be reduced by 5 yuan for every 20 yuan. The discount information of the geofence A2 can include a discount activity of the merchant NO. 3, and the discount activity of the merchant NO. 3 can include a discount rule “9 for all”, indicating that regardless of the product purchased and the payment method used, the total price of the product can be discounted by 90% if the product is purchased in the merchant NO. 3.

[0235] It can be understood that the above embodiment shown in Table 2 is only an example. In the embodiments of the present application, the payment cloud server 300 can also store more, less or different geofences and corresponding discount information of the geofences than the above embodiment, and the discount information can also be different from the above embodiment, which is not limited herein.

[0236] In a possible implementation, after receiving the discount information acquisition request 1, the payment cloud server 300 can determine that the geofence in which the electronic device 100 is located is the geofence A1 based on the position 1 and / or the geofence A1 in the discount information acquisition request 1, and determine the merchant discount information 1 corresponding to the geofence A1 based on the geofence A1.

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

[0238] S605. The electronic device 100 displays the merchant discount information 1.

[0239] Step S605 is an optional step.

[0240] In some embodiments, after receiving the merchant offer information 1, the electronic device 100 can display the merchant offer information 1.

[0241] For example, the interface in which the electronic device 100 displays the merchant offer information 1 can refer to the interface 410 in the embodiment shown in FIG. 4B.

[0242] In this way, when entering a geographic fence, the electronic device 100 can obtain merchant offer information corresponding to the geographic fence, and display the merchant offer information, so as to facilitate the user to select whether to shop by himself / herself, and also can improve the customer flow of the merchant. In addition, the user can also make payment based on the merchant offer information, and save shopping expenses.

[0243] It should be noted that after receiving the payment credential sent by the electronic device 100, the payment device 200 can deduct the payment account indicated by the payment credential through the payment cloud server 300. When deducting the payment account based on the payment credential, the payment cloud server 300 also needs to obtain the payment permission corresponding to the payment account. The payment permission can include a password-free payment permission and a verification payment permission, and the specific functions of the two permissions can refer to the related description in the embodiment shown in FIG. 5.

[0244] In some application scenarios, the payment cloud server 300 can determine whether to obtain the verification payment permission from the electronic device 100 based on whether the current payment account can use the password-free payment in this payment. The specific interaction process can refer to the related description in the embodiment shown in FIG. 7.

[0245] FIG. 7 shows a flow diagram of a payment account deduction method according to an embodiment of the present application.

[0246] As shown in FIG. 7, the electronic device 100 can include a payment application set 11, and the specific process in which the payment device 200 deducts the payment account based on the payment credential sent by the electronic device 100 can include the following steps:

[0247] S701. The payment device 200 sends payment information 1 to the payment cloud server 300, the payment information 1 including a payment amount, a payment credential, and a payment account.

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

[0249] The payment credential is used to indicate a payment account for payment, the payment account is an account for the merchant of the payment device 200 to receive payment, the payment amount can include a payable amount and / or a real payment amount, and optionally, a discount amount. The payable amount refers to the amount that the payment account should collect, the real payment amount refers to the deduction amount of the payment account, and the discount amount can refer to the difference between the payable amount and the real payment amount.

[0250] S702. The payment cloud server 300 determines whether the payment account indicated by the payment credential enables the password-free payment.

[0251] If the payment account enables the password-free payment, the payment cloud server 300 can perform the following step S703.

[0252] If the payment account does not enable the password-free payment, the payment cloud server 300 can perform the following step S704.

[0253] S703. The payment cloud server 300 determines whether the real payment amount is greater than a preset password-free payment amount.

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

[0255] If the real payment amount is greater than the password-free payment amount, the payment cloud server 300 can perform the following step S704.

[0256] If the real payment amount is less than or equal to the password-free payment amount, the payment cloud server 300 can perform the following step S706.

[0257] S704. The payment cloud server 300 sends a payment verification request to the payment application set 11.

[0258] It should be noted that in the embodiments of the present application, the payment application set 11 can include one or more applications (also referred to as payment applications) having payment functions, and each payment application can manage one or more small programs (also referred to as payment small programs) having payment functions, and each payment small program can be regarded as a payment method.

[0259] In some embodiments, the payment verification request is used to request the user to perform payment verification. In other embodiments, the payment verification request can also be used to request the electronic device 100 to send a payment permission verification to the payment cloud server 300.

[0260] In this way, in the non-password-free payment scenario, or in the scenario where the payment amount is greater than the password-free payment amount, the security of the user's property can be improved.

[0261] S705. The payment application set 11 receives and responds to the user's payment verification operation, and sends the payment permission verification to the payment cloud server 300.

[0262] The user can complete payment verification through one or more of face, fingerprint, password, etc.

[0263] The payment permission verification is used to authorize the payment cloud server 300 to deduct the payment account indicated by the payment credential.

[0264] S706. The payment cloud server 300 deducts the payment account indicated by the payment credential based on the payment information 1, and the deduction amount is the actual payment amount.

[0265] In the case of password-free payment, and the actual payment amount is less than or equal to the password-free payment amount, the payment cloud server 300 can directly deduct based on the payment information. In this way, even in the offline state of the electronic device 100, the payment can still be completed.

[0266] In the case of non-password-free payment, and 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 based on the payment information.

[0267] After step S706 is executed, the payment cloud server 300 can execute the following steps S707 and S709 in parallel, or execute step S707 and step S709 in sequence, and the execution order of step S707 and step S709 is not limited by the embodiments of the present application.

[0268] S707. The payment cloud server 300 pays the payment account, and the payment amount includes the actual payment amount and the discount amount.

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

[0270] In other embodiments, the payment information 1 can carry the discount amount, or carry the payable amount and the actual payment amount. In this case, the payment cloud server 300 can determine the discount amount based on the payment information 1. Optionally, the payment cloud server 300 can check the discount amount based on the discount activity of the payment method stored by itself before paying the payment account, and after the check is correct, pay the payment account.

[0271] S708. The payment cloud server 300 sends the payment notification 1 to the payment device 200.

[0272] The payment notification 1 is used to notify the payment device 200 that the payment account has received a specified amount of money. The payment notification 1 can include the payment amount, and optionally, any one or more of the following: the payment account, the payment account, the time of arrival, the actual payment amount, the discount amount, etc.

[0273] S709. The payment cloud server 300 sends the payment notification 1 to the payment application set 11.

[0274] After performing step S706, the payment cloud server 300 can perform step S709.

[0275] The payment notification 1 is used to notify the electronic device 100 that the payment has been completed.

[0276] The payment notification 1 can include the actual payment amount, and optionally, any one or more of the following: the payment amount, the discount amount, the payment account, the payment time, etc.

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

[0278] It can be understood that the above-mentioned embodiment shown in FIG. 7 is only an example, and in the embodiments of the present application, the payment device 200 can also complete the payment in other ways, for example, the merchant backend server and the payment cloud server 300 can complete the above-mentioned interaction process, etc., which is not limited in the present application.

[0279] In some application scenarios, after determining the payment account, the electronic device 100 can also determine the way and timing of sending the payment permission to the payment cloud server 300 based on whether the payment account can be used for password-free payment in this payment. In the case of password-free payment, the electronic device 100 can send the payment credentials and the password-free payment permission to the payment cloud server 300 through the payment device 200. In the case of non-password-free payment, the electronic device 100 can send the payment verification permission to the payment cloud server 300. The specific interaction mode can refer to the embodiment shown in FIG. 8.

[0280] For example, the payment application corresponding to the determined payment method is payment application A, and FIG. 8 shows a payment process after determining the payment method according to an embodiment of the present application.

[0281] As shown in FIG. 8, the electronic device 100 can include an NFC service module 12 and a payment application A, and the payment process after determining the payment method according to an embodiment of the present application can include the following steps:

[0282] S801. The NFC service module 12 sends a payment notification to the payment application A, and the payment notification includes the identification of the payment method and the actual payment amount.

[0283] In this embodiment, the NFC service module 12 may include the NFC module 102 and the NFC basic service module shown in FIG3A above. The NFC service module 12 may also refer to the NFC protocol stack shown in FIG3B above. In some embodiments, step S1104 and step S1106 below may be executed by the access layer in the NFC protocol stack shown in FIG3B above; that is, the access layer processes the received data and controls the transmitted data.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0305] The specific details of steps S807 to S809 can be found in the description of steps S706 to S708 in the embodiment shown in Figure 7 above, and will not be repeated here.

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

[0307] 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 referred to the relevant description of the payment notification 1 in the embodiment shown in Figure 7 above.

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

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

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

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

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

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

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

[0315] Step S813 is an optional step.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0331] It is understood that the embodiment shown in Figure 8 is only an example. In the embodiments of this application, the payment application corresponding to the payment method determined by the electronic device 100 may also be a different payment application from the embodiment shown in Figure 8 above. This application does not limit it here.

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

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

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

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

[0336] For example, Figure 9 shows a schematic diagram of a payment method provided in an embodiment of this application.

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

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

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

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

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

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

[0343] The specific details of steps S901 to S905 can be found in the relevant descriptions in the embodiment shown in Figure 6 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0367] 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 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, and the payment cloud server 300 will complete the payment based on the receiving account, payment account 1, and amount due. The specific process of the payment cloud server 300 completing the payment based on the receiving account, payment voucher 1, and amount due can also refer to the relevant steps in the embodiments shown in Figure 7 or Figure 8 above, and will not be repeated here.

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

[0369] Step S917 is an optional step.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0383] For example, payment success notification 1 can be payment success notification 450 in the embodiment shown in Figure 4G above.

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

[0385] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0400] 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, and the payment cloud server 300 will complete the payment based on the receiving account, payment account 1, and amount due. The specific process of the payment cloud server 300 completing the payment based on the receiving account, payment account 2, and amount due can also refer to the relevant steps in the embodiment shown in Figure 6 below, which will not be repeated here.

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

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

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

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

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

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

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

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

[0409] It is understood that the embodiment shown in Figure 9 is only an example. 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 it here.

[0410] The payment method provided in this application allows for the acquisition and display of promotional information corresponding to a geofence upon entry, facilitating user decision-making and increasing customer traffic for merchants. Furthermore, users can make payments based on these promotional offers, saving on shopping expenses.

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

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

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

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

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

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

[0417] In another possible implementation, in step S912 shown in Figure 9, 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, and the corresponding payment account 1, actual payment amount 1, etc., the electronic device 100 can send the payment account 1, receiving account 1, and the amount due and / or 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.

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

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

[0420] For example, Figure 10 shows a flowchart of another payment method provided in an embodiment of this application.

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

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

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

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

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

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

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

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

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

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

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

[0432] The specific details of steps S1001 to S1009 can be found in the relevant descriptions in the embodiment shown in Figure 5 above.

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

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

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

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

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

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

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

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

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

[0442] The specific contents of payment voucher 3 and payment method 3 can be found in the descriptions of payment voucher 1 and payment license 1 in the embodiment shown in Figure 5 above, and will not be repeated here.

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

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

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

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

[0447] The details of step S1014 can be found in the description of step S513 in Figure 5 above, and will not be repeated here.

[0448] It is understood that the embodiment shown in Figure 10 is only an example. 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 invention.

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

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

[0451] For example, Figure 11 shows a flowchart of another payment method provided in an embodiment of this application.

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

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

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

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

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

[0457] The NFC service module 12 may include the NFC module 102 and the NFC basic service module in the embodiment shown in FIG3A above. The NFC service module 12 may also refer to the NFC protocol stack in the embodiment shown in FIG3B above. In some embodiments, step S1104 and step S1106 below may be executed by the access layer in the NFC protocol stack shown in FIG3B above, that is, the access layer processes the received data and controls the transmitted data.

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

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

[0460] After determining the service type, in the NFC protocol stack shown in Figure 3B above, 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 with payment functions (also referred to as payment application set 11) 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.

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

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

[0463] For details on steps S1101 to S1107, please refer to the relevant descriptions of steps S501 to S507 shown in Figure 5 above.

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

[0465] The discount capability inquiry request can be used to inquire about the discounted payment methods supported by the electronic device 100. The specific definition of the discounted payment methods can be referred to the relevant description in the embodiment shown in Figure 10 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0492] 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 in the relevant descriptions in the embodiment shown in Figure 5 above, and will not be repeated here.

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

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

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

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

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

[0498] The specific process of the payment device 200 deducting funds based on the payment account 4 can be referred to the relevant steps in the embodiments shown in Figure 7 or Figure 8 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

[0508] S1117. Payment device 200 determines whether the payment device 200 supports membership card payment as a preferential payment method.

[0509] Steps S1117 to S1122 are optional steps.

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

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

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

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

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

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

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

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

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

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

[0520] In some embodiments, the specific process of the payment device 200 deducting payment based on the member account can also refer to the deduction process in the embodiments shown in Figure 7 or Figure 8 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0534] For details regarding the platform's promotional information, please refer to the relevant descriptions in the embodiment shown in Figure 10 above.

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

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

[0537] Table 3

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

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

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

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

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

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

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

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

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

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

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

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

[0550] In some embodiments, the specific process of step S1128 can also refer to the relevant description in the embodiments shown in Figure 7 or Figure 8 above, and will not be repeated here.

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

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

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

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

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

[0556] It is understood that the embodiment shown in Figure 11 is only an example. In the embodiments of this application, the electronic device 100 and the payment device 200 may also use different interaction processes than those in the above embodiments to complete the payment. This application does not limit this.

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

[0558] Figure 12A shows a schematic diagram of the functional modules of a payment cloud server 300 provided in an embodiment of this application.

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

[0560] 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 embodiment shown in Figure 6 above, the payment cloud server 300 can refer to the discount information module 1210.

[0561] The payment module 1220 can interact with any one or more of the electronic device 100 and the payment receiving device 200 to complete the payment. For example, in the embodiments shown in Figures 7 and 8 above, the payment cloud server 300 can refer to the payment module 1220.

[0562] It is understood that the embodiment shown in Figure 12A is only an example. In the embodiments of this application, the payment cloud server 300 may also include more, fewer, or different functional modules than those in the above embodiments, and this application does not limit this. In addition, in one possible implementation, the discount information module 1210 and the payment module 1220 may also be different servers in the payment cloud server 300, and this application does not limit this.

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

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

[0565] The following description uses electronic device 100 as an example to illustrate the embodiment. It should be understood that the electronic device 100 shown in FIG12B is merely an example, and the electronic device 100 may have more or fewer components than those shown in FIG12B, may combine two or more components, or may have different component configurations. The various components shown in the figures 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.

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

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

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

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

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

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

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

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

[0574] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (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.

[0575] 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).

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

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

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

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

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

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

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

[0583] 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. 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 in the embodiment shown in FIG3A above, and will not be repeated here.

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

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

[0586] The communication device of the present application embodiment will now be described in detail with reference to Figures 13 to 16.

[0587] Referring to FIG13, which is a schematic diagram of the structure of a 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. As shown in FIG13, the communication device 1300 may include a transceiver unit 1310 and a processing unit 1320.

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

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

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

[0591] Referring to FIG14, which is a schematic diagram of the structure of a 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. As shown in FIG14, the communication device 1400 may include a transceiver unit 1410 and a processing unit 1420.

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

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

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

[0595] The above describes the electronic device 100 and the payment device 200 of the embodiments of this application. It should be understood that any product with the functions of the electronic device 100 described in FIG13 above, and any product with the functions of the payment device 200 described in FIG14 above, falls within the protection scope of the embodiments of this application.

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

[0597] Referring to Figure 15, Figure 15 is a schematic diagram of the structure of a communication device 1500 provided in an embodiment of this application. The communication device 1500 can be an electronic device 100, or a device therein. As shown in Figure 15, 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, etc. For example, it can be a central processing unit and / or an NFC controller, etc. The transceiver 1502 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1502 can include a receiver and a transmitter. The receiver can be referred to as a receiver or receiving circuit, etc., and is used to implement a receiving function, such as an NFC receiving function; the transmitter can be referred to as a transmitter or transmitting circuit, etc., and 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 (not shown in Figure 15), for example, an NFC antenna, wherein the NFC antenna can be a coil-type antenna. The antenna 1503 and / or radio frequency unit may be located inside the communication device 1500 or separate from the communication device 1500, that is, the antenna 1503 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

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

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

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

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

[0603] 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), p-type metal-oxide-semiconductor (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

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

[0605] (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.

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

[0607] Referring to Figure 16, Figure 16 is a schematic diagram of the structure of a communication device 1600 provided in an embodiment of this application. The communication device 1600 can be a payment receiving device 200, or a device therein. As shown in Figure 16, 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, for example, an NFC controller. The transceiver 1602 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 1602 can include a receiver and a transmitter. The receiver can be referred to as a receiver or receiving circuit, etc., and is used to implement a receiving function; the transmitter can be referred to as a transmitter or transmitting circuit, etc., and 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 radio frequency unit may be located inside the communication device 1600 or separate from the communication device 1600, that is, the antenna 1603 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

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

[0610] In one design, the communication device 1600 can be used to perform the functions of the payment device 200 in the foregoing embodiments: the processor 1601 can be used to perform the functional steps related to NFC protocol parsing and encapsulation, NFC service processing flow and / or other processes used in the technology described herein, performed by the payment device 200 in the embodiment shown in FIG16; the transceiver 1602 can be used to perform the functional steps related to NFC sending and NFC receiving performed by the payment device 200 in the embodiment shown in FIG16 and / or other processes used in the technology described herein.

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

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

[0613] Figure 17 shows a flowchart of a payment method provided in an embodiment of this application.

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

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

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

[0617] For example, the first identifier of the first merchant can be a merchant ID, and the first amount can refer to the amount payable, that is, the amount that the receiving device should collect. The first payment request can be payment request 1 in the embodiment shown in Figure 5, payment request 2 in the embodiment shown in Figure 9, or payment request 3 in the embodiment shown in Figure 10, etc., which will not be elaborated here.

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

[0619] For example, one or more promotional activities of the first merchant may be promotional activity 1 in the embodiment shown in Figure 9 above.

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

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

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

[0623] For example, the first payment method can be payment method 1 in the embodiment shown in Figure 5, payment method 1 in the embodiment shown in Figure 9, or payment method 3 in the embodiment shown in Figure 10, etc., which will not be elaborated here.

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

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

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

[0627] The first server can be the payment cloud server 300 in the above embodiments. In some embodiments, the first server can be the discount information module 1210 in the payment cloud server 300 in the embodiment shown in FIG12A.

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

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

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

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

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

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

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

[0635] For example, the first geofence can be geofence A1 in the embodiments of Figures 6 and 9 above.

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

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

[0638] For example, the specific way in which the electronic device displays the first discount information can be referred to the relevant description in the embodiment shown in Figure 6 above.

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

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

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

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

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

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

[0645] For example, taking the embodiment shown in Figure 5 above, 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. As another example, taking the embodiment shown in Figure 9 above, 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 yet another example, taking the embodiment shown in Figure 10 above, the first payment response can be payment response 3, the first payment credential can be payment credential 3, and the first payment account can be payment account 3, etc., and will not be elaborated further here.

[0646] 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 embodiments, such as the payment module 1220 in the payment cloud server 300 in the embodiment shown in Figure 12A.

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

[0648] The first receiving account refers to the receiving account of the receiving device. For a detailed description of its functions, please refer to the relevant descriptions in the embodiments shown in Figure 7 or Figure 8 above. The second amount refers to the actual amount paid by the electronic device.

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

[0650] In one possible implementation, payment is completed via a first payment method, specifically including: sending a third payment response 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.

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

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

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

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

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

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

[0657] For example, the one or more payment options may be one or more payment options in the embodiment shown in FIG4E above, such as AA bank card option 431, payment application A option 432, payment application B option 433, etc.

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

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

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

[0661] 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. The first notification may be a payment notification as described in the above embodiments (e.g., payment notification 1 in the embodiment shown in Figure 7).

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

[0663] 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 of successful payment. For example, the first notification could be payment success notification 1 in the embodiment shown in Figure 9 above, or payment success notification 3 in the embodiment shown in Figure 11 above, etc.

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

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

[0666] The first crowdsourcing can be the payment crowdsourcing 1 in the embodiment shown in Figure 9 above.

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

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

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

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

[0671] For example, the first promotional activity can be promotional activity 2 in the embodiment shown in Figure 9 above.

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

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

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

[0675] Figure 18 shows a flowchart of another payment method provided in an embodiment of this application.

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

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

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

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

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

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

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

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

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

[0685] For example, the second discount information can be the merchant discount information 2 in the embodiment shown in Figure 9 above.

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

[0687] For example, the second payment method can be payment method 2 in the embodiment shown in Figure 9 above.

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

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

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

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

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

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

[0694] Figure 19 shows a flowchart of a payment method provided in an embodiment of this application.

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

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

[0697] 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 discount information module 1210 in the payment cloud server 300 in the embodiment shown in Figure 12A.

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

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

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

[0701] The specific details of steps S1901-S1904 can be found in the description of steps S501-S504 shown in Figure 5 above, and will not be repeated here.

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

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

[0704] In another possible implementation, the device feature 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 feature information can be found in step S505 of Figure 5 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0725] 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).

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

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

[0728] 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).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0753] 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).

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

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

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

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

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

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

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

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

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

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

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

[0765] After receiving a payment completion notification, electronic device 100 can output a payment completion prompt, which indicates to the user that the payment amount has been successfully made. This prompt can be text-based, audio-based, image-based, mechanically vibrating, or an indicator light, etc. For example, after receiving the payment completion notification, electronic device 100 can display a payment completion page or a payment success prompt (e.g., the payment success prompt 450 shown in Figure 4G above). 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 electronic device 100. After receiving the payment failure notification, electronic device 100 can display a payment failure page. This payment failure page includes a payment failure prompt, which indicates to the user that the payment has failed.

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

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

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

[0769] It is understood that the embodiment shown in Figure 19 is only an example. 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 invention.

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

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

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

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

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

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

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

[0777] 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 an electronic device, characterized by, The method comprises: After entering the radio frequency field of the payment device of the first merchant, receiving a first payment request sent by the payment device, the first payment request comprising a first identifier and a first amount 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 methods supported by the payment device based on the first payment request; Determining a first payment method from the one or more payment methods supported by the payment device based on the one or more preferential activities of the first merchant; Completing payment through the first payment method.

2. The method of claim 1, wherein, The method further comprises: Sending the first identifier to a first server; Receiving one or more preferential activities of the first merchant sent by the first server.

3. The method of claim 1, wherein, The first payment request further comprises the one or more preferential activities of the first merchant.

4. The method of claim 1, wherein, Before entering the radio frequency field of the payment device of the first merchant, the method further comprises: Receiving first preferential information sent by a first server, the first preferential information comprising preferential activities of one or more merchants; The method further comprises: Determining the one or more preferential activities of the first merchant from the first preferential information based on the first identifier.

5. The method of claim 4, wherein, Before receiving the first preferential information sent by the first server, the method further comprises: When the electronic device enters a first geographic fence, sending a first request to the first server, the first request carrying an identifier of the first geographic fence, the first request being used to request the first server to send the first preferential information, the one or more merchants being located in the first geographic fence.

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

7. The method according to any one of claims 1 to 6, characterized in that, Displaying the first preferential information. The method further comprises:

8. The method according to any one of claims 1-6, characterized in that, Obtaining one or more payment methods supported by the payment device based on the first identifier.

9. The method according to any one of claims 1-8, characterized in that, The first payment request further comprises identifiers of the one or more payment methods supported by the payment device. The method further comprises:

10. The method according to any one of claims 1-8, characterized in that, Sending a first payment response to the payment device, the first payment response comprising a first payment credential, the first payment credential being used to indicate a first payment account of the first payment method. The first payment request further comprises a first payment account; The method further comprises: Determining a second amount corresponding to the first payment method based on the first amount and the one or more preferential activities of the first merchant; 11. The method according to any one of claims 1-8, characterized in that, Sending a second payment response to a second server, the second payment response comprising the first payment credential, the second amount and the first payment account, the first payment credential being used to indicate a first payment account of the first payment method. The method further comprises: sending a third payment response to the second server, the third payment response comprising a first payment credential, the first payment credential being used to indicate a first payment account of the first payment method.

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

13. The method of claim 9, wherein, The first payment response further comprises an identification of the first payment method.

14. The method of any one of claims 1-13, wherein, The determining the first payment method from the one or more payment methods based on the one or more preferential activities of the first merchant specifically comprises: determining a preferential amount of each of the one or more payment methods based on the one or more preferential activities of the first merchant; displaying one or more payment options, the one or more payment options comprising a first option corresponding to the first payment method, the first option comprising an identification of the first payment method and the preferential amount of the first payment method; receiving and responding to an operation of a user on the first option to determine the first payment method.

15. The method of any one of claims 1-13, wherein, The determining the first payment method from the one or more payment methods based on the one or more preferential activities of the first merchant specifically comprises: determining a preferential amount of each of the one or more payment methods based on the one or more preferential activities of the first merchant; determining the first payment method based on the preferential amount of each of the one or more payment methods, the first payment method being the payment method with the largest preferential amount among the one or more payment methods.

16. The method of any one of claims 1-15, wherein, The method further comprises: receiving a first notification sent by the second server, the first notification being used to notify the electronic device of a successful payment.

17. The method of any one of claims 1-15, wherein, The method further comprises: receiving a first notification sent by the second server, the first notification being used to notify the electronic device of a successful payment.

18. The method according to claim 16 or 17, characterized in that The method further comprises: determining a first preferential activity from the one or more preferential activities of the first merchant based on the first payment method; after the payment is completed by the first payment account using the first payment method, the method further comprises: sending a first crowd source to the first server, the first crowd source comprising location information of the electronic device, a first identification of the first merchant, and the first preferential activity.

19. The method of claim 18, wherein, The first notification comprises the first amount and / or a second amount, the first amount being a payment amount of the payment device, and the second amount being a payment amount of the electronic device; The first crowd source further comprises the first amount and / or the second amount.

20. The method of claim 18 or 19, wherein, after the first preferential activity is determined from the one or more preferential activities of the first merchant based on the first payment method, the method further comprises: sending the first preferential activity to the payment device.

21. The method of any one of claims 1-20, wherein, after entering a radio frequency field of the payment device, the method further comprises: receiving a probe frame sent by the payment device, the probe frame being used to indicate that the payment device supports a specified NFC protocol; sending a probe acknowledgement frame to the payment device, the probe acknowledgement frame being used to indicate that the electronic device supports the specified NFC protocol; receiving a pick frame sent by the payment device, the pick frame carrying device characteristic information of the payment device, the device characteristic information of the payment device including a service identifier and a device organization identifier, wherein the service identifier is used to indicate a type of NFC service supported by the payment device, and the device organization identifier is used to indicate a manufacturer that provides NFC service using the payment device; determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is no-code payment; sending a pick acknowledgement (Pick ACK) frame to the payment device, the Pick ACK frame being used to indicate that the electronic device has determined the type of NFC service of the payment device.

22. A payment method applied to an electronic device, comprising: The method comprises: after entering a radio frequency field of a payment device of the first merchant, receiving a first payment request sent by the payment device, the first payment request including a first identifier and a first amount of the first merchant; determining one or more preferential activities of the first merchant based on the first payment request; determining an identifier of one or more payment methods supported by the payment device based on the first payment request; determining a first payment method from the one or more payment methods based on the one or more preferential activities of the first merchant; determining a first preferential activity from the one or more preferential activities based on the first payment method; sending a fourth payment response to the payment device, the fourth payment response including the first payment credential and the first preferential activity, the first payment credential being used to indicate a first payment account of the first payment method; receiving second preferential information sent by the payment device, the second preferential information including one or more preferential activities of the first merchant; determining a second payment method and a second preferential activity based on the second preferential information; completing payment through the second payment method.

23. The method of claim 22, wherein, After the payment is completed through the second payment method, the method further comprises: sending a second crowd source to the first server, the second crowd source including location information of the electronic device, the first identifier of the first merchant, and the second preferential information.

24. A payment method applied to an electronic device, comprising: The method comprises: receiving first preferential information sent by a first server, the first preferential information including preferential activities of one or more merchants within a first geographic fence, the one or more merchants including a first merchant; receiving a first merchant identifier sent by a payment device; determining the second preferential information from the first preferential information based on the first merchant identifier; sending a first response to the payment device, the first response being used to indicate that the electronic device successfully receives the first merchant identifier; receiving a first selection command sent by a payment device of the first merchant; sending a first selection response to the payment device, the first selection response including an identifier of one or more payment applications supported by the electronic device and the second preferential information; receiving a second selection command sent by the payment device, the second selection command including an identifier of a first payment application; sending a second selection response to the payment-receiving device, the second selection response being used to indicate that the first payment application is selected successfully; completing payment through the first payment application.

25. The method of claim 24, wherein, The method further includes: sending a first request to the first server when the electronic device enters a first geofence, the first request carrying an identifier of the first geofence, the first request being used to request the first server to send the first preferential information; The first preferential information sent by the first server is received, and specifically includes: receiving a first response sent by the first server, the first response including the first preferential information.

26. The method of claim 24 or 25, wherein, The first merchant identifier sent by the payment-receiving device is received, and specifically includes: receiving device feature information sent by the payment-receiving device, the device feature information of the payment-receiving device including a service identifier and a device organization identifier, wherein the service identifier is used to indicate a 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 of claim 26, wherein, The method further includes: receiving a probe frame sent by the payment-receiving device, the probe frame being used to indicate that the payment-receiving device supports a specified NFC protocol; sending a probe acknowledgement (Probe ACK) frame to the payment-receiving device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; The device feature information sent by the payment-receiving device is received, and specifically includes: receiving a notification (Notify) frame sent by the payment-receiving device, the Notify frame carrying the device feature information of the payment-receiving device; The method further includes: determining, based on the device feature information of the payment-receiving device, that a type of NFC service of the payment-receiving device is no-code payment; The first response sent to the payment-receiving device specifically includes: sending a notification acknowledgement (Notify ACK) frame to the payment-receiving device, the Notify ACK frame being used to indicate that the Notify frame is received successfully; The method further includes: receiving a parameter negotiation command sent by the payment-receiving device; In response to the parameter negotiation command, sending a parameter negotiation response to the payment-receiving device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between an application layer of the payment-receiving device and the electronic device.

28. The method of any one of claims 24-27, wherein, The method further includes: displaying the first preferential information.

29. The method of any one of claims 24-28, wherein, The payment is completed through the first payment application, and specifically includes: receiving a first order command sent by the payment-receiving device, the first order command including a first order identifier and a first payment amount; sending a first order response to the payment-receiving device, the first order response being used to indicate that the first order command is received successfully; receiving a first initialization transaction command of the payment-receiving device, the first initialization transaction command being used to obtain a first payment credential of the first payment application; sending a first initialization transaction response to the payment-receiving device, the first initialization transaction response carrying the first payment credential.

30. The method of any one of claims 24-29, wherein, The method further includes: receiving a first payment notification sent by the payment-receiving device, the first payment notification being used to indicate payment success or payment failure; and / or, receiving a second payment notification sent by the second server, the second payment notification being used to indicate a payment success or a payment failure.

31. An electronic device, comprising: The chip system comprises: a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit the code instructions to the processing circuit, the processing circuit being used to run the code instructions to execute the payment method in any one of claims 1-30.

32. A chip system, characterized by The chip system comprises: a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit the code instructions to the processing circuit, the processing circuit being used to run the code instructions to execute the payment method in any one of claims 1-30.

33. A readable storage medium, characterized by, The chip system comprises: a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit the code instructions to the processing circuit, the processing circuit being used to run the code instructions to execute the payment method in any one of claims 1-30.

34. A computer program product, characterised in that, The chip system comprises: a processing circuit and an interface circuit, the interface circuit being used to receive code instructions and transmit the code instructions to the processing circuit, the processing circuit being used to run the code instructions to execute the payment method in any one of claims 1-30.

Images