Content query method and device, equipment and storage medium

Abstract

The embodiment of the invention relates to an electronic payment method and device, equipment and a storage medium. The method comprises the steps that in response to a payment request in a first application, a web payment page provided by a second application is presented, and the web payment page presents multiple preset payment modes; in response to the received selection of a target payment mode in the multiple preset payment modes, presenting an authentication page associated with the target payment mode; acquiring authentication information associated with the target payment mode through the authentication page; and in response to the verification of the authentication information, triggering to complete the payment request through the target payment mode. In this way, the payment efficiency of the user can be improved.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, devices, apparatuses, and computer-readable storage media for electronic payment. Background Art

[0002] In recent years, with the development of the Internet, users have an increasing demand for online payments. However, in the process of cross-terminal payment, users need to go through a cumbersome login process before they can continue to pay, resulting in low payment efficiency for users. Summary of the invention

[0003] In a first aspect of the present disclosure, a method for electronic payment is provided, comprising: in response to a payment request within a first application, presenting a web payment page provided by a second application, the web payment page presenting a plurality of preset payment methods; in response to receiving a selection of a target payment method from the plurality of preset payment methods, presenting an authentication page associated with the target payment method; obtaining authentication information associated with the target payment method via the authentication page; and in response to the authentication information being verified, triggering completion of the payment request through the target payment method.

[0004] In a second aspect of the present disclosure, a device for electronic payment is provided. The device includes: a presentation module configured to, in response to receiving a query request, obtain rich text information generated by a target model based on the query request, the rich text information indicating a target access address; an authentication module configured to, in response to receiving a selection of a target payment method from among a plurality of preset payment methods, present an authentication page associated with the target payment method; an acquisition module configured to, via the authentication page, obtain authentication information associated with the target payment method; and a payment module configured to, in response to the authentication information being verified, trigger a payment request to be completed through the target payment method.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect or the second aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect or the second aspect.

[0007] It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0009] Figure 1 A schematic diagram showing an example environment in which embodiments according to the present disclosure may be implemented;

[0010] FIG. 2A to FIG. 2F shows an example interface according to some embodiments of the present disclosure;

[0011] FIG. 3A to FIG. 3C shows example interfaces according to still other embodiments of the present disclosure;

[0012] Figure 4 A flowchart illustrating an example process of electronic payment according to some embodiments of the present disclosure;

[0013] Figure 5 A schematic structural block diagram showing an example apparatus for electronic payment according to some embodiments of the present disclosure; and

[0014] Figure 6 A block diagram of an electronic device capable of implementing various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0015] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0016] It should be noted that the titles of any sections / subsections provided herein are not restrictive. Various embodiments are described throughout this article, and any type of embodiment may be included under any section / subsection. In addition, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0018] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects are subject to the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user knows and confirms. Accordingly, when implementing each embodiment of the present disclosure, the type, scope of use, usage scenario, etc. of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method can vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0019] In this specification and the embodiments, if personal information processing is involved, it will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or it is necessary to perform a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0020] As mentioned above, with the development of the Internet, users have an increasing demand for online payments. However, in the process of cross-terminal payment, users need to go through a cumbersome login process before they can continue to pay. For example, when a user is shopping on platform A, he or she can choose the payment service provided by platform B to complete the payment. However, during the payment process, the user needs to log in to the account associated with platform B to complete the payment. Therefore, the cross-terminal payment process is cumbersome and difficult to meet the user's demand for convenient payment, resulting in low payment efficiency for users.

[0021] The embodiment of the present disclosure proposes a scheme for electronic payment. According to the scheme, in response to a payment request in a first application, a web payment page provided by a second application can be presented, and the web payment page presents multiple preset payment methods; in response to receiving a selection of a target payment method among the multiple preset payment methods, an authentication page associated with the target payment method is presented; via the authentication page, authentication information associated with the target payment method is obtained; and in response to the authentication information being verified, the payment request is triggered to be completed through the target payment method.

[0022] In this way, the embodiment of the present disclosure can present a web payment page provided by the second application for the payment request in the first application. Further, the embodiment of the present disclosure can complete the payment request based on the verification of the authentication information of the target payment method in the web payment page. Therefore, the embodiment of the present disclosure can directly verify the authentication information corresponding to the payment method in cross-terminal payment to complete the payment, without logging into the account of the payment application, etc., thereby improving the payment efficiency and meeting the payment needs of the user.

