Merchant profile data management system and method

Abstract

The application discloses a kind of merchant archives data management system and method, it is related to the field of financial technology, can be used in blockchain field, system includes: application user node, for receiving uploaded merchant archives file and entered merchant archives data, send to storage node through network, in the application user node storage summary, and broadcast summary message to other nodes;Examination and approval user node, for after receiving summary message through network, read the merchant archives data and merchant archives file of storage node through network, carry out audit, and broadcast audit message to other nodes;Application user node is further used: after receiving audit message through network, confirm consistent after summary, operate the summary of application user node storage, send merchant archives data operation instruction to storage node;Storage node, for storing the merchant archives data received through network;Execute operation instruction.The application can realize the automatic import of merchant archives data, approval and efficient storage.

Description

Technical Field

[0001] This invention relates to the field of distributed technology, and in particular to a merchant profile data management system and method. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] The bank's merchant profile system is currently an internal system and is not open to the public. All merchant information is filled in manually by business staff, then manually approved, and then entered into the system. This process is cumbersome and prone to errors.

[0004] Therefore, there is currently a lack of an open and automated method for managing merchant profile data, including merchant profile entry and approval, to address the issues of closed merchant profile systems and entirely manual processes. Summary of the Invention

[0005] This invention provides a merchant file data management system to solve the problems of closed systems and fully manual processes in traditional merchant file systems, enabling automatic import, approval, and efficient storage of merchant file data. The system includes:

[0006] Multiple nodes on a decentralized network structure, the multiple nodes including at least one applicant user node, at least one approval user node, and a storage node;

[0007] The user node is used to receive merchant profile files and entered merchant profile data uploaded by users, send them to the storage node via the network, store a summary of the merchant profile data on the user node, and broadcast the summary message to other nodes.

[0008] The approval user node is used to read the merchant profile data and merchant profile file from the storage node through the network after receiving the summary message through the network, and to review and broadcast the review message to other nodes.

[0009] The application user node is also used to: after receiving an audit message through the network and confirming that the summary in the audit message is consistent with the summary stored by the application user node, operate the summary stored by the application user node according to the audit result in the audit message, and send a merchant profile data operation instruction to the storage node, wherein the operation instruction is an update instruction or a transfer instruction;

[0010] Storage nodes are used to store merchant profile data received over the network and to execute operation instructions on the received merchant profile data.

[0011] This invention also provides a merchant profile data management method, applied to the application user node in a merchant profile data management system, to solve the problems of closed systems and entirely manual processes in merchant profile systems, and to achieve automatic import, approval, and efficient storage of merchant profile data. The method includes:

[0012] Receive merchant profile files uploaded by users and enter merchant profile data;

[0013] Send to the storage node via the network;

[0014] In this application, the user node stores a summary of the merchant profile data and broadcasts the summary message to other nodes.

[0015] After receiving the audit message via the network and confirming that the summary in the audit message is consistent with the summary stored by the user node of this application, the user node operates on the summary stored by this application according to the audit result in the audit message, and sends a merchant profile data operation instruction to the storage node. The operation instruction is an update instruction or a transfer instruction; wherein, the storage node executes the received merchant profile data operation instruction.

[0016] The review message is broadcast by the approving user node after receiving the summary message through the network, reading the merchant profile data and merchant profile file from the storage node through the network, reviewing it, and then broadcasting it.

[0017] This invention also provides another merchant profile data management method, applied to the approval user node in a merchant profile data management system, to solve the problems of closed systems and fully manual processes in merchant profile systems, and to achieve automatic import, approval, and efficient storage of merchant profile data. The method includes:

[0018] After receiving the summary message over the network, the merchant profile data and merchant profile files of the storage node are read over the network. The summary message is broadcast by the requesting user node after receiving the merchant profile files uploaded by the user and the merchant profile data entered by the user, and after storing the summary of the merchant profile data on the requesting user node.

[0019] Verify the merchant profile data and merchant profile files read from the network storage nodes;

