Payment method and terminal

By displaying and switching payment card snapshots of the second payment application in the first payment application, the problem of cumbersome switching operations of the default payment application during NFC payment is solved, and the user experience and the efficiency of the terminal device are improved.

CN119067653APending Publication Date: 2024-12-03SHENZHEN XUNLIAN ZHIFU NETWORK CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310606908.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-26
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

In the prior art, NFC payments are complicated to switch the default payment application in different payment scenarios, which reduces the intelligent interaction ability and usage efficiency between the terminal device and the user.

Method used

By obtaining and displaying a snapshot of the payment card of the second payment application in the first payment application, the user is allowed to select different payment cards in one application, and the switching and use of different payment applications is realized, avoiding the cumbersome setting process.

Benefits of technology

This simplifies the process of users switching payment applications between different payment scenarios, improves user experience and terminal devices' usage efficiency, and reduces operation steps.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119067653A_ABST
    Figure CN119067653A_ABST
Patent Text Reader

Abstract

The invention discloses an NFC payment method and a terminal, relates to the technical field of terminals, and aims to solve the problem that in the prior art, when NFC payment is used, the operation of switching a default payment application is tedious. The NFC payment method comprises the steps that after one of a plurality of NFC payment applications is selected as a first payment application, namely a system default NFC payment application, and the other payment applications are selected as second payment applications, namely non-system default NFC payment applications, a second payment card is opened by the second payment applications; the first payment application obtains a second payment card snapshot of a second payment application; in response to an operation of opening the NFC payment interface of the first payment application by the user, displaying a second payment card of a second payment application in the NFC payment interface; in response to an operation of selecting a second payment card of a second payment application by the user, the first payment application displays a payment interface of the second payment application according to a second payment card snapshot of the second payment application; and the second payment application interacts with the second terminal to complete payment. The user can select the second payment card in the first payment application to complete payment.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a payment method and a terminal. Background Art

[0002] With the rapid development of mobile payment, NFC (Near Field Communication) is becoming more and more widely used in the payment field. NFC payment has been widely used in payment applications such as bank cards and transportation cards.

[0003] Huawei Wallet, Apple Pay Samsung Pay and Xiaomi Pay Payment applications such as NFC are developed by terminal manufacturers, card organizations, and card issuers based on the secure element (SE) and NFC in the terminal. They allow users to bind their physical bank cards such as credit cards or debit cards to the terminal to form a virtual bank card. The card organization can be China UnionPay, etc.; the card issuer can be a state-owned bank such as Bank of China, as well as a commercial bank such as China Merchants Bank. After the physical bank card is bound to the terminal to form a virtual bank card, the terminal can be used to stick the card reader of the NFC point of sale (POS) machine. This action is also called "Tap", and the card payment can be completed. According to UnionPay's name, it is "Quick Pay". It should be noted that the virtual bank card data, including the payment token and payment key, are stored in the SE. The SE has a security storage capacity that is no less than that of the physical bank card and is a reliable virtual bank card carrier. The virtual bank card generated by binding the physical bank card to the terminal is also called a payment card.

[0004] in addition, Third-party payment apps such as NFC also support NFC payment.

[0005] In the prior art, each payment application on the terminal can rely on NFC payment capabilities to complete the interaction with POS machines and gate machines to achieve the corresponding transaction purpose. When the user faces different payment scenarios and wants to change the payment application, the default payment application in the NFC function on the terminal device can be set as the payment application the user wants.

[0006] For example, if a user initially sets the default payment app for NFC payment to "Huawei Wallet", and then the user wants to pass through the subway gate, he wants to set the default payment app to Reference Figure 1:The user needs to select "More connections" in the setting interface 101 of the mobile phone 100 to open the "More connections" interface shown in interface 102; then select the "NFC" option in interface 102 to switch to the interface shown in interface 103; select "Default payment application" in interface 103 to enter the "Default payment application" selection interface shown in interface 104. Finally, the user selects the "Default payment application" in the "Default payment application" interface shown in interface 104. As the default payment application for NFC payment, it can be seen that in the process of setting and switching the default payment application, the user has to perform many operations, which is too cumbersome. Summary of the invention

[0007] The embodiments of the present application provide a payment method and a terminal to solve the problem in the prior art of cumbersome operation when switching default payment applications in different payment scenarios when using NFC payment.

[0008] In a first aspect, an embodiment of the present application provides a payment method, including: a second payment application activates a second payment card, wherein the second payment application is a payment application for NFC payment that is not the system default, and the payment card refers to a virtual card that has the ability to use NFC payment for payment transactions; the first payment application obtains a second payment card snapshot of the second payment application, wherein the first payment application is set as the system default NFC payment payment application, and the second payment card snapshot includes a link to jump to a payment interface of the second payment card; in response to a user's operation of opening the NFC payment interface of the first payment application, displaying the second payment card of the second payment application in the NFC payment interface; in response to a user's operation of selecting the second payment card of the second payment application, the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application; the second payment application interacts with a second terminal to complete the payment.

[0009] The embodiment of the present application allows the user to see the payment card of the second payment application in the first payment application, and to use different payment capabilities by selecting different payment cards.

[0010] In a possible implementation manner of the first aspect, the method further includes: the first payment application opening a first payment card.

[0011] That is to say, the first payment application can also activate its own first payment card.

[0012] In a possible implementation manner of the first aspect, after the first payment application activates the first payment card, the method further includes: in response to a user opening the NFC payment interface of the first payment application, displaying the first payment card in the NFC payment interface.

[0013] In a possible implementation manner of the first aspect, the first payment application obtains the second payment card snapshot of the second payment application, including: the first payment application sends a message to the second payment application requesting to obtain the second payment card snapshot of the second payment application; and the second payment application sends the second payment card snapshot of the second payment application to the first payment application.

[0014] That is, the first payment application may actively request the second payment application to obtain the second payment card snapshot of the second payment application, and the second payment application sends the second payment card snapshot to the first payment application.

[0015] In a possible implementation manner of the first aspect, before the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application, it also includes: the first payment application obtains the state of the foreground payment application setting switch of the NFC payment setting of the first terminal, wherein the foreground payment application setting switch is used to control the turning on or off of the foreground application priority function, and the foreground application priority function is used to use the payment application located on the current display interface as the preferred payment application; if the foreground payment application setting switch is not turned on, the first payment application sets the foreground payment application setting switch to the on state.

[0016] That is, the state of the foreground payment application setting switch needs to be set to the on state in order for the first payment application to successfully display the payment interface of the second payment application according to the second payment card snapshot of the second payment application.

[0017] In a possible implementation of the first aspect, after the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application, it also includes: the second payment application interacts with the second terminal to display a prompt message of insufficient balance; the second payment application displays the recharge interface of the second payment application in response to the user selecting a recharge operation; in response to the user completing the recharge operation in the recharge interface of the second payment application, the second payment application displays an interface where recharge is completed.

[0018] That is, when the user selects the second payment card of the second payment application for payment and the balance of the second payment card is insufficient, the user can recharge the second payment card.

[0019] In a possible implementation manner of the first aspect, after the second payment application displays an interface indicating that recharge is completed, the method further includes: the second payment application displays the payment interface of the second payment application.

[0020] In a possible implementation manner of the first aspect, the second payment application interacts with the second terminal, and after the payment is completed, it also includes: the second payment application closes the payment interface of the second payment application; and the first payment application displays the second payment card in the NFC payment interface.

[0021] In a possible implementation manner of the first aspect, the second payment application interacts with the second terminal, and after the payment is completed, it also includes: the second payment application provides a message indicating that the balance of the second payment card is insufficient to the first payment application; the first payment application receives the message indicating that the balance of the second payment card is insufficient, and displays the information indicating that the balance of the second payment card is insufficient in the NFC payment interface of the first payment application.

[0022] In a possible implementation manner of the first aspect, the second payment card snapshot also includes a link to jump to a second payment card recharge interface, and the method further includes: in response to the user selecting an operation to recharge the second payment card, the first payment application displays the recharge interface of the second payment application according to the second payment card snapshot; and in response to the user completing the recharge operation in the recharge interface of the second payment application, the second payment application displays an interface indicating that the recharge of the second payment application has been completed.

[0023] That is, after the second payment application interacts with the second terminal to complete the payment, when it is found that the balance of the second payment card is insufficient, the second payment card can be recharged.

[0024] In a possible implementation manner of the first aspect, after displaying the interface showing that the second payment application has completed recharging, it also includes: the second payment application closes the interface showing that the recharging has been completed of the second payment application; and the first payment application displays the second payment card in the NFC payment interface.

