CN115953241A - Block chain-based fund management method and device - Google Patents

Abstract

The present disclosure discloses a block chain based fund management method and apparatus. The block chain comprises a plurality of block chain nodes, and the plurality of block chain nodes correspond to the plurality of application systems for fund management one by one. The method comprises the following steps: receiving a registration request aiming at a payment code; responding to the registration request, generating a payment code, and storing the payment code on the block chain; receiving account moving information aiming at payment codes; and generating a payment bill according to the account moving information, and storing the payment bill on the block chain, wherein the payment bill is associated with the account moving information.

Description

Block chain-based fund management method and device

Technical Field

The disclosure relates to the technical field of block chains, in particular to a fund management method and device based on block chains.

Background

The management of funds in the financial field typically requires the involvement of multiple departments, and requires the interaction of information or funds between the multiple departments. Since the application systems for fund management of various departments are usually independent and can be distributed in different network environments, the interaction of information or funds thereof needs to rely on a communication interface. However, this approach is susceptible to network influences, which may cause anomalies in the process of fund management.

Disclosure of Invention

In view of the above, the present disclosure provides a block chain-based fund management method and apparatus. Various aspects of embodiments of the disclosure are described below.

In a first aspect, a method for fund management based on a blockchain is provided, where the blockchain includes a plurality of blockchain nodes, and the plurality of blockchain nodes correspond to a plurality of application systems for fund management in a one-to-one manner, and the method includes: receiving a registration request aiming at a payment code; responding to the registration request, generating the payment code, and storing the payment code on the block chain; receiving account moving information aiming at the payment code; and generating a payment bill according to the account moving information, and storing the payment bill on the block chain, wherein the payment bill is associated with the account moving information.

In a second aspect, there is provided a fund management apparatus based on a blockchain, where the blockchain includes a plurality of blockchain nodes, and the plurality of blockchain nodes have one-to-one correspondence with a plurality of application systems for fund management, the apparatus including: the first receiving module is used for receiving a registration request aiming at a payment code; the first generation module is used for responding to the registration request, generating the payment code and storing the payment code on the block chain; the second receiving module is used for receiving account moving information aiming at the payment codes; and the second generation module is used for generating a payment bill according to the account moving information and storing the payment bill on the block chain, wherein the payment bill is associated with the account moving information.

In a third aspect, there is provided a blockchain-based funds management apparatus comprising a memory having stored therein executable code and a processor configured to execute the executable code to implement the method of the first aspect.

In a fourth aspect, there is provided a computer readable storage medium having stored thereon executable code which, when executed, is capable of implementing the method of the first aspect.

In a fifth aspect, there is provided a computer program product comprising executable code which, when executed, is capable of implementing the method of the first aspect.

According to the fund management method based on the block chain, the payment codes and the payment bills can be generated and stored by means of the block chain, so that application systems for fund management can interact through the block chain, the influence of network instability in the related technology on the financial fund management is avoided, and the safety, stability and credibility of the fund management are guaranteed.

Drawings

Fig. 1 is a block chain architecture diagram provided in the implementation of the present disclosure.

Fig. 2 is a schematic flow chart illustrating a method for block chain-based fund management according to an embodiment of the present disclosure.

Fig. 3 is a schematic structural diagram of a block chain system according to an embodiment of the disclosure.

Fig. 4 is a flowchart illustrating information interaction based on the blockchain system in fig. 3.

Fig. 5 is a schematic structural diagram of a fund management device based on a block chain according to an embodiment of the present disclosure.

Fig. 6 is a schematic structural diagram of a fund management device based on a block chain according to another embodiment of the present disclosure.

Detailed Description

The technical solutions in the embodiments of the present disclosure are clearly and completely described below, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments.

The management of funds in the financial field typically requires the involvement and interaction of information or funds between multiple departments. For example, the fund management may be management of central financial non-tax revenue. Correspondingly, the plurality of departments may be, for example, finance, receipt units, and banks. The finance may refer to a department that manages national finance, such as the finance department or the financial bureau. The collection unit may refer to a unit responsible for collecting tax revenue and various non-tax revenue, and may be, for example, a traffic management department, an education department, a business inspection department, a planning department, and the like.