[0020] Broadcast the audit message to other nodes;

[0021] When the applicant user node receives the review message via the network and confirms that the summary in the review message is consistent with the summary stored by the applicant user node, it operates on the summary stored by the applicant user node according to the review result in the review message and sends a merchant profile data operation instruction to the storage node for the storage node to execute. The operation instruction is an update instruction or a transfer instruction.

[0022] This invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described merchant file data management method.

[0023] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned merchant profile data management method.

[0024] In this embodiment of the invention, an application user node is used to receive merchant profile files and entered merchant profile data uploaded by users, send them to a storage node via the network, store a summary of the merchant profile data at the application user node, and broadcast the summary message to other nodes. An approval user node is used to, after receiving the summary message via the network, read the merchant profile data and merchant profile files from the storage node via the network, review them, and broadcast the review message to other nodes. The application user node is also used to: after receiving a review message via the network and confirming that the summary in the review message matches the summary stored at the application user node, operate the summary stored at the application user node according to the review result in the review message, and send a merchant profile data operation instruction to the storage node, wherein the operation instruction is an update instruction or a transfer instruction. The storage node is used to store the merchant profile data received via the network and execute the received merchant profile data operation instruction. Compared with existing technologies that require manual approval of profiles, in this embodiment of the invention, all nodes adopt a decentralized network structure, making the entry, approval, and storage of merchant profile data secure and efficient, and realizing automatic import, approval, and efficient storage of merchant profile data. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0026] Figure 1 This is a schematic diagram of the merchant profile data management system in an embodiment of the present invention;

[0027] Figure 2 This is a schematic diagram illustrating the deployment of the merchant profile data management system in an embodiment of the present invention;

[0028] Figure 3 This is a structural diagram of a user node in an embodiment of the present invention;

[0029] Figure 4This is a structural diagram of a storage node in an embodiment of the present invention;

[0030] Figure 5 This is a flowchart of the process for entering a single merchant profile data in an embodiment of the present invention;

[0031] Figure 6 This is a structural diagram of the retrieval node in an embodiment of the present invention;

[0032] Figure 7 This is a flowchart of the online deduction process in an embodiment of the present invention;

[0033] Figure 8 This is a flowchart of the merchant profile data management method in an embodiment of the present invention;

[0034] Figure 9 This is a flowchart of another merchant profile data management method in an embodiment of the present invention;

[0035] Figure 10 This is a schematic diagram of a computer device in an embodiment of the present invention. Detailed Implementation

[0036] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0037] Figure 1 This is a schematic diagram of a merchant profile data management system in an embodiment of the present invention, including:

[0038] Multiple nodes on a decentralized network structure, the multiple nodes including at least one applicant user node 101, at least one approval user node 102, and storage node 103;

[0039] User node 101 is used to receive merchant profile files and entered merchant profile data uploaded by users, send them to the storage node via the network, store a summary of the merchant profile data on this user node, and broadcast the summary message to other nodes.

[0040] Approval user node 102 is used to read the merchant profile data and merchant profile file of the storage node through the network after receiving the summary message through the network, and to review and broadcast the review message to other nodes.

[0041] The application user node 101 is also used to: after receiving an audit message through the network and confirming that the summary in the audit message is consistent with the summary stored by the application user node, operate the summary stored by the application user node according to the audit result in the audit message, and send a merchant file data operation instruction to the storage node, wherein the operation instruction is an update instruction or a transfer instruction;

[0042] Storage node 103 is used to store merchant profile data received over the network and to execute operation instructions on the received merchant profile data.

[0043] In this embodiment of the invention, compared with the prior art which requires manual document approval, all nodes in this embodiment adopt a decentralized network structure, which makes the input, approval and storage of merchant document data secure and efficient, and realizes the automatic import, approval and efficient storage of merchant document data.

