CN114493731A

CN114493731A - Merchant information processing system, method and medium

Info

Publication number: CN114493731A
Application number: CN202011159337.9A
Authority: CN
Inventors: 张璐; 张国庆
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-10-26
Filing date: 2020-10-26
Publication date: 2022-05-13

Abstract

The present application relates to the field of computer technologies, and in particular, to a system, a method, and a medium for processing merchant information, where the system includes: the system can be used for realizing the unified management of merchant information under the operation of a plurality of services, providing merchant parking and merchant information modification services under multiple scenes for the business parking business system, and improving the merchant information processing efficiency.

Description

Merchant information processing system, method and medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a system, a method, and a medium for processing merchant information.

Background

At present, most service platforms support multiple services, and a merchant needs to log in a corresponding service in the service platform before using a certain service with the help of the service platform. The docking processes corresponding to different services are different, so in the related art, the merchant terminal is directly and directly docked with the service background to be docked, and the merchant docking process is completed.

However, in this way, different business backgrounds are required to filter and manage merchant information input when merchants stay in, and more merchants stay in need to be processed in each period of time in the business background, which results in low efficiency of merchant stay.

Disclosure of Invention

Embodiments of the present application provide a system, a method, and a medium for merchant information processing, so as to improve merchant information processing efficiency.

In one aspect, an embodiment of the present application provides a merchant information processing system, including a parking service subsystem, a merchant information processing subsystem, and a service subsystem, where:

the system comprises a parking business subsystem, a merchant information processing subsystem and a business service subsystem, wherein:

the parking business subsystem is used for acquiring information corresponding to each information item in a target merchant information model according to the target merchant information model matched with the business service to be parked currently by the merchant, and acquiring merchant information of the merchant; the target merchant information model comprises at least one information item required by a merchant for residing in a corresponding business service;

the business information processing subsystem is used for receiving the business information of the business, classifying and storing various information in the business information according to the business information, determining target business information required by the business service subsystem from the business information, and sending the target business information to the business service subsystem;

and the business service subsystem is used for receiving the target merchant information and carrying out merchant parking processing according to the target merchant information.

The embodiment of the application provides a merchant information processing method, which comprises the following steps:

the merchant information processing subsystem receives merchant information from the parking service subsystem; the merchant information comprises information corresponding to each information item in a target merchant information model acquired by the resident service subsystem; the target merchant information model is a merchant information model matched with the business service to be currently resident by the merchant;

and when the resident business subsystem receives the merchant information, classifying and storing various information in the merchant information, determining target merchant information required by the business service subsystem from the merchant information, and sending the target merchant information to the business service subsystem so that the business service subsystem performs merchant resident processing according to the target merchant information.

In a possible embodiment, the method further comprises:

receiving a merchant number application request from the parking business subsystem, and sending the merchant number application request to the business service subsystem; the merchant number application request is used for requesting a unique merchant number of the merchant;

and when a merchant number is received from the business service subsystem, the merchant number is sent to the resident business subsystem, so that the merchant number is carried in the merchant information by the resident business subsystem.

In one possible embodiment, after entering target merchant information required for hosting the business service subsystem to the business service subsystem, the method further comprises:

receiving and storing the merchant state fed back by the business service subsystem;

and when a merchant state query request is received from the parking service subsystem, feeding back the merchant state to the parking service subsystem.

the parking service subsystem acquires information corresponding to each information item in a target merchant information model according to the target merchant information model matched with the service to be parked currently by the merchant, and acquires merchant information of the merchant;

and sending the merchant information to a merchant information processing subsystem, so that the merchant information processing subsystem determines target merchant information required by the business service subsystem from the merchant information and sends the target merchant information to the business service subsystem.

In a possible embodiment, acquiring information corresponding to each information item in a target merchant information model according to the target merchant information model matched with a business service currently needing to be hosted by a merchant, to obtain merchant information of the merchant, includes:

receiving a merchant number sent from the merchant information processing subsystem;

according to merchant information input operation, obtaining information corresponding to each information item in the target information model;

and generating merchant information of the merchant according to the information corresponding to each information item in the target information model and the merchant number.

In a possible embodiment, after the sending the merchant information of the merchant to the merchant-information processing subsystem, the method further includes:

generating a merchant state query request according to the merchant state query operation, and sending the merchant state query request to a merchant information processing subsystem;

receiving a merchant state from the merchant information processing subsystem service.

according to the merchant information modification operation, obtaining modified merchant information and generating a merchant information modification request carrying the modified merchant information;

and sending the merchant information modification request to the merchant information processing subsystem so that the merchant information processing subsystem modifies the merchant information stored by the merchant information processing subsystem and sends the modified merchant information to the business service subsystem.

An embodiment of the present application provides a merchant information processing apparatus, including:

the receiving and sending module is used for receiving the merchant information from the resident service subsystem; the merchant information comprises information corresponding to each information item in a target merchant information model acquired by the resident service subsystem; the target merchant information model is a merchant information model matched with the business service to be currently resident by the merchant;

the storage module is used for storing various information in the merchant information in a classified manner when the resident service subsystem receives the merchant information;

the receiving and sending module is used for determining target merchant information required by the business service subsystem from the merchant information and sending the target merchant information to the business service subsystem so that the business service subsystem performs merchant parking processing according to the target merchant information.

the acquisition module is used for acquiring information corresponding to each information item in a target merchant information model according to the target merchant information model matched with the business service currently to be resident by the merchant, and acquiring merchant information of the merchant;

the receiving and sending module is used for sending the merchant information to a merchant information processing subsystem so that the merchant information processing subsystem determines target merchant information required by the business service subsystem from the merchant information and sends the target merchant information to the business service subsystem.

An embodiment of the present application provides a computer device, including:

at least one processor, and

a memory communicatively coupled to the at least one processor;

wherein the memory stores instructions executable by the at least one processor, the at least one processor implementing any of the merchant information processing methods as previously discussed by executing the instructions stored by the memory.

Embodiments of the present application provide a storage medium storing computer instructions that, when executed on a computer, cause the computer to perform any of the merchant information processing methods as discussed above.

The embodiment of the application at least comprises the following beneficial effects:

in the embodiment of the application, the merchant information processing system comprises an enrollment business subsystem, a merchant information processing subsystem and a business service subsystem, the merchant information processing subsystem creates merchant information models for each business service by regulating merchant information management requirements of different business services, and shares the merchant information models with the enrollment business subsystem, on one hand, the enrollment business subsystem collects merchant information according to the business service to be enrolled by the current merchant and feeds the collected merchant information back to the merchant information processing system, and then the merchant information processing system is in butt joint with the business service subsystem to simplify the merchant enrollment flow, on the other hand, the merchant information processing subsystem can provide target merchant information required by the business service subsystem according to the business service subsystem to be enrolled by the current merchant after obtaining the merchant information, so that the business service subsystem can quickly finish the merchant parking according to the target merchant information. The business service subsystem does not need to filter the merchant information at the later stage and the like, and does not need to process a large amount of merchant information, so that the efficiency of merchant information processing can be improved. In addition, the business-resident subsystem collects the information required by the business-resident business service, so that the conditions of filtering the information of the business and collecting invalid information in the later period are avoided, and the information processing efficiency of the business is improved. In addition, the embodiment of the application can be used for solving the problem of unified management of the information of the merchants under the operation of a plurality of businesses, and improving the efficiency of the merchant parking for parking and modifying the information service of the merchants of different business service subsystems under the parking business service.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1A is a schematic diagram of an application scenario of a merchant information processing scheme according to an embodiment of the present application;