Specifically, for the payment of the central financial non-tax income, no matter direct payment or centralized collection is adopted, the financial or receipt unit is required to issue payment codes for payment of payers. After the payment is finished, a payment bill is required to be issued for the payer. The payer can pay the cost to the finance through the collection bank, and can also pay the cost to the collection unit through the collection bank and then be uniformly paid to the finance by the collection unit.

In some embodiments, financial or receipt units may also each have a corresponding agent bank to handle the relevant business. Therefore, the capital of the central financial non-tax income payment process usually relates to the finance, the receipt unit and various agent banks, and the information of the payment codes or payment bills needs to be transferred among various departments.

In the related art, the interaction of information or funds between the respective departments is performed through the communication interfaces of the application systems for fund management of the respective departments. However, since the application systems are usually independent and can be deployed in different network environments, they need to use external communication interfaces provided in different networks when interacting with information or funds. Taking non-tax income as an example, a financial non-tax income and payment management system can be deployed in a telecommunication network, and a corresponding bank-interfacing non-tax income and payment management system can be deployed in a local area network, and the financial system and the bank system need to depend on a communication interface of the telecommunication network and a communication interface in the local area network when interacting.

However, when interacting through external communication interfaces in different networks, it is necessary to rely on the stability and reliability of the networks. If one network is abnormal, the other network can not receive the information which needs to be transmitted. This is very disadvantageous for the management of financial funds, and may cause an abnormality in the process of funds management.

In view of this, the embodiments of the present disclosure provide a fund management scheme based on a block chain. Because the block chain technology has the characteristics of decentralization, distribution, non-tamper-proof property, traceability, safety, credibility and the like, the application systems for fund management can interact through the block chain by generating and storing the payment codes and the payment bills through the block chain, the influence of network instability in the related technology on the financial fund management is avoided, and the safety, the stability and the credibility of the fund management are ensured.

For ease of understanding, the blockchain and its partial concepts involved in the embodiments of the present disclosure will be briefly described.

Block chain (Blockchain)

The blockchain is a distributed chain storage accounting technology based on a cryptographic technology, and therefore, the blockchain can also be called a distributed ledger. In some embodiments, the blockchain is referred to as ledger chain. The block chain technology can prevent and maintain a large amount of data in a decentralized or multi-centralized mode, and has the characteristics of distribution, non-tamper property, traceability, safety, credibility and the like.

Referring to fig. 1, a blockchain 100 is a typical distributed collaboration system. The system includes a plurality of blockchain nodes 110. The plurality of blockchain nodes 110 may collectively maintain an ever-increasing distributed data record. The recorded data may be cryptographically protected in content and timing to make it difficult for either party to tamper with, repudiate, and counterfeit. Blockchain nodes 110 may be devices with computing capabilities, such as servers, groups of servers, blockchain chips, etc., where the groups of servers may be centralized or distributed. In some implementations, the server may be regional or remote. In other implementations, the server may also be a server that provides services for a cloud platform. And the cloud platform may include one or any combination of private cloud, public cloud, hybrid cloud, community cloud, decentralized cloud, internal cloud, and the like.

In the blockchain, data (e.g., transaction information, transaction execution results, etc.) may be encapsulated in the form of blocks (blocks). The tiles may be linked to each other by a forward reference to form a "chain," i.e., a chain of tiles. In general, the first block in a block chain may be referred to as an "originating block" or an "initial block", the one block in the block chain that precedes the current block as a "previous block", and the one block in the block chain that follows the current block as a "subsequent block".

In general, a tile may include a tile head and a tile body. The block header may contain basic information of the current block to ensure that the current block can correctly enter the block chain. For example, the chunk header may record a chunk hash value of a last chunk of the current chunk. As another example, the block header may also record the block height of the current block. The block height is called "block height" for short, and is used to identify the position of the block in the block chain. Typically, the starting block has a block height of 0. The block body can be used for recording transaction information. The transaction information may include, for example, information such as transaction amount and transaction data.

Blockchains are generally divided into three types: public chain (Public Blockchain), private chain (Private Blockchain) and alliance chain (Consortium Blockchain). Furthermore, there may be a combination of the above types, such as private chain + federation chain, federation chain + public chain, and so on. Embodiments provided by the present disclosure can be implemented in a suitable type of blockchain.

In some implementations, the block link point 110 may have a corresponding block link ue (for short, ue), and the block link point 110 may be connected to the ue to enable the ue to obtain the service of the block link. The user side may be an end device or an application on the end device. The terminal device may be any device with computing capabilities, such as a mobile phone, a computer, a wearable computing device or a server, etc. The user terminal may obtain the blockchain service by initiating a blockchain transaction (transaction for short, also referred to as a request), that is, the user terminal may generate a transaction and send the generated transaction to the blockchain through the blockchain node 110. For example, the ue may initiate an uplink request to its corresponding block-link node 110 for data therein, and the block-link node 110 may store the data on the block chain in response to the request.

However, when the user side is an Application on the external end device, the user side may deploy an Application Program Interface (API) for external access in the Application, so that the Application interacts with the blockchain node 110 through the API.

Consensus mechanisms

The consensus mechanism can be understood as how to agree between the nodes responsible for accounting (or accounting nodes) in the blockchain to identify the validity of a record.

The consensus mechanism of the block chain has the characteristics of 'few obedience majority' and 'human-equal', wherein the 'few obedience majority' does not completely refer to the number of nodes, and can also be the computing power, the number of shares or other characteristic quantities which can be compared by a computer. "equal people" means that when the nodes meet the condition, all the nodes have the right to give priority to the consensus result, are directly identified by other nodes, and finally possibly become the final consensus result. Taking bitcoins as an example, workload proofs are used that it is possible to falsify a record that does not exist only if accounting nodes that control more than 51% of the total network are involved. When enough nodes are added into the block chain, the method is basically impossible, thereby avoiding the possibility of counterfeiting.

The trust of the block chain is mainly embodied in that users distributed in the block chain do not need to trust another party of the transaction or trust a centralized mechanism, and the transaction can be realized only by trusting a software system under a block chain protocol. The premise of self-trust is the consensus mechanism of the blockchain, that is, in a mutually untrusted market, a sufficient requirement for each node to agree is that each node, considering the maximization of its own interest, will spontaneously and honestly obey the rules preset in the protocol, judge the authenticity of each record, and finally record the record judged to be true into the blockchain. In other words, if the nodes have independent interests and compete with each other, the nodes are almost impossible to collude to cheat you, which is especially evident when the nodes have a common reputation in the network. The blockchain technology just applies a set of consensus-based mathematical algorithm to establish a 'trust' network between machines, so that brand-new credit creation is performed through technical endorsements rather than centralized credit organizations.

The consensus mechanism of the blockchain may be, for example, one of the following consensus mechanisms: a Proof Of Work (POW), (POS) right and interest (PBFT), a Proof Of share authorization (rsg), a pool verification mechanism, and a Practical Byzantine Fault Tolerance (PBFT).

Intelligent contract

A Smart Contract (Smart Contract) is a computer protocol intended to propagate, verify or execute contracts in an informative manner. In other words, a smart contract may be understood as a piece of program deployed on a computer system, and the smart contract may be automatically executed when a trigger condition of the smart contract is satisfied. There may be multiple intelligent contracts on a blockchain, each of which may execute different code or protocols to achieve different functionality. Smart contracts allow trusted transactions to be conducted without third parties, which transactions are traceable and irreversible.

The presence of blockchains provides technical support for the implementation of intelligent contracts. The smart contract is written into the block chain in a digital form, the storage, reading and execution of the smart contract are guaranteed by the characteristics of the block chain technology, and the whole process is transparent, trackable and not easy to grasp. On the other hand, a set of state machine system can be constructed by the block chain self-contained consensus algorithm, so that the intelligent contract can run efficiently.

In some implementations, a blockchain user can invoke an intelligent contract by submitting a transaction to a blockchain system, set data recorded in the intelligent contract, and then store the set intelligent contract in the blockchain. Accordingly, when a specific condition in the intelligent contract is triggered, the block chain nodes can execute the intelligent contract and record the execution result of the intelligent contract and the execution state of the intelligent contract.

The block chain network in the embodiment of the disclosure supports the development capability of the intelligent contract on the system level, and can write the graphic complete service logic based on the intelligent contract to realize rich service scenes. Meanwhile, the block chain network design supports the multi-language contract programming capability, and the intelligent contract of the multi-language version is compiled to generate a uniform execution instruction set through the design target of the LLVM.

The intelligent contracts provided in the blockchain of embodiments of the present disclosure include a lifecycle of: compiling contracts, namely compiling intelligent contracts by using a contract development language; compiling the contract, namely compiling the intelligent contract into byte codes by using a contract compiler; contract deployment, namely deploying the compiled byte codes to a block chain; the contract is called, and the client sends the transaction for calling the contract method to the blockchain node for execution; contract upgrading, namely, modifying contract codes according to business requirements, recompiling and then updating the contract codes to a block chain; the contract freezes, and the frozen contract no longer allows new calls, and this feature is used for emergency intervention under a contract defect or contract offline.

In view of the above features of the blockchain, as shown in fig. 2, a schematic flow chart of a method for fund management based on a blockchain according to an embodiment of the present disclosure is provided. The blockchain includes a plurality of blockchain nodes, and the plurality of blockchain nodes are in one-to-one correspondence with the plurality of application systems for fund management as described above. The method may be applied to a blockchain node.

It is understood that the correspondence between the block link points and the application system in the embodiments of the present disclosure may refer to that the application system is integrated on the block link nodes, that is, the application system forms a part of the block link network as the block link points. Or, the fact that a blockchain node corresponds to an application system may also mean that the application system may be in communication connection with a node of a blockchain network, that is, the application system may interact with the corresponding blockchain node through its API interface.

Turning in detail to fig. 2, the method in the disclosed embodiment may include steps S210-S240.

In step S210: a registration request for a payment code is received.

The originator of the registration request for a payment code may be a financial or receipt unit. For example, a financial or collection unit may send a registration request for a payment code to a corresponding block link point via a client. Or the financial or collection unit can also be used as a registered user of the block chain to directly send a registration request for the payment code to the block chain link point.

The registration request for the payment code may include related information for generating the payment code, for example, a user identifier of an initiator initiating the payment code, a user identifier of a payer, payment detail information, and the like.

In step S220: and responding to the registration request, generating a payment code, and storing the payment code on the block chain.

The payment code may refer to a data credential for the payer to pay. The payment code may typically be in an agreed format. In some embodiments, the payment code may be a basic element in a non-tax income general payment book (hereinafter, referred to as a payment book). The payment book is a voucher in the form of a digital telegraph text which is issued, stored, transmitted and received by a computer and an information network technology when a financial supervision and collection unit legally collects and collects government non-tax receipts, and is a financial bill expressed in the form of electronic data. The basic elements in the payment can also include receipt unit code, receipt unit name, bill code, bill number, check date, fill-in date, payer (full name, account number, bank of opening an account), payee (full name, account number, bank of opening an account), item code, income item name, unit, quantity, standard of collection, amount of money, receipt unit signature, financial supervision signature, etc. The payment code may be associated with other basic elements in the payment book, that is, other contents of the payment book may also be obtained through the payment code.

In the embodiment of the disclosure, an intelligent contract which automatically generates a payment code may be deployed on the blockchain. After the block chain link point receives the registration request, the intelligent contract can be automatically triggered, so that the block chain executes the relevant codes to generate payment codes.

After the block chain node completes generation of the payment code through the intelligent contract on the block chain, the block chain node can initiate a consensus request. If other nodes on the block chain can achieve consensus based on a consensus mechanism, the block chain link broadcasts the payment code to other nodes on the block chain, and therefore the process of carrying out chain loading and evidence saving on the payment code is completed. By storing the payment code, any block chain node on the block chain can acquire the payment code.

In step S230: and receiving account moving information aiming at the payment codes.

The sender of the account moving information for the payment code can be a payment user. A paying user may be a user who is directed to a financial payment, which may be a payer or a collection unit. Taking the collection of non-tax income as an example, if the collection is a direct collection form, the payment user is a payer or a proxy bank of the payer. If the payment is in a centralized payment form, the payment user can be a collection unit or an agent bank of the collection unit. In the form of centralized remittance, although the payment users who remit to the finance are the collection units or the agent banks of the collection units, the actual payment items still come from the payment persons, and only the collection units can be used as intermediate agents to uniformly pay the payments of a plurality of payment users.

It can be understood that the block chain node receiving the registration request for the payment code and the block chain node receiving the account moving information for the payment code may not be the same block chain node. For example, the block link point that receives the registration request for the payment code may be a node corresponding to finance, and the block link point that receives the account moving information for the payment code may be a node corresponding to a bank. The financial and bank corresponding nodes may together form an ledger chain as shown in fig. 3.

The specific process of account moving may be: and the payment user acquires the payment code through the block chain node. Because the payment code comprises the user identification of the payment user, the payment user can determine whether to process the payment code after acquiring the payment code. If processing is required, a payment request is initiated to have its agent bank initiate the transfer. The transfer information can be understood as account transfer information aiming at payment codes.

In step S240: and generating a payment bill according to the account moving information, and storing the payment bill on the block chain.

The payment bill is associated with account moving information, which is a bill representing account information. The payment bill can be understood as a payment code in a completed state or a completed payment book. In other words, the payment bill contains information of the payment code and the following information that has been filled in: the system comprises a receipt unit code, a receipt unit name, a bill code, a bill number, a check date, a filing date, a payer (full name, account number, bank of opening an account), a payee (full name, account number, bank of opening an account), a project code, a income project name, a unit, a quantity, a collection standard, an amount, a receipt unit signature and a financial supervision signature.

In the embodiment of the disclosure, an intelligent contract which automatically generates a payment bill can be deployed on the block chain. After the block chain link point receives the account moving information, the intelligent contract can be automatically triggered so that the block chain executes the related codes to generate a payment bill. The process of storing the payment bill and the payment code on the block chain is consistent, and details are not repeated here, and reference may be made to the above payment code storage mode.

In the fund management method based on the block chain in the embodiment of the disclosure, the payment code and the payment bill can be generated and stored by means of the block chain. Therefore, the application systems for fund management can interact through the blockchain, the influence of network instability in the related technology on the financial fund management is avoided, and the safety, stability and credibility of the fund management are ensured.

The management of the financial funds includes reconciliation management in addition to the receipt management. In view of this, in some embodiments, the method for block chain-based funds management further comprises the following steps.

In step S250: and receiving a reconciliation request for the payment bill.

The sender of the reconciliation request for the payment instrument may be a financial, receipt or bank. For example, a financial, receipt or bank may send a reconciliation request to the corresponding block link point via its client. Or, the financial, collection unit or bank can be used as a registered user of the block chain to directly send account checking requests for payment bills to the block chain link points.

In step S260: and responding to the account checking request, and calling a payment bill from the block chain.

After receiving the reconciliation request, the block chain node can acquire the payment bill from the transaction address on the chain corresponding to the payment bill. In some embodiments, the transaction address on the chain is block high, and the transaction address on the acquisition chain may be referred to as a pull block high. Financial and collection units or banks can acquire payment bills through the blockchain and check accounts based on the payment bills. By implementing the embodiment of the disclosure, account information can be acquired among users (financial, receipt units or banks) needing account checking through the blockchain without depending on limitations such as network or working time, for example, when account checking is performed among banks, account checking time of banks of both sides can be omitted, so that account checking among application systems for fund management is safer and more reliable.

As mentioned above, the payment code is a data certificate for the payer to pay. In actual use, the payment code can be updated or invalidated. For example, a payment code that has been issued at this time when a failure occurs needs to be updated. Or the payer does not need to pay after complaint, and the payment code needs to be invalidated at the moment.

In view of this, in some embodiments, the method for block chain-based funds management further comprises the following steps.

In step S270: and receiving an operation request aiming at the payment code.

In the embodiment of the present disclosure, the initiator receiving the operation request for the payment code may be consistent with the initiator of the registration request for the payment code described above. For example, as shown in FIG. 3, the initiators are all financial. The operation request may include specific operation contents of an operation for the payment code, for example, the operation performed on the payment code is updated or invalidated.

In step S280: and responding to the operation request, and executing corresponding operation on the payment code through the intelligent contract on the block chain.

The intelligent contracts deployed on the block chain comprise intelligent contracts for updating payment codes and intelligent contracts for invalidating the payment codes. After receiving an operation request for a payment code, the block chain node can determine to specifically trigger a certain intelligent contract according to information contained in the operation request.

In step S290: and storing the operated result on the block chain.

The result after the operation can be understood as the information that the corresponding updated payment code or the payment code is invalidated after the payment code is updated or invalidated. The process of storing the certificate is consistent with that of the payment code, and is not described again here.

The payment code is updated or invalidated through the block chain, and the updated payment code or the invalidated information of the payment code is stored on the block chain, so that corresponding contents can be updated conveniently in time by the block chain links, the safety, the credibility and the non-tamper property are ensured, and the abnormity in the fund management (such as collection or account checking) process is avoided.

In the embodiment of the present disclosure, the payment code or the payment bill may be stored on the block chain in a hash value or hash digest manner, that is, before the consensus request is issued again, the payment code or the payment bill may be converted into the hash value by the block chain link point. The payment code can be a newly registered payment code or an updated payment code. In some embodiments, encryption may also be performed prior to initiating consensus.

Taking the payment code as an example for storing the certificate on the blockchain, storing the payment code on the blockchain may include the following steps: carrying out parameter verification on the payment code; after the parameters are verified, the payment codes are encrypted, and the encrypted payment codes are stored on the block chain. The encrypted payment code comprises an identifier of a payment user corresponding to the payment code.

The parameter verification may be that after the block link point used for generating the payment code calculates the payment code as a hash value, the block link point used for verification is used to verify the hash value so as to ensure credibility. Specifically, the parameter verification may be that after the block link point used for generating the payment code calculates the payment code as a hash value (mark hash value 1), the verified block link point may be used to obtain the hash value (hash value 1) and the payment code. The block link point for verification can perform hash calculation on the payment code to obtain a hash value (marked with the hash value 2), and compare whether the hash value 1 is consistent with the hash value 2. If the hash value 2 and the hash value 1 are identical, the parameter check is passed.

After the parameter verification, the block link point can encrypt the corresponding hash value to ensure the credibility and the non-tamper-resistance of the data to the maximum extent. The encryption method may be, for example, encryption based on an asymmetric encryption technique, or encryption based on an asymmetric encryption technique and time stamping.

It will be appreciated that electronic signatures are typically methods employing asymmetric encryption. Specifically, a trusted node in the block chain obtains a pair of private key and public key when applying for joining the block chain. The private key is only available to the current node and the private keys of other nodes are completely different from it. Signing the same data with different private keys is completely different, similar to the handwriting of a physical signature (i.e. each person signs with a pen is completely different in handwriting). The process of encrypting data using a private key can be referred to as adding an electronic signature, and the encrypted data is a digital signature. The public key is possessed by all nodes belonging to a block chain, and after other nodes receive the broadcasted data and the digital signature, the integrity of the data and the legality of the identity of the sender can be verified by utilizing the public key. If the verification can be successfully passed, the subsequent process is triggered, for example, each node saves it on the block.

The following describes the blockchain and the fund management method based on the blockchain in the embodiment of the disclosure as a specific example in conjunction with fig. 3 and 4. In fig. 3 and 4, its blockchain is referred to as ledger chain. In fig. 3 and 4, finance and banking may interact with corresponding blockchain nodes through their own application systems to obtain blockchain services.

Referring to fig. 3 in detail, the finance side includes the application system of the finance itself and the blockchain non-tax payment dapp1 running in the system. The bank end comprises an application system of the bank and a block chain non-tax payment dapp2 running in the system. dapp is a decentralized application, i.e., an application created based on a chain of blocks. Finance and banks can interact with corresponding block chain link points on the account book chain through corresponding dapp, and the account book chain is operated by using the dapp.

For example, finance may register a payment code, update a payment code, or invalidate a payment code using dapp1. And after the payment code is subjected to parameter verification of dapp1, the payment code can be encrypted and deposited onto an account book chain through the dapp1. The user of the payment code can obtain the encrypted payment code in real time by using a block chain kit (the non-tax ledger SDK1 in fig. 3), and determine whether to analyze the deposit receipt transaction according to the attribution in the encrypted payment code. Taking the bank in fig. 3 as an example of a user, if the analysis is needed, the bank interacts with dapp2 through the fund posting interface, and the account is moved and the certificate is stored in an encrypted manner by using dapp2. It is understood that the SDK can be embedded in dapp, and that FIG. 3 separates the SDK and dapp into two parts for clarity of understanding only.

In addition, all the partners in the account book chain can acquire complete payment code information through the SDK in the dapp, so that account checking among the partners is not based on the stability of the network or the accounting time any more, and the reliability of account checking is ensured.

Fig. 4 is a schematic flow chart of financial fund exchange based on the system in fig. 3. The method specifically comprises a payment code generating process and a bill information generating process.

In fig. 4, a financial or bank may specify at any time a block height (or on-chain transaction address) to pull to request for evidence data or to query for data. In view of this, the complete life cycle of the payment code on the blockchain is safely recorded. Any authorized user can audit the payment code, and banks and financing can also carry out internal reconciliation through a complete payment code list. Because the payment codes on the chain have digital signatures and timestamps, if the financial or bank internal bills and the chain bills are aligned, but the online account checking is abnormal, the error transaction can be quickly positioned, and the next step of correction work can be carried out on the payment codes and the corresponding bank.

Method embodiments of the present disclosure are described in detail above in conjunction with fig. 1-4, and apparatus embodiments of the present disclosure are described in detail below in conjunction with fig. 5 and 6. It is to be understood that the description of the method embodiments corresponds to the description of the apparatus embodiments, and therefore reference may be made to the method embodiments above for parts which are not described in detail.

FIG. 5 is a schematic block diagram of a block chain based fund management device according to an embodiment of the present disclosure. The blockchain includes a plurality of blockchain nodes, and the plurality of blockchain nodes correspond to the application systems of the plurality of departments for fund management in a one-to-one manner.

As shown in fig. 5, the apparatus 500 may include a first receiving module 510, a first generating module 520, a second receiving module 530, and a second generating module 540. These modules are described in detail below.

The first receiving module 510 is configured to receive a registration request for a payment code.

The first generating module 520 is configured to generate a payment code in response to the registration request, and store the payment code on the block chain.

The second receiving module 530 is configured to receive account moving information for the payment code.

The second generating module 540 is configured to generate a payment bill according to the account moving information, and store the payment bill on the blockchain, where the payment bill is associated with the account moving information.

Optionally, the apparatus 500 further includes a third receiving module, configured to receive a reconciliation request for the payment ticket; and the sending module is used for responding to the account checking request and calling the payment bill from the block chain.

Optionally, the first receiving module 510 is further configured to receive an operation request for a payment code, and the apparatus 500 further includes: the execution module is used for responding to the operation request and executing corresponding operation on the payment code through the intelligent contract on the block chain, wherein the operation comprises updating or invalidation; and the evidence storage module is used for storing the operated result on the block chain.

Optionally, the first generating module 520 further comprises: the verification module is used for verifying parameters of the payment codes; the encryption module is used for encrypting the payment code after the parameter verification is passed, and storing the encrypted payment code on the block chain; the encrypted payment code comprises an identifier of a payment user corresponding to the payment code.

Optionally, the sender of the reconciliation request is a financial, receipt or bank.

Fig. 6 is a schematic structural diagram of a fund management device based on a block chain according to still another embodiment of the present disclosure. The apparatus 600 may be, for example, a computing device having computing functionality. The apparatus 600 may be, for example, a mobile terminal or a server. The apparatus 600 may include a memory 610 and a processor 620. Memory 610 may be used to store executable code. The processor 620 is operable to execute the executable code stored in the memory 610 to implement the steps of the various methods described previously. In some embodiments, the apparatus 600 may further include a network interface 630, and data exchange between the processor 620 and an external device may be implemented through the network interface 630.

