WO2021081705A1 - Method and device for payment platform management, payment platform, and computer storage medium - Google Patents

Abstract

A method and device for payment platform management, a payment platform, and a computer-readable storage medium. The method for payment platform management comprises: acquiring an account-opening instruction of a payment collecting terminal (S101); acquiring account-opening information of the payment collecting terminal on the basis of the account-opening instruction, where the account-opening information comprises merchant registration information, merchant contact information, and merchant business information (S102); creating a merchant file on the basis of the account-opening information of the payment collecting terminal (S103); and configuring a system permission and login information in the merchant file, thus allowing the payment collecting terminal to log in to a payment platform via the login information (S104). The method for payment platform management allows, on the basis of the account-opening instruction of the payment collecting terminal, the automatic acquisition of the account-opening information related to the account-opening instruction, thus creating the merchant file for the payment collecting terminal, and increasing the work efficiency of payment platform management.

Description

Payment platform management method, equipment, payment platform and computer storage medium Technical field

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

Background technique

With the continuous development of science and technology, shopping payment methods have gradually evolved from cash payment methods to electronic payment methods. The use of cash has gradually decreased, and the existing electronic payment platforms need to manually input a large amount of merchant information when managing merchants, which requires a lot of manual time, resulting in low management efficiency and affecting the payment experience of merchants and users.

Technical solutions

This application provides a payment platform management method, device, payment platform, and computer storage medium to solve the problem of complicated and cumbersome payment platform management process in the prior art.

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

Obtain the account opening instructions of the collection terminal;

Acquiring account opening information of the payment terminal based on the account opening instruction, where the account opening information includes merchant registration information, merchant contact information, and merchant business information;

Create a merchant profile according to the account opening information of the payment terminal;

The system authority and login information are configured in the merchant profile, so that the payment terminal can log in to the payment platform through the login information.

In order to solve the above technical problems, this application proposes a payment platform that includes a merchant management system and a login management system; wherein the merchant management system is used to create and manage merchant files, and the login management system is used to manage Login function;

The merchant management system includes an instruction acquisition unit, an information acquisition unit, an archive creation unit, and an information configuration unit;

The instruction acquisition unit is configured to acquire the account opening instruction of the payment terminal; the information acquisition unit is configured to acquire the account opening information of the payment terminal based on the account opening instruction, wherein the account opening information includes merchant registration information, Merchant contact information and merchant business information; the file creation unit is used to create a merchant file based on the account opening information of the payment terminal; the information configuration unit is used to configure system permissions and login information in the merchant file to Enabling the payment terminal to log in to the payment platform through the login management system.

To solve the above technical problems, this application proposes a payment platform management device, the payment platform 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 platform 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 platform management method as described above.

Different from the prior art, the beneficial effects of this application are: the payment platform management device obtains the account opening instructions of the collection terminal; obtains the account opening information of the collection terminal based on the account opening instructions, where the account opening information includes merchant registration information, merchant contact information, and merchant Business information; create a merchant profile based on the account opening information of the payment terminal; configure system permissions and login information in the merchant profile so that the payment terminal can log in to the payment platform through the login information. The payment platform management method provided in this application can automatically obtain account opening information related to the account opening instructions based on the account opening instructions of the payment terminal, thereby creating a merchant profile for the payment terminal and improving the work efficiency of the payment platform management.

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 platform management method provided by the present application;

FIG. 2 is a schematic structural diagram of a merchant management interface in the embodiment shown in FIG. 1;

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

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

FIG. 5 is a schematic diagram of the structure of the login interface in the embodiment shown in FIG. 4;

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

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

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

FIG. 9 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 complicated and cumbersome problem of the current payment platform management process, this application proposes a payment platform management method. Please refer to FIG. 1 for details. FIG. 1 is a schematic flowchart of a first embodiment of a payment platform management method provided by the present application. The follicle measurement method of the present application is applied to a payment platform management device.

among them. The payment platform management device can 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 training model update device, such as the various units, subunits, modules, and submodules, can all be set in the server, all in the terminal device, or 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 platform management method of this application, the management device is unified as the execution subject.

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

S101: Obtain an account opening instruction of the payment terminal.

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. After the new merchant signs a contract with the settled bank or credit card center in the payment platform, the management device obtains the account opening instruction of the payment terminal, and opens an account on the payment platform for the payment terminal based on the account opening instruction. Among them, the account opening instruction may include information such as the opening time, the account opening merchant, and the account opening time limit.

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: Acquire account opening information of the payment terminal based on the account opening instruction, where the account opening information includes merchant registration information, merchant contact information, and merchant business information.

The management device obtains the account opening information of the payment terminal from the network cloud according to the account opening instruction, where the account opening information includes merchant registration information, merchant contact information, and merchant business information.

Specifically, network clouds can be divided into public clouds and private clouds from application scenarios. Among them, public clouds usually refer to clouds that can be used by third-party providers, and public clouds are generally available through the Internet, which may be free or cost-effective. Inexpensive, the core attribute of public cloud is shared resource services, which can provide services in the entire open public network. Private Clouds (Private Clouds) are constructed for a single customer to use, thus providing the most effective control over data, security and service quality. The company owns the infrastructure and can control how applications are deployed on this infrastructure. Private clouds can be deployed in the firewall of an enterprise data center, or they can be deployed in a secure hosting location. The core attribute of a private cloud is proprietary resources. In this embodiment, the private cloud can be constructed for independent use by the settled bank or credit card center in the payment platform.

The management device may obtain the first account opening information of the payment terminal from the public cloud according to the account opening instruction. The first account opening information may include basic information and contact information of the merchant, and specifically may be information such as the name of the merchant, the address of the merchant, and the contact information of the merchant. The management device can also obtain the second account opening information of the collection terminal from the private cloud of the preset bank or the preset credit card center according to the account opening instruction. The second account opening information can be bank information or credit card center information signed by the merchant, which can be specifically a bank or a credit card. Center-specific identification information and/or communication information.

Because the first account opening information of the payment terminal is generally uploaded to the public cloud for storage by the payment terminal itself, or is uploaded to the public cloud for storage by the contracted bank or credit card center. If the first account opening information of the receiving terminal is not stored in the public cloud, the management device will not be able to pull the account opening information of the receiving terminal from the public cloud. Therefore, before obtaining the first account opening information, the management device can also obtain the merchant number of the receiving terminal from the account opening instruction, and use the merchant number to query whether the merchant number and the corresponding account opening information of the receiving terminal are stored in the public cloud . If it does not exist, the management device needs to notify the payment terminal so that the payment terminal uploads the account opening information to the public cloud or directly sends it to the payment platform of the management device. If it exists, the management device can continue to pull the account opening information of the payment terminal.

S103: Create a merchant profile according to the account opening information of the payment terminal.

Among them, the management device creates a merchant profile on the payment platform according to the acquired account opening information of the payment terminal, as shown in Figure 2. The merchant management interface of the payment platform includes the merchant name, merchant number, merchant type, creation date, and operation options. The management personnel of the payment platform or the employees of the merchant can log in to the payment platform to view the specific information of the payment terminal.

Further, when the management personnel of the payment platform enters the merchant number through the merchant management interface in FIG. 2, the merchant profile and operable options corresponding to the merchant number can be further displayed.

S104: Configure system permissions and login information in the merchant profile, so that the receiving terminal logs in to the payment platform through the login information.

Among them, after the management device creates the merchant profile, the system permissions and login information are further configured in the merchant profile. The login information can be the unified account and secret information for the payment terminal to log in to the payment platform, or it can be the multiple account and secret information for multiple employees in the merchant to log in to the payment platform. In the merchant management application scenario, merchants or merchant employees can log in to the payment platform through login information to view or edit merchant profiles.

In this embodiment, the payment platform management device acquires the account opening instructions of the payment terminal; acquires the account opening information of the payment terminal based on the account opening instructions, where the account opening information includes merchant registration information, merchant contact information, and merchant business information; according to the payment terminal Create a merchant profile with the account opening information; configure system permissions and login information in the merchant profile so that the payment terminal can log in to the payment platform through the login information. The payment platform management method provided in this application can automatically obtain account opening information related to the account opening instructions based on the account opening instructions of the payment terminal, thereby creating a merchant profile for the payment terminal and improving the work efficiency of the payment platform management.

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

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

S201: Obtain employee information from the business information of the merchant, and configure employee roles and corresponding employee permissions in the merchant file based on the employee information.

Among them, the management device extracts employee information from the business information of the merchant, and the employee information can be the internal staff composition and the staff structure of the merchant. When the management device configures the system permissions in the merchant file, you can further configure the permissions of each employee in the merchant. For example, for the employees of the business department, the management device only opens the permissions related to the business of the business department in the merchant file; for the employees of the technical department , The management device only opens the authority related to the business of the technical department in the merchant file.

Further, similar to the permission setting for employees, the management device can also configure unique account and secret information for each employee, or configure unique account and secret information for each department.

S202: Send a platform activation email to the payment terminal, where the platform activation email includes at least login information.

Among them, on the premise that the payment terminal has a payment platform mailbox, the management device sends a platform activation email to the corresponding collection terminal. The platform activation email includes login information or specific account and secret information, activation time, payment platform link and other information .

In other embodiments, the management device may also associate payment platform mailboxes with other mailboxes, such as 163 mailboxes, 126 mailboxes, and QQ mailboxes, so that the payment terminal can receive platform activation even when the payment platform mailbox is not set up. mailbox.

S203: Upload the login information corresponding to the payment terminal to the public cloud.

Among them, when the management device sends the platform activation email, it can also upload the login information or specific account and secret information corresponding to the payment terminal to the public cloud to facilitate subsequent calls to the public cloud to verify the user login.

In this embodiment, when the management device configures system permissions for the payment terminal, it can further configure the corresponding permissions for the employee structure of the merchant, so that the payment platform can open different permissions for different employees, and improve the management of the payment platform. Relevance: The management device notifies the receiving terminal to successfully open the merchant profile by sending the platform activation email, and uploads the login information, which facilitates subsequent calls to the public cloud to verify the user login and improves the work efficiency of the payment platform management.

After S104 in the embodiment shown in FIG. 1, this application also proposes another specific payment platform management method. For details, please refer to FIG. 4. FIG. 4 is the flow of the second embodiment of the payment platform management method provided by this application. Schematic.

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

S301: Acquire the account and secret information input by the user, and call the login information stored in the public cloud.

Among them, the management device provides the user with a login interface composed of multiple input boxes through the payment platform, as shown in FIG. 5 in detail. The login interface in FIG. 5 includes at least an account input box, a password input box, a verification code input box, and a login button. After the payment terminal enters the account and secret information and the verification code, click the login button to send a login instruction to upload the account and secret information to the payment platform. When the payment platform receives the login instruction, it calls the login information stored in the public cloud.

S302: Determine whether the account secret information is consistent with the login information.

Among them, the management device adjusts the verification function of the public cloud through the payment platform, and verifies whether the account secret information entered by the user matches the stored login information through the public cloud. If it matches, go to S304; if it does not match, go to S303.

S303: Return the first login failure information to prompt the user that the account password is entered incorrectly.

S304: Whether the user who inquires about the account and secret information has system authority.

Among them, after the management device learns that the public cloud has successfully verified the account and secret information, it further verifies the user's login authority on the platform. If the user does not have the login authority, then go to S305; if the user has the login authority, then go to S306.

S305: Return the second login failure information to prompt the user that the system authority has not been activated.

S306: Display the payment platform interface including the merchant profile corresponding to the system authority.

Wherein, when the user's account and secret information is correct and the user has the login authority, the management device displays the merchant management interface as shown in Figure 2 through the payment platform. The merchant management interface in Figure 2 provides operation buttons, such as "details", "edit", "send mail" and other operation buttons for users to view and manage merchant files. For example, when the user selects the "details" button, the management device displays more information about the merchant profile; when the user selects the "edit" button, the management device modifies the information recorded in the merchant profile according to the subsequent editing instructions entered by the user; When the "Send Mail" button is selected, the management device sends the mail content entered by the user to other users of the payment terminal through the payment platform mailbox.

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

As shown in FIG. 6, the payment platform 600 includes a merchant management system 61 and a login management system 62; wherein, the merchant management system 61 is used to create and manage merchant files, and the login management system 62 is used to manage login functions.

The merchant management system 61 includes an instruction acquisition unit 611, an information acquisition unit 612, an archive creation unit 613, and an information configuration unit 614.

The instruction acquisition unit 611 is used to acquire the account opening instructions of the payment terminal; the information acquisition unit 612 is used to acquire the account opening information of the payment terminal based on the account opening instructions, where the account opening information includes merchant registration information, merchant contact information, and merchant business information; The profile creation unit 613 is used to create a merchant profile based on the account opening information of the payment terminal; the information configuration unit 614 is used to configure system permissions and login information in the merchant profile so that the payment terminal can log in to the payment platform through the login management system.

Among them, the account opening information includes the first account opening information and the second account opening information.

The information obtaining unit 612 is further configured to obtain first account opening information from the public cloud based on the account opening instruction; obtain second account opening information from the private cloud of the preset bank based on the account opening instruction, where the second account opening information includes bank information of the preset bank.

The information acquisition unit 612 is also configured to acquire the merchant number of the payment terminal from the account opening instruction; query whether the merchant number exists in the public cloud; if it exists, acquire the first account opening information corresponding to the merchant number.

The information configuration unit 614 is also used to obtain employee information from the business information of the merchant, and configure employee roles and corresponding employee permissions in the merchant file based on the employee information.

The merchant management system 61 also includes an information sending unit 615. The information sending unit 615 is configured to send a platform activation email to the payment terminal, where the platform activation email includes at least login information. The information sending unit 615 is also used to upload login information corresponding to the payment terminal to the public cloud.

The login management system 62 includes a login input unit 621, a login verification unit 622, and a login sending unit 623. The login input unit 621 is used to obtain the account and secret information input by the user and call the login information stored in the public cloud; the login verification unit 622 is used to determine whether the account and secret information is consistent with the login information; the login sending unit 623 is used to register the account When the secret information is inconsistent with the login information, the first login failure information is returned to prompt the user account password input error.

The login management system 62 also includes a login display unit 624; a login verification unit 622, which is also used to inquire whether the user of the account secret information has system authority when the account secret information is consistent with the login information; When the user of the information has the system authority, the payment platform interface including the merchant profile corresponding to the system authority is displayed; the login sending unit 623 is also used to return the second login failure message when the user of the account and secret information does not have the system authority. The user is prompted that the system authority has not been activated. The login display unit 624 is also used to obtain an input instruction including the merchant number, and display the payment platform interface including the merchant profile corresponding to the merchant number.

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

As shown in FIG. 7, the payment platform management device 700 of this embodiment includes an acquisition module 71, a creation module 72, and a configuration module 73, wherein the acquisition module 71 and the configuration module 73 are respectively coupled to the creation module 72.

Wherein, the acquisition module 71 is used to obtain the account opening instructions of the payment terminal; it is also used to acquire the account opening information of the payment terminal based on the account opening instructions, where the account opening information includes merchant registration information, merchant contact information, and merchant business information.

The creation module 72 is used to create a merchant profile according to the account opening information of the payment terminal.

The configuration module 73 is used to configure system permissions and login information in the merchant profile so that the payment terminal can log in to the payment platform through the login information.

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

As shown in FIG. 8, the payment platform 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 platform 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. 9, 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 platform management method provided in this application. The method described in the example.

The methods involved in the embodiments of the payment platform 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, such as 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 (18)

A payment platform management method, characterized in that, the payment platform management method includes: Obtain the account opening instructions of the collection terminal; Acquiring account opening information of the payment terminal based on the account opening instruction, where the account opening information includes merchant registration information, merchant contact information, and merchant business information; Create a merchant profile according to the account opening information of the payment terminal; The system authority and login information are configured in the merchant profile, so that the payment terminal can log in to the payment platform through the login information. The payment platform management method according to claim 1, wherein: The account opening information includes first account opening information and second account opening information; The step of obtaining account opening information of the payment terminal based on the account opening instruction includes: Acquiring the first account opening information from the public cloud based on the account opening instruction; The second account opening information is acquired from the private cloud of a preset bank based on the account opening instruction, where the second account opening information includes bank information of the preset bank. The payment platform management method according to claim 2, wherein: The step of obtaining the first account opening information from a public cloud based on the account opening instruction includes: Acquiring the merchant number of the payment terminal from the account opening instruction; Query whether the merchant number exists in the public cloud; If it exists, obtain the first account opening information corresponding to the merchant number. The payment platform management method according to claim 2, wherein: The step of configuring system permissions in the merchant profile includes: Obtain employee information from the business information of the merchant, and configure employee roles and corresponding employee permissions in the merchant file based on the employee information. The payment platform management method according to claim 4, characterized in that: After the step of configuring system permissions and login information in the merchant profile, the management method includes: Sending a platform activation email to the payment terminal, wherein the platform activation email includes at least the login information; Upload the login information corresponding to the payment terminal to the public cloud. The payment platform management method according to claim 5, wherein: After the step of configuring system permissions and login information in the merchant profile, the management method includes: Acquire the account and secret information entered by the user, and call the login information stored in the public cloud; Determine whether the account secret information is consistent with the login information; If not, return the first login failure message to prompt that the user account password is entered incorrectly. The payment platform management method according to claim 6, wherein: After the step of judging whether the account secret information is consistent with the login information, the management method includes: If yes, whether the user who inquires the account and secret information has the system authority; If yes, display the payment platform interface including the merchant profile corresponding to the system authority; If not, return the second login failure information to prompt the user that the system authority has not been activated. The payment platform management method according to claim 1, wherein: After the step of configuring system permissions and login information in the merchant profile, the management method includes: Obtain the input instruction including the merchant number, and display the payment platform interface including the merchant profile corresponding to the merchant number. A payment platform, characterized in that the payment platform includes a merchant management system and a login management system; wherein the merchant management system is used to create and manage merchant files, and the login management system is used to manage login functions; The merchant management system includes an instruction acquisition unit, an information acquisition unit, an archive creation unit, and an information configuration unit; The instruction acquisition unit is configured to acquire the account opening instruction of the payment terminal; the information acquisition unit is configured to acquire the account opening information of the payment terminal based on the account opening instruction, wherein the account opening information includes merchant registration information, Merchant contact information and merchant business information; the file creation unit is used to create a merchant file based on the account opening information of the payment terminal; the information configuration unit is used to configure system permissions and login information in the merchant file to Enabling the payment terminal to log in to the payment platform through the login management system. The payment platform according to claim 9, wherein the account opening information includes first account opening information and second account opening information; The information obtaining unit is further configured to obtain the first account opening information from a public cloud based on the account opening instruction; obtain the second account opening information from a private cloud of a preset bank based on the account opening instruction, wherein the first 2. The account opening information includes the bank information of the preset bank. The payment platform according to claim 10, wherein the information obtaining unit is further configured to obtain the merchant number of the payment terminal from the account opening instruction; and query whether the merchant exists in the public cloud Number; if it exists, obtain the first account opening information corresponding to the merchant number. The payment platform according to claim 10, wherein the information configuration unit is further configured to obtain employee information from the business information of the merchant, and configure employee roles and corresponding roles in the merchant file based on the employee information. Employee permissions. The payment platform according to claim 12, wherein the merchant management system further comprises an information sending unit; The information sending unit is configured to send a platform activation email to the payment terminal, wherein the platform activation email includes at least the login information; The information sending unit is further configured to upload login information corresponding to the payment terminal to the public cloud. The payment platform according to claim 13, wherein the login management system comprises a login input unit, a login verification unit, and a login sending unit; The login input unit is configured to obtain account and secret information input by a user, and call the login information stored in the public cloud; The login verification unit is used to determine whether the account secret information is consistent with the login information; The login sending unit is configured to return the first login failure information when the account secret information is inconsistent with the login information to prompt the user account password to be entered incorrectly. The payment platform according to claim 14, wherein the login management system further comprises a login display unit; The login verification unit is further configured to query whether the user of the account and secret information has the system authority when the account and secret information is consistent with the login information; The login display unit is configured to display the payment platform interface including the merchant profile corresponding to the system authority when the user of the account and secret information has the system authority; The login sending unit is further configured to, when the user of the account and secret information does not have the system authority, return the second login failure information to prompt the user that the system authority has not been activated. The payment platform according to claim 15, wherein the login display unit is further configured to obtain an input instruction including the merchant number, and display a payment platform interface including a merchant profile corresponding to the merchant number. A payment platform management device, characterized in that the payment platform 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 platform management method according to any one of claims 1-8. A computer storage medium, wherein the computer storage medium is used to store a computer program, and when the computer program is executed by a processor, it is used to implement the payment platform according to any one of claims 1 to 8. Management method.

Images