[0025] In a second aspect, an embodiment of the present application provides a first terminal device, comprising: a memory for storing instructions executed by one or more processors of the first terminal; a transceiver for receiving or sending radio signals; and a processor, which, when the processor executes the instructions in the memory, enables the first terminal device to implement the steps of the NFC payment method proposed in the first aspect of the embodiment of the present application.

[0026] In a third aspect, an embodiment of the present application provides a chip, wherein the chip system includes a processing circuit and a storage medium, wherein the storage medium stores computer program code; when the computer program code is executed by the processing circuit, the steps of the NFC payment method proposed in the first aspect of the embodiment of the present application are implemented.

[0027] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer program runs on a computer, the computer executes the steps of the NFC payment method proposed in the first aspect of the embodiment of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 A schematic diagram of the process of selecting a default payment application in NFC payment in the prior art;

[0029] FIG. 2( a ) is a schematic diagram of an application scenario of the NFC payment method provided in an embodiment of the present application;

[0030] FIG2( b ) is a schematic diagram of another application scenario of the NFC payment method provided in an embodiment of the present application;

[0031] Figure 3 A schematic diagram of the structure of a mobile phone provided in an embodiment of the present application;

[0032] Figure 4 A software structure block diagram of a first terminal and a second terminal provided in an embodiment of the present application;

[0033] Figure 5 A schematic diagram of a system architecture of a first payment application and a second payment application provided in an embodiment of the present application;

[0034] Figure 6 A schematic diagram of a foreground application priority setting interface provided in an embodiment of the present application;

[0035] FIG. 7( a ) is a schematic diagram of a NFC payment method provided in an embodiment of the present application. Figure 1 ;

[0036] FIG. 7( b ) is a second process diagram of an NFC payment method provided in an embodiment of the present application;

[0037] FIG. 7( c ) is a schematic diagram of a NFC payment method provided in an embodiment of the present application. Figure 3 ;

[0038] FIG8( a ) is a schematic diagram of a NFC payment method provided in an embodiment of the present application. Figure 4 ;

[0039] FIG8( b ) is a schematic diagram of a NFC payment method provided in an embodiment of the present application. Figure 5 ;

[0040] Fig. 9 Schematic diagram of the NFC payment method provided in this application embodiment Figure 1 ;

[0041] Fig.10 Schematic diagram 2 of the NFC payment method provided in the embodiment of the present application;

[0042] Fig.11 A schematic diagram of the structure of the first terminal provided in the embodiment of the present application Figure 1 ;

[0043] Fig.12 A second structural diagram of the first terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0045] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0046] Near Field Communication (NFC) is a short-range wireless connection technology based on Radio Frequency Identification (RFID) technology. NFC operates at a distance of 10 cm at an operating frequency of 13.56 MHz ± 7 kHz, and its transmission speed is 106 Kbit / s, 212 Kbit / s or 424 Kbit / s. At present, NFC technology has become a relevant international standard and is widely used. NFC technology uses radio frequency field induction to achieve short-range communication between NFC terminals. Two NFC terminals can achieve fast, secure and contactless exchange of information, content and transactions by touching or approaching each other.

[0047] Specifically, the working modes of NFC terminals can be divided into three types: 1. Reader mode (Reader / Writer, R / W), in which the NFC terminal is used as a contactless reader. For example, relevant information can be read from a poster or an NFC tag on an exhibition. In this mode, an NFC terminal with read and write functions can collect data from an NFC tag and then process the data. Typical scenarios based on this mode include electronic advertising reading and ticket and cinema ticket sales. For example, an NFC tag is attached to a movie poster, and users can use an NFC-enabled terminal to get detailed information about the movie by placing it close to the movie poster. The reader mode can also be used for simple data acquisition, such as bus station information, park map information, etc. 2. Peer-to-Peer mode (P2P), in which two NFC terminals can quickly establish a connection to achieve peer-to-peer data transmission. Based on this mode, multiple digital cameras, tablets, and mobile phones with NFC functions can be wirelessly connected to achieve data exchange. Typical application scenarios based on this mode include quickly establishing a Bluetooth connection and exchanging contact business cards. 3. Card Emulation (CE) mode, which is specifically used in mobile payment or identity authentication scenarios such as bank cards, transportation cards, membership cards, coupons, and ID cards. In card emulation mode, the NFC reader is an active device that generates an NFC radio frequency field; the NFC terminal is a passive device that simulates a contactless radio frequency card that complies with the NFC standard to interact with the above NFC reader. This mode is mainly used in contactless mobile payment scenarios such as stores and transportation. Users only need to bring the NFC terminal close to the NFC reader and enter the password to confirm the transaction or directly receive the transaction. This allows the use of NFC terminals for contactless payment services without changing existing facilities. Typical scenarios based on this mode include local payment, access control, etc.

[0048] In card emulation mode, current NFC terminals can support three types of emulated cards at the same time. An emulated card refers to a radio frequency card that is emulated by a mobile device through NFC hardware. These three types of emulated cards are bank cards, bus cards, and access control cards. These three types of emulated cards are virtual cards, also known as payment cards.

[0049] Taking the NFC terminal as a mobile phone as an example, currently, when a payment application provided by a bank or other financial institution is installed on the mobile phone, the mobile phone can work in the card emulation working mode to complete the payment. That is, by downloading and installing the payment application on the mobile phone, binding the payment application with the physical card to realize the card emulation of the mobile phone, it can replace the traditional physical integrated circuit (IC) card and directly use the mobile phone to complete the payment.

[0050] However, when users need to switch the default payment application in different NFC payment scenarios, they need to go through the following steps: Figure 1 The numerous steps of the setting operation shown seriously reduce the intelligent interaction capability between the terminal device and the user, and also make the use efficiency of the terminal device low, causing inconvenience to the user.

[0051] In order to solve the problem in the prior art that it is cumbersome to switch the default payment application in different payment scenarios when using NFC payment, the embodiment of the present application integrates different payment applications in NFC payment to provide a method for swiping a card to complete NFC payment in different payment scenarios without switching the default payment application.

[0052] The NFC payment method provided in the embodiment of the present application is applied to the scenario of payment between two different terminals supporting the NFC function. For the convenience of description, the two different terminals supporting the NFC function are referred to as the first terminal and the second terminal in the embodiment of the present application. Among them, the first terminal can be a mobile phone, a tablet computer, a laptop computer, a super mobile personal computer, a netbook, a personal digital assistant, a wearable device, etc. The second terminal can also be a mobile phone, a tablet computer, a laptop computer, a wearable device, a POS machine, etc.

[0053] Exemplarily, as shown in FIG. 2( a ), the first terminal referred to in the embodiment of the present application may be a mobile phone 100 , and the second terminal may be a POS terminal 200 .

[0054] Exemplarily, as shown in FIG. 2( b ), the first terminal and the second terminal referred to in the embodiment of the present application may both be a mobile phone 100 .

[0055] The first terminal and the second terminal referred to in the embodiment of the present application both support the NFC function. And a payment application that can support NFC payment is installed in the first terminal and the second terminal, wherein the payment application may be an application preset by the manufacturer of the first terminal or the second terminal or a so-called system-provided application, which can carry bank cards, bus cards and other card simulation applications that support NFC payment. The payment application may also be a third-party application, mainly referring to an application provided by a payment service provider with an online card binding function (it can be understood that the association record of the account of the third-party payment application and the card bound to it online can be saved on the server side, and there is no need to download the card application and personal data locally on the terminal to simulate the card). In other words, the third-party payment application referred to in the embodiment of the present application includes but is not limited to applications that only provide online card binding and online payment functions, or at least provide online card binding and online payment functions. For example: the third-party payment application includes wait.

[0056] It should be noted that the third-party payment application described in the embodiments of the present application generally supports users to set it as the default payment application for NFC payment, such as Figure 1 The middle interface 104 shows etc. Some of these third-party applications, such as Able to activate payment cards and successfully pay using NFC. There are also some third-party applications, such as Since the third-party application may not have the ability to activate a payment card, setting it as the default payment application may not be able to use the NFC payment capability to make payments normally. The NFC payment method provided in the embodiment of the present application can also enable these third-party applications to successfully complete payment by calling the NFC payment capability of other payment applications.

[0057] For example, the first terminal and the second terminal are both mobile phones. Figure 3 As shown, the mobile phone 100 includes:

[0058] Processor 310, memory (including external memory interface 320 and internal memory 321), universal serial bus (USB) interface 330, charging management module 340, power management module 341, battery 342, antenna 1, antenna 2, mobile communication module 350, wireless communication module 360, audio module 370, speaker 370A, receiver 370B, microphone 370C, headphone interface 370D, sensor module 380, button 390, motor 391, indicator 392, camera 393, display screen 394, and subscriber identification module (SIM) card interface 395, etc.