Embodiments of the present disclosure also provide a computer-readable storage medium having stored thereon executable code that, when executed, is capable of implementing a method as described above.

In the above embodiments, all or part of the implementation may be realized by software, hardware, firmware or any other combination. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the disclosure are, in whole or in part, generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., digital Video Disk (DVD)), or a semiconductor medium (e.g., solid State Disk (SSD)), among others.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. 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.

In the several embodiments provided in the present disclosure, 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 be in an electrical, mechanical or other form.

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 purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present disclosure 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 above description is only for the specific embodiments of the present disclosure, but the scope of the present disclosure is not limited thereto, and any person skilled in the art can easily think of the changes or substitutions within the technical scope of the present disclosure, and shall cover the scope of the present disclosure. Therefore, the protection scope of the present disclosure should be subject to the protection scope of the claims.

Claims (12)

1. A method for fund management based on a blockchain, the blockchain comprising a plurality of blockchain nodes in one-to-one correspondence with a plurality of application systems for fund management, the method comprising:

receiving a registration request aiming at a payment code;

responding to the registration request, generating the payment code, and storing the payment code on the block chain;

receiving account moving information aiming at the payment code;

and generating a payment bill according to the account moving information, and storing the payment bill on the block chain, wherein the payment bill is associated with the account moving information.

2. The method of claim 1, further comprising:

receiving a reconciliation request for the payment bill;

and responding to the account checking request, and calling the payment bill from the block chain.

3. The method of claim 1, further comprising:

receiving an operation request aiming at the payment code;

responding to the operation request, and executing corresponding operation on the payment code through an intelligent contract on a block chain, wherein the operation comprises updating or invalidation;

and storing the operated result on the block chain.

4. The method of claim 1, the crediting the payment code on the blockchain comprising:

carrying out parameter verification on the payment code;

after the parameter is verified, encrypting the payment code, and storing the encrypted payment code on the block chain;

the encrypted payment code comprises an identifier of a payment user corresponding to the payment code.

5. The method of claim 2, wherein the sender of the reconciliation request is a financial, receipt, or bank.

6. A fund management apparatus based on a blockchain, the blockchain comprising a plurality of blockchain nodes, the plurality of blockchain nodes corresponding one-to-one to a plurality of application systems for fund management, the apparatus comprising:

the first receiving module is used for receiving a registration request aiming at a payment code;

the first generation module is used for responding to the registration request, generating the payment code and storing the payment code on the block chain;

the second receiving module is used for receiving account moving information aiming at the payment codes;

and the second generation module is used for generating a payment bill according to the account moving information and storing the payment bill on the block chain, wherein the payment bill is associated with the account moving information.

7. The apparatus of claim 6, further comprising:

the third receiving module is used for receiving a reconciliation request aiming at the payment bill;

and the sending module is used for responding to the reconciliation request and calling the payment bill from the block chain.

8. The apparatus of claim 6, the first receiving module further configured to receive an operation request for the payment code, the apparatus further comprising:

the execution module is used for responding to the operation request and executing corresponding operation on the payment code through an intelligent contract on a block chain, wherein the operation comprises updating or invalidation;

and the evidence storage module is used for storing the operated result on the block chain.

9. The apparatus of claim 6, the first generation module further comprising:

the verification module is used for performing parameter verification on the payment code;

the encryption module is used for encrypting the payment code after the parameter verification is passed, and storing the encrypted payment code on the block chain;

the encrypted payment code comprises an identifier of a payment user corresponding to the payment code.

10. The apparatus of claim 7, the sender of the reconciliation request being a financial, receipt, or bank.

11. A blockchain based funds management apparatus comprising a memory having stored therein executable code and a processor configured to execute the executable code to implement the method of any of claims 1-5.

12. A computer readable storage medium having stored thereon executable code which, when executed, is capable of implementing the method of any one of claims 1-5.

Images