Payment method and system, and related apparatus

Abstract

The present application discloses a payment method and system, and a related apparatus. The method comprises: after entering a radio frequency field of a collection device, receiving a first payment request sent by the collection device, wherein the first payment request comprises a first amount and an identifier of one or more payment modes supported by the collection device; on the basis of the first payment request, determining a first payment mode from among the one or more payment modes supported by the collection device; and completing payment by means of the first payment mode. In this way, an electronic device can complete payment by means of a touch with the collection device, thereby simplifying payment steps and improving payment efficiency.

Description

Payment method, system and related device

[0001] The present application claims priority to the Chinese patent application No. 202411025555.1, 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. 202510543139.9, 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] When a user makes a payment, the user can first open a payment application in a mobile phone, then open a payment QR code in the payment application, and show the payment QR code to a payee. After the payee completes the deduction by scanning the payment QR code through a designated electronic device, the mobile phone of the user can display a payment success interface, prompting the user that the payment has been completed. In this way, the payment function can be realized.

[0005] However, the above-mentioned payment method has complicated operation steps and low efficiency. SUMMARY

[0006] The present application provides a payment method, system and related device, which simplifies the payment steps and improves the payment efficiency.

[0007] In a first aspect, the present application provides a payment method, comprising: receiving a first payment request sent by a collection device after entering a radio frequency field of the collection device, the first payment request comprising a first amount and an identifier of one or more payment methods supported by the collection device; determining a first payment method from the one or more payment methods supported by the collection device based on the first payment request; and completing payment through the first payment method.

[0008] In this way, the electronic device can complete the payment through the touch with the collection device, which simplifies the payment steps and improves the payment efficiency.

[0009] In a possible implementation, before receiving the first payment request sent by the payment device, 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 a 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; 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 the 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 code-free payment; and 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.

[0010] In this way, the electronic device can communicate with the payment device based on the preset first protocol.

[0011] In a possible implementation, the determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is code-free payment specifically includes: determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is a first sub-service in code-free payment, the first sub-service being code-free payment service without a preferential payment mode.

[0012] In this way, in the case where it is determined that the payment device does not have preferential payment service, the electronic device does not need to acquire preferential information of each payment mode, thereby simplifying the payment step and improving payment efficiency.

[0013] In a possible implementation, the determining the first payment mode from the one or more payment modes supported by the payment device based on the first payment request specifically includes: determining the first payment mode from the one or more payment modes supported by the payment device based on a first operation of the user; or determining the first payment mode from the one or more payment modes supported by the payment device based on a preset payment priority.

[0014] In this way, the payment mode finally used can be determined based on user selection.

[0015] In a possible implementation, the determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is code-free payment specifically includes: determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is a second sub-service in code-free payment, the second sub-service being code-free payment service with a preferential payment mode.

[0016] In this way, the payment device can inform the electronic device that the payment device has a preferential payment service, so that the electronic device selects a payment method with a discount to save the user's expenses.

[0017] In a possible implementation, after determining that the type of the NFC service of the payment device is the second sub-service in the non-coding payment based on the device feature information of the payment device, the method further includes: receiving a first inquiry request sent by the payment device after entering the radio frequency field of the payment device, the first inquiry request being used to request to obtain a preferential payment method with a preferential activity; in response to the first inquiry request, sending a first preferential response to the payment device, the first preferential response including the identification of one or more preferential payment methods; receiving a first payment request sent by the payment device, specifically including: receiving the first payment request sent by the payment device based on the first preferential response, the first payment request carrying the identification of one or more preferential payment methods supported by the payment device; determining a first payment method from the one or more payment methods supported by the payment device based on the first payment request, specifically including: determining the first payment method from the one or more preferential payment methods supported by the payment device based on the first payment request.

[0018] In this way, in the case that the electronic device determines that the payment device has a preferential payment service, the electronic device can obtain the preferential payment method of the payment device and select a final payment method from the preferential payment methods supported by the payment device, thereby saving the user's expenses.

[0019] In a possible implementation, the one or more preferential payment methods supported by the payment device include a member card payment; and the first payment method is determined from the one or more payment methods supported by the payment device based on the first payment request, specifically including: determining the first payment method to be the member card payment based on the first payment request.

[0020] In this way, when the electronic device has a member card corresponding to the payment device, the member card payment can be preferentially used.

[0021] In a possible implementation, the first payment method is determined from the one or more payment methods supported by the payment device based on the first payment request, specifically including: obtaining first preferential information based on the identification of the one or more preferential payment methods supported by the payment device, the first preferential information including preferential activities corresponding to the one or more preferential payment methods supported by the payment device; and determining the first payment method from the one or more preferential payment methods based on the first preferential information.

[0022] In this way, the preferential activities of the preferential payment methods supported by the payment device can be obtained, and the payment method to be finally used can be determined based on the preferential activities of each preferential payment method.

[0023] In one possible implementation, the preferential payment methods supported by one or more payment devices do not include membership card payments.

[0024] In this way, when it is determined that membership card payments are not supported, electronic devices can obtain specific promotional offers for other payment methods and then select the final payment method from among them.

[0025] In one possible implementation, determining a first payment method from among one or more preferential payment methods supported by one or more payment devices based on first preferential information specifically includes: determining the discount amount of each preferential payment method supported by one or more payment devices based on the first preferential information; 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.

[0026] This allows users to easily choose the appropriate payment method based on the initial discount information.

[0027] In one possible implementation, a first payment method is determined from among the preferential payment methods supported by one or more payment devices based on the first preferential information. Specifically, this includes: determining the discount amount of each preferential payment method among the preferential payment methods supported by one or more payment devices based on the first preferential information; and determining the first payment method based on the discount amount of each preferential payment method among the preferential payment methods supported by one or more payment devices, wherein the first payment method is the payment method with the largest discount amount among the preferential payment methods supported by one or more payment devices.

[0028] In this way, electronic devices can determine the payment method with the greatest discount based on the first discount information.

[0029] In one possible implementation, after determining that the type of the NFC service of the receiving device is the second sub-service in codeless payment based on the device feature information of the receiving device, the method further includes: after entering the radio frequency field of the receiving device, receiving a first inquiry request sent by the receiving device, the first inquiry request being used to request the identification of a preferential payment method with a promotional activity; in response to the first inquiry request, sending a second preferential response to the receiving device, the second preferential response being used to indicate that there is no preferential payment method.

[0030] In this way, if the payment device offers discounted payment services, it can inquire with the electronic device whether the electronic device also offers discounted payment options. If the electronic device does not offer discounted payment options, it does not need to obtain further discount information.

[0031] In one possible implementation, determining a first payment method from one or more payment methods supported by a payment device based on a first payment request specifically includes: displaying one or more payment options, the one or more payment options including a second option corresponding to the first payment method, the second option including an identifier of the first payment method; receiving and responding to the user's operation on the second option, and determining the first payment method.

[0032] In this way, users can choose a suitable payment method, and the electronic device can determine the final payment method based on the user's choice.

[0033] In one possible implementation, determining a first payment method from among the payment methods supported by one or more payment devices based on a first payment request specifically includes: determining the first payment method from among the payment methods supported by one or more payment devices based on a preset payment method priority of the electronic device, wherein the first payment method is the payment method with the highest priority among the payment methods supported by one or more payment devices.

[0034] In this way, if no preferential payment method is available on the electronic device, the electronic device can choose the payment method with the highest priority as the final payment method.

[0035] 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 is used to indicate a first payment account.

[0036] In this way, electronic devices can send payment credentials to the server through the payment device. The payment credentials are used to indicate the payment account so that the server can complete the deduction.

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

[0038] In this way, the receiving device can determine the payment method used by the electronic device based on the first payment credential.

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

[0040] In this way, the receiving device can determine the payment method used by the electronic device based on the first payment response.

[0041] 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 first discount information; sending a second payment response to the 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.

[0042] In this way, electronic devices can interact directly with the server based on the communication connection between them to complete the payment.

[0043] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a third payment response to the server. The third payment response includes a first payment credential, which is used to indicate a first payment account.

[0044] In this way, electronic devices can send payment vouchers and other information to the server based on communication with the server, and the server can also obtain information such as the receiving account and the amount due from the receiving device. That is, the server can complete the payment through interaction with electronic devices and receiving devices.

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

[0046] In this way, after a successful payment, the electronic device can confirm the payment success based on the notification sent by the server.

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

[0048] In this way, after a successful payment, the electronic device can confirm the payment success based on the notification sent by the server.

[0049] Secondly, this application provides a payment method applied to an electronic device. The method includes: receiving a first merchant identifier sent by a receiving device, the first merchant identifier indicating the merchant to which the receiving device belongs; sending a first response to the receiving device, the first response indicating that the electronic device has successfully received the first merchant identifier; determining, based on the first merchant identifier, identifiers of one or more payment applications supported by the electronic device; receiving a first selection command sent by the receiving device; sending a first selection response to the receiving device based on the first merchant identifier, the first selection response including identifiers of one or more payment applications supported by the electronic device; receiving a second selection command sent by the receiving device, the second selection command including identifiers of a first payment application; sending a second selection response to the receiving device, the second selection response indicating that the first payment application has been successfully selected; and completing the payment through the first payment application.

[0050] In this way, users can complete the payment simply by touching the payment device, simplifying the payment process and improving the user experience. Furthermore, the electronic device can determine the identifiers of one or more payment applications sent to the payment device based on the first merchant's identifier, allowing the first merchant's payment device to select the appropriate payment application to complete the payment.

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

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

[0053] In one possible implementation, the first selection response further includes a first priority order, which is a priority order of one or more payment applications supported by the electronic device.

[0054] This makes it easier for the payment device to determine the first payment application to be used based on the first priority ranking.

[0055] In one possible implementation, sending a first selection response to the payment device based on the first merchant identifier specifically includes: determining a first priority order based on the first merchant identifier; and sending the first selection response to the payment device.

[0056] In this way, the priority order of one or more payment applications supported by the electronic device can be determined based on the first merchant identifier (i.e., the first priority order), which makes it easier for the electronic device to adjust the priority of each payment application based on different merchants, so as to use a more suitable payment application.

[0057] In one possible implementation, determining the first priority order based on the first merchant identifier specifically includes: determining that the first electronic device has a membership card of the first merchant based on the first merchant identifier; and setting the payment application with the highest priority in the first priority order as the membership card payment of the first merchant.

[0058] In this way, when a membership card is available, the priority of membership card payment can be set to the highest priority, making it easier for the payment device to select membership card payment.

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

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

[0061] In one possible implementation, before receiving the first selection command sent by 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 device feature information sent by the receiving device, specifically including: receiving a notification frame sent by the receiving device, the notification frame carrying the device feature information of the receiving device; the method further includes: determining that the type of NFC service of the receiving device is codeless payment based on the device feature information of the receiving device; sending a first response to the receiving device, specifically including: sending a notification ACK frame to the receiving device, the notification ACK frame indicating that the notification frame was successfully received; the method further includes: receiving a parameter negotiation command sent by the receiving device; in response to the parameter negotiation command, sending a parameter negotiation response to the receiving device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between the application layer of the receiving device and the electronic device.

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

[0063] In one possible implementation, the type of the NFC service of the receiving device is determined to be codeless payment based on the device feature information of the receiving device. Specifically, this includes: determining the type of the NFC service of the receiving device as the first sub-service of codeless payment based on the device feature information, where the first sub-service is codeless payment service without preferential payment methods.

[0064] In this way, the type of NFC service of the receiving device can be determined based on the device's characteristic information as the first sub-service in codeless payment, which is a codeless payment service without preferential payment methods. In this case, the first selection command can omit preferential information.

[0065] In one possible implementation, the type of NFC service of the receiving device is determined to be codeless payment based on the device feature information of the receiving device. Specifically, this includes: determining the type of NFC service of the receiving device as codeless payment based on the device feature information as a second sub-service, where the second sub-service is a codeless payment service with preferential payment methods.

[0066] In this way, based on the device characteristic information of the receiving device, the type of NFC service of the receiving device can be determined to be the second sub-service in codeless payment, which is a codeless payment service with preferential payment methods. In this case, the first selection command can carry preferential information.

[0067] In one possible implementation, the first selection response further includes first offer information, which indicates promotional activities of one or more payment applications supported by the electronic device.

[0068] In this way, the first offer information can be sent to the payment device, so that the payment device can determine the most favorable payment application based on the first offer information.

[0069] Thirdly, this application provides a payment method applied to a payment receiving device. The method includes: sending a first merchant identifier to an electronic device, the first merchant identifier indicating the merchant to which the payment receiving device belongs; receiving a first response from the electronic device, the first response indicating that the electronic device has successfully received the first merchant identifier; sending a first selection command to the electronic device, the first selection command selecting a payment service; receiving a first selection response from the electronic device, the first selection response including identifiers of one or more payment applications supported by the electronic device; determining one or more payment applications supported by both the electronic device and the payment receiving device based on the one or more payment applications supported by the electronic device and the one or more payment applications supported by the payment receiving device; determining a first payment application from the one or more payment applications supported by both the electronic device and the payment receiving device; sending a second selection command to the electronic device, the second selection command including the identifier of the first payment application; receiving a second selection response from the electronic device, the second selection response indicating that the first payment application has been successfully selected; and completing the payment through the first payment application.

[0070] In this way, users can complete the payment simply by touching the payment device, simplifying the payment process and improving the user experience. Moreover, the payment device can determine the first payment application to be used based on the identifiers of one or more payment applications sent by the electronic device, and notify the electronic device to use the first payment application to complete the payment.

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

[0072] In this way, the receiving device can indicate the first merchant's identifier through the device organization identifier in the device feature information.