[0059] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0060] The processor 310 may include one or more processing units. For example, the processor 310 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a flight controller, 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.

[0061] In some embodiments, the mobile phone 100 may also include one or more processors 310. Among them, the controller can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions. In some other embodiments, a memory can also be set in the processor 310 to store instructions and data. Exemplarily, the memory in the processor 310 can be a cache memory. The memory can save instructions or data that the processor 310 has just used or circulated. If the processor 310 needs to use the instruction or data again, it can be directly called from the memory. In this way, repeated access is avoided, the waiting time of the processor 310 is reduced, and the efficiency of the mobile phone 100 in processing data or executing instructions is improved.

[0062] In some embodiments, the processor 310 may include one or more interfaces. The interface 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.

[0063] The external memory interface 320 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external memory card communicates with the processor 310 through the external memory interface 320 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0064] The internal memory 321 can be used to store computer executable program codes, which include instructions. The internal memory 321 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the mobile phone 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 321 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 310 executes various functional applications and data processing of the mobile phone 100 by running instructions stored in the internal memory 321 and / or instructions stored in a memory provided in the processor.

[0065] The charging management module 340 is used to receive charging input from a charger. The charger may be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 340 may receive charging input from a wired charger through the USB interface 330. In some wireless charging embodiments, the charging management module 340 may receive wireless charging input through a wireless charging coil of the mobile phone 100. While the charging management module 340 is charging the battery 342, it may also power the mobile phone 100 through the power management module 341.

[0066] The power management module 341 is used to connect the battery 342, the charging management module 340 and the processor 310. The power management module 341 receives input from the battery 342 and / or the charging management module 340, and supplies power to the processor 310, the internal memory 321, the display screen 394, the camera component 393, and the wireless communication module 360. The power management module 341 can also be used to monitor parameters such as battery capacity, battery cycle number, battery health status (leakage, impedance), etc. In some other embodiments, the power management module 341 can also be set in the processor 310. In other embodiments, the power management module 341 and the charging management module 340 can also be set in the same device.

[0067] The wireless communication function of the mobile phone 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 350, the wireless communication module 360, the modem processor and the baseband processor.

[0068] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in mobile phone 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0069] The mobile communication module 350 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the mobile phone 100. The mobile communication module 350 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 350 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 350 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the processor 310. In some embodiments, at least some of the functional modules of the mobile communication module 350 can be set in the same device as at least some of the modules of the processor 310.

[0070] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 370A, a receiver 370B, etc.), or displays an image or video through a display screen 394. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 310 and be set in the same device as the mobile communication module 350 or other functional modules.

[0071] The wireless communication module 360 ​​can provide wireless communication solutions including nearfield communication (NFC), wireless local area networks (WLAN) (such as WiFi network), Bluetooth BT, global navigation satellite system (GNSS), frequency modulation (FM), infrared technology (IR), etc., which are applied to the mobile phone 100. The wireless communication module 360 ​​can be one or more devices integrating at least one communication processing module. The wireless communication module 360 ​​receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and filters it, and sends the processed signal to the processor 310. The wireless communication module 360 ​​can also receive the signal to be sent from the processor 310, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0072] In the embodiment of the present application, the NFC module included in the wireless communication module 360 ​​may also include an NFC controller (Near Field Communication Cntroller, NFCC), whose functions include modulation and demodulation of radio frequency signals and NFC protocol processing. The NFCC is connected to the radio frequency antenna (i.e., the NFC antenna) to realize the sending and receiving of NFC signals.

[0073] Optionally, in order to implement NFC payment, the mobile phone 100 may also include a security element (SE). SE is used to securely store sensitive information and provide a secure execution environment for transactions. It can be integrated in the processor 310, or located in the subscriber identification module (SIM) card of the mobile phone 100, or located in the secure digital memory card (SD) of the mobile phone, or it can be an independent chip. NFCC can be connected to SE.

[0074] In some embodiments, the antenna 1 of the mobile phone 100 is coupled to the mobile communication module 350, and the antenna 2 is coupled to the wireless communication module 360, so that the mobile phone 100 can communicate with the network and other devices through 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 technology. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS) and / or satellite based augmentation system (SBAS). The mobile phone 100 can establish a communication connection with other devices through the mobile communication module 350, and perform data transmission with other devices through the established communication connection.

[0075] The mobile phone 100 implements the display function through a GPU, a display screen 394, and an application processor. The GPU is a microprocessor for image processing, which is connected to the display screen 394 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs, which execute program instructions to generate or change display information. In an embodiment of the present application, the GPU can be used to convert and drive the display information required by the computer system, and provide a row scan signal to the display to control the correct display of the display.

[0076] The display screen 394 is used to display images, videos, etc. The display screen 394 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile phone 100 may include 1 or N display screens 394, where N is a positive integer greater than 1.

[0077] The mobile phone 100 can realize the shooting function through ISP, camera component 393, video codec, GPU, display screen 394 and application processor.

[0078] The mobile phone 100 can realize audio functions through the audio module 370, the speaker 370A, the receiver 370B, the microphone 370C and the application processor, such as music playing and recording. For the specific working principles and functions of the audio module 370, the speaker 370A, the receiver 370B and the microphone 370C, reference can be made to the introduction in the conventional technology.

[0079] The sensor module 380 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0080] The key 390 includes a power key, a volume key, etc. The key 390 may be a mechanical key or a touch key. The mobile phone 100 may receive key input and generate key signal input related to user settings and function control of the mobile phone 100.

[0081] Motor 391 can generate vibration prompts. Motor 391 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 394, motor 391 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0082] Indicator 392 may be an indicator light, which may be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0083] The camera 393 is used to shoot pictures, and the camera can be a wide-angle camera, a main camera, a macro camera, a telephoto camera, a time of flight (TOF) camera, etc.

[0084] The SIM card interface 395 is used to connect the SIM card. The SIM card can be connected to and separated from the mobile phone 100 by inserting it into the SIM card interface 395 or pulling it out from the SIM card interface 395. The mobile phone 100 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 395 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 395 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 395 can also be compatible with different types of SIM cards. The SIM card interface 395 can also be compatible with external memory cards. The mobile phone 100 interacts with the network through the SIM card to realize functions such as calls and data communications. In some embodiments, the mobile phone 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the mobile phone 100 and cannot be separated from the mobile phone 100.

[0085] It should be noted that Figure 3 The hardware modules included in the mobile phone 100 are only described for example, and do not limit the specific structure of the mobile phone 100. For example, the mobile phone 100 may also include other functional modules.

[0086] The following introduces the software system architecture of the first terminal and the second terminal. Exemplarily, the software system of the first terminal and the second terminal provided in the embodiment of the present application can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. For example, the software system can include but is not limited to (Symbian), (Android), (iOS), (Blackberry), Hongmeng (Harmony) and other operating systems, this application is not limited.

[0087] Please refer to Figure 4 , Figure 4 Layered architecture Taking the operating system as an example, the software structure block diagram of the first terminal and the second terminal in the embodiment of the present application is specifically introduced.

[0088] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. The operating system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system library, and kernel layer.

[0089] The application layer may include a series of application packages, including system applications and third-party applications, which may include video, camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, short message and other applications. For example, in the embodiment of the present application, the system application includes Huawei Wallet that supports NFC payment, and the third-party application includes wait.

[0090] The application framework layer provides application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. Figure 4 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. For example, in the embodiment of the present application, the application framework layer may provide a Huawei wallet in the system application of the application layer or a third-party application. Payment applications such as PayPal and PayPal provide setting capabilities, that is, setting these applications as foreground payment applications.

[0091] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0092] Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0093] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

[0094] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.), management of voice call function and video call function, etc.

[0095] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0096] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, an electronic device vibrates, an indicator light flashes, etc.

[0097] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for Scheduling and management of the system.

[0098] The core library consists of two parts: one is the function that the Java language needs to call, and the other is The core library.

[0099] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0100] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0101] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

[0102] The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0103] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0104] A 2D graphics engine is a drawing engine for 2D drawings.

[0105] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver. For example, the display driver can drive the display screen to display screen content. The camera driver can drive the camera to capture images. The audio driver is used to drive the audio player to play audio.

[0106] It should be noted that Figure 4 Only layered architecture The system is used as an example to introduce the software structure diagram of the first terminal or the second terminal. This application does not limit the specific architecture of the software system of the first terminal and the second terminal. For the specific introduction of software systems of other architectures, reference can be made to conventional technologies.

