Payment method and terminal

By displaying and switching payment card snapshots in NFC payment applications and setting priority functions with the front-end payment application, the cumbersome problem of switching default payment applications during NFC payments is solved, and the convenience and efficiency of payment operations are improved.

WO2024244921A1PCT designated stage expired Publication Date: 2024-12-05HUAWEI TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091550
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-26
Filing Date
2024-05-08
Publication Date
2024-12-05

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 payment card snapshots of the second payment application in the first payment application, users are allowed to select different payment cards in one application and set priority functions through the front-end payment application, so that NFC can be completed without switching the default payment application without switching to the default payment application Pay.

Benefits of technology

It simplifies the process of users switching payment applications between different payment scenarios, improves the convenience and efficiency of payment operations, and reduces the complexity of user operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091550_05122024_PF_FP_ABST
    Figure CN2024091550_05122024_PF_FP_ABST
Patent Text Reader

Abstract

An NFC payment method and a terminal, relating to the technical field of terminals, and aiming to solve the problem in the prior art of complexity in the operation of switching a default payment application during NFC payment. The NFC payment method comprises: after one of a plurality of NFC payment applications is selected as a first payment application, i.e., a system default NFC payment application, and the remaining payment applications are each used as a second payment application, i.e., a non-system default NFC payment application, activating a second payment card in the second payment application; the first payment application acquiring a second payment card snapshot of the second payment application; in response to an operation of 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 an operation of the user selecting the second payment card of the second payment application, the first payment application displaying a payment interface of the second payment application according to the second payment card snapshot of the second payment application; and the second payment application interacting with a 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

Payment method and terminal Technical Field

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

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

[0003] Huawei Wallet, and Payment applications such as NFC are developed by terminal manufacturers in conjunction with 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 or debit cards, to the terminal to form a virtual bank card. The card organization can be China UnionPay, and the card issuer can be a state-owned bank such as the Bank of China, or 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 tapped against the card reader of an NFC point of sale (POS) machine. This action is also called "Tap," and payment can be completed by tapping the card. According to UnionPay, this is called "Quick Pay." It should be noted that virtual bank card data, including payment tokens and payment keys, are stored in the SE. The SE has a security storage capability no less than that of a physical bank card and is a reliable carrier for virtual bank cards. The virtual bank card generated by binding a physical bank card to a terminal is also called a payment card.

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

[0005] In existing technologies, various payment applications on terminals can rely on NFC payment capabilities to interact with POS terminals and gate machines to achieve corresponding transaction purposes. When users need to change payment applications for different payment scenarios, they can set the default payment application in the NFC function on the terminal device to the payment application they want.

[0006] For example, if the user initially sets the default payment application for NFC payment to "Huawei Wallet", and then the user wants to go through the subway gate, he wants to set the default payment application to Referring to Figure 1: the user needs to select "More Connections" on the settings interface 101 of the mobile phone 100 to open the "More Connections" interface shown in interface 102; then select the "NFC" option on interface 102 to switch to the interface shown in interface 103; select "Default Payment App" on interface 103 to enter the "Default Payment App" selection interface shown in interface 104. Finally, the user selects the "Default Payment App" on the "Default Payment App" interface shown in interface 104. As the default payment application for NFC payments, it is obvious that the user has to perform many operations in the process of setting up and switching the default payment application, which is too cumbersome.

[0007] Summary of the Invention

[0008] The embodiments of the present application provide a payment method and 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.

[0009] 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 that is not the system default NFC payment, and the payment card refers to a virtual card with 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 the second payment card payment interface; 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.

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

[0011] In a possible implementation of the first aspect, the method further includes: activating, by the first payment application, a first payment card.

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

[0013] In a possible implementation 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 on the NFC payment interface.

[0014] In a possible implementation of the first aspect, the first payment application obtaining the second payment card snapshot of the second payment application includes: the first payment application sending 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 sending the second payment card snapshot of the second payment application to the first payment application.

[0015] That is, the first payment application may proactively 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.

[0016] In a possible implementation of the first aspect, before 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, it also includes: the first payment application obtains the status 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.

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

[0018] In a possible implementation of the first aspect, after 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, it also includes: the second payment application interacts with the second terminal to display a prompt message of insufficient balance; the second payment application responds to the user selecting a recharge operation and displays the recharge interface of the second payment application; 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 the recharge is completed.

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

