CN114399299A - Payment method, payment device, electronic equipment and storage medium - Google Patents

Abstract

The embodiments of the present application disclose a payment method, an apparatus, an electronic device, and a storage medium. The method includes: acquiring payment order information sent by a third-party applet through a payment capability interface; generating an order creation request according to the payment order information; sending the order creation request to a payment platform; The payment parameters returned by the payment order information in the order creation request; according to the payment parameters, the interface provided by the third-party applet is invoked to pull up the payment page, and the user completes the payment in the payment page. The embodiment of the present application can save payment time and improve payment efficiency.

Description

Payment method, device, electronic device and storage medium

technical field

The present application relates to the technical field of software development, and in particular, to a payment method, device, electronic device and storage medium.

Background technique

With the continuous improvement of the level of science and technology, the application of small programs has become more and more extensive, such as WeChat small programs.

At present, WeChat mini-programs have stricter requirements for mini-programs to activate the WeChat payment function. Only mini-programs whose main body is an organization can apply for WeChat certification. Individual developers cannot apply for payment functions. The application for WeChat payment needs to go through the review process, which takes a lot of time. long, reducing the payment efficiency.

SUMMARY OF THE INVENTION

The present application provides a payment method, device, electronic device and storage medium to solve the problem that the payment method through the applet in the prior art takes a long time and reduces the payment efficiency.

In order to solve the above problems, the embodiments of the present application are implemented as follows:

In the first aspect, the embodiment of the present application provides a payment method, which is applied to a payment capability provider, including:

Obtain the payment order information sent by the third-party applet through the payment capability interface;

generating an order creation request according to the payment order information;

sending the order creation request to the payment platform;

acquiring the payment parameters returned by the payment platform according to the payment order information in the order creation request;

According to the payment parameters, the interface provided by the third-party applet is invoked to pull up the payment page, and the user completes the payment in the payment page.

Optionally, before obtaining the payment order information sent by the third-party applet through the payment capability interface, the method further includes:

Send a payment function activation request to the target application; the target application is the host application of the third-party applet;

After the payment function is successfully activated, the payment capability interface is provided to the third-party applet.

Optionally, the payment order information includes: a callback address provided by the third-party applet,

After the interface provided by the third-party applet is invoked to pull up the payment page according to the payment parameters, and the user completes the payment in the payment page, the method further includes:

Obtain the payment result returned by the third-party applet;

The callback address is called to jump to the application page corresponding to the third-party applet.

In the second aspect, the embodiment of the present application provides a payment method, which is applied to a third-party applet, including:

After receiving the payment request initiated by the user, generate payment order information according to the payment data contained in the payment request;

Based on the interface provided by the payment capability provider, the payment capability provider sends the payment order information to the payment capability provider, so that the payment capability provider initiates an order creation request to the payment platform according to the payment order information, and the payment capability provider initiates an order creation request from the payment capability provider. The capability provider receives the payment parameters returned by the payment platform;

The payment page pulled up by the payment capability provider according to the payment parameter is displayed, and the user completes the payment in the payment page.

In a third aspect, an embodiment of the present application provides a payment device, which is applied to a payment capability provider, including:

The payment order obtaining module is used to obtain the payment order information sent by the third-party applet through the payment capability interface;

an order creation request generation module, configured to generate an order creation request according to the payment order information;

an order creation request sending module, configured to send the order creation request to the payment platform;

a payment parameter return module, configured to obtain the payment parameters returned by the payment platform according to the payment order information in the order creation request;

The payment page pull-up module is used to call up the interface provided by the third-party applet to pull up the payment page according to the payment parameters, and the user completes the payment in the payment page.

Optionally, the device further includes:

a payment function activation request sending module, configured to send a payment function activation request to a target application; the target application is the host application of the third-party applet;

The payment capability interface providing module is configured to provide the payment capability interface to the third-party applet after the payment function is successfully activated.

Optionally, the payment order information includes: a callback address provided by the third-party applet,

The device also includes:

a payment result acquisition module, configured to acquire the payment result returned by the third-party applet;

The application page jumping module is used for calling the callback address and jumping to the application page corresponding to the third-party applet.

In a fourth aspect, an embodiment of the present application provides a payment device, which is applied to a third-party applet, including:

A payment order generation module, configured to generate payment order information according to the payment data contained in the payment request after receiving the payment request initiated by the user;

A payment order sending module, configured to send the payment order information to the payment capability provider based on the interface provided by the payment capability provider, so that the payment capability provider can initiate order creation to the payment platform according to the payment order information request, and the payment capability provider receives the payment parameters returned by the payment platform;

The payment page display module is configured to display the payment page pulled up by the payment capability provider according to the payment parameter, and the user completes the payment in the payment page.

In a fifth aspect, an embodiment of the present application provides an electronic device, including:

A processor, a memory, and a computer program stored on the memory and executable on the processor, when the processor executes the program, the payment method described in any of the above is implemented.

In a sixth aspect, an embodiment of the present application provides a readable storage medium, when an instruction in the storage medium is executed by a processor of an electronic device, the electronic device can execute any of the payment methods described above.

Compared with the prior art, the present application includes the following advantages:

The embodiments of the present application provide a payment method, device, electronic device, and storage medium, by acquiring payment order information sent by a third-party applet through a payment capability interface, generating an order creation request according to the payment order information, and sending the order creation request Go to the payment platform to obtain the payment parameters returned by the payment platform according to the payment order information in the order creation request. According to the payment parameters, the interface provided by the third-party applet is invoked to pull up the payment page, and the user completes the payment on the payment page. In the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, there is no need to go through the payment review route, which saves payment time and greatly improves payment efficiency.

Description of drawings

1 is a flowchart of steps of a payment method provided by an embodiment of the present application;

FIG. 2 is a flowchart of steps of another payment method provided by the embodiment of the present application;

FIG. 3 is a schematic structural diagram of a payment device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of another payment device provided by an embodiment of the present application;

FIG. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed ways

In order to make the above objects, features and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and specific embodiments.

Example 1

Referring to FIG. 1, a flowchart of steps of a payment method provided by an embodiment of the present application is shown. The payment method may be applied to a payment capability provider. As shown in FIG. 1, the payment method may include the following steps:

Step 101: Obtain payment order information sent by the third-party applet through the payment capability interface.

The embodiments of the present application can be applied to a scenario where a payment capability provider provides a third-party applet payment capability to complete payment.

The embodiments of the present application may be applied to a payment capability provider, that is, the execution subject is a payment capability provider, and in this example, the payment capability provider may be a separate application program or the like.

An applet is an application that can be used without downloading, such as a WeChat applet.

The payment capability interface refers to the interface provided by the payment capability provider to the third-party applet for payment operations.

In the scenario where the user logs in to the third-party applet, they may encounter payment scenarios, such as purchasing game props, etc. When the user pays, they can choose the host program of the third-party applet for payment, and when making payment, they can obtain the first The payment order information sent by the third-party applet through the payment capability interface.

In this embodiment, a payment capability interface may be provided to the third-party applet by the payment capability provider in advance, and specifically, a detailed description may be given in conjunction with the following specific implementation manner.

In a specific implementation manner of the present application, before the above step 101, it may further include:

Step A1: Send a payment function activation request to a target application; the target application is the host application of the third-party applet.

In this embodiment, the target application refers to the host application of the third-party applet. For example, when a user logs in to the third-party applet through WeChat, the target application is WeChat, and WeChat is the host application of the third-party applet. program etc.

It can be understood that the above examples are only examples listed for better understanding of the technical solutions of the embodiments of the present application, and are not used as the only limitations on the present embodiments.

The payment capability provider may send a payment function activation request to the target application in advance, where the payment function request is a request for activation of the payment function applied by the payment capability provider to the target application.

After sending the payment function activation request to the target application, step A2 is executed.

Step A2: After the payment function is successfully activated, the payment capability interface is provided to the third-party applet.

After the payment capability provider's payment function is successfully activated, the payment capability provider has the payment capability. At this time, the payment capability provider can provide the payment capability interface to the third-party applet, and the third-party applet can complete the payment through this interface. pay.

In the embodiment of this application, the payment capability provider provides a payment capability interface for the third-party applet in advance. When the user makes a payment in the third-party applet, the user can directly call the interface to realize the payment, and there is no need to go to the third-party applet. Apply for the payment capability interface, which can save the user's payment time and greatly improve the user's experience.

