WO2021081702A1

WO2021081702A1 - Payment page management method and device, payment system and storage medium

Info

Publication number: WO2021081702A1
Application number: PCT/CN2019/113669
Authority: WO
Inventors: 张钟文; 柳彤; 朱大卫; 汤慧秀
Original assignee: 深圳海付移通科技有限公司
Priority date: 2019-10-28
Filing date: 2019-10-28
Publication date: 2021-05-06
Also published as: CN111801696A

Abstract

A payment page management method and device, a payment system and a storage medium. The payment page management method comprises: obtaining a payment page opening request, wherein the payment page opening request comprises merchant information (S101); creating a first payment page according to the merchant information of the payment page opening request (S102); obtaining an edit instruction, and updating the first payment page to a second payment page according to the edit instruction (S103); and generating a network identity on the basis of the second payment page, and sending the network identity to a payee terminal so that the payee terminal accesses the second payment page by means of the network identity (S104). The payment page management method can automatically generate a corresponding payment page according to merchant information, thereby improving the quickness and safety of electronic payment.

Description

Payment page management method, equipment, payment system and storage medium

Technical field

This application relates to the field of electronic payment technology, in particular to a payment page management method, device, payment system, and computer storage medium.

Background technique

With the advancement of science and technology, the 5th generation HTML (H5) has become a powerful means of publicity and marketing on the Internet platform with its advantages of creativity and fast dissemination. Many companies use H5 pages to make advertisements into a scene to realize the interaction of web pages and enable users to have a more intuitive experience.

The current H5 page generation method is that a visual designer designs a diagram, and then the H5 developer writes the code for development. Due to the large number of merchants, this method of generating H5 pages for merchants’ personalized writing code will spend more time communicating on the needs of operators and developers, resulting in a long development cycle, time and development costs. High and low production efficiency.

Technical solutions

This application provides a payment page management method, device, payment system, and computer storage medium to solve the problems of long development cycle, high development cost, and low generation efficiency in the prior art.

In order to solve the above technical problems, this application proposes a payment page management method, and the payment page management method includes:

Acquiring a payment page opening request, where the payment page opening request includes merchant information;

Creating a first payment page according to the merchant information requested for opening the payment page;

Acquiring an editing instruction, and updating the first payment page to a second payment page according to the editing instruction;

A network identification is generated based on the second payment page, and the network identification is sent to the payment terminal, so that the payment terminal can access the second payment page through the network identification.

In order to solve the above technical problems, this application proposes a payment system, the payment system includes at least a payment terminal and a payment platform, wherein the payment terminal and the payment platform establish a communication connection;

The payment terminal is configured to send a payment page opening request to the payment platform, wherein the payment page opening request includes merchant information;

The payment platform is configured to create a first payment page according to the merchant information requested by the payment page opening request;

The payment terminal is further configured to send an editing instruction to the payment platform based on the first payment page;

The payment platform is further configured to update the first payment page to a second payment page according to the editing instruction;

The payment platform is further configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal accesses the second payment terminal through the network identification. Payment page.

In order to solve the above technical problems, this application proposes a payment page management device. The payment page management device includes an acquisition module, a processing module, and a sending module; wherein the acquisition module and the sending module are coupled to the processing module ；

The obtaining module is configured to obtain a payment page opening request, wherein the payment page opening request includes merchant information;

The processing module is configured to create a first payment page according to the merchant information of the payment page activation request;

The processing module is further configured to obtain an editing instruction, and update the first payment page to a second payment page according to the editing instruction;

The sending module is configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal can access the second payment through the network identification page.

In order to solve the above technical problems, this application proposes a payment page management device, the payment page management device includes a memory and a processor coupled with the memory;

Wherein, the memory is used to store a computer program, and the processor is used to execute the computer program to implement the payment page management method as described above.

In order to solve the above technical problems, this application proposes a computer storage medium, which is used to store a computer program, and when the computer program is executed by a processor, it is used to implement the payment page management method as described above.

Different from the prior art, the beneficial effects of this application are: the payment page management device obtains the payment page opening request, where the payment page opening request includes merchant information; the first payment page is created according to the merchant information of the payment page opening request; the editing instruction is obtained , And update the first payment page to the second payment page according to the editing instruction; generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal accesses the second payment page through the network identification. The payment page management method provided in this application can automatically generate a corresponding payment page according to the merchant information, and improve the speed and security of electronic payment.

Description of the drawings

In order to explain the technical solutions in the embodiments of the present invention more clearly, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained from these drawings without creative work.

Fig. 1 is a schematic flowchart of a first embodiment of a payment page management method provided by the present application;

FIG. 2 is a schematic diagram of the first payment interface in the embodiment shown in FIG. 1;

3 is a schematic flowchart of a second embodiment of the payment page management method provided by the present application;

4 is a schematic flowchart of a third embodiment of the payment page management method provided by the present application;

Figure 5 is a schematic structural diagram of an embodiment of the payment system provided by the present application;

Fig. 6 is a schematic structural diagram of an embodiment of a payment page management device provided by the present application;

FIG. 7 is a schematic structural diagram of another embodiment of the payment page management device provided by the present application;

FIG. 8 is a schematic structural diagram of an embodiment of a computer storage medium provided by the present application.

Embodiments of the present invention

The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

In order to solve the problems of long H5 page development cycle, high development cost, and low generation efficiency in the prior art, this application proposes a payment page management method. Please refer to FIG. 1 for details. FIG. 1 is a schematic flowchart of the first embodiment of the payment page management method provided by the present application. The payment page management method of the present application is applied to a payment page management device.

Among them, the payment page management device may be a server, a terminal device, or a system in which the server and the terminal device cooperate with each other. Correspondingly, the various parts included in the payment page management device, such as each unit, sub-unit, module, and sub-module, can be all set in the server, or all set in the terminal device, or set in the server and the terminal device respectively.

Further, the aforementioned server may be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the server is software, it can be implemented as multiple software or software modules, for example, a software or software module used to provide a distributed server, or it can be implemented as a single software or software module, which is not specifically limited here.

It should be noted that in the description of the payment page management method of this application, the management device is unified as the execution subject.

As shown in Figure 1, the payment page management method of this embodiment specifically includes the following steps:

S101: Acquire a payment page opening request, where the payment page opening request includes merchant information.

Among them, the management device can be equipped with a payment platform, and data management of information interaction can be carried out through the payment platform. When the merchant applies to the payment platform to open the H5 page, the receiving terminal sends a payment page opening request to the management device. Among them, the payment page opening request includes information such as merchant information and application time. Among them, the payment platform of the present application and the merchant implement the payment page management through the payment terminal of this embodiment, and the payment terminal may be a smart phone, a POS machine, a tablet computer, or other terminal devices. The identification, instruction, information, etc. sent or obtained by the merchant can also occur between the payment terminal and the payment platform or gateway.

S102: Create a first payment page according to the merchant information requested for opening the payment page.

Among them, after the management device obtains the payment page activation request, it extracts the merchant information therein. Researchers develop H5 pages based on merchant information and generate corresponding URL (Uniform Resoure Locator) addresses. Specifically, please refer to FIG. 2 for the first payment page of this embodiment. The management device inputs the merchant information into the development page, so that the first payment page displays some fixed items, such as the merchant name "Hong Kong Baptist University", the bill category "tuition", etc.

S103: Obtain an editing instruction, and update the first payment page to the second payment page according to the editing instruction.

Among them, the first payment page is the same template developed by the management device for most merchants. Further, the payment terminal can also customize the front-end display interface of the payment page according to its own needs through the editing function provided by the payment platform.

Specifically, the payment terminal enters the H5 management system of the payment platform by logging in, and enters a custom editing instruction by selecting a drop-down item. For example, the payment terminal can select the supported language and payment currency of the first payment page, and can also enter a custom logo, edit the displayed field name, and so on.

The management device updates the first payment page in FIG. 2 to the second payment page according to the custom editing instructions input by the payment terminal, thereby customizing the front-end display interface of the H5 page according to the needs of the merchant.

S104: Generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal accesses the second payment page through the network identification.

The terminal device generates a network identification based on the second payment page, and the network identification may be a two-dimensional code, and the two-dimensional code is used to store or carry the network address of the first payment page. The H5 management system of the payment platform also provides the function of downloading the QR code. As shown in Figure 2, the receiving terminal can download the corresponding QR code by clicking the download button in it.

After the payment terminal downloads the QR code, it can identify the QR code to access the corresponding second payment page, or send the QR code to its own user group, so that users in the user group can pass the second payment page. The payment page conducts a payment transaction with the payment terminal.

In this embodiment, the payment page management device obtains the payment page activation request, where the payment page activation request includes merchant information; creates the first payment page according to the merchant information of the payment page activation request; obtains the editing instructions, and converts the first payment page according to the editing instructions. A payment page is updated to a second payment page; a network identification is generated based on the second payment page, and the network identification is sent to the payment terminal, so that the payment terminal can access the second payment page through the network identification. The payment page management method provided in this application can automatically generate a corresponding payment page according to the merchant information, and improve the speed and security of electronic payment.

After the embodiment S101 shown in FIG. 1, this application further proposes another specific payment page management method. Please continue to refer to FIG. 3, which is a schematic flowchart of the second embodiment of the payment page management method provided by the present application.

As shown in Figure 3, the payment page management method of this embodiment specifically includes the following steps:

S201: Query whether there is a merchant number in the merchant file.

Among them, after receiving the payment page opening request of the payment terminal, the management device can obtain the merchant number from the merchant information, and inquire whether the merchant number and the corresponding merchant file are stored in the payment management system. If not, go to step S202; if yes, go to step S203.

S202: Return an application failure message, prompting that the payment terminal has not established a merchant profile.

Among them, the payment terminal has not created a merchant profile in the payment management system, indicating that the payment terminal cannot call the functions in the payment management system. At this time, the management device rejects the payment page opening request of the payment terminal and returns an application failure message. To remind the receiving terminal that no merchant profile has been created. The receiving terminal can choose to abandon the opening of the payment page, or apply for the merchant profile of the payment management, so as to continue to apply for the opening of the payment page.

S203: Create a first payment page according to the merchant information requested for opening the payment page.

Wherein, S203 in this embodiment is the same as S102 in the foregoing embodiment, and will not be repeated here.

S204: According to the merchant information, query whether the receiving terminal has activated the payment page authority.

Wherein, the management device further queries whether the receiving terminal has the authority to open the payment page or the authority to edit the payment page. If the receiving terminal does not have the permission to open the payment page, the receiving terminal cannot obtain the network identification of the first payment page; if the receiving terminal does not have the permission to edit the payment page, the receiving terminal cannot customize the front-end display interface of the payment page.

S205: Activate the payment page permission of the payment terminal.

Wherein, when the payment terminal does not have the payment page permission, the management device activates the payment page permission of the payment terminal according to the user information to perform custom editing of the payment page.

After S104 in the embodiment shown in FIG. 1, this application also proposes another specific payment page management method. Please refer to FIG. 4 for details. FIG. 4 is the flow of the third embodiment of the payment page management method provided by this application. Schematic.

As shown in Figure 4, the payment page management method of this embodiment specifically includes the following steps:

S301: Receive a user's page request instruction and tag information, where the tag information is obtained by the user from the payment terminal by scanning a code.

The H5 page is the second payment page in the above embodiment, and the function of the H5 page is provided by a third-party server. When users access H5 pages through a third-party server, they need to be authorized by the payment platform.

Specifically, the management device obtains the merchant number from the merchant information, and generates tag information according to the merchant number and the network identification, where the tag information may be unique authorization token information with a valid period. The management device sends the token information to the receiving terminal, so that the receiving terminal stores and sends the token to users in the subordinate user group.

S302: Verify the tag information. After the verification is passed, the network identification is sent to the user, so that the user can access the second payment page through the network identification.

Among them, when a user accesses an H5 page through a network identifier, the user will submit token information to a third-party server that provides the function of the H5 page. The third-party server queries the payment platform whether there is an authorized token that is associated with the token information and has not expired. If it exists, the verification result is returned.

The third-party server sends H5 page information to the user's terminal, so that the user's terminal display interface jumps to the H5 interface.

S303: Receive user input information based on the second payment page.

Among them, the user inputs payment transaction information in the H5 interface, such as bill account number, payment amount, etc.

Specifically, the management device needs to determine whether the payment transaction information meets the preset verification rule. For example, the input information in the billing account input box should be a numeric string of preset length; the input information in the payment amount input box should be a numeric string, and the default currency of the amount is HKD or other currencies.

S304: Send a payment transaction request to the gateway according to the input information, so that the gateway performs payment transaction processing based on the payment transaction request.

Wherein, the management device sends a payment transaction request to the gateway according to the input information, so that the gateway performs payment transaction processing based on the payment transaction request.

S305: Receive the payment transaction result of the gateway and send it to the user and the payment terminal.

Among them, the management device receives the payment transaction result of the gateway and sends it to the user and the payment terminal to notify the user and the payment terminal of the payment transaction result.

In order to implement the payment page management method described above, this application provides a payment system. Please refer to FIG. 5 for details. FIG. 5 is a schematic structural diagram of an embodiment of the payment system provided in this application.

As shown in FIG. 5, the payment system 600 of this embodiment at least includes a payment terminal 61, a payment platform 62, a gateway 63, and a user 64. The payment terminal 61, the gateway 63, and the user 64 respectively establish a communication connection with the payment platform 62 .

Wherein, the payment terminal 61 is configured to send a payment page opening request to the payment platform 62, where the payment page opening request includes merchant information;

The payment platform 62 is configured to create a first payment page according to the merchant information requested by the payment page opening request;

The payment terminal 61 is also used to send an editing instruction to the payment platform 62 based on the first payment page;

The payment platform 62 is also used to update the first payment page to the second payment page according to the editing instruction;

The payment platform 62 is also configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal 61, so that the payment terminal 61 accesses the second payment page through the network identification.

Further, the payment platform 62 is configured to receive a page request instruction and tag information from the user 64, where the tag information is obtained by the user 64 from the payment terminal 61 by scanning a code;

The payment platform 62 is also used to verify the tag information. After the verification is passed, the network identification is sent to the user 64 so that the user 64 can access the second payment page through the network identification.

Further, the user 64 is used to send input information based on the second payment page;

The payment platform 62 is configured to send a payment transaction request to the gateway 63 according to the input information;

The gateway 63 is configured to perform payment transaction processing based on the payment transaction request, and send the payment transaction result to the payment platform 62;

The payment platform 62 is configured to send the payment transaction result to the user 64 and the payment terminal 61.

In order to implement the above payment page management method, this application also provides a payment page management device. Please refer to Fig. 6 for details. Fig. 6 is a schematic structural diagram of an embodiment of the payment page management device provided by the present application.

As shown in FIG. 6, the payment page management device 700 of this embodiment includes an acquiring module 71, a processing module 72, and a sending module 73, wherein the acquiring module 71 and the sending module 73 are respectively coupled to the processing module 72;

Wherein, the obtaining module 71 is configured to obtain a payment page opening request, where the payment page opening request includes merchant information;

The processing module 72 is configured to create a first payment page according to the merchant information of the payment page activation request;

The processing module 72 is further configured to obtain an editing instruction, and update the first payment page to the second payment page according to the editing instruction;

The sending module 73 is configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal can access the second payment page through the network identification.

In order to implement the above payment page management method, this application also provides another payment page management device. Please refer to FIG. 7 for details. FIG. 7 is a schematic structural diagram of another embodiment of the payment page management device provided by this application.

As shown in FIG. 7, the payment page management device 800 of this embodiment includes a processor 81, a memory 82, an input and output device 83, and a bus 84.

The processor 81, the memory 82, and the input/output device 83 are respectively connected to the bus 84, the memory 82 stores a computer program, and the processor 81 is configured to execute the computer program to implement the payment page management method described in the foregoing embodiment.

In this embodiment, the processor 81 may also be referred to as a CPU (Central Processing Unit, central processing unit). The processor 81 may be an integrated circuit chip with signal processing capability. The processor 81 may also be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component . The general-purpose processor may be a microprocessor or the processor 81 may also be any conventional processor or the like.

This application also provides a computer storage medium. As shown in FIG. 8, the computer storage medium 900 is used to store a computer program 91. When the computer program 91 is executed by a processor, it is used to implement the payment page management method provided in this application. The method described in the example.

The methods involved in the embodiments of the payment page management method provided in this application, when implemented in the form of software functional units and sold or used as independent products, can be stored in the device, for example, a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes. .

The above are only the embodiments of the present invention, and do not limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied to other related technologies In the same way, all fields are included in the scope of patent protection of the present invention.

Claims

A payment page management method, characterized in that the payment page management method includes:

Acquiring a payment page opening request, where the payment page opening request includes merchant information;

Creating a first payment page according to the merchant information requested for opening the payment page;

Acquiring an editing instruction, and updating the first payment page to a second payment page according to the editing instruction;

A network identification is generated based on the second payment page, and the network identification is sent to a payment terminal, so that the payment terminal can access the second payment page through the network identification.
The payment page management method according to claim 1, wherein:

After the step of creating a first payment page according to the merchant information of the payment page activation request, the payment page management method includes:

Query whether the payment terminal has activated payment page authority according to the merchant information;

If not, activate the payment page authority of the payment terminal.
The payment page management method according to claim 2, wherein:

The step of generating a network identification based on the second payment page and sending the network identification to the payment terminal includes:

Acquiring a network address corresponding to the second payment page;