[0023] Various example implementations of the solution are described in detail below in conjunction with the accompanying drawings.

[0024] Example Environment

[0025] Figure 1 1 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, example environment 100 may include electronic device 110 .

[0026] In this example environment 100, the electronic device 110 may run an application 120 that supports interface interaction. The application 120 may be any suitable type of application for interface interaction, examples of which may include, but are not limited to, a commodity application or other suitable applications. The user 140 may interact with the application 120 via the electronic device 110 and / or its attached device.

[0027] exist Figure 1 In the environment 100, if the application 120 is in an active state, the electronic device 110 can present an interface 150 for supporting interface interaction through the application 120.

[0028] In some embodiments, the electronic device 110 communicates with the server 130 to provide services for the application 120. The electronic device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a handheld computer, a portable game terminal, a VR / AR device, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio receiver, an e-book device, a game device, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the electronic device 110 can also support any type of interface for the user (such as a "wearable" circuit, etc.).

[0029] The server 130 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content distribution networks, and big data and artificial intelligence platforms. The server 130 may include, for example, a computing system / server, such as a mainframe, an edge computing node, a computing device in a cloud environment, etc. The server 130 may provide background services for the application 120 that supports interface interaction in the electronic device 110.

[0030] A communication connection may be established between the server 130 and the electronic device 110. The communication connection may be established in a wired manner or a wireless manner. The communication connection may include, but is not limited to, a Bluetooth connection, a mobile network connection, a Universal Serial Bus (USB) connection, a Wireless Fidelity (WiFi) connection, etc., and the embodiments of the present disclosure are not limited in this respect. In the embodiments of the present disclosure, the server 130 and the electronic device 110 may implement signaling interaction through the communication connection between the two.

[0031] It should be understood that the structure and function of each element in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0032] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0033] Example Interaction

[0034] FIG. 2A to FIG. 2F 200A to 200F according to some embodiments of the present disclosure. The interfaces 200A to 200F may be composed of, for example, Figure 1 The electronic device 110 is provided as shown.

[0035] In some embodiments, Figure 2A As shown, the electronic device 110 may present a web payment page 200A provided by the second application.

[0036] In some embodiments, the electronic device 110 may present a payment page provided by a second application in response to a payment request in the first application. As an example, the first application may include an e-commerce application, a video application, or a music application that provides consumer services, etc. The second application may include a payment application that provides payment services, etc.

[0037] In some embodiments, electronic device 110 may present a payment page provided by a second application in response to a payment request within the first application (eg, a payment request for a product within the first application).

[0038] In some embodiments, the payment page may be a web page written in Hypertext Markup Language (HTML), which may be presented independently of the client of the second application, for example. For example, in response to a payment request in the first application, the first application or the local browser of the electronic device 110 may present a corresponding web payment page by accessing the address of the web payment page. Thus, the web payment page may support cross-end payment without installing the second application.

[0039] In some embodiments, continue to refer to Figure 2A In response to not detecting a client associated with the second application, the electronic device 110 may present a web payment page provided by the second application.

[0040] In some embodiments, the payment request within the first application may indicate a first identifier of the target device that initiated the payment request. Further, the electronic device 110 may determine whether the second identifier of the current device (e.g., the electronic device 110) matches the first identifier indicated by the payment request. As an example, the first identifier or the second identifier may include encoding information or name information for indicating the uniqueness of the device, such as the mac address (Media Access Control Address) of the device.

[0041] As an example, the electronic device 110 can present a web payment page provided by the second application using the current device in response to the second identifier matching the first identifier. In this way, the embodiments of the present disclosure can prevent the completion of the payment request from not matching the generation of the payment request, thereby improving the security of network payment.

[0042] Exemplarily, the electronic device 110 may obtain a web payment page provided by the second application based on an interface associated with the second application. As an example, the web payment page may be presented based on a browser application or any other application or interface capable of providing web services.

[0043] As an example, a web page may include multiple elements such as text, pictures, videos, audio, hyperlinks, forms, etc. A web page may be structured based on Hypertext Markup Language (HTML). As an example, a web payment page in the present disclosure may be provided based on HTML5 technology.