After acquiring the payment order information sent by the third-party applet through the payment capability interface, step 102 is performed.

Step 102: Generate an order creation request according to the payment order information.

After the payment capability provider obtains the payment order information sent by the third-party applet through the payment capability interface, the payment capability provider can generate an order creation request based on the payment order information, and the order creation request includes the payment order information, such as the payment amount and other information.

After the payment capability provider generates an order creation request according to the payment order information, step 103 is performed.

Step 103: Send the order creation request to the payment platform.

After the payment capability provider generates the order creation request according to the payment order information, the payment capability provider may send the order creation request to the payment platform.

After the payment capability provider sends the order creation request to the payment platform, step 104 is performed.

Step 104: Acquire the payment parameters returned by the payment platform according to the payment order information in the order creation request.

After the payment platform receives the order creation request sent by the payment capability provider, the payment platform can parse the order creation request to obtain the payment order information included in the order creation request, such as the payment amount, etc., and then, according to the analysis, it can be obtained The payment order information to generate payment parameters.

After the payment platform generates the payment parameters, the payment platform may return the payment parameters to the payment capability provider.

After the payment capability provider obtains the payment parameters returned by the payment platform according to the payment order information in the order creation request, step 105 is executed.

Step 105: According to the payment parameters, call up the interface provided by the third-party applet to pull up the payment page, and the user completes the payment in the payment page.

After the payment capability provider obtains the payment parameters returned by the payment platform according to the payment order information in the order creation request, the payment capability provider can call up the interface provided by the third-party applet according to the payment parameters to pull up the payment page, and the payment page is opened by the payment capability provider. The user completes the payment within the payment page. Specifically, the payment capability provider can pull up the payment page, and add payment parameters in the payment page, so as to generate a to-be-paid page, which contains information such as the amount to be paid to indicate to the user Complete the payment.

In the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, there is no need to go through the payment review route, which saves payment time and greatly improves payment efficiency.

In this example, the payment order information sent by the third-party applet to the payment capability provider also includes the callback address provided by the third-party applet, through which you can jump to the application page corresponding to the third-party applet. Specifically, detailed description may be made in conjunction with the following specific implementation manners.

In a specific implementation of the present application, the payment order information includes: a callback address provided by the third-party applet, and after step 105 above, the method may further include:

Step B1: Obtain the payment result returned by the third-party applet.

In this embodiment, the payment result refers to the result of the user making payment in the payment page. In this example, the payment result may include: a payment success result and a payment failure result.

After obtaining the payment result returned by the third-party applet, step B2 is performed.

Step B2: calling the callback address and jumping to the application page corresponding to the third-party applet.

After obtaining the payment result returned by the third-party applet, you can call the callback address to jump to the application page corresponding to the third-party applet.

The above process can be described in detail with the following examples (in this example, the Huango applet is the payment capability provider), and the overall payment steps are as follows:

1. The Huango applet has WeChat payment capability;

2. The Huango applet has designed the interface to provide the payment ability of the third-party applet in advance, and established the payment ability agreement;

3. The third-party applet does not need to apply for the official WeChat payment function. The third-party applet will jump to the payment ability page of the payment ability provider of the Huango applet with relevant parameters such as order information and callback address;

4. The Huango applet initiates an order creation request to the Dianqu payment platform and transmits the order information provided by the third-party applet;

5. In response, the Dianqu payment platform will return the parameters required for launching WeChat payment to the Huango applet;

6. The Huango applet calls the API provided by the WeChat applet according to the relevant parameters to initiate WeChat payment;

7. The payment process is completed, and the Huango applet gets the payment result;

8. The Huango applet carries the payment result and jumps back to the corresponding page of the third-party applet according to the callback address provided by the third-party applet.

The steps for the third-party applet to jump to the Huango applet payment page are as follows:

a) The third-party applet first adds the AppID of the Huango applet to the navigateToMiniProgramAppIdList property in the configuration file app.json;

b) When you need to jump to the Huango applet payment page, call the WeChat applet's own apiwx.navigateToMiniProgram to realize the applet jump, and attach the sysparam parameter to the page path;