[0020] In a possible implementation manner of the first aspect, 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.

[0021] In a possible implementation of the first aspect, after the second payment application interacts with the second terminal and completes the payment, the method further includes: the second payment application closing the payment interface of the second payment application; and the first payment application displaying the second payment card in the NFC payment interface.

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

[0023] In a possible implementation of the first aspect, the second payment card snapshot further includes a link to a second payment card recharge interface. The method further includes: in response to a user selecting to recharge the second payment card, the first payment application displaying, by the first payment application, a recharge interface of the second payment application based on the second payment card snapshot; and in response to the user completing the recharge operation on the recharge interface of the second payment application, the second payment application displaying an interface indicating that the recharge has been completed by the second payment application.

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

[0025] In a possible implementation of the first aspect, after displaying the interface showing that the second payment application has completed recharging, the method further 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.

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

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

[0028] 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 is run 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

[0029] FIG1 is a schematic diagram of the process of selecting a default payment application in NFC payment in the prior art;

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

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

[0032] FIG3 is a schematic diagram of the structure of a mobile phone provided in an embodiment of the present application;

[0033] FIG4 is a software structure block diagram of a first terminal and a second terminal provided in an embodiment of the present application;

[0034] FIG5 is 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;

[0035] FIG6 is a schematic diagram of a foreground application priority setting interface provided by an embodiment of the present application;

[0036] FIG7( a ) is a process diagram 1 of an NFC payment method provided in an embodiment of the present application;

[0037] FIG7( b ) is a second process diagram of an NFC payment method provided in an embodiment of the present application;

[0038] FIG7( c ) is a third process diagram of an NFC payment method provided in an embodiment of the present application;

[0039] FIG8( a ) is a fourth process diagram of an NFC payment method provided in an embodiment of the present application;

[0040] FIG8( b ) is a fifth process diagram of an NFC payment method provided in an embodiment of the present application;

[0041] FIG9 is a flowchart of the NFC payment method according to an embodiment of the present application;

[0042] FIG10 is a second flow chart of the NFC payment method provided in an embodiment of the present application;

[0043] FIG11 is a first structural diagram of a first terminal provided in an embodiment of the present application;

[0044] FIG12 is a second structural diagram of the first terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying 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 merely a description of the association relationship of associated objects, indicating that three relationships can exist, 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.

[0046] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Therefore, 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.

[0047] Near Field Communication (NFC) is a short-range wireless connection technology based on Radio Frequency Identification (RFID) technology. NFC operates at a frequency of 13.56MHz±7kHz within a distance of 10 cm, with transmission speeds of 106Kbit / s, 212Kbit / s, or 424Kbit / s. Currently, NFC technology has become an international standard and is widely used. NFC technology uses radio frequency field induction to achieve short-range communication between NFC terminals. By touching or bringing two NFC terminals close together, they can quickly, securely, and contactlessly exchange information, content, and transactions.

[0048] Specifically, NFC terminals can operate in three modes: 1. Reader / Writer mode (R / W): In this mode, an NFC terminal functions as a contactless reader. For example, it can read information from an NFC tag on a poster or exhibit. In this mode, an NFC terminal with read / write capabilities can collect data from the NFC tag and then process it. Typical scenarios based on this mode include reading electronic advertisements and selling tickets for buses and cinemas. For example, a user can hold an NFC-enabled terminal close to a movie poster with an NFC tag to obtain detailed information about the movie. Reader mode can also be used for simple data acquisition, such as obtaining bus stop information or park maps. 2. Peer-to-Peer mode (P2P): In this mode, two NFC terminals can quickly establish a connection, enabling point-to-point data transmission. Using this mode, multiple NFC-enabled digital cameras, tablets, and mobile phones can wirelessly connect and exchange data. Typical application scenarios based on this mode include quickly establishing Bluetooth connections and exchanging contact information. 3. Card Emulation (CE) mode: This mode 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 exchange data with the NFC reader. This mode is mainly used in contactless mobile payment scenarios such as stores and transportation. The user only needs to bring the NFC terminal close to the NFC reader and enter a 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 and access control.