[0044] Exemplarily, for security reasons, before the user makes a payment based on the web page provided by the second application, the electronic device 110 needs to obtain authentication information associated with the user for verification. Further, the electronic device 110 may generate cache information associated with the authentication information in response to the authentication information being verified. As an example, the electronic device 110 may generate cache information based on the verified authentication information associated with the second application (also referred to as historical verification information). As an example, the electronic device 110 may store the cache information in a local folder (e.g., a cache folder associated with a browser application) for processing subsequent payment requests. In this way, when the user uses the same device to perform payment activities based on the second application, he only needs to complete the verification process once, thereby improving the user's payment efficiency.

[0045] As an example, historical verification information may include terminal device information (e.g., device information of electronic device 110), web payment page information (e.g., order information) and / or payment account information of the current user associated with the second application (e.g., account number, user identity, etc.), etc.

[0046] In some embodiments, the electronic device 110 may determine whether there is historical authentication information associated with the second application based on the cache information.

[0047] In some embodiments, continue to refer to Figure 2A , the electronic device 110 may present a first web payment page including multiple preset payment methods in response to the absence of historical authentication information. As an example, Figure 2A As shown, the electronic device 110 can preset multiple payment methods 205 in the web payment page 200A (also referred to as the first web payment page 200A). As an example, the multiple preset payment methods 205 may include, for example, a first preset payment method 205-1, a second preset payment method 205-2, a third preset payment method 205-3, and a fourth preset payment method 205-4. As an example, the multiple preset payment methods 205 may include, for example, payment methods corresponding to different bank card service providers, change wallet payment, etc.

[0048] As an example, continue to refer to Figure 2A , the multiple preset payment methods 205 may include multiple default payment methods. In addition, the multiple preset payment methods 205 may also be adjusted based on the user's operation. For example, the electronic device 110 may present a group of candidate payment methods in response to the user's click operation on the add entry 206 in the web payment page 200A. Further, the electronic device 110 may add at least one payment method from the group of candidate payment methods to the multiple preset payment methods 205 based on the user's selection.

[0049] In some embodiments, continue to refer to Figure 2A In response to receiving a selection of a target payment method from among the plurality of preset payment methods 205, the electronic device 110 may present an authentication page associated with the target payment method. As an example, in response to selecting the first payment method 205-1, the electronic device 110 may present an authentication page associated with the first payment method 205-1.

[0050] In some embodiments, Figure 2B As shown, the electronic device 110 can present the authentication page 210 in the web payment page 200B. Further, the electronic device 110 can obtain the authentication information associated with the target payment method via the authentication page 210.

[0051] In some embodiments, the authentication information includes dynamic authentication information associated with the current user.

[0052] In some embodiments, continue to refer to Figure 2B , the electronic device 110 may provide a first input control 215 in the authentication page 210. Further, the electronic device 110 may obtain dynamic authentication information associated with the current user based on the first input control 215. As an example, the electronic device 110 may obtain dynamic authentication information input by the current user based on the first input control 215. The dynamic authentication information may include, for example, a mobile phone number and a verification code obtained based on the mobile phone number.

[0053] In some embodiments, continue to refer to Figure 2B In response to the authentication information being verified, the electronic device 110 may trigger the completion of the payment request through the target payment method. As an example, the electronic device 110 may complete the payment based on the bank card corresponding to the first payment method 205-1.

[0054] In some embodiments, continue to refer to Figure 2B , the electronic device 110 can determine the first payment account corresponding to the target payment method in response to the dynamic authentication information being verified. As an example, the first payment account can include the payment account of the current user associated with the second application. Further, the electronic device 110 can trigger the use of the first payment account to complete the payment request. As an example, the electronic device 110 can trigger the use of the bank card associated with the first payment method 205-1 bound to the first payment account to complete the payment.

[0055] In some embodiments, Figure 2CAs shown, the electronic device 110 can present a third authentication page 200C in response to the dynamic authentication information being verified. Further, the electronic device 110 can obtain the account authentication information associated with the target payment method via the third authentication page 200C. For example, based on the second input control 220, the account authentication information associated with the target payment method input by the current user (for example, the bank card information corresponding to the target payment method) is obtained. Further, the electronic device 110 can trigger the completion of the payment request through the target payment method in response to the account authentication information being verified. For example, the payment request is completed through the bank card corresponding to the target payment method.

[0056] In some embodiments, the authentication information includes static authentication information associated with the current user.

[0057] In some embodiments, Figure 2D As shown, the electronic device 110 may present an authentication page 225 (also referred to as a first authentication page 225 ) in the web payment page 200D. Further, the electronic device 110 may obtain static authentication information associated with the current user via the authentication page 225 .