c) The sysparam parameter is an encrypted string, which is an interface provided by a third party to call the payment platform to create an order. The required head and biz parameters are encrypted by AES, and the secret key is provided by the applet team.

The sysparam parameter construction steps are as follows:

1) First, generate a sysparam parameter object according to the third-party applet Tiaohuan go applet payment capability agreement provided by the payment platform, which contains the head object and the biz object, and convert it into a JSON string;

2) AES encryption is performed on the JSON string, and after obtaining the ciphertext, the ciphertext is processed in hex format, and finally the processed ciphertext is spliced to the back of the page path of the Huango applet.

In the payment method provided by the embodiment of the present application, the payment order information sent by the third-party applet through the payment capability interface is obtained, an order creation request is generated according to the payment order information, the order creation request is sent to the payment platform, and the payment platform according to the order is obtained by the payment platform. Create the payment parameters returned by the payment order information in the request. According to the payment parameters, the interface provided by the third-party applet is invoked to pull up the payment page, and the user completes the payment on the payment page. In the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, there is no need to go through the payment review route, which saves payment time and greatly improves payment efficiency.

Embodiment 2

Referring to FIG. 2, a flowchart of steps of a payment method provided by an embodiment of the present application is shown. The payment method may be applied to a third-party applet. As shown in FIG. 2, the payment method may include the following steps:

Step 201: After receiving the payment request initiated by the user, generate payment order information according to the payment data included in the payment request.

The embodiments of the present application can be applied to third-party applet programs, that is, the execution subject is the third-party applet program.

In the process of logging into the third-party applet, when the user needs to complete the payment through the third-party applet, the user can initiate a payment request. In the specific implementation, the payment request can be the user triggering a payment button on a certain page of the third-party applet The generated request may also be a request generated by the user in the form of inputting voice, etc. Specifically, the generation method of the payment request may be determined according to business requirements, which is not limited in this embodiment.

Payment data refers to the data contained in the payment request, for example, the payment amount, payment items and other data.

Payment order information refers to payment order information generated in combination with payment data.

After receiving the payment request initiated by the user, the third-party applet may generate payment order data according to the payment data. Specifically, the third-party applet may create payment order information according to the payment amount, payment items, and other data.

After the payment order information is generated according to the payment data included in the payment request, step 202 is executed.

Step 202: Based on the interface provided by the payment capability provider, send the payment order information to the payment capability provider, so that the payment capability provider initiates an order creation request to the payment platform according to the payment order information, and the The payment capability provider receives payment parameters returned by the payment platform.

After the payment order information is generated according to the payment data included in the payment request, the payment order information can be sent to the payment capability provider based on the interface provided by the payment capability provider, so that the payment capability provider can initiate order creation to the payment platform according to the payment order information request, and the payment capability provider receives the payment parameters returned by the payment platform. For this process, reference may be made to the description in the foregoing Embodiment 1, which is not repeated in this embodiment.

After the payment order information is sent to the payment capability provider based on the interface provided by the payment capability provider, step 203 is executed.

Step 203: Display the payment page pulled up by the payment capability provider according to the payment parameters, and the user completes the payment in the payment page.

After the payment capability provider receives the payment parameters returned by the payment platform, the payment capability provider can pull up the payment page according to the payment parameters. Therefore, the payment page can be displayed in the applet interface of the user terminal, and the payment parameters are displayed in the payment page to instruct the user to complete the payment according to the payment parameters in the payment page.

In the embodiment of the present application, when the user completes the payment in the third-party applet, the payment can be completed by using a provider with payment capability, and there is no need to go through the payment audit route, which saves the user's payment time in the third-party applet, and greatly improves the The payment efficiency is improved, and the user experience of using third-party mini programs is improved.

The payment method provided by the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, does not need to go through the payment review route, saves the payment time, and greatly improves the payment efficiency.

Embodiment 3

Referring to FIG. 3 , a schematic structural diagram of a payment device provided by an embodiment of the present application is shown. The payment device can be applied to a payment capability provider. As shown in FIG. 3 , the payment device 300 may include the following modules:

A payment order obtaining module 310, configured to obtain payment order information sent by the third-party applet through the payment capability interface;

