Payment solutions and systems

Abstract

The present application provides a payment solution and system, which includes the following steps: obtaining order information of a payment application; creating a built-in order webpage and loading a built-in payment webpage according to the order information, and linking the payment platform through the built-in payment webpage to make payment; calling back the built-in payment webpage and passing the payment status through the built-in payment webpage, obtaining the payment status and passing it to the payment application. The payment solution and system provided by the present application enable users to complete commodity payment without jumping to other applications or browsers, which greatly improves the user experience.

Description

Technical Field

[0001] The present application mainly relates to the field of mobile payment technology, and in particular to a payment solution and system. Background Art

[0002] With the popularization of mobile payment technology, users are increasingly inclined to complete payment operations within specific applications. For the huge number of transactions between enterprises, existing payment solutions usually require users to jump between specific applications and browsers to complete payments. This payment method not only affects the user experience, but also further increases the complexity of the payment process. In addition, traditional payment methods between enterprises often need to be completed in the browser, which leads to the loss of users of enterprise transaction applications and the interruption of the payment process. Summary of the invention

[0003] The technical problem to be solved by this application is to provide a payment solution and system that enables users to complete product payment without jumping to other applications or browsers, greatly improving the user experience.

[0004] To solve the above technical problems, the present application provides a payment solution, including the following steps: obtaining order information of a payment application; creating a built-in order web page and loading a built-in payment web page based on the order information, and making payments by linking to a payment platform through the built-in payment web page; calling back the built-in payment web page and passing the payment status through the built-in payment web page, obtaining the payment status and passing it to the payment application.

[0005] Optionally, the order information includes order number, order amount, order time, order quantity and order SKU.

[0006] Optionally, the built-in payment web page includes an H5 payment page.

[0007] Optionally, obtaining the payment status and transmitting it to the payment application includes updating the status of the built-in payment webpage.

[0008] To solve the above technical problems, the present application provides a payment solution system, including: an order module, which is configured to obtain order information of a payment application; a built-in order module, which is configured to create a built-in order webpage and load a built-in payment webpage according to the order information, and make payment by linking to a payment platform through the built-in payment webpage; a payment feedback module, which is configured to call back the built-in payment webpage and transmit the payment status through the built-in payment webpage, obtain the payment status and transmit it to the payment application.

[0009] Optionally, the order module includes purchasing services, and the purchasing services include membership subscriptions and / or digital goods.

[0010] Optionally, the payment feedback module includes a payment interface and a payment account, and the payment interface and the payment account perform account interaction in the built-in payment webpage.

[0011] Optionally, the payment application includes a mobile phone payment application and a computer payment application.

[0012] In order to solve the above technical problem, the present application provides a computer-readable medium storing a computer program code, and the computer program code implements the above method when executed by a processor.

[0013] Compared with the prior art, this application uses a built-in order webpage to load a built-in payment webpage, and makes payments by linking the built-in payment webpage to the payment platform, so that users can complete the payment of goods without jumping to other applications or browsers, which greatly improves the user experience. Furthermore, the payment solution of this application can also pass the payment status obtained to the payment application by calling back the built-in payment webpage and passing the payment status through the built-in payment webpage, so that users can understand the payment status through the payment information, further improving the convenience of payment. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are included to provide a further understanding of the present application. They are included and constitute a part of the present application. The accompanying drawings illustrate embodiments of the present application and together with the present specification serve to explain the principles of the present application. In the accompanying drawings:

[0015] Figure 1 It is a flow chart of a payment solution in one embodiment of the present application;

[0016] Figure 2 It is a structural module diagram of a payment solution system in one embodiment of the present application. DETAILED DESCRIPTION

[0017] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for the description of the embodiments. Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. Unless it is obvious from the language environment or otherwise explained, the same reference numerals in the figures represent the same structure or operation.