[0058] As an example, continue to refer to Figure 2D , the electronic device 110 may provide a third input control 230 in the authentication page 225. Further, the electronic device 110 may obtain static authentication information associated with the current user based on the third input control 230. As an example, the electronic device 110 may obtain static authentication information input by the current user based on the third input control 230. The static authentication information may include, for example, the name and certificate number of the current user.

[0059] In some embodiments, Figure 2E As shown, the electronic device 110 may present a second authentication page 200E in response to the static authentication information passing the verification. Further, the electronic device 110 may obtain the account authentication information associated with the second payment account via the second authentication page 200E. As an example, the electronic device 110 may obtain the account information associated with the second payment account input by the current user based on the fourth input control 235. As an example, the account information associated with the second payment account may include, for example, bank card information associated with the second payment account. As an example, the electronic device 110 may verify the reserved mobile phone number associated with the bank card information based on the bank service interface associated with the bank card information input by the user to complete the verification of the account authentication information.

[0060] In some embodiments, continue to refer to Figure 2F, the electronic device 110 can trigger the completion of the payment request using the second payment account in response to the account authentication information being verified. As an example, the electronic device 110 can complete the payment request using a bank card associated with the second payment account. As an example, the electronic device 110 can use identification information 240 to indicate the completion of the payment request in the completion interface 200F. As an example, the identification information 240 may include, for example, a text identifier (e.g., "Payment successful"), payee information, and payment method, etc. In this way, based on an embodiment of the present disclosure, the user only needs to pass the verification to complete the payment request, and there is no need to log in to the account associated with the second application, thereby improving payment efficiency.

[0061] FIG. 3A to FIG. 3C 300A to 300C according to some embodiments of the present disclosure. The interfaces 300A to 300C may be composed of, for example, Figure 1 The electronic device 110 is provided as shown.

[0062] In some embodiments, the electronic device 110 may determine whether there is historical authentication information associated with the second application based on the cache information.

[0063] In some embodiments, Figure 3A As shown, the electronic device 110 can determine at least one payment method associated with the historical authentication information in response to the existence of the historical authentication information. As an example, the electronic device 110 can determine the account information of the current user associated with the second application based on the historical authentication information. Further, the electronic device 110 can determine at least one payment method based on the account information associated with the second application. For example, the at least one payment method corresponds to at least one bank card bound to the account associated with the second application.

[0064] In some embodiments, continue to refer to Figure 3A , the electronic device 110 may present a second web payment page 300A including at least one payment method. As an example, the electronic device 110 may present at least one payment method 305 in the second web payment page 300A. As an example, the at least one payment method 305 may include, for example, multiple bank card payments (e.g., the first payment method 305-1 and the second payment method 305-2) and change payments (e.g., the third payment method 305-3).

[0065] In some embodiments, continue to refer to Figure 3A , the electronic device 110 can present the account information 310 associated with the second application in the second web payment page 300A. As an example, the account information 310 may include an account name, an account number, and the like.

[0066] In some embodiments, Figure 3B As shown, the electronic device 110 can present a verification panel 315 for selecting a target payment method (e.g., a first payment method 305-1) in at least one payment method 305. As an example, the verification panel 315 is used to obtain a password associated with the account information 310 to complete the payment request.

[0067] In some embodiments, Figure 3C As shown, the electronic device 110 can complete the payment request in response to the password obtained via the verification panel 315 passing the verification. As an example, the electronic device 110 can use the identification information 320 in the completion interface 300C to indicate the completion of the payment request. As an example, the identification information 320 can include, for example, a text logo (e.g., "Payment successful"), payee information, and payment method, etc.

[0068] Based on the process described above, the embodiment of the present disclosure can present a web payment page provided by the second application based on the payment request in the first application, so as to complete the information verification in the web payment page, thereby completing the payment request. In addition, the present disclosure can generate cache information associated with the authentication information after the information verification is successful, so that the user can directly complete the payment request based on the historical authentication information.

[0069] In this way, the embodiments of the present disclosure can directly verify the authentication information corresponding to the payment method in cross-terminal payment to complete the payment without logging into the account of the payment application. In addition, the embodiments of the present disclosure can record historical authentication information, without the need for the user to perform repeated authentication in the same device. Therefore, the present disclosure meets the payment needs of users and improves payment efficiency.