[0073] In one possible implementation, the first selection response further includes a first priority order, which is a priority order of one or more payment applications supported by the electronic device.

[0074] In this way, the payment device can determine the first payment application to be used based on the first priority ranking.

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

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

[0077] In one possible implementation, before receiving the first selection command sent by the receiving device, the method further includes: sending a probe frame to the electronic device, the probe frame indicating that the receiving device supports a specified NFC protocol; receiving a probe ACK frame sent by the electronic device, the probe ACK frame indicating that the electronic device supports the specified NFC protocol; sending device characteristic information to the electronic device, specifically including: sending a notification frame to the electronic device, the notification frame carrying the device characteristic information of the receiving device; receiving a first response sent by the electronic device, specifically including: receiving a notification ACK frame sent by the electronic device, the notification ACK frame indicating that the notification frame was successfully received; the method further includes: sending a parameter negotiation command to the electronic device; receiving a parameter negotiation response sent by the electronic device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between the application layer of the receiving device and the electronic device.

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

[0079] In one possible implementation, the first selection response further includes first offer information, which indicates promotional activities of one or more payment applications supported by the electronic device.

[0080] In this way, the payment device can determine the most favorable payment application based on the initial discount information.

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

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

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

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

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

[0086] Figures 1A-1E are schematic diagrams of an interface for a payment method provided in an embodiment of this application;

[0087] Figure 2 is a schematic diagram of the working principle of NFC provided in an embodiment of this application;

[0088] Figure 3A is a schematic diagram of the system architecture of a payment system provided in an embodiment of this application;

[0089] Figure 3B is a schematic diagram of the communication interaction between an electronic device and a payment cloud server provided in an embodiment of this application;

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

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

[0092] Figure 3E is a schematic diagram of the positional relationship between an electronic device and a payment device based on NFC technology, according to an embodiment of this application.

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

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

[0095] Figures 5A and 5B are schematic diagrams of the interfaces of a set of electronic devices performing payment methods according to embodiments of this application;

[0096] Figures 6A-6D are schematic diagrams of the interface for another set of electronic devices performing payment methods according to embodiments of this application;

[0097] Figures 7A and 7B are schematic diagrams of the interface for another set of electronic devices performing payment methods according to embodiments of this application;

[0098] Figures 8A-8C are schematic diagrams of the interface for selecting a payment method and completing payment on a set of electronic devices provided in the embodiments of this application;

[0099] Figure 9 is a flowchart illustrating a payment method provided in an embodiment of this application;

[0100] Figure 10 is a flowchart illustrating a payment method provided in an embodiment of this application;

[0101] Figure 11 is a flowchart illustrating a payment method provided in an embodiment of this application;

[0102] Figure 12 is a schematic diagram of a payment account deduction process provided in an embodiment of this application;

[0103] Figure 13 is a schematic diagram of a payment process after determining the payment method according to an embodiment of this application;

[0104] Figure 14 is a schematic diagram of the process of an electronic device determining the most favorable payment method and completing the payment using the most favorable payment method according to an embodiment of this application;

[0105] Figure 15 is a schematic diagram of another process for completing payment on an electronic device based on a membership card and other payment methods, provided by an embodiment of this application.

[0106] Figure 16 is a schematic diagram of a payment collection device selecting a payment method and completing the payment through interaction with an electronic device, according to an embodiment of this application.

[0107] Figure 17 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0108] Figures 18 to 21 are schematic diagrams of a set of communication devices provided in the embodiments of this application;

[0109] Figure 22 is a flowchart illustrating a payment method provided in an embodiment of this application;

[0110] Figure 23 is a flowchart illustrating a payment method provided in an embodiment of this application;

[0111] Figure 24 is a flowchart illustrating a payment method provided in an embodiment of this application. Detailed Implementation

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

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

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

[0115] Figures 1A-1E show schematic diagrams of the interface for one payment method.

[0116] As shown in Figure 1A, the phone is in a screen-off state. Users can use fingerprint unlocking or other methods to switch the phone's display from a screen-off state to a screen-on state, displaying desktop 1000 as shown in Figure 1B.

[0117] As shown in Figure 1B, the desktop 1000 displays a page with application icons, including multiple application icons (e.g., payment application icon 1001, settings application icon, browser application icon, etc.). Below the page with application icons, a page indicator 1002 is also displayed to indicate the total number of pages on the desktop and the positional relationship between the currently displayed page and other pages. For example, the desktop 1000 may include three pages, and the black dot in the page indicator, located at the first position from the left, indicates that the currently displayed page is the first page from the left among the three pages. Optionally, a status bar is also displayed above the page with application icons, which may include information such as signal strength indicator, battery level, and time. Further optionally, a tray (dock) area 1003 may be present below the page indicator, which may include one or more tray icons (e.g., dialer application icon, messaging application icon, contacts application icon, camera application icon, etc.). The one or more tray icons in the dock area may remain displayed when switching pages.

[0118] The mobile phone can receive and respond to the user's click on the payment application icon 1001, and display the payment application interface 1010 as shown in Figure 1C.

[0119] As shown in Figure 1C, the payment application interface 1010 may include one or more controls, such as a scan control, a pay control 1011, a receive control, a wallet control, etc. Each control can be used to trigger the mobile phone to jump to the interface corresponding to the control, and realize the corresponding functions of scanning, paying, receiving money, etc.

[0120] The mobile phone can receive and respond to the user's click operation on the payment control 1011, and display the payment interface 1020 as shown in Figure 1D.

[0121] As shown in Figure 1D, the payment interface 1020 may include a payment QR code 1021, which can be used for payment. The payee can deduct the payment from the account corresponding to the payment QR code 1021 by scanning the payment QR code 1021.

[0122] After successful payment, the mobile phone can display a payment success interface 1030 as shown in Figure 1E. The payment success interface 1030 can be used to notify the user that the payment has been completed.

[0123] As shown in Figure 1E, the payment success interface 1030 can display a payment success message, which is used to notify the user that the payment has been completed. The payment success message may include information such as the payee, the amount due, the amount actually paid, and the discount amount.

[0124] In this way, payment can be made by opening the payment QR code in the payment application.

[0125] However, the above payment methods are cumbersome and inefficient.

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

[0127] Figure 2 shows a schematic diagram of the working principle of NFC provided in an embodiment of this application.

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

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

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

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

[0132] Figure 3A shows a schematic diagram of the system architecture of a payment system 10 provided in an embodiment of this application.

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

[0134] When electronic device 100 enters the radio frequency field of payment receiving device 200 (e.g., by touching payment receiving device 200), electronic device 100 can communicate with payment receiving device 200 based on NFC technology to determine one or more payment methods supported by payment receiving device 200, and optionally, also determine the payment amount. Electronic device 100 can also obtain discount information from payment cloud server 300, which can be used to determine the discount amount for different payment methods, thereby determining the final payment method to be adopted. Electronic device 100 can determine the final payment method based on discount information, user selection, or communication with payment receiving device 200, and send the payment voucher corresponding to the payment method to payment receiving device 200. The payment voucher can be used to indicate the payment account.

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

[0136] The payment cloud server 300 can be a server cluster, which may include one or more servers (or server modules). The communication interaction between each server in the payment cloud server 300 and the electronic device 100 can be referred to the relevant description in the embodiment shown in Figure 3B below, and will not be detailed here. The payment cloud server 300 can receive and respond to the discount information acquisition request sent by the electronic device 100, and send discount information to the electronic device 100. The payment cloud server 300 can also deduct funds from the payment account indicated by the payment voucher based on the payable amount, payment voucher, and payment account sent by the payment receiving device 200, and transfer the payable amount to the payment receiving account. In some embodiments, before deducting funds from the payment account, the payment cloud server 300 can also initiate payment verification to the electronic device 100 based on the communication connection with the electronic device 100, and perform the deduction operation only after successful verification.

[0137] For example, the payment device 200 can be a point of sale (POS) machine as shown in Figure 3A, and the electronic device 100 can be a smartphone as shown in Figure 3A. In this embodiment of the application, the payment device 200 and the electronic device 100 can also be other types of electronic devices, which are not limited here.

[0138] It is understood that the embodiment shown in Figure 3A above is only an example. In the embodiments of this application, the payment system 10 may also include more, fewer or different electronic devices than the above embodiments, such as merchant back-end servers. The merchant back-end server may undertake some of the functions of the payment collection device 200 in the above embodiments, and this application does not limit it here.

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

[0140] For example, Figure 3B shows a schematic diagram of the communication interaction between an electronic device 100 and a payment cloud server 300 provided in an embodiment of this application.

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

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

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

[0144] It is understood that the embodiment shown in Figure 3B is merely an illustrative example. The electronic device 100 can communicate with the server (or server module) corresponding to the payment application installed on it. In this embodiment, the electronic device 100 may also have more, fewer, or different payment applications than those in the above embodiments. The payment cloud server 300 may also include more, fewer, or different servers than those in the above embodiments. This application does not impose any limitations on this.

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

[0146] Figure 3C shows a schematic diagram of the device configuration of an electronic device 100 provided in an embodiment of this application.

[0147] As shown in Figure 3C, the electronic device 100 may include a front and a back. The front of the electronic device 100 may have a display screen 401. Optionally, the front of the electronic device 100 may also have one or more of the following: a front-facing camera 402, an earpiece 403, etc. The back of the electronic device 100 may include an NFC area 404. Optionally, the back of the electronic device 100 may also include one or more of the following: a rear-facing camera 405, a flashlight 406, etc. When the electronic device 100 touches the payment receiving device 200, the NFC area 404 is used to make contact with the payment receiving device 200 to facilitate NFC communication between the electronic device 100 and the payment receiving device 200.

[0148] It is understood that the embodiment shown in Figure 3C is only an example. In this application embodiment, the NFC area of ​​the electronic device 100 can also be set in other locations of the electronic device 100, and this application does not limit it. In addition, the electronic device 100 can be a mobile phone, a tablet computer, a wearable device, or other electronic devices, and this application does not limit it.

[0149] Figure 3D shows a schematic diagram of the device configuration of a payment collection device 200 provided in an embodiment of this application.

[0150] As shown in Figure 3D, the payment receiving device 200 may include a card swiping area 411 and a display screen 412. Optionally, the payment receiving device 200 may also include a button 413. When the electronic device 100 touches or approaches the card swiping area 411 of the payment receiving device 200, NFC communication between the electronic device 100 and the payment receiving device 200 is facilitated. The display screen 412 can be used to display the amount due, and can also be used to display payment success notifications, etc. In some embodiments, the areas where the card swiping area 411 and the display screen 412 are located may partially or completely overlap. The button 413 can be used for user interaction, such as outputting the amount due to the payment receiving device 200. In some embodiments, the payment receiving device 200 may also not have physical buttons, but instead achieve interaction between the payment receiving device 200 and the user through touch screen operation of the display screen 412.

[0151] It is understood that the embodiment shown in Figure 3D above is only an example. In the embodiments of this application, the payment device 200 adopts a different device form than the above embodiment, including more, fewer or different devices than the embodiment shown in Figure 3D above. This application does not limit it here.

[0152] Figure 3E shows a schematic diagram of the positional relationship between an electronic device 100 and a payment device 200 based on NFC technology, according to an embodiment of this application.

[0153] As shown in Figure 3E, the user can touch the NFC area 404 on the back of the electronic device 100 to the card swiping area 411 of the payment device 200 to complete the contact between the electronic device 100 and the payment device 200. In this way, the electronic device 100 and the payment device 200 can communicate based on NFC technology to complete the payment.

[0154] It is understood that the embodiment shown in Figure 3E is merely an illustrative description of the positional relationship between the electronic device 100 and the payment device 200 when they are touched. In this application embodiment, if the position of the NFC area 404 or the card swiping area 411 is different from that in the above embodiment, the electronic device 100 and the payment device 200 may also communicate based on NFC technology using a different positional relationship than that in the above embodiment. This application does not limit this.

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

[0156] Figure 4A shows a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0170] Figure 4B shows a schematic diagram of the layered architecture of an NFC protocol stack provided in an embodiment of this application.

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

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

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

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

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

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

[0177] In this embodiment of the application, the NFC protocol stack shown in Figure 4B above can be referred to as the first protocol stack.

[0178] The following describes the interface of the electronic device 100 that performs the payment method according to the embodiments of this application.

[0179] Figures 5A and 5B are schematic diagrams of the interface of a set of electronic devices 100 performing a payment method according to an embodiment of this application.

[0180] In some application scenarios, electronic device 100 can be in a screen-off state. When electronic device 100 touches payment device 200, electronic device 100 can communicate with payment device 200 based on NFC technology to complete the payment. After the payment is completed, electronic device 100 can display a payment success message to notify the user that the payment was successful.

[0181] This simplifies the payment process and improves payment efficiency.

[0182] For example, as shown in Figure 5A, the electronic device 100 is in a screen-off state. When the user touches the electronic device 100 to the payment device 200, the electronic device 100 can display a payment success interface 500 as shown in Figure 5B.

[0183] As shown in Figure 5B, the payment success interface 500 may include a payment success notification 501, which can be used to notify the user that the payment has been successful. The payment success notification 501 may include one or more of the following: payee 502, amount due 503, actual amount paid 504, discount amount 505, payment method 506, completion control 507, etc. Among them, payee 502 can be used to notify the user of the payee's account (e.g., the payee's account number), making it easier for the user to verify the payee's correctness. Amount due 503 is used to notify the user of the amount due. Actual amount paid 504 is used to notify the user of the amount actually paid. Discount amount 505 is used to notify the user of the discount amount; the sum of the discount amount and the actual amount paid is the amount due. Optionally, discount amount 505 can also indicate the user of specific promotional activities, such as "XX Bank offers a discount of 5 yuan off for purchases over 50 yuan." Payment method 506 can be used to indicate the user's current payment method, such as "AA Bank savings card," etc. In some embodiments, the completion control 507 is used to trigger the electronic device 100 to stop displaying the payment success message 501.

