CN115760338A

CN115760338A - File message processing method and device of bank-enterprise docking system and storage medium

Info

Publication number: CN115760338A
Application number: CN202211485927.XA
Authority: CN
Inventors: 王铖
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-11-24
Filing date: 2022-11-24
Publication date: 2023-03-07

Abstract

The document provides a method, a device and a storage medium for processing file messages of a bank-enterprise docking system, wherein the method comprises the following steps: acquiring a text file sent by an enterprise; verifying the text file according to the file signature and the file format, and storing the basic information of the text file into a file basic information table after the verification is successful; all the text files corresponding to the file basic information table are obtained, and according to the file content obtained by verifying the text files, all the text files are converted into different types of file messages and then sent to the message processing platform, so that the file messages can be processed.

Description

File message processing method and device of bank-enterprise docking system and storage medium

Technical Field

The invention relates to the technical field of network security, in particular to a file message processing method, a file message processing device and a storage medium for a bank-enterprise docking system.

Background

With the development of science and technology, more and more enterprises switch the interaction channel with the bank from the traditional online bank to the bank-enterprise direct connection in order to reduce financial cost and improve efficiency.

The bank-enterprise direct connection has an online message request response mode (http) and a file message interaction mode, in brief, a client system generates a text file, uploads the text file to a preprocessing module, the preprocessing module converts the text file into a file message which can be identified by a bank, and the file message is processed through a processing platform.

However, in the generation of the text file, due to user habits or external influences, the writing of the file message does not conform to relevant regulations of the bank, the text file cannot be normally converted into the file message, or after the text file is converted into the file message, the processing platform cannot normally read relevant information in the file message, and cannot normally process the file message.

Disclosure of Invention

In view of the above problems in the prior art, an object of the present disclosure is to provide a method, an apparatus, and a storage medium for processing a document message in a bank-enterprise docking system, so as to solve the problem in the prior art that a bank does not verify a document message written by an enterprise, and even if the writing of the document message corresponding to the enterprise does not meet relevant regulations of the bank, the processing is performed, which results in poor bank processing efficiency.

In order to solve the technical problems, the specific technical scheme is as follows:

in one aspect, this document provides a method for processing a file packet of a bank-enterprise docking system, including:

acquiring a text file sent by an enterprise;

verifying the text file according to the file signature and the file format, and storing the basic information of the text file into a file basic information table after the verification is successful;

and acquiring all text files corresponding to the file basic information table, converting all the text files into different types of file messages according to the file content obtained by verifying the text files, and then sending the different types of file messages to a message processing platform.

As an embodiment herein, the file content includes a remittance account number and a unified credit card number of a sender, a receiving account number and a unified credit card number of a receiver, and transfer type information;

the converting all the text files into different types of file messages and sending the different types of file messages to a message processing platform according to the file contents obtained by verifying the text files further comprises the following steps:

determining the remitter as a public account number or a private account number according to the remittance account number and the unified credit card number of the remitter;

determining the payee as a public account or a private account according to the payee account and the unified credit card number of the payee;

when the sender is a public account number and the receiver is a public account number, determining that the file message is a public-to-public file message and sending the public-to-public file message to a first module of the processing platform for processing;

when the sender is a public account number and the receiver is a private account number, determining that the file message is a public-private file message and sending the public-private file message to a second module of the processing platform for processing;

when the remitter is a private account number and the payee is a public account number, determining that the file message is a private-to-public file message and sending the file message to a third module of the processing platform for processing;

and when the remitter is a private account number and the payee is a private account number, determining that the file message is a private file message and sending the file message to a fourth module of the processing platform for processing.

As an embodiment herein, said verifying said text file according to a file signature and a file format further comprises:

determining the field length of the unified credit card number in the text file according to the file format;

when the length of the field of the unified credit card number is the same as the length of the preset unified credit card number in the file format, splitting the text file to obtain a target key identifier, a target check value and target ciphertext data;

inquiring a target key matched with the target key identification from a key bank;

decrypting the target ciphertext data by using the target key to obtain plaintext data;

calculating a check value of the plaintext data according to a set rule;

