Payment method, intelligent terminal and storage medium

By generating identification codes in the payment APP in response to preset payment conditions, users can realize delayed payment and third-party payment, solving the problem of insufficient payment convenience in the existing technology and improving the payment experience.

CN119444210APending Publication Date: 2025-02-14SHANGHAI TRANSSION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411527009.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-29
Publication Date
2025-02-14

AI Technical Summary

Technical Problem

When paying for bills in existing payment apps, users can only confirm payment by entering their payment account number and payment password, which cannot meet the needs of delayed payment and third-party payment, reducing payment convenience.

Method used

By responding to preset payment conditions, the smart terminal determines or generates an identification code, and the user can make delayed payment and third-party payment based on the identification code.

Benefits of technology

It realizes delayed payment and third-party payment functions, improves user payment convenience, and solves the problem of being unable to pay when the network is poor or without signals.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119444210A_ABST
    Figure CN119444210A_ABST
Patent Text Reader

Abstract

The invention provides a payment method, an intelligent terminal and a storage medium, and the payment method can be applied to the intelligent terminal, and comprises the steps: responding to a preset payment condition, determining or generating an identification code, and paying a to-be-paid bill based on the identification code. According to the technical scheme, when the preset payment condition is met, the intelligent terminal can determine or generate the identification code, the user can pay the bill to be paid based on the identification code, and the payment requirement under the preset payment condition can be met; therefore, the payment convenience of the user can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] Currently, due to technical limitations, when users use payment apps to pay bills, they can usually only confirm payment by entering the payment account number and the payment password of the payment app. This cannot meet the user's other payment needs, reducing the user's payment convenience.

[0003] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Summary of the invention

[0004] In response to the above technical problems, the present application provides a payment method, a smart terminal and a storage medium, so that users can realize delayed payment and / or third-party payment, thereby improving the payment convenience of users.

[0005] The present application provides a payment method, which can be applied to a smart terminal, including:

[0006] S10: In response to satisfying a preset payment condition, determining or generating an identification code to pay the bill to be paid based on the identification code.

[0007] Optionally, the preset payment condition includes at least one of the following:

[0008] The need for delayed payment is detected;

[0009] It is detected that payment is required by the second smart terminal.

[0010] Optionally, the detecting that payment needs to be delayed includes at least one of the following:

[0011] Network delay detected;

[0012] Signal interruption detected;

[0013] In response to a selection operation for a deferred payment method.

[0014] Optionally, after step S10, at least one of the following items is further included:

[0015] storing the identification code locally to perform delayed payment based on the identification code;

[0016] The identification code is sent to the second smart terminal, so that the second smart terminal makes payment based on the identification code.

[0017] Optionally, the method further comprises:

[0018] In response to not meeting the preset payment condition, a prompt message is output based on the payment information corresponding to the bill to be paid.

[0019] Optionally, after step S10, the method further includes:

[0020] In response to a scanning operation on the identification code, prompt information is output.

[0021] Optionally, the output prompt information includes at least one of the following:

[0022] Output the prompt information for checking the account information;

[0023] Output payment failure prompt information.

[0024] Optionally, the payment information includes at least one of a payee account and a payee location.

[0025] Optionally, the identification code carries preset usage restriction information.

[0026] Optionally, the preset usage restriction information includes at least one of a payer's location, a payee's location, a payment amount, a number of times the identification code is used, and a receiving account.

[0027] Optionally, the prompt information for outputting the verification account information includes at least one of the following:

[0028] If the receiving account does not exist in the local historical payment record, output a prompt message for verifying the account information of the receiving account;

[0029] If the receiving account exists in the local historical payment record, determine whether the receiving party location is the same as the historical location corresponding to the receiving account recorded in the historical payment record; if not, output prompt information for verifying the account information of the receiving account;

[0030] If the receiving account exists in the local historical payment record, a target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output;

[0031] If the local location is different from the payer's location, a prompt message for verifying the account information of the receiving account is output.

[0032] Optionally, the prompt information of outputting payment failure includes:

[0033] If the location of the local smart terminal is different from the location of the payer, a prompt message indicating payment failure is output;

[0034] If the current usage count of the identification code is greater than the usage count of the identification code, a prompt message indicating payment failure is output.

[0035] Optionally, after step S10, the method further includes:

[0036] In response to a preset modification condition, modifying the preset usage restriction information;

[0037] And / or, the preset modification condition includes at least one of the following:

[0038] Payment failure is detected and payment needs to be continued;

[0039] An editing operation on the preset usage restriction information is detected.