[0184] It is understood that the embodiments shown in Figures 5A and 5B are merely illustrative examples. In the screen-off state, the electronic device 100 can complete the payment by touching the payment device 200. In other embodiments, the payment success notification may include more, less, or different content than the above embodiments, and the payment success interface may also be a different interface from the above embodiments. This application does not limit this.

[0185] In other application scenarios, the electronic device 100 is in a screen-on state and displays a desktop or any other application interface. When the user touches the electronic device 100 to the payment receiving device 200, the electronic device 100 can also display the payment success interface 500 shown in Figure 5B above. This application does not limit the interface displayed by the electronic device 100 before touching the payment receiving device 200.

[0186] It should be noted that in some embodiments, when the electronic device 100 touches the payment receiving device 200, it can complete the payment and display the payment success interface 500 shown in Figure 5B, provided that the electronic device 100 has enabled the password-free payment function and the payment amount is less than or equal to the password-free payment amount. This simplifies the payment process, improves payment efficiency, and reduces losses due to accidental or fraudulent transactions.

[0187] In some application scenarios, electronic device 100 can be in a screen-off state or a screen-on state. When electronic device 100 touches payment device 200, electronic device 100 can display a payment verification prompt, which prompts the user to verify the payment. After confirming that the user has completed the payment verification, electronic device 100 can display a payment success prompt, which prompts the user that the payment was successful.

[0188] This not only simplifies the payment process and improves payment efficiency, but also enhances payment security and prevents fraudulent and accidental transactions.

[0189] For example, when a user touches the electronic device 100 to the payment device 200, the electronic device 100 may display a payment verification interface 600 as shown in Figure 6A.

[0190] As shown in Figure 6A, the payment verification interface 600 may include a payment verification prompt 601, which can be used to prompt the user to perform payment verification. The payment verification prompt 601 may include a payee 602, amount due 603, amount actually paid 604, payment method 605, and fingerprint verification prompt 606. The descriptions of the payee 602, amount due 603, amount actually paid 604, and payment method 605 can be referred to the descriptions in the embodiment shown in Figure 5B above, and will not be repeated here. Furthermore, before performing payment verification, the user can also check whether the payee 602, amount due 603, amount actually paid 604, and payment method 605 displayed in the payment verification prompt 601 are correct. The fingerprint verification prompt 606 can be used to prompt the user to complete payment verification through fingerprint verification. Optionally, the payment verification prompt 601 may also include one or more of the following: a payment method switching control 607 and a verification method switching control 608. The payment method switching control 607 can be used to trigger the electronic device 100 to switch the current payment method. The verification method switching control 608 can be used to trigger the electronic device 100 to switch the current payment verification method.

[0191] In some embodiments, after detecting that the user has completed fingerprint verification in the fingerprint recognition area, the electronic device 100 may display a payment success prompt, such as displaying the payment success interface 500 shown in Figure 5B above.

[0192] In other embodiments, the electronic device 100 may receive and respond to a user's click operation on the verification method switching control 608, as shown in FIG6B, displaying the verification method switching window 610 on the payment verification interface 600.

[0193] As shown in Figure 6B, the verification method switching window 610 may include one or more verification options, such as fingerprint verification option 611, payment password verification option 612, and face verification option 613. Each option may include a selection identifier, which indicates whether the option is selected. For example, fingerprint verification option 611 may include selection identifier 611a, payment password verification option 612 may include selection identifier 612a, and face verification option 613 may include selection identifier 613a. The selection identifier may include two states: a selected state and an unselected state. In some embodiments, the electronic device 100 may use different display colors to indicate the two states of the selection identifier. For example, selection identifier 611a may be filled with black, while other selection identifiers may not be filled, indicating that fingerprint verification option 611 is selected and other options are unselected. It is understood that in this embodiment, a different selection identifier than the one described above may also be used to indicate whether an option is selected, and this application does not limit this. In addition, the verification method switching window 610 may also include a completion control 614. The completion control 614 can be used to trigger the electronic device 100 to switch the verification method to the verification method corresponding to the currently selected verification option.

[0194] The electronic device 100 can receive and respond to the user's click operation on the payment password verification option 612, as shown in FIG6C, by switching the state of the selection mark 612a in the payment password verification option 612 to the selected state and switching the state of the selection mark 611a in the fingerprint verification option 611 to the unselected state.

[0195] Electronic device 100 can receive and respond to a user's click on the completion control 614, displaying the payment verification interface 620 as shown in FIG6D. In other embodiments, electronic device 100 may also display the payment verification interface 620 as shown in FIG6D when the receiving device 200 is touched.

[0196] As shown in Figure 6D, the payment verification interface 620 may include a payment verification prompt 621, which can be used to prompt the user to perform payment verification. The payment verification prompt 621 may include the payee 622, the amount due 623, the amount actually paid 624, the payment method 625, and a payment password verification prompt 626. The descriptions of the payee 622, the amount due 623, the amount actually paid 624, and the payment method 625 can be found in the embodiments shown in Figure 6A above, and will not be repeated here. The payment password verification prompt 626 can be used to prompt the user to complete the payment verification by means of a payment password. Optionally, the payment verification prompt 621 may also include one or more of the following: a payment method switching control 627 and a verification method switching control 628. The specific functional descriptions of the payment method switching control 627 and the verification method switching control 628 can be found in the embodiments shown in Figure 6A above, and will not be repeated here. The payment verification interface 620 may also display a keyboard 629, which can be used to input the payment password.

[0197] In some embodiments, after detecting that the user has entered the correct payment password, the electronic device 100 may display a payment success message, such as the payment success interface 500 shown in Figure 5B above.

[0198] It is understood that the embodiments shown in Figures 6A-6D above are merely illustrative examples illustrating how payment verification can be performed using methods such as fingerprints or payment passwords to improve payment security. In other embodiments, the electronic device 100 may employ more, fewer, or different payment verification methods than those described in the above embodiments, and this application does not impose any limitations on these methods.

[0199] It should be noted that in some embodiments, when the electronic device 100 touches the payment receiving device 200, if the electronic device 100 has not enabled the password-free payment function, the electronic device 100 can use the payment method shown in the embodiments of Figure 6A or Figure 6D above, display a payment verification prompt, and complete the payment after confirming that the user has passed the verification. Furthermore, the payment verification method indicated by the payment verification prompt displayed by the electronic device 100 can be the default payment verification method with the highest priority. This payment verification method can be the fingerprint verification method shown in the embodiment of Figure 6A above, the payment password verification method shown in the embodiment of Figure 6D above, or other methods such as facial recognition verification. This application does not limit this to any particular method.

[0200] In some application scenarios, electronic device 100 can be in a screen-off or screen-on state. When electronic device 100 touches the payment device 200, it can display a payment interface for entering the payment amount. After the user enters the payment amount, electronic device 100 completes the payment and displays a payment completion notification to inform the user that the payment has been completed.

[0201] This simplifies the payment process, improves payment efficiency, and allows users to input the payment amount, preventing fraudulent and accidental transactions and enhancing payment security.

[0202] For example, when a user touches the electronic device 100 to the payment device 200, the electronic device 100 may display a payment interface 700 as shown in Figure 7A.

[0203] As shown in Figure 7A, the payment interface 700 may include an amount input box 701, a keyboard 702, and a payment confirmation control 703. Optionally, the amount input box 701 may also display text 704, which can be used to prompt the user to enter the payment amount, such as "Please enter the amount." The keyboard 702 can be used to receive and respond to the user's click operation on one or more number keys on the keyboard 702, allowing the user to enter the payment amount in the amount input box 701. The payment confirmation control 703 can be used to trigger the electronic device 100 to pay the amount entered by the user in the amount input box 701.

[0204] The electronic device 100 can receive and respond to the user's input of an amount in the amount input box 701, as shown in Figure 7B, and display the amount entered by the user in the amount input box 701, such as "50". At this time, the text 704 may no longer be displayed in the amount input box 701.

[0205] In some embodiments, after the user enters the amount, the electronic device 100 can receive and respond to the user's click operation on the payment confirmation control 703, and the electronic device 100 can complete the payment and display the payment success interface 500 shown in FIG5B above, prompting the user that the payment was successful.

[0206] In other embodiments, after the user enters the amount, the electronic device 100 can also receive and respond to the user's click operation on the payment confirmation control 703. The electronic device 100 can display a payment verification prompt, such as the payment verification prompt 601 shown in FIG6A above or the payment verification prompt 621 shown in FIG6D above. After confirming that the user has completed the payment verification, the electronic device 100 can complete the payment.

[0207] It is understood that the embodiments shown in Figures 7A and 7B are only examples. In the embodiments of this application, when the electronic device 100 touches the payment device 200, the electronic device 100 may also display more, less, or different content than the above embodiments. This application does not limit this.

[0208] In some application scenarios, the electronic device 100 can be in a screen-off state or a screen-on state. When the electronic device 100 touches the payment device 200, the electronic device 100 can display one or more payment options (including payment option 1), each payment option corresponding to a payment method. Each payment option may also include the payment amount corresponding to that payment option. The electronic device 100 can receive and respond to the user's selection of payment option 1, complete the payment based on payment method 1 corresponding to payment option 1, and display a payment success prompt to notify the user that the payment has been completed.

[0209] This not only simplifies the payment process and improves payment efficiency, but also displays the discount amounts for different payment methods to users, allowing them to choose the appropriate payment method themselves.

[0210] For example, when a user touches the electronic device 100 to the payment device 200, the electronic device 100 can obtain one or more payment methods supported by the payment device 200, and obtain the corresponding discount amount for the one or more payment methods from the payment cloud server 300. Then, the electronic device 100 can display a payment method selection interface 800 as shown in Figure 8A, which includes one or more payment options sorted by discount amount.

[0211] As shown in Figure 8A, the payment method selection interface 800 can include one or more payment options. These options can be displayed in the interface 800 according to the amount of the discount, for example, from top to bottom, options include AA Bank Card 801, Payment Application A 802, and Payment Application B 803. This allows users to easily determine the most favorable payment option based on the order. Each payment option can correspond to one payment method; for example, AA Bank Card option 801 corresponds to payment via AA Bank Card, Payment Application A option 802 corresponds to payment via Payment Application A, and Payment Application B option 803 corresponds to payment via Payment Application B. Each payment option can include an amount prompt, which can be used to indicate the actual payment amount and / or discount amount corresponding to that payment option to the user. For example, option 801 (AA bank card) may include an amount prompt 801a, which indicates that the actual payment amount when using AA bank card is 45 yuan, with a discount of 5 yuan. Option 802 (payment application A) may include an amount prompt 802a, which indicates that the actual payment amount when using payment application A is 48 yuan, with a discount of 2 yuan. Option 803 (payment application B) may include an amount prompt 803a, which indicates that the actual payment amount when using payment application B is 49 yuan, with a discount of 1 yuan. Furthermore, each payment option may include a selection identifier. For example, option 801 (AA bank card) includes a selection identifier 801b, option 802 (payment application A) includes a selection identifier 802b, and option 803 (payment application B) includes a selection identifier 803b. Each selection identifier includes a selected state and an unselected state, indicating whether the corresponding payment option is selected. In the embodiment shown in Figure 8A, selection identifier 801b is in the selected state, and the other selection identifiers are in the unselected state. The specific details of the selected identifier can be found in the relevant description in the embodiment shown in Figure 6B above, and will not be repeated here. The payment method selection interface 800 may also include a payment confirmation control 804, which can be used to trigger the electronic device 100 to complete the payment based on the currently selected payment option.

[0212] In some embodiments, the electronic device 100 can receive and respond to a user's click on the payment confirmation control 804, complete the payment through the payment application A, and display a payment success prompt, such as the payment success prompt 501 shown in Figure 5B, which is used to inform the user that the payment has been completed. Optionally, before the electronic device 100 completes the payment, it can also display a payment verification prompt (e.g., the payment verification prompt in the embodiments shown in Figures 6A or 6D), and complete the payment after confirming successful payment verification.

[0213] In other embodiments, when a user touches the electronic device 100 to the payment device 200, the electronic device 100 can obtain one or more payment methods supported by the payment device 200 and retrieve the corresponding discount amount for the one or more payment methods from the payment cloud server 300. Then, the electronic device 100 can display a payment method selection interface 810 as shown in Figure 8B, which includes one or more payment options displayed in the default payment order.

[0214] As shown in Figure 8B, the payment method selection interface 810 may include one or more payment options. These options can be displayed in the payment method selection interface 810 based on a default payment order, such as payment application B option 811, AA bank card option 812, payment application A option 813, etc., displayed from top to bottom. Each payment option may include a selection indicator, where the selection indicator 811b of payment application B option 811 is selected, and the selection indicators of other payment options (such as selection indicators 812b, selection indicators 813b, etc.) are unselected. Each payment option may also include an amount prompt, such as amount prompt 811a, amount prompt 812a, and amount prompt 813a, etc. The amount prompt is used to indicate the payment amount corresponding to the payment method to the user. The payment method selection interface 810 may also include a payment confirmation control 814. The specific content and function description of each payment option and payment confirmation control 814 in the payment method selection interface 810 can be found in the relevant description in the embodiment shown in Figure 8A above, and will not be repeated here.