[0018] As shown in this application and claims, unless the context clearly indicates an exception, the words "a", "an", "an" and / or "the" do not refer to the singular and may also include the plural. Generally speaking, the terms "include" and "comprise" only indicate the inclusion of the steps and elements that have been clearly identified, and these steps and elements do not constitute an exclusive list. The method or device may also include other steps or elements.

[0019] Unless otherwise specifically stated, the relative arrangement, numerical expressions and numerical values ​​of the parts and steps set forth in these embodiments do not limit the scope of the present application. At the same time, it should be understood that, for ease of description, the sizes of the various parts shown in the accompanying drawings are not drawn according to the actual proportional relationship. The technology, method and equipment known to those of ordinary skill in the relevant field may not be discussed in detail, but in appropriate cases, the technology, method and equipment should be considered as a part of the authorization specification. In all examples shown and discussed here, any specific value should be interpreted as being merely exemplary, rather than as a limitation. Therefore, other examples of exemplary embodiments may have different values. It should be noted that similar reference numerals and letters represent similar items in the following drawings, so that once a certain item is defined in an accompanying drawing, it does not need to be further discussed in subsequent drawings.

[0020] In the description of the present application, it should be understood that the directions or positional relationships indicated by directional words such as "front, back, up, down, left, right", "lateral, vertical, perpendicular, horizontal" and "top, bottom" are usually based on the directions or positional relationships shown in the drawings, and are only for the convenience of describing the present application and simplifying the description. Unless otherwise specified, these directional words do not indicate or imply that the device or element referred to must have a specific direction or be constructed and operated in a specific direction, and therefore cannot be understood as limiting the scope of protection of the present application; the directional words "inside and outside" refer to the inside and outside relative to the contours of each component itself.

[0021] For ease of description, spatially relative terms such as "above", "above", "on the upper surface of", "above", etc. may be used here to describe the spatial positional relationship between a device or feature and other devices or features as shown in the figure. It should be understood that spatially relative terms are intended to include different orientations of the device in use or operation in addition to the orientation described in the figure. For example, if the device in the accompanying drawings is inverted, the device described as "above other devices or structures" or "above other devices or structures" will be positioned as "below other devices or structures" or "below other devices or structures". Thus, the exemplary term "above" can include both "above" and "below". The device can also be positioned in other different ways (rotated 90 degrees or in other orientations), and the spatially relative descriptions used here are interpreted accordingly.

[0022] In addition, it should be noted that the use of words such as "first" and "second" to define components is only for the convenience of distinguishing the corresponding components. If not otherwise stated, the above words have no special meaning and cannot be understood as limiting the scope of protection of this application. In addition, although the terms used in this application are selected from well-known and commonly used terms, some terms mentioned in the specification of this application may be selected by the applicant at his or her discretion, and their detailed meanings are explained in the relevant parts of the description of this article. In addition, it is required to understand this application not only by the actual terms used, but also by the meaning implied by each term.

[0023] This application refers to Figure 1 A payment solution 10 (hereinafter referred to as "solution 10") is proposed. A flowchart is used in this application to illustrate the operations performed by the system according to the embodiment of the present application. It should be understood that the previous or following operations are not necessarily performed in exact order. Instead, various steps can be processed in reverse order or simultaneously. At the same time, other operations can be added to these processes, or one or more operations can be removed from these processes. Solution 10 mainly includes steps S1 to S3.

[0024] Steps S1 to S3 will now be described in detail. First, step S1 includes obtaining the order information of the payment application, wherein the order information includes the order number, order amount, order time, order quantity, and order SKU. In other embodiments of the present application, the order information may also include information in addition to the above information, and the present application does not limit this. Further, step S2 includes creating a built-in order web page and loading a built-in payment web page according to the order information, and making payment by linking the payment platform through the built-in payment web page. Exemplarily, the built-in order web page includes a webview, and the built-in payment web page includes an H5 payment page. Further, step S3 includes calling back the built-in payment web page and passing the payment status through the built-in payment web page, obtaining the payment status and passing it to the payment application.