[0040] The present application also provides a smart terminal, comprising: a memory and a processor, wherein a payment program is stored in the memory, and when the payment program is executed by the processor, the steps of any of the above-mentioned payment methods are implemented.

[0041] The present application also provides a storage medium, wherein the storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above payment methods are implemented.

[0042] As described above, the payment method of the present application can be applied to a smart terminal, including: in response to meeting a preset payment condition, determining or generating an identification code to pay the bill to be paid based on the identification code. Through the technical solution of the present application, when the preset payment condition is met, the smart terminal will determine or generate an identification code, and the user can pay the bill to be paid based on the identification code, which can meet the payment requirements under the preset payment conditions; therefore, the present application can improve the payment convenience of users. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the description of the embodiments are briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor.

[0044] Figure 1 A schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0045] Figure 2 A communication network system architecture diagram provided for an embodiment of the present application;

[0046] Figure 3 is a schematic diagram of a payment method according to the first embodiment;

[0047] Figure 4 is a specific flow chart of delayed payment or payment by a second smart terminal according to the payment method shown in the second embodiment;

[0048] Figure 5 It is a specific flow chart of ordinary payment according to the payment method shown in the first embodiment.

[0049] The realization of the purpose, functional features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The above-mentioned drawings have shown clear embodiments of this application, which will be described in more detail later. These drawings and textual descriptions are not intended to limit the scope of the concept of this application in any way, but to illustrate the concept of this application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0050] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0051] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0052] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of" or "when" or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising" and "including" indicate that there are the described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or", "and / or", "including at least one of the following" etc. used in this application can be interpreted as inclusive, or mean any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”, and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will only occur when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0053] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

[0054] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting", depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to determining" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)", depending on the context.

[0055] It should be noted that in this article, step codes such as S10 and S20 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence. When implementing the step, those skilled in the art may execute S20 first and then S10, etc., but these should all be within the scope of protection of this application.

[0056] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0057] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0058] The smart terminal may be implemented in various forms. For example, the smart terminal described in this application may include smart terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminals such as digital TVs and desktop computers.

[0059] The following description will be made by taking a mobile terminal as an example, and those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the construction according to the embodiments of the present application can also be applied to fixed-type terminals.

[0060] See also Figure 1 , which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application, the mobile terminal 100 may include: RF (Radio Frequency, radio frequency) unit 101, WiFi module 102, audio output unit 103, A / V (audio / video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111 and other components. Those skilled in the art can understand that Figure 1 The structure of the mobile terminal shown in the figure does not constitute a limitation on the mobile terminal. The mobile terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0061] Combine the following Figure 1 The following is a detailed introduction to the various components of the mobile terminal:

[0062] The radio frequency unit 101 can be used for receiving and sending signals during information transmission or communication. Specifically, after receiving the downlink information of the base station, it is sent to the processor 110 for processing; in addition, the uplink data is sent to the base station. Generally, the radio frequency unit 101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 101 can also communicate with the network and other devices through wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G and 6G, etc.

[0063] WiFi is a short-range wireless transmission technology. Mobile terminals can help users send and receive emails, browse web pages, and access streaming media through WiFi module 102. It provides users with wireless broadband Internet access. Figure 1 The WiFi module 102 is shown, but it is understandable that it is not an essential component of the mobile terminal and can be omitted as needed without changing the essence of the invention.

[0064] The audio output unit 103 can convert the audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, etc. Moreover, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, etc.

[0065] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processor (GPU) 1041 and a microphone 1042, and the graphics processor 1041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 106. The image frame processed by the graphics processor 1041 can be stored in the memory 109 (or other storage medium) or sent via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 can receive sound (audio data) via the microphone 1042 in a telephone call mode, a recording mode, a voice recognition mode, and other operating modes, and can process such sound into audio data. The processed audio (voice) data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 101 in the case of a telephone call mode. The microphone 1042 can implement various types of noise elimination (or suppression) algorithms to eliminate (or suppress) noise or interference generated in the process of receiving and sending audio signals.

[0066] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can also be configured on the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0067] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0068] The user input unit 107 can be used to receive input digital or character information, and generate key signal input related to user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by users using fingers, styluses, or any other suitable objects or accessories on or near the touch panel 1071), and drive corresponding connection devices according to a pre-set program. The touch panel 1071 may include a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact point coordinates, and then sends it to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, a function key (such as a volume control key, a switch key, etc.), a trackball, a mouse, a joystick, etc., which are not specifically limited here.