[0215] The electronic device 100 can receive and respond to the user's click operation on option A of payment application 813, as shown in FIG8C, changing the selection mark 813b of option A of payment application 813 to the selected state and changing the selection mark 811b of option B of payment application 811 to the unselected state.

[0216] Electronic device 100 can receive and respond to a user's click operation on the payment confirmation control 814, complete the payment through payment application A, and display a payment success prompt, such as the payment success prompt 501 shown in Figure 5B. The payment success prompt is used to inform the user that the payment has been completed. Optionally, before electronic device 100 completes the payment, it can also display a payment verification prompt (such as the payment verification prompt in the embodiments shown in Figure 6A or Figure 6D), and complete the payment after confirming successful payment verification.

[0217] It is understood that the embodiments shown in Figures 8A-8C above are only two examples. In the embodiments of this application, the electronic device 100 may also display one or more payment options in a different arrangement than the above embodiments, and the electronic device 100 may also display more, fewer or different payment options than the above embodiments. This application does not limit this.

[0218] The specific process of the payment method provided in the embodiments of this application is described below.

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

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

[0221] S901. Electronic device 100 enters the radio frequency field of receiving device 200.

[0222] S902. The receiving device 200 sends a probe frame to the electronic device 100.

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

[0224] S903. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

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

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

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

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

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

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

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

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

[0233] Table 1

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

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

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

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

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

[0239] S905. Electronic device 100 determines the service type as a general service in code-free payment based on the device feature information of the receiving device 200.

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

[0241] S906. Electronic device 100 sends a Pick ACK frame.

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

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

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

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

[0246] S908. Electronic device 100 determines payment method 1 from one or more payment methods supported by payment request 1.

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

[0248] S909. Electronic device 100 obtains payment credential 1 and payment authorization 1 for payment method 1, wherein payment credential 1 is used to instruct payment account 1 for payment method 1.

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

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

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

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

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

[0254] S911. The receiving device 200 deducts funds from the payment account 1 based on the payment voucher 1 and the payment license 1, and the deducted amount is the amount payable.

[0255] The specific method by which the receiving device 200 deducts funds from the payment account 1 based on the payment voucher 1 and payment license 1 can be referred to the relevant steps in the embodiments shown in Figure 12 or Figure 13 below, which will not be described in detail here.

[0256] It is understood that the embodiment shown in Figure 9 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.

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

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

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

[0260] S1001. Electronic device 100 enters the radio frequency field of receiving device 200.

[0261] S1002. The receiving device 200 sends a probe frame to the electronic device 100.

[0262] S1003. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0263] S1004. 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.

[0264] Since in step S1004, the device feature information is used to indicate that the service type of the receiving device 200 is the 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. In this way, the service type of the receiving device 200 can be indicated by the device service identifier in the device feature information.

[0265] S1005. 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.

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

[0267] S1006. Electronic device 100 sends a Pick ACK frame.

[0268] The specific details of steps S1001 to S1006 can be found in the description of steps S901 to S906 in the embodiment shown in Figure 9 above, and will not be repeated here.

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

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

[0271] In some embodiments, the merchant ID can be used to obtain the payment methods supported by the payment receiving device 200. In other embodiments, the merchant ID can also be used to determine whether a membership card corresponding to the merchant ID exists in the electronic device 100.

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

[0273] Preferential payment methods refer to payment methods with promotional offers, where the actual amount paid under the preferential payment method is less than the amount due.

[0274] In one possible implementation, after determining that the service type of the receiving device 200 is a codeless payment discount service, the electronic device 100 can obtain from the payment cloud server 300 the payment methods with promotional activities among all the payment methods supported by the electronic device 100. In this case, after receiving payment request 2, the electronic device 100 can determine one or more payment methods supported by the receiving device 200 based on payment request 2. Then, based on the payment methods supported by one or more receiving devices 200 and the payment methods with promotional activities among all the payment methods supported by the electronic device 100, the electronic device 100 can determine one or more discounted payment methods supported by both the electronic device 100 and the receiving device 200.

[0275] It should be noted that, in some embodiments, when the payment request 2 includes a merchant ID, the electronic device 100 can obtain one or more payment methods supported by the payment cloud server 300 based on the merchant ID. In other embodiments, when the payment request 2 includes an identifier of one or more payment methods supported by the payment device 200, the electronic device 100 can determine one or more payment methods supported by the payment device 200 based on the payment request 2.

[0276] In another possible implementation, after determining that the service type of the receiving device 200 is a codeless payment preferential service and receiving the payment request 2, the electronic device 100 can obtain one or more preferential payment methods supported by both the electronic device 100 and the receiving device 200 from the payment cloud server 300 based on the payment request 2.

[0277] S1009. Electronic device 100 determines payment method 2 from preferential payment methods supported by one or more electronic devices 100 and payment device 200.

[0278] After determining that one or more preferential payment methods are supported by both the electronic device 100 and the payment receiving device 200, the electronic device 100 can obtain preferential information, which includes the promotional activities of the one or more preferential payment methods, and determine payment method 2 from the one or more preferential payment methods based on the preferential information and the amount payable.

[0279] In one possible implementation, electronic device 100 can determine the discount amount for each preferential payment method based on the discount information and the amount payable, and determine the payment method 2 as the preferential payment method with the largest discount amount.

[0280] In another possible implementation, the electronic device 100 can determine and display the discount amount and / or actual payment amount for each preferential payment method based on the discount information and the amount payable, and determine the payment method selected by the user as payment method 2 based on the user's operation of selecting a payment method.

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

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

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

[0284] Electronic device 100 can determine the actual payment amount 1 corresponding to payment method 2 based on the promotional information and payment method 2. The actual payment amount 1 is the amount that electronic device 100 actually needs to pay when using payment method 2. The actual payment amount 1 is less than or equal to the amount due.

[0285] S1011. Electronic device 100 sends payment response 2, which includes payment voucher 2, actual payment amount 1, and payment authorization 2.

[0286] Electronic device 100 can send payment response 2 to payment device 200 in a single communication or in multiple communications. For details, please refer to the relevant description in step S910 shown in Figure 9 above, which will not be repeated here.

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

[0288] The details of step S1012 can be found in the description of step S911 shown in Figure 9 above, and will not be repeated here.

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

[0290] The payment method provided in this application can not only simplify the payment process and improve payment efficiency, but also obtain preferential information and reduce user expenses.

[0291] In some application scenarios, the device feature information carried in the Pick frame sent by the payment receiving device 200 indicates that the service type of the payment receiving device 200 is codeless payment, but it cannot indicate whether the sub-service type of the payment receiving device 200 is a payment discount service. That is, the payment receiving device 200 cannot confirm whether there is a payment method with a discount promotion among the payment methods it supports. In this case, the payment receiving device 200 can query the electronic device 100 to see if there is a payment method with a discount promotion, and based on the query result, determine whether there is a payment method with a discount promotion among the payment methods supported by both the payment receiving device 200 and the electronic device 100. Based on the determination result, the payment receiving device 200 can determine the subsequent payment process.

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

[0293] As shown in Figure 11, the electronic device 100 may include a payment application set 11 and an NFC service module 12. The specific process of a payment method provided in this embodiment may include the following steps:

[0294] S1101. Electronic device 100 enters the radio frequency field of receiving device 200.

[0295] S1102. The receiving device 200 sends a probe frame to the electronic device 100.

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

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

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

[0299] The specific content of the device feature information can be found in the relevant description of step S904 shown in Figure 9 above, and will not be repeated here.

[0300] In this embodiment, the Pick frame sent by the payment device 200 may carry a device service identifier for indicating codeless payment, such as 0x07 as shown in Table 1 above. This device service identifier can be used to indicate that the service type of the payment device 200 is codeless payment.

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

[0302] In some embodiments, the NFC service module 12 can determine that the service type of the payment device 200 is codeless payment based on the device service identifier of the payment device 200.

[0303] After determining the service type, in the NFC protocol stack shown in Figure 4B 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.

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

[0305] S1106.NFC service module 12 sends a Pick ACK frame.

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

[0307] For details of steps S1101 to S1106, please refer to the relevant descriptions of steps S901 to S906 shown in Figure 9 above.

[0308] S1107. 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 identifier.

[0309] The request for discount capability inquiry can be used to inquire about the discounted payment methods supported by the electronic device 100. In this embodiment, a discounted payment method refers to a payment method with discount capability, that is, a payment method where the actual payment amount is less than the total amount of the goods.

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

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

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

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

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

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

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

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

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

[0319] S1109. Payment device 200 determines whether payment device 200 has a preferential payment method.

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

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

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

[0323] 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 step S1110.

[0324] 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 S1116.

[0325] S1110. The receiving device 200 sends a payment request 3, which includes the amount due.

[0326] If the receiving device 200 does not offer a preferential payment method, it can send a payment request 3 to the NFC service module 12. The payment request 3 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 3 may include the amount due. The amount due refers to the amount that the receiving device 200 should receive.

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

[0328] S1111.NFC service module 12 determines payment method 1 among one or more payment methods supported by the receiving device 200.

[0329] 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 3. 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 S1107 above. The specific determination method can be referred to the relevant description in step S1108 above, and will not be repeated here.

[0330] In one possible implementation, after receiving payment request 3, the NFC service module 12 can determine the highest priority payment method 1 as the final payment method based on the user's default payment method sorting.

[0331] In another possible implementation, after receiving payment request 3, the NFC service module 12 can display one or more payment options for the user to choose a payment method. The NFC service module 12 can receive and respond to the user's selection of a payment method, determining the user-selected payment method 1 as the final payment method. For example, the one or more payment options displayed by the NFC service module 12 can be the payment options shown in the embodiments of Figure 8A or Figure 8B above (e.g., AA bank card option 801, payment application A option 802, etc.).

[0332] 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 S1112 after determining payment method 1 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 payment voucher 1 corresponding to payment method 1 to the payment cloud server 300 through the communication connection with the payment cloud server 300. Payment voucher 1 can be used to indicate the payment account for payment method 1. Moreover, 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.

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

[0334] S1112. NFC service module 12 sends a payment response 3 to the receiving device 200. The payment response 3 includes a payment credential 1, which indicates the payment account 1 of payment method 1.

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

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

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

[0338] 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 1 for payment method 1. In this case, when it is determined that payment method 1 is to be used, the NFC service module 12 may determine the payment credential 1 corresponding to payment method 1 and send the payment credential 1 to the receiving device 200.

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

[0340] S1113. The receiving device 200 deducts funds based on payment account 1, and the deducted amount is the amount payable.

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

[0342] 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 12 or Figure 13 below, and will not be repeated here.

[0343] In some embodiments, after the receiving device 200 receives the amount due from the payment account 1, the receiving device 200 may perform the following step S1114.

[0344] S1114. Payment receiving device 200 sends payment success notification 1.

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

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

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

[0348] In another possible implementation, the receiving device 200 may also send a payment success notification 1 to the NFC service module 12, and the NFC service module 12 shall perform the following steps S1115 to output a payment success prompt 1.

[0349] S1115. Payment application set 11 can output a payment success message 1.

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

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

[0352] For example, payment success message 1 can be payment success message 501 as shown in Figure 5B above.

[0353] S1116. The payment device 200 determines whether the payment device 200 supports membership card payment as a preferential payment method.

[0354] Steps S1116 to S1121 are optional steps.

[0355] 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 S1109 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 S1116 to S1121 to determine the subsequent payment process based on whether the payment receiving device 200 supports membership card payment.

[0356] In another possible implementation, if it is determined that a preferential payment method exists for the payment receiving device 200, 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, after executing step S1109 and determining that a preferential payment method exists for the payment receiving device 200, the payment receiving device 200 and subsequent steps can be executed, without executing steps S1116 to S1121.

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

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

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

[0360] The payment device 200 can determine the amount paid by the member, which can be less than or equal to the amount payable in step S1113 above.

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

[0362] S1118. Payment application set 11 sends a member payment response, which includes member payment credentials used to indicate the member account.

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

[0364] S1119. Payment device 200 deducts funds based on member accounts, with the deduction amount being the amount paid by the member.

[0365] 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 12 or Figure 13 below, which will not be repeated here.

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

[0367] S1120. Payment receiving device 200 sends payment success notification 2.

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

[0369] In some embodiments, the payment success notification 2 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 S1119 above), the payee, the payment time, etc.

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

[0371] S1121. Payment application set 11 can output a payment success message 2.

[0372] The details of step S1121 can be found in the description of step S1115 above, and will not be repeated here.

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

[0374] Payment request 4 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.

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

[0376] In some embodiments, if in step S1107 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 4 may not include the identifier of the preferential payment method supported by the receiving device 200.

[0377] It should be noted that if the receiving device 200 does not execute step S1116 above, the identifier of the preferential payment method in payment request 4 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 after obtaining the discount amount of other preferential payment methods, select the final preferential payment method. If the receiving device 200 executes step S1116 above, the identifier of the preferential payment method in payment request 4 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.

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

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

[0380] For example, Table 2 shows the composition of a type of preferential information provided in an embodiment of this application.

[0381] Table 2

[0382] As shown in Table 2, the discount information may include 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 promotional activity for AA bank card payment is Promotional Activity 1 (e.g., 5 RMB off for purchases over 50 RMB), and the promotional activity for balance payment is Promotional Activity 3. The promotional activity for any payment method in payment application B is Promotional Activity 3.

[0383] It is understood that the embodiments shown in Table 2 are only examples. In the embodiments of this application, the preferential information may also include more, fewer or different preferential activities than those in the above embodiments, and this application does not limit it here.

[0384] S1124.NFC service module 12 displays promotional information.

[0385] In some embodiments, the NFC service module 12 may display promotional information to help users choose a suitable payment method.

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

