CN112734416A - Secure payment method and mobile terminal - Google Patents

Secure payment method and mobile terminal Download PDF

Info

Publication number
CN112734416A
CN112734416A CN201910973285.XA CN201910973285A CN112734416A CN 112734416 A CN112734416 A CN 112734416A CN 201910973285 A CN201910973285 A CN 201910973285A CN 112734416 A CN112734416 A CN 112734416A
Authority
CN
China
Prior art keywords
payment
mobile terminal
payment interface
displaying
interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201910973285.XA
Other languages
Chinese (zh)
Inventor
闪超星
于东洋
周佐华
张政学
何泽瑞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910973285.XA priority Critical patent/CN112734416A/en
Publication of CN112734416A publication Critical patent/CN112734416A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401Transaction verification
    • G06Q20/4014Identity check for transactions
    • G06Q20/40145Biometric identity checks
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327Short range or proximity payments by means of M-devices
    • G06Q20/3274Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/382Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3823Payment protocols; Details thereof insuring higher security of transaction combining multiple encryption tools for a transaction
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/42Confirmation, e.g. check or permission by the legal debtor of payment

Abstract

The embodiment of the application provides a method and equipment for secure payment, wherein the method comprises the following steps: when the mobile terminal detects a payment operation, displaying a first payment interface, wherein the first payment interface does not include a payment code; and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code. The safety of payment is improved, prevent that other people from stealing and brushing the payment sign indicating number.

Description