[0049] In card emulation mode, current NFC terminals can simultaneously support three types of emulated cards. These cards are RFID cards simulated by mobile devices 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.

[0050] Taking a mobile phone as an example, currently, when a payment app provided by a bank or other financial institution is installed on the phone, the phone can operate in card emulation mode to complete payments. That is, by downloading and installing the payment app on the phone and binding it to a physical card, the phone can achieve card emulation, replacing the traditional physical integrated circuit (IC) card and completing payments directly using the phone.

[0051] However, when users need to switch the default payment application in different NFC payment scenarios, they need to go through a lot of setting steps as shown in Figure 1, which seriously reduces the intelligent interaction capability between the terminal device and the user, makes the terminal device inefficient, and brings inconvenience to the user.

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

[0053] The NFC payment method provided in the embodiments of this application is applied to payment scenarios between two different NFC-enabled terminals. For ease of description, the two different NFC-enabled terminals are referred to as the first terminal and the second terminal in this embodiment. The first terminal can be a mobile phone, tablet computer, laptop computer, ultra-mobile personal computer, netbook, personal digital assistant, wearable device, etc. The second terminal can also be a mobile phone, tablet computer, laptop computer, wearable device, POS terminal, etc.

[0054] For example, 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 .

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

[0056] The first terminal and the second terminal referred to in the embodiment of the present application both support NFC functions. 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 it may be called a 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, which mainly refers to an application provided by a payment service provider with an online card binding function (it is understandable 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.

[0057] It should be noted that the third-party payment application described in the embodiment of the present application generally supports users to set it as the default payment application for NFC payment, as shown in the interface 104 in FIG1 etc. Some of these third-party applications, such as Able to activate payment cards and make successful payments 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 payments by calling the NFC payment capability of other payment applications.

[0058] Taking the first terminal and the second terminal as an example, as shown in FIG3 , the mobile phone 100 includes:

[0059] 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 jack 370D, sensor module 380, button 390, motor 391, indicator 392, camera 393, display screen 394, and subscriber identification module (SIM) card interface 395, etc.

[0060] It should be understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on mobile phones. In other embodiments of the present application, the mobile phone may include more or fewer components than shown in the figure, or some components may be combined or separated, or the components may be arranged differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0061] 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 processing unit (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). The different processing units may be independent devices or integrated into one or more processors.

[0062] In some embodiments, the mobile phone 100 may also include one or more processors 310. The controller may generate an operation control signal based on the instruction opcode and timing signal to control instruction fetching and execution. In other embodiments, the processor 310 may also be provided with a memory for storing instructions and data. For example, the memory in the processor 310 may be a cache memory. This memory may store instructions or data that have just been used or are being recycled by the processor 310. If the processor 310 needs to use the instruction or data again, it may directly call it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 310, and thereby improves the efficiency of the mobile phone 100 in processing data or executing instructions.

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

[0064] 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 data storage functions. For example, files such as music and videos can be stored on the external memory card.

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

[0066] The charging management module 340 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 340 can receive charging input from the wired charger via the USB interface 330. In some wireless charging embodiments, the charging management module 340 can receive wireless charging input via the wireless charging coil of the mobile phone 100. While charging the battery 342, the charging management module 340 can also provide power to the mobile phone 100 via the power management module 341.

[0067] 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 provides power to the processor 310, the internal memory 321, the display 394, the camera assembly 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 count, and battery health status (leakage, impedance). In some other embodiments, the power management module 341 can also be provided in the processor 310. In other embodiments, the power management module 341 and the charging management module 340 can also be provided in the same device.

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

[0069] 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 antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

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

[0071] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted 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 being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 370A, the receiver 370B, etc.) or displays an image or video through the 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 provided in the same device as the mobile communication module 350 or other functional modules.