[0387] S1125.NFC service module 12 receives and responds to the user's selection of payment method 2, and determines the actual payment amount 1 of payment method 2 based on the discount information.

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

[0389] After determining that payment method 2 is adopted, the NFC service module 12 can determine the actual payment amount (i.e., actual payment amount 1) of payment method 2 based on the amount payable and the promotional activities corresponding to payment method 2 in the promotional information.

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

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

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

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

[0394] In some embodiments, the specific process of step S1127 can also refer to the relevant description in the embodiments shown in Figure 12 or Figure 13 below, and will not be repeated here.

[0395] S1128. Payment receiving device 200 sends payment success notification 3.

[0396] The specific content of payment success notification 3 can be compared with the relevant description of payment success notification 1 in step S1114 above, and will not be repeated here.

[0397] S1129. Payment application set 11 outputs payment success message 3.

[0398] The details of step S1129 can be found in the relevant content of step S1115 above, and will not be repeated here.

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

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

[0401] It should be noted that after receiving the payment credential sent by the electronic device 100, the payment receiving device 200 can deduct funds from the payment account indicated by the payment credential through the payment cloud server 300. When deducting funds based on the payment credential, the payment cloud server 300 also needs to obtain the payment permission corresponding to the payment account. The payment permission may include a password-free payment permission and a verification payment permission. The specific functions of the two permissions can be referred to the relevant descriptions in the embodiment shown in Figure 9 above.

[0402] In some application scenarios, the payment cloud server 300 can determine whether to obtain payment verification permission from the electronic device 100 based on whether the current payment account can use password-free payment in this payment. The specific interaction process can be found in the relevant description in the embodiment shown in Figure 12 below.

[0403] Figure 12 shows a schematic diagram of a payment account deduction process provided in an embodiment of this application.

[0404] As shown in Figure 12, the specific process of deducting funds from the payment account indicated by the payment voucher sent by the electronic device 100 by the receiving device 200 may include the following steps:

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

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

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

[0408] S1202. Payment cloud server 300 determines whether the payment account indicated by the payment credential has enabled password-free payment.

[0409] If the payment account has enabled password-free payment, the payment cloud server 300 can perform the following steps S1203.

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

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

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

[0413] For example, if the payment account is payment account 1 in step S911 of Figure 9 or payment account 1 in step S1113 of Figure 11, the actual payment amount can be the amount payable; as another example, if the payment account is the member account in step S1119 of Figure 11, the actual payment amount can be the member payment amount; as another example, if the payment account is payment account 2 in step S1012 of Figure 10 or payment account 2 in step S1127 of Figure 11, the actual payment amount can be actual payment amount 1, etc.

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

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

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

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

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

[0419] S1205. Payment application set 11 receives and responds to the user's payment verification operation, and sends a verification payment permission to the payment cloud server 300.

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

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

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

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

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

[0425] After executing step S1206, the payment cloud server 300 can execute the following steps S1207 and S1209 in parallel, or execute steps S1207 and S1209 sequentially. This application embodiment does not limit the execution order of steps S1207 and S1209.

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

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

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

[0429] S1208. Payment cloud server 300 sends payment notification 1 to payment receiving device 200.

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

[0431] S1209. Payment cloud server 300 sends payment notification 1 to payment application set 11.

[0432] After executing step S1206, the payment cloud server 300 can execute step S1209.

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

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

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

[0436] It is understood that the embodiment shown in Figure 12 above is only an example. In this application embodiment, the payment receiving device 200 can also complete the payment in other ways, such as through the merchant backend server and the payment cloud server 300 to complete the above interaction process, etc. This application does not limit it here.

[0437] In some application scenarios, after identifying the payment account, the electronic device 100 can also determine the method and timing for sending payment authorization to the payment cloud server 300 based on whether the payment account can use password-free payment in this payment. In the case of password-free payment, the electronic device 100 can send payment credentials and password-free payment authorization to the payment cloud server 300 through the receiving device 200. In the case of non-password-free payment, the electronic device 100 can send a verification payment authorization to the payment cloud server 300. For specific interaction methods, please refer to the embodiment shown in Figure 13 below.

[0438] For example, taking payment application A as an example, Figure 13 shows a schematic diagram of a payment process after the payment method is determined, provided by an embodiment of this application.

[0439] As shown in Figure 13, an embodiment of this application provides a payment process after determining the payment method, which may include the following steps:

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

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

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

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

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

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

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

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

[0448] 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 S1304.

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

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

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

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

[0453] S1305.NFC service module 12 sends a payment credential and passwordless payment permission to the receiving device 200. The payment credential is used to indicate the payment account.

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

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

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

[0457] S1306. 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.

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

[0459] S1307. Payment cloud server 300 deducts funds from the payment account based on payment information 2, and the deducted amount is the actual amount paid.

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

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

[0462] The specific details of steps S1307 to S1309 can be found in the description of steps S1206 to S1208 in the embodiment shown in Figure 12 above, and will not be repeated here.

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

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

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

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

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

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

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

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

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

[0472] Step S1313 is an optional step.

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

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

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

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

[0477] S1315. Payment application A receives the user's payment verification operation.

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

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

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

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

[0482] S1317. Payment cloud server 300 deducts funds from the payment account based on payment information 3, and the deducted amount is the actual payment amount.

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

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

[0485] The specific details of steps S1317 to S1319 can be found in the descriptions of steps S1307 to S1309 above, and will not be repeated here.

[0486] S1320. Payment cloud server 300 sends payment notification 3 to payment application A.

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

[0488] It is understood that the embodiment shown in Figure 13 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 13 above. This application does not limit it here.

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

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

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

[0492] In some embodiments, after the electronic device 100 performs step S1123 as shown in FIG11, it may also determine the most favorable payment method based on the obtained preferential information and complete the payment using the most favorable payment method.

[0493] Figure 14 illustrates a schematic diagram of the process by which an electronic device 100, according to an embodiment of this application, determines the most favorable payment method and completes payment using that method.

[0494] As shown in Figure 14, the specific process by which electronic device 100 determines and uses the most favorable payment method to complete the payment may include the following steps:

[0495] S1401.NFC service module 12 determines the most favorable payment method based on preferential information.

[0496] After obtaining discount information from the payment application set 11, the NFC service module 12 can determine the discount amount of all discounted payment methods supported by the payment receiving device 200 based on the discount information, and then determine the most favorable payment method based on the size of the discount amount. The most favorable payment method is the payment method with the largest discount amount among all discounted payment methods supported by the payment receiving device 200.

[0497] S1402.NFC service module 12 determines the actual payment amount for the most favorable payment method based on the discount information 2.

[0498] After determining the most favorable payment method, the NFC service module 12 can determine the actual payment amount 2 for the most favorable payment method based on the discount amount and the amount due. The actual payment amount 2 is the difference between the amount due and the discount amount of the most favorable payment method.

[0499] S1403.NFC service module 12 sends payment credential 3 to receiving device 200, which indicates the payment account 3 of the most favorable payment method.

[0500] After determining the most favorable payment method, the NFC service module 12 can also determine the payment credential 3 for the most favorable payment method and send the payment credential 3 to the receiving device 200. The specific method by which the NFC service module 12 determines the payment credential 3 can be referred to the method for determining the payment credential 1 in step S1112 of Figure 11 above, and will not be repeated here.

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

[0502] S1405. The receiving device 200 sends a payment success notification to the payment application A via the NFC service module 12.

[0503] S1406. Payment application A outputs a payment success message 3.

[0504] The specific details of steps S1404 to S1406 can be found in the descriptions of steps S1113 to S1115 shown in Figure 11 above, and will not be repeated here.

[0505] In this way, the electronic device 100 can determine the most favorable payment method and make the payment without the user having to make a selection, thus improving payment efficiency.

[0506] It is understood that the embodiment shown in Figure 14 is only another example of determining the final payment method. In the embodiments of this application, the electronic device 100 may use the most favorable payment method, or it may use the payment method selected by the user, or it may use other methods to determine the final payment method. This application does not limit this.

[0507] In some application scenarios, a merchant's membership card does not have a payment function. In this case, even if the electronic device 100 has a merchant's membership card, it still needs to use other payment methods to complete the payment.

[0508] For example, Figure 15 shows another schematic diagram of a payment process in an electronic device 100 based on a membership card and other payment methods, provided by an embodiment of this application.

[0509] As shown in Figure 15, another specific process for completing a payment on electronic device 100 based on a membership card and other payment methods may include the following steps:

[0510] S1501. Payment device 200 determines that the payment device 200 supports preferential payment methods including membership card payment, and that the membership card does not have payment function.

[0511] S1502. Payment device 200 determines the member's payment amount.

[0512] The payment device 200 can determine the amount paid by the member based on activities such as membership card discounts and / or membership card points, as well as the amount due.

[0513] S1503. The payment device 200 sends a payment request 5, which includes an identifier of the preferential payment method supported by the payment device 200 and the member payment amount.

[0514] For details of step S1503, please refer to the relevant content in step S1117 shown in Figure 11 above.

[0515] S1504.NFC service module 12 sends the identifier of the preferential payment method supported by the payment device 200 and the member payment amount to the payment application set 11.

[0516] S1505. Payment application set 11 sends promotional information to NFC service module 12, which includes promotional activities for preferential payment methods supported by payment device 200.

[0517] S1506.NFC service module 12 displays promotional information.

[0518] S1507.NFC service module 12 receives and responds to the user's selection of payment method 4, and determines the actual payment amount 3 of payment method 4 based on the discount information and the member's payment amount.

[0519] S1508.NFC service module 12 sends a payment response 5 to the receiving device 200. The payment response 5 includes a payment credential 4 for payment method 4, which indicates the payment account 4 for payment method 4.

[0520] S1509. Payment device 200 deducts payment based on payment account 4, and the deduction amount is the actual payment amount 3.

[0521] S1510. The receiving device 200 sends a payment success notification 4 to the payment application set 11 via the NFC service module 12.

[0522] S1511. Payment Application Set 11 outputs payment success message 4.

[0523] The specific details of steps S1505 to S1511 can be found in the relevant descriptions of steps S1123 to S1129 shown in Figure 11 above, and will not be repeated here.

[0524] In this way, even if the membership card does not have payment capabilities, the electronic device 100 can still complete the payment by combining it with other payment methods, and can also take advantage of the promotional activities of other payment methods.

[0525] In other embodiments, the payment receiving device 200 may also obtain preferential information from the payment cloud server 300, and select the most favorable payment method by combining the payment methods supported by the payment receiving device 200 and the payment methods supported by the electronic device 100, and notify the electronic device 100 to complete the payment using the most favorable payment method.

[0526] Figure 16 illustrates a schematic diagram of the process by which a payment device 200 selects a payment method and completes payment through interaction with an electronic device 100, according to an embodiment of this application.

[0527] As shown in Figure 16, the specific process of a payment receiving device 200 selecting a payment method and completing a payment through interaction with an electronic device 100 may include the following steps:

[0528] S1601. The payment device 200 sends a request to the payment cloud server 300 to obtain preferential information.

[0529] The request for discount information may include identifiers of one or more payment methods, all of which are supported by the payment device 200.

[0530] The request for obtaining promotional information can be used to request the payment cloud server 300 to send promotional information to the payment receiving device 200. The promotional information includes promotional activities for one or more payment methods.

[0531] It should be noted that steps S1601 to S1602 may be performed before or after step S1603. In some other embodiments, steps S1601 and S1603 may be repeated steps, and the payment device 200 may perform step S1601 based on a fixed cycle.

[0532] S1602. The payment cloud server 300 sends promotional information to the payment receiving device 200.

[0533] The payment cloud server 300 can receive and respond to requests for obtaining promotional information and send promotional information to the payment receiving device 200.

[0534] S1603. Electronic device 100 enters the radio frequency field of receiving device 200.

[0535] S1604. The receiving device 200 sends a probe frame to the electronic device 100.

[0536] S1605.NFC service module 12 sends a probe ACK frame to the receiving device 200.

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

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

[0539] S1608.NFC service module 12 sends a pick ACK frame to the receiving device 200.

[0540] The specific details of steps S1603 to S1608 can be found in the relevant content of steps S1101 to S1106 in the embodiment shown in Figure 11 above, and will not be repeated here.

[0541] S1609. The receiving device 200 sends a payment method acquisition request to the electronic device 100.

[0542] The payment method acquisition request is used to request electronic device 100 to send the identifier of the payment method supported by electronic device 100.

[0543] S1610. The NFC service module 12 sends a payment method response to the receiving device 200, the payment method response including an identifier of one or more payment methods supported by the electronic device 100.

[0544] The payment method response can be used to inform the receiving device 200 and electronic device 100 of the payment methods supported.

[0545] S1611. Based on the preferential information, the payment device 200 determines the most favorable payment method among the payment methods supported by the electronic device 100 and the payment device 200.

[0546] S1612. Payment device 200 determines the actual payment amount for the most favorable payment method based on preferential information 4.

[0547] In steps S1611 and S1612, the method for determining the most favorable payment method and the method for determining the actual payment amount 4 can be referred to the relevant descriptions of steps S1401 and S1402 shown in Figure 14 above, and will not be repeated here.

[0548] S1613. The receiving device 200 sends a payment request 6 to the NFC service module 12. The payment request 6 includes the actual payment amount 4 and the identifier of the most favorable payment method.

[0549] Payment request 6 is used to request electronic device 100 to complete the payment using the payment method indicated in payment request 6 (i.e., the most favorable payment method), and the payment amount is the actual amount 4.

[0550] S1614. NFC service module 12 sends a payment response 6 to the receiving device 200. The payment response 6 includes a payment credential 5, which indicates the payment account 5 for the most favorable payment method.