[0069] Optionally, the touch panel 1071 may cover the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. Then, the processor 110 provides corresponding visual output on the display panel 1061 according to the type of touch event. Figure 1 In the figure, the touch panel 1071 and the display panel 1061 are used as two independent components to implement the input and output functions of the mobile terminal. However, in some embodiments, the touch panel 1071 and the display panel 1061 can be integrated to implement the input and output functions of the mobile terminal, which is not limited here.

[0070] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

[0071] The memory 109 can be used to store software programs and various data. The memory 109 can mainly include a program storage area and a data storage area. Optionally, the program storage area can 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 can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0072] The processor 110 is the control center of the mobile terminal. It uses various interfaces and lines to connect various parts of the entire mobile terminal. It executes various functions of the mobile terminal and processes data by running or executing software programs and / or modules stored in the memory 109, and calling data stored in the memory 109, so as to monitor the mobile terminal as a whole. The processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor. Optionally, the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 110.

[0073] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0074] although Figure 1 Not shown, the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0075] In order to facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0076] See also Figure 2 , Figure 2 A communication network system architecture diagram is provided for an embodiment of the present application, wherein the communication network system is an LTE system of universal mobile communication technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203 and an operator's IP service 204, which are connected in sequence for communication.

[0077] Optionally, UE201 may be the above-mentioned terminal 100, which will not be described in detail here.

[0078] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 , etc. Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface), and eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide UE 201 with access to EPC 203 .

[0079] EPC203 may include MME (Mobility Management Entity) 2031, HSS (Home Subscriber Server) 2032, other MMEs 2033, SGW (Serving Gate Way) 2034, PGW (PDN Gate Way) 2035 and PCRF (Policy and Charging Rules Function) 2036, etc. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, and provides bearer and connection management. HSS 2032 is used to provide some registers to manage functions such as home location register (not shown in the figure), and store some user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, which selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0080] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem) or other IP services.

[0081] Although the above introduction takes the LTE system as an example, those skilled in the art should know that the present application is not only applicable to the LTE system, but also to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., without limitation here.

[0082] Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

[0083] First embodiment

[0084] The present application embodiment provides a payment method, including:

[0085] Step S10: In response to satisfying a preset payment condition, determining or generating an identification code to pay the bill to be paid based on the identification code.

[0086] Optionally, the payment method may be applied to a smart terminal.

[0087] Optionally, the smart terminal may be a mobile terminal such as a mobile phone or a tablet.

[0088] Optionally, the mobile phone can be a double-sided screen terminal or a folding screen terminal.

[0089] The application scenario of this embodiment can be to use the payment APP to pay bills. When the preset payment conditions are met, the smart terminal will determine or generate an identification code, and the user can pay the bill based on the identification code, which can meet the payment needs under the preset payment conditions, thereby improving the user's payment convenience.

[0090] Optionally, the steps are as follows:

[0091] Step S10: in response to satisfying a preset payment condition, determining or generating an identification code to pay the bill to be paid based on the identification code;

[0092] Optionally, the identification code may be a static identification code or a dynamic identification code, specifically, a static QR code, a static barcode, a dynamic QR code, a dynamic barcode, etc., without specific limitation.

[0093] Optionally, the identification code is generated when a preset payment condition is met.

[0094] Optionally, the identification code is used to provide payment information for a bill to be paid.

[0095] Optionally, the identification code may be determined or generated based on payment information of the bill to be paid.

[0096] Optionally, the payment information includes payment account, payment amount, etc.

[0097] Optionally, the user can pay the bill by scanning the identification code.

[0098] Optionally, when a user uses a payment app to pay a bill, if the preset payment conditions are met, the user can pay the bill using the identification code.

[0099] Optionally, when a user uses a payment app to pay a bill, if the preset payment conditions are not met, the user can pay the bill by entering his or her payment app payment password.

[0100] Optionally, when determining or generating a bill to be paid, it may be determined whether a preset payment condition is met.

[0101] Optionally, the bill to be paid may be determined or generated when the payment account number is entered in the payment APP.

[0102] Optionally, refer to Figure 4 , after clicking Start Payment in the payment app, confirm or generate the bill to be paid to determine whether the preset payment conditions are met.

[0103] Optionally, the preset payment condition includes at least one of the following:

[0104] The need for delayed payment is detected;

[0105] It is detected that payment is required by the second smart terminal.

[0106] Optionally, when a need for delayed payment is detected, an identification code is determined or generated.

