Method and apparatus for electronic payment, device, and storage medium

Abstract

Embodiments of the present disclosure relate to a method and apparatus for electronic payment, a device, and a storage medium. The method provided herein comprises: in response to a payment request in a first application, presenting a web payment page provided by a second application, the web payment page presenting a plurality of preset payment modes; in response to receiving a selection of a target payment mode among the plurality of preset payment modes, presenting an authentication page associated with the target payment mode; via the authentication page, acquiring authentication information associated with the target payment mode; and in response to the authentication information passing verification, triggering completion of the payment request by means of the target payment mode. In this way, the embodiments of the present disclosure can improve user payment efficiency.

Description

Methods, devices, equipment and storage media for electronic payment

[0001] This application claims priority to Chinese Patent Application No. 202411435028.8, filed on October 14, 2024, entitled "Method, Apparatus, Device and Storage Medium for Content Search", the entire contents of which are incorporated herein by reference. Technical Field

[0002] The exemplary embodiments disclosed herein generally relate to the field of computers, and particularly to methods, apparatus, devices, and computer-readable storage media for electronic payments. Background Technology

[0003] In recent years, with the development of the internet, users' demand for online payments has been increasing. However, in the process of cross-platform payments, users need to go through a cumbersome login process before they can continue to make payments, resulting in low payment efficiency. Summary of the Invention

[0004] In a first aspect of this 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 multiple preset payment methods; in response to receiving a selection of a target payment method among the multiple 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 a payment request to be completed through the target payment method.

[0005] In a second aspect of this disclosure, an apparatus for electronic payment is provided. The apparatus includes: a presentation module configured to, in response to receiving a query request, acquire 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 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, acquire 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 complete via the target payment method.

[0006] In a third aspect of this disclosure, an electronic device is provided. The device includes at least one processor; and at least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor. When executed by the at least one processor, the instructions cause the device to perform the method of the first aspect.

[0007] In a fourth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-executable instructions that can be executed by a processor to implement the method of the first aspect.

[0008] In a fifth aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions that, when executed by a processor, implement the method of the first aspect.

[0009] It should be understood that the content described in this content section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0010] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0011] Figure 1 shows a schematic diagram of an example environment in which embodiments of the present disclosure may be implemented;

[0012] Figures 2A to 2F illustrate example interfaces according to some embodiments of the present disclosure;

[0013] Figures 3A to 3C illustrate example interfaces according to further embodiments of the present disclosure;

[0014] Figure 4 illustrates a flowchart of an example electronic payment process according to some embodiments of the present disclosure;

[0015] Figure 5 shows a schematic structural block diagram of an example device for electronic payment according to some embodiments of the present disclosure; and

[0016] Figure 6 shows a block diagram of an electronic device capable of implementing several embodiments of the present disclosure. Detailed Implementation

[0017] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0018] It should be noted that the headings of any section / subsection provided herein are not limiting. Various embodiments are described throughout this document, and embodiments of any type may be included under any section / subsection. Furthermore, embodiments described in any section / subsection may be combined in any way with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0019] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based 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 also be included below. The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0020] The embodiments of this disclosure may involve user data, data acquisition, and / or use. All of these aspects comply with applicable laws, regulations, and relevant provisions. In the embodiments of this disclosure, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, in implementing the embodiments of this disclosure, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained in accordance with relevant laws and regulations through appropriate means. The specific methods of notification and / or authorization may vary depending on the actual situation and application scenario, and the scope of this disclosure is not limited in this respect.

[0021] In this specification and the embodiments, any processing of personal information will be carried out only under the premise of legality (such as obtaining the consent of the personal information subject, or being necessary for the performance of a contract), and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information other than that necessary for basic functions will not affect the user's use of basic functions.

[0022] As mentioned above, with the development of the internet, users' demand for online payments is increasing. However, in cross-platform payments, users need to go through a cumbersome login process before they can proceed. For example, when a user shops on platform A, they can choose to use 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-platform payment process is relatively cumbersome, failing to meet users' demand for convenient payments and resulting in low payment efficiency.