[0551] S1615. Payment device 200 deducts payment based on payment account 5, with the deduction amount being the actual payment amount 4.

[0552] S1616. The receiving device 200 sends a payment success notification 5 to the payment application A via the NFC service module 12.

[0553] Payment application A refers to the payment application corresponding to the most favorable payment method. In some other embodiments, the most favorable payment application may also correspond to other payment applications. In this case, payment application A in the embodiment shown in Figure 16 may also be replaced by the other payment application.

[0554] S1617. Payment application A outputs a payment success message 5.

[0555] The specific details of steps S1614 to S1617 can be found in the description of steps S1403 to S1406 shown in Figure 14 above, and will not be repeated here.

[0556] In this way, the payment receiving device 200 can select the most favorable payment method and notify the electronic device 100 to complete the payment using the most favorable payment method.

[0557] It is understood that the embodiment shown in Figure 16 above is only an example. In the embodiments of this application, the payment device 200 can also receive the discount information sent by the electronic device 100 and determine the final payment method based on the discount information. This application does not limit this.

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

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

[0560] 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 FIG. 17 is merely an example, and the electronic device 100 may have more or fewer components than those shown in FIG. 17, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0578] 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 FIG4A above, and will not be repeated here.

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

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

[0581] The communication device of the present application embodiment will now be described in detail with reference to Figures 18 to 21.

[0582] Referring to FIG18, which is a schematic diagram of the structure of a communication device 1800 provided in an embodiment of this application, the communication device 1800 can be the electronic device 100 in the above embodiments. Optionally, the communication device 1800 can be a chip / chip system, such as an NFC chip. As shown in FIG18, the communication device 1800 may include a transceiver unit 1810 and a processing unit 1820.

[0583] The transceiver unit 1810 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.

[0584] Optionally, the processing unit 1820 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.

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

[0586] Referring to FIG19, which is a schematic diagram of the structure of a communication device 1900 provided in an embodiment of this application, the communication device 1900 can be the payment receiving device 200 in the above embodiments. Optionally, the communication device 1900 can be the payment receiving device 200. As shown in FIG19, the communication device 1900 may include a transceiver unit 1910 and a processing unit 1920.

[0587] Optionally, the transceiver unit 1910 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.

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

[0589] It should be understood that the communication device 1900 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 again here.

[0590] 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 FIG18 above, and any product with the functions of the payment device 200 described in FIG19 above, falls within the protection scope of the embodiments of this application.

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

[0592] Referring to Figure 20, which is a schematic diagram of the structure of a communication device 2000 provided in an embodiment of this application, the communication device 2000 may be an electronic device 100, or a device therein. As shown in Figure 20, the communication device 2000 includes a processor 2001 and a transceiver 2002 internally connected and communicating with the processor 2001. The processor 2001 may be a general-purpose processor or a dedicated processor, for example, a central processing unit and / or an NFC controller. The transceiver 2002 may be referred to as a transceiver unit, transceiver, or transceiver circuit, and is used to implement transceiver functions. The transceiver 2002 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, and is used to implement a receiving function, such as an NFC receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, and is used to implement a transmitting function, such as an NFC transmitting function. Optionally, the communication device 2000 may also include an antenna 2003 and / or a radio frequency unit (not shown in Figure 20), for example, an NFC antenna, wherein the NFC antenna may be a coil-type antenna. The antenna 2003 and / or radio frequency unit may be located inside the communication device 2000 or separate from the communication device 2000, that is, the antenna 2003 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

[0594] The processor 2001, transceiver 2002, and memory 2004 can be connected via a communication bus.

[0595] In one design, the communication device 2000 can be used to perform the functions of the electronic device 100 in the foregoing embodiments: the processor 2001 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 2002 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.

[0596] In any of the above designs, the processor 2001 may include a transceiver for implementing receiving and transmitting 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 receiving and transmitting 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.

[0597] In any of the above designs, the processor 2001 may store instructions, which may be computer programs. These computer programs, running on the processor 2001, cause the communication device 2000 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 2000; in this case, the processor 2001 may be implemented in hardware.

[0598] In one implementation, the communication device 2000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the aforementioned 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.

[0599] 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 FIG20. The communication device 2000 can be a standalone device or part of a larger device. For example, the communication device 2000 can be:

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

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

[0602] Referring to Figure 21, Figure 21 is a schematic diagram of the structure of a communication device 2100 provided in an embodiment of this application. The communication device 2100 can be a payment receiving device 200, or a device therein. As shown in Figure 21, the communication device 2100 includes a processor 2101 and a transceiver 2102 internally connected and communicating with the processor 2101. The processor 2101 can be a general-purpose processor or a dedicated processor, etc. For example, it can be an NFC controller. The transceiver 2102 can be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement transceiver functions. The transceiver 2102 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 2100 may also include an antenna 2103 and / or a radio frequency unit (not shown in the figure). The antenna 2103 and / or radio frequency unit may be located inside the communication device 2100 or separate from the communication device 2100, that is, the antenna 2103 and / or radio frequency unit may be deployed remotely or in a distributed manner.

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

[0604] The processor 2101, transceiver 2102, and memory 2104 can be connected via a communication bus.

[0605] In one design, the communication device 2100 can be used to perform the functions of the payment device 200 in the foregoing embodiments: the processor 2101 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 FIG. 21; the transceiver 2102 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 FIG. 21 and / or other processes used in the technology described herein.

[0606] In any of the above designs, the processor 2101 may include a transceiver for implementing receiving and transmitting 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 receiving and transmitting 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.

[0607] In any of the above designs, the processor 2101 may store instructions, which may be computer programs. These computer programs, running on the processor 2101, cause the communication device 2100 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 2101; in this case, the processor 2101 may be implemented in hardware.

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

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

[0610] S2201. After entering the radio frequency field of the receiving device, the electronic device receives a first payment request sent by the receiving device, the first payment request including a first amount and an identifier of one or more payment methods supported by the receiving device.

[0611] The electronic device can be the electronic device 100 in the above embodiments. The payment receiving device can be the payment receiving device 200 in the above embodiments.

[0612] The first payment request can be a payment request as described in the above embodiments, such as payment request 1 in the embodiment shown in Figure 9, payment request 2 in the embodiment shown in Figure 10, payment request 3 or payment request 4 in the embodiment shown in Figure 11, etc., which will not be elaborated here.

[0613] The first amount can be the amount that the receiving device should collect, i.e., the amount payable in the above embodiment.

[0614] S2202. The electronic device determines a first payment method from one or more payment methods supported by a first payment request.

[0615] The first payment method can be the payment method ultimately adopted by the electronic device.

[0616] For example, the first payment method can be payment method 1 in the embodiment shown in Figure 9 above, or payment method 2 in the embodiment shown in Figure 10 above, etc., which will not be described in detail here.

[0617] S2203. The electronic device completes payment via the first payment method.

[0618] The specific process for electronic devices to complete payment through the first payment method can be referred to the relevant steps in the embodiments shown in Figure 12 or Figure 13 above, and will not be repeated here.

[0619] In this way, electronic devices can complete payments by touching the payment device, simplifying the payment process and improving payment efficiency.

[0620] In one possible implementation, before receiving the first payment request sent by 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 feature information of the receiving device, the device feature 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 that the type of NFC service of the receiving device is codeless payment based on the device feature information of the receiving device; and sending a pick ACK frame to the receiving device, the pick ACK frame indicating that the electronic device has determined the type of NFC service of the receiving device.

[0621] The specific details of each of the above steps can be found in the detailed description of the relevant steps in the embodiment shown in Figure 9 above, and will not be repeated here.

[0622] In this way, electronic devices can communicate with payment devices based on a preset first protocol.

[0623] In one possible implementation, the type of NFC service of the receiving device is determined to be codeless payment based on the device feature information of the receiving device. Specifically, this includes: determining the type of NFC service of the receiving device as a first sub-service of codeless payment based on the device feature information of the receiving device. The first sub-service is codeless payment service without preferential payment methods.

[0624] For example, the first sub-service can be a general service under the codeless payment service in the embodiments shown in Table 1 above.

[0625] In this way, if it is determined that the receiving device does not offer preferential payment services, the electronic device does not need to obtain preferential information for each payment method, simplifying the payment process and improving payment efficiency.

[0626] In one possible implementation, determining the first payment method from one or more payment methods supported by a payment device based on a first payment request specifically includes: determining the first payment method from one or more payment methods supported by a payment device based on a user's first operation; or, determining the first payment method from one or more payment methods supported by a payment device based on a preset payment priority.

[0627] In this way, the final payment method can be determined based on the user's choice.

[0628] In one possible implementation, the type of NFC service of the receiving device is determined to be codeless payment based on the device feature information of the receiving device. Specifically, this includes determining the type of NFC service of the receiving device as codeless payment based on the device feature information of the receiving device as a second sub-service, where the second sub-service is a codeless payment service with preferential payment methods.

[0629] For example, the second sub-service may be the payment discount service under the codeless payment service in the embodiment shown in Table 1 above.

[0630] In this way, the payment device can inform the electronic device that it offers preferential payment services, allowing the electronic device to choose the most advantageous payment method and save the user money.

[0631] In one possible implementation, after determining that the NFC service of the receiving device is a second sub-service in codeless payment based on the device feature information of the receiving device, the method further includes: after entering the radio frequency field of the receiving device, receiving a first inquiry request sent by the receiving device, the first inquiry request being used to request the acquisition of preferential payment methods with promotional activities; in response to the first inquiry request, sending a first preferential response to the receiving device, the first preferential response including the identifier of one or more preferential payment methods; receiving a first payment request sent by the receiving device, specifically including: receiving a first payment request sent by the receiving device based on the first preferential response, the first payment request carrying the identifier of one or more preferential payment methods supported by the receiving device; determining a first payment method from the payment methods supported by one or more receiving devices based on the first payment request, specifically including: determining the first payment method from the preferential payment methods supported by one or more receiving devices based on the first payment request.

[0632] The first inquiry request can be the discount capability inquiry request in the embodiment shown in Figure 11 above. The first discount response can be the discount capability response 1 in the embodiment shown in Figure 11 above.

[0633] In this way, when the electronic device determines that the receiving device offers preferential payment services, the electronic device can obtain the preferential payment methods of the receiving device and choose the final payment method from the preferential payment methods supported by the receiving device, thus saving the user's expenses.

[0634] In one possible implementation, the preferential payment methods supported by one or more payment devices include membership card payment; determining the first payment method from the payment methods supported by one or more payment devices based on the first payment request specifically includes: determining the first payment method as membership card payment based on the first payment request.

[0635] The details regarding membership card payments can also be found in the embodiments shown in Figures 11 and 15 above, and will not be repeated here.

[0636] In this way, when an electronic device has a membership card corresponding to the payment device, membership card payment can be used first.

[0637] In one possible implementation, determining the first payment method from among the payment methods supported by one or more payment devices based on the first payment request specifically includes: obtaining first discount information based on the identifier of the discount payment method supported by one or more payment devices, the first discount information including the discount activities corresponding to the discount payment method supported by one or more payment devices; and determining the first payment method from the discount payment method supported by one or more payment devices based on the first discount information.

[0638] For example, the first discount information may be the discount information in the embodiment shown in Figure 11 above.

[0639] In this way, we can obtain promotional offers for the payment methods supported by the payment device, and determine the final payment method to be used based on the promotional offers for each payment method.

[0640] In one possible implementation, the preferential payment methods supported by one or more payment devices do not include membership card payments.

[0641] In this way, when it is determined that membership card payments are not supported, electronic devices can obtain specific promotional offers for other payment methods and then select the final payment method from among them.

[0642] In one possible implementation, determining a first payment method from among one or more preferential payment methods supported by one or more payment devices based on first preferential information specifically includes: determining the discount amount of each preferential payment method supported by one or more payment devices based on the first preferential information; 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.

[0643] This allows users to easily choose the appropriate payment method based on the initial discount information.

[0644] In one possible implementation, a first payment method is determined from among the preferential payment methods supported by one or more payment devices based on the first preferential information. Specifically, this includes: determining the discount amount of each preferential payment method among the preferential payment methods supported by one or more payment devices based on the first preferential information; and determining the first payment method based on the discount amount of each preferential payment method among the preferential payment methods supported by one or more payment devices, wherein the first payment method is the payment method with the largest discount amount among the preferential payment methods supported by one or more payment devices.

[0645] In this way, electronic devices can determine the payment method with the greatest discount based on the first discount information.

[0646] In one possible implementation, after determining that the type of the NFC service of the receiving device is the second sub-service in codeless payment based on the device feature information of the receiving device, the method further includes: after entering the radio frequency field of the receiving device, receiving a first inquiry request sent by the receiving device, the first inquiry request being used to request the identification of a preferential payment method with a promotional activity; in response to the first inquiry request, sending a second preferential response to the receiving device, the second preferential response being used to indicate that there is no preferential payment method.

[0647] For example, the second offer response can be the offer capability response 2 in the embodiment shown in Figure 11 above.

[0648] In this way, if the payment device offers discounted payment services, it can inquire with the electronic device whether the electronic device also offers discounted payment options. If the electronic device does not offer discounted payment options, it does not need to obtain further discount information.

[0649] In one possible implementation, determining a first payment method from one or more payment methods supported by a payment device based on a first payment request specifically includes: displaying one or more payment options, the one or more payment options including a second option corresponding to the first payment method, the second option including an identifier of the first payment method; receiving and responding to the user's operation on the second option, and determining the first payment method.

[0650] In this way, users can choose a suitable payment method, and the electronic device can determine the final payment method based on the user's choice.