[0107] An embodiment of the present application provides an NFC payment method. In the method, after selecting one of multiple NFC payment applications as a first payment application, i.e., a system-default NFC payment application, and the remaining payment applications as second payment applications, i.e., non-system-default NFC payment applications, the second payment application activates a second payment card; the first payment application obtains a snapshot of the second payment card of the second payment application; in response to a user's operation of opening the NFC payment interface of the first payment application, the second payment card of the second payment application is displayed in the NFC payment interface; in response to a user's operation of selecting the second payment card of the second payment application, the first payment application displays the payment interface of the second payment application according to the snapshot of the second payment card of the second payment application; the second payment application interacts with a second terminal to complete the payment.

[0108] Through the above steps, when users want to change payment applications in different payment scenarios, they do not need to Figure 1 The first payment application and the second payment application are both located in Figure 4 The application layer shown in FIG. 1 and the user program framework in the application program framework layer can set the second payment application as the foreground payment application. The system architecture diagram is shown in FIG. Figure 5 shown.

[0109] It should be noted that setting the second payment application as the foreground payment application uses the foreground application priority (Prioritize currently running app) setting capability in the user program framework. In the NFC payment scenario, foreground application priority means that the payment application located on the current display interface is used as the preferred payment application. In an embodiment of the present application, when the user selects the second payment card of the second payment application in the first payment application, the second payment application is pulled up by the first payment application, is in a running state, and appears in the current display interface; at this time, the second payment application sends a message to the system to set the second payment application as the foreground payment application; the system's user program framework uses the foreground application priority setting capability to set the second payment application as the preferred payment application in the current payment scenario. The foreground payment application setting can be set by the program in the background, or an explicit setting switch can be provided for the user to choose. For example, in an NFC payment scenario, Figure 6 The NFC payment setting interface shown provides a foreground payment application setting switch for users to choose. Figure 1 Interface 103, Figure 6 In the interface 601, there is an additional "Settings" option under the "Default Payment Application" option. When the user selects the "Settings" option, the interface 602 is entered. In the interface 602, the user can choose to turn on "Foreground Application Priority". More specifically, Taking the system as an example, the user program framework can call CardEmulation.categoryAllowsForegroundPreference(CardEmulation.CATEGORY_PAYMENT) in the android.nfc.cardemulation package to enable "foreground application priority".

[0110] It should be understood that "foreground application priority" and "always use default payment application" are mutually exclusive, that is, after selecting "foreground application priority", the system will use the currently running program for NFC payment, and will not always use the default NFC payment application.

[0111] Figure 5 In the payment application, the first payment application can be a system-provided payment application that supports NFC payment, such as Huawei Wallet; it can also be a third-party payment application, such as The first payment application may be an application that supports NFC function and has the function of activating payment cards, such as It can also be an application that supports NFC function but does not have the function of opening payment cards, such as The first payment application can be set as the default payment application for NFC payment in the system, and can load the payment card snapshot of the second payment application. The payment card snapshot includes: payment card identifier ID, card face image, link to jump to card recharge interface, link to jump to card payment interface and other information.

[0112] The second payment application can be a system-provided payment application that supports NFC payment, such as Huawei Wallet; it can also be a third-party payment application, such as It should be noted that the second payment application is an application that supports the NFC function and has the ability to activate payment cards, so that after being launched by the first payment application, when it is set as the foreground payment application through the user program framework, payment cards can be used for normal payment. The second payment application can provide the first payment application with a payment card snapshot, and when launched by the first payment application, it sends a message to the user program framework to set itself as the foreground payment application.

[0113] The user program framework in the application framework layer may provide the ability to set each second payment application in the application layer as a foreground payment application.

[0114] Please refer to Figure 7(a), which takes a mobile phone as the first terminal of NFC payment as an example, which is a schematic diagram of the changes in the interface of the mobile phone with user operations in an NFC payment method provided in an embodiment of the present application.

[0115] In Figure 7(a), the first payment application is Huawei Wallet, which is the default payment application for NFC payment in the system; the second payment application is When the user uses the NFC payment function of Huawei Wallet, an interface 701 on the mobile phone 100 in FIG7(a) appears. It should be noted that Huawei Wallet, as a system-provided application that supports the NFC function, can itself activate payment cards. For example, the Huawei Wallet shown in FIG7(a) activates UnionPay International Bank Card 7010. Assume that the second payment application The payment application has opened a payment card, then The payment card will be displayed in the display interface of the first payment application, such as the China Bank card 7011 shown in the interface 701 of the first payment application Huawei Wallet in Figure 7 (a). Similarly, the second payment application The payment application has opened a payment card, then The payment card will be displayed in the display interface of the first payment application, such as the China Merchants Bank card 7012 shown in the interface 701 of the first payment application Huawei Wallet in Figure 7 (a). Similarly, assuming that the second payment application If the payment card is activated in the payment application, The payment card will be displayed in the display interface of the first payment application, such as the Nanjing transportation card 7013 shown in the interface 701 of the first payment application Huawei Wallet in Figure 7(a).

[0116] When the user selects a Chinese bank card for NFC payment, the interface of the mobile phone 100 changes to interface 702, and then displays Payment application interface. Interface 702 shows an activated payment card and prompts "Please place your mobile phone close to the POS machine to complete the card swipe."

[0117] When the mobile phone 100 is close to the POS terminal 200 (shown as process 703 in FIG. 7( a )), after payment is completed, the interface of the mobile phone 100 changes to interface 704 in FIG. 7( a ), displaying “Payment successful”.

[0118] Optionally, after successful payment, The payment page can be closed, and the mobile phone 100 will change to display as shown in interface 701, displaying the payment card of the first payment application and the payment card of the second payment application to the user.

[0119] Optionally, in After closing the payment page, mobile phone 100 can also exit the display interface of the current first payment application Huawei Wallet, which is not limited to this in the embodiment of the present application.

[0120] Alternatively, in the same case as the first payment application and the second payment application shown in FIG. 7(a), when the user selects a Chinese bank card for NFC payment but chooses to recharge due to insufficient balance on the Chinese bank card, see the scenario shown in FIG. 7(b). In FIG. 7(b), when the mobile phone 100 is close to the POS terminal 200 (shown as process 703 in FIG. 7(b)) for payment, the balance on the Chinese bank card is insufficient, and the interface is transformed into interface 705 in FIG. 7(b), which prompts "Insufficient balance! Payment failed!" and displays the current balance and recharge entry.

[0121] It should be noted that interface 705 is only an exemplary display of the prompt information of insufficient balance, the current balance and the recharge entrance. Interface 705 can also be displayed in the form of other pictures or texts, which is not limited in the embodiment of the present application. In addition, interface 705 can also include more or fewer display elements, which is not limited in the embodiment of the present application.

[0122] When the user chooses to recharge, the interface changes to interface 706 in FIG. 7( b), where the user can enter the recharge amount, select the bank card to be recharged, and click the "Recharge" option to complete the recharge. The rest of the bank cards with online payment capabilities can be transferred to the China Bank card shown on the interface 706, and other methods can be used for recharging, which is not limited in the embodiment of the present application. The interface 706 can also be presented in the form of other pictures or texts, and can also include more or fewer display elements, which is not limited in the embodiment of the present application.

[0123] When the user completes the recharge, the interface changes to interface 707, showing "Recharge successful".

[0124] After the recharge is successful, the interface may be changed to interface 702, and the user may bring the mobile phone 100 close to the POS terminal 200 again (as shown in process 703 in FIG. 7(b)) to complete the payment.

[0125] Optionally, in the same case as the first payment application and the second payment application shown in FIG. 7(a), when the user selects a Chinese bank card for NFC payment but changes the card for payment due to insufficient balance on the Chinese bank card, the scenario shown in FIG. 7(c) can be referred to. When the user uses the NFC payment function of Huawei Wallet, an interface as shown in interface 701 on the mobile phone 100 in FIG. 7(c) appears. In FIG. 7(c), when the mobile phone 100 approaches the POS terminal 200 (shown as process 703 in FIG. 7(c)) for payment, the balance of the Chinese bank card is insufficient, and the interface changes to interface 705 in FIG. 7(c), which prompts "Insufficient balance! Payment failed!" and displays the current balance and recharge entry. At this time, if the user does not choose to recharge the Chinese bank card but chooses to change the card for payment, such as selecting option 7050 in interface 705 to return to the previous interface, the interface changes to interface 701 of the first payment application Huawei Wallet. Then the user selects China Merchants Bank card 7012 in interface 701 for NFC payment, and the interface of the mobile phone 100 changes to interface 708, which displays Payment application interface. Interface 708 shows an activated payment card and prompts "Please place your mobile phone close to the POS machine to complete the card swipe."