[0044] In this embodiment of the invention, the storage nodes are deployed using a distributed database. The decentralized network structure enables all nodes to form a mesh structure, with nodes interconnected. Figure 2 This is a deployment diagram of the merchant file data management system in an embodiment of the present invention. The acquiring system is an external system that communicates with the retrieval node and the storage node to provide services to the outside world. Merchants acquire files for verification.

[0045] Figure 3 The diagram below shows the structure of a user node in an embodiment of the present invention. It is applicable to user node application and user node review. In one embodiment, the node includes an operation management layer storage unit, a basic file layer storage unit, and a product service layer storage unit.

[0046] The operation management layer storage unit is used to record unapproved merchant profile data;

[0047] The basic file layer storage unit is used to record the basic file data in the effective merchant file data;

[0048] The product service layer storage unit is used to record product service data in the effective merchant profile data;

[0049] The application for a user node is specifically used to: store a summary of merchant profile data in the operation management layer storage unit;

[0050] Specifically, the storage node is used to: store merchant profile files and merchant profile data received over the network into the operation management layer storage unit; update the merchant profile data in the operation management layer storage unit when receiving an update instruction; transfer the basic profile data of the merchant profile data in the operation management layer storage unit to the basic profile layer storage unit, transfer the product and service data of the merchant profile data in the operation management layer storage unit to the product and service layer storage unit, and clear the merchant profile files in the operation management layer storage unit when receiving a transfer instruction.

[0051] In the user node, the basic file layer storage unit and the product service layer storage unit are reserved. The operation management layer storage unit stores the merchant file files uploaded by users and the merchant file data entered. Among them, the merchant file data includes merchant attribute file data, department file data, terminal file data and product agreement data. It stores the encrypted data of merchant number, department number, terminal number and temporary number for each type of data. It can also store the hash value of the above data for secure comparison.

[0052] Storage nodes store all data, and are used in the operation management layer storage unit, basic archive layer storage unit, and product service layer storage unit. Figure 4 This is a structural diagram of a storage node in an embodiment of the present invention. In one embodiment, the storage node is specifically used for:

[0053] If no merchant profile data operation instruction is received within the preset time period, the merchant profile file and merchant profile data in the operation management layer storage unit will be cleared.

[0054] In one embodiment, the application for a user node is specifically used for:

[0055] If the review result in the review message is "approved", delete the digest stored on the user node of this application; send a transfer instruction to the storage node;

[0056] When the review result in the review message is "not approved", the system receives the updated merchant profile data from the user, sends an update instruction to the storage node, and the update instruction carries the updated merchant profile data; the system also updates a summary of the merchant profile data on the user node in this application.

[0057] In one embodiment, the user audit node is specifically used for:

[0058] Intelligent recognition of text in merchant profile files to obtain data corresponding to each field of the merchant profile data;

[0059] If the data extracted based on field comparison is completely consistent with the above-mentioned archive data, the review result is determined to be passed; otherwise, the review result is determined to be failed.

[0060] Broadcast an audit message to other nodes, the audit message including fields for when the audit fails.

[0061] The following is a specific example illustrating the process of entering a single merchant profile data entry. (See attached image.) Figure 5 .

[0062] Implementation 1

[0063] Assume there are a total of user nodes A (application), B (approval), and C (storage).

[0064] After user node A writes the merchant profile data, user node B performs the approval process. The merchant profile file is a scanned electronic version of the merchant's basic information and approval materials. User node B intelligently recognizes the text in the merchant profile file to obtain the data corresponding to each field of the merchant profile data. This can be achieved using artificial intelligence image processing and text extraction technology. The fields included are: merchant name, merchant's English name, merchant's contract date, merchant's English abbreviation, merchant address, merchant's English address, mailing address, merchant contact person, merchant contact person's email address, merchant registration number, actual controller's name, actual controller's identification number, and merchant's security deposit, etc.

[0065] If the comparison is completely consistent, the audit result is determined to be passed; otherwise, the audit result is determined to be failed. The audit message is broadcast to other nodes, and the audit message includes the fields for when it fails.