[0023] The embodiments of this disclosure propose a scheme for electronic payment. According to this scheme, in response to a payment request within a first application, a web payment page provided by a second application can be presented, the web payment page presenting multiple preset payment methods; in response to receiving a selection of a target payment method from the multiple preset payment methods, an authentication page associated with the target payment method can be presented; authentication information associated with the target payment method can be obtained via the authentication page; and in response to the authentication information being verified, a payment request is triggered to complete through the target payment method.

[0024] In this way, embodiments of this disclosure can present a web payment page provided by a second application in response to a payment request in a first application. Furthermore, embodiments of this disclosure can complete the payment request based on the verification of authentication information for the target payment method on the web payment page. Therefore, embodiments of this disclosure can directly verify the authentication information corresponding to the payment method to complete the payment in cross-platform payments, without needing to log in to the payment application's account, thus improving payment efficiency and meeting users' payment needs.

[0025] The following section provides a detailed description of various example implementations of this scheme, with reference to the accompanying drawings.

[0026] Example Environment

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

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

[0029] In environment 100 of Figure 1, if application 120 is active, electronic device 110 can use application 120 to present interface 150 for supporting interface interaction.

[0030] In some embodiments, electronic device 110 communicates with server 130 to provide services to application 120. Electronic device 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, handheld computers, portable gaming terminals, VR / AR devices, personal communication system (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio receivers, e-book devices, gaming devices, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, electronic device 110 can also support any type of user-facing interface (such as "wearable" circuitry).

[0031] Server 130 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and big data and artificial intelligence platforms. Server 130 may include, for example, computing systems / servers such as mainframes, edge computing nodes, computing devices in a cloud environment, etc. Server 130 can provide backend services for applications 120 that support user interface interaction in electronic devices 110.

[0032] A communication connection can be established between server 130 and electronic device 110. This communication connection can be established via wired or wireless means. The communication connection may include, but is not limited to, Bluetooth, mobile network, Universal Serial Bus (USB), and Wireless Fidelity (WiFi) connections; the embodiments of this disclosure are not limited in this respect. In the embodiments of this disclosure, server 130 and electronic device 110 can achieve signaling interaction through the communication connection between them.

[0033] It should be understood that the structure and function of the various elements in environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of this disclosure.

[0034] The following description will continue with reference to the accompanying drawings, which will provide some exemplary embodiments of this disclosure.

[0035] Example Interaction

[0036] Figures 2A to 2F illustrate example interfaces 200A to 200F according to some embodiments of the present disclosure. Interfaces 200A to 200F may be provided, for example, by the electronic device 110 shown in Figure 1.

[0037] In some embodiments, as shown in FIG2A, electronic device 110 may present a web payment page 200A provided by a second application.

[0038] In some embodiments, the electronic device 110 may respond to a payment request within a first application by displaying a payment page provided by a second application. For example, the first application may include an e-commerce application, video application, or music application that provides consumption services, etc. The second application may include a payment application that provides payment services, etc.

[0039] In some embodiments, the electronic device 110 may respond to a payment request within a first application (e.g., a payment request for goods within the first application) by presenting a payment page provided by a second application.

[0040] In some embodiments, the payment page can be a webpage written in Hypertext Markup Language (HTML), which can be presented independently of the client of the second application. For example, in response to a payment request within the first application, the first application or a browser native to the electronic device 110 can present the corresponding web payment page by accessing its address. Thus, the web payment page can support cross-platform payments without the second application being installed.

[0041] In some embodiments, continuing to refer to FIG2A, electronic device 110 may, in response to the absence of a client associated with the second application, present a web payment page provided by the second application.

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

[0043] As an example, electronic device 110 may, in response to a match between the second identifier and the first identifier, present a web payment page provided by a second application using the current device. Thus, embodiments of this disclosure can prevent a mismatch between the completed payment request and the generated payment request, thereby improving the security of online payments.

[0044] For example, electronic device 110 can 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 can be presented based on a browser application or any other application or interface capable of providing web services.

[0045] As an example, a web page can contain various elements such as text, images, videos, audio, hyperlinks, and forms. The web page can be structured based on Hyper Text Markup Language (HTML). For example, the web payment page in this disclosure can be based on HTML5 technology.

[0046] For example, for security reasons, before a user makes a payment based on a web page provided by a second application, electronic device 110 needs to obtain authentication information associated with the user for verification. Further, electronic device 110 can generate cached information associated with the authentication information in response to successful authentication. As an example, electronic device 110 can generate cached information based on the successfully verified authentication information associated with the second application (also known as historical verification information). As an example, electronic device 110 can store the cached information in a local folder (e.g., a cache folder associated with a browser application) for use in processing subsequent payment requests. In this way, when a user uses the same device to make a payment activity based on the second application, only one verification process is required, improving the user's payment efficiency.

[0047] 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 the current user's payment account information associated with the second application (e.g., account number, user identity, etc.).

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

[0049] In some embodiments, continuing to refer to FIG2A, the electronic device 110 may, in response to the absence of historical authentication information, present a first web payment page including multiple preset payment methods. As an example, as shown in FIG2A, the electronic device 110 may display multiple preset payment methods 205 on 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 payment methods corresponding to different bank card service providers, and wallet payments, etc.

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

[0051] In some embodiments, continuing to refer to FIG2A, the electronic device 110 may, in response to receiving a selection of a target payment method among a plurality of preset payment methods 205, present an authentication page associated with the target payment method. As an example, the electronic device 110 may, in response to a selection of a first payment method 205-1, present an authentication page associated with the first payment method 205-1.

[0052] In some embodiments, as shown in FIG2B, the electronic device 110 may present an authentication page 210 on a web payment page 200B. Further, the electronic device 110 may obtain authentication information associated with the target payment method via the authentication page 210.

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

[0054] In some embodiments, continuing to refer to FIG2B, the electronic device 110 may provide a first input control 215 on 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, for example, include a mobile phone number and a verification code obtained based on that mobile phone number.

[0055] In some embodiments, continuing to refer to FIG2B, electronic device 110 may trigger the completion of the payment request via the target payment method in response to the authentication information being verified. As an example, electronic device 110 may complete the payment based on the bank card corresponding to the first payment method 205-1.

[0056] In some embodiments, continuing to refer to FIG2B, the electronic device 110 may determine a first payment account corresponding to the target payment method in response to the successful verification of dynamic authentication information. As an example, the first payment account may include the payment account of the current user associated with the second application. Further, the electronic device 110 may trigger a payment request to be completed using the first payment account. As an example, the electronic device 110 may trigger a payment to be completed using the bank card associated with the first payment method 205-1 bound to the first payment account.

[0057] In some embodiments, as shown in FIG2C, the electronic device 110 may present a third authentication page 200C in response to the successful verification of dynamic authentication information. Further, the electronic device 110 may obtain account authentication information associated with the target payment method via the third authentication page 200C. For example, it may obtain the account authentication information associated with the target payment method currently input by the user (e.g., bank card information corresponding to the target payment method) based on the second input control 220. Further, the electronic device 110 may trigger a payment request to be completed through the target payment method in response to the successful verification of the account authentication information. For example, it may complete the payment request through the bank card corresponding to the target payment method.

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

[0059] In some embodiments, as shown in FIG2D, the electronic device 110 may present an authentication page 225 (also referred to as the 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.

[0060] As an example, continuing to refer to Figure 2D, electronic device 110 can provide a third input control 230 on authentication page 225. Further, electronic device 110 can obtain static authentication information associated with the current user based on the third input control 230. As an example, electronic device 110 can obtain static authentication information entered by the current user based on the third input control 230. Static authentication information may include, for example, the current user's name and identification number.

[0061] In some embodiments, as shown in FIG2E, the electronic device 110 may present a second authentication page 200E in response to the successful verification of static authentication information. Further, the electronic device 110 may obtain account authentication information associated with the second payment account via the second authentication page 200E. For example, the electronic device 110 may obtain account information associated with the second payment account input by the current user based on the fourth input control 235. For example, the account information associated with the second payment account may include, for instance, bank card information associated with the second payment account. For 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 user-input bank card information to complete the verification of the account authentication information.

[0062] In some embodiments, continuing to refer to FIG2F, electronic device 110 may trigger a payment request to be completed using a second payment account in response to successful verification of account authentication information. As an example, electronic device 110 may complete the payment request using a bank card associated with the second payment account. As an example, electronic device 110 may display identification information 240 in the completion interface 200F indicating the completion of the payment request. As an example, identification information 240 may include, for example, text identification (e.g., "Payment Successful"), payee information, and payment method. Thus, based on embodiments of this disclosure, users only need to complete the payment request through verification, eliminating the need to log in to an account associated with a second application, thereby improving payment efficiency.

[0063] Figures 3A to 3C illustrate example interfaces 300A to 300C according to some embodiments of the present disclosure. Interfaces 300A to 300C may be provided, for example, by the electronic device 110 shown in Figure 1.

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

[0065] In some embodiments, as shown in FIG3A, electronic device 110 may determine at least one payment method associated with historical authentication information in response to the existence of such information. As an example, electronic device 110 may determine the account information of the current user associated with the second application based on the historical authentication information. Further, electronic device 110 may determine at least one payment method based on the account information associated with the second application. For example, the at least one payment method may correspond to at least one bank card linked to the account associated with the second application.

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

[0067] In some embodiments, continuing to refer to FIG3A, the electronic device 110 may present account information 310 associated with the second application on the second web payment page 300A. As an example, the account information 310 may include, for example, an account name and an account number.

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

[0069] In some embodiments, as shown in FIG3C, electronic device 110 may complete a payment request in response to successful verification of a password obtained via verification panel 315. As an example, electronic device 110 may include identification information 320 in the completion interface 300C to indicate the completion of the payment request. As an example, identification information 320 may include, for example, text identification (e.g., “Payment successful”), payee information, and payment method.

[0070] Based on the process described above, embodiments of this disclosure can present a web payment page provided by a second application based on a payment request in a first application, so as to complete information verification on the web payment page and thus complete the payment request. Furthermore, this disclosure can generate cached information associated with the authentication information after successful information verification, so that the user can directly complete the payment request based on historical authentication information.

[0071] In this way, embodiments of this disclosure can directly verify the authentication information corresponding to the payment method to complete the payment in cross-platform payments, without needing to log in to the payment application's account. Furthermore, embodiments of this disclosure can record historical authentication information, eliminating the need for users to perform repeated authentication on the same device. Therefore, this disclosure meets users' payment needs and improves payment efficiency.

[0072] It should be understood that the various types of authentication information and identification information mentioned above are all actively entered by the user when making payment authentication, and the acquisition and use of such information are carried out with the user's knowledge and permission.

[0073] Example process

[0074] Figure 4 shows a flowchart of an example electronic payment process 400 according to some embodiments of the present disclosure. Process 400 can be implemented at electronic device 110. Process 400 will now be described with reference to Figure 1.

[0075] As shown in the figure, in box 410, electronic device 110 responds to a payment request within the first application and presents a web payment page provided by the second application, which displays a variety of preset payment methods.

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

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

[0078] In box 440, electronic device 110 responds to the authentication information being verified and triggers a payment request to complete the payment through the target payment method.

[0079] 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, based on cached information, whether there is historical authentication information associated with the second application; and in response to the absence of historical authentication information, presenting a first web payment page including multiple preset payment methods.

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

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

[0082] In some embodiments, the payment request indicates a first identifier of the target device initiating the payment request, and presenting a web page provided by a second application includes: determining 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, presenting a web payment page provided by the second application using the current device.

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

[0084] In some embodiments, triggering a payment request to complete via a target payment method in response to successful authentication information verification includes: determining a first payment account corresponding to the target payment method in response to successful dynamic authentication information verification; and triggering the payment request to be completed using the first payment account.

[0085] In some embodiments, the authentication page is a first authentication page, and triggering a payment request to complete the payment through the target payment method in response to the authentication information being verified includes: presenting a second authentication page in response to the static authentication information being verified; obtaining account authentication information associated with the second payment account through the second authentication page; and triggering a payment request to complete the payment using the second payment account in response to the account authentication information being verified.

[0086] Example devices and equipment

[0087] Embodiments of this disclosure also provide corresponding apparatus for implementing the methods or processes described above. Figure 5 shows a schematic structural block diagram of an example apparatus 500 for electronic payment according to certain embodiments of this disclosure. Apparatus 500 may be implemented as or included in an electronic device. The various modules / components in apparatus 500 may be implemented by hardware, software, firmware, or any combination thereof.

[0088] As shown in Figure 5, the device 500 includes a presentation module 510 configured to, in response to receiving a query request, acquire rich text information generated by the target model based on the query request, wherein the rich text information indicates the target access address; an authentication module 520 configured to, in response to receiving a selection of a target payment method from a variety of preset payment methods, present an authentication page associated with the target payment method; an acquisition module 530 configured to, via the authentication page, acquire authentication information associated with the target payment method; and a payment module 540 configured to, in response to the authentication information being verified, trigger a payment request to complete the payment through the target payment method.

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

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

[0091] In some embodiments, the apparatus 500 further includes a caching module configured to generate cache information associated with the authentication information in response to the authentication information being authenticated, for use in processing subsequent payment requests.

[0092] In some embodiments, the payment request indicates a first identifier of the target device initiating 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.

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

[0094] 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 verification of dynamic authentication information; and trigger a payment request to be completed using the first payment account.

[0095] In some embodiments, the authentication page is a first authentication page, and the payment module 540 is further configured to: present a second authentication page in response to the static authentication information being verified; obtain account authentication information associated with the second payment account via the second authentication page; and trigger a payment request to be completed using the second payment account in response to the account authentication information being verified.

[0096] The units included in device 500 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units may 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 device 500 may be implemented at least partially by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that may 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 so on.

[0097] Figure 6 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 the electronic device 600 shown in Figure 6 is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. The electronic device 600 shown in Figure 6 can be used to implement the electronic device 110 of Figure 1.

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

[0099] Electronic device 600 typically includes multiple computer storage media. Such media can be any accessible media that is accessible to electronic device 600, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 620 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 630 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media that can be used to store information and / or data and can be accessed within electronic device 600.

[0100] Electronic device 600 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 6, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. Memory 620 may include computer program product 625 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.

[0101] The communication unit 640 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 600 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 600 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0102] Input device 650 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 660 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 600 can also communicate with one or more external devices (not shown) via communication unit 640 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 600, or with any device that enables electronic device 600 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

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

[0104] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0105] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

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