[0126] It should be noted that the option 7050 for the user to select to return to the previous interface in FIG. 7(c) is only an exemplary display, and the option 7050 for returning to the previous interface can also be presented in the form of other images or texts, which is not limited in the embodiments of the present application. In addition, in FIG. 7(c), the interface 705 directly changes to the interface 701 in response to the user selecting to return to the previous interface; in another possible implementation, it can also first change to the interface 702 in response to the user selecting to return to the previous interface, and then change to the interface 701 after the user selects to enter the interface 701; or the interface 705 changes to a certain form of display interface in response to the user selecting to return to the previous interface, and then changes to the interface 701, which is not limited in the embodiments of the present application.

[0127] When the mobile phone 100 is close to the POS terminal 200 (shown as process 709 in FIG. 7( c )), after payment is completed, the interface of the mobile phone 100 may be transformed into the interface 7010 shown in FIG. 7( c ), displaying “Payment successful”.

[0128] Optionally, after successful payment, The payment page can be closed, and the mobile phone 100 will change to display as shown in interface 701, displaying the payment card of the first payment application and the payment card of the second payment application to the user.

[0129] Optionally, in After closing the payment page, mobile phone 100 can also exit the display interface of the current first payment application Huawei Wallet, which is not limited to this in the embodiment of the present application.

[0130] Optionally, applications that support NFC functionality but do not have the ability to activate payment cards, such as etc. can also be set as the first payment application, i.e. the default payment application. Available in Figure 1 The NFC payment setting interface 104 shown is set as the default payment application, but since it does not have the ability to activate payment cards, it is unable to display payment cards in the interfaces of these payment applications.

[0131] For example, please refer to FIG8(a), where a mobile phone is used as the first terminal for NFC payment. is the first payment application, and the second payment application is Schematic diagram of the interface changes as the user operates.

[0132] As shown in the interface 801 in FIG8(a), assuming that the second payment application The payment application has opened a payment card, then The payment card will be displayed in the display interface of the first payment application, such as the first payment application in FIG8(a). Similarly, assuming that the second payment application The payment application has opened a payment card, then The payment card will be displayed in the display interface of the first payment application, such as the first payment application in FIG8(a). Nanjing transportation card 8011 shown in interface 801.

[0133] When the user selects Nanjing Transportation Card for NFC payment, the interface of the mobile phone 100 changes to interface 802, and then displays Payment application interface. Interface 802 shows an activated payment card and prompts "Please place your mobile phone close to the POS machine to complete the card swipe."

[0134] When the mobile phone 100 approaches the POS terminal 200 (shown as process 803 in FIG. 8( a )), after payment is completed, the interface of the mobile phone 100 changes to interface 804 in FIG. 8( a ), displaying “Payment successful”.

[0135] Optionally, after successful payment, The payment page can be closed, and the mobile phone 100 will change to display as shown in interface 801, displaying the payment card of the first payment application and the payment card of the second payment application to the user.

[0136] Optionally, in After closing the payment page, the mobile phone 100 can also exit the current first payment application The display interface is not limited to this embodiment of the present application.

[0137] Optionally, when the NFC payment is completed, if When it is found that the balance of the payment card is insufficient, a schematic diagram of the interface changes with the user's operation can be seen in Figure 8(b).

[0138] As shown in the interface 805 of FIG8(b), the payment card Nanjing Transportation Card 8051 displays "Insufficient Balance" and displays the "Recharge" option. The insufficient balance of the payment card can be determined by the amount in the card being lower than a certain amount threshold. For example, It is mainly used for public transportation card swiping, etc. If the amount in the card is lower than the amount required for the longest round trip of the city bus, it can be judged that the balance of the payment card is insufficient. The embodiment of the present application does not limit the setting of the amount threshold.

[0139] When the user selects the recharge operation in interface 805, the interface may be changed to interface 806. The user may enter the recharge amount, select the bank card for recharging, and click the "Recharge" option to complete the recharge. In Figure 8(b), the recharge may be transferred from a bank card with online payment capabilities to the Nanjing Transportation Card shown in interface 806, or may be recharged in other ways, which is not limited in the present embodiment of the application. Interface 806 may also be presented in the form of other images or texts, and may also include more or fewer display elements, which is not limited in the present embodiment of the application.

[0140] After the recharge is successful, the interface is shown as interface 807, prompting "Recharge successful". Afterwards, optionally, the interface can be transformed into interface 801 shown in Figure 8(b), that is, the NFC payment interface of the first payment application Alipay.

[0141] The technical solution in this application is described in detail below in conjunction with specific embodiments. In the embodiment of this application, after selecting one of multiple NFC payment applications as the first payment application, that is, the system default NFC payment application, and the remaining payment applications as the second payment application, that is, the non-system default NFC payment payment application, the second payment application activates the second payment card; the first payment application obtains the second payment card snapshot of the second payment application; in response to the user's operation of opening the NFC payment interface of the first payment application, the second payment card of the second payment application is displayed in the NFC payment interface; in response to the user's operation of selecting the second payment card of the second payment application, the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application; the second payment application interacts with the second terminal to complete the payment. The embodiment of this application can avoid the cumbersome operation of users switching the default payment application in NFC payment, bringing convenience to users.

[0142] Please refer to Fig. 9 , Fig. 9 The flowchart of the NFC payment method provided by the embodiment of the present application is shown. The NFC payment method comprises the following steps:

[0143] S901. The second payment application activates the second payment card.

[0144] The second payment application is a payment application that is not the default NFC payment application of the system, and the payment card refers to a virtual card that has the ability to use NFC payment for payment transactions. For example, a physical bank card is bound to a virtual bank card generated in the terminal. A transportation card opened in China that can be used to pay for public transportation.

[0145] It should be noted that the second payment application is an application that supports the NFC function and has the function of activating a payment card.

[0146] Optionally, when the first payment application is also an application that supports the NFC function and has the function of activating a payment card, step S902 may also be executed.

[0147] S902: The first payment application activates the first payment card.

[0148] Optionally, after the first payment application activates the first payment card, in response to the user opening the NFC payment interface of the first payment application, the first payment card is displayed in the NFC payment interface.

[0149] Exemplarily, as shown in Figure 7(a), Huawei Wallet is the first payment application. As a system-provided application that supports NFC function, it can activate payment cards itself. For example, the Huawei Wallet shown in Figure 7(a) has activated the UnionPay International bank card, such as the UnionPay International bank card 7010 displayed on the interface 701.

[0150] In addition, the first payment application may also be an application that supports the NFC function but does not have the function of activating a payment card, such as Since it does not have the ability to activate a payment card, there is no need to execute step S902.

[0151] It should be noted that step S902 may be executed simultaneously with step S901, or may be executed before or after step S901, and this embodiment of the present application does not limit this.

[0152] S903: The first payment application obtains a snapshot of a second payment card of the second payment application.

[0153] The second payment card snapshot of the second payment application includes a link to jump to the second payment card payment interface. The second payment card snapshot may also include: a second payment card identifier ID, a card face image, a link to jump to the second payment card recharge interface, and other information.

[0154] Specifically, the first payment application may request to obtain the second payment card snapshot of the second payment application; and the second payment application sends the second payment card snapshot of the second payment application to the first payment application.

[0155] For example, assume that the first payment application is Huawei Wallet and the second payment application is The Bank of China has opened a payment card, namely the Bank of China card shown in interface 702 of FIG. 7(a). Then in step S903, Huawei Wallet can request to obtain Payment card snapshot of Chinese bank cards, Send a snapshot of your Chinese bank card to Huawei Wallet.

[0156] S904: In response to the user opening the NFC payment interface operation of the first payment application, the first payment application displays the second payment card of the second payment application in the NFC payment interface.

[0157] It should be noted that in step S903, the first payment application has obtained the second payment card snapshot of the second payment application, and can display the card face image and other information in the second payment card snapshot of the second payment application in step S904.

[0158] For example, when a user opens the NFC payment interface of the first payment application Huawei Wallet, as shown in the interface 701 of the mobile phone 100 in FIG7(a), in addition to displaying the payment card UnionPay International bank card of the first payment application Huawei Wallet, the card of the second payment application is also displayed, including Payment cards: Bank of China cards, Payment cards: China Merchants Bank card, Payment card: Nanjing Transportation Card.

[0159] Taking FIG8(a) as an example, as shown in the interface 801 of the mobile phone 100 in FIG8(a), the first payment application is Second payment application Payment cards Chinese bank cards, second payment applications The payment card Nanjing Transportation Card is displayed in the First Payment App NFC payment interface in China.