and when the check value of the plaintext data is consistent with the target check value, displaying the plaintext data of the text file, wherein the plaintext data comprises the file content.

As an embodiment herein, the calculating a check value of the plaintext data according to a set rule further includes:

respectively determining account number types of the sender and account number types of the receiver according to the unified credit card number of the sender and the unified credit card number of the receiver, wherein each account number type corresponds to an account number code;

and calculating the check value of the plaintext data according to the account number code.

As an embodiment herein, the acquiring all the text files corresponding to the file basic information table further includes:

periodically inquiring the file basic information table at polling time;

and acquiring a text file corresponding to the basic information stored in the file basic information table.

As an embodiment herein, after saving the basic information of the text file into the file basic information table, the method includes:

and returning the messages to be processed to the enterprise.

As one embodiment herein, after said verifying said text file according to file signature and file format, comprising:

and when the verification fails, returning a rejection message to the enterprise.

As an embodiment herein, after converting all the text files into different types of file messages and sending the file messages to a message processing platform, the method includes:

and deleting the basic information corresponding to the converted text file in the file basic information table.

On the other hand, this document also provides a file message processing device of the bank-enterprise docking system, which includes:

the acquisition unit is used for acquiring a text file sent by an enterprise;

the verification unit is used for verifying the text file according to the file signature and the file format, and storing the basic information of the text file into a file basic information table after the verification is successful;

and the conversion unit is used for acquiring all the text files corresponding to the file basic information table, converting all the text files into file messages of different types and then sending the file messages to the message processing platform, wherein the file messages are used for indicating the processing platform to perform service processing.

In another aspect, a computer device is further provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the file message processing method of the bank enterprise docking system when executing the computer program.

In another aspect, a computer-readable storage medium is provided, where a computer program is stored, and when executed by a processor, the computer program implements the file message processing method of the bank-enterprise docking system.

In another aspect, a computer program product is provided, where the computer program product includes a computer program, and when executed by a processor, the computer program implements the file message processing method of the bank-enterprise docking system.

By adopting the technical scheme, the text file sent by an enterprise can be directly obtained through a platform corresponding to the enterprise; the text file is verified according to the file signature and the file format, after the verification is successful, the basic information of the text file is stored in a file basic information table, the text file can be verified, the text file which does not meet the bank requirement is removed, and the text file which meets the bank requirement is sent to a processing platform; all the text files corresponding to the file basic information table are obtained, and according to the file content obtained by verifying the text files, all the text files are converted into different types of file messages and then sent to the message processing platform, so that the file messages can be processed.

In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is an overall system diagram illustrating a file message processing method of a bank-enterprise docking system according to an embodiment of the present disclosure;

fig. 2 is a schematic diagram illustrating steps of a file message processing method of a bank-enterprise docking system according to an embodiment of the present disclosure;

FIG. 3 shows a text document validation schematic of embodiments herein;

FIG. 4 is a schematic diagram illustrating a file message processing apparatus of a bank-enterprise docking system according to an embodiment of the present disclosure;

fig. 5 shows a schematic diagram of a computer device according to an embodiment of the present disclosure.

Description of the figures the symbols:

101. an enterprise side;

102. a bank end;

103. a message processing platform;

401. an acquisition unit;

402. a verification unit;

403. a conversion unit;

502. a computer device;

504. a processor;

506. a memory;

508. a drive mechanism;

510. an input/output module;

512. an input device;

514. an output device;

516. a presentation device;

518. a graphical user interface;

520. a network interface;

522. a communication link;

524. a communication bus.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.

It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

Fig. 1 shows an overall system diagram of a file message processing method of a bank-enterprise docking system, which includes an enterprise terminal 101, a bank terminal, and a message processing platform.

And the enterprise terminal 101 is used for receiving the requirements of the user, including delayed account transfer, instant account transfer, deposit or withdrawal and the like, generating a text file after analyzing the requirements and sending the text file to the bank terminal. For example, in a transfer scenario, the user fills out a remittance account number and a uniform credit card number of a sender, a remittance account number and a uniform credit card number of a receiver, and transfer type information at the enterprise side, wherein the transfer type information includes a public-to-public account, a private-to-private transfer, a public-to-private transfer, and a private-to-public transfer.

The bank end 102 is configured to receive the text file, temporarily store the text file after the text file arrives, convert the text file into a file message after a time threshold is met, where the bank end may parse the text file to obtain plaintext data in the file message, and then send the file message to different interfaces in the message processing platform according to related information in the plaintext data. In this context, a message processing platform has several processing modules, each of which is responsible for the processing of one type of document message.

And the message processing platform 103 is used for performing data processing according to the plaintext data in the file message.

Because, in the prior art, the transfer type information needs to be filled by the user, when the user is wrongly filled, the file message is distributed to different processing modules by the bank end, and the processing modules cannot normally process the file message, for example, the bank calculates the exchange rate or the commission charge incorrectly, so that the text file needs to be verified and the correct file message is generated.

In order to solve the above problem, embodiments herein provide a method for processing a file packet in a bank-enterprise docking system, which can ensure that a correct file packet is sent to a processing platform, and improve the efficiency of a bank responding to a client. Fig. 2 is a schematic step diagram of a file message processing method of a bank-enterprise docking system provided in an embodiment of the present disclosure, and this specification provides operation steps of the method as described in the embodiment or the flowchart, but may include more or less operation steps based on conventional or non-creative labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures. Specifically, as shown in fig. 2, the method may include:

step 201, acquiring a text file sent by an enterprise.

Step 202, verifying the text file according to the file signature and the file format, and storing the basic information of the text file into a file basic information table after the verification is successful.

Step 203, obtaining all the text files corresponding to the file basic information table, converting all the text files into different types of file messages according to the file content obtained by verifying the text files, and then sending the different types of file messages to a message processing platform.

By adopting the technical scheme, the text file sent by an enterprise can be directly obtained through a platform corresponding to the enterprise; the text file is verified according to the file signature and the file format, and after verification is successful, the basic information of the text file is stored in a file basic information table, so that the text file can be verified, the text file which does not meet bank requirements is removed, and the text file which meets bank requirements is sent to a processing platform; all the text files corresponding to the file basic information table are obtained, and according to the file content obtained by verifying the text files, all the text files are converted into different types of file messages and then sent to the message processing platform, so that the file messages can be processed.

Herein, the text file may be acquired through the FTP server, and herein, the format of the text file may be a TXT format.

The format of the document message may be an XML format herein.

As an embodiment of this document, step 202, the text file is verified according to the file signature and the file format, and when the verification is successful, the basic information of the text file is saved in a file basic information table.

In this step, the basic information of the text file may be a serial number or a label, the file basic information table records the basic information of the text file in a mapping manner, that is, the file basic information table only stores the serial number, while the real text file is stored in the virtual cache, and when the time threshold is met, the virtual cache and the file basic information table are emptied in a unified manner.

And if the verification is successful, returning the message to be processed to the enterprise.

And if the verification fails, returning a rejection message to the enterprise.

And after the text file is successfully verified, the text file is proved to meet the bank requirement and can be processed.

The text file verification diagram shown in fig. 3 includes:

step 301, determining the field length of the unified credit card number in the text file according to the file format.

In this step, the text file is composed of a plurality of segments and encrypted using the ciphertext, e.g., first segment-second segment-third segment-fourth segment-fifth segment. The contents of the document herein include at least a remittance account number and a unified credit card number of a sender, a collection account number and a unified credit card number of a receiver, and transfer type information.

The encryption method used in the text can ensure that the digits of each segment of data before and after encryption are consistent, and the first segment, the second segment, the third segment, the fourth segment and the fifth segment can be unified credit card numbers in the text file due to business adjustment. The specific corresponding relationship may be determined according to an instruction of a file format, for example, in a text file, if a plaintext is used to specify that the second segment and the third segment are the unified credit card number, the bank may identify the second segment and the third segment, if the text file is not described, the bank may identify the unified credit card number by using a default specification, for example, if the first segment and the second segment are the unified credit card number by default, the bank may identify the first segment and the second segment.

Because the field lengths of the unified credit card numbers have uniformity, when a bank identifies the field length of the unified credit card numbers in a ciphertext state, if the field length of the unified credit card numbers in the ciphertext state obtained by identification is different from the preset length of the unified credit card numbers, the form of a text file sent by an enterprise is wrong, and the bank cannot identify the text file.

And step 302, when the length of the field of the unified credit card number is the same as the length of the preset unified credit card number in the file format, splitting the text file to obtain a target key identifier, a target check value and target ciphertext data.

In this context, if the lengths are the same, it is proved that the data integrity of the text file meets the requirements of the message processing platform.

When the data integrity of the text file meets the requirements of the message processing platform, whether the text file is tampered and whether the processing type of the text file is correctly filled are required to be verified, so that the text needs to be decrypted by using the target key identifier, the target check value and the target ciphertext data to obtain final plaintext data.

Step 303, querying a target key matched with the target key identification from a key store.

In this step, the key bank includes a plurality of keys, and in order to ensure security, the encryption mode of each text file may not be used, i.e., different public keys are used for encryption, and when the text file is encrypted by using the public key, a key identifier is automatically generated, so that the bank uses the key identifier to obtain a private key (key) corresponding to the public key, and decryption of the target ciphertext data is completed.

And 304, decrypting the target ciphertext data by using the target key to obtain plaintext data.

In this step, the text file may be encrypted using the asymmetrically encrypted public key, and then the bank decrypts the text file using the private key (secret key).

And 305, calculating the check value of the plaintext data according to a set rule.

In this step, the transfer scenario may be used for illustration: and the bank respectively determines the account number type of the sender and the account number type of the receiver according to the unified credit card number of the sender and the unified credit card number of the receiver, wherein each account number type corresponds to an account number code. The public account may be 01 and the private account may be 10 herein.

And calculating the check value of the plaintext data according to the account number code. Specifically, account codes of both remittance and remittance parties can be spliced, and when a public account transfers money to a private account, the spliced account code can be 0110; when the public account transfers to the public account, the spliced account code may be 0101, when the private account transfers to the public account, the spliced account code may be 1001, and when the private account transfers to the private account, the spliced account code may be 1010.

Step 306, when the check value of the plaintext data is consistent with the target check value, displaying the plaintext data of the text file, wherein the plaintext data includes the file content.

In this step, the target verification value may be filled by the user, and when the user uses the enterprise terminal to fill the current transfer as a public-to-public transfer, the enterprise terminal automatically generates the target verification value 0101. When the bank obtains that both the remittance and the collection have an account which is not a public account through unifying the credit card numbers, the calculated check value of the plaintext data can be not 0101, and the user is proved to fill in an error at the moment, so that the file message corresponding to the text file cannot be sent to the message processing platform.

And if the verification value of the plaintext data obtained through verification is consistent with the target verification value, storing the basic information of the text file into a file basic information table, and after the storage is finished, returning a message to be processed to the enterprise which finishes the verification and stores the basic information of the text file into the file basic information table in order to enable an enterprise user to know the current transmission progress of the text file. Similarly, a denial message may also be returned to the enterprise upon a failure to verify.

As an embodiment herein, the step 203 converts all the text files into different types of file messages according to the file content obtained by verifying the text file, and then sends the different types of file messages to the message processing platform, and further includes:

periodically inquiring the file basic information table at polling time;

when the sender is a public account number and the receiver is a public account number, determining that the file message is a public-to-public file message and sending the file message to a first module of the processing platform for processing;

In this step, since different services need different processing logics in the processing platform, for example, a public-private need needs to have a specific administrator to intervene to prevent fund outflow, and similarly, a private-private need to have a specific supervisor to intervene to prevent bribery and the like, it is necessary to verify and ensure that different types of file packets can be accurately sent to corresponding modules without errors.

Similarly, after the processing of the document message is completed, a completed indication may be sent to the enterprise. In this document, in order to ensure that the cache of the basic information table of the file is normal, the basic information corresponding to the converted text file may be deleted in the basic information table of the file.

As shown in fig. 4, a file message processing apparatus of a bank-enterprise docking system includes:

an obtaining unit 401, configured to obtain a text file sent by an enterprise;

a verification unit 402, configured to verify the text file according to a file signature and a file format, and store the basic information of the text file in a file basic information table after the verification is successful;

a converting unit 403, configured to obtain all text files corresponding to the file basic information table, convert all text files into file messages of different types, and send the file messages to a message processing platform, where the file messages are used to instruct the processing platform to perform service processing.

By adopting the technical scheme, the text file can be directly acquired through the platform corresponding to the enterprise through the acquisition unit; the verification unit can verify the text file, remove the text file which does not meet the bank requirement and send the text file which meets the bank requirement to the processing platform; the conversion unit can process the file message, and compared with the prior art, the text message processing method has the advantages that the identification of the text file is increased, the processing success rate of the processing platform is guaranteed, and the processing efficiency is improved.

As shown in fig. 5, for a computer device provided in the embodiments herein to execute the file message processing method described herein, the computer device 502 may include one or more processors 504, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 502 may also include any memory 506 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 506 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 502. In one case, when the processor 504 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 502 can perform any of the operations of the associated instructions. The computer device 502 also includes one or more drive mechanisms 508, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.

Computer device 502 may also include an input/output module 510 (I/O) for receiving various inputs (via input device 512) and for providing various outputs (via output device 514). One particular output mechanism may include a presentation device 516 and an associated Graphical User Interface (GUI) 518. In other embodiments, input/output module 510 (I/O), input device 512, and output device 514 may not be included, but merely as a computer device in a network. Computer device 502 can also include one or more network interfaces 520 for exchanging data with other devices via one or more communication links 522. One or more communication buses 524 couple the above-described components together.

Communication link 522 may be implemented in any manner, such as over a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 522 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

Corresponding to the methods in fig. 2 and 3, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, performs the steps of the above-described method.

Embodiments herein also provide computer readable instructions, wherein the program therein causes a processor to perform the method as shown in fig. 2 and 3 when the instructions are executed by the processor.

It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.

It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.

In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes 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 steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, 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.

The principles and embodiments of the present disclosure are explained in detail by using specific embodiments, and the above description of the embodiments is only used to help understanding the method and its core idea; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.

Claims

1. A file message processing method of a bank-enterprise docking system is characterized by comprising the following steps:

acquiring a text file sent by an enterprise;

2. The method for processing document messages of a bank-enterprise docking system according to claim 1,

the file content comprises a remittance account number and a unified credit card number of a sender, a receiving account number and a unified credit card number of a receiver and transfer type information;

3. The method of claim 2, wherein the verifying the text file according to the file signature and the file format further comprises:

calculating a check value of the plaintext data according to a set rule;

4. The method for processing document and message of bank-enterprise docking system according to claim 3, wherein the calculating the check value of the plaintext data according to the set rule further comprises:

and calculating a check value of the plaintext data according to the account number code.

5. The method for processing the file message of the bank-enterprise docking system according to claim 1, wherein the obtaining of all the text files corresponding to the file basic information table further comprises:

periodically inquiring the file basic information table at polling time;

6. The method for processing the file message of the bank-enterprise docking system according to claim 1, after the basic information of the text file is saved in a file basic information table, comprising:

and returning the messages to be processed to the enterprise.

7. The method for processing document messages in a bank-enterprise docking system according to claim 1, wherein after verifying the text document according to the document signature and the document format, the method comprises:

8. The file message processing method of the bank-enterprise docking system according to claim 1, wherein after converting all the text files into different types of file messages and sending the different types of file messages to a message processing platform, the method comprises the following steps:

9. A file message processing device of a bank-enterprise docking system is characterized by comprising:

the acquisition unit is used for acquiring a text file sent by an enterprise;

10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the file message processing method of the bank-enterprise docking system according to any one of claims 1 to 8 when executing the computer program.

11. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the file message processing method of a bank-enterprise docking system according to any one of claims 1 to 8.

12. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, carries out the method of file message handling of a bank-enterprise docking system according to any one of claims 1-8.