[0072] The wireless communication module 360 ​​can provide wireless communication solutions including near field communication (NFC), wireless local area networks (WLAN) (such as WiFi networks), Bluetooth BT, global navigation satellite system (GNSS), frequency modulation (FM), infrared technology (IR), etc. applied on 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 310. The wireless communication module 360 ​​can also receive the signal to be sent from the processor 310, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0073] In the embodiment of the present application, the NFC module included in the wireless communication module 360 ​​may also include an NFC controller (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 transmit and receive NFC signals.

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

[0075] 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 technologies. The wireless communication technologies 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 the other devices through the established communication connection.

[0076] The mobile phone 100 implements display functions through a GPU, display screen 394, and an application processor. The GPU is a microprocessor for image processing that connects 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 that execute program instructions to generate or change display information. In embodiments of the present application, the GPU can be used to convert and drive the display information required by the computer system and provide row scan signals to the display to control the correct display of the display.

[0077] Display screen 394 is used to display images, videos, and the like. 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 (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, mobile phone 100 may include one or N display screens 394, where N is a positive integer greater than one.

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

[0079] The mobile phone 100 can implement audio functions such as music playback and recording through the audio module 370, speaker 370A, receiver 370B, microphone 370C, and application processor. For the specific operating principles and functions of the audio module 370, speaker 370A, receiver 370B, and microphone 370C, please refer to the description in conventional technology.

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

[0081] Keys 390 include a power button, a volume button, etc. Keys 390 may be mechanical keys or touch keys. Mobile phone 100 may receive key inputs and generate key signal inputs related to user settings and function control of mobile phone 100.

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

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

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

[0085] The SIM card interface 395 is used to connect a SIM card. The SIM card can be connected to and disconnected from the mobile phone 100 by inserting it into or removing it from the SIM card interface 395. The mobile phone 100 can support one or N SIM card interfaces, where N is a positive integer greater than one. The SIM card interface 395 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. 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 implement 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.

[0086] It should be noted that the hardware modules included in the mobile phone 100 shown in FIG3 are merely exemplary descriptions and do not limit the specific structure of the mobile phone 100. For example, the mobile phone 100 may also include other functional modules.

[0087] The following describes the software system architecture of the first terminal and the second terminal. For example, 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 may include but is not limited to This application does not limit the operating system to Harmony.

[0088] Please refer to Figure 4, Figure 4 shows a 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.

[0089] 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. In some embodiments, 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.

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

[0091] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions. As shown in Figure 4, 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 window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc. to the system application in the application layer or the third-party application. Payment applications such as PayPal and PayPal provide setting capabilities, that is, setting these applications as foreground payment applications.

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

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

[0094] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0095] 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 functions and video call functions, etc.

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

[0097] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0098] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for System scheduling and management.

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

[0100] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0101] The system library can 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.

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

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

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

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

[0106] The kernel layer is the layer between hardware and software. It includes at least the display driver, camera driver, audio driver, and sensor driver. For example, the display driver drives the display screen to display content. The camera driver drives the camera to capture images. The audio driver drives the audio player to play audio.

[0107] It should be noted that Figure 4 only shows the layered architecture. 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.

[0108] An embodiment of the present application provides an NFC payment method. In this method, after selecting one of multiple NFC payment applications as a first payment application, that is, a system-default NFC payment application, and the remaining payment applications as second payment applications, that is, 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.

[0109] Through the above steps, when users need to change payment applications in different payment scenarios, they no longer need to perform the tedious settings switching operation as shown in Figure 1. The first payment application and the second payment application are both located in the application layer shown in Figure 4. The user program framework in the application framework layer can set the second payment application as the foreground payment application. The system architecture diagram is shown in Figure 5.

[0110] It should be noted that setting the second payment application as the foreground payment application utilizes the "Prioritize currently running app" setting capability in the user application framework. In the NFC payment scenario, "foreground application priority" means that the payment application currently displayed is designated as the primary payment application. In this embodiment of the present application, when a user selects a second payment card in the second payment application within the first payment application, the second payment application is launched by the first payment application, enters a running state, and appears on the current display interface. At this point, 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 application framework uses the "foreground application priority" setting capability to set the second payment application as the primary payment application for the current payment scenario. The foreground payment application setting can be set by the application in the background, or an explicit setting switch can be provided for the user to select. For example, in the NFC payment scenario, a foreground payment application setting switch can be provided for the user to select within the NFC payment settings interface shown in FIG6 . Compared to interface 103 in FIG1 , interface 601 in FIG6 includes a "Set" option under the "Default payment application" option. Selecting "Set" brings the user to interface 602. In 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".

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