[0160] Optionally, after executing step S904, the first payment application may further execute steps S905 to S906:

[0161] S905: The first payment application obtains the status of the foreground payment application setting switch of the NFC payment setting of the first terminal.

[0162] Among them, the foreground payment application setting switch is used to control the opening or closing of the foreground application priority function, and the foreground application priority function is used to set the payment application located in the current display interface as the preferred payment application. For example, in the initial scenario, in the interface 701 of the mobile phone 100 shown in Figure 7(a), the first payment application Huawei Wallet is the foreground payment application. For another example, in the interface 702 of the mobile phone 100 shown in Figure 7(a), when the second payment application When running in the current display interface, It is the front-end payment application.

[0163] S906. If the foreground payment application setting switch is not turned on, the first payment application sets the foreground payment application setting switch to the on state.

[0164] It should be noted that the foreground payment application setting switch is set to on so that the foreground payment application can be switched when the foreground payment application changes in the next step. For example, in FIG7 (a), the interface 701 of the mobile phone 100 displays the NFC payment interface of the first payment application Huawei Wallet. At this time, the foreground payment application is Huawei Wallet by default; if the user chooses to pay with a Chinese bank card, the foreground payment application needs to be switched to If you want to switch the foreground payment application, you must first turn on the foreground payment application setting switch.

[0165] Specifically, turning on the foreground payment application setting switch is achieved by calling the foreground application priority setting capability in the user program framework. The foreground application priority means giving priority to the currently running program. In step S906, this capability can be called in the background. Taking the system as an example, the user program framework can call the CardEmulation.categoryAllowsForegroundPreference(CardEmulation.CATEGORY_PAYMENT) function in the android.nfc.cardemulation package to enable foreground application priority, that is, to enable the foreground payment application setting switch.

[0166] In addition, if the first payment application has explicitly turned on the foreground payment application setting switch before steps S905 to S906, there is no need to perform steps S905 to S906. Figure 6 As shown in interface 602, if the user chooses to turn on "foreground application priority" in the NFC payment setting interface 602, that is, turns on the foreground payment application setting switch, there is no need to execute steps S905 to S906.

[0167] S907. In response to the user selecting the second payment card of the second payment application, the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application.

[0168] More specifically, through steps S902 to S903, the first payment application obtains the second payment card snapshot of the second payment application, and the second payment card snapshot contains a link to jump to the second payment card payment interface. The first payment application displays the payment interface of the second payment application through the link to the second payment card payment interface carried in the second payment card snapshot of the second payment application.

[0169] It should be noted that when the second payment application is displayed, the second payment application will call the system registration interface to register the components related to the payment interface of the second payment application and the service capabilities for processing NFC instructions into the system; after receiving the registration information, the system will temporarily switch the system default payment application (i.e. the first payment application) to the second payment application registered this time.

[0170] Specifically, Taking the system as an example, you can jump to the second payment application through Intent. The sample code is as follows:

[0171] Intent launchIntent=new Intent(Intent.ACTION_VIEW);

[0172] launchIntent.setPackage("Link to the second payment card payment interface of the second payment application");

[0173] launchIntent.setData(Uri.parse("Entrance to the second payment card payment interface of the second payment application"));

[0174] The first payment application displays the payment interface of the second payment application based on the second payment card snapshot of the second payment application. The existing capabilities of the system are implemented through the above-mentioned Uri class. For specific details, please refer to conventional technologies.

[0175] When the second payment application is displayed, the second payment application will call CardEmulation.setPreferredService in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class. The basic application component in the system that users can interact with to complete a task; HostApduService is a convenient Service class that can be extended to facilitate The NFC card emulation mode is implemented in the component. After receiving the registration information, the system will temporarily switch the NFC route used to point to NFC payment to the second payment application registered this time. The NFC route is the path information that guides the forwarding of NFC messages. The route can confirm the path of forwarding IP messages. It should be understood that the registration process of the second payment application calls The existing capabilities of the system will not be described in detail in the embodiments of this application.

[0176] In the interface 701 of the mobile phone 100 as shown in FIG. 7( a ), when the user selects a Chinese bank card for NFC payment, the second payment application It will be displayed. The components related to its payment interface and the service capabilities for processing NFC instructions will be registered in the system; after receiving the registration information, the system will temporarily switch the default payment application from Huawei Wallet to the second payment application registered this time.

[0177] S908: The second payment application displays a payment interface.

[0178] Please refer to Figure 7(a), the interface 702 of the mobile phone 100 is the second payment application The payment interface shows an activated payment card and prompts "Please place your phone close to the POS machine to complete the card swipe."

[0179] As shown in the interface 802 in FIG. 8( a ), the second payment application is displayed. The payment interface.

[0180] Optionally, after executing step S908, the second payment application may further execute optional steps S909-S911:

[0181] S909: The second payment application interacts with the second terminal and displays a prompt message indicating insufficient balance.

[0182] Please refer to Figure 7(b). When the mobile phone 100 is close to the POS terminal 200 (shown as process 703 in Figure 7(b)) for payment, if the balance of the Bank of China card is insufficient, the interface will be transformed into interface 705 in Figure 7(b), displaying a prompt message of "Insufficient balance! Payment failed!" and displaying the current balance and recharge entry.

[0183] In a possible implementation, the prompt message indicating insufficient balance may include more, fewer, or different display elements from those of the interface 705 in FIG. 7( b ).

[0184] S910. In response to the user selecting a recharge operation, the second payment application displays a recharge interface of the second payment application.

[0185] Please refer to Figure 7(b), when the user selects recharge in interface 705, the interface changes to interface 706 in Figure 7(b). The user can enter the recharge amount, select the recharge bank card, and click the recharge option to complete the recharge.

[0186] In a possible implementation, recharge can be performed by transferring money from other payment cards with online payment capabilities activated in the second payment application to the currently displayed payment card, and recharge can also be performed by other methods, which is not limited in this embodiment of the present application.

[0187] In addition, the recharge interface of the second payment application may include more, fewer, or different display elements from the interface 706 in FIG. 7( b ), which is not limited in this embodiment of the present application.

[0188] S911. In response to the user completing the recharging operation, the second payment application displays an interface indicating that the recharging of the second payment application has been completed.

[0189] For example, as shown in FIG. 7( b ), when the user clicks the recharge option in interface 706 to successfully recharge, the interface changes to interface 707 , which prompts “Recharge successful”.

[0190] After the recharge is successful, the interface of the mobile phone 100 may be transformed into the interface 702 as shown in FIG. 7( b ) to facilitate the completion of the payment.

[0191] In some embodiments, after the second payment application interacts with the second terminal and displays a prompt message of insufficient balance to the user, the second payment application may, in response to the user's card change payment operation, return to displaying the NFC payment interface of the first payment application; in response to the user's operation of reselecting the second payment card of the second payment application, the first payment application displays the payment interface of the reselected second payment application based on a snapshot of the second payment card of the reselected second payment application.

[0192] Please refer to FIG. 7(c). When the mobile phone 100 is close to the POS terminal 200 (shown as process 703 in FIG. 7(c)) to make a payment, the balance of the Bank of China card is insufficient, and the interface 705 prompts "Insufficient balance! Payment failed!" and displays the current balance and the recharge entrance. At this time, the user can choose to change the card for payment, such as selecting option 7050 in the interface 705 to return to the previous interface, and the interface is changed to the interface 701 of the first payment application Huawei Wallet.

[0193] It should be noted that before the interface changes to the interface 701 of the first payment application Huawei Wallet, the secondary application needs to call the system deregistration interface in the background to register the registered second payment application The components related to the payment interface and the service capabilities for processing NFC instructions are deregistered from the system; after the system receives the deregistration information, the first payment application Huawei Wallet will be restored to the payment application currently performing NFC payment.

[0194] More specifically, the second payment application It will call CardEmulation.unsetPreferredService in the android.nfc.cardemulation package to de-inject Activity and de-register HostApduService implementation class. After receiving the de-registration information, the system will switch the NFC route used to point to NFC payment back to the first payment application, and make the first payment application Huawei Wallet call CardEmulation.setPreferredService in the android.nfc.cardemulation package to inject Activity and register HostApduService implementation class.

[0195] It should be noted that option 7050 for the user to select to return to the previous interface in Figure 7(c) is only an exemplary display. Option 7050 for returning to the previous interface can also be presented in the form of other pictures or texts, and the embodiment of the present application is not limited to this.

[0196] Then the user selects China Merchants Bank card 7012 in interface 701 to make NFC payment, and the interface of mobile phone 100 changes to interface 708, and displays Interface of payment application. Interface 708 shows an activated payment card and prompts "Please place your mobile phone close to the POS machine to complete the card swipe".

[0197] More specifically, with the interface 702 When displayed similarly, When the interface is displayed, CardEmulation.setPreferredService in the android.nfc.cardemulation package will be called to inject the Activity and register the HostApduService implementation class.

[0198] In addition, interface 705 in Figure 7(c) directly transforms into interface 701 in response to the user's selection operation; in another possible implementation, it can first transform into interface 702 in response to the user's selection operation and then transform into interface 701 through the user's selection operation; or interface 705 can first transform into a certain form of display interface in response to the user's selection operation and then transform into interface 701, and the embodiments of the present application are not limited to this.

[0199] S912: The second payment application interacts with the second terminal to complete the payment.

[0200] Optionally, from a user-visible perspective, the interaction between the second payment application and the second terminal includes the first terminal where the second payment application is located touching the second terminal. Specifically, the first terminal touching the second terminal means that the distance between the first terminal and the second terminal is within the communication distance specified by the NFC protocol, and the first terminal and the second terminal can perform NFC communication.

[0201] Although for the user, the first terminal touching the second terminal is just a simple action of "touching" and the duration is very short, the first terminal and the second terminal actually go through the NFC interaction process such as the first terminal and the second terminal establishing an NFC connection, radio frequency (RF) discovery, the first terminal receiving the payment instruction sent by the second terminal, and the first terminal responding to the payment instruction. For the NFC payment process, please refer to the prior art, and the embodiments of this application will not be repeated one by one.

[0202] Optionally, in a possible implementation, when the second payment application interacts with the second terminal, the second payment application may also prompt the user to perform identity authentication, and after successful identity authentication, use the second payment application to complete the NFC payment. The method of prompting the user to perform identity authentication includes: displaying fingerprint recognition area prompt information to prompt the user to perform fingerprint recognition in the fingerprint recognition area, and after successful fingerprint recognition, using the second payment application to perform NFC payment. It also includes: prompting the user to enter a password, prompting the user to enter a specific gesture, prompting the user to enter voice information, etc.

[0203] Optionally, whether the second payment application authenticates the user is determined by the second payment application based on the transaction amount. When the transaction amount is large and exceeds a certain amount, the user is prompted to authenticate. When the transaction amount is small and less than a certain amount, there is no need to prompt the user to authenticate. Of course, it is also possible to decide whether to require the user to authenticate based on information such as the time and location of the transaction. For example, the time range or location range of the user's usual transactions can be calculated in advance using methods such as big data analysis, and the time range is set as a safe time range, and the location range is set as a safe location range. If the current transaction time matches the safe time range; or the current location matches the safe location range, there is no need to require the user to authenticate. Otherwise, the user is prompted to authenticate.

[0204] Optionally, after the second payment application interacts with the second terminal and completes the NFC payment, the second payment application prompts the user that the NFC payment has been completed. The prompt method may be to display a prompt message and information such as the payment amount on the second payment application, and may be prompted in the form of a text message, or in other ways such as voice, vibration, etc. The embodiment of the present application does not limit the prompt method.

[0205] For example, as shown in FIG. 7( a ), the first terminal is a mobile phone 100 and the second terminal is a POS terminal. When the mobile phone 100 is close to the POS terminal 200 (shown as process 703 in FIG. 7( a )), the second payment application Interact with the POS terminal to complete the payment. The interface then changes to interface 704, displaying "Payment Successful".

[0206] For example, in FIG8(a), the first terminal is a mobile phone 100 and the second terminal is a POS terminal. When the mobile phone 100 is close to the POS terminal 200 (shown as process 803 in FIG8(a)), the second payment application Interact with the POS terminal to complete the payment. The interface then changes to interface 804, displaying "Payment Successful".

[0207] It should be noted that, from the user's visible perspective, the second payment application only displays "Payment successful" after the payment is successful, but the second payment application still needs to perform a series of operations in the background: the second payment application will call the system deregistration interface to deregister the payment interface-related components and service capabilities for processing NFC instructions of the second payment application registered in step S907 from the system; after the system receives the deregistration information, the first payment application will be restored to the payment application currently performing NFC payment.

[0208] More specifically, the second payment application calls CardEmulation.unsetPreferredService in the android.nfc.cardemulation package to de-inject the Activity and de-register the HostApduService implementation class. After receiving the de-registration information, the system switches the NFC route used to point to NFC payment back to the first payment application, and makes the first payment application call CardEmulation.setPreferredService in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class.

[0209] For example, in the scenario shown in FIG. 7( a), after the interface 704 is displayed, the second payment application Call the system deregistration interface in the background to register the registered The components related to the payment interface and the service capabilities for processing NFC instructions are deregistered from the system; after receiving the deregistration information, the system will restore the default payment application to Huawei Wallet.

[0210] For example, in the scenario shown in FIG8(a), after the interface 804 is displayed, the second payment application Close the payment interface and call the system deregistration interface in the background to deregister the registered The components related to the payment interface and the service capabilities for processing NFC instructions are deregistered from the system; after receiving the deregistration information, the system will restore the default payment application to Huawei Wallet.

[0211] Optionally, after the payment is completed, step S913 may be further performed:

[0212] S913: The second payment application closes the payment interface.

[0213] Optionally, after executing step S913, step S914 may also be executed:

[0214] S914: The first payment application displays the second payment card of the second payment application in the NFC payment interface.

[0215] Please refer to Figure 7(a), the second payment application After closing interface 704, the interface returns to the interface shown in 701. For example, as shown in FIG8(a), the second payment application After closing interface 804 , the interface returns to the interface shown in 801 .

[0216] Optionally, after executing step S913, the second payment application may further execute optional steps S1001-S1007:

[0217] S1001. The second payment application provides a message to the first payment application indicating that the balance of the second payment card is insufficient.

[0218] S1002. The first payment application receives a message indicating that the balance of the second payment card is insufficient, and displays the message indicating that the balance of the second payment card is insufficient in the NFC payment interface of the first payment application.

[0219] Please refer to the interface 805 of Figure 8(b), the second payment application Send a message to the first payment application that the payment card balance is insufficient The first payment application The Nanjing Transportation Card in its NFC payment interface shows “Insufficient Balance” and a “Recharge” option.

[0220] It should be noted that The insufficient balance of the payment card can be determined by the amount in the card being lower than a certain amount threshold. For example, It is mainly used for public transportation card swiping, etc. If the amount in the card is lower than the amount required for the longest round trip of the city bus, it can be judged that the balance of the payment card is insufficient. The embodiment of the present application does not limit the setting of the amount threshold.

[0221] S1003: In response to the user selecting to recharge the second payment card, the first payment application displays a recharge interface of the second payment application according to a snapshot of the second payment card.

[0222] It should be noted that, from the user's visible perspective, displaying the recharge interface of the second payment application only converts the interface into the recharge interface of the second payment application, but in fact the first payment application displays the recharge interface of the second payment application through the link to the second payment card recharge interface carried in the second payment card snapshot of the second payment application (obtained through steps S902 to S903).

[0223] Specifically, Taking the system as an example, you can jump to the recharge interface of the second payment application through Intent. The sample code is as follows:

[0224] Intent launchIntent=new Intent(Intent.ACTION_VIEW);

[0225] launchIntent.setPackage("Link to the second payment card recharge interface of the second payment application");

[0226] launchIntent.setData(Uri.parse("Entrance to the second payment card recharge interface of the second payment application"));

[0227] The first payment application displays the recharge interface of the second payment application based on the snapshot of the second payment card. The existing capabilities of the system are implemented through the above-mentioned Uri class. For specific details, please refer to conventional technologies.

[0228] When the second payment application is displayed, the second payment application will call CardEmulation.setPreferredService in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class. After receiving the registration information, the system will temporarily switch the NFC route used to point to the NFC payment to the second payment application registered this time. It should be understood that the registration process of the second payment application calls The existing capabilities of the system will not be described in detail in the embodiments of this application.

[0229] S1004. The second payment application displays a recharge interface.

[0230] For example, in the recharge interface shown in interface 806 in FIG8(b), the user can enter the recharge amount and click the "Recharge" option to complete the recharge. In FIG8(b), the recharge can be transferred from a bank card with online payment capabilities to the Nanjing Transportation Card shown in interface 806, and can also be recharged in other ways, which is not limited in the embodiment of the present application. Interface 806 can also be presented in the form of other pictures or texts, and can also include more or fewer display elements, which is not limited in the embodiment of the present application.