[0070] It should be understood that the various types of authentication information, identification information, etc. mentioned above are all actively input by the user for payment authentication, and the acquisition and use of relevant information are carried out with the user's knowledge and permission.

[0071] Example Process

[0072] Figure 4 4 is a flowchart showing an example process 400 of electronic payment according to some embodiments of the present disclosure. The process 400 may be implemented at the electronic device 110. Figure 1 4. The process 400 is described below.

[0073] As shown in the figure, in box 410, the electronic device 110 presents a web payment page provided by the second application in response to a payment request within the first application, and the web payment page presents multiple preset payment methods.

[0074] In block 420 , in response to receiving a selection of a target payment method from among a plurality of preset payment methods, the electronic device 110 presents an authentication page associated with the target payment method.

[0075] In block 430 , the electronic device 110 obtains authentication information associated with the target payment method via the authentication page.

[0076] In block 440 , the electronic device 110 triggers completion of the payment request through the target payment method in response to the authentication information being verified.

[0077] In some embodiments, in response to a payment request within a first application, presenting a web payment page provided by a second application includes: determining whether there is historical authentication information associated with the second application based on cache information; and in response to the absence of historical authentication information, presenting a first web payment page including multiple preset payment methods.

[0078] In some embodiments, process 400 further includes: in response to the existence of the historical authentication information, determining at least one payment method associated with the historical authentication information; and presenting a second web payment page including the at least one payment method.

[0079] In some embodiments, process 400 further includes: in response to the authentication information passing authentication, generating cache information associated with the authentication information for use in processing subsequent payment requests.

[0080] In some embodiments, the payment request indicates a first identifier of a target device that initiates the payment request, and presenting a web page provided by a second application includes: determining whether a second identifier of a current device matches a first identifier indicated by the payment request; and in response to the second identifier matching the first identifier, presenting a web payment page provided by the second application using the current device.

[0081] In some embodiments, the authentication information includes static authentication information and / or dynamic authentication information associated with the current user.

[0082] In some embodiments, in response to the authentication information being verified, triggering the completion of the payment request through the target payment method includes: in response to the dynamic authentication information being verified, determining a first payment account corresponding to the target payment method; and triggering the completion of the payment request using the first payment account.

[0083] In some embodiments, the authentication page is a first authentication page, and in response to the authentication information passing the verification, triggering the completion of the payment request through the target payment method includes: in response to the static authentication information passing the verification, presenting a second authentication page; obtaining account authentication information associated with the second payment account via the second authentication page; and in response to the account authentication information passing the verification, triggering the completion of the payment request using the second payment account.

[0084] Example devices and equipment

[0085] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 5 A schematic structural block diagram of an example apparatus 500 for electronic payment according to some embodiments of the present disclosure is shown. The apparatus 500 may be implemented as or included in an electronic device. Each module / component in the apparatus 500 may be implemented by hardware, software, firmware, or any combination thereof.

[0086] like Figure 5 As shown, the device 500 includes a presentation module 510, which is configured to obtain rich text information generated by the target model based on the query request in response to receiving a query request, and the rich text information indicates a target access address; an authentication module 520, which is configured to present an authentication page associated with the target payment method in response to receiving a selection of a target payment method from a plurality of preset payment methods; an acquisition module 530, which is configured to obtain authentication information associated with the target payment method via the authentication page; and a payment module 540, which is configured to trigger completion of a payment request through the target payment method in response to verification of the authentication information.

[0087] In some embodiments, the presentation module 510 is further configured to: determine whether there is historical authentication information associated with the second application based on the cache information; and in response to the absence of historical authentication information, present a first web payment page including multiple preset payment methods.

[0088] In some embodiments, the apparatus 500 further comprises an information module configured to: in response to the existence of the historical authentication information, determine at least one payment method associated with the historical authentication information; and present a second web payment page including the at least one payment method.

[0089] In some embodiments, the apparatus 500 further includes a cache module, which is configured to: in response to the authentication information passing the authentication, generate cache information associated with the authentication information for processing subsequent payment requests.

[0090] In some embodiments, the payment request indicates a first identifier of a target device that initiates the payment request, and the presentation module 510 is further configured to: determine whether a second identifier of the current device matches the first identifier indicated by the payment request; and in response to the second identifier matching the first identifier, present a web payment page provided by a second application using the current device.

[0091] In some embodiments, the authentication information includes static authentication information and / or dynamic authentication information associated with the current user.