A two-dimensional code is generated according to the network address, and a download address of the two-dimensional code is provided to the payment terminal, so that the payment terminal can download the two-dimensional code through the download address.
The payment page management method according to claim 1, wherein:

The step of obtaining an editing instruction and updating the first payment page to a second payment page according to the editing instruction includes:

Acquire the custom editing instruction of the payment terminal, and customize and edit the front-end display interface of the first payment page according to the custom editing instruction to form the second payment page.
The payment page management method according to claim 1, wherein:

The merchant information includes a merchant number, and after the step of obtaining a payment page activation request, the payment page management method includes:

Check whether the merchant number exists in the merchant file;

If not, return the application failure information, prompting that the payment terminal has not established the merchant profile;

If yes, perform the step of creating the first payment page according to the merchant information requested for opening the payment page.
The payment page management method according to claim 1, wherein:

After the step of generating a network identification based on the second payment page, and sending the network identification to the payment terminal, so that the payment terminal can access the second payment page through the network identification, The payment page management method includes:

Receiving a user's page request instruction and marking information, wherein the marking information is obtained by the user from the payment terminal by scanning a code;

The marking information is verified, and after the verification is passed, the network identification is sent to the user, so that the user can access the second payment page through the network identification.
The payment page management method according to claim 6, wherein:

Before the step of receiving the user's page request instruction and marking information, the payment page management method includes:

Obtain the merchant number from the merchant information;

Generating the tag information according to the merchant number and the network identification;

The marking information is sent to the payment terminal, so that the payment terminal stores the marking information.
The payment page management method according to claim 6, wherein:

After the step of sending the network identification to the user so that the user can access the second payment page through the network identification, the payment page management method includes:

Receiving input information of the user based on the second payment page;

Sending a payment transaction request to the gateway according to the input information, so that the gateway performs payment transaction processing based on the payment transaction request;

Receive the payment transaction result of the gateway and send it to the user and the payment terminal.
The payment page management method according to claim 8, wherein:

After the step of receiving the input information of the user based on the second payment page, the payment page management method includes:

Judging whether the input information meets a preset verification rule;

If it does not match, it will return a verification failure message;

If yes, execute the step of sending a payment transaction request to the gateway according to the input information.
A payment system, characterized in that the payment system at least includes a payment terminal and a payment platform, wherein the payment terminal and the payment platform establish a communication connection;

The payment terminal is configured to send a payment page opening request to the payment platform, wherein the payment page opening request includes merchant information;

The payment platform is configured to create a first payment page according to the merchant information requested by the payment page opening request;

The payment terminal is further configured to send an editing instruction to the payment platform based on the first payment page;

The payment platform is further configured to update the first payment page to a second payment page according to the editing instruction;

The payment platform is further configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal accesses the second payment terminal through the network identification. Payment page.
The payment system according to claim 10, wherein the payment system further comprises a user, wherein the user establishes a communication connection with the payment platform;

The payment platform is configured to receive a page request instruction and tag information of the user, wherein the tag information is obtained by the user from the payment terminal by scanning a code;

The payment platform is also used to verify the marking information, and after the verification is passed, the network identification is sent to the user, so that the user can access the second payment page through the network identification.
The payment system according to claim 11, wherein the payment system further comprises a gateway, wherein the gateway establishes a communication connection with the payment platform;

The user is used to send input information based on the second payment page;

The payment platform is configured to send a payment transaction request to the gateway according to the input information;

The gateway is configured to perform payment transaction processing based on the payment transaction request, and send the payment transaction result to the payment platform;

The payment platform is configured to send the payment transaction result to the user and the payment terminal.
A payment page management device, wherein the payment page management device includes an acquisition module, a processing module, and a sending module; wherein the acquisition module and the sending module are coupled to the processing module;

The obtaining module is configured to obtain a payment page opening request, wherein the payment page opening request includes merchant information;

The processing module is configured to create a first payment page according to the merchant information of the payment page activation request;

The processing module is further configured to obtain the editing instruction, and update the first payment page to a second payment page according to the editing instruction;

The sending module is configured to generate a network identification based on the second payment page, and send the network identification to the payment terminal, so that the payment terminal can access the second payment through the network identification page.
A payment page management device, wherein the payment page management device includes a memory and a processor coupled with the memory;

Wherein, the memory is used to store a computer program, and the processor is used to execute the computer program to implement the payment page management method according to any one of claims 1-9.
A computer storage medium, wherein the computer storage medium is used to store a computer program, and the computer program, when executed by a processor, is used to implement the payment page according to any one of claims 1-9 Management method.