[0107] Optionally, since the traditional payment method of entering the payment account number and payment APP payment password usually needs to be completed immediately, if it is not convenient for the user to obtain the payment APP payment password at present, the payment cannot be completed immediately. In this scenario, the user can be provided with a delayed payment function by determining or generating an identification code to meet the user's payment needs.

[0108] Optionally, refer to Figure 4 , it can be that after clicking to start payment in the payment APP, the bill to be paid is determined or determined or generated, and it is determined whether payment needs to be delayed and / or whether payment needs to be made by the second smart terminal.

[0109] Optionally, the detecting that payment needs to be delayed includes at least one of the following:

[0110] Network delay detected;

[0111] Signal interruption detected;

[0112] In response to a selection operation for a deferred payment method.

[0113] It should be noted that when using a payment app to make a payment, it is usually necessary to use USSD (Unstructured Supplementary Service Data, a standard communication protocol for sending text messages) signaling to obtain the payment password of the payment app. Since this method requires a stable network connection to send and receive information, when the network is poor or there is no signal, the USSD session will not be established, and the payment password of the payment app cannot be obtained immediately through USSD signaling, resulting in the inability to complete the payment.

[0114] Optionally, when a network delay is detected, it is determined that payment needs to be delayed and an identification code is determined or generated.

[0115] Optionally, when a signal interruption is detected, it is determined that payment needs to be delayed and an identification code is determined or generated.

[0116] Optionally, when using a payment APP to make a payment, multiple payment methods can be displayed on the page for determining or generating the bill to be paid, for example, displaying the ordinary payment method (a method of obtaining the payment password of the payment APP through USSD signaling), displaying the delayed payment method, and / or displaying the method that needs to be paid by a second smart terminal (a method of payment on behalf of others), etc.

[0117] Optionally, in response to a selection operation for a delayed payment method, it is determined that delayed payment is required, and an identification code is determined or generated.

[0118] Optionally, the user can select a corresponding payment method through touch operation or key operation.