[0066] When the review result in the review message is "approved", the user node deletes the summary stored in the application node; sends a transfer instruction to the storage node; when the review result in the review message is "disapproved", the user node receives the updated merchant profile data, sends an update instruction to the storage node, the update instruction carrying the updated merchant profile data; and updates the summary of the merchant profile data in the application node.

[0067] In one embodiment, the plurality of nodes further includes a retrieval node 104;

[0068] The storage node is also used to: after transferring the product service data of the merchant profile data in the operation management layer storage unit to the product service layer storage unit, send the file number and address of the merchant profile data to the retrieval node;

[0069] The retrieval node is used to: receive query instructions from the acquiring system, query the storage address of merchant profile data in the storage node according to the keywords in the query instructions, and send a retrieval instruction carrying the storage address to the storage node;

[0070] The storage node is also used to: after receiving a retrieval instruction carrying a storage address, query the merchant profile data corresponding to the keywords in the retrieval instruction from the database corresponding to the storage address, and feed it back to the acquiring system.

[0071] Figure 6 This is a structural diagram of a retrieval node in an embodiment of the present invention. The operation management layer storage unit of the retrieval node is reserved.

[0072] Below are two examples of reading merchant profile data based on retrieval nodes.

[0073] Example 2 - Online Deduction Processing Flow

[0074] Figure 7 This is a flowchart of the online deduction process in an embodiment of the present invention. Both online transactions and batch processing require calling merchant clearing account data from basic file data and product service data. Basic file data is used for checking file status, and merchant clearing account data is used for merchant clearing and accounting processing.

[0075] The online payment processing flow starts with a query request initiated by the acquiring system. The retrieval node receives the query instruction and determines the storage address of the file (which can be represented by a pointer) based on the file number as a keyword. Since the retrieval node only stores the file number and storage address, the data is simple and consumes less memory. The memory consumption of traversal is low, thus improving retrieval efficiency.

[0076] The retrieval node sends a retrieval instruction carrying the storage address to the storage node. The storage node returns the actual merchant profile data, including basic profile data and merchant clearing account data. The merchant clearing account data specifically includes the merchant acquiring product business processing switch and fee rate data, which are directly returned to the acquiring system for deducting from the customer's account.

[0077] Example 3 - End-of-Day Batch Merchant Invoicing Process

[0078] The end-of-day bulk merchant payment processing flow is the same as the online deduction processing flow. The end-of-day bulk merchant payment processing is initiated by the acquiring system. The retrieval node receives the query instruction and sends the retrieval instruction with the storage address to the storage node. The storage node returns the actual merchant profile data, including basic profile data, merchant clearing account, and currency, and directly returns it to the acquiring system for bulk payment.

[0079] In addition to single-entry file creation, the system proposed in this embodiment also supports batch file creation. Currently, the platform's distributed system processes the following logic: create a new merchant file -> approval -> generate a 12-digit merchant number -> create a new department file -> approval -> generate a 15-digit department number. Only after obtaining both the merchant and department numbers can product agreements and terminal files be created. However, in business operations, a large amount of archival information requires manual entry by business personnel. Supporting batch entry and batch approval of files is urgently needed, but the current technical bottleneck is that when batch entering merchants, departments, and corresponding product agreements and terminal files, the corresponding merchant and department numbers are not yet generated, preventing batch entry from being achieved.

[0080] The solution proposed in this invention involves user nodes uploading data such as merchants, departments, terminals, and product agreements in batches. The user nodes push the data in batches to user nodes with approval authority through the management operation layer. The approval user nodes first perform intelligent approval on the merchant files. Referring to the single file approval scheme, the department files, terminal files, and product agreements are temporarily stored in the management operation layer and not processed yet. After the merchant file approval node completes the approval, the approval user node automatically initiates the approval request for the department files. After the department approval node completes the approval, the approval requests for the terminal files and product agreements are initiated in sequence.

[0081] In one embodiment, the requesting user node is further used for:

[0082] The system receives merchant profile files uploaded in batches by users and merchant profile data entered in batches. The basic profile data includes, but is not limited to, merchant attribute profile data, department profile data, and terminal profile data. The product service data includes product agreement data. The system also broadcasts summary messages to other nodes.

[0083] The user approval node is also used for:

[0084] After receiving the summary message via the network, the merchant profile data and merchant profile file of the storage node are read via the network, the merchant attribute profile data is approved, and the first approval result is obtained.

[0085] If the first approval result is "passed", the department's file data will be approved to obtain the second approval result;

[0086] If the second approval result is passed, the terminal file data is approved to obtain the third approval result;

[0087] If the third approval result is passed, the product agreement data will be approved.

[0088] As for the relationship between merchant files, department files, terminal files and product agreements, it will be intelligently linked and verified by artificial intelligence through approval user nodes.

[0089] In one embodiment, the requesting user node is further used for:

[0090] When batch-entering merchant profile data, the merchant attribute profile data and department profile data are labeled by merchant name and department name;

[0091] The approval user node is also used to: automatically assign a value to the merchant file number field in the department file data based on the annotations in the merchant attribute file data and the department file data when the first approval result is passed;

[0092] Verify the merchant names in the merchant attribute profile data and the department names in the department profile data. After verification, approve the department profile data.

[0093] Terminal files and product agreements are handled in the same way.

[0094] In summary, in the system proposed in this embodiment of the invention, the application user node is used to receive merchant profile files and entered merchant profile data uploaded by users, send them to the storage node via the network, store a summary of the merchant profile data at the application user node, and broadcast the summary message to other nodes; the approval user node is used to, after receiving the summary message via the network, read the merchant profile data and merchant profile files from the storage node via the network, review them, and broadcast the review message to other nodes; the application user node is also used to: after receiving the review message via the network and confirming that the summary in the review message is consistent with the summary stored at the application user node, operate the summary stored at the application user node according to the review result in the review message, and send a merchant profile data operation instruction to the storage node, wherein the operation instruction is an update instruction or a transfer instruction; the storage node is used to store the merchant profile data received via the network; and execute the received merchant profile data operation instruction. Compared with the prior art, which requires manual file approval, in this embodiment of the invention, all nodes adopt a decentralized network structure, making the entry, approval, and storage of merchant profile data secure and efficient, and realizing the automatic import, approval, and efficient storage of merchant profile data.

[0095] This invention also provides a merchant profile data management method, applied to the application user node in a merchant profile data management system, as described in the following embodiments. Since the principle by which this device solves the problem is similar to that of the merchant profile data management system, the implementation of this method can refer to the implementation of the merchant profile data management system; repeated details will not be elaborated further.

[0096] Figure 8 The flowchart of the merchant profile data management method in this embodiment of the invention includes:

[0097] Step 801: Receive the merchant profile file uploaded by the user and the entered merchant profile data;

[0098] Step 802: Send to the storage node via the network;

[0099] Step 803: Store a summary of the merchant profile data on the user node in this application and broadcast the summary message to other nodes;

[0100] Step 804: After receiving the audit message via the network and confirming that the summary in the audit message is consistent with the summary stored by the user node of this application, the user node of this application operates on the summary according to the audit result in the audit message and sends a merchant file data operation instruction to the storage node. The operation instruction is an update instruction or a transfer instruction; wherein, the storage node executes the received merchant file data operation instruction.

[0101] The review message is broadcast by the approving user node after receiving the summary message through the network, reading the merchant profile data and merchant profile file from the storage node through the network, reviewing it, and then broadcasting it.

[0102] This invention also provides another merchant profile data management method, applied to the approval user node in a merchant profile data management system, as described in the following embodiments. Since the principle by which this device solves the problem is similar to that of the merchant profile data management system, the implementation of this method can refer to the implementation of the merchant profile data management system; repeated details will not be elaborated further.

[0103] Figure 9 The flowchart of the merchant profile data management method in this embodiment of the invention includes:

[0104] Step 901: After receiving the summary message via the network, read the merchant profile data and merchant profile file of the storage node via the network. The summary message is broadcast by the requesting user node after receiving the merchant profile file uploaded by the user and the merchant profile data entered by the user, and after storing the summary of the merchant profile data in the requesting user node.

[0105] Step 902: Review the merchant profile data and merchant profile files read from the network storage node;

[0106] Step 903: Broadcast the audit message to other nodes;

[0107] When the applicant user node receives the review message via the network and confirms that the summary in the review message is consistent with the summary stored by the applicant user node, it operates on the summary stored by the applicant user node according to the review result in the review message and sends a merchant profile data operation instruction to the storage node for the storage node to execute. The operation instruction is an update instruction or a transfer instruction.

[0108] In summary, compared with the existing technical solutions that require manual document approval, the method proposed in this embodiment of the invention adopts a decentralized network structure for all nodes, which makes the input, approval and storage of merchant document data secure and efficient, and realizes the automatic import, approval and efficient storage of merchant document data.

[0109] This invention also provides a computer device. Figure 10 This is a schematic diagram of a computer device in an embodiment of the present invention. The computer device 1000 includes a memory 1010, a processor 1020, and a computer program 1030 stored in the memory 1010 and executable on the processor 1020. When the processor 1020 executes the computer program 1030, it implements the above-mentioned merchant file data management method.

[0110] This invention also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned merchant profile data management method.

[0111] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can 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, etc.) containing computer-usable program code.

[0112] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0113] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0114] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0115] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above descriptions are merely specific embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A merchant profile data management system, characterized in that, include: Multiple nodes on a decentralized network structure, the multiple nodes including at least one applicant user node, at least one approval user node, and a storage node; The user node is used to receive merchant profile files and entered merchant profile data uploaded by users, send them to the storage node via the network, store a summary of the merchant profile data on the user node, and broadcast the summary message to other nodes. The approval user node is used to read the merchant profile data and merchant profile file from the storage node through the network after receiving the summary message through the network, and to review and broadcast the review message to other nodes. The application user node is also used to: after receiving an audit message through the network and confirming that the summary in the audit message is consistent with the summary stored by the application user node, operate the summary stored by the application user node according to the audit result in the audit message, and send a merchant profile data operation instruction to the storage node, wherein the operation instruction is an update instruction or a transfer instruction; A storage node is used to store merchant profile data received via the network and to execute operation instructions on the received merchant profile data; wherein, the storage node is deployed using a distributed database. The node includes an operation management layer storage unit, a basic file layer storage unit, and a product service layer storage unit. The operation management layer storage unit is used to record unapproved merchant profile data; The basic file layer storage unit is used to record the basic file data in the effective merchant file data; The product service layer storage unit is used to record product service data in the effective merchant profile data; The application for a user node is specifically used to: store a summary of merchant profile data in the operation management layer storage unit; Specifically, the storage node is used to: store merchant profile files and merchant profile data received over the network into the operation management layer storage unit; update the merchant profile data in the operation management layer storage unit when receiving an update instruction; transfer the basic profile data of the merchant profile data in the operation management layer storage unit to the basic profile layer storage unit, transfer the product and service data of the merchant profile data in the operation management layer storage unit to the product and service layer storage unit, and clear the merchant profile files in the operation management layer storage unit when receiving a transfer instruction.

2. The system as described in claim 1, characterized in that, Storage nodes are specifically used for: If no merchant profile data operation instruction is received within the preset time period, the merchant profile file and merchant profile data in the operation management layer storage unit will be cleared.

3. The system as described in claim 1, characterized in that, The application for a user node is specifically used for: If the review result in the review message is "approved", delete the digest stored on the user node of this application; send a transfer instruction to the storage node; When the review result in the review message is "not approved", the system receives the updated merchant profile data from the user and sends an update instruction to the storage node, the update instruction carrying the updated merchant profile data. This application updates a summary of the merchant profile data on the user node.

4. The system as described in claim 3, characterized in that, The user node is specifically used for: Intelligent recognition of text in merchant profile files to obtain data corresponding to each field of the merchant profile data; If the data extracted based on field comparison is completely consistent with the above-mentioned archive data, the review result is determined to be passed; otherwise, the review result is determined to be failed. Broadcast an audit message to other nodes, the audit message including fields for when the audit fails.

5. The system as described in claim 1, characterized in that, The plurality of nodes also includes a retrieval node; The storage node is also used to: after transferring the product service data of the merchant profile data in the operation management layer storage unit to the product service layer storage unit, send the file number and address of the merchant profile data to the retrieval node; The retrieval node is used to: receive query instructions from the acquiring system, query the storage address of merchant profile data in the storage node according to the keywords in the query instructions, and send a retrieval instruction carrying the storage address to the storage node; The storage node is also used to: after receiving a retrieval instruction carrying a storage address, query the merchant profile data corresponding to the keywords in the retrieval instruction from the database corresponding to the storage address, and feed it back to the acquiring system.

6. The system as described in claim 1, characterized in that, Applying for a user node is also used for: The system receives merchant profile files uploaded in batches by users and merchant profile data entered in batches. The basic profile data includes, but is not limited to, merchant attribute profile data, department profile data, and terminal profile data. The product service data includes product agreement data. The system also broadcasts summary messages to other nodes. The user approval node is also used for: After receiving the summary message via the network, the merchant profile data and merchant profile file of the storage node are read via the network, the merchant attribute profile data is approved, and the first approval result is obtained. If the first approval result is "passed", the department's file data will be approved to obtain the second approval result; If the second approval result is passed, the terminal file data is approved to obtain the third approval result; If the third approval result is passed, the product agreement data will be approved.

7. The system as described in claim 1, characterized in that, Applying for a user node is also used for: When batch-entering merchant profile data, the merchant attribute profile data and department profile data are labeled by merchant name and department name; The approval user node is also used to: automatically assign a value to the merchant file number field in the department file data based on the annotations in the merchant attribute file data and the department file data when the first approval result is passed; Verify the merchant names in the merchant attribute profile data and the department names in the department profile data. After verification, approve the department profile data.

8. A method for managing merchant profile data, characterized in that, The application user node applied in the merchant profile data management system according to any one of claims 1-7 includes: Receive merchant profile files uploaded by users and enter merchant profile data; Send to the storage node via the network; In this application, the user node stores a summary of the merchant profile data and broadcasts the summary message to other nodes. After receiving the audit message via the network and confirming that the summary in the audit message is consistent with the summary stored by the user node of this application, the user node operates on the summary stored by this application according to the audit result in the audit message, and sends a merchant profile data operation instruction to the storage node. The operation instruction is an update instruction or a transfer instruction; wherein, the storage node executes the received merchant profile data operation instruction. The review message is broadcast by the approving user node after receiving the summary message through the network, reading the merchant profile data and merchant profile file from the storage node through the network, reviewing it, and then broadcasting it.

9. A method for managing merchant profile data, characterized in that, An approval user node applied in the merchant profile data management system according to any one of claims 1-7 includes: After receiving the summary message over the network, the merchant profile data and merchant profile files of the storage node are read over the network. The summary message is broadcast by the requesting user node after receiving the merchant profile files uploaded by the user and the merchant profile data entered by the user, and after storing the summary of the merchant profile data on the requesting user node. Verify the merchant profile data and merchant profile files read from the network storage nodes; Broadcast the audit message to other nodes; When the applicant user node receives the review message via the network and confirms that the summary in the review message is consistent with the summary stored by the applicant user node, it operates on the summary stored by the applicant user node according to the review result in the review message and sends a merchant profile data operation instruction to the storage node for the storage node to execute. The operation instruction is an update instruction or a transfer instruction.

10. A computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method of claim 8 or 9.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the method of claim 8 or 9.

Images