[0025] On the other hand, the present application also refers to Figure 2 A payment solution system 20 is proposed, which is applicable to the payment solution proposed in any embodiment of the present application, such as the above-mentioned payment solution 10. Figure 2 As shown, the payment settlement system 20 includes an order module, a built-in order module and a payment feedback module.

[0026] Specifically, the order module is configured to obtain order information of the payment application. The built-in order module is configured to create a built-in order webpage and load a built-in payment webpage according to the order information, and make payment through the built-in payment webpage linking the payment platform. The payment feedback module is configured to call back the built-in payment webpage and transmit the payment status through the built-in payment webpage, obtain the payment status and transmit it to the payment application. Exemplarily, the payment application includes a mobile payment application and a computer payment application.

[0027] In this embodiment, the order module includes a purchase service, and the purchase service includes a membership subscription and / or digital goods. The payment feedback module includes a payment interface and a payment account, and the payment interface and the payment account interact with each other in the built-in payment webpage. The design of interacting with the payment account through the payment interface can increase payment security, that is, the payment information can be protected during the interaction process through the built-in browser and the secure communication interface, further improving the security and reliability of payment.

[0028] The process of payment by the user using the payment solution and payment solution system proposed in this application will now be specifically described. First, the user can select products in the order module and initiate a payment request. At this time, the payment solution 10 will obtain the user's order information in the payment application, and then the built-in order module will create a webview window to load the H5 payment interface based on the user's order information (such as order amount, order SKU, etc.). The payment process is completed in the H5 payment interface. During the payment process, the third-party payment platform (such as a bank) performs payment actions through the payment interface and the interaction of the payment account. After the payment is successful, the webview will feed back the payment situation to the payment application, and further notify the payment application to complete the payment and refresh the payment status, so that the user can perform related operations after the payment is successful, such as viewing order information, logistics information, etc.

[0029] In addition, the present application also proposes a computer-readable medium storing a computer program code, which implements the above-mentioned payment solution when executed by a processor.

[0030] This application uses a built-in order webpage to load a built-in payment webpage, and makes payments by linking the payment platform through the built-in payment webpage, so that users can complete the payment of goods without jumping to other applications or browsers, which greatly improves the user experience. Furthermore, the payment solution of this application can also pass the payment status obtained to the payment application by calling back the built-in payment webpage and passing the payment status through the built-in payment webpage. Users can understand the payment status through the payment information, further improving the convenience of payment. The payment solution and payment solution system provided by this application can integrate the payment process into the payment application, improve the smoothness of the payment experience, improve the user experience, reduce user churn, simplify the payment process, and further improve the success rate of payment.

[0031] The basic concepts have been described above. Obviously, for those skilled in the art, the above application disclosure is only an example and does not constitute a limitation of the present application. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements and amendments to the present application. Such modifications, improvements and amendments are suggested in the present application, so such modifications, improvements and amendments still belong to the spirit and scope of the exemplary embodiments of the present application.

[0032] At the same time, the present application uses specific words to describe the embodiments of the present application. For example, "one embodiment", "an embodiment", and / or "some embodiments" refer to a certain feature, structure or characteristic related to at least one embodiment of the present application. Therefore, it should be emphasized and noted that "one embodiment" or "an embodiment" or "an alternative embodiment" mentioned twice or more in different positions in this specification does not necessarily refer to the same embodiment. In addition, some features, structures or characteristics in one or more embodiments of the present application can be appropriately combined.

[0033] Some aspects of the present application may be performed entirely by hardware, entirely by software (including firmware, resident software, microcode, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as "data blocks", "modules", "engines", "units", "components" or "systems". The processor may be one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DAPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or combinations thereof. In addition, various aspects of the present application may be expressed as computer products located in one or more computer-readable media, which include computer-readable program codes. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, tapes ...), optical disks (e.g., compact disks CDs, digital versatile disks DVDs ...), smart cards, and flash memory devices (e.g., cards, sticks, key drives ...).