Secure payment method and mobile terminal
Technical Field
The embodiment of the application relates to the technical field of electronics, in particular to a secure payment method and a mobile terminal.
Background
Mobile payment is more and more widely used, but security issues need to be taken into account. For example, when a user waits for payment in a supermarket, a payment interface (for example, a payment two-dimensional code interface of a payment treasure) of the mobile terminal is usually opened in advance. If the payment interface is not shielded tightly, the user can be stolen by surrounding lawless persons (for example, a mobile phone or code scanning equipment is used for shooting or scanning the payment two-dimensional code interface), so that privacy is leaked. Especially, when the user sets up the password-free payment, the embezzlement can directly deduct money from the user account, which results in property loss. If the privacy-exempt payment is turned off, the convenience of payment is reduced.
Disclosure of Invention
The embodiment of the application provides a secure payment method and a mobile terminal, which can prevent lawbreakers from embezzling a payment interface and improve the security of payment.
In order to achieve the above purpose, the embodiment of the present application adopts the following technical solutions:
in a first aspect, an embodiment of the present application provides a method for secure payment, including: when the mobile terminal detects a payment operation, displaying a first payment interface, wherein the first payment interface does not include a payment code; and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code. The payment code can be prevented from being embezzled.
In a possible implementation manner, the first payment interface does not include a payment code, and specifically includes: and carrying out fuzzy, shielding or replacement processing on the payment code.
In a possible implementation manner, the displaying the second payment interface when the mobile terminal meets the first preset condition includes: and displaying a second payment interface within a first preset time after the payment operation is detected.
In a possible implementation manner, the displaying the second payment interface when the mobile terminal meets the first preset condition includes: and when the mobile terminal detects that the face of the user does not exist, displaying a second payment interface.
In a possible implementation manner, the displaying the second payment interface when the mobile terminal meets the first preset condition includes: and when the mobile terminal is in the preset position range, displaying a second payment interface.
In a possible implementation manner, the displaying the second payment interface when the mobile terminal meets the first preset condition includes: and displaying the second payment interface when the finger of the user is detected to be placed at the fingerprint identification of the mobile terminal.
In a possible implementation manner, the displaying the second payment interface when the mobile terminal meets the first preset condition includes: and displaying a second payment interface when the finger of the user is detected to be placed on the screen of the mobile terminal.
In one possible implementation, after displaying the second payment interface, the method further includes: and when the mobile terminal meets the second preset condition, displaying the first payment interface.
In one possible implementation, after displaying the second payment interface, the method further includes: and when the mobile terminal meets a second preset condition, switching the application program to which the payment operation belongs to a background.
In one possible implementation manner, the second preset condition is: and the mobile terminal detects that the payment is not finished within a second preset time after the second payment interface is displayed.
In one possible implementation manner, the mobile terminal is a foldable mobile terminal and comprises a first screen and a second screen, and when the mobile terminal detects a payment operation on the first screen, a first payment interface is displayed on the first screen; and when the mobile terminal meets the first preset condition, displaying a second payment interface on a second screen.
In a second aspect, an embodiment of the present application provides a mobile terminal, which includes a detection unit, a processing unit and a display unit, where the detection unit is configured to detect whether a payment operation exists; the processing unit is used for indicating the display unit to display a first payment interface when the detection unit detects that the payment operation exists; the display unit is used for displaying a first payment interface, and the first payment interface does not include a payment code; the processing unit is further used for indicating the display unit to display a second payment interface when the mobile terminal meets the first preset condition; and the display unit is also used for displaying a second payment interface, and the second payment interface comprises a payment code. The payment code can be prevented from being embezzled.
In one possible implementation, the first payment interface does not include a payment code, including: and carrying out fuzzy, shielding or replacement processing on the payment code.
In a possible implementation manner, the instructing, when the mobile terminal satisfies the first preset condition, the displaying unit to display the second payment interface includes: and in a first preset time after the detection unit detects the payment operation, the processing unit indicates the display unit to display a second payment interface.
In a possible implementation manner, the instructing, when the mobile terminal satisfies the first preset condition, the displaying unit to display the second payment interface includes: when the detection unit detects that the face of the user does not exist, the processing unit instructs the display unit to display a second payment interface.
In a possible implementation manner, the instructing, when the mobile terminal satisfies the first preset condition, the displaying unit to display the second payment interface includes: when the detection unit detects that the mobile terminal is located in the preset position range, the processing unit indicates the display unit to display a second payment interface.
In a possible implementation manner, the instructing, when the mobile terminal satisfies the first preset condition, the displaying unit to display the second payment interface includes: when the detection unit detects that the finger of the user is placed at the fingerprint identification position of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
In a possible implementation manner, the instructing, when the mobile terminal satisfies the first preset condition, the displaying unit to display the second payment interface includes: when the detection unit detects that the finger of the user is placed on the screen of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
In a possible implementation manner, the processing unit is further configured to instruct the display unit to display the first payment interface when the mobile terminal meets the second preset condition.
In a possible implementation manner, the processing unit is further configured to switch the application to which the payment operation belongs to the background when the mobile terminal meets a second preset condition.
In one possible implementation manner, the second preset condition is: the detection unit detects that the payment is not completed within a second preset time after the second payment interface is displayed.
In a third aspect, embodiments of the present application provide a mobile terminal, which includes one or more processors, a memory, and one or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of the first aspect.
In a fourth aspect, embodiments of the present application provide a storage medium for storing computer software instructions for performing the method according to the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product, which when executed, causes a computer to perform the method according to the first aspect.
Through the scheme, the payment code can be prevented from being stolen and brushed during payment, and the payment safety is improved.
Drawings
Fig. 1 is a schematic view of a scenario of mobile payment using a payment app according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;
fig. 3 is a flowchart of a method for secure payment according to an embodiment of the present application;
FIG. 4 is a schematic view of a first payment interface provided in an embodiment of the present application;
FIG. 5 is a flow chart of another method for secure payment provided by embodiments of the present application;
FIG. 6 is a schematic diagram illustrating a user manually triggering an anti-swipe stealing process according to an embodiment of the present application;
FIG. 7 is a flow chart of another method for secure payment provided by embodiments of the present application;
FIG. 8 is a flow chart of another method for secure payment provided by embodiments of the present application;
FIG. 9 is a flow chart of another method for secure payment provided by embodiments of the present application;
FIG. 10 is a flow chart of another method for secure payment provided by embodiments of the present application;
FIG. 11 is a flow chart of another method for secure payment provided by embodiments of the present application;
fig. 12 is a flowchart of a method for secure payment according to an embodiment of the present application;
fig. 13 is a schematic diagram of a mobile terminal according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the description of the embodiments herein, "/" means "or" unless otherwise specified, for example, a/B may mean a or B; "and/or" herein is merely an association describing an associated object, and means that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present application, "a plurality" means two or more than two.
Mobile payment refers to completing payment or confirming payment using a mobile terminal, rather than payment with cash, a bank card, or a check. A buyer can use a mobile phone to purchase a range of services, digital products or goods, etc. The mobile terminal may include devices such as a mobile phone, a tablet computer, a wearable device (e.g., a watch, a bracelet, a smart helmet, etc.), an in-vehicle device, a smart home device, an Augmented Reality (AR)/Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and the like. Some embodiments of the present application take a mobile phone as an example, and it is understood that these embodiments can also be applied to other types of mobile terminals.
When the user uses the mobile terminal to carry out mobile payment, the payment code can be displayed to the merchant, so that the merchant can read the payment code through the code scanning device to finish payment. Specifically, there are many ways to expose the payment code to the merchant, such as opening a payment-type application, or opening a payment interface of the application, or invoking the payment interface through a browser, or invoking the payment interface through an applet, or opening any interface with the payment code. The pay code may be any information for mobile payment, such as a bar code, a two-dimensional code, a pay code number string, etc., which are commonly used. The code scanning equipment is used for a merchant to read a payment code on the mobile terminal, and can be divided into bar code scanning equipment, two-dimensional code scanning equipment and the like according to different types of the read payment code; according to the reading physical principle, the method can be divided into an infrared code scanning device or a laser code scanning device and the like. The user may also set a payment password (including but not limited to a numeric password, a graphical password, a swipe password, a fingerprint password, a face recognition password, a voice print recognition password, an iris recognition password, etc.) for confirming payment completion transaction authorization. When the user sets the password-free payment, the payment can be directly made without the user inputting a password. Especially for payment of small amount, the payment without secret can bring great convenience.
An application (app) related to the embodiment of the present application may be simply referred to as an application, and is a software program capable of implementing one or more specific functions. Generally, a plurality of applications, such as an instant messaging application, a video application, an audio application, an image capturing application, and the like, may be installed in the electronic device; payment class applications such as pay-Bay (Alipay) or WeChat payments, etc. The application mentioned in the embodiment of the present application may be an application installed when the electronic device leaves a factory, or an application downloaded from a network or acquired by another electronic device during the process of using the electronic device by a user.
As an example shown in fig. 1, when using a payment app for mobile payment, a user may open the payment app on a cell phone and enter a payment interface. The payment interface displays a payment code comprising a bar code and a two-dimensional code, and a merchant can read the payment code (which can read either the bar code or the two-dimensional code) of the payment interface by using a code scanning device (such as a code scanning gun), so that the payment code and order information are uploaded to a server to initiate payment. If the user sets up a privacy-free payment, the user can be directly deducted from the user account without password authorization of the user.
As shown in fig. 2, the mobile terminal in the embodiment of the present application may be a mobile phone 100. The embodiment will be specifically described below by taking the mobile phone 100 as an example. It should be understood that the illustrated handset 100 is only one example of a mobile terminal and that the handset 100 may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration of components.
As shown in fig. 2, the mobile phone 100 may specifically include: processor 101, Radio Frequency (RF) circuitry 102, memory 103, touch screen 104, bluetooth device 105, one or more sensors 106, Wi-Fi device 107, positioning device 108, audio circuitry 109, peripherals interface 110, and power system 111. These components may communicate over one or more communication buses or signal lines (not shown in fig. 2). Those skilled in the art will appreciate that the hardware configuration shown in fig. 2 is not intended to be limiting, and that the handset 100 may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes the components of the handset 100 in detail with reference to fig. 2:
the processor 101 is a control center of the cellular phone 100, connects various parts of the cellular phone 100 using various interfaces and lines, and performs various functions of the cellular phone 100 and processes data by running or executing an application program stored in the memory 103 and calling data stored in the memory 103. In some embodiments, processor 101 may include one or more processing units; for example, the processor 101 may be an kylin 960 chip manufactured by Huanti technologies, Inc. In some embodiments of the present application, the processor 101 may further include a fingerprint verification chip for verifying the acquired fingerprint.
The rf circuit 102 may be used for receiving and transmitting wireless signals during the transmission and reception of information or calls. In particular, the rf circuit 102 may receive downlink data of the base station and then process the received downlink data to the processor 101; in addition, data relating to uplink is transmitted to the base station. Typically, the radio frequency circuitry includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency circuitry 102 may also communicate with other devices via wireless communication. The wireless communication may use any communication standard or protocol including, but not limited to, global system for mobile communications, general packet radio service, code division multiple access, wideband code division multiple access, long term evolution, email, short message service, and the like.
The memory 103 is used for storing application programs and data, and the processor 101 executes various functions and data processing of the mobile phone 100 by running the application programs and data stored in the memory 103. The memory 103 mainly includes a program storage area and a data storage area, wherein the program storage area can store an operating system and application programs (such as a sound playing function and an image playing function) required by at least one function; the storage data area may store data (e.g., audio data, a phonebook, etc.) created from use of the handset 100. Further, the memory 103 may include high speed random access memory, and may also include non-volatile memory, such as a magnetic disk storage device, a flash memory device, or other volatile solid state storage device. The memory 103 may store various operating systems, such as those developed by apple Inc
Figure BDA0002232809750000041
Operating System, developed by Google
Figure BDA0002232809750000042
An operating system, etc. The memory 103 may be independent and connected to the processor 101 through the communication bus; the memory 103 may also be integrated with the processor 101.
The touch screen 104 may include a touch pad 104-1 and a display 104-2. Wherein the touch pad 104-1 can capture touch events on or near the touch pad 104-1 by a user of the cell phone 100 (e.g., user operation on or near the touch pad 104-1 using any suitable object such as a finger, a stylus, etc.), and transmit the captured touch information to other devices, such as the processor 101. Among them, a touch event of a user near the touch pad 104-1 can be called a hover touch; hover touch may refer to a user not having to directly contact the touchpad in order to select, move, or drag a target (e.g., an icon, etc.), but rather only having to be located near the electronic device in order to perform a desired function. In the context of a hover touch application, the terms "touch," "contact," and the like do not imply a direct contact to the touch screen, but rather a nearby or near contact. The touch panel 104-1 capable of floating touch can be implemented by using capacitive type, infrared light sensing, ultrasonic wave, and the like. In addition, the touch pad 104-1 can be implemented by various types, such as resistive, capacitive, infrared, and surface acoustic wave. Display (also referred to as a display screen) 104-2 may be used to display information entered by or provided to the user as well as various menus for handset 100. The display 104-2 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The trackpad 104-1 may be overlaid on the display 104-2, and when the trackpad 104-1 detects a touch event thereon or nearby, it is communicated to the processor 101 to determine the type of touch event, and the processor 101 may then provide a corresponding visual output on the display 104-2 based on the type of touch event. Although in FIG. 2, the touch pad 104-1 and the display screen 104-2 are shown as two separate components to implement the input and output functions of the cell phone 100, in some embodiments, the touch pad 104-1 and the display screen 104-2 may be integrated to implement the input and output functions of the cell phone 100. It is understood that the touch screen 104 is formed by stacking multiple layers of materials, and only the touch pad (layer) and the display screen (layer) are shown in the embodiment of the present application, and other layers are not described in the embodiment of the present application. In addition, in some other embodiments of the present application, the touch pad 104-1 may be covered on the display 104-2, and the size of the touch pad 104-1 is larger than that of the display screen 104-2, so that the display screen 104-2 is completely covered under the touch pad 104-1, or the touch pad 104-1 may be disposed on the front surface of the mobile phone 100 in a full-panel manner, that is, the touch of the user on the front surface of the mobile phone 100 can be sensed by the mobile phone, so that the full-touch experience on the front surface of the mobile phone can be achieved. In other embodiments, the touch pad 104-1 is disposed on the front surface of the mobile phone 100 in a full-panel manner, and the display screen 104-2 may also be disposed on the front surface of the mobile phone 100 in a full-panel manner, so that a frameless structure can be implemented on the front surface of the mobile phone.
In the embodiment of the present application, the mobile phone 100 may further have a fingerprint recognition function. For example, the fingerprint acquisition device 112 may be configured in the touch screen 104 to implement the fingerprint identification function, i.e., the fingerprint acquisition device 112 may be integrated with the touch screen 104 to implement the fingerprint identification function of the mobile phone 100. In this case, the fingerprint acquisition device 112 is disposed in the touch screen 104, may be a part of the touch screen 104, and may be disposed in the touch screen 104 in other manners. Additionally, the fingerprint acquisition device 112 may also be implemented as a full panel fingerprint acquisition device. Thus, the touch screen 104 can be viewed as a panel that can be fingerprinted anywhere. The fingerprint acquisition device 112 may send the acquired fingerprint to the processor 101 for processing (e.g., fingerprint verification, etc.) by the processor 101. The main component of the fingerprint acquisition device 112 in the present embodiment is a fingerprint sensor, which may employ any type of sensing technology, including but not limited to optical, capacitive, piezoelectric, or ultrasonic sensing technologies, among others.
The handset 100 may also include a bluetooth device 105 for enabling data exchange between the handset 100 and other short-range electronic devices (e.g., cell phones, smartwatches, etc.). The bluetooth device in the embodiment of the present application may be an integrated circuit or a bluetooth chip.
The handset 100 may also include at least one sensor 106, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that adjusts the brightness of the display of the touch screen 104 according to the brightness of ambient light, and a proximity sensor that turns off the power of the display when the mobile phone 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone 100, further description is omitted here.
The Wi-Fi device 107 is used for providing network access for the mobile phone 100 according to Wi-Fi related standard protocols, the mobile phone 100 can be accessed to a Wi-Fi access point through the Wi-Fi device 107, so that the mobile phone helps a user to send and receive e-mails, browse webpages, access streaming media and the like, and wireless broadband internet access is provided for the user. In other embodiments, the Wi-Fi apparatus 107 can also be a Wi-Fi wireless access point, which can provide Wi-Fi network access to other electronic devices.
And a positioning device 108 for providing a geographical position for the handset 100. It is understood that the positioning device 108 may be a receiver of a Global Positioning System (GPS) or a positioning system such as the beidou satellite navigation system, russian GLONASS, etc. After receiving the geographical location transmitted by the positioning system, the positioning device 108 transmits the information to the processor 101 for processing or transmits the information to the memory 103 for storage. In still other embodiments, the positioning device 108 may also be a receiver of an Assisted Global Positioning System (AGPS) that assists the positioning device 108 in performing ranging and positioning services by acting as an assistance server, in which case the assistance positioning server provides positioning assistance by communicating with the positioning device 108 (i.e., GPS receiver) of an electronic device, such as the handset 100, over a wireless communication network. In other embodiments, the location device 108 may also be a Wi-Fi access point based location technology. Because each Wi-Fi access point has a globally unique MAC address, the electronic equipment can scan and collect broadcast signals of the surrounding Wi-Fi access points under the condition of starting Wi-Fi, and therefore the MAC addresses broadcasted by the Wi-Fi access points can be obtained; the electronic device sends the data (such as the MAC address) capable of identifying the Wi-Fi access points to the location server through the wireless communication network, the location server retrieves the geographical location of each Wi-Fi access point, and calculates the geographical location of the electronic device according to the strength of the Wi-Fi broadcast signal and sends the geographical location of the electronic device to the positioning device 108 of the electronic device.
The audio circuitry 109, speaker 113, microphone 114 can provide an audio interface between a user and the handset 100. The audio circuit 109 may transmit the electrical signal converted from the received audio data to the speaker 113, and convert the electrical signal into a sound signal by the speaker 113 for output; on the other hand, the microphone 114 converts the collected sound signal into an electrical signal, converts the electrical signal into audio data after being received by the audio circuit 109, and outputs the audio data to the RF circuit 102 to be transmitted to, for example, another cellular phone, or outputs the audio data to the memory 103 for further processing.
Peripheral interface 110, which is used to provide various interfaces for external input/output devices (e.g., keyboard, mouse, external display, external memory, SIM card, etc.). For example, a mouse via a Universal Serial Bus (USB) interface, and a subscriber identity module card (SIM) card provided by a telecommunications carrier via metal contacts on a SIM card slot. Peripheral interface 110 may be used to couple the aforementioned external input/output peripherals to processor 101 and memory 103.
The mobile phone 100 may further include a power supply device 111 (such as a battery and a power management chip) for supplying power to each component, and the battery may be logically connected to the processor 101 through the power management chip, so as to implement functions of managing charging, discharging, and power consumption through the power supply device 111.
Although not shown in fig. 2, the mobile phone 100 may further include a camera (front camera and/or rear camera), a flash, a micro-projector, a Near Field Communication (NFC) device, and the like, which are not described in detail herein.
Fig. 3 provides a method of secure payment, the method comprising the steps of:
301: when the mobile terminal detects the payment operation, a first payment interface is displayed, and the first payment interface does not include a payment code.
When the mobile phone detects a payment operation of a user, for example, the user opens a payment APP or performs payment through an application program, a browser, an applet, or the like, in order to prevent a lawless person from embezzling a payment interface, the payment interface including a payment code may not be displayed, but a first payment interface not including the payment code may be displayed. The first payment interface does not include the payment code, which means that the first payment interface cannot be read by the code scanning device or other mobile terminals to obtain a correct and complete payment code, so that payment cannot be completed. For example, the payment code cannot be read, or the read payment code is incomplete such that no payment is possible, or an incorrect payment code is read, or a failed payment code is read, etc. The first payment interface does not include the payment code, and the implementation manner may be various, for example, the first payment interface may perform a blurring or blocking process on the payment code, may display only a partial payment code, may replace the payment code with another picture, or hide the payment code, or display an incorrect payment code, and the like. Optionally, the first payment interface is displayed, and may be automatically displayed when the mobile terminal detects the payment operation, or manually triggered by the user to display the first payment interface. Optionally, in some cases, "the first payment interface does not include a payment code" may be replaced with: the first payment interface is an interface after the payment codes are subjected to fuzzy, shielding or replacement processing.
302: and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code.
When the user is ready to perform a payment action or confirms that the possibility of being swiped illegally by a lawbreaker is low, the first preset condition can be considered to be met, and at this time, a normal payment interface, namely the second payment interface, can be displayed. The second payment interface includes a payment code so that a correct, complete payment code can be read by a code scanning device or other mobile terminal to complete the payment. The first preset condition may be a time condition, such as a certain point in time, or within a certain time interval (e.g. 5 seconds) after the detection of the payment operation; or the mobile terminal detects that the surrounding environment is a secure payment environment, for example, whether a camera of the mobile terminal can detect a human face, whether the mobile terminal is located at a specific geographic location, and the like; or the mobile terminal receives some instructions from the server or the user; other preset conditions are also possible. It is to be understood that the first preset condition may also be a condition that the second payment interface is displayed in fig. 5, fig. 7, fig. 8, fig. 9, fig. 10, fig. 11, fig. 12 hereinafter. It can be understood that the first preset condition may be set by the user, may also be set by the mobile terminal system, may also be set by the payment APP itself, and may also be set by the payment server in advance. Optionally, when the mobile terminal meets the first preset condition, the mobile terminal may automatically display the second payment interface, or the user manually triggers to display the second payment interface.
Optionally, after step 302, the method may further include step 303: and when the mobile terminal meets a second preset condition, displaying a first payment interface, wherein the first payment interface does not comprise a payment code.
For example, when the user is ready to pay, when the mobile terminal meets the first preset condition, the mobile terminal detects that the user keeps placing a finger at the fingerprint identification position, and at this time, the two-dimension code blurring or shielding processing is cancelled and the second payment interface is displayed. It can be understood that when the finger leaves the fingerprint identification place (the second preset condition is met), the two-dimension code blurring or shielding treatment (namely the first payment interface) can be recovered again, the two-dimension code is ensured to be in a protected state, and the stealing brushing is prevented.
For another example, when the user is ready to pay, when the mobile terminal meets the first preset condition, it may be detected that the user presses a finger on any position of the screen, and at this time, the two-dimensional code blurring or shielding process is cancelled, and the second payment interface is displayed. It can be understood that when the user finger is released (the second preset condition is met), the two-dimensional code blurring or shielding processing (namely the first payment interface) can be restored again, the two-dimensional code is ensured to be in a protected state, and the stealing brushing is prevented.
Fig. 4 shows several examples of the first payment interface, and as described above, there are various ways to implement that the first payment interface does not include the payment code, as long as the first payment interface cannot be read by the code scanning device or other mobile terminals to read the correct and complete payment code. It is understood that the reader may think of more examples of the first payment interface, all of which fall within the scope of the first payment interface, according to the example of fig. 4.
In fig. 4, (a) is a diagram showing the effect of replacing or blocking the payment code with a blank page or disappearing the payment code; (b) the image is to replace or obscure the payment code with other pictures; (c) the image processing (such as mosaic and fuzzification) is carried out on the payment code; (d) the figure shows only partial payment codes, and the figure (e) shows wrong payment codes. There are further examples of the first payment interface, which are not described in detail herein.
Optionally, in a specific implementation, the above replacement, blocking, image processing, local display and other manners may be to replace an original image frame with a new image frame, or to directly process an original image frame, which depends on the display principle of the mobile terminal. For example, the mobile phone may replace the original page with the whole image frame, and may also detect and process the area where the payment code image is located, which is not limited herein.
Fig. 5 provides another method of secure payment, the method comprising the steps of:
501: when the mobile terminal detects a payment operation, a first instruction of a user is received, wherein the first instruction is used for displaying a first payment interface, and the first payment interface does not include a payment code.
When the mobile phone detects a payment operation of a user, for example, the user opens a payment APP or pays through an application program, a browser, an applet, or the like, a first instruction of the user may be received, where the first instruction is used to display a first payment interface, and the first payment interface does not include a payment code. In other words, the anti-swipe-through process is manually triggered by the user. The first command can be implemented in various ways, such as clicking a button on the screen, pressing a key of the mobile phone (or a combination of keys, where the key can be physical or virtual), using a gesture command, using a voice command, shaking the mobile phone, turning the mobile phone, folding the mobile phone, clicking the mobile phone screen, double clicking the mobile phone screen, clicking the mobile phone screen with a finger joint, long-pressing the mobile phone screen, releasing the long-pressed mobile phone screen, and the like. Optionally, the first instruction may also be a long-time press of the fingerprint identification location with a finger (the fingerprint identification location may be integrated on the home key or a side key of the mobile phone, or located on the back of the mobile phone, or located below the screen), or a re-press or multiple-click of the fingerprint identification location.
502: and when the mobile terminal meets the first preset condition, receiving a second instruction of the user, wherein the second instruction is used for displaying a second payment interface, and the second payment interface comprises a payment code.
When the user is ready to perform a payment action or confirms that the possibility of being swiped illegally by a lawbreaker is low, the first preset condition can be considered to be met, and at the moment, the user can manually trigger and display a normal payment interface, namely the second payment interface. The second payment interface includes a payment code so that a correct, complete payment code can be read by a code scanning device or other mobile terminal to complete the payment. Similar to the first instruction, the second instruction may also be implemented in a variety of ways. Optionally, the second instruction may also be a long-time press of the fingerprint identification location with a finger (the fingerprint identification location may be integrated on the home key or a side key of the mobile phone, or located on the back of the mobile phone, or located below the screen), or a re-press or multiple clicks of the fingerprint identification location.
Alternatively, the second instruction may be the same as or different from the first instruction. For example, the first instruction may be to press the mobile phone screen for a long time, and the second instruction may be to release the mobile phone screen for a long time; or, the first instruction may be to click a first key of the mobile phone, and the second instruction may be to click a second key of the mobile phone; or the first instruction is the long press fingerprint identification, and the second instruction is the release of the long press fingerprint identification; or the first instruction is any position of a click screen, and the second instruction is also any position of the click screen; and so on.
For example, when a user is preparing to pay, a finger may be placed at all times at the fingerprint, displaying a first payment interface that does not include a payment code (e.g., a blurred or obscured processed two-dimensional code); when the finger is removed from the fingerprint identification, a second payment interface is displayed that includes a full clear payment code.
Fig. 6 shows an example of a user manually triggering the anti-swipe stealing process, where the first command is the user clicking a button on the screen. The button may be displayed in any payment interface (e.g., the first payment interface or the second payment interface), and the user may trigger the first instruction when needed, such that the first payment interface is displayed without including the payment code. It will be appreciated that the user may also use this button to trigger the second instruction to cause the display of a second payment interface including a payment code.
Fig. 7 provides another method of secure payment, the method comprising the steps of:
701: when the mobile terminal detects a payment operation, if the payment is not completed within a first preset time, a first payment interface is displayed, and the first payment interface does not include a payment code.
If the payment operation is performed but the payment is not completed for a long time, the possibility of the brush being stolen is high. For example, when the user queues for checkout, the payment APP is opened in advance to show the payment code, but the user may wait for a long time when the user checks out, and may be stolen by a lawbreaker. In this case, a first preset time (e.g., 3 seconds, 1 minute, etc.) may be set, and if it is determined that the payment is not completed within the first preset time, a first payment interface not including the payment code is displayed (e.g., the payment code is blocked or hidden). It can be understood that the first preset time may be set by the user, may also be set by the mobile terminal system, may also be set by the payment APP itself, and may also be set by the payment server in advance.
702: and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code.
When the user is ready to perform a payment action or confirms that the possibility of being swiped illegally by a lawbreaker is low, the first preset condition can be considered to be met, and at this time, a normal payment interface, namely the second payment interface, can be displayed. The second payment interface includes a payment code so that a correct, complete payment code can be read by a code scanning device or other mobile terminal to complete the payment. Optionally, the user may manually trigger the display of the second payment interface, or may automatically trigger the display of the second payment interface.
Fig. 8 provides another method of secure payment, comprising the steps of:
801: when the mobile terminal detects the payment operation of the payment application, if the payment is not completed within the first preset time, the payment application is switched to the background.
If the payment operation is performed but the payment is not completed for a long time, the possibility of the brush being stolen is high. For example, when the user queues for checkout, the payment APP is opened in advance to show the payment code, but the user may wait for a long time when the user checks out, and may be stolen by a lawbreaker. In this case, the payment application performing the payment operation may be automatically switched to the background, thereby avoiding displaying the payment code. After switching to the background, the system desktop (which may be the main screen desktop or other screen desktop) may be displayed, and other applications may also be displayed (e.g., switching to other background applications that have already been opened, or newly opening an application).
802: and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code.
When the user is ready to perform a payment action or confirms that the possibility of being swiped illegally by a lawbreaker is low, the first preset condition can be considered to be met, and at this time, a normal payment interface, namely the second payment interface, can be displayed. The second payment interface includes a payment code so that a correct, complete payment code can be read by a code scanning device or other mobile terminal to complete the payment. Optionally, the user may manually trigger the display of the second payment interface, or may automatically trigger the display of the second payment interface. Since the payment interface has been switched to the background in step 801, the second payment interface may be automatically popped up to complete the payment.
Fig. 9 provides another method for secure payment, applied to a folded screen terminal (e.g., an external folded handset having two screens), comprising the steps of:
901: when the folding screen terminal is in a folding state, whether payment operation exists on the first screen is detected.
When a user performs a payment operation using an external folder phone having two screens, it may be detected whether there is a payment operation of opening a payment APP on one of the screens (which may be referred to as a first screen).
902: and when the payment operation is detected on the first screen, displaying a second payment interface on a second screen, wherein the second payment interface comprises a payment code.
When fold condition, first screen and second screen orientation are opposite, open the payment APP back at the first screen of orientation oneself when the user, in order to prevent that lawless persons from stealing the brush, can show the payment code at the second screen at the cell-phone back. Optionally, when a payment operation is detected on the first screen, it may be determined that the payment is not completed within a first preset time, and a second payment interface is displayed on the second screen, where the second payment interface includes a payment code.
FIG. 10 provides another method of secure payment, the method comprising the steps of:
1001: when the mobile terminal detects the payment operation, a first payment interface is displayed, and the first payment interface does not include a payment code.
1002: and detecting whether a face exists by using a camera, and if the face does not exist, displaying a second payment interface, wherein the second payment interface comprises a payment code.
Optionally, a front camera may be used to detect whether a human face exists. If a human face is not present (e.g., only the ceiling of a roof can be detected), it may be possible for the user to lay the phone flat so that the merchant scans the payment code using the code scanning device, at which point a second payment interface including the payment code may be displayed. If a human face (possibly the user's face or the face of another person) is present, there may be a risk of being swiped illegally, continuing to display the first payment interface.
Optionally, a face recognition technology may be used, and a camera may be used to detect whether a face of a user exists. For example, detecting whether a face of the user exists by using a front camera, and if the face of the user exists, continuing to display the first payment interface; and if the face of the user does not exist, displaying a second payment interface comprising the payment code. The absence of the face of the user may be the absence of any face, or the absence of the face of the user but the presence of other faces (for example, the face of a merchant cashier). For example, if the front-facing camera cannot detect the face of the user, but can detect the face of the merchant, which indicates that the mobile phone may face a cashier, and at this time, the user needs to pay, a second payment interface containing the payment code is displayed, so that the merchant can scan the payment code on the screen by using the code scanning device to complete the payment.
It can be understood that, besides detecting a human face, other methods may also be used to determine whether a user faces a mobile phone, for example, iris recognition may be used, and details are not described here.
FIG. 11 provides another method of secure payment, the method comprising the steps of:
1101: when the mobile terminal detects the payment operation, a first payment interface is displayed, and the first payment interface does not include a payment code.
1102: and when the mobile terminal is in the first preset posture, displaying a second payment interface, wherein the second payment interface comprises a payment code.
The first preset posture can be a posture which is suitable for scanning and payment of code scanning equipment and is not easy to be embezzled by lawbreakers. For example, when the mobile phone is horizontally placed, it may be that the user needs to make a payment in order for the merchant to scan the payment code using the code scanning device, at which point a second payment interface including the payment code may be displayed. For another example, when the upper half of the phone is tilted downward or placed vertically, it may be that the user is presenting the payment code to the merchant, at which time a second payment interface including the payment code may be displayed. For another example, when the upper half of the mobile phone is at any angle between horizontal and vertical, it may be that the user needs to pay, and a second payment interface including the two-dimensional code may be displayed. The attitude (e.g., tilt angle) of the handset may be determined using a gyroscope internal to the handset.
It will be appreciated that the various secure payment methods described above may be used in combination to better enhance the security of the payment and prevent fraudulent swiping. For example, as shown in fig. 12, a method of possible secure payments may include the steps of:
1201: when the mobile terminal detects the payment operation, a first payment interface is displayed, and the first payment interface does not include a payment code.
1202: detecting whether a human face exists by using a camera;
1203: and if the face does not exist, when the mobile terminal is in the first preset posture, displaying a second payment interface, wherein the second payment interface comprises a payment code.
Other possible combinations may include: when the payment operation is detected, if the payment is not completed within the first preset time, displaying a first payment interface, then detecting a face by using a camera, and when the face does not exist, displaying a second payment interface. Such combination is many and will not be described in detail here.
In addition, the present application provides another method of secure payment, comprising: when the mobile terminal detects a payment operation, displaying a first payment interface, wherein the first payment interface does not include a payment code; and when the mobile terminal meets the first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code.
Optionally, the first payment interface does not include a payment code, and includes: and carrying out fuzzy, shielding or replacement processing on the payment code.
Optionally, when the mobile terminal meets the first preset condition, displaying a second payment interface, including: and displaying a second payment interface within a first preset time after the payment operation is detected.
Optionally, when the mobile terminal meets the first preset condition, displaying a second payment interface, including: and when the mobile terminal detects that the face of the user does not exist, displaying a second payment interface.
Optionally, when the mobile terminal meets the first preset condition, displaying a second payment interface, including: and when the mobile terminal is in the preset position range, displaying a second payment interface.
Optionally, when the mobile terminal meets the first preset condition, displaying a second payment interface, including: and displaying the second payment interface when the finger of the user is detected to be placed at the fingerprint identification of the mobile terminal.
Optionally, when the mobile terminal meets the first preset condition, displaying a second payment interface, including: and when the finger of the user is detected to be placed on the screen of the mobile terminal, displaying the second payment interface.
Optionally, after displaying the second payment interface, the method further includes: and when the mobile terminal meets the second preset condition, displaying the first payment interface.
Optionally, after displaying the second payment interface, the method further includes: and when the mobile terminal meets a second preset condition, switching the application program to which the payment operation belongs to a background.
Optionally, the second preset condition is: and the mobile terminal detects that the payment is not finished within a second preset time after the second payment interface is displayed.
Optionally, the mobile terminal is a foldable mobile terminal, and includes a first screen and a second screen, and when the mobile terminal detects a payment operation on the first screen, a first payment interface is displayed on the first screen; and when the mobile terminal meets the first preset condition, displaying a second payment interface on a second screen.
Fig. 13 provides a mobile terminal including a detection unit 1301, a processing unit 1302, and a display unit 1303. The detection unit 1301 is configured to detect whether a payment operation exists; the processing unit 1302 is configured to, when the detection unit 1301 detects that there is a payment operation, instruct the display unit 1303 to display a first payment interface; the display unit 1303 is configured to display a first payment interface, where the first payment interface does not include a payment code; the processing unit 1302 is further configured to instruct the display unit 1303 to display a second payment interface when the mobile terminal meets a first preset condition; the display unit 1303 is further configured to display a second payment interface, where the second payment interface includes a payment code. It will be appreciated that the mobile terminal may perform the methods as described in fig. 3-12.
Optionally, the first payment interface does not include a payment code, and includes: and carrying out fuzzy, shielding or replacement processing on the payment code.
Optionally, when the mobile terminal meets a first preset condition, instructing the display unit to display a second payment interface, including: and in a first preset time after the detection unit detects the payment operation, the processing unit indicates the display unit to display a second payment interface.
Optionally, when the mobile terminal meets a first preset condition, instructing the display unit to display a second payment interface, including: when the detection unit detects that the face of the user does not exist, the processing unit instructs the display unit to display a second payment interface.
Optionally, when the mobile terminal meets a first preset condition, instructing the display unit to display a second payment interface, including: when the detection unit detects that the mobile terminal is located in the preset position range, the processing unit indicates the display unit to display a second payment interface.
Optionally, when the mobile terminal meets a first preset condition, instructing the display unit to display a second payment interface, including: when the detection unit detects that the finger of the user is placed at the fingerprint identification position of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
Optionally, when the mobile terminal meets a first preset condition, instructing the display unit to display a second payment interface, including: when the detection unit detects that the finger of the user is placed on the screen of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
Optionally, the processing unit is further configured to instruct the display unit to display the first payment interface when the mobile terminal meets a second preset condition.
Optionally, the processing unit is further configured to switch the application to which the payment operation belongs to the background when the mobile terminal meets a second preset condition.
Optionally, the second preset condition is: the detection unit detects that the payment is not completed within a second preset time after the second payment interface is displayed.
The present application also provides another mobile terminal comprising one or more processors, memory, one or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the methods described above in fig. 3-12.
The present application also provides a storage medium for storing computer software instructions for performing the methods described above with respect to fig. 3-12.
The present application also provides a computer program product which, when executed, causes a computer to perform the method described above with reference to fig. 3-12.
Through the description of the above embodiments, those skilled in the art will understand that, for convenience and simplicity of description, only the division of the above functional modules is used as an example, and in practical applications, the above function distribution may be completed by different functional modules as needed, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or a plurality of physical units, that is, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (24)

1. A method of secure payment, the method comprising:
when the mobile terminal detects a payment operation, displaying a first payment interface, wherein the first payment interface does not include a payment code;
and when the mobile terminal meets a first preset condition, displaying a second payment interface, wherein the second payment interface comprises a payment code.
2. The method of claim 1, wherein the first payment interface does not include a payment code, comprising:
and carrying out fuzzy, shielding or replacement processing on the payment code.
3. The method according to claim 1 or 2, wherein the displaying a second payment interface when the mobile terminal meets a first preset condition comprises:
and displaying the second payment interface within a first preset time after the payment operation is detected.
4. The method according to claim 1 or 2, wherein the displaying a second payment interface when the mobile terminal meets a first preset condition comprises:
and when the mobile terminal detects that the face of the user does not exist, displaying the second payment interface.
5. The method according to claim 1 or 2, wherein the displaying a second payment interface when the mobile terminal meets a first preset condition comprises:
and when the mobile terminal is in a preset position range, displaying the second payment interface.
6. The method according to claim 1 or 2, wherein the displaying a second payment interface when the mobile terminal meets a first preset condition comprises:
and when the finger of the user is detected to be placed at the fingerprint identification of the mobile terminal, displaying the second payment interface.
7. The method according to claim 1 or 2, wherein the displaying a second payment interface when the mobile terminal meets a first preset condition comprises:
and when the finger of the user is detected to be placed on the screen of the mobile terminal, displaying the second payment interface.
8. The method of claim 1, wherein after said displaying the second payment interface, the method further comprises:
and when the mobile terminal meets a second preset condition, displaying the first payment interface.
9. The method of claim 1, wherein after said displaying the second payment interface, the method further comprises:
and when the mobile terminal meets a second preset condition, switching the application program to which the payment operation belongs to a background.
10. The method according to claim 8 or 9, characterized in that the second preset condition is: and the mobile terminal detects that the payment is not finished within a second preset time after the second payment interface is displayed.
11. The method of claim 1, the mobile terminal being a foldable mobile terminal comprising a first screen and a second screen, characterized in that:
when the mobile terminal detects a payment operation, a first payment interface is displayed, specifically: when the mobile terminal detects the payment operation on the first screen, displaying the first payment interface on the first screen;
when the mobile terminal meets a first preset condition, a second payment interface is displayed, and the method specifically comprises the following steps: and when the mobile terminal meets a first preset condition, displaying the second payment interface on the second screen.
12. A mobile terminal, the mobile terminal comprising a detection unit, a processing unit and a display unit, characterized in that:
the detection unit is used for detecting whether payment operation exists or not;
the processing unit is used for indicating the display unit to display a first payment interface when the detection unit detects that the payment operation exists;
the display unit is used for displaying the first payment interface, and the first payment interface does not include a payment code;
the processing unit is further used for indicating the display unit to display a second payment interface when the mobile terminal meets a first preset condition;
the display unit is further used for displaying a second payment interface, and the second payment interface comprises a payment code.
13. The mobile terminal of claim 12, wherein the first payment interface does not include a payment code, comprising:
and carrying out fuzzy, shielding or replacement processing on the payment code.
14. The mobile terminal according to claim 12 or 13, wherein the instructing the display unit to display a second payment interface when the mobile terminal satisfies a first preset condition comprises:
and the processing unit indicates the display unit to display the second payment interface within a first preset time after the detection unit detects the payment operation.
15. The mobile terminal according to claim 12 or 13, wherein the instructing the display unit to display a second payment interface when the mobile terminal satisfies a first preset condition comprises:
when the detection unit detects that the face of the user does not exist, the processing unit instructs the display unit to display the second payment interface.
16. The mobile terminal according to claim 12 or 13, wherein the instructing the display unit to display a second payment interface when the mobile terminal satisfies a first preset condition comprises:
when the detection unit detects that the mobile terminal is located in a preset position range, the processing unit instructs the display unit to display the second payment interface.
17. The mobile terminal according to claim 12 or 13, wherein the instructing the display unit to display a second payment interface when the mobile terminal satisfies a first preset condition comprises:
when the detection unit detects that the finger of the user is placed at the fingerprint identification position of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
18. The mobile terminal according to claim 12 or 13, wherein the instructing the display unit to display a second payment interface when the mobile terminal satisfies a first preset condition comprises:
when the detection unit detects that the finger of the user is placed on the screen of the mobile terminal, the processing unit instructs the display unit to display the second payment interface.
19. The mobile terminal of claim 12, wherein;
the processing unit is further used for indicating the display unit to display the first payment interface when the mobile terminal meets a second preset condition.
20. The mobile terminal of claim 12, wherein;
the processing unit is further configured to switch the application program to which the payment operation belongs to a background when the mobile terminal meets a second preset condition.
21. The mobile terminal according to claim 19 or 20, wherein the second preset condition is that: the detection unit detects that the payment is not completed within a second preset time after the second payment interface is displayed.
22. A mobile terminal comprising one or more processors, memory, one or more programs; wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing the method of claims 1-11.
23. A storage medium storing computer software instructions for performing the method of claims 1-11.
24. A computer program product which, when run, causes a computer to perform the method of claims 1-11.
CN201910973285.XA 2019-10-14 2019-10-14 Secure payment method and mobile terminal Pending CN112734416A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910973285.XA CN112734416A (en) 2019-10-14 2019-10-14 Secure payment method and mobile terminal

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910973285.XA CN112734416A (en) 2019-10-14 2019-10-14 Secure payment method and mobile terminal

Publications (1)

Publication Number Publication Date
CN112734416A true CN112734416A (en) 2021-04-30

Family

ID=75588446

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910973285.XA Pending CN112734416A (en) 2019-10-14 2019-10-14 Secure payment method and mobile terminal

Country Status (1)

Country Link
CN (1) CN112734416A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114282561A (en) * 2021-12-23 2022-04-05 珠海格力电器股份有限公司 Code identification display method and device, electronic equipment and storage medium
WO2023065783A1 (en) * 2021-10-18 2023-04-27 花瓣云科技有限公司 Display method and electronic device

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023065783A1 (en) * 2021-10-18 2023-04-27 花瓣云科技有限公司 Display method and electronic device
CN114282561A (en) * 2021-12-23 2022-04-05 珠海格力电器股份有限公司 Code identification display method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
EP3693911B1 (en) Card linking method and terminal
CN110705983B (en) Method, device, equipment and storage medium for code scanning payment processing
JP6997343B2 (en) How to quickly open an application or application function, and a terminal
EP3096275B1 (en) Mobile terminal and method for controlling the same
CN109074571B (en) Transaction method and device based on Near Field Communication (NFC)
EP4307198A2 (en) Card binding method and terminal
CN113034226B (en) Live broadcast data processing method and device, electronic equipment, medium and product
CN108629579B (en) Payment method and mobile terminal
US20160092668A1 (en) Methods and devices for authorizing operation
US20170024736A1 (en) Mobile terminal and method for controlling the same
CN112734416A (en) Secure payment method and mobile terminal
CN112837057A (en) Method for preventing payment code from being stolen, terminal equipment and computer readable storage medium
CN111523871B (en) Payment processing method and electronic equipment
CN111723843B (en) Sign-in method, sign-in device, electronic equipment and storage medium
CN112967043A (en) Resource transfer method, device, equipment and storage medium
KR101867450B1 (en) Mobile terminal, server, payment systetm and method for payment based on identification code
CN110458563B (en) Display interface processing method and device, electronic equipment and readable storage medium
CN111831385A (en) Business credit information processing method, device, equipment and storage medium
CN108322519B (en) Page pushing processing method, mobile terminal and computer readable storage medium
CN110738491A (en) Numerical value transferring method, system, device, terminal and storage medium
CN112036887A (en) Resource transfer method, device, equipment and storage medium
CN108229149B (en) Data protection method and device
CN110956469A (en) Payment method, device, equipment and storage medium
CN111047328B (en) Mobile payment method, device, system and storage medium
CN112764824B (en) Method, device, equipment and storage medium for triggering identity verification in application program

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination