Financial data synchronization method, device and storage medium

Abstract

The present invention relates to the field of data synchronization, and discloses a method, device, and storage medium for synchronizing financial data. The method comprises: an internal control system sends a data synchronization request to a verification system according to the TLS two-way transmission protocol; the verification system receives the synchronization request, verifies the sending platform certificate, and obtains a verification result; according to a preset mapping blockchain, queries and maps the internal control system code to obtain the management system code; connects to the financial management system corresponding to the management system code, and sends the synchronization request to the financial management system; monitors the status code returned by the financial management system; when it is a preset update code, determines that the data corresponding to the synchronization request is in a synchronized state in the financial management system; when it is not a preset update code, resends the synchronization request to the financial management system according to a preset exponential backoff algorithm. In an embodiment of the present invention, encryption and multi-layer verification are utilized to achieve efficient and secure synchronization of financial data across multiple systems.

Description

Technical Field

[0001] The present invention relates to the field of data synchronization, and in particular to a method, device and storage medium for synchronizing financial data. Background Art

[0002] After the application of Internet technology in various production fields, various data platforms have been born. A large number of data platforms have generated heterogeneous data with different data structures. In order to solve the data transmission and interaction between different data platforms, a system specifically for heterogeneous data synchronization has been created.

[0003] Conventional data synchronization systems primarily focus on converting data structures between heterogeneous data, achieving significant success in scenarios such as video entertainment and social communications. However, in the financial system domain, data synchronization must not only consider heterogeneous data conversion but also the confidentiality issues inherent in financial scenarios. The financial internal control system is the source of financial data and is responsible for core operations such as payment, accounting, and collection. The financial management system is the platform for external operations, providing data display, reimbursement, and transaction printing. Data synchronization between the financial internal control system and the financial management system is not secure. Even if the financial internal control system operates on an independent network, regular synchronization of the financial internal control system data with the financial management system is required. However, the existing data synchronization process between the financial internal control system and external financial business management systems is subject to numerous vulnerabilities that can be exploited by external injection attacks. Therefore, to address the inadequate security of data synchronization in the financial system domain, a new technology is needed to address current technical issues. Summary of the Invention

[0004] The main purpose of the present invention is to solve the technical problem of insufficient security of data synchronization in the field of financial systems.

[0005] A first aspect of the present invention provides a method for synchronizing financial data. The method is applied to a financial data synchronization system. The financial data synchronization system includes an internal control system and a verification system. The method includes:

[0006] The internal control system sends a data synchronization request to the verification system according to the preset TLS two-way transmission protocol, wherein the synchronization request includes: the internal control system code and the sending platform certificate;

[0007] The verification system receives the synchronization request according to the preset TLS two-way transmission protocol, verifies the sending platform certificate, and obtains a verification result;

[0008] When the verification result is qualified, the internal control system code is queried and mapped according to the preset mapping blockchain to obtain the management system code;

[0009] Connecting to the financial management system corresponding to the management system code, and sending the synchronization request to the financial management system;

[0010] Monitor the status code returned by the financial management system;

[0011] When the status code is a preset update code, determining that the data corresponding to the synchronization request is in a synchronized state in the financial management system;

[0012] When the status code is not a preset update code, the synchronization request is resent to the financial management system according to a preset exponential backoff algorithm.

[0013] Optionally, in a first implementation of the first aspect of the present invention, the step of sending the synchronization request to the financial management system includes:

[0014] Encrypting the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request;

[0015] According to the preset HTTPS protocol, the encrypted synchronization request is sent to the financial management system.

[0016] Optionally, in a second implementation of the first aspect of the present invention, the step of connecting to the financial management system corresponding to the management system code and sending the synchronization request to the financial management system includes:

[0017] Creating a container cluster in a pre-set cloud database, and creating a deployment container on the container cluster, wherein the container cluster is used to manage the deployment container;

[0018] Storing the synchronization request in the deployment container through the container cluster;

[0019] Sending the system address of the financial management system corresponding to the management system code to the container cluster, so that the container cluster connects to the financial management system based on the system address;

[0020] A transmission instruction is sent to the container cluster so that the container cluster transmits the storage data in the deployment container to the financial management system.

[0021] Optionally, in a third implementation of the first aspect of the present invention, the step of storing the synchronization request in the deployment container through the container cluster includes:

[0022] Encrypting the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request;

[0023] The encrypted synchronization request is stored in the deployment container through the container cluster.

[0024] Optionally, in a fourth implementation of the first aspect of the present invention, the deployment container includes: a first deployment sub-container and a second deployment sub-container, and the step of storing the encrypted synchronization request in the deployment container through the container cluster includes:

[0025] Splitting the encryption synchronization request through the container cluster to obtain a first encryption split request and a second encryption split request;

[0026] The first encryption split request is stored in the first deployment sub-container through the container cluster, and the second encryption split request is stored in the second deployment sub-container.

[0027] Optionally, in a fifth implementation of the first aspect of the present invention, the step of querying and mapping the internal control system code according to the preset mapping blockchain to obtain the management system code includes:

[0028] According to the preset parameter storage table, query the block parameters corresponding to the internal control system code;

[0029] The data corresponding to the block parameters is queried in the preset mapping blockchain to obtain the management system code.

[0030] The step of querying the data corresponding to the block parameters in the preset mapping blockchain to obtain the management system code includes:

[0031] Querying the data corresponding to the block parameters in the preset mapping blockchain to obtain the query results;

[0032] When the query result is empty, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period;

[0033] When the query result is not empty, the management system code is extracted from the query result.

[0034] Optionally, in a seventh implementation of the first aspect of the present invention, after the verification system receives the synchronization request according to the preset TLS two-way transmission protocol and verifies the sending platform certificate to obtain a verification result, the method further includes:

[0035] When the verification result is unqualified, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period.

[0036] A second aspect of the present invention provides a financial data synchronization device, comprising: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; the at least one processor calls the instructions in the memory so that the financial data synchronization device executes the above-mentioned financial data synchronization method.

[0037] A third aspect of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the above-mentioned method for synchronizing financial data.

[0038] In an embodiment of the present invention, by introducing a verification system to interact with the internal control system for data exchange, and the verification system to interact with an external financial management system, direct data transmission between the internal control system and the external financial management system is avoided. Furthermore, this solution utilizes the TLS bidirectional transmission protocol to ensure secure transmission between the verification system and the internal control system. Blockchain records are used to map the internal control system to a pre-designated financial management system, preventing the manual modification of important mapping rules that could cause synchronized data to leak to non-designated financial management systems. This allows for efficient and secure synchronization of financial data, resolving the technical issue of insufficient data synchronization security in the financial system field. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of an embodiment of a method for synchronizing financial data according to an embodiment of the present invention;

[0040] Figure 2 This is a schematic diagram of a specific embodiment of step 103 of the method for synchronizing financial data in an embodiment of the present invention;

[0041] Figure 3 This is a schematic diagram of a specific embodiment of step 104 of the method for synchronizing financial data in an embodiment of the present invention;

[0042] Figure 4 This is another specific embodiment diagram of step 104 of the method for synchronizing financial data in an embodiment of the present invention;

[0043] Figure 5 Schematic diagram of an embodiment of a financial data synchronization device in an embodiment of the present invention. DETAILED DESCRIPTION

[0044] Embodiments of the present invention provide a method, device, and storage medium for synchronizing financial data.

[0045] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.

[0046] In the description of the embodiments disclosed herein, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to." The term "based on" should be understood as "based, at least in part, on." The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment." The terms "first," "second," etc. may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0047] For ease of understanding, the specific process of the embodiment of the present invention is described below. Figure 1 In one embodiment of a method for synchronizing financial data according to an embodiment of the present invention, the method for synchronizing financial data is applied to a synchronization system for financial data. The synchronization system for financial data includes: an internal control system and a verification system. The method for synchronizing financial data includes:

[0048] 101. The internal control system sends a data synchronization request to the verification system according to the preset TLS two-way transmission protocol, wherein the synchronization request includes: an internal control system code and a sending platform certificate;

[0049] In this embodiment, the TLS two-way transmission protocol is a protocol mechanism for two-way authentication between the client and the server. When the internal control system needs to synchronize data, the TLS two-way transmission protocol is used to send a data synchronization request to the verification system. The verification system receives the data to be synchronized and exposes the interface to the outside world to prevent external injection from destroying the internal control system data.

[0050] 102. The verification system receives the synchronization request according to the preset TLS two-way transmission protocol, verifies the sending platform certificate, and obtains a verification result;

[0051] In this embodiment, the verification system receives the synchronization request through the TLS two-way transmission protocol, and then further verifies the platform certificate sent in the synchronization request. The obtained synchronization request is an authorized request for external synchronization. The synchronization request can also encapsulate the data table entity data that needs to be synchronized, and after the header file is confirmed to be qualified, it can avoid re-transmission for data synchronization.

[0052] The verification system and internal control system can be built based on the OAuth 2.0 framework. The verification system can assign client identity cards and client passwords to the internal control system and set fine-grained permission policies for the internal control system.

[0053] A standardized RESTful API interface can be configured on the interface between the verification system and the internal control system:

[0054] Financial data indicator synchronization interface: POST / api / v1 / fiscal / indicators (supports JSON / XML heterogeneous data parsing);

[0055] Payment data push interface: PUT / api / v1 / payment / orders (mandatory SM2 encryption + HTTPS transmission).

[0056] Furthermore, after step 102, the following specific implementations are also included:

[0057] 1021. When the verification result is unqualified, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period.

[0058] In step 1021, if the verification result fails, it means that the authorization does not comply with the regulations, an unauthorized alarm message is sent to the internal control system, and an address restriction is set for 5 minutes to prohibit the connection of the internal control system address.

[0059] 103. When the verification result is qualified, the internal control system code is queried and mapped according to the preset mapping blockchain to obtain the management system code;

[0060] In this embodiment, if the verification result is identified as qualified, an external mapping blockchain set to record the mapping code is accessed, and the corresponding mapping data recorded in the blockchain is queried based on the internal control system code in the synchronization request to obtain the management system code.

[0061] For further information, see Figure 2 , Figure 2 This is a specific embodiment of step 103 of the method for synchronizing financial data in an embodiment of the present invention. Step 103 includes the following specific implementation methods:

[0062] 1031. Query the block parameter corresponding to the internal control system code according to the preset parameter storage table;

[0063] 1032. Query the data corresponding to the block parameters in the preset mapping blockchain to obtain the management system code.

[0064] In steps 1031-1032, the internal control system code does not record the blockchain's block information. Instead, it records the blockchain's parameter storage table in the verification system. Block parameters include interface methods, user IDs, access tokens, blockchain IDs, hash parameters, request strings, and other data. Based on the block parameters, the data corresponding to the block parameters is queried on the mapped blockchain, and the management system code is extracted from the query data.

[0065] Specifically, step 1032 includes the following specific implementation methods:

[0066] 10321. Query the data corresponding to the block parameters in the preset mapping blockchain to obtain the query results;

[0067] 10322. When the query result is empty, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period;

[0068] 10323. When the query result is not empty, extract the management system code from the query result.

[0069] In steps 10321-10323, the block parameters are used to query the recorded data from the mapped blockchain, and the data returned by the query component is received to obtain the query results.

[0070] When the query result is empty, it means that there is no bound financial management system in the authorized internal control system. If an abnormality occurs, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period.

[0071] When the query result is not empty, the query result may be in the form of a key-value pair, an array, etc., and the management system code is extracted from the query result.

[0072] 104. Connect to the financial management system corresponding to the management system code and send the synchronization request to the financial management system;

[0073] In this embodiment, the verification system finds the address corresponding to the management system code from the registry or other internal storage table, connects to the financial management system corresponding to the management system code based on the address, sends the synchronization request to the financial management system, and then the financial management system updates the synchronization data in the synchronization request to the database of the financial management system based on the pre-set update logic.

[0074] For further information, see Figure 3 , Figure 3 This is a specific embodiment of step 104 of the method for synchronizing financial data in an embodiment of the present invention, wherein "sending the synchronization request to the financial management system" includes the following specific implementation methods:

[0075] 1041. Encrypt the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request.

[0076] 1042. Send the encrypted synchronization request to the financial management system according to the preset HTTPS protocol.

[0077] In steps 1041-1042, to prevent sensitive financial data from being intercepted and leaked during transmission from the verification system to the financial management system, the verification system first encrypts the synchronization request using the SM2 algorithm to obtain an encrypted synchronization request. The verification system then directly accesses the financial management system via a dedicated network channel and sends the encrypted synchronization request to the financial management system using the HTTPS protocol. After receiving the encrypted synchronization request, the financial management system decrypts it using the SM2 algorithm to obtain a synchronization request. Finally, the synchronization data in the synchronization request is used to update the financial management system's database.

[0078] For further information, see Figure 4 , Figure 4 This is another specific embodiment of step 104 of the method for synchronizing financial data in an embodiment of the present invention. Step 104 includes the following specific implementation methods:

[0079] 1043. Create a container cluster in a pre-set cloud database, and create a deployment container on the container cluster, wherein the container cluster is used to manage the deployment container;

[0080] 1044. Store the synchronization request in the deployment container through the container cluster;

[0081] 1045. Send the system address of the financial management system corresponding to the management system code to the container cluster, so that the container cluster connects to the financial management system based on the system address.

[0082] 1046. Send a transmission instruction to the container cluster so that the container cluster transmits the storage data in the deployed container to the financial management system.

[0083] In steps 1043-1046, in order to prevent the verification system from directly connecting to an external financial management system, a cloud database is first established, data is uploaded to the cloud database, and then the cloud database transmits the synchronization request to the financial management system. A container cluster is created in the cloud database, and a deployment container is set under the container cluster. The master node in the k8s cluster is referred to as the container cluster, and the node node under the master node is the deployment container. The container cluster is used to manage the deployment container. When the deployment container is a container, the verification system stores the synchronization request in the deployment container through the container cluster. Then, the management system code corresponding to the system address of the financial management system is sent to the container cluster, and the container cluster calls the integration interface to connect to the financial management system.

[0084] Finally, the verification system sends a transmission instruction to the container cluster, which controls the storage synchronization request in the deployed container and transmits it to the financial management system.

[0085] Specifically, step 1044 includes the following specific implementation methods:

[0086] 10441. Encrypt the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request.

[0087] 10442. Store the encrypted synchronization request in the deployment container through the container cluster.

[0088] In steps 10441-10442, the verification system first encrypts the synchronization request using the SM2 algorithm before transmission, generating an encrypted synchronization request. The encrypted synchronization request is then stored in the deployed container via the container cluster. This means encryption is performed before transmission, making it difficult for sensitive data to be directly leaked even if the cloud database is compromised.

[0089] Furthermore, the deployment container includes: a first deployment sub-container and a second deployment sub-container, and step 10442 includes:

[0090] 104421. Split the encryption synchronization request through the container cluster to obtain a first encryption split request and a second encryption split request.

[0091] 104422. Through the container cluster, store the first encryption split request in the first deployment sub-container, and store the second encryption split request in the second deployment sub-container.

[0092] In steps 104421-104422, during the container cluster storage process, the stored data is split and stored, and the synchronization encryption request is first split into a first encryption split request and a second encryption split request. The first encryption split request is then stored in the first deployment sub-container, and the second encryption split request is stored in the second deployment sub-container. Upon receiving the transmission instruction, the data stored in the two sub-containers is queried and the original split data is merged into a single encryption synchronization request for transmission to the financial management system. This splitting method can achieve distributed storage using cloud databases, speeding up upload and download speeds and improving data security.

[0093] 105. Monitor the status code returned by the financial management system;

[0094] In this embodiment, the verification system monitors the status code returned by the financial management system. If the status code is the preset k200, it is considered that the synchronization data of the synchronization request has been decrypted by the financial management system and the database has been updated.

[0095] 106. When the status code is a preset update code, determining that the data corresponding to the synchronization request is in a synchronized state in the financial management system;

[0096] In this embodiment, an if statement is used for conditional confirmation. When the update code is confirmed to be k200, the verification system determines in the preset status record information log that the data corresponding to the synchronization request is in a synchronized state in the financial management system, so that users can check the data update status in a timely manner.

[0097] 107. When the status code is not a preset update code, resend the synchronization request to the financial management system according to a preset exponential backoff algorithm.

[0098] In this embodiment, if the status code is not an update code such as 500, it may be that the information is not smooth due to network problems. The exponential backoff algorithm can set a maximum number of retries, such as 5 times, and resend the synchronization request to the financial management system after 2, 4, 6, 8, 16, and 64 seconds in sequence until the financial management system returns an update code, or after more than 5 retries, it is confirmed that the synchronization request to update the financial management system has failed.

[0099] In an embodiment of the present invention, by introducing a verification system to interact with the internal control system for data exchange, and the verification system to interact with an external financial management system, direct data transmission between the internal control system and the external financial management system is avoided. Furthermore, this solution utilizes the TLS bidirectional transmission protocol to ensure secure transmission between the verification system and the internal control system. Blockchain records are used to map the internal control system to a pre-designated financial management system, preventing the manual modification of important mapping rules that could cause synchronized data to leak to non-designated financial management systems. This allows for efficient and secure synchronization of financial data, resolving the technical issue of insufficient data synchronization security in the financial system field.

[0100] Figure 5 The figure is a schematic diagram of the structure of a financial data synchronization device provided by an embodiment of the present invention. The financial data synchronization device 500 may vary significantly depending on configuration or performance. It may include one or more processors (central processing units, CPUs) 510 (e.g., one or more processors), memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) storing applications 533 or data 532. The memory 520 and storage media 530 may be either transient or persistent storage. The program stored in the storage medium 530 may include one or more modules (not shown), each of which may include a series of instructions operating on the financial data synchronization device 500. Furthermore, the processor 510 may be configured to communicate with the storage medium 530 to execute the series of instructions stored in the storage medium 530 on the financial data synchronization device 500.