[0107] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0108] Various implementations of this disclosure have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for electronic payment, comprising: In response to a payment request within the first application, a web payment page provided by the second application is displayed, which presents a variety of preset payment methods; In response to receiving a selection of a target payment method from the multiple preset payment methods, an authentication page associated with the target payment method is presented; Authentication information associated with the target payment method is obtained via the authentication page; as well as In response to the authentication information being verified, the payment request is triggered to complete the payment through the target payment method.

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

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

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

5. The method of claim 1, wherein the payment request indicates a first identifier of the target device initiating the payment request, and presenting a web page provided by the second application includes: Determine whether the second identifier of the current device matches the first identifier indicated by the payment request; as well as In response to the second identifier matching the first identifier, the web payment page provided by the second application is presented using the current device.

6. The method according to claim 1, wherein the authentication information includes static authentication information and / or dynamic authentication information associated with the current user.

7. The method according to claim 6, wherein triggering the completion of the payment request via the target payment method in response to the authentication information being verified includes: Upon successful verification of the dynamic authentication information, a first payment account corresponding to the target payment method is determined; as well as The payment request is triggered to be completed using the first payment account.

8. The method according to claim 6, wherein the authentication page is a first authentication page, and triggering the payment request to complete via the target payment method in response to the authentication information being verified includes: Upon successful verification of the static authentication information, a second authentication page is displayed. Obtain account authentication information associated with the second payment account via the second authentication page; as well as In response to the successful verification of the account authentication information, the payment request is triggered to be completed using the second payment account.

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

10. An electronic device, comprising: At least one processor; as well as At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, 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 processor.

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

12. A computer program product comprising computer-executable instructions, wherein the computer-executable instructions, when executed by a processor, implement the method according to any one of claims 1 to 8.

Images