[0119] Optionally, in response to the selection operation for the payment method by the second smart terminal, it is determined that the payment needs to be made by the second smart terminal, and an identification code is determined or generated (refer to Figure 4 If payment or delayed payment is required by the second smart terminal, an identification code (payment information QR code) is determined or generated.

[0120] Optionally, in response to the selection operation for the common payment method, obtain the payment password of the payment APP and complete the payment (refer to Figure 4 , if the second smart terminal does not need to pay (other people help pay) or delay payment (delayed payment), the payment is completed).

[0121] Optionally, after step S10, at least one of the following items a1-a2 is further included:

[0122] a1, storing the identification code locally to perform delayed payment based on the identification code.

[0123] Optionally, when it is detected that a delayed payment is required, an identification code is determined or generated, the identification code is stored locally, and reference is made to Figure 4 .

[0124] Optionally, after the identification code is stored locally, payment reminder information is sent out regularly to prevent the user from forgetting to delay payment.

[0125] Optionally, when the user delays payment, the identification code can be obtained locally, so as to complete the delayed payment based on the identification code.

[0126] a2. Send the identification code to the second smart terminal, so that the second smart terminal can make payment based on the identification code.

[0127] Optionally, when it is detected that payment is required by the second smart terminal, an identification code is determined or generated, and the identification code is sent to the second smart terminal. Figure 4 .

[0128] For example, when mobile phone A detects that payment needs to be made by the second smart terminal, it determines or generates an identification code and sends the identification code to mobile phone B. Mobile phone B can then pay the bill based on the identification code to realize payment on behalf of the user.

[0129] In this embodiment, when the user uses the payment APP to pay the bill, the smart terminal determines or generates an identification code in response to meeting the preset payment conditions, so as to pay the bill to be paid based on the identification code. Through the above technical solution, when the preset payment conditions are met, the smart terminal will determine or generate an identification code, and the user can pay the bill to be paid based on the identification code, which can meet the payment needs under the preset payment conditions; specifically, it can meet the user's delayed payment needs, payment needs for others, etc., solve the problem of being unable to pay when the network is poor or there is no signal, and can automatically generate an identification code containing payment information, which is convenient for users to realize delayed payment and payment on behalf of others, and improves the convenience of users' payment.

[0130] Second embodiment

[0131] Based on the first embodiment of the present application, another embodiment of the present application is provided. In this embodiment, a method of ensuring payment security when a user uses an ordinary payment method to make a payment is discussed.

[0132] The method further comprises:

[0133] Step b1: In response to not meeting the preset payment condition, outputting a prompt message based on the payment information corresponding to the bill to be paid.

[0134] Optionally, when determining or generating a bill to be paid, it may be determined whether a preset payment condition is met. If the preset payment condition is not met, a prompt message is output based on the payment information corresponding to the bill to be paid.

[0135] Optionally, when no network delay is detected, no signal interruption is detected, no user selection operation for a delayed payment method is detected, and no user selection operation for a payment method by a second smart terminal is detected, it is determined that the preset payment condition is not met.

[0136] Optionally, when a selection operation of a user for a common payment method is detected, it is determined that the preset payment condition is not met.

[0137] Optionally, in response to not meeting the preset payment conditions, the smart terminal determines that ordinary payment is required, and outputs a prompt message based on the payment information corresponding to the bill to be paid.

[0138] Alternatively, the payment information may be determined when the bill to be paid is determined or generated.

[0139] Optionally, the payment information may be determined when the bill to be paid is determined or generated and displayed in the interface.

[0140] Optionally, after the user selects a normal payment method, he or she will see a prompt message.

[0141] Optionally, the payment information includes at least one of a payee account and a payee location.

[0142] Optionally, the receiving account in the payment information may be input by the user.

[0143] Optionally, the payee's location in the payment information may be input by the user, or may be obtained through positioning during face-to-face payment.

[0144] Optionally, based on the payment information corresponding to the bill to be paid, the output prompt information includes at least one of the following:

[0145] Output the prompt information for checking the account information;

[0146] Output payment failure prompt information.

[0147] Optionally, in response to the user's confirmation operation on the prompt information for verifying the account information, the payment is completed.

[0148] Optionally, in response to the user's denial of the prompt information for verifying the account information, the user returns to the payment page and can modify the payment information on the payment page.

[0149] Optionally, in response to the user's confirmation operation on the prompt information of payment failure, return to the payment page.

[0150] Optionally, based on the payment information corresponding to the bill to be paid, the output prompt information for verifying the account information includes at least one of the following:

[0151] If the receiving account does not exist in the local historical payment record, output a prompt message for verifying the account information of the receiving account;

[0152] If the receiving account exists in the local historical payment record, determine whether the receiving party location is the same as the historical location corresponding to the receiving account recorded in the historical payment record; if not, output prompt information for verifying the account information of the receiving account;

[0153] If the receiving account exists in the local historical payment record, the target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output.

[0154] Optionally, in the process of payment using a common payment method, in order to ensure payment security, when payment is made to a new account, a prompt message for verifying the account information of the receiving account may be output to remind the user to confirm the account information.

[0155] Optionally, if the receiving account does not exist in the local historical payment record, the receiving account is considered to be a new account, and a prompt message for verifying the account information of the receiving account can be output to avoid payment errors caused by incorrect user account input.

[0156] Optionally, in the process of payment using ordinary payment methods, in order to further improve payment security, after confirming that the receiving account is not a new account, it is also possible to determine whether the location of the receiving account has changed. If it has changed, the user needs to be reminded to confirm the account information.

[0157] Optionally, if the receiving account exists in the local historical payment record, it is determined whether the receiving party location is the same as the historical location corresponding to the receiving account recorded in the historical payment record. If not, a prompt message for verifying the account information of the receiving account is output, referring to Figure 5 .

[0158] Optionally, in the process of face-to-face payment (face-to-face operation during normal payment), in order to improve payment efficiency, the location of the payee can be obtained by locating the local smart terminal, and the target account can be automatically matched from the historical payment records and automatically filled into the account input field, without the need for manual input by the user, thereby improving the user experience.

[0159] Optionally, if the receiving account exists in the local historical payment record, the target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output.

[0160] Optionally, based on the payment information corresponding to the bill to be paid, the output prompt information of payment failure may be: the corresponding payment account of the bill to be paid does not exist, the corresponding payment party location of the bill to be paid does not exist, etc.

[0161] In this embodiment, when the user adopts the ordinary payment method, the smart terminal verifies the payment account and / or the location of the payee, and reminds the user to check the payment account, thereby improving payment security; at the same time, it can automatically match and fill in account information based on the location of the payee, thereby improving user payment efficiency.

[0162] Third embodiment

[0163] Based on the first embodiment and the second embodiment of the present application, another embodiment of the present application is provided. In this embodiment, it is discussed how to ensure payment security when the user adopts a delayed payment method or a payment method on behalf of another person to make a payment.

[0164] After step S10, the method further includes:

[0165] Step c1: outputting prompt information in response to a scanning operation on the identification code.

[0166] Optionally, the user can scan a local identification code.

[0167] Optionally, the user may scan the identification code sent by the second smart terminal.

[0168] Optionally, the local identification code may be stored in the payment APP or in a local photo album.

[0169] Optionally, the identification code sent by the second smart terminal may be the one stored in the payment APP.

[0170] Optionally, the user scans the identification code to see the prompt information.

[0171] Optionally, the identification code carries preset usage restriction information.

[0172] Optionally, the preset usage restriction information includes at least one of a payer's location, a payee's location, a payment amount, a number of times the identification code is used, and a receiving account.

[0173] Optionally, the preset usage restriction information may include the payment amount, the number of times the identification code is used, and the payment account may be input by the user.

[0174] Optionally, the payer's location and the payee's location in the preset usage restriction information may be input by the user, or may be obtained through positioning during face-to-face payment.

[0175] Optionally, after scanning the identification code, the user can see at least one of the payer's location, payee's location, payment amount, number of times the identification code is used, and receiving account, so that the user can check the information by himself and confirm whether payment can be made.

[0176] Optionally, in response to a scanning operation on the identification code, the output prompt information includes at least one of the following:

[0177] Output the prompt information for checking the account information;

[0178] Output payment failure prompt information.

[0179] Optionally, in response to the scanning operation on the identification code, the output prompt information for verifying the account information includes at least one of the following:

[0180] If the receiving account does not exist in the local historical payment record, output a prompt message for verifying the account information of the receiving account;

[0181] If the receiving account exists in the local historical payment record, a target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output;

[0182] If the receiving account exists in the local historical payment record, determine whether the receiving party location is the same as the historical location corresponding to the receiving account recorded in the historical payment record; if not, output prompt information for verifying the account information of the receiving account;

[0183] If the local location is different from the payer's location, a prompt message for verifying the account information of the receiving account is output.

[0184] Optionally, in the process of delayed payment or payment by the second smart terminal, in order to ensure payment security, a prompt message for verifying the account information of the receiving account can be output when payment is made to a new account to remind the user to confirm the account information.

[0185] Optionally, if the receiving account does not exist in the local historical payment record, the receiving account is considered to be a new account, and a prompt message for verifying the account information of the receiving account can be output to avoid payment errors caused by incorrect user account input.

[0186] Optionally, in the process of delayed payment or payment by the second smart terminal, in order to further improve payment security, after confirming that the receiving account is not a new account, it is also possible to determine whether the location of the receiving account has changed. If it has changed, the user needs to be reminded to confirm the account information.

[0187] Optionally, if the receiving account exists in the local historical payment record, it is determined whether the payee location is the same as the historical location corresponding to the receiving account recorded in the historical payment record. If not, a prompt message for verifying the account information of the receiving account is output.

[0188] Optionally, in the process of delayed payment or payment by a second smart terminal, in order to improve payment efficiency, the location of the payee can be obtained by scanning the identification code, and the target account can be automatically matched from the historical payment records and automatically filled into the account input field, without the need for manual input by the user, thereby improving the user experience.

[0189] Optionally, if the receiving account exists in the local historical payment record, the target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output.

[0190] Optionally, during the process of delayed payment performed locally by the smart terminal, in order to ensure payment security, the local location can be obtained by locating the local smart terminal, and the location of the payer can be obtained by scanning the identification code to avoid local payment errors.

[0191] Optionally, if the local location is different from the payer's location, a prompt message is output to verify the account information of the receiving account, referring to Figure 4 .

[0192] Optionally, in response to the scanning operation on the identification code, the payment failure prompt information output includes:

[0193] If the location of the local smart terminal is different from the location of the payer, a prompt message indicating payment failure is output;

[0194] If the current usage count of the identification code is greater than the usage count of the identification code, a prompt message indicating payment failure is output.

[0195] Optionally, after scanning the identification code, if the location of the local smart terminal is different from the location of the payee, a prompt message indicating payment failure is output. Figure 4 .

[0196] Optionally, after scanning the identification code, the current number of times the identification code is used and the number of times the identification code is used in the preset usage restriction information are obtained. In order to avoid leakage of the identification code information after being used multiple times, the local smart terminal can determine whether the current number of times the identification code is used is greater than the number of times the identification code is used. If it is greater, a prompt message of payment failure is output; if it is less than or equal to, it is determined that the user can continue to use it.

[0197] Optionally, after step S10, the method further includes:

[0198] Step d1: In response to a preset modification condition, modify the preset usage restriction information.

[0199] Optionally, after determining or generating the identification code, the local intelligent terminal may need to modify the preset usage restriction information, and therefore, in response to a preset modification condition, the preset usage restriction information is modified.

[0200] Optionally, the preset modification condition includes at least one of the following:

[0201] Payment failure is detected and payment needs to be continued;

[0202] An editing operation on the preset usage restriction information is detected.

[0203] Optionally, after scanning the identification code locally, if payment failure is detected and payment needs to be continued, the preset usage restriction information can be modified.

[0204] Optionally, after scanning the identification code locally, if the location of the local smart terminal is different from the location of the payee, but the user confirms that he needs to continue paying the bill corresponding to the identification code, the preset usage restriction information can be modified.

[0205] Optionally, after scanning the identification code locally, if the location of the local smart terminal is different from the location of the payer or the current usage count of the identification code is greater than the usage count of the identification code, but the user confirms the need to continue to delay payment of the bill to be paid corresponding to the identification code, the local smart terminal can modify the preset usage restriction information.

[0206] Optionally, after scanning the identification code locally, if the location of the local smart terminal is different from the payee's location or the current number of times the identification code is used is greater than the number of times the identification code is used, but the user confirms that he needs to continue paying the bill corresponding to the identification code, the local smart terminal can send the payee's location or the number of times the identification code is used that needs to be modified to the second smart terminal, and the second smart terminal can modify the preset usage restriction information.

[0207] Optionally, after scanning the identification code locally, if the user wants to modify the preset usage restriction information, the user can directly edit the identification code in the delayed payment bill or the payment bill. When the smart terminal detects the editing operation on the preset usage restriction information, it can modify the preset usage restriction information.

[0208] Optionally, if a static identification code is generated in response to meeting preset payment conditions, when payment failure is detected and payment needs to be continued, a new static identification code can be generated based on the usage restriction information that needs to be modified and saved to the local smart terminal or sent to a second smart terminal.

[0209] Optionally, if a dynamic identification code is generated by the QR code management platform in response to meeting preset payment conditions, when a payment failure is detected and payment needs to be continued, the usage restriction information that needs to be modified can be sent to the QR code management platform. The QR code management platform modifies the usage restriction information of the dynamic identification code and sends it to the local smart terminal or the second smart terminal.

[0210] In this embodiment, when the user adopts the delayed payment method or the payment method through the second smart terminal, the smart terminal verifies the preset usage restriction information and reminds the user to check the receiving account to improve payment security; and it can automatically match and fill in account information based on the location of the payee to improve user payment efficiency; it can also modify the preset usage restriction information when necessary to improve payment convenience.

[0211] Optionally, in actual implementation, combination judgment may also be performed according to actual conditions, as shown in the following Table 1.

[0212] Table 1

[0213]

[0214] For example, for combination example 1, step S10 can be determined as a technical solution in conjunction with a response condition (such as when a preset payment condition is met) and a payment method (such as delayed payment).

[0215] Optionally, the corresponding technical solution is: in response to satisfying a preset payment condition, determining or generating an identification code, storing the identification code locally, and performing delayed payment based on the identification code.

[0216] For another example, for combination example 2, the response condition (such as when the preset payment condition is met) and the payment method (such as payment by the second smart terminal) and step S10 can be determined as a technical solution.

[0217] Optionally, the corresponding technical solution is: in response to satisfying a preset payment condition, determining or generating an identification code, and sending the identification code to the second smart terminal, so that the second smart terminal makes payment based on the identification code.

[0218] For example, for combination example 3, the response condition (such as when the preset payment condition is not met) and the payment method (such as ordinary payment) can be determined as the technical solution.

[0219] Optionally, the corresponding technical solution is: in response to not meeting the preset payment conditions, determining the payment method as ordinary payment, and completing the payment by entering the payment account number and password.

[0220] Through the combined solution, a target application or target service can be determined more accurately and / or intelligently from multiple applications or services, thereby improving user experience.

[0221] The above examples are only reference examples. In order to avoid redundancy, they are not listed one by one here. In actual development or application, they can be flexibly combined according to actual needs, but any combination belongs to the technical solution of this application and is covered within the scope of protection of this application.

[0222] An embodiment of the present application also provides an intelligent terminal, including a memory and a processor, wherein a payment program is stored in the memory, and when the payment program is executed by the processor, the steps of the payment method in any of the above embodiments are implemented.

[0223] The present application also provides a storage medium on which a payment program is stored. When the payment program is executed by a processor, the steps of the payment method in any of the above embodiments are implemented.

[0224] In the embodiments of the smart terminal and storage medium provided in the present application, all technical features of any of the above-mentioned payment method embodiments may be included, and the expanded and explained contents of the specification are basically the same as those of the embodiments of the above-mentioned methods, and will not be repeated here.

[0225] The embodiment of the present application further provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer executes the methods in the above various possible implementation modes.

[0226] An embodiment of the present application also provides a chip, including a memory and a processor, the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device equipped with the chip executes the methods in various possible implementation modes as described above.

[0227] It is understood that the above scenarios are only examples and do not constitute a limitation on the application scenarios of the technical solutions provided in the embodiments of the present application. The technical solutions of the present application can also be applied to other scenarios. For example, it is known to those skilled in the art that with the evolution of the system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0228] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0229] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0230] The units in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0231] In the present application, the same or similar terminology concepts, technical solutions and / or application scenario descriptions are generally described in detail only the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of the present application, for the same or similar terminology concepts, technical solutions and / or application scenario descriptions that are not described in detail later, reference can be made to the previous related detailed descriptions.

[0232] In the present application, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0233] The various technical features of the technical solution of the present application can be arbitrarily combined. In order to make the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of the present application.

[0234] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as above, and includes several operations to enable a terminal device (which can be a mobile phone, a computer, a server, a controlled terminal, or a network device, etc.) to execute the method of each embodiment of the present application.

[0235] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer operations. When the computer program operation is loaded and executed on the computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer operation can be stored in a storage medium, or transmitted from one storage medium to another storage medium. For example, the computer operation can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk SolidState Disk (SSD)), etc.

[0236] The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A payment method, characterized in that: include: S10: In response to satisfying a preset payment condition, determining or generating an identification code to pay the bill to be paid based on the identification code.

2. The method according to claim 1, characterized in that The preset payment conditions include at least one of the following: The need for delayed payment is detected; It is detected that payment is required by the second smart terminal.

3. The method according to claim 2, characterized in that The detection of the need for delayed payment includes at least one of the following: Network delay detected; Signal interruption detected; In response to a selection operation for a deferred payment method.

4. The method according to claim 2, characterized in that After step S10, at least one of the following items is also included: storing the identification code locally to perform delayed payment based on the identification code; The identification code is sent to the second smart terminal, so that the second smart terminal makes payment based on the identification code.

5. The method according to claim 1, characterized in that The method further comprises: In response to not meeting the preset payment condition, outputting a prompt message based on the payment information corresponding to the bill to be paid; And / or, after step S10, the method further includes: In response to a scanning operation on the identification code, outputting prompt information; And / or, the output prompt information includes at least one of the following: Output the prompt information for checking the account information; Output payment failure prompt information.

6. The method according to claim 5, characterized in that The payment information includes at least one of a payment recipient account and a payment recipient location; and / or, the identification code carries preset usage restriction information; And / or, the preset usage restriction information includes at least one of a payer's location, a payee's location, a payment amount, a number of times the identification code is used, and a receiving account.

7. The method according to claim 6, characterized in that The outputting of the prompt information for verifying the account information includes at least one of the following: If the receiving account does not exist in the local historical payment records, output a prompt message for verifying the account information of the receiving account; If the receiving account exists in the local historical payment record, determine whether the receiving party location is the same as the historical location corresponding to the receiving account recorded in the historical payment record; if not, output prompt information for verifying the account information of the receiving account; If the receiving account exists in the local historical payment record, a target account is matched from the historical payment record based on the location of the payee, and prompt information for verifying the account information of the target account is output; If the local location is different from the payer's location, outputting a prompt message for verifying the account information of the receiving account; And / or, the output payment failure prompt information includes: If the location of the local smart terminal is different from the location of the payer, a prompt message indicating payment failure is output; If the current usage count of the identification code is greater than the usage count of the identification code, a prompt message indicating payment failure is output.

8. The method according to claim 6, characterized in that After step S10, the method further includes: In response to a preset modification condition, modifying the preset usage restriction information; And / or, the preset modification condition includes at least one of the following: Payment failure is detected and payment needs to be continued; An editing operation on the preset usage restriction information is detected.

9. An intelligent terminal, characterized in that: include: A memory and a processor, wherein a payment program is stored in the memory, and when the payment program is executed by the processor, the steps of the payment method as described in any one of claims 1 to 8 are implemented.

10. A storage medium, characterized in that: The storage medium stores a computer program, which, when executed by a processor, implements the steps of the payment method according to any one of claims 1 to 8.