[0034] A computer-readable medium may include a propagated data signal containing computer program code, such as in baseband or as part of a carrier wave. The propagated signal may have a variety of manifestations, including electromagnetic, optical, etc., or a suitable combination. A computer-readable medium may be any computer-readable medium other than a computer-readable storage medium, which may be connected to an instruction execution system, device or apparatus to communicate, propagate or transmit a program for use. The program code on the computer-readable medium may be propagated via any suitable medium, including radio, cable, fiber optic cable, radio frequency signal, or similar medium, or any combination of the above mediums.

[0035] Similarly, it should be noted that in order to simplify the description of the disclosure of this application and thus help understand one or more application embodiments, in the above description of the embodiments of this application, multiple features are sometimes merged into one embodiment, figure or description thereof. However, this disclosure method does not mean that the features required by the object of this application are more than the features mentioned in the claims. In fact, the features of the embodiments are less than all the features of the single embodiment disclosed above.

[0036] In some embodiments, numbers describing the number of components and attributes are used. It should be understood that such numbers used in the description of the embodiments are modified by the modifiers "about", "approximately" or "substantially" in some examples. Unless otherwise specified, "about", "approximately" or "substantially" indicate that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may change according to the required features of individual embodiments. In some embodiments, the numerical parameters should take into account the specified significant digits and adopt the general method of retaining digits. Although the numerical domains and parameters used to confirm the breadth of their range in some embodiments of the present application are approximate values, in specific embodiments, the setting of such numerical values ​​is as accurate as possible within the feasible range.

[0037] Although the present application has been described with reference to the current specific embodiments, ordinary technicians in this technical field should recognize that the above embodiments are only used to illustrate the present application, and various equivalent changes or substitutions may be made without departing from the spirit of the present application. Therefore, as long as the changes and modifications to the above embodiments are within the essential spirit of the present application, they will fall within the scope of the claims of the present application.

Claims

1. A payment solution, characterized in that: The steps include: Get order information of payment application; Create a built-in order webpage according to the order information and load a built-in payment webpage, and make payment through the built-in payment webpage linking to the payment platform; The built-in payment webpage is called back and the payment situation is transmitted through the built-in payment webpage, and the payment situation is obtained and transmitted to the payment application.

2. The payment solution as claimed in claim 1, characterized in that: The order information includes order number, order amount, order time, order quantity and order SKU.

3. The payment solution as claimed in claim 1, characterized in that: The built-in order web page includes a webview.

4. The payment solution as claimed in claim 1, characterized in that: The built-in payment web page includes an H5 payment page.

5. The payment solution according to claim 1, wherein: Acquiring the payment status and transmitting it to the payment application includes updating the status of the built-in payment webpage.

6. A payment settlement system, characterized in that include: An order module, wherein the order module is configured to obtain order information of a payment application; A built-in order module, wherein the built-in order module is configured to create a built-in order webpage according to the order information and load a built-in payment webpage, and make payment by linking the built-in payment webpage to a payment platform; A payment feedback module, wherein the payment feedback module is configured to call back the built-in payment webpage and transmit the payment status through the built-in payment webpage, obtain the payment status and transmit it to the payment application.

7. The payment settlement system according to claim 6, characterized in that: The order module includes purchasing services, which include membership subscriptions and / or digital goods.

8. The payment settlement system according to claim 6, characterized in that: The payment feedback module includes a payment interface and a payment account, and the payment interface and the payment account perform account interaction in the built-in payment webpage.

9. The payment settlement system according to claim 6, characterized in that: The payment application includes a mobile phone payment application and a computer payment application.

10. A computer readable medium storing computer program code, wherein the computer program code implements the method according to any one of claims 1 to 5 when executed by a processor.

Images