[0112] In Figure 5, 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 can be an application that supports NFC function and has a payment card enabled, such as It can also be an application that supports NFC function but does not have the ability to activate payment cards, such as The first payment app can be set as the default payment app for NFC payments in the system and can load the payment card snapshot of the second payment app. The payment card snapshot includes information such as the payment card identifier ID, card image, link to the card top-up interface, and link to the card payment interface.

[0113] The second payment application can be a system-built payment application that supports NFC payment, such as Huawei Wallet; or a third-party payment application, such as It should be noted that the second payment app supports NFC and has payment card activation enabled. This allows it to be used for payment when launched by the first payment app and set as the foreground payment app by the user application framework. The second payment app can provide the first payment app with a payment card snapshot and, when launched by the first payment app, send a message to the user application framework to set itself as the foreground payment app.

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

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

[0116] 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 NFC function, can activate payment cards. For example, the Huawei Wallet shown in FIG7(a) has activated 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).

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

[0118] When the mobile phone 100 is brought 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”.

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

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

[0121] Alternatively, in the same scenario as the first and second payment applications shown in FIG7(a), if the user selects a Bank of China card for NFC payment but chooses to top up due to insufficient balance on the Bank of China card, see the scenario shown in FIG7(b). In FIG7(b), when the mobile phone 100 is brought close to the POS terminal 200 (shown as process 703 in FIG7(b)) to make a payment, the Bank of China card balance is insufficient, and the interface changes to interface 705 in FIG7(b), which displays "Insufficient balance! Payment failed!" and displays the current balance and a top-up entry.

[0122] It should be noted that interface 705 is merely an example of displaying the insufficient balance prompt, the current balance, and the recharge entry. Interface 705 may also be displayed in other graphic or text forms, and this embodiment of the application is not limited thereto. In addition, interface 705 may also include more or fewer display elements, and this embodiment of the application is not limited thereto.

[0123] When the user chooses to recharge, the interface changes to the interface 706 shown in Figure 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. Other bank cards with online payment capabilities can be transferred to the Bank of China card shown on interface 706, and other methods can also be used to top up the account, which is not limited in this embodiment of the application. Interface 706 can also be presented in other graphic or text forms, and can include more or fewer display elements, which is not limited in this embodiment of the application.

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

[0125] 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 by process 703 in FIG. 7( b )) to complete the payment.

[0126] Alternatively, in the same situation as the first and second payment applications shown in FIG7(a), if the user selects a Bank of China card for NFC payment but switches to a different card due to insufficient balance on the Bank of China card, the scenario shown in FIG7(c) may be referred to. When the user uses the NFC payment function of Huawei Wallet, an interface 701 on the mobile phone 100 in FIG7(c) appears. In FIG7(c), when the mobile phone 100 approaches the POS terminal 200 (shown as process 703 in FIG7(c)) to make a payment, the Bank of China card balance is insufficient, and the interface changes to interface 705 in FIG7(c), which prompts "Insufficient balance! Payment failed!" and displays the current balance and the recharge entry. If the user does not choose to recharge the Bank of China card but instead chooses to switch to a different card, 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. The user then 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 displays an activated payment card and prompts "Please hold your phone close to the POS machine to complete the card swipe."

[0127] It should be noted that the option 7050 for the user to select to return to the previous interface in FIG7 (c) is merely an exemplary display. The option 7050 for returning to the previous interface can also be presented in other graphic or text forms, and the present embodiment does not limit this. In addition, the interface 705 in FIG7 (c) directly changes to the interface 701 in response to the user selecting to return to the previous interface; in another possible implementation, the interface 705 can 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, and the present embodiment does not limit this.

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

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

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

[0131] 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, that is, the default payment application. It can be set as the default payment application in the NFC payment setting interface 104 shown in FIG1 , but since it does not have the ability to activate payment cards, it cannot display payment cards in the interfaces of these payment applications.