[0101] The financial data-based synchronization device 500 may further include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input and output interfaces 560, and / or one or more operating systems 531, such as Windows Server, Mac OS X, Unix, Linux, Free BSD, etc. It will be understood by those skilled in the art that Figure 5 The structure of the synchronization device for financial data shown does not constitute a limitation on the synchronization device based on financial data, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0102] The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the steps of the financial data synchronization method.

[0103] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0104] In addition, although adopting specific order to describe each operation, this should be understood as requiring such operation to be carried out in the specific order shown or in sequential order, or requiring that all illustrated operations should be carried out to obtain desired results. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although comprising some specific implementation details in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Some features described in the context of separate embodiment can also be implemented in a single implementation in combination. On the contrary, the various features described in the context of a single implementation also can be implemented in a plurality of implementations individually or in the mode of any suitable subcombination.

[0105] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for synchronizing financial data, characterized in that: The financial data synchronization method is applied to a financial data synchronization system, wherein the financial data synchronization system includes: an internal control system and a verification system. The financial data synchronization method includes: The internal control system sends a data synchronization request to the verification system according to the preset TLS two-way transmission protocol, wherein the synchronization request includes: the internal control system code and the sending platform certificate; The verification system receives the synchronization request according to the preset TLS two-way transmission protocol, verifies the sending platform certificate, and obtains a verification result; When the verification result is qualified, the internal control system code is queried and mapped according to the preset mapping blockchain to obtain the management system code; Connecting to the financial management system corresponding to the management system code, and sending the synchronization request to the financial management system; Monitor the status code returned by the financial management system; When the status code is a preset update code, determining that the data corresponding to the synchronization request is in a synchronized state in the financial management system; When the status code is not a preset update code, the synchronization request is resent to the financial management system according to a preset exponential backoff algorithm.

2. The method for synchronizing financial data according to claim 1, wherein: The step of sending the synchronization request to the financial management system includes: Encrypting the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request; According to the preset HTTPS protocol, the encrypted synchronization request is sent to the financial management system.

3. The method for synchronizing financial data according to claim 1, characterized in that: The step of connecting to the financial management system corresponding to the management system code and sending the synchronization request to the financial management system includes: Creating a container cluster in a pre-set cloud database, and creating a deployment container on the container cluster, wherein the container cluster is used to manage the deployment container; Storing the synchronization request in the deployment container through the container cluster; Sending the system address of the financial management system corresponding to the management system code to the container cluster, so that the container cluster connects to the financial management system based on the system address; A transmission instruction is sent to the container cluster so that the container cluster transmits the storage data in the deployment container to the financial management system.

4. The method for synchronizing financial data according to claim 3, characterized in that: The step of storing the synchronization request in the deployment container through the container cluster includes: Encrypting the synchronization request according to a preset SM2 algorithm to obtain an encrypted synchronization request; The encrypted synchronization request is stored in the deployment container through the container cluster.

5. The method for synchronizing financial data according to claim 4, characterized in that: The deployment container includes: a first deployment sub-container and a second deployment sub-container, and the step of storing the encrypted synchronization request in the deployment container through the container cluster includes: Splitting the encryption synchronization request through the container cluster to obtain a first encryption split request and a second encryption split request; The first encryption split request is stored in the first deployment sub-container through the container cluster, and the second encryption split request is stored in the second deployment sub-container.

6. The method for synchronizing financial data according to claim 1, characterized in that: The step of querying and mapping the internal control system code according to the preset mapping blockchain to obtain the management system code includes: According to the preset parameter storage table, query the block parameters corresponding to the internal control system code; The data corresponding to the block parameters is queried in the preset mapping blockchain to obtain the management system code.

7. The method for synchronizing financial data according to claim 6, characterized in that: The step of querying the data corresponding to the block parameters in the preset mapping blockchain to obtain the management system code includes: Querying the data corresponding to the block parameters in the preset mapping blockchain to obtain the query results; When the query result is empty, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period; When the query result is not empty, the management system code is extracted from the query result.

8. The method for synchronizing financial data according to claim 1, characterized in that: After the verification system receives the synchronization request according to the preset TLS two-way transmission protocol and verifies the sending platform certificate to obtain the verification result, the following steps are further included: When the verification result is unqualified, an alarm message is sent to the internal control system, and connection with the internal control system is prohibited within a preset time period.

9. A financial data synchronization device, characterized in that: The financial data synchronization device includes: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a line; The at least one processor calls the instructions in the memory to enable the financial data synchronization device to execute the financial data synchronization method according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the financial data synchronization method according to any one of claims 1 to 8 is implemented.

Images