[0651] In one possible implementation, determining a first payment method from among the payment methods supported by one or more payment devices based on a first payment request specifically includes: determining the first payment method from among the payment methods supported by one or more payment devices based on a preset payment method priority of the electronic device, wherein the first payment method is the payment method with the highest priority among the payment methods supported by one or more payment devices.

[0652] In this way, if no preferential payment method is available on the electronic device, the electronic device can choose the payment method with the highest priority as the final payment method.

[0653] 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 is used to indicate a first payment account.

[0654] The first payment response can be the payment response in the above embodiments, such as payment response 1 in the embodiment shown in Figure 9, payment response 2 in the embodiment shown in Figure 10, etc., which will not be elaborated here.

[0655] The first payment credential can be the payment credential in the above embodiments, such as the payment credential in the embodiment shown in Figure 9, or payment credential 2 in the embodiment shown in Figure 10, etc., which will not be described again here.

[0656] The first payment account is the payment account indicated by the first payment credential and is used for payment. For example, the first payment account can be payment account 1 in the embodiment shown in Figure 9 above, or payment account 2 in the embodiment shown in Figure 10 above, etc., which will not be described in detail here.

[0657] In this way, electronic devices can send payment credentials to the server through the payment device. The payment credentials are used to indicate the payment account so that the server can complete the deduction.

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

[0659] In this way, the receiving device can determine the payment method used by the electronic device based on the first payment credential.

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

[0661] In this way, the receiving device can determine the payment method used by the electronic device based on the first payment response.

[0662] 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 first discount information; sending a second payment response to the 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.

[0663] The second amount can be the actual amount paid for the electronic device.

[0664] The first receiving account refers to the account used by the receiving device to receive payments, i.e., the receiving account in the above embodiment.

[0665] In this way, electronic devices can interact directly with the server based on the communication connection between them to complete the payment.

[0666] In one possible implementation, payment is completed via a first payment method, which specifically includes sending a third payment response to the server. The third payment response includes a first payment credential, which is used to indicate a first payment account.

[0667] In this way, electronic devices can send payment vouchers and other information to the server based on communication with the server, and the server can also obtain information such as the receiving account and the amount due from the receiving device. That is, the server can complete the payment through interaction with electronic devices and receiving devices.

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

[0669] For example, in this embodiment, the first notification may be a payment notification as described in the above embodiments, such as payment notification 1 in the embodiment shown in FIG12, payment notification 2 and payment notification 3 in the embodiment shown in FIG13, etc., which will not be described again here.

[0670] In this way, after a successful payment, the electronic device can confirm the payment success based on the notification sent by the server.

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

[0672] For example, in this embodiment, the first notification may be the payment success notification in the above embodiments, such as payment success notification 1 and payment success notification 2 shown in Figure 11 above, etc., which will not be described again here.

[0673] In this way, after a successful payment, the electronic device can confirm the payment success based on the notification sent by the server.

[0674] The specific process of the payment method provided in the embodiments of this application is described below.

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

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

[0677] S2301. Electronic device 100 enters the radio frequency field of receiving device 200.

[0678] S2302. The receiving device 200 sends a probe frame to the electronic device 100.

[0679] S2303. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0680] The specific details of steps S2301-S2303 can be found in the description of steps S901-S903 shown in Figure 9 above, and will not be repeated here.

[0681] S2304. After receiving the Probe ACK frame, the payment receiving device 200 sends a Notify frame. The Notify frame carries the merchant ID and 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 a general service in codeless payment.

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

[0683] In another possible implementation, the device feature information may include a device organization identifier (ND_OUI), which can be used to indicate the manufacturer using the payment device 200 to provide NFC services. 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.

[0684] The specific content of the device feature information can be found in the relevant description in step S904 of Figure 9 above, and will not be repeated here.

[0685] S2305. Electronic device 100 determines the service type as a general service in codeless payment based on the device feature information of the receiving device 200.

[0686] In some embodiments, the electronic device 100 may determine the type of the NFC service of the receiving device as the first sub-service in codeless payment based on the device feature information. The first sub-service is a codeless payment service without preferential payment methods, that is, a general service in codeless payment.

[0687] In this embodiment, the Notify frame sent by the receiving device 200 may carry a device service identifier for indicating codeless payment, such as 0x07 as shown in Table 1 above. Optionally, it may also carry a device sub-service identifier to indicate the sub-service type of the receiving device 200. In step S2304, the device feature information is used to indicate that the service type of the receiving device 200 is a general service in codeless payment. Therefore, the device main service identifier that can be carried in the Notify frame may be 0x07 as shown in Table 1 above, and the device sub-service identifier may be 0x01. In this way, the service type of the receiving device 200 can be indicated by the device service identifier in the device feature information.

[0688] S2306. Electronic device 100 sends a Notify ACK frame.

[0689] 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. In some embodiments, the Notify ACK frame may be used to indicate that the electronic device 100 has determined the NFC service type of the receiving device 200.

[0690] The Notify ACK frame can be used to inform the receiving device 200 that the electronic device 100 has received the Notify frame.

[0691] S2307. Payment device 200 sends parameter negotiation command.

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

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

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

[0695] S2308. Electronic device 100 sends parameter negotiation response.

[0696] 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 S2307 above.

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

[0698] 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 S2309 and subsequent steps, the payment device 200 can interact with the electronic device 100 at the application layer via NFC.

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

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

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

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

[0703] S2310. 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.

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

[0705] In some embodiments, after receiving selection command 1, electronic device 100 can obtain the merchant ID of payment device 200 based on the Notify frame, and determine the identifier 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 identifier of one or more payment applications carried in selection response 1 may include the identifier of membership card payment.

[0706] Optionally, the selection response 1 may also carry capability information of one or more payment applications supported by the electronic device 100. This capability information can be used to indicate the payment capabilities of the payment applications. The higher the payment capability, the more preferentially the payment application is selected for use.

[0707] In some embodiments, capability information may include priority. Priority indicates the degree of priority set by the electronic device 100 for the payment application. 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. The receiving device 200 can determine the target payment application as the final payment method based on the capability information of one or more payment applications supported by the electronic device 100.

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

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

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

[0711] S2311. The receiving device 200 determines the target payment application 1 based on the payment methods supported by the electronic device 100 and the payment methods supported by the receiving device 200.

[0712] The receiving device 200 can determine the target payment application 1 based on one or more payment methods supported by the electronic device 100 and the one or more payment methods supported by the receiving device 200. The target payment application 1 is a payment method supported by both the receiving device 200 and the electronic device 100. In some embodiments, the target payment application 1 is also referred to as the first payment application.

[0713] If both the receiving device 200 and the electronic device 100 support only one payment application, the receiving device 200 can use that single payment application, which both the receiving device 200 and the electronic device 100 support, as the target payment application 1.

[0714] If both the receiving device 200 and the electronic device 100 support multiple payment applications, the receiving device 200 can select one of the multiple payment applications supported by both the receiving device 200 and the electronic device 100 as the target payment application 1.

[0715] In one example, the receiving device 200 may randomly select one of several payment applications that both the receiving device 200 and the electronic device 100 support as the target payment application 1.

[0716] In another example, the receiving device 200 may select and determine the target payment application 1 from multiple payment applications supported by both the receiving device 200 and the electronic device 100, based on the capability information of one or more payment applications supported by the electronic device 100, the one or more payment applications supported by the receiving device 200, and the one or more payment applications supported by the electronic device 100.

[0717] For example, electronic device 100 may support one or more payment applications, including payment application A1, payment application A2, payment application A3, payment application A4, and payment application A5. Payment receiving device 200 may support one or more payment applications, including payment application A1, payment application A2, payment application A3, payment application B1, and payment application B2. Both payment receiving device 200 and electronic device 100 may 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. Therefore, the target payment application 1 can be payment application A1.

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

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

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

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

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

[0723] S2314. The receiving device 200 sends order command 1, which carries order information 1.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0739] 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 could be, for example, the payment verification interface 600 shown in Figure 6A, or the payment verification interface 620 shown in Figure 6D. After the user completes 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.

[0740] S2318. 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.

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

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

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

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

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