[0132] For example, please refer to Figure 8(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.

[0133] 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, as shown in the first payment application in Figure 8(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, as shown in the first payment application in Figure 8(a) Nanjing transportation card 8011 shown in interface 801.

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

[0135] When the mobile phone 100 is brought close to 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”.

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

[0137] 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 in this embodiment of the present application.

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

[0139] 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 bus card swiping and other purposes. If the amount on the card is lower than the amount required for the longest round trip of the city bus, it can be judged that the payment card balance is insufficient. The embodiment of the present application does not limit the setting of the amount threshold.

[0140] When the user selects the recharge operation in interface 805, the interface may change to interface 806. The user can 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 can be transferred from a bank card with online payment capabilities to the Nanjing Transportation Card shown in interface 806. Recharge can also be performed by other methods, which are not limited in this embodiment of the application. Interface 806 can also be presented in the form of other images or text, and can also include more or fewer display elements, which are not limited in this embodiment of the application.

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

[0142] The technical solution in this application is described in detail below with reference to specific embodiments. In the embodiment of this application, after selecting one of multiple NFC payment applications as the first payment application, i.e., the system default NFC payment application, and the remaining payment applications as the second payment application, i.e., the non-system default NFC payment application, the second payment application activates the second payment card; the first payment application obtains a snapshot of the second payment card 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 snapshot of the second payment card 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 tedious operation of users switching the default payment application in NFC payment, bringing convenience to users.

[0143] Please refer to Figure 9, which shows a flow chart of the NFC payment method provided by an embodiment of the present application. The NFC payment method includes the following steps:

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

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

[0146] It should be noted that the second payment application is an application that supports NFC function and has an activated payment card.

[0147] Optionally, when the first payment application also supports the NFC function and is an application capable of activating a payment card, step S902 may also be performed.

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

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

[0150] For example, as shown in Figure 7(a), Huawei Wallet is the first payment application. As an application that supports NFC function and comes with the system, it can activate payment cards. 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.

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

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

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

[0154] The second payment card snapshot of the second payment application includes a link to the payment interface of the second payment card. The second payment card snapshot may also include information such as the second payment card identifier, a card image, and a link to the recharge interface of the second payment card.

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

[0156] For example, assuming 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 the interface 702 of Figure 7(a). Then in step S903, Huawei Wallet can request to obtain A snapshot of payment cards from Chinese banks. Send a snapshot of your Chinese bank card to Huawei Wallet.

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

[0158] 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 image and other information in the second payment card snapshot of the second payment application in step S904.

[0159] 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, The payment card is Nanjing Transportation Card.

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

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

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

[0163] 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 make the payment application located on the current display interface 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.

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

[0165] It should be noted that the foreground payment application setting switch is set to on so that when the foreground payment application changes in the next step, the foreground payment application can be switched. For example, in Figure 7(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.

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

[0167] In addition, if the first payment application has explicitly turned on the foreground payment application setting switch before steps S905 to S906, then steps S905 to S906 do not need to be performed again. As shown in interface 602 of Figure 6, if the user selects "Foreground application priority" in the NFC payment setting interface 602, that is, the foreground payment application setting switch is turned on, then steps S905 to S906 do not need to be performed again.

[0168] 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 snapshot of the second payment card of the second payment application.

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

[0170] 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 capability of 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.

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

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

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

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

[0175] 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 system's existing capabilities are implemented through the above-mentioned Uri class. For specific details, please refer to conventional technologies.

[0176] 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 use to interact in order to complete a task; HostApduService is a convenient Service class that can be extended to facilitate NFC card emulation mode is implemented in the component. After receiving the registration information, the system will temporarily switch the NFC routing used to point to NFC payment to the second payment application registered this time. The NFC routing is the path information that guides the forwarding of NFC messages. The routing can confirm the path of the forwarded IP message. 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.

[0177] As shown in the interface 701 of the mobile phone 100 in FIG7 (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.

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

[0179] 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 hold your phone close to the POS machine to complete the card swipe."

[0180] As shown in the interface 802 in Figure 8(a), the second payment application is displayed payment interface.

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

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

[0183] 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)) to make a payment, if the balance of the Bank of China card is insufficient, the interface will change to interface 705 in Figure 7(b), displaying the prompt message "Insufficient balance! Payment not successful!" and displaying the current balance and recharge entry.

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

[0185] S910. The second payment application displays a recharge interface of the second payment application in response to the user selecting a recharge operation.

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

[0187] In one 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, or by other methods, which are not limited in this embodiment of the present application.

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

[0189] S911. In response to the user completing the recharge operation, the second payment application displays an interface indicating that the second payment application has completed the recharge.

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

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

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

[0193] Referring to Figure 7(c), when mobile phone 100 is brought close to POS terminal 200 (shown as process 703 in Figure 7(c)), the balance on the Bank of China card is insufficient. Interface 705 displays the message "Insufficient Balance! Payment Unsuccessful!" and displays the current balance and a recharge entry. The user can then choose to switch cards, for example by selecting option 7050 in interface 705 to return to the previous interface. This changes the interface to interface 701 of the primary payment application, Huawei Wallet.

[0194] 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 payments.

[0195] More specifically, the second payment application The system will call the CardEmulation.unsetPreferredService method in the android.nfc.cardemulation package to de-inject the Activity and unregister the HostApduService implementation class. After receiving the de-registration information, the system will switch the NFC route used for NFC payment back to the primary payment app and instruct the primary payment app, Huawei Wallet, to call the CardEmulation.setPreferredService method in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class.

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

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

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

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

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

[0201] 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 are capable of NFC communication.

[0202] Although for the user, the first terminal touching the second terminal is just a simple "touch" action and the duration is very short, the NFC interaction process between the first and second terminals actually goes through the first and second terminals, including 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 existing technology and will not be detailed in this embodiment.

[0203] Optionally, in one possible implementation, when the second payment application interacts with the second terminal, the second payment application may prompt the user to authenticate their identity. Upon successful authentication, the user completes the NFC payment using the second payment application. Methods for prompting the user to authenticate their identity include: displaying a fingerprint recognition area prompt to prompt the user to perform fingerprint authentication in the fingerprint recognition area; upon successful fingerprint authentication, using the second payment application to perform the NFC payment. Other methods include prompting the user to enter a password, prompting the user to enter a specific gesture, prompting the user to enter a voice message, etc.

[0204] Optionally, whether the second payment application authenticates the user is determined by the second payment application based on the transaction amount. If the transaction amount is large, exceeding a certain limit, the user will be prompted to authenticate. If the transaction amount is small, below a certain limit, the user does not need to be prompted for authentication. Of course, the decision to require user authentication may also be based on information such as the time and location of the transaction. For example, big data analysis or other methods can be used to pre-calculate the user's typical transaction time range or location range, and this time range and location range can be set as a safe time range and a safe location range. If the current transaction time matches the safe time range, or the current location matches the safe location range, the user does not need to authenticate. Otherwise, the user is prompted for authentication.

[0205] Optionally, after the second payment application interacts with the second terminal and completes the NFC payment, the second payment application notifies the user that the NFC payment has been completed. This notification may be displayed on the second payment application along with information such as the payment amount, via text message, voice, vibration, or other means. This embodiment of the present application does not limit the notification method.

[0206] For example, as shown in FIG7 (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 FIG7 (a)), the second payment application After interacting with the POS terminal and completing the payment, the interface changes to interface 704, displaying "Payment Successful".

[0207] 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 After interacting with the POS terminal and completing the payment, the interface changes to interface 804, displaying "Payment Successful".

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

[0209] More specifically, the second payment app calls the CardEmulation.unsetPreferredService method in the android.nfc.cardemulation package to de-inject the Activity and unregister the HostApduService implementation class. Upon receiving the de-registration information, the system switches the NFC route used for NFC payment back to the first payment app and instructs the first payment app to call the CardEmulation.setPreferredService method in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class.

[0210] For example, in the scenario shown in FIG7(a), after the interface 704 is displayed, the second payment application 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] 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.

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

[0213] S913. The second payment application closes the payment interface.

[0214] Optionally, after executing step S913, step S914 may be further executed:

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

[0216] See 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 Figure 8(a), the second payment application After closing interface 804 , the interface returns to the interface shown in 801 .

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

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

[0219] S1002. The first payment application receives a message indicating insufficient balance on the second payment card, and displays the message indicating insufficient balance on the second payment card on the NFC payment interface of the first payment application.

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

[0221] 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 bus card swiping and other purposes. If the amount on the card is lower than the amount required for the longest round trip of the city bus, it can be judged that the payment card balance is insufficient. The embodiment of the present application does not limit the setting of the amount threshold.

[0222] 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 based on a snapshot of the second payment card.

[0223] It should be noted that, from the user's visible perspective, displaying the recharge interface of the second payment application is merely converting 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).

[0224] 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:

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

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

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

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

[0229] 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 the system receives the registration information, it 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.

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

[0231] For example, as shown in the recharge interface shown in interface 806 in Figure 8(b), the user can enter the recharge amount and click the "Recharge" option to complete the recharge. In Figure 8(b), the recharge can be transferred from a bank card with online payment capabilities to the Nanjing Transportation Card shown in interface 806. Recharge can also be performed by other methods, which are not limited in this embodiment of the application. Interface 806 can also be presented in other graphic or text forms, and can also include more or fewer display elements, which are not limited in this embodiment of the application.

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

[0233] As shown in the interface 807 in FIG8(b), the second payment application Display "Recharge successful!" Interface 807 can also be displayed in other graphic or text forms, and can also include more or fewer display elements, which is not limited in this embodiment of the present application.

[0234] It should be noted that, from the user's visible perspective, after the second payment application is successfully recharged, 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.

[0235] More specifically, the second payment app calls the CardEmulation.unsetPreferredService method in the android.nfc.cardemulation package to de-inject the Activity and unregister the HostApduService implementation class. Upon receiving the de-registration information, the system switches the NFC route used for NFC payment back to the first payment app and instructs the first payment app to call the CardEmulation.setPreferredService method in the android.nfc.cardemulation package to inject the Activity and register the HostApduService implementation class.

[0236] Optionally, after executing step S1005, step S1006 may be further executed:

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

[0238] Optionally, after executing step S1006, step S1007 may be further executed:

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

[0240] 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

[0241] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It can be understood that in order to realize the above functions, each network element, such as the first terminal, the second terminal, the first payment application and the second payment application, includes a hardware structure and / or software module corresponding to the execution of 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 document, 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 a hardware or computer software driven hardware manner 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 be beyond the scope of this application.

[0242] In the embodiment of the present application, the functional modules of the first terminal, the second terminal, etc. can be divided according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules 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 functional division. In actual implementation, there may be other division methods.

[0243] In the case of an integrated unit, FIG11 shows a possible schematic diagram of the structure of the first terminal involved in the above embodiment. 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 in displaying specific information. For example, the display module 1104 is used to support the first terminal 1100 in executing processes S904, S908, S909, S910, S911, and S914 in FIG9. The display module 1104 is also used to support the first terminal 1100 in executing processes S1002, S1004, S1005, and S1007 in FIG10. Processing module 1102 is used to control and manage the actions of first terminal 1100. For example, processing module 1102 is used to support first terminal 1100 in executing processes S901, S902, S903, S905, S906, S907, S912, and S913 in Figure 9, processes S1003 and S1006 in Figure 10, and / or other processes used in the techniques described herein. Communication module 1103 is used to support communication between a first payment application and a second payment application in first terminal 1100. For example, communication module 1103 is used to support the first terminal in executing process S907 in Figure 9 and process S1001 in Figure 10. Communication module 1103 is also used to support communication with other network entities, such as communication with a second terminal. First terminal 1100 may also include a storage module 1101 for storing program code and data for the first terminal.

[0244] Among them, the processing module 1102 can be a processor or controller, for example, a central processing unit (CPU), a general-purpose 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 the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, 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.

[0245] 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 may be the first terminal shown in FIG. 12 .

[0246] As shown in Figure 12 , 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, for example. The bus can be categorized as an address bus, a data bus, a control bus, etc. For ease of illustration, Figure 12 shows only one thick line, but this does not imply that there is only one bus or only one type of bus.

[0247] 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 (RAM), a flash memory, a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a register, a hard disk, a mobile hard disk, a read-only compact disc (CD-ROM) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the 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 an integral part of the processor. The processor and the storage medium can be located in an ASIC.

[0248] Those skilled in the art will appreciate that, in one or more of the examples above, the functions described herein may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions may 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 medium that facilitates the transmission of a computer program from one place to another. The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0249] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this 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.

Citation Information

Patent Citations

  • Mode setting method and apparatus

    CN104933555A

  • Non-contact payment method, device and system

    CN105631664A

  • Near field communication (NFC) mobile payment method and apparatus, and NFC mobile payment terminal

    CN105897749A

  • Method and device for switching payment

    CN106170808A

  • Snap Mobile Payment Apparatuses, Methods and Systems

    US20150248664A1