an order creation request generating module 320, configured to generate an order creation request according to the payment order information;

an order creation request sending module 330, configured to send the order creation request to the payment platform;

A payment parameter returning module 340, configured to obtain payment parameters returned by the payment platform according to the payment order information in the order creation request;

The payment page pulling module 350 is configured to call up the interface provided by the third-party applet to pull up the payment page according to the payment parameters, and the user completes the payment in the payment page.

Optionally, the device further includes:

a payment function activation request sending module, configured to send a payment function activation request to a target application; the target application is the host application of the third-party applet;

The payment capability interface providing module is configured to provide the payment capability interface to the third-party applet after the payment function is successfully activated.

Optionally, the payment order information includes: a callback address provided by the third-party applet,

The device also includes:

a payment result acquisition module, configured to acquire the payment result returned by the third-party applet;

The application page jumping module is used for calling the callback address and jumping to the application page corresponding to the third-party applet.

The payment device provided by the embodiment of the present application obtains payment order information sent by a third-party applet through the payment capability interface, generates an order creation request according to the payment order information, sends the order creation request to the payment platform, and obtains the payment order according to the order by the payment platform. Create the payment parameters returned by the payment order information in the request. According to the payment parameters, the interface provided by the third-party applet is invoked to pull up the payment page, and the user completes the payment on the payment page. In the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, there is no need to go through the payment review route, which saves payment time and greatly improves payment efficiency.

Embodiment 4

Referring to FIG. 4 , a schematic structural diagram of a payment device provided by an embodiment of the present application is shown. The payment device can be applied to a third-party applet. As shown in FIG. 4 , the payment device 400 may include the following modules:

The payment order generation module 410 is configured to generate payment order information according to the payment data contained in the payment request after receiving the payment request initiated by the user;

A payment order sending module 420, configured to send the payment order information to the payment capability provider based on the interface provided by the payment capability provider, so that the payment capability provider can initiate an order to the payment platform according to the payment order information Create a request, and receive the payment parameters returned by the payment platform by the payment capability provider;

The payment page display module 430 is configured to display the payment page pulled up by the payment capability provider according to the payment parameter, and the user completes the payment in the payment page.

The payment device provided by the embodiment of the present application, by using the payment capability provider to provide the third-party applet payment capability, does not need to go through the payment review route, saves the payment time, and greatly improves the payment efficiency.

For the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, Certain steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

Embodiment 5

An embodiment of the present application provides an electronic device, including: a processor, a memory, and a computer program stored on the memory and executable on the processor, and the processor implements any of the above when executing the program the payment method described in the item.

Referring to FIG. 5, a schematic structural diagram of an electronic device provided by an embodiment of the present application is shown. As shown in FIG. 5, the electronic device 500 includes a central processing unit (CPU) 501, which can Computer program instructions in 502 or computer program instructions loaded into random access memory (RAM) 503 from storage unit 508 to perform various appropriate actions and processes. In the RAM 503, various programs and data required for the operation of the electronic device 500 can also be stored. The CPU 501 , the ROM 502 , and the RAM 503 are connected to each other through a bus 504 . An input/output (I/O) interface 505 is also connected to bus 504 .

Various components in the electronic device 500 are connected to the I/O interface 505, including: an input unit 506, such as a keyboard, mouse, microphone, etc.; an output unit 507, such as various types of displays, speakers, etc.; a storage unit 508, such as a disk , optical disc, etc.; and a communication unit 509, such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 509 allows the electronic device 500 to exchange information/data with other devices through a computer network such as the Internet and/or various telecommunication networks.

The various processes and processes described above may be performed by the processing unit 501 . For example, the method of any of the above-described embodiments may be implemented as a computer software program tangibly embodied on a computer-readable medium, such as storage unit 508 . In some embodiments, part or all of the computer program may be loaded and/or installed on the electronic device 500 via the ROM 502 and/or the communication unit 509 . When a computer program is loaded into RAM 503 and executed by CPU 501, one or more of the actions of the methods described above may be performed.

Embodiment 6

An embodiment of the present application provides a readable storage medium, when an instruction in the storage medium is executed by a processor of an electronic device, the electronic device can execute any of the payment methods described above.