[0231] S1005. In response to the user completing the recharging operation in the recharging interface of the second payment application, the second payment application displays an interface indicating that the recharging of the second payment application has been completed.

[0232] As shown in interface 807 in FIG. 8( b ), the second payment application The interface 807 may also be displayed in the form of other images or texts, and may also include more or fewer display elements, which is not limited in the present embodiment.

[0233] It should be noted that, from the user's visible perspective, after the second payment application is recharged successfully, it only displays "Recharge successful", but the second payment application still needs to perform a series of operations in the background: the second payment application will call the system deregistration interface to deregister the payment interface-related components and service capabilities for processing NFC instructions of the second payment application registered in step S1003 from the system; after the system receives the deregistration information, the first payment application will be restored to the payment application currently performing NFC payment.

[0234] More specifically, the second payment application calls CardEmulation.unsetPreferredService in the android.nfc.cardemulation package to de-inject the Activity and de-register the HostApduService implementation class. After receiving the de-registration information, the system switches the NFC route used to point to NFC payment back to the first payment application, and makes the first payment application call CardEmulation.setPreferredService in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class.

[0235] Optionally, after executing step S1005, step S1006 may also be executed:

[0236] S1006. The second payment application closes the recharge completed interface of the second payment application.

[0237] Optionally, after executing step S1006, step S1007 may also be executed:

[0238] S1007: The first payment application displays the second payment card of the second payment application in the NFC payment interface.

[0239] For example, the second payment application in FIG8(b) After closing the recharge interface, the interface returns to interface 801. Payment cards are displayed in the

[0240] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements. It is understandable that each network element, such as the first terminal, the second terminal, the first payment application and the second payment application, etc., in order to realize the above functions, includes a hardware structure and / or software module corresponding to each function. It should be easy for those skilled in the art to realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0241] The embodiment of the present application can divide the functional modules of the first terminal, the second terminal, etc. according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0242] In the case of an integrated unit, Fig.11 A possible structural diagram of the first terminal involved in the above embodiment is shown. The first terminal 1100 includes: a processing module 1102, a communication module 1103 and a display module 1104. The display module 1104 is used to support the first terminal 1100 to display specific information, for example, the display module 1104 is used to support the first terminal 1100 to execute Fig. 9 In the processes S904, S908, S909, S910, S911 and S914, the display module 1104 is also used to support the first terminal 1100 to perform the following Fig.10 The processing module 1102 is used to control and manage the actions of the first terminal 1100. For example, the processing module 1102 is used to support the first terminal 1100 to perform Fig. 9 In the processes S901, S902, S903, S905, S906, S907, S912 and S913, Fig.10 The communication module 1103 is used to support the communication between the first payment application in the first terminal 1100 and the second payment application. For example, the communication module 1103 is used to support the first terminal to perform the following steps: Fig. 9 In process S907, Fig.10 The communication module 1103 is also used to support communication with other network entities, such as communication with the second terminal. The first terminal 1100 may also include a storage module 1101, which is used to store program codes and data of the first terminal.

[0243] Wherein, the processing module 1102 can be a processor or a controller, for example, a central processing unit (CPU), a general processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can implement or execute various exemplary logic boxes, modules and circuits described in conjunction with the disclosure of the present application. The processor can also be a combination that implements a computing function, for example, a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The communication module 1103 can be a transceiver, a transceiver circuit or a communication interface, and the like. The display module 1104 can be various types of displays, and the storage module 1101 can be a memory.

[0244] When the processing module 1102 is a processor, the communication module 1103 is a transceiver, the display module 1104 is a display, and the storage module 1101 is a memory, the first terminal involved in the embodiment of the present application can be Fig.12 The first terminal is shown.

[0245] See also Fig.12 As shown, the first terminal 1200 includes: a display 1201, one or more processors 1202, a transceiver 1203, a memory 1204 and a bus 1205. The transceiver 1203, the processor 1202 and the memory 1204 are interconnected via the bus 1205. The bus 1205 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.12 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0246] The steps of the method or algorithm described in conjunction with the disclosure of the present application can be implemented in a hardware manner, or can be implemented by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (Random Access Memory, RAM), a flash memory, a read-only memory (ReadOnly Memory, ROM), an erasable programmable read-only memory (Erasable Programmable ROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disk (CD-ROM) or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read information from the storage medium and can write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0247] Those skilled in the art should be aware that in one or more of the above examples, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of a computer program from one place to another. The storage medium can be any available medium that a general or special-purpose computer can access.

[0248] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of the present application in detail. It should be understood that the above description is only the specific implementation methods of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present application should be included in the scope of protection of the present application.

Claims

1. An NFC payment method, characterized in that: The method comprises: The second payment application activates a second payment card, wherein the second payment application is a payment application that is not a default NFC payment application of the system, and the payment card refers to a virtual card that has the ability to use NFC payment to conduct payment transactions; The first payment application obtains a second payment card snapshot of the second payment application, wherein the first payment application is set as a system default NFC payment application, and the second payment card snapshot includes a link to jump to a payment interface of the second payment card; In response to a user opening an NFC payment interface of the first payment application, displaying the second payment card of the second payment application in the NFC payment interface; In response to a user selecting the second payment card of the second payment application, the first payment application displays a payment interface of the second payment application according to a snapshot of the second payment card of the second payment application; The second payment application interacts with the second terminal to complete the payment.

2. The method according to claim 1, characterized in that The method further comprises: The first payment application activates a first payment card.

3. The method according to claim 2, characterized in that After the first payment application activates the first payment card, the method further includes: In response to the user opening the NFC payment interface of the first payment application, displaying the first payment card in the NFC payment interface.

4. The method according to claim 1, characterized in that: The first payment application obtains the second payment card snapshot of the second payment application, including: The first payment application sends a message to the second payment application requesting to obtain the second payment card snapshot of the second payment application; The second payment application sends the second payment card snapshot of the second payment application to the first payment application.

5. The method according to any one of claims 1 to 4, characterized in that Before the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application, the method further includes: The first payment application obtains the state of the foreground payment application setting switch of the NFC payment setting of the first terminal, wherein the foreground payment application setting switch is used to control the turning on or off of the foreground application priority function, and the foreground application priority function is used to use the payment application located on the current display interface as the preferred payment application; If the foreground payment application setting switch is not turned on, the first payment application sets the foreground payment application setting switch to an on state.

6. The method according to any one of claims 1 to 5, characterized in that After the first payment application displays the payment interface of the second payment application according to the second payment card snapshot of the second payment application, the method further includes: The second payment application interacts with the second terminal and displays a prompt message indicating insufficient balance; The second payment application displays a recharge interface of the second payment application in response to the user selecting a recharge operation; In response to the user completing the recharging operation in the recharging interface of the second payment application, the second payment application displays an interface indicating that the recharging has been completed.

7. The method according to claim 6, characterized in that After the second payment application displays an interface indicating that the recharge is completed, the method further includes: The second payment application displays the payment interface of the second payment application.

8. The method according to any one of claims 1 to 7, characterized in that After the second payment application interacts with the second terminal and the payment is completed, the method further includes: The second payment application closes the payment interface of the second payment application; The first payment application displays the second payment card in the NFC payment interface.

9. The method according to any one of claims 1 to 8, characterized in that After the second payment application interacts with the second terminal and the payment is completed, the method further includes: The second payment application provides the first payment application with a message that the balance of the second payment card is insufficient; The first payment application receives a message indicating that the balance of the second payment card is insufficient, and displays the information indicating that the balance of the second payment card is insufficient in the NFC payment interface of the first payment application.

10. The method according to claim 9, characterized in that The second payment card snapshot also includes a link to jump to a second payment card recharge interface, and the method further includes: In response to the user selecting to recharge the second payment card, the first payment application displays a recharge interface of the second payment application according to a snapshot of the second payment card; In response to the user completing the recharging operation in the recharging interface of the second payment application, the second payment application displays an interface indicating that the recharging of the second payment application has been completed.

11. The method according to claim 10, characterized in that After displaying the interface of the second payment application that the recharge is completed, the method further includes: The second payment application closes the recharge completed interface of the second payment application; The first payment application displays the second payment card in the NFC payment interface.

12. A first terminal, characterized in that: include: a memory for storing instructions executed by one or more processors of the first terminal; transceivers, used to receive or send radio signals; The processor, when executing the instructions in the memory, can enable the first terminal to execute the NFC payment method according to any one of claims 1 to 11.

13. A chip, characterized in that: The chip system includes a processing circuit and a storage medium, wherein the storage medium stores a computer program code; when the computer program code is executed by the processing circuit, the method according to any one of claims 1 to 11 is implemented.

14. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 11.