[0746] After receiving a payment completion notification, electronic device 100 can output a payment completion prompt to inform the user that the payment amount has been successfully paid. This prompt can be text-based, audio-based, image-based, mechanical vibration-based, or indicator light-based, etc. For example, after receiving the payment completion notification, electronic device 100 can display a payment success interface (e.g., the payment success interface 500 shown in Figure 5B 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 to inform the user that the payment has failed.

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

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

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

[0750] It is understood that the embodiment shown in Figure 23 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.

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

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

[0753] As shown in Figure 24, the specific process of another payment method may include the following steps:

[0754] S2401. Electronic device 100 enters the radio frequency field of receiving device 200.

[0755] S2402. The receiving device 200 sends a probe frame to the electronic device 100.

[0756] S2403. After receiving a probe frame, electronic device 100 sends a probe ACK frame.

[0757] S2404. After receiving the Probe ACK frame, the payment receiving device 200 sends a Notify frame. The Notify frame carries the merchant ID and 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.

[0758] The specific details of steps S2401 to S2404 can be found in the description of steps S2301 to S2304 in the embodiment shown in Figure 23 above, and will not be repeated here.

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

[0760] The details of step S2405 can be found in step S1005 shown in Figure 10 above, and will not be repeated here.

[0761] In some embodiments, the electronic device 100 may determine the type of the NFC service of the receiving device as the second sub-service in codeless payment based on the device feature information. The second sub-service is a codeless payment service with preferential payment methods, that is, a payment preferential service in codeless payment.

[0762] In this embodiment, the Notify frame sent by the payment receiving device 200 may carry a device service identifier for indicating codeless payment, such as 0x07 as shown in Table 1 above. Optionally, it may also carry a device sub-service identifier to indicate the sub-service type of the payment receiving device 200. In step S2404, the device feature information is used to indicate that the service type of the payment receiving device 200 is a payment discount service in codeless payment. Therefore, the main device service identifier that can be carried in the Notify frame may be 0x07 as shown in Table 1 above, and the device sub-service identifier may be 0x02. In this way, the service type of the payment receiving device 200 can be indicated by the device service identifier in the device feature information.

[0763] S2406. Electronic device 100 sends a Notify ACK frame.

[0764] The Notify ACK frame can be used to inform the receiving device 200 that the electronic device 100 has received the Notify frame.

[0765] S2407. Payment device 200 sends parameter negotiation command.

[0766] S2408. Electronic device 100 sends parameter negotiation response.

[0767] The specific details of steps S2407-S2408 can be found in the relevant content of steps S2307-S2308 shown in Figure 23 above, and will not be repeated here.

[0768] S2409. The receiving device 200 sends selection command 3, which is used to select a payment service.

[0769] In some embodiments, selection command 3 is also referred to as the first selection command.

[0770] The details of step S2409 can be found in the description of step S2309 shown in Figure 23 above, and will not be repeated here.

[0771] S2410. Electronic device 100 sends selection response 3 based on merchant ID, selection response 3 carrying the identifiers and promotional information of one or more payment applications supported by electronic device 100.

[0772] In some embodiments, selection command 3 is also referred to as the first selection response.

[0773] In this embodiment of the application, the discount information is used to indicate the discount level when paying with a payment application.

[0774] Optionally, the selection response 3 may also include a priority (e.g., the priority in the capability information in the embodiment shown in Figure 23 above). The priority indicates the degree of priority set by the electronic device 100 for the payment application. In other embodiments, the electronic device 100 may also update the priority ranking of the payment applications based on the merchant ID and discount information; for example, setting the priority of payment applications with higher discounts to high priority, or setting the priority of membership card payments to high priority, etc.

[0775] In one example, response 3 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.

[0776] For details of step S2410, please refer to the relevant description in step S2310 shown in Figure 23 above, which will not be repeated here.

[0777] S2411. The receiving device 200 determines the target payment application 2 based on the payment application supported by the electronic device 100, the payment application supported by the receiving device 200, and the promotional information.

[0778] In some embodiments, the target payment application 2 is also referred to as the first payment application.

[0779] In one possible implementation, the receiving device 200 can receive 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, determines the actual payment amount for each of these payment applications, and selects the payment application with the lowest actual payment amount as the target payment application 2.

[0780] In other possible implementations, the receiving device 200 may also determine the final target payment application 2 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 2. 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 2. 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 2.

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

[0782] S2412. The receiving device 200 sends a selection command 4, which carries the identifier of the target payment application 2.

[0783] In some embodiments, selection command 4 is also referred to as the second selection command.

[0784] S2413. Electronic device 100 sends selection response 4, which indicates that electronic device 100 has successfully selected target payment application 2.

[0785] In some embodiments, option response 4 is also referred to as the second option response.

[0786] The specific details of steps S2412-S2413 can be found in the relevant descriptions of steps S2312-S2313 shown in Figure 23 above, and will not be repeated here.

[0787] S2414. The receiving device 200 sends order command 2, which carries order information 2.

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

[0789] The specific content of order information 2 can be compared with the relevant content of order information 1 in step S2314 of Figure 23 above, and will not be repeated here.

[0790] S2415. Electronic device 100 sends order response 2, which indicates that electronic device 100 has received order command 2.

[0791] In some embodiments, order response 2 is also referred to as the first order response.

[0792] S2416. The receiving device 200 sends a transaction initialization command 2, which is used to obtain a payment voucher.

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

[0794] S2417. Electronic device 100 sends transaction initialization response 2, which carries payment voucher 2.

[0795] In some embodiments, transaction initialization response 2 is also referred to as the first transaction initialization response.

[0796] S2418. The payment receiving device 200 initiates a payment receiving process to the server of the target payment application 2 based on the payment voucher 2 and the order information 2.

[0797] The specific content of steps S2414-S2418 can also be referred to the relevant content of steps S2314-S2318 shown in Figure 23 above, and will not be repeated here. It is understood that the embodiment shown in Figure 24 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, and this application does not limit it here.

[0798] The payment method provided in this application can not only simplify the payment process and improve payment efficiency, but also obtain preferential information and reduce user expenses.

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

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

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

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

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

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

[0805] 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, receiving a first payment request sent by the payment device, the first payment request comprising a first amount and an identification of one or more payment methods supported by the payment device; Determining a first payment method from the one or more payment methods supported by the payment device based on the first payment request; Completing payment through the first payment method.

2. The method of claim 1, wherein, Before receiving the first payment request sent by 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 acknowledgment (Probe ACK) frame to the payment 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 payment device, the pick frame carrying device characteristic information of the payment device, the device characteristic information of the payment device comprising a service identification and a device organization identification, wherein the service identification is used to indicate the type of NFC service supported by the payment device, and the device organization identification is used to indicate the 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 non-cash payment; Sending a pick acknowledgment (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.

3. The method of claim 2, wherein, The determination, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is non-cash payment specifically comprises: Determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is a first sub-service in non-cash payment, the first sub-service being a non-cash payment service without preferential payment method.

4. The method of claim 3, wherein, The determination, based on the first payment request, of the first payment method from the one or more payment methods supported by the payment device specifically comprises: Determining, based on a first operation of a user, the first payment method from the one or more payment methods supported by the payment device; Or, Determining, based on a preset payment priority, the first payment method from the one or more payment methods supported by the payment device.

5. The method of claim 2, wherein, The determination, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is non-cash payment specifically comprises: Determining, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is a second sub-service in non-cash payment, the second sub-service being a non-cash payment service with preferential payment method.

6. The method of claim 5, wherein, After the determination, based on the device characteristic information of the payment device, that the type of NFC service of the payment device is the second sub-service in non-cash payment, the method further comprises: After entering the radio frequency field of the payment device, receiving a first inquiry request sent by the payment device, the first inquiry request being used to request a preferential payment method with preferential activity; in response to the first inquiry request, sending a first preferential response to the payment-receiving device, the first preferential response comprising identification of one or more preferential payment methods; the receiving the first payment request sent by the payment-receiving device comprises: receiving the first payment request sent by the payment-receiving device based on the first preferential response, the first payment request carrying identification of one or more preferential payment methods supported by the payment-receiving device; the determining the first payment method from the one or more payment methods supported by the payment-receiving device based on the first payment request comprises: determining the first payment method from the one or more preferential payment methods supported by the payment-receiving device based on the first payment request.

7. The method of claim 6, wherein, the one or more preferential payment methods supported by the payment-receiving device comprise member card payment; the determining the first payment method from the one or more payment methods supported by the payment-receiving device based on the first payment request comprises: determining, based on the first payment request, that the first payment method is member card payment.

8. The method of claim 6, wherein, the determining the first payment method from the one or more payment methods supported by the payment-receiving device based on the first payment request comprises: obtaining first preferential information based on the identification of the one or more preferential payment methods supported by the payment-receiving device, the first preferential information comprising preferential activities corresponding to the one or more preferential payment methods supported by the payment-receiving device; determining the first payment method from the one or more preferential payment methods supported by the payment-receiving device based on the first preferential information.

9. The method of claim 8, wherein, the one or more preferential payment methods supported by the payment-receiving device do not comprise member card payment.

10. The method according to claim 8 or 9, characterized in that, the determining the first payment method from the one or more payment methods supported by the payment-receiving device based on the first payment request comprises: determining, based on the first preferential information, preferential amounts of each of the one or more preferential payment methods supported by the payment-receiving device; 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 identification of the first payment method and a preferential amount of the first payment method; receiving and responding to user operation on the first option to determine the first payment method.

11. The method according to claim 8 or 9, characterized in that, the determining the first payment method from the one or more payment methods supported by the payment-receiving device based on the first payment request comprises: determining, based on the first preferential information, preferential amounts of each of the one or more preferential payment methods supported by the payment-receiving device; determining the first payment method based on the preferential amounts of each of the one or more preferential payment methods supported by the payment-receiving device, the first payment method being the payment method with the largest preferential amount among the one or more preferential payment methods supported by the payment-receiving device.

12. The method of claim 5, wherein, after the determining, based on the device feature information of the payment-receiving device, that the type of NFC service of the payment-receiving device is the second sub-service in the code-free payment, the method further comprises: After entering a radio frequency field of a payment device, a first inquiry request sent by the payment device is received, the first inquiry request being used to request an identification of a preferential payment method with a preferential activity; In response to the first inquiry request, a second preferential response is sent to the payment device, the second preferential response being used to indicate that there is no preferential payment method.

13. The method of claim 12, wherein, The first payment method is determined from the one or more payment methods supported by the payment device based on the first payment request, specifically including: One or more payment options are displayed, the one or more payment options including a second option corresponding to the first payment method, the second option including an identification of the first payment method; The first payment method is determined in response to an operation of a user on the second option.

14. The method of claim 12, wherein, The first payment method is determined from the one or more payment methods supported by the payment device based on the first payment request, specifically including: The first payment method is determined from the one or more payment methods supported by the payment device based on a payment method priority preset by the electronic device, the first payment method being a payment method with the highest priority among the one or more payment methods supported by the payment device.

15. The method of any one of claims 1-14, wherein, The payment is completed through the first payment method, specifically including: A first payment response is sent to the payment device, the first payment response including a first payment credential, the first payment credential being used to indicate the first payment account.

16. The method of any one of claims 1-14, wherein, The first payment request further includes a first payment account; The payment is completed through the first payment method, specifically including: A second amount corresponding to the first payment method is determined based on the first amount and the first preferential information; A second payment response is sent to the server, the second payment response including a first payment credential, the second amount, and the first payment account, the first payment credential being used to indicate the first payment account.

17. The method of any one of claims 1-14, wherein, The payment is completed through the first payment method, specifically including: A third payment response is sent to the server, the third payment response including a first payment credential, the first payment credential being used to indicate the first payment account.

18. The method of any one of claims 1-17, wherein, The method further includes: A first notification sent by the server is received, the first notification being used to notify the electronic device of a successful payment.

19. The method of any one of claims 1-17, wherein, The method further includes: A first notification sent by the payment device is received, the first notification being used to notify the electronic device of a successful payment.

20. A payment method applied to an electronic device, comprising: The method includes: A first merchant identification sent by the payment device is received, the first merchant identification being used to indicate a merchant to which the payment device belongs; A first response is sent to the payment device, the first response being used to indicate that the electronic device successfully receives the first merchant identification; An identification of one or more payment applications supported by the electronic device is determined based on the first merchant identification; A first selection command sent by the payment device is received; A first selection response is sent to the payment device based on the first merchant identification, the first selection response including the identification of the one or more payment applications supported by the electronic device; A first selection response is sent to the payment device based on the first merchant identification, the first selection response including the identification of the one or more payment applications supported by the electronic device; receiving a second selection command sent by the payment device, the second selection command comprising an identification of the 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; completing payment through the first payment application.

21. The method of claim 20, wherein, The receiving of the first merchant identification sent by the payment device specifically comprises: receiving device characteristic information sent by the payment device, the device characteristic information of the payment device comprising a service identification and a device organization identification, wherein the service identification is used to indicate a type of NFC service supported by the payment device, and the device organization identification is used to indicate the first merchant identification.

22. The method of claim 20 or 21, wherein, The first selection response further comprises a first priority ranking of one or more payment applications supported by the electronic device.

23. The method of claim 22, wherein, The sending of the first selection response to the payment device based on the first merchant identification specifically comprises: determining the first priority ranking based on the first merchant identification; sending the first selection response to the payment device.

24. The method of claim 23, wherein, The determining of the first priority ranking based on the first merchant identification specifically comprises: determining that the first electronic device has a member card of the first merchant based on the first merchant identification; setting a payment application with the highest priority in the first priority ranking as the member card payment of the first merchant.

25. The method of any one of claims 20-24, wherein, The completing of payment through the first payment application specifically comprises: receiving a first order command sent by the payment device, the first order command comprising a first order identification 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; sending a first initialization transaction response to the payment device, the first initialization transaction response carrying the first payment credential.

26. The method of any one of claims 21-25, wherein, Before receiving the first selection command sent by 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 (Probe ACK) frame to the payment device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; The receiving of the device characteristic information sent by the payment device specifically comprises: 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 comprises: determining, based on the device characteristic information of the payment device, that a type of NFC service of the payment device is no-code payment; The sending of the first response to the payment device specifically comprises: sending a notification acknowledgement (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 comprises: receiving a parameter negotiation command sent by the payment device; In response to the parameter negotiation command, a parameter negotiation response is sent to the payment device. The parameter negotiation command and the parameter negotiation response are used to negotiate data transmission parameters between the application layer of the payment device and the electronic device.

27. The method of claim 26, wherein, The step of determining that the NFC service type of the payment device is codeless payment based on the device feature information of the payment device specifically includes: Based on the device feature information, the NFC service of the payment device is determined to be the first sub-service in codeless payment, which is a codeless payment service without preferential payment methods.

28. The method of claim 26, wherein, The step of determining that the NFC service type of the payment device is codeless payment based on the device feature information of the payment device specifically includes: Based on the device feature information, the NFC service of the payment device is determined to be the second sub-service in codeless payment, and the second sub-service is a codeless payment service with preferential payment methods.

29. The method of claim 28, wherein, The first selection response further includes first offer information, which indicates promotional activities of one or more payment applications supported by the electronic device.

30. A payment method applied to a payee device, the method comprising: The method includes: Send a first merchant identifier to the electronic device, the first merchant identifier being used to indicate the merchant to which the payment device belongs; Receive a first response sent by the electronic device, the first response being used to indicate that the electronic device has successfully received the first merchant identifier; Send a first selection command to the electronic device, the first selection command being used to select a payment service; Receive a first selection response sent by the electronic device, the first selection response including identifiers of one or more payment applications supported by the electronic device; Based on one or more payment applications supported by the electronic device and one or more payment applications supported by the receiving device, one or more payment applications supported by both the electronic device and the receiving device are determined. A first payment application is determined from one or more payment applications supported by both the electronic device and the receiving device; Send a second selection command to the electronic device, the second selection command including the identifier of the first payment application; Receive a second selection response sent by the electronic device, the second selection response being used to indicate that the first payment application has successfully selected; Complete the payment through the first payment application.

31. The method of claim 30, wherein, Sending the first merchant identifier to the electronic device specifically includes: The device characteristic information of the receiving device is sent to the electronic device. The device characteristic information of the receiving device includes a service identifier and a device organization identifier. The service identifier is used to indicate the type of NFC service supported by the receiving device, and the device organization identifier is used to indicate the first merchant identifier.

32. The method of claim 30 or 31, wherein, The first selection response further includes a first priority order, which is a priority order of one or more payment applications supported by the electronic device.

33. The method of any one of claims 30-32, wherein, The payment process via the first payment application specifically includes: A first order command sent to the electronic device, the first order command including a first order identifier and a first payment amount; receive a first order response sent by the electronic device, the first order response being used to indicate that the first order command is successfully received; send a first initialization transaction command to the electronic device, the first initialization transaction command being used to obtain a first payment credential of the first payment application; receive a first initialization transaction response sent by the electronic device, the first initialization transaction response carrying the first payment credential; send the first order identifier, the first payment amount and the first payment credential to a server corresponding to the first payment application; receive a collection success notification sent by the server corresponding to the first payment application, the collection success notification being used to indicate that the collection is successful.

34. The method of any one of claims 31-33, wherein, Before receiving the first selection command sent by the collection device, the method further comprises: sending a probe frame to the electronic device, the probe frame being used to indicate that the collection device supports a specified NFC protocol; receiving a probe acknowledgement (Probe ACK) frame sent by the electronic device, the Probe ACK frame being used to indicate that the electronic device supports the specified NFC protocol; sending device feature information to the electronic device, specifically comprising: sending a notification (Notify) frame to the electronic device, the Notify frame carrying the device feature information of the collection device; receiving a first response sent by the electronic device, specifically comprising: receiving a notification acknowledgement (Notify ACK) frame sent by the electronic device, the Notify ACK frame being used to indicate that the Notify frame is successfully received; The method further comprises: sending a parameter negotiation command to the electronic device; receiving a parameter negotiation response sent by the electronic device, the parameter negotiation command and the parameter negotiation response being used to negotiate data transmission parameters between the application layer of the collection device and the electronic device.

35. The method of any one of claims 30-34, wherein, The first selection response further comprises first discount information, the first discount information being used to indicate discount activities of one or more payment applications supported by the electronic device.

36. An electronic device, comprising: The chip system comprises one or more processors and one or more memories, wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store computer instructions, and when the one or more processors execute the computer instructions, the payment method in any one of claims 1-29 and 30-35 is implemented.

37. A chip system, characterized by The chip system comprises processing circuitry and interface circuitry, the interface circuitry being used to receive code instructions and transmit the code instructions to the processing circuitry, and the processing circuitry being used to run the code instructions to execute the payment method in any one of claims 1-29 and 30-35.

38. A readable storage medium characterized by, The computer instructions are stored in the memory and are executed by the processor to implement the payment method in any one of claims 1-29 and 30-35.

39. A computer program product, characterised in that, The computer program comprises computer instructions, and when the computer instructions are executed by the processor, the payment method in any one of claims 1-29 and 30-35 is implemented.

Images