fig. 1B is a schematic diagram of an application scenario of another merchant information processing scheme provided in the embodiment of the present application;

FIG. 2A is a block diagram of a merchant information processing system according to an embodiment of the disclosure;

fig. 2B is a schematic distribution diagram of subsystems in a merchant information processing system according to an embodiment of the present disclosure;

fig. 2C is a schematic deployment diagram of subsystems in a merchant information processing system according to an embodiment of the present disclosure;

fig. 3A is a schematic flow chart of merchant enrollment according to an embodiment of the present disclosure;

FIG. 3B is a diagram illustrating an example of a web page provided by an embodiment of the present application;

FIG. 3C is a diagram of another example of a web page provided by an embodiment of the present application;

FIG. 4 is a schematic flow chart illustrating a process for modifying merchant information according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of interaction between subsystems shown in FIG. 2A according to an embodiment of the present disclosure;

fig. 6 is a schematic flow chart of permission activation provided in the embodiment of the present application;

fig. 7 is a schematic process diagram of a merchant information query provided in an embodiment of the present application;

FIG. 8 is a schematic diagram of a process for modifying merchant information according to an embodiment of the present disclosure;

fig. 9 is a schematic structural diagram of a merchant information processing apparatus according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of another merchant information processing apparatus according to an embodiment of the present disclosure;

fig. 11 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the technical solutions of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments described in the present application without any creative effort belong to the protection scope of the technical solution of the present application.

Some concepts related to the embodiments of the present application are described below.

1. The service party: the platform has a self merchant management platform, can expand merchants and can provide paid services or management services for the merchants. Such as an enterprise payment type merchant platform, an instant messaging type merchant platform, a group type merchant platform, a test type merchant platform, and the like.

2. Service: it is understood that the merchant is provided with the underlying business services, such as providing a money receiving service, a payment service, a settlement service, a wind control service or a refund service, etc.

3. Managing and controlling service: one under a business service is a management platform or team used to ensure that the business service is operating properly and legitimately. Specifically, for example, a compliance service, a wind control service, or the like. Wherein, wind control is a job of controlling the financial loss risk of enterprises in modern economic management. Briefly, "make finance not suffer unexpected loss". For the sake of memory, it is understood as "risk control," which means that a risk manager takes various measures and methods to eliminate or reduce various possibilities of occurrence of a risk event, or a risk controller reduces losses caused when a risk event occurs.

4. Mobile Device Management (MDM): the platform Technology for transition from enterprise IT to mobile Internet helps enterprises extend Information Technology (IT) management capability from traditional Personal Computers (PCs) to mobile devices and even mobile Applications (APPs). With the development of time, MDM manufacturers gradually expand more functions such as Mobile Application Management (MAM), Mobile Email Management (MEM), and Mobile Content Management (MCM).

5. An MDM system: the method is used for managing the life cycle of the mobile equipment facing enterprise equipment, and uniformly managing all links of registration, activation, logout, loss and elimination of the mobile equipment. The MDM system provides strong equipment control capability, comprises mechanisms such as function limitation, remote screen locking, remote erasing, remote configuration, remote positioning, jail-crossing monitoring, remote pushing and unloading of applications and the like, and has equipment management capabilities such as delivery equipment authorization, activation limitation, asset statistics and the like. Based on the MDM, the enterprise can realize life cycle management, configuration management and safety control of the user equipment.

6. Merchant information: various information of the merchant is referred, including information required by the merchant for business service. According to the use scenario and the business service requirement, the merchant information in the application can be classified into the following categories: basic information, qualification information, personnel information, bank information, settlement contract information, authority information and invoice information. Each information category includes at least one information item.

The basic information classification describes basic information required by the merchant; the qualification information classification describes information required by the qualification of the merchant; the personnel information classification describes the personnel information included by the merchant; the bank information classification describes bank information associated with the merchant; the settlement contract information describes contract information signed by the merchant and the service party in a classified manner; the authority information describes the business authority of the merchant on the business side in a classified manner; the invoice information classification describes relevant information of merchant invoices.

7. The merchant information model is as follows: for representing a collection of information items required for hosting a business service. Since the information items correspond to the respective information categories, the merchant information model can be understood as a set of information categories required by the resident business service. Aiming at a platform corresponding to the same business service, the business service platform may include a plurality of business service subsystems, for example, the business service platform a includes a core business subsystem and a settlement business subsystem, and information required by each business service subsystem may not be identical, for example, information classification required by the core business includes basic information, qualification information, personnel information, bank information, authority information and invoice information; the information classification required by the settlement service includes basic information, qualification information, personnel information, settlement contract information, authority information, invoice information and the like.

The following examples of the various information categories are described with reference to the information items included under the information categories shown in table 1:

TABLE 1

Table 1 is an example of each information category, and actually does not limit the information items included in each information category.

In the related art, merchant information processing relates to various links such as merchant docking, merchant information modification, merchant cancellation and the like, each link may relate to a plurality of systems, for example, merchant docking relates to a plurality of systems such as business, core, settlement, collection and payment and the like, and business management modes corresponding to different systems are different.

The following introduces the design idea of the embodiment of the present application:

in view of this, an embodiment of the present application provides a merchant information processing scheme, in which a merchant information processing subsystem creates a merchant information model for each business service by normalizing merchant information management requirements of different business services, a parking business subsystem can provide a corresponding target merchant information model for the business service according to a business service to be parked by a current merchant, merchant information is acquired according to the target merchant information model, and the acquired merchant information is fed back to the merchant information processing system, and then the merchant information processing system determines target merchant information required by the parking business service subsystem, so that the business service subsystem completes a merchant parking process according to the target merchant information.

In the embodiment of the application, the business service subsystem does not need to carry out subsequent excessive processing on the merchant information at the later stage, so that the efficiency of merchant information processing can be relatively improved; the second time, the merchant information processing system can be directly connected with the plurality of resident business subsystems in an abutting mode, and can also be connected with the plurality of business service subsystems in an abutting mode, unified management of merchant information is achieved, merchant information processing efficiency is improved, the problem of unified management of merchant information under operation of a plurality of businesses is solved, and functions of merchant resident, merchant information modification and the like under multiple scenes are provided for the business resident business system.

The preferred embodiments of the present application will be described below with reference to the accompanying drawings of the specification, it should be understood that the preferred embodiments described herein are merely for illustrating and explaining the present application, and are not intended to limit the present application, and that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.

Fig. 1A is a schematic diagram of an application scenario to which the merchant information processing scheme according to the embodiment of the present application can be applied, where the application scenario includes a plurality of terminals 110 and a server 120. Each terminal 110 and the server 120 may communicate with each other through a communication network. The communication network is a wired network or a wireless network. In fig. 1A, two terminals 110 are taken as an example, and the number of terminals 110 is not limited in practice.

Wherein the terminals 110 are devices used by users who deal with merchant residency, each terminal 110 can access the server 120 through a web page or a client. The client related to the embodiments of the present application may be a client such as a software application or an applet, and the server 120 is a background corresponding to the client or the web page.

In the embodiment of the present application, the server 120 is used for implementing the functions of the merchant information processing system related to the present application. The functions of the subsystems in the merchant information processing system are all deployed on the same hardware carrier, and may be implemented by a process in the server 120, or implemented by a part of servers in a corresponding server cluster, for example. Each subsystem in the merchant information processing system is obtained by packaging different functional modules in the merchant information system for providing business services. For example, the business party a can provide the settlement and payment functions, package each module of the business party providing the settlement function, obtain the business service subsystem a1, package each module of the business party a providing the payment function, and obtain the business service subsystem a 2.

Specifically, the merchant information processing system comprises a resident business subsystem, a merchant information processing subsystem and a business service subsystem. The resident service subsystem is used for interacting with the terminal 110 used by the user, receiving various requests sent by the user through the terminal 110, and feeding back the various requests to the merchant information processing subsystem. The merchant information processing subsystem is used for receiving various requests and connecting the business service subsystem to complete various processing requests, and the merchant information processing subsystem is also used for feeding back the results of the processing requests to the parking business subsystem.

Referring to fig. 1B, for another application scenario in which the merchant information processing scheme according to the embodiment of the present application is applicable, compared to fig. 1A, each subsystem in the merchant information processing system in fig. 1B may be implemented by different servers, which is equivalent to that each subsystem in the merchant information processing system is disposed on mutually independent hardware carriers. Taking fig. 1B as an example, the business-resident subsystem in the merchant information processing system is implemented by the first server 120-1, the merchant information processing subsystem is implemented by the second server 120-2, and the business service subsystem is implemented by the third server 120-3. For example, the business party a supports the settlement function, and the settlement function of the business party a may be separately packaged and implemented by the first server 120-1.

It should be noted that, in the embodiment shown in fig. 1B, hardware devices in which the subsystems are deployed may communicate with each other, for example, the second server 120-2 may communicate with the first server 120-1 and the third server 120-3, and the communication manner is various, which is not limited in this application.

The main functions of each subsystem in the merchant information processing system may refer to the contents discussed in fig. 1A, and are not described herein again.

The terminal 110 discussed in fig. 1A to 1B may be a mobile phone, a tablet computer, a Personal Digital Assistant (PDA), a notebook computer, an intelligent wearable device (such as a smart watch and a smart band), a Personal computer, or the like. Each terminal 110 communicates with a server 120 through a wireless network. The server 120 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a web service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like.

To further explain the merchant information processing scheme provided in the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or figures, more or less operation steps may be included in the method based on the conventional or non-inventive labor. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application. The method can be executed in sequence or in parallel according to the method shown in the embodiment or the figures when the method is executed in an actual processing procedure or a device (for example, a parallel processor or an application environment of multi-thread processing).

Referring to fig. 2A, which is a schematic diagram of an architecture of a merchant information processing system according to an embodiment of the present disclosure, the merchant information processing system 200 includes a parking business subsystem 210, a merchant information processing subsystem 220, and a business service subsystem 230.

The resident service subsystem 210 is, for example, a service a subsystem, a service B subsystem, a service C subsystem, a service D subsystem, a service E subsystem, or a service F subsystem in fig. 2A. For example, when a user wants a merchant to park in a certain service subsystem 230 corresponding to the service a subsystem, the user may access the service a subsystem through the terminal 110.

The merchant information processing subsystem 220 provides unified management of merchant information, such as providing a merchant inquiry function, a merchant management function or a public service management function. The merchant management function includes, for example, a merchant enrollment management function, a merchant operation management function, a merchant clearing management function, a merchant authority management function, and the like. When the merchant information processing subsystem 220 provides the common service management function, it may be necessary to obtain external information via, for example, interfacing with, an external system. External systems such as MDM systems.

The business service subsystem 230 interfaces with the merchant information processing subsystem 220, and performs parking processing and the like on the merchant information fed back by the merchant information processing subsystem 220. The business service subsystem 230 is, for example, a core subsystem, a settlement subsystem, a balance subsystem or a wind control subsystem shown in fig. 2A.

To more clearly illustrate the merchant information processing system shown in FIG. 2A, an example description is provided below in conjunction with the distribution schematic diagram of the merchant information processing system shown in FIG. 2B:

the inbound service subsystem 210 is distributed on the service side and interfaces with the user's terminal 110. The merchant information processing subsystem 220 may interface with various external systems and the docking service subsystem 210 to manage various merchant information for the merchant. Business services subsystem 230 is distributed at the bottom layer and interfaces with merchant information processing subsystem 220.

To more clearly illustrate the merchant information processing system shown in FIG. 2A, an example description is provided below in conjunction with the deployment diagram of the merchant information processing system shown in FIG. 2C:

when the business service subsystem provides corresponding services for the merchant, the resident business subsystem 210 accesses the merchant information processing subsystem 220 through the gateway and the relay, and the merchant information processing subsystem 220 accesses the business service subsystem 230 through various business service relays respectively.

For example, the service a and the service B may access a clearing out-of-clearing-area relay through a financial gateway, the clearing out-of-clearing-area relay accesses a clearing set access layer or an integration layer, and then accesses a payment relay through a service of the merchant information processing subsystem, the payment relay accesses a core service through a payment intermediate layer, and may also access a wind-controlled relay through a service of the merchant information processing subsystem, and the wind-controlled relay accesses a wind-controlled service through a wind-controlled intermediate layer.

Or for example, the service C may access a clearing out-of-clearing-domain relay through a clearing gateway, the clearing out-of-domain relay accesses a clearing set access layer or an integration layer, and then accesses a payment relay through a merchant information processing subsystem service, the payment relay accesses a core service through a payment intermediate layer, and may also access a wind-controlled relay through a merchant information processing subsystem service, and the wind-controlled relay accesses a wind-controlled service through a wind-controlled intermediate layer.

Based on fig. 2A to fig. 2C, functions of subsystems of the merchant information processing system related to the embodiment of the present application are specifically described below.

The merchant information processing system in the embodiment of the application can provide a merchant management function, and the merchant management function specifically includes a merchant residence management function, a merchant state query function, a merchant information modification function, and the like.

The following describes the functions of the merchant information processing system 200 for implementing merchant presence management and merchant status query, with reference to the flow chart of merchant presence shown in fig. 3A.

Firstly, a merchant residence management function:

s301, the parking service subsystem 210 generates a merchant number application request according to the parking application operation.

The user can access the parking service subsystem 210 through the terminal 110 to perform a parking application operation. For example, the user may click a parking application button on the web page, which is equivalent to performing a parking application operation, or the user may perform a selection operation of the business service subsystem on the web page, which is equivalent to performing a parking application operation. The parking service subsystem 210 generates a merchant number application request according to the parking application operation. The merchant number application request requests generation of a unique merchant number for a merchant. The merchant number application request carries a merchant identifier of the merchant, such as a merchant name or an organization code of the merchant.

For example, please refer to fig. 3B, which is a schematic diagram of the terminal 110 displaying the parking application web page, and after the user clicks the parking application button shown in fig. 3B, it is equivalent to the operation of parking application as much as possible. The enrollment application button is specifically "register merchant" as shown in fig. 3B.

S302, the parking service subsystem 210 performs blacklist check.

The parking service subsystem 210 may pre-store a blacklist recording merchant identifications of merchants that are not allowed to park. An enrolled merchant, such as a merchant with a number of credits greater than a threshold, is not allowed. After the merchant enrollment request is generated, the enrollment service subsystem 210 may check whether the merchant currently applying for enrollment belongs to the merchant in the blacklist, and if the merchant currently applying for enrollment belongs to the merchant in the blacklist, terminate the enrollment this time. And if the merchant applying for enrollment at present does not belong to the merchants in the blacklist, executing S303, namely performing wind control, legal affairs and anti-money laundering audit on the merchant.

And S303, the resident business subsystem 210 performs wind control, legal affair and anti-money laundering audit on the merchant.

The enrollment service subsystem 210 may further perform a programmed audit on the merchant, and may refuse the merchant to enroll when the risk level of the merchant is high. And the method can also be used for carrying out legal audit on the merchant, and can refuse the merchant to stay in the house when the merchant has illegal behaviors. And the merchant can also be subjected to anti-money laundering auditing, and when the merchant is determined to have money laundering behavior, the merchant is refused to stay in.

As an embodiment, the parking service subsystem 210 may not be able to determine the conditions of the wind control, the legal affairs, or the anti-money laundering, and the like of the merchant, and at this time, the parking service subsystem 210 accesses the external wind control system, the legal affairs system, the anti-money laundering system, and the like through the interface to perform the auditing of the wind control, the legal affairs, and the anti-money laundering for the merchant.

In the embodiments shown in S302 to S303, the parking service subsystem 210 performs blacklist, wind control, legal affair or anti-money laundering audit and the like on the merchant, so as to ensure that the credibility of the subsequent parked merchant is higher, thereby reducing the risk of the merchant information processing system.

S301 to S303 correspond to a link of auditing access to a merchant, and as an embodiment, S302 to S303 are optional steps.

S304, the parking service subsystem 210 sends the merchant number application request to the merchant information processing subsystem 220.

After the enrollment service subsystem 210 determines that the merchant audit is passed, the enrollment service subsystem 210 sends a merchant number application request to the merchant information processing subsystem 220 through the pre-assigned number interface.

S305, the merchant information processing subsystem 220 sends the merchant number application request to the business service subsystem 230.

S306, the business service subsystem 230 generates a merchant number.

S307, the merchant information processing subsystem 220 obtains merchant number information from the business service subsystem 230.

The merchant number information is used to indicate a merchant number, and the merchant number information may be a merchant number.

S308, the resident service subsystem 210 obtains the merchant number information from the merchant information processing subsystem 220.

S304-S308 are links in which the merchant applies for the merchant number, which may facilitate subsequent identification of relevant information of the merchant and may also facilitate the merchant to know the acceptance condition of the current merchant.

As an example, S304-S308 are optional components.

S309, the docking service subsystem 210 determines the target merchant information model.

Since the merchant information required by the merchant to reside in each business service is different, the merchant information processing subsystem 220 in the embodiment of the present application provides a merchant information model that can cover various business services, so as to meet the requirements of the merchant to access different business services. After the merchant information processing subsystem 220 obtains the merchant information models required for the respective business services, a plurality of merchant information models may be sent to the respective resident business subsystems 210 in advance.

The parking business subsystem 210 also obtains merchant information models required for parking each business service in advance, and the merchant information processing subsystem 220 may determine a target merchant model matched with the business service from the plurality of merchant information models according to the business service selected by the merchant and required to be parked. Or, the parking service subsystem 210 determines the service to be parked by the merchant according to the page address of the merchant performing the parking application operation, and determines a target merchant model matching the service from the multiple merchant information models, for example, the merchant clicks a link corresponding to the service a to access the parking service subsystem 210, so that the parking service subsystem 210 determines that the merchant wants to park the service a. The target merchant information model includes information items needed to host the business service subsystem.

Or, the parking business subsystem 210 may send the business service that the merchant needs to park currently to the merchant information processing subsystem 220, and the merchant information processing subsystem 220 receives and feeds back the target merchant information model that the merchant needs currently to the parking business subsystem 210, in this way, the merchant information processing subsystem 220 determines the target merchant information model, so as to reduce the processing amount of the parking business subsystem 210.

The above description relates to how the merchant information processing subsystem 220 obtains a plurality of pre-stored merchant information models, and the following description is given as an example:

the first method is as follows:

the merchant information processing subsystem 220 obtains the merchant information model required by each business service subsystem 230 from network resources.

The merchant information processing subsystem 220 may query information items required for hosting the business service subsystems 230 from network resources, and integrate the information items required for hosting each business service subsystem 230 to obtain a merchant information model corresponding to each business service subsystem 230. For example, the name of the service subsystem S is used as a key word to query the set of information items required for hosting the service subsystem S.

The second method comprises the following steps:

the merchant information processing subsystem 220 classifies the information of the merchant information accessed to the network by the merchant according to the various business service subsystems 230, and establishes merchant information models corresponding to the various business service subsystems.

Specifically, the merchant information processing subsystem 220 may collect information requirements of various business service subsystems 230 for the merchant accessing the network, and obtain various information items. And classifying the various information items according to the service scene so as to obtain various information classifications. Each information category may also be associated with an information item belonging to that information category. Each business service subsystem 230 is associated with the corresponding required information classification, so that the merchant information model corresponding to each business service subsystem 230 is obtained according to the information classification associated with the business service subsystem 230 and the information items associated with the information classification. The business scenario may be a business service subsystem where the merchant information is to be embedded, or a type of the business service subsystem to be embedded.

In the process of actually obtaining the pre-stored merchant information model, it may exist that the merchant information models corresponding to the two different business service subsystems 230 are the same, and the merchant information models are the same, which means that the information items included in the two merchant information models are the same.

After the merchant information model corresponding to each business service is obtained, various merchant information models can be obtained. For the convenience of subsequent search, the merchant information processing subsystem 220 may use the business service as a key and the merchant information model corresponding to the business service subsystem as a value to establish an association relationship between the business service subsystem and the merchant information model. When the merchant information processing subsystem 220 sends a plurality of merchant information models to the parking service subsystem 210, the business service and the merchant information model one corresponding to the business service may be sent to the parking service subsystem 210.

S310, the resident service subsystem 210 collects merchant information according to the target merchant information model.

After the resident service subsystem 210 obtains the target merchant information model, information items required to be input by the merchant can be displayed for the merchant through the terminal 110, and the resident service subsystem 210 acquires information corresponding to each information item required by obtaining the target merchant information model according to the input of the merchant through the terminal 110, so that the merchant information is obtained.

In a possible embodiment, since the merchant may have been previously resident in other resident business service subsystems through the merchant information processing system, in this case, the merchant information processing subsystem 220 stores the merchant information of the merchant, and for convenience of distinction, the merchant information of the merchant pre-stored by the merchant information processing subsystem 220 is referred to as historical merchant information in the embodiment of the present application. However, since the business service subsystem that is previously resident is different from the business service subsystem that the current merchant needs to be resident, the merchant information processing subsystem 220 may obtain reference information that matches the information item in the target merchant information model from the pre-stored historical merchant information according to the target merchant information model, and feed back the reference information determined by associating the target merchant information model to the resident business subsystem 210. Under the condition, part of information items in the target merchant information model are associated with corresponding reference information, so that the merchant only needs to confirm whether the reference information is correct or not, and repeated input is not needed. In this embodiment, when the merchant information processing subsystem 220 stores historical merchant information, the business entering subsystem 210 may be started in time, so as to reduce the input amount of the merchant and improve the use experience of the merchant.

After the enrollment service subsystem 210 acquires the merchant information, the merchant information may be fed back to the merchant information processing subsystem 220, and the enrollment service subsystem 210 may feed back the merchant information to the merchant information processing subsystem 220 through an information synchronization interface, for example.

For example, referring to fig. 3C, an exemplary diagram of a target merchant information model displayed by the parking service subsystem 210 is shown in fig. 3C, where the target merchant information model displays various information items that the user needs to fill, such as a main body type, a merchant abbreviation, a customer service telephone, a place of business, and the like.

S312, the merchant information processing subsystem 220 stores the merchant information in a classified manner.

The merchant information processing subsystem 220 may store merchant information in a classified manner after receiving the merchant information, and may store the merchant information in a classified manner according to each information classification when storing the merchant information in a classified manner, so as to arrange the merchant information and obtain each information item in the merchant information in a later period.

In order to reduce the data storage amount, when the merchant information of the merchant is stored in a classified manner, each information item may be associated with an information item identifier, for example, each information item may be represented by two digits, which is convenient for the merchant information processing subsystem 220 to find a corresponding information item, and the like.

In one embodiment, the merchant information processing subsystem 220 stores a verification rule set, which includes at least one verification rule, each verification rule verifying respective information entered. The verification rule may be set according to one or two of the business requirements of each business service system of the merchant information processing subsystem 220 and the information requirements of each information item itself, where the business requirements of the merchant information processing subsystem 220 itself, for example, the authority limit required to be input by the merchant information processing subsystem 220, is 1 digit, the information requirements of the information item itself, for example, the taxpayer identification number requirement, is 12 digit composition, and the like. In this embodiment, the merchant information processing subsystem 220 may check each piece of information in advance, so that the obtained merchant information can meet the requirements.

S313, the merchant information processing subsystem 220 sends the acceptance result to the parking service subsystem 210.

After the merchant information is stored, the merchant information processing subsystem 220 may feed back an acceptance result, so that the enrollment service subsystem 210 may determine the merchant state in time, for example, the acceptance result is "successful in authorization, and is to be corrected".

S309-S313 are the links of synchronizing the information of the commercial tenant.

In one possible embodiment, for example, the user may perform a merchant information query operation through the terminal 110, the enrollment service subsystem 210 generates a merchant information query request in response to the merchant information query operation, the merchant information query request is used to request to query some information of the merchant, and the merchant information query request is sent to the merchant information processing subsystem 220. The merchant information processing subsystem 220 feeds back a corresponding merchant information query result to the parking service subsystem 210 according to the merchant information query operation.

S314, the merchant information processing subsystem 220 sends the target merchant information to the business service subsystem 230.

After the merchant information processing subsystem 220 obtains the merchant information of the merchant, since the merchant information processing subsystem 220 records the information classification required by the business service subsystems 230 to be resident and the information item under each information classification, the merchant information processing subsystem 220 determines each item of information required by the merchant to be resident in the business service subsystems 230 according to the business service subsystems 230 to be resident in the merchant, and can screen out target merchant information from the merchant information, wherein the target merchant information can be understood as the information required by the business service subsystems 230 to be resident, and the target merchant information includes all or part of the merchant information of the merchant. After determining the target merchant information, merchant information processing subsystem 220 sends the target merchant information to business services subsystem 230.

Or, after obtaining the merchant information of the merchant and classifying and storing the merchant information, the merchant information processing subsystem 220 determines the information classification included in the merchant information, thereby determining at least one business service subsystem 230 under the business service where the merchant can reside, and sends target merchant information corresponding to the information classification required by each business service subsystem 230 residing in the at least one business service subsystem 230 to the corresponding business service subsystem 230.

For example, since the merchant information processing subsystem 220 may also obtain other information of the merchant from an external system, the merchant information processing subsystem 220 may send the other information to the business service subsystem after obtaining the other information. For example, as shown with continued reference to fig. 2A, the merchant information processing subsystem 220 may acquire MDM information of the business party by the MDM system and send the MDM information to the business service subsystem 230.

S315, the business service subsystem 230 registers the target merchant information.

After receiving the target merchant information, the business service subsystem 230 may perform a merchant enrollment process according to the target merchant information, and the merchant enrollment process registers the target merchant information of the merchant in the business service subsystem 230, for example.

For example, when the business service subsystem 230 is a core business subsystem, the target merchant information specifically includes basic information, qualification information, personnel information, bank information, authority information, and invoice information, and after receiving the target merchant information, the business service subsystem 230 may register the basic information, qualification information, personnel information, bank information, authority information, and invoice information of the merchant.

Further, if the business service subsystem 230 obtains MDM information from the merchant information processing platform, the business service subsystem 230 may also register MDM information and the like.

II, secondly: merchant state query function

S316, the enrollment service subsystem 210 sends the merchant status query request to the merchant information processing subsystem 220.

After the business service subsystem 230 receives the merchant information, the user may query the merchant state in real time, where the merchant state includes an entry state of the merchant in the business service subsystem 230 during the merchant entry process, such as a data auditing state, an entry auditing state, a successful entry, and the like, and the merchant state also includes an operation state of the merchant after the merchant is entered, such as a normal or frozen state.

For example, the user may perform a merchant state query operation through the terminal 110, where the merchant state query operation is used to request to query the merchant state, for example, the merchant state query operation may be that the user clicks a query button on a corresponding web page of the enrollment service subsystem 210. The enrollment service subsystem 210 generates a merchant state query request according to the merchant state query operation, and sends the merchant state query request to the merchant information processing subsystem 220. The enrollment service subsystem 210 may send a merchant status query request to the merchant information processing subsystem 220, for example, through an audit trail interface.

S317, the business service subsystem 230 sends the merchant state to the merchant information processing subsystem 220.

The business service subsystem 230 can feed back the merchant state to the merchant information processing subsystem 220 in time during the process of parking the merchant, and the merchant information processing subsystem 220 receives and stores the merchant state.

It should be noted that the execution order of S317 and S316 may be arbitrary.

S318, the merchant information processing subsystem 220 feeds back the merchant status to the parking service subsystem 210.

After receiving the merchant state, the enrollment service subsystem 210 may present the merchant state in the web page so that the user can know about the merchant enrollment in time.

S316-S318 are merchant status query links, in this embodiment, the merchant information processing subsystem 220 may provide the merchant status to the parking service subsystem 210 in time, so that the user can know the merchant parking situation in time.

S319, the parking service subsystem 210 signs the settlement electronic agreement, and feeds back the settlement electronic agreement to the merchant information processing subsystem 220.

The enrollment service subsystem 210 may determine that the merchant signed up the settlement electronic agreement based on the signing operation. The parking service subsystem 210, after determining that the merchant has signed up for the settlement e-agreement, may feed back the settlement e-agreement to the merchant information processing subsystem 220.

S320, the merchant information processing subsystem 220 settles the contract agreement.

The merchant information processing subsystem 220 may store the settlement contract agreement and send the settlement contract agreement to the business service subsystem.

S321, the business service subsystem 230 settles the contract information.

The business service subsystem 230 receives the settlement contract information and provides settlement services for the merchant according to the settlement contract information.

S319 to S321 are settlement contract landing links, and when some resident business service subsystems 230 do not relate to settlement contracts, the S319 to S321 parts do not need to be executed.

After the merchant information processing system 200 is described as including the merchant enrollment management function and the merchant status query function, the merchant information processing system 200 is described as modifying the merchant information function with reference to the merchant information modification flow diagram shown in fig. 4.

S401, the parking service subsystem 210 generates a merchant information modification request.

The resident service subsystem 210 generates a merchant information modification request according to the merchant information modification operation performed by the user through the terminal 110. The merchant information modification operation is, for example, the user clicks a merchant information modification button on a corresponding page of the parking service subsystem 210 through the terminal 110. Further, the parking service subsystem 210 may also obtain the modified merchant information according to the input of the user through the terminal 110. The merchant information modification request is used for requesting merchant information, and the merchant information modification request includes modified merchant information.

Since the merchant information actually relates to various information items, when a user requests to modify the merchant information, part of the information items may be modified, or all the information items may be modified, so as to facilitate the merchant information processing subsystem 220 to modify the corresponding information.

S402, the resident service subsystem 210 checks the modified merchant information.

The enrollment service subsystem 210 may perform an audit on the modified merchant information, for example, audit whether the modified merchant information meets legal regulations or not.

After the enrollment service subsystem 210 determines that the modified merchant information check passes, the modified merchant information may be sent to the merchant information processing subsystem 220.

S403, the merchant information processing subsystem 220 performs rule check on the modified merchant information.

Similarly, the merchant information processing subsystem 220 may also pre-store a check rule set, and the content of the check rule set may refer to the foregoing discussion, which is not described herein again. If it is determined that the modified merchant information verification fails, S404 is executed, that is, the merchant information processing subsystem 220 sends a modification failure notification to the parking service subsystem 210. If it is determined that the modified merchant information is verified, S405 is performed, i.e., the modified record is stored, and the modified merchant information is stored. The storing of the modification record specifically includes recording the time for modifying the merchant information, and may also include the modified merchant information and the like.

Further, in order to facilitate the merchant information processing subsystem 220 to manage the merchant information, after the merchant information processing subsystem 220 receives the modified merchant information, the modified merchant information may be stored in the corresponding information item, so as to facilitate subsequent searching for information corresponding to the information item.

S406, the merchant information processing subsystem 220 sends the modified merchant information to the business service subsystem 230.

After receiving the modified merchant information, the business service subsystem 230 may update the previously stored merchant information to the modified merchant information, so as to ensure that the merchant is provided with services according to the latest merchant information. After updating the merchant information, a modification success notification may be generated indicating that the merchant information has been modified.

S407, the business service subsystem 230 sends a modification success notification to the merchant information processing subsystem 220.

S408, the merchant information processing subsystem 220 sends a modification success notification to the parking service subsystem 210.

The portions S401 to S408 are optional portions.

After the description of the merchant information processing system 200 according to the embodiment of the present application, a merchant information processing method implemented by the merchant information processing system 200 according to the embodiment of the present application is described below.

Fig. 5 is a flowchart of a merchant information processing method. The following describes the merchant information processing method in detail with reference to fig. 5:

s501, the parking service subsystem 210 generates a request for applying for a merchant number according to the parking application operation.

The enrollment application operation and the merchant number application request may refer to the foregoing discussion and are not described in detail herein.

S502, the parking service subsystem 210 sends the merchant number application request to the merchant information processing subsystem 220.

S503, the merchant information processing subsystem 220 sends the merchant number application request to the business service subsystem 230.

After receiving the request for applying for the merchant number, the business service subsystem 230 generates the merchant number.

The business number can refer to the content discussed above, and is not described here.

S504, the business service subsystem sends the information of the merchant number to the merchant information processing subsystem 220.

The merchant number information may refer to the content discussed above, and will not be described in detail here.

S505, the merchant information processing subsystem 220 sends the merchant number information to the parking service subsystem 210.

S506, the docking service subsystem 210 determines a target merchant information model.

The merchant information processing subsystem 220 pre-stores a plurality of merchant information models and sends the plurality of merchant information models to the parking service subsystem 210 in advance. The parking business subsystem 210 obtains a target merchant information model according to the business services that the merchant needs to park. The manner in which the multiple merchant information models are obtained can refer to the foregoing discussion, and will not be described herein. The meaning of the merchant information model and the meaning of the target merchant information model may refer to the foregoing discussion, and are not described herein again.

S507, the parking service subsystem 210 collects the merchant information.

The docking service subsystem 210 may collect corresponding merchant information according to the target merchant information model. The merchant information can refer to the content discussed above, and is not described in detail here.

S508, the enrollment service subsystem 210 examines the merchant information.

The resident service subsystem 210 may perform an audit on the merchant information, and the content of the audit may refer to the content in S302 and S303, which is not described herein again.

S509, the docking service subsystem 210 sends the merchant information to the merchant information processing subsystem 220.

S510, the merchant information processing subsystem 220 verifies the merchant information.

The content of the merchant information verified by the merchant information processing subsystem 220 can refer to the content discussed in S403, and is not described in detail here.

S511, the merchant information processing subsystem 220 stores the merchant information in a classified manner.

The manner of classifying and storing the merchant information can refer to the foregoing discussion, and is not described herein.

S512, the merchant information processing subsystem 220 sends the acceptance result to the parking service subsystem 210.

S513, the merchant information processing subsystem 220 sends the merchant information to the business service subsystem 230.

S514, the business service subsystem 230 sends the merchant status to the merchant information processing subsystem 220.

S515, the merchant information processing subsystem 220 sends the permission fulfillment request to the business service subsystem 230.

Since there are many kinds of merchant information obtained by the merchant information processing subsystem 220, the merchant information processing subsystem 220 may call various interfaces in the business service subsystem 230, and register corresponding information in the business service subsystem 230 to complete the process of opening the authority.

For clearer explanation, the authorization opening process related to the merchant information processing subsystem 220 is described below with reference to the schematic flow chart of authorization opening shown in fig. 6:

s601, the merchant information processing subsystem 220 loads basic information.

The basic information is the basic information in the merchant information.

S602, the merchant information processing subsystem 220 loads the merchant registration information.

S603, the merchant information processing subsystem 220 calls the registration interface to perform registration.

The registration interface may be, for example, an interface for the business service subsystem 230 to register the merchant information, and if the registration fails, S604 is performed, that is, the merchant registration failure is returned to the enrollment business subsystem 210. If the registration is successful, S605 is performed, i.e., the registration information table state is updated.

S606, the merchant information processing subsystem 220 loads the authority information.

S607, the merchant information processing subsystem 220 invokes the permission modification interface.

The permission modification interface may be, for example, an interface for the business service subsystem 230 to modify the merchant permission, and if the modification fails, S608 is executed, that is, the permission modification failure is returned to the resident business subsystem 210. If the registration is successful, S609 is executed, that is, the state of the authority information table is updated, and further, the state of the basic information table is updated according to the states of the authority information table and the registration information table.

S516, the business service subsystem 230 sends the permission fulfillment result to the merchant information processing subsystem 220.

S517, the merchant information processing subsystem 220 sends the permission opening result to the parking service subsystem 210.

S518, the parking service subsystem 210 generates a merchant state query request according to the merchant state query operation.

After generating the merchant status query request, the merchant status query request may be sent to merchant information processing subsystem 220.

S519, the merchant information processing subsystem 220 sends the merchant status to the parking service subsystem 210.

In one possible embodiment, the user may query the merchant information through the merchant information processing subsystem 220, and the process of querying the merchant information is illustrated below with reference to the merchant information query flow diagram shown in fig. 7.

S701, the parking service subsystem 210 generates a merchant information query request according to the merchant information query operation.

After generating the merchant information query request, the merchant information query request may be sent to the parking service subsystem 210. The merchant information query request is used for requesting to query merchant information, and the merchant information query request carries a merchant number and information items carrying query.

S702, the merchant information processing subsystem 220 verifies the parameters.

The merchant information processing subsystem 220 may, for example, check whether the format of the merchant number in the merchant information inquiry request meets requirements, etc.

S703, the merchant information processing subsystem 220 determines whether the merchant number is successfully registered.

The merchant information processing subsystem 220 queries the existing merchant and the corresponding merchant information to determine whether the merchant number exists. If the merchant number exists, S704 is executed, i.e., various information tables are queried. If no merchant number exists, a query failure result is returned to the parking service subsystem 210.

S704, the merchant information processing subsystem 220 queries various information tables.

The merchant information processing subsystem 220 stores various information tables associated with merchants, and the merchant information processing subsystem 220 may query the various information tables to obtain corresponding merchant information.

S705, the merchant information processing subsystem 220 feeds back the merchant information query result to the parking service subsystem 210.

In one possible embodiment, the merchant information may be changed, so the user may also modify the merchant information through the merchant information processing subsystem.

The following describes the merchant information modification process with reference to the merchant information modification flowchart shown in fig. 8:

s801, the docking service subsystem 210 sends the merchant information modification request to the merchant information processing subsystem 220.

The parking service subsystem 210 generates a merchant information modification request according to the merchant information modification operation, where the merchant information modification request carries the modified merchant information and the merchant number of the merchant. The enrollment service subsystem 210 sends a merchant information modification request to the merchant information processing subsystem 220.

S802, the ingress service subsystem 210 checks the parameters.

The parking service subsystem 210 may verify each information in the merchant information modification request, for example, may verify whether the merchant number satisfies the set format, and if the merchant information modification request is verified to be failed, the merchant modification failure information may be returned to the parking service subsystem 210.

S803, the merchant information processing subsystem 220 discards the original merchant information according to the inquired original merchant information.

S804, the merchant information processing subsystem 220 writes the modified merchant information.

After invalidating the original merchant information, the merchant information processing subsystem 220 may store the modified merchant information.

Further, after storing the modified merchant information, the merchant information processing subsystem 220 may send the modified merchant information to the business service subsystem 230, so that the business service subsystem 230 can obtain the latest merchant information.

S805, the merchant information processing subsystem 220 sends a modification success notification to the parking service subsystem 210.

After the merchant information processing subsystem 220 determines to modify the merchant information, a modification success notification may be generated indicating that the merchant information processing subsystem 220 has successfully modified the merchant information.

Based on the same inventive concept, an embodiment of the present application provides a merchant information processing apparatus, please refer to fig. 9, the apparatus includes:

a transceiver module 901, configured to receive merchant information from the parking service subsystem; the merchant information comprises information corresponding to each information item in the target merchant information model acquired by the resident service subsystem; the target merchant information model is a merchant information model matched with the business service to be currently resident by the merchant;

the storage module 902 is configured to store each item of information in the merchant information in a classified manner when the resident service subsystem receives the merchant information;

the transceiver module 901 is configured to determine target merchant information required by the business service subsystem from the merchant information, and send the target merchant information to the business service subsystem, so that the business service subsystem performs merchant parking processing according to the target merchant information.

In a possible embodiment, the transceiver module 901 is further configured to:

and sending the plurality of pre-stored merchant information models to the parking service subsystem so that the parking service subsystem determines a target merchant information model from the plurality of merchant information models.

In a possible embodiment, the apparatus further comprises a generating module 903, wherein the generating module 903 is configured to:

classifying various information items required by various business services to obtain information classification of each information item in the various information items;

according to the multiple information classifications, generating a merchant information model corresponding to each business service, and obtaining the information classifications needed by each business service subsystem residing under each business service;

the transceiver module is specifically configured to: and determining target merchant information from the merchant information according to the information classification required by the resident business service subsystem.

In a possible embodiment, the transceiver module 901 is further configured to:

receiving a merchant number application request from the parking business subsystem and sending the merchant number application request to the business service subsystem; the merchant number application request is used for requesting a unique merchant number of a merchant;

and when the merchant number is received from the business service subsystem, the merchant number is sent to the resident business subsystem, so that the merchant number is carried in the merchant information by the resident business subsystem.

In a possible embodiment, the transceiver module 901 is further configured to:

receiving a merchant information modification request from the parking service subsystem; the merchant information modification request is used for requesting to update the merchant information of the merchant, and the merchant information modification request carries the modified merchant information;

and if the modified merchant information is successfully verified, modifying the merchant information stored by the merchant and sending the modified merchant information to the business service subsystem so that the business service subsystem updates the merchant information of the merchant stored by the merchant into the modified merchant information.

In a possible embodiment, the transceiver module 901 is further configured to:

receiving and storing the state of the commercial tenant fed back by the business service subsystem;

and when a merchant state query request is received from the parking service subsystem, the merchant state is fed back to the parking service subsystem.

The apparatus shown in fig. 9 may also be used to implement any of the merchant information processing methods discussed above, and will not be described here again.

Based on the same inventive concept, an embodiment of the present application provides a merchant information processing apparatus, please refer to fig. 10, the apparatus includes:

the acquisition module 1001 is configured to acquire information corresponding to each information item in a target merchant information model according to the target merchant information model matched with the business service currently to be hosted by the merchant, and acquire merchant information of the merchant;

the transceiving module 1002 is configured to send merchant information to the merchant information processing subsystem, so that the merchant information processing subsystem determines, from the merchant information, target merchant information required by the business service subsystem, and sends the target merchant information to the business service subsystem.

In a possible embodiment, the apparatus further comprises a determining module 1003, wherein:

the transceiver module 1002 is further configured to receive multiple merchant information models sent by the merchant information processing subsystem;

the determining module 1003 is configured to determine a target merchant information model corresponding to the business service from the plurality of merchant information models.

In a possible embodiment, the acquisition module 1001 is specifically configured to:

receiving a merchant number sent from a merchant information processing subsystem;

according to the merchant information input operation, obtaining information corresponding to each information item in the target information model;

In a possible embodiment, the apparatus further comprises a first generating module 1004, wherein:

the first generating module 1004 is configured to generate a merchant state query request according to a merchant state query operation after merchant information of a merchant is sent to the merchant information processing subsystem, and send the merchant state query request to the merchant information processing subsystem;

the transceiver module 1002 is configured to receive a merchant status from a merchant information processing subsystem service.

In a possible embodiment, the apparatus further includes a second generating module 1005, where the second generating module 1005 is further configured to obtain, after the merchant information is sent to the merchant information processing subsystem, the modified merchant information according to the merchant information modification operation, and generate a merchant information modification request carrying the modified merchant information;

the transceiving module 1002 is further configured to send a merchant information modification request to the merchant information processing subsystem, so that the merchant information processing subsystem sends the modified merchant information to the business service subsystem.

The apparatus shown in fig. 10 may also be used to implement any of the merchant information processing methods discussed above, and will not be described here again.

For convenience of description, the above parts are separately described as modules (or units) according to functional division. Of course, the functionality of the various modules (or units) may be implemented in the same one or more pieces of software or hardware when implementing the present application.

Based on the same inventive concept, the present application provides a computer device, please refer to fig. 11, which includes a processor 1101 and a memory 1102.

The processor 1101 may be a Central Processing Unit (CPU), or a digital processing unit, etc. The specific connection medium between the memory 1102 and the processor 1101 is not limited in the embodiment of the present application. In the embodiment of the present application, the memory 1102 and the processor 1101 are connected by a bus 1103 in fig. 11, the bus 1103 is indicated by a thick line in fig. 11, and the connection manner between other components is merely illustrative and not limited thereto. The bus 1103 may be divided into an address bus, data bus, control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 11, but this is not intended to represent only one bus or type of bus.

Memory 1102 may be a volatile memory (volatile memory), such as a random-access memory (RAM); the memory 1102 may also be a non-volatile memory (non-volatile memory) such as, but not limited to, a read-only memory (rom), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD), or the memory 1102 may be any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Memory 1102 may be a combination of the memories described above.

The processor 1101 is configured to execute the merchant information processing method discussed above when invoking the computer program stored in the memory 1102, and may also be configured to implement the functions of the merchant information processing system discussed above or to implement the functions of any subsystem in the merchant information processing system discussed above.

Based on the same inventive concept, embodiments of the present application provide a storage medium storing computer instructions, which, when executed on a computer, cause the computer to perform any of the merchant information processing methods discussed above.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Based on the same inventive concept, the embodiments of the present application provide a computer program product, which includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the merchant information processing method.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the method embodiments may be implemented by hardware related to program instructions, and the program may be stored in a computer readable storage medium, and when executed, the program performs the steps including the method embodiments; and the aforementioned storage medium includes: a mobile storage device, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Alternatively, the integrated units described above in the present application may be stored in a computer-readable storage medium if they are implemented in the form of software functional modules and sold or used as independent products. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or portions thereof contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a removable storage device, a ROM, a RAM, a magnetic or optical disk, or various other media capable of storing program code.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. A merchant information processing system is characterized by comprising a resident business subsystem, a merchant information processing subsystem and a business service subsystem, wherein:

the parking business subsystem is used for acquiring information corresponding to each information item in a target merchant information model according to the target merchant information model matched with the business service to be parked currently by the merchant, and acquiring merchant information of the merchant; the target merchant information model comprises at least one information item required by a merchant for registering corresponding business service;

and the business service subsystem is used for receiving the target merchant information and performing merchant parking processing according to the target merchant information.

2. The system of claim 1,

the merchant information processing subsystem is also used for sending a plurality of pre-stored merchant information models to the parking service subsystem;

the resident business subsystem is further configured to receive the plurality of merchant information models and determine a target merchant information model corresponding to the business service from the plurality of merchant information models.

3. The system of claim 2, wherein the merchant information processing subsystem is further configured to classify a plurality of information items required for hosting various business services, and obtain an information classification to which each of the plurality of information items belongs; according to the multiple information classifications, generating a merchant information model corresponding to each business service, and obtaining the information classifications needed by each business service subsystem residing under each business service;

the merchant information processing subsystem is specifically configured to determine the target merchant information from the merchant information according to the information classification required by the business service subsystem.

4. The system of claim 1,

the resident service subsystem is also used for generating a merchant number application request and sending the merchant number application request to the merchant information processing subsystem; the merchant number application request is used for requesting a unique merchant number of the merchant;

the business information processing subsystem is also used for sending the business number application request to the business service subsystem;

the business service subsystem is also used for generating a merchant number when receiving the merchant number application request and sending the merchant number to the merchant information processing subsystem;

the merchant information processing subsystem is also used for sending the merchant number to the parking service subsystem when the merchant number is received;

the entrance business subsystem is specifically configured to receive the merchant number, and generate merchant information of the merchant according to the acquired information corresponding to each information item in the target merchant information model and the merchant number.

5. The system according to any one of claims 1 to 4, wherein the parking service subsystem is further configured to obtain modified merchant information according to a merchant information modification operation, generate a merchant information modification request carrying the modified merchant information, and send the merchant information modification request to the merchant information processing subsystem;

the business information processing subsystem is also used for receiving the business information modification request, modifying the business information stored by the business information processing subsystem and sending the modified business information to the business service subsystem;

the business service subsystem is further configured to receive the modified merchant information, and update the stored merchant information of the merchant to the modified merchant information.

6. The system according to any one of claims 1 to 4, wherein the parking service subsystem is further configured to generate a merchant state query request according to a merchant state query operation, and send the merchant state query request to the merchant information processing subsystem;

the business service subsystem is also used for generating a merchant state according to the merchant parking processing progress;

the business service subsystem is used for receiving business information sent by the business service subsystem and storing the business information, and sending the business information to the business-resident subsystem.

7. A merchant information processing method is characterized by comprising the following steps:

8. The method of claim 7, wherein the method further comprises:

and sending a plurality of pre-stored merchant information models to the parking service subsystem so that the parking service subsystem determines the target merchant information model from the merchant information models.

9. The method of claim 8, wherein the method further comprises:

classifying a plurality of information items required by various business services to obtain information classification of each information item in the plurality of information items;

determining target merchant information required by the business service subsystem from the merchant information, wherein the target merchant information comprises: and determining the target merchant information from the merchant information according to the information classification required by the business service subsystem.

10. The method according to any one of claims 7 to 9, wherein after storing each item of information in the merchant information in a classified manner when the merchant information is received by the parking service subsystem, the method further comprises:

if the modified merchant information is successfully verified, the merchant information stored by the merchant is modified, and the modified merchant information is sent to the business service subsystem, so that the business service subsystem updates the merchant information of the merchant stored by the merchant into the modified merchant information.

11. A merchant information processing method is characterized by comprising the following steps:

12. The method of claim 11, wherein the method further comprises:

receiving a plurality of merchant information models sent by the merchant information processing subsystem;

and determining a target merchant information model corresponding to the business service from the plurality of merchant information models.

13. The method of claim 11 or 12, wherein after sending the merchant information for the merchant to a merchant information processing subsystem, the method further comprises:

14. A storage medium storing computer instructions which, when run on a computer, cause the computer to perform the method of any one of claims 7-10 or 11-13.