The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same and similar parts between the various embodiments may be referred to each other.

Finally, it should also be noted that in this document, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply these entities or that there is any such actual relationship or sequence between operations. Furthermore, the terms "comprising", "comprising" or any other variation thereof are intended to encompass a non-exclusive inclusion such that a process, method, article of manufacture or device comprising a list of elements includes not only those elements, but also includes not explicitly listed or other elements inherent to such a process, method, commodity or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article of manufacture, or device that includes the element.

A payment method, a payment device, an electronic device, and a storage medium provided by the present application have been described above in detail. The principles and implementations of the present application are described with specific examples. The description of the embodiment is only used to help understand the method of the present application and its core idea; meanwhile, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation and application scope. As mentioned above, the contents of this specification should not be construed as limiting the present application.

Claims (10)

1. A payment method applied to a payment capability provider, comprising:

obtaining payment order information sent by a third-party applet through a payment capability interface;

generating an order establishing request according to the payment order information;

sending the order creation request to a payment platform;

obtaining payment parameters returned by the payment platform according to the payment order information in the order creation request;

and calling an interface provided by the third-party applet to pull up a payment page according to the payment parameters, and completing payment in the payment page by the user.

2. The method of claim 1, further comprising, prior to the obtaining payment order information sent by the third party applet over the payment capability interface:

sending a payment function opening request to a target application program; the target application program is a host application program of the third-party applet;

providing the payment capability interface to the third party applet after successful provisioning of a payment function.

3. The method of claim 1, wherein the payment order information comprises: a callback address provided by the third-party applet,

after the interface provided by the third-party applet is invoked to pull up a payment page according to the payment parameters and payment is completed in the payment page by a user, the method further comprises:

obtaining a payment result returned by the third-party applet;

and calling the callback address, and jumping to an application page corresponding to the third-party applet.

4. A payment method applied to a third-party applet, comprising:

after a payment request initiated by a user is received, generating payment order information according to payment data contained in the payment request;

sending the payment order information to a payment capability provider based on an interface provided by the payment capability provider, so that the payment capability provider initiates an order creation request to a payment platform according to the payment order information, and the payment capability provider receives payment parameters returned by the payment platform;

and displaying a payment page pulled up by the payment capability provider according to the payment parameters, and completing payment in the payment page by a user.

5. A payment apparatus applied to a payment capability provider, comprising:

the payment order acquisition module is used for acquiring payment order information sent by the third-party applet through the payment capability interface;

the order creating request generating module is used for generating an order creating request according to the payment order information;

the order creating request sending module is used for sending the order creating request to a payment platform;

a payment parameter returning module for obtaining payment parameters returned by the payment platform according to the payment order information in the order establishing request;

and the payment page pull-up module is used for calling an interface provided by the third-party applet to pull up a payment page according to the payment parameters, and completing payment in the payment page by a user.

6. The apparatus of claim 5, further comprising:

the payment function opening request sending module is used for sending a payment function opening request to the target application program; the target application program is a host application program of the third-party applet;

and the payment capability interface providing module is used for providing the payment capability interface for the third-party applet after the payment function is successfully opened.

7. The apparatus of claim 5, wherein the payment order information comprises: a callback address provided by the third-party applet,

the device further comprises:

the payment result acquisition module is used for acquiring a payment result returned by the third-party applet;

and the application page jump module is used for calling the callback address and jumping to the application page corresponding to the third-party applet.

8. A payment device for use with a third-party applet, comprising:

the payment order generation module is used for generating payment order information according to payment data contained in a payment request after receiving the payment request initiated by a user;

the payment order sending module is used for sending the payment order information to a payment capability provider based on an interface provided by the payment capability provider, so that the payment capability provider initiates an order creating request to a payment platform according to the payment order information, and the payment capability provider receives payment parameters returned by the payment platform;

and the payment page display module is used for displaying the payment page pulled up by the payment capability provider according to the payment parameters and completing payment in the payment page by the user.

9. An electronic device, comprising:

a processor, a memory, and a computer program stored on the memory and executable on the processor, the processor implementing the payment method of any one of claims 1-4 when executing the program.

10. A readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the payment method of any one of claims 1-4.

Images