[0092] In some embodiments, the payment module 540 is further configured to: determine a first payment account corresponding to the target payment method in response to the dynamic authentication information being verified; and trigger the completion of the payment request using the first payment account.

[0093] In some embodiments, the authentication page is a first authentication page, and the payment module 540 is also configured to: present a second authentication page in response to the static authentication information passing the verification; obtain account authentication information associated with the second payment account via the second authentication page; and trigger the completion of the payment request using the second payment account in response to the account authentication information passing the verification.

[0094] The units included in the device 500 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units in the device 500 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0095] Figure 6 1 shows a block diagram of an electronic device 600 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 6 The electronic device 600 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 6 The electronic device 600 shown can be used to implement Figure 1 An electronic device 110.

[0096] like Figure 6 As shown, the electronic device 600 is in the form of a general electronic device. The components of the electronic device 600 may include, but are not limited to, one or more processors or processing units 610, a memory 620, a storage device 630, one or more communication units 640, one or more input devices 650, and one or more output devices 660. The processing unit 610 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 620. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 600.

[0097] The electronic device 600 typically includes a plurality of computer storage media. Such media may be any accessible media that is accessible to the electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 620 may be a volatile memory (e.g., registers, caches, random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 630 may be a removable or non-removable medium, and may include a machine-readable medium, such as a flash drive, a disk, or any other medium, which may be capable of being used to store information and / or data and may be accessed within the electronic device 600.

[0098] The electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 6 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 620 may include a computer program product 625 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0099] The communication unit 640 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 600 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 600 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0100] The input device 650 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 660 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 600 may also communicate with one or more external devices (not shown) through the communication unit 640 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 600, or communicate with any device that allows the electronic device 600 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0101] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0102] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0103] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0104] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0105] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0106] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. An electronic payment method, comprising: In response to a payment request in the first application, presenting a web payment page provided by the second application, the web payment page presenting a plurality of preset payment methods; In response to receiving a selection of a target payment method from among the plurality of preset payment methods, presenting an authentication page associated with the target payment method; Obtaining authentication information associated with the target payment method via the authentication page; as well as In response to the authentication information being verified, completing the payment request through the target payment method is triggered.

2. The method of claim 1, wherein in response to a payment request within the first application, presenting a web payment page provided by the second application comprises: Based on the cache information, determining whether there is historical authentication information associated with the second application; as well as In response to the absence of the historical authentication information, presenting a first web payment page including the plurality of preset payment methods.

3. The method according to claim 2, further comprising: In response to the existence of the historical authentication information, determining at least one payment method associated with the historical authentication information; as well as A second web payment page including the at least one payment method is presented.

4. The method according to claim 1, further comprising: In response to the authentication information passing the authentication, cache information associated with the authentication information is generated for processing subsequent payment requests.

5. The method of claim 1 , wherein the payment request indicates a first identifier of a target device that initiates the payment request, and presenting a web page provided by a second application comprises: Determining whether a second identifier of the current device matches a first identifier indicated by the payment request; as well as In response to the second identifier matching the first identifier, presenting the web payment page provided by the second application using the current device. The method according to claim 1 , wherein the authentication information comprises static authentication information and / or dynamic authentication information associated with a current user.

7. The method according to claim 6, wherein in response to the authentication information being verified, triggering the completion of the payment request through the target payment method comprises: In response to the dynamic authentication information being verified, determining a first payment account corresponding to the target payment method; as well as Triggering the completion of the payment request using the first payment account.

8. The method according to claim 6, wherein the authentication page is a first authentication page, and in response to the authentication information being verified, triggering the completion of the payment request through the target payment method comprises: In response to the static authentication information passing verification, presenting a second authentication page; Obtaining, via the second authentication page, account authentication information associated with the second payment account; as well as In response to the account authentication information being verified, completing the payment request using the second payment account is triggered.

9. An apparatus for electronic payment, comprising: A presentation module, configured to, in response to receiving a query request, obtain rich text information generated by a target model based on the query request, wherein the rich text information indicates a target access address; an authentication module configured to, in response to receiving a selection of a target payment method from among a plurality of preset payment methods, present an authentication page associated with the target payment method; an acquisition module, configured to acquire, via the authentication page, authentication information associated with the target payment method; as well as The payment module is configured to trigger the completion of the payment request through the target payment method in response to the authentication information being verified.

10. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 8 when executed by the at least one processing unit.

11. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 8.

Images