Fund tag management and silver acceptance money flow conversion processing method

Abstract

This invention relates to the field of financial technology, specifically to a method for managing fund tags and processing bank acceptance bills. The method involves acquiring the bill elements of an electronic bank acceptance bill within a co-managed bank account, physically freezing and locking the bill, and generating at least one bank acceptance bill tag within a payment account. Upon receiving a split payment instruction, the method performs tag-level operations only within the payment account, ensuring the bill itself is not physically split. It constructs a tag status hash fingerprint and a mirror snapshot hash for periodic verification. At the maturity date, the method aggregates the current holders to obtain a settlement allocation set and initiates a one-time payment request. This invention enables free splitting and payment of any amount of bank acceptance bills with zero intrusion into the underlying bills, supports multi-level circulation in the industrial chain with zero marginal cost, and triggers a chain topology inversion settlement at the maturity date.

Description

Technical Field

[0001] This invention relates to the field of financial technology, specifically to methods for fund tag management and bank acceptance bill transfer processing. Background Technology

[0002] In recent years, with the rapid development of industrial chain finance and the continuous upgrading of supply chain finance infrastructure, electronic bank acceptance bills, as one of the most important non-cash payment tools between upstream and downstream enterprises in the industrial chain, have become a core indicator for measuring the service efficiency of the entire industrial chain finance infrastructure due to their ability to be split and transferred. However, due to their inherent characteristics of rigid face value and the requirement to transfer the entire bill, traditional electronic bank acceptance bills have long suffered from prominent problems such as mismatched amounts, inflexible transfer, and long periods of capital occupation in the actual payment scenarios of SMEs in the midstream and downstream of the industrial chain. This has become a key bottleneck restricting the extension of industrial chain financial services to SMEs at the end of the chain.

[0003] To alleviate these bottlenecks, the industry has proposed several solutions. Chinese invention patent application CN112149077A discloses a supply chain bill method, system, and computer device based on blockchain technology. This method receives supply chain bill issuance requests to obtain bill data and the issuer, and stores the bill data on the blockchain for distributed storage and access management. All bill holders synchronize bill status through distributed nodes, and operations such as circulation, discounting, and pledging are triggered through on-chain consensus and smart contracts. However, the essence of this solution is still to issue, endorse, and split the bill as a complete certificate on the blockchain. Each split requires a consensus broadcast event between distributed nodes, causing the marginal cost of splitting and circulating to increase approximately linearly with the depth of the supply chain. This cannot support the real-world needs of SMEs at the lower levels of the supply chain for high-frequency splitting and circulation based on actual payment amounts.

[0004] US Patent No. US11250438B2 (PCT family No. WO2021017432A1, original application from China) discloses a blockchain-based method for expense splitting. This method involves a blockchain node receiving a target transaction carrying a target electronic invoice identifier, invoking expense splitting logic declared in a smart contract, and generating multiple expense splitting slips based on the unreimbursed amount in the expense information corresponding to the electronic invoice identifier stored on the blockchain. These slips are then broadcast to the blockchain storage. However, this scheme still requires triggering the smart contract to execute and broadcasting the newly generated expense splitting slips to the blockchain each time expense is split. Each split is accompanied by an on-chain state change registration event, failing to fundamentally escape the constraint that the transfer of vouchers must be equivalent to voucher registration.

[0005] The new-generation bill trading system launched by the Shanghai Commercial Paper Exchange on June 3, 2022, uses a bill package system composed of bills with a minimum unit of 0.01 yuan, combined with a sub-bill range number mechanism, to achieve the splitting and circulation of bills. In this system, the exchange automatically generates bill package numbers and sub-bill range numbers for acceptance bill issuance registration applications. Holders can split and use their bill packages according to the actual amount in endorsement, discounting, and pledging transactions. When the main bill package is frozen, all split sub-bill packages are also frozen. However, the splitting operation still relies on the Shanghai Commercial Paper Exchange's centralized registration system for sequential processing. Each split is accompanied by a bill status change registration event on the exchange's side, and the granularity of sub-bill range splitting is limited to integer multiples of the 0.01 yuan standard unit. The chain-triggered mechanism of sub-bill package freezing also makes the circulation of some sub-bill packages strongly constrained by the status of the main bill package.

[0006] In summary, whether it's a distributed certificate splitting scheme based on blockchain or a sub-ticket number sub-transfer scheme based on centralized bill exchanges, existing technologies couple certificate movement events and bank credit locking events simultaneously. Each split requires a centralized or decentralized state registration cost, causing the marginal cost of splitting electronic bank acceptance bills in multi-level circulation scenarios across the industry chain to increase linearly with the depth of circulation levels. Furthermore, the throughput of banking systems, bill exchanges, or blockchain systems becomes a rigid bottleneck restricting the depth of credit penetration in the industry chain. The root cause of this bottleneck lies in the fact that existing technologies have failed to decouple the bank credit locking of the electronic bank acceptance bill itself from changes in certificate holding shares at the user level. This means that every small-amount splitting payment downstream in the industry chain inevitably affects the state registration of the upstream banking system or infrastructure, resulting in the inability to effectively solve the problem of amount mismatch in actual payment scenarios for SMEs at the end of the industry chain at the engineering level. Summary of the Invention

[0007] To address the core bottleneck in existing electronic bank acceptance bill splitting and transfer schemes within the supply chain finance field—namely, the strong coupling between document movement events and bank credit locking events—which necessitates centralized or decentralized state registration costs for each split, causing the marginal cost of splitting and transfer to increase linearly with the supply chain level and restricting the depth of credit penetration within the supply chain, this invention provides a method for fund tag management and bank acceptance bill transfer processing. This method establishes a five-step deeply coupled closed-loop architecture: physical freezing and locking of the electronic bank acceptance bill itself, free transfer of bank acceptance bill tags at the payment account level, immobile bill, arbitrary amount splitting of the tag layer, mandatory inheritance of maturity date time anchors, periodic verification of mirror invariants, and settlement through maturity date link topology inversion. While maintaining the uniqueness of bill ownership and regulatory compliance, this method achieves free splitting and payment of bank acceptance bills of any amount without any intrusion into the underlying electronic bank acceptance bill, based on the principles of the legal dichotomy of property rights and debt and the conservation of debt flow.

[0008] The technical solution of this invention is: a method for managing fund tags and processing bank acceptance bill transfers, comprising the following steps:

[0009] Obtain the bill elements of the electronic bank acceptance bill body in the co-managed bank account, the bill elements including the face value and maturity date, perform physical freezing and locking on the electronic bank acceptance bill body, and generate at least one bank acceptance gold tag for the electronic bank acceptance bill body in the payment account, the bank acceptance gold tag including the maturity date time anchor field, the value of the maturity date time anchor field is forcibly assigned by the maturity date and cannot be modified by any entity;

[0010] Receive a split payment instruction for any bank acceptance bill held by any payer in the payment account, perform the label layer operation of deducting the face value of the payer's bank acceptance bill and increasing the face value of the payee's bank acceptance bill only in the payment account, and keep the electronic bank acceptance bill body in the co-managed bank account from being physically split, and the maturity date time anchor field of the payee's bank acceptance bill inherits the maturity date time anchor field of the payer's bank acceptance bill;

[0011] Construct the tag state hash fingerprint of the set of all bank acceptance tags corresponding to the electronic bank acceptance bill body. The tag state hash fingerprint Perform a periodic mirror invariant verification with the mirror snapshot hash H_M of the electronic bank acceptance bill body in the co-managed bank account. If the verification fails, issue a reverse write-back correction instruction.

[0012] At the trigger time of the maturity date corresponding to the maturity date time anchor field, scan all bank acceptance bill tags in the payment account whose maturity date time anchor field is equal to the maturity date, aggregate them according to the current holder to obtain a settlement allocation set, initiate a one-time payment request to the electronic bank acceptance bill body in the co-managed bank account, and transfer the payment funds to the cash accounts of each holder according to the settlement allocation set.

[0013] The beneficial effects of this invention are reflected in the following aspects.

[0014] Firstly, this invention achieves complete decoupling between bank credit locking events and document circulation events by simultaneously physically freezing and locking the electronic bank acceptance bill within a co-managed bank account and generating an independently circulated bank acceptance gold tag within the payment account. The mechanism is as follows: the bank credit essence of an electronic bank acceptance bill is the bank's legal commitment to pay the face value on the maturity date, regardless of how the bill is segmented and circulated at the user level. By freezing the electronic bank acceptance bill in the co-managed bank account as a credit anchoring unit, changes in user-level holding shares are devolved to the bank acceptance gold tag accounting layer of the payment account. This allows small-amount, high-frequency split payments in the downstream of multi-level industrial chains to be completed independently at the tag layer, without affecting the co-managed bank account layer or the bill exchange layer. Compared with supply chain bill solutions, this invention reduces the number of bank-level registration events in multi-level circulation scenarios from linearly increasing with the depth of industrial chain levels to a constant number, significantly reducing the marginal cost of splitting and circulating the bill.

[0015] Secondly, this invention establishes a legally binding proof of origin for the set of tags derived from the same electronic bank acceptance bill entity by forcibly inheriting the maturity date anchor field of the payee's bank acceptance bill tag from the payer's bank acceptance bill tag. The mechanism is that the maturity date anchor field cannot be modified by any entity at any stage of the transfer process after the tag is generated, allowing any bank acceptance bill tag to be directly anchored to a unique source electronic bank acceptance bill entity through its maturity date anchor field. This immutability constraint breaks the engineering dependency in smart contract fee splitting schemes that require tiered endorsement tracing to verify the origin relationship of the vouchers, fundamentally eliminating the backtracking costs of multi-level transfer links.

[0016] Third, this invention achieves efficient verification of two-layer ledger consistency at a scale of millions of tags by constructing a periodic verification mechanism of the tag state hash fingerprint and the mirror snapshot hash, and incrementally recalculating the tag state hash fingerprint only when the tag set changes. The mechanism is as follows: the tag state hash fingerprint of the tag set corresponding to the unchanged electronic bank acceptance bill remains unchanged, reducing the global verification complexity from O(M) to O(ΔM), where M is the total number of tags and ΔM is the size of the changed subset. This incremental verification mechanism represents a non-linear efficiency leap compared to the centralized registration or on-chain consensus scheme of the Shanghai Commercial Paper Exchange's new generation of commercial paper business systems.

[0017] Fourth, this invention aggregates all bank acceptance bill tags corresponding to the maturity date time anchor field into a settlement allocation set according to the current holder, and executes a one-time redemption request based on the physical constraint of the debt conservation equation, realizing batch convergence settlement of multi-level circulation links. Its mechanism is as follows: all derived tags originating from the same electronic bank acceptance bill body share the same maturity date time anchor field. At the maturity date trigger time, snapshot aggregation can be directly performed based on the debt flow conservation constraint that the total holding share equals the face value, without the need to trace back the endorsement chain level by level. This topology inversion settlement path reduces the number of bank interactions for maturity settlement from linearly increasing with the number of circulation levels to a constant one, and is non-intrusive and compatible with the current central bank regulatory framework and the existing clearing process of the co-managed bank account opening bank.

[0018] Fifth, the five-step framework of this invention forms a deeply coupled closed loop with bill anchoring, tag splitting, maturity date inheritance, mirror verification, and maturity settlement: the output of the previous step serves as the key input of the next step, and the results of the subsequent step influence the parameters of the previous step through reverse write-back correction instructions. The synergistic effect between multiple steps results in a non-linear increase in the overall system's splitting and circulation efficiency. For example, the incremental verification mechanism of tag status hash fingerprint not only serves the consistency verification of the two-layer ledger itself, but also provides atomic snapshot support for the verification of the debt conservation equation when the maturity date is triggered; the instruction feedback loop of the financial chain payment system writes the elliptic curve digital signature result of each splitting event into the operation log as the audit basis for the reverse write-back correction instructions. This closed-loop synergy achieves a non-linear technical effect far exceeding the simple superposition of each step. Attached Figure Description

[0019] Figure 1 This is an overall flowchart of the fund tag management and bank acceptance gold transfer processing method described in this invention;

[0020] Figure 2 This is a schematic diagram of the two-layer heterogeneous ledger system architecture of the fund tag management and bank acceptance fund transfer processing method described in this invention;

[0021] Figure 3This is a detailed flowchart of step S1, the bill anchoring and bank acceptance gold tag generation steps, as described in this invention.

[0022] Figure 4 This is a detailed flowchart of step S2, the tag layer splitting payment step, as described in this invention;

[0023] Figure 5 This is a detailed flowchart of step S3, the incremental verification step of the tag status hash fingerprint, as described in this invention.

[0024] Figure 6 This is a detailed flowchart of the link topology inversion and settlement step S4 of the present invention. Detailed Implementation

[0025] The technical solution of the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0026] The fund tag management and bank acceptance bill transfer processing method described in this invention operates on a two-tier heterogeneous ledger system architecture. For example... Figure 2 As shown, the system architecture consists of three logical entities: the upper-level financial chain payment system, the middle-level payment account, and the lower-level co-managed bank account.

[0027] The Caijinlian payment system, as the upper-level instruction source for the split payment instructions, is responsible for transforming the actual payment needs between the bill holder and the payee into standardized split payment instructions and issuing them to the payment account. The Caijinlian payment system is typically operated by core enterprises in the industry chain, government special fund managers, or payment institutions with a People's Bank of China payment license. It establishes a two-way instruction channel with the payment account through a dedicated application programming interface. The payment account, as the tagged debt layer, carries the independent addition and subtraction accounting for at least one bank acceptance bill tag. The bank acceptance bill tags within the payment account can freely circulate between different users for any amount, and any transaction does not affect the co-managed bank account layer. The co-managed bank account, as the underlying property rights layer, carries the physical custody and maturity payment of the electronic bank acceptance bill itself and is the legal entity anchored to bank credit. The co-managed bank account is operated by a commercial bank with acceptance and custody qualifications recognized by the "Administrative Measures for Electronic Commercial Bill Business" as the opening bank.

[0028] The core of this invention lies in freezing the electronic bank acceptance bill in a co-managed bank account into a non-transferable, non-splitable, and non-endorsable anchored state through a physical freeze-lock command. Simultaneously, a set of independently transferable bank acceptance gold tags is generated for the electronic bank acceptance bill in the payment account, creating an asymmetric projection relationship between the two: the electronic bank acceptance bill itself remains physically immobile, while the tag layer allows for arbitrary amount splitting. This asymmetric projection relationship maintains consistency through the mandatory inheritance constraint of the maturity date anchor field and the periodic verification mechanism of the tag state hash fingerprint and the mirror snapshot hash. Specifically, when the bill holder deposits an electronic bank acceptance bill into the co-managed bank account, the electronic bank acceptance bill is frozen and locked at the co-managed bank account level, while its face value, maturity date, bill number, and other bill elements are mapped to the bank acceptance gold tag field at the payment account level. Subsequent split payment commands only affect the bank acceptance gold tag set at the payment account level, while the electronic bank acceptance bill itself remains frozen and locked at the co-managed bank account level.

[0029] The overall process of the method of the present invention is as follows: Figure 1 As shown, the system comprises four core steps: Step S1, bill anchoring and bank acceptance label generation; Step S2, label layer splitting and payment; Step S3, incremental verification of label status hash fingerprint; and Step S4, settlement based on the link topology inversion on the maturity date. These steps are interconnected through a closed-loop feedback mechanism: when Step S3 detects an anomaly in the periodic verification of the mirror invariant, it writes back to the label snapshot in Step S2; similarly, Step S4 triggers a reverse write-back correction instruction when the debt conservation equation fails, ensuring the entire system maintains strong consistency across the two-layer ledger.

[0030] Step S1: Bill anchoring and bank acceptance bond generation. (For example...) Figure 3 As shown, the specific execution process of step S1, bill anchoring and bank acceptance gold tag generation, is as follows.

[0031] Suppose that Company M holds an electronic bank acceptance bill with a face value of RMB 1 million, an issue date of May 1, 2026, and a maturity date of August 1, 2026. The accepting bank is a commercial bank. Company M deposits the electronic bank acceptance bill into a co-managed bank account through the corporate electronic banking channel of the co-managed bank account opening bank. The co-managed bank account opening bank receives a physical freeze request submitted by the payment account operator. The physical freeze request carries the bill elements of the electronic bank acceptance bill and the elliptic curve digital signature of the payment account operator. The elliptic curve digital signature is generated using the ECDSA-secp256k1 signature algorithm, and the signature input is the SHA-256 digest value of the bill elements and the request timestamp. After the co-managed bank account opening bank verifies the elliptic curve digital signature, it switches the status field of the electronic bank acceptance bill from a transferable state to a frozen state. In the frozen and locked state, the electronic bank acceptance bill itself does not respond to any endorsement, transfer, discount, or pledge requests from outside the co-managed bank account opening bank, but still responds to payment requests triggered on the maturity date, thereby maintaining compatibility with the existing electronic commercial bill system.

[0032] After the physical freeze is completed, the payment account operator generates the first bank acceptance bond tag for the bill holder, Company M, within the payment account. The data structure of this first bank acceptance bond tag includes a unique tag identifier, a source electronic bank acceptance bill identifier, a face value field, a current holder identifier, a maturity date anchor field, and a hash fingerprint auxiliary field. The face value field is assigned a value of 1 million yuan, equal to the face value of the electronic bank acceptance bill; the maturity date anchor field is forcibly assigned August 1, 2026, equal to the maturity date of the electronic bank acceptance bill; and the current holder identifier is assigned the payment account user identifier of Company M. The payment account operator stores the first bank acceptance bond tag in the bank acceptance bond sub-account of the payment account.

[0033] In the payment account view of holder M company, the first bank acceptance bill tag is presented as an asset unit that can be used for splitting payments. In the view of the co-managing bank account opening bank, the electronic bank acceptance bill itself remains frozen and locked, and its bill elements such as face value, maturity date, drawer, and acceptor do not change. Through this step, the bank credit represented by the electronic bank acceptance bill is anchored at the co-managing bank account layer, while its corresponding holding share is sinking to the payment account layer in the form of a bank acceptance bill tag. The two establish a common source mapping relationship through the maturity date time anchor field. The electronic bank acceptance bill itself remains physically immobile throughout its entire lifecycle. All subsequent splitting, circulation, market transactions, and maturity settlement are completed independently at the tag layer without triggering any state changes at the co-managing bank account layer.

[0034] It is important to note that the design of this step is fully compatible with the existing "Administrative Measures for Electronic Commercial Draft Business" and the operating rules of the People's Bank of China's electronic commercial draft system: the physical freeze and lock-up state of the electronic bank acceptance draft itself is essentially a special application of the existing pledge lock-up state of the electronic commercial draft system, requiring no modification to the central bank's electronic commercial draft system; the bank acceptance gold tag at the payment account layer is an internal account recording activity of the payment institution, covered by the payment institution's own licensing and compliance system. This non-intrusive compatibility design allows the present invention to be implemented without altering the existing financial infrastructure.

[0035] Step S2: Split payment at the tag layer. For example... Figure 4 As shown, the specific execution process of step S2, label layer split payment, is as follows.

[0036] Suppose that Company M, the bill holder, initiates a small-amount split payment to its upstream suppliers, Companies A, B, and C. Company M pays Company A 300,000 yuan, Company B 250,000 yuan, and Company C 150,000 yuan, totaling 700,000 yuan. The remaining 300,000 yuan is held in Company M's bank acceptance certificate account. Company M initiates the split payment instruction to the payment account operator through its payment account client. The split payment instruction includes the payer's bank acceptance certificate tag identifier, a list of payee payment account user identifiers, the payment amount corresponding to each payee, and the due date anchor field of the payer's bank acceptance certificate tag.

[0037] Upon receiving the split payment instruction, the payment account operator first performs a deduction operation on the face value of the payer's bank acceptance certificate within the payment account: reducing the face value of the first bank acceptance certificate held by Company M from 1 million yuan to 300,000 yuan. Then, new bank acceptance certificates are generated for the three payees, A, B, and C: Company A receives a bank acceptance certificate with a face value of 300,000 yuan, Company B receives a bank acceptance certificate with a face value of 250,000 yuan, and Company C receives a bank acceptance certificate with a face value of 150,000 yuan. The expiration date anchor field of all three newly generated bank acceptance certificates is forcibly assigned the exact same value as the expiration date anchor field of Company M's first bank acceptance certificate, i.e., August 1, 2026.

[0038] At this point, the number of bank acceptance tags derived from the same electronic bank acceptance bill body within the payment account has increased from one at the time of issuance to four, namely RMB 300,000 for Company M, RMB 300,000 for Company A, RMB 250,000 for Company B, and RMB 150,000 for Company C. The sum of the face values ​​of the four bank acceptance tags remains equal to the face value of the electronic bank acceptance bill body, RMB 1,000,000. The execution process of the split payment instruction is completed solely through tag recording within the payment account, without initiating any instructions to the co-managing bank account opening bank. The status field of the electronic bank acceptance bill body within the co-managing bank account remains frozen and locked without any change.

[0039] Companies A, B, and C, as the recipients of this split payment, can view the newly acquired bank acceptance bill tags in their payment accounts and initiate subsequent split payment instructions to upstream suppliers based on these tags. For example, Company A can further split the acquired 300,000 yuan bank acceptance bill tag into 180,000 yuan to pay Company D and 120,000 yuan to pay Company E. The entire secondary splitting process is also completed solely within the aforementioned payment accounts through tag accounting. When Companies D and E obtain new bank acceptance bill tags, their maturity date anchor field is also forcibly equal to August 1, 2026. This continues down to third-, fourth-, and even deeper levels of the supply chain suppliers, where the maturity date anchor field of all derived bank acceptance bill tags originating from the electronic bank acceptance bill deposited by Company M is strictly equal to August 1, 2026.

[0040] Through the mandatory inheritance constraint of the maturity date anchor field, all derived bank acceptance tags originating from the electronic bank acceptance bill entity held by Company M share the same maturity date anchor field value after any level of circulation. This immutable constraint allows the current holder of any bank acceptance tag to be directly anchored to the unique source electronic bank acceptance bill entity solely based on the maturity date anchor field, without relying on any form of endorsement chain backtracking or blockchain consensus broadcasting.

[0041] Specifically, when the payer's bank acceptance label corresponds to two or more source electronic bank acceptance bills, for example, Company M deposits two electronic bank acceptance bills with maturity dates of August 1, 2026 and September 15, 2026 respectively, the execution steps of the split payment instruction further include dividing the payer's bank acceptance labels into at least two subsets according to the maturity date time anchor field. Within each subset, label layer operations are performed to deduct the face value of the payer's bank acceptance label and increase the face value of the payee's bank acceptance label. After the split payment instruction is completed, the payee simultaneously holds multiple bank acceptance labels with different maturity date time anchor fields in the payment account. This subset division mechanism enables the present invention to flexibly handle complex scenarios where the payer's account simultaneously holds multiple bank acceptance labels derived from source electronic bank acceptance bills.

[0042] Step S3: Incremental verification of tag status hash fingerprint. For example... Figure 5 As shown, the specific execution process of step S3, incremental verification of the tag status hash fingerprint, is as follows.

[0043] Because the bank acceptance bill tags in the payment account may be in a constantly changing state due to frequent split payments, and the electronic bank acceptance bill itself in the co-managed bank account remains frozen and unchanged, an efficient two-layer ledger mirror invariant periodic verification mechanism must be established to ensure that the identity constraint between the tag set state of the payment account layer and the electronic bank acceptance bill itself state of the co-managed bank account layer holds at any time. To this end, this invention introduces a tag state hash fingerprint incremental verification algorithm.

[0044] For any frozen or locked electronic bank acceptance bill entity T within the co-managed bank account, the set of all bank acceptance gold tags in the payment account whose source electronic bank acceptance bill entity identifier is equal to T is sorted lexicographically by holder identifier, resulting in a sorted tag record sequence. A SHA-256 hash operation is then performed on this sorted tag record sequence to obtain the tag status hash fingerprint. The calculation formula is:

[0045] ,

[0046] in: The tag status hash fingerprint is the set of all bank acceptance tags corresponding to the electronic bank acceptance bill body T, which is a scalar hash value of length 256 bits, and its value range is... The unit is bit, which is calculated by the SHA-256 hash operation of this formula, and represents the state fingerprint of the set of tags derived from the same electronic bank acceptance bill body at a certain moment. This is a lexicographical sorting operator, meaning that the tag records are arranged according to the lexicographical order of the holder identifier. It is a sequence transformation operation, and its value range is the full permutation space of the input sequence. It has no unit and is determined by the sorting algorithm. The technical effect is to eliminate the difference in the storage order of tag records in the original database to ensure the repeatability of the tag state hash fingerprint. The set of records corresponding to all bank acceptance gold tags of the electronic bank acceptance bill body T is a variable-length vector. Each element is a tag record with a value range of the Cartesian product of the set of non-negative integers. It has no unit and is obtained by filtering the source electronic bank acceptance bill body identifier in the payment account. The technical effect is to form the input data source of the tag status hash fingerprint. The SHA-256 cryptographic hash function, as specified by the National Institute of Standards and Technology (NIST), maps an input message of arbitrary length to a fixed output hash value of 256 bits. It is a one-way hash function with a value range of [value range missing]. Unitless, defined by the FIPS 180-4 standard, its technical effect is to provide a collision-resistant state fingerprint for the tag recording sequence. (Left side of the equation) The unit is bit, and the right side of the equation... The output is fixed at 256 bits, and the unit is also bit, with the units on both sides being strictly consistent.

[0047] Furthermore, construct the mirror snapshot hash of the electronic bank acceptance bill body T. The calculation formula is:

[0048] ,

[0049] in: The hash of the mirror snapshot of the electronic bank acceptance bill body T is a scalar hash value of length 256 bits, with a value range of [value range missing]. The unit is bits, which is calculated by the SHA-256 hash operation of this formula, and represents the current snapshot fingerprint of the electronic bank acceptance bill body in the co-managed bank account; Let T be the face value of the electronic bank acceptance bill, which is a scalar quantity with a value range of [value range missing]. The unit is yuan, which is determined by the bank where the co-managed bank account is opened when the bill is issued. The technical effect is to identify the bank credit limit of the bill. The maturity date of the electronic bank acceptance bill body T is a date scalar, and its value range is any working day within 6 months after the billing date. The unit is day, which is determined by the drawer at the time of billing. The technical effect is to mark the time anchor point that identifies the bank's payment obligation. The unique identifier of the electronic bank acceptance bill body T is a string scalar with a value range of the bill number space defined by the electronic commercial bill system specification. It has no unit and is assigned by the bank where the co-managed bank account is opened when the bill is issued. Its technical effect is to identify the unique identity of the bill. This is a string concatenation operator, meaning it concatenates the strings on both sides sequentially to form a single input sequence. It is a concatenation operation, has no unit (as defined by the system), and its technical effect is to construct a composite input for the SHA-256 hash function. (Left side of the equation) The unit is bit, and the right side of the equation... The output is fixed at 256 bits, and the unit is also bit, with the units on both sides being strictly consistent.

[0050] The payment account operator performs verification according to a preset cycle. The mirror invariant periodic verification is performed periodically, wherein the preset verification period is... The typical value is 60s. Within each preset verification period, the total face value of all bank acceptance tags corresponding to the electronic bank acceptance bill body T is calculated, and the following identity is verified:

[0051] ,

[0052] Where: the summation symbol on the left side of the equation This indicates the electronic bank acceptance bill body T corresponding to Sum the face values ​​of the silver and gold ingots; This is the index subscript of the silver certificate label, a positive integer, with a value range of [value missing]. The units are not specified; they are allocated in chronological order by the tag accounting system of the payment account, and the technical effect is to number the tags participating in the summation. The total number of bank acceptance gold tags corresponding to the electronic bank acceptance bill body T at the current moment is a positive integer, and its value ranges from 1 to 2. The unit is not specified. It is obtained by the payment account counting the bank acceptance gold tags whose identifier is equal to T at the current moment. The technical effect is to represent the number of tags at the current circulation level. For the first The face value of each silver and gold coin is a scalar quantity, with a range of values ​​of [value range missing]. The unit is yuan, determined by the tag accounting system of the payment account at the time of execution of the split payment instruction. The technical effect is to characterize the first... The number of claims held by each current holder; The definition is the same as in the previous formula, and the unit is yuan. The left side of the equation is... The summation of the face value scalars, in yuan; the right side of the equation is the face value of the electronic bank acceptance bill body T, also in yuan, and the units on both sides are strictly consistent.

[0053] When the identity relation holds, the periodic verification of the mirror invariant is deemed successful. When the split payment instruction causes a change in the set of bank acceptance tags corresponding to the electronic bank acceptance bill body T, the tag state hash fingerprint is recalculated only for the changed set of bank acceptance tags. The hash fingerprint of the tag status of the electronic bank acceptance bill body corresponding to the bank acceptance tag set that has not changed. This incremental verification mechanism reduces the complexity of global verification for millions of tags from O(M) to O(ΔM), where M is the total number of bank acceptance tags in the payment account, and ΔM is the size of the subset of bank acceptance tags that changed during the current period. In typical industry chain scenarios, the size of the changed subset ΔM within a single verification period is usually much smaller than the total number of tags M, giving the incremental verification mechanism a significant non-linear efficiency advantage over global traversal verification in engineering implementation.

[0054] When the aforementioned identity relationship fails, for example, due to system malfunction or abnormal operation causing some bank acceptance bill tags to be incorrectly deducted, the payment account operator triggers the reverse write-back correction instruction. The reverse write-back correction instruction sends a tag snapshot reset instruction to the payment account, restoring the face value status of all bank acceptance bill tags corresponding to the electronic bank acceptance bill body T to the previous verified snapshot point. The specific content of the snapshot point includes the tag's unique identifier, face value field, current holder identifier, and maturity date time anchor field of all bank acceptance bill tags corresponding to the electronic bank acceptance bill body T at that snapshot point, and is persistently stored by the payment account operator in the payment account's snapshot storage facility according to a preset snapshot period.

[0055] During the incremental verification process of the tag state hash fingerprint, this invention discovered an unexpected emergence phenomenon: the tag state hash fingerprint The frequency of changes actually reflects the depth of industry chain penetration corresponding to the electronic bank acceptance bill itself. The higher the frequency of changes, the more levels of splitting and circulation the bank acceptance gold label derived from the electronic bank acceptance bill itself has undergone. Based on this emergence characteristic, this invention introduces an industry chain penetration index.

[0056] In the statistical period Within, the hash fingerprint of the tag status corresponding to the electronic bank acceptance bill body T is statistically analyzed. The number of changes, constructing a supply chain penetration index The calculation formula is:

[0057] ,

[0058] in: The industry chain penetration index of the set of bank acceptance gold tags corresponding to the electronic bank acceptance bill body T is a scalar quantity with a value range of [value range missing]. The unit is times / h, which is calculated by this formula and represents the splitting and circulation activity of the tag set derived from the same electronic bank acceptance bill body within a unit of time. For the statistical period The tag state hash fingerprint described inside The number of changes, which is a non-negative integer, has a range of values ​​of 1. The unit is times, and the tag status hash fingerprint is generated by the tag accounting system of the payment account within the statistical period. The recalculated event count is obtained, and the technical effect is the original observation that characterizes the activity of the industrial chain circulation; The statistical period for the aforementioned industry chain penetration index is denoted as , where is a scalar and its value range is . The unit is h, which is pre-configured by the payment account operator according to the risk control strategy. A typical value is 24h. The technical effect is to determine the time resolution of the industry chain penetration indicator. Too short a time resolution will introduce random noise and fail to stably reflect the flow pattern; too long a time resolution will lose transient flow characteristics and fail to identify anomalies in a timely manner. (Left side of the equation) The unit is times / h, and the numerator on the right side of the equation is... The unit is times, and the denominator is times. The unit is h, and the unit of the ratio is times / h. The units on both sides are strictly consistent.

[0059] The payment account operator uses the industry chain penetration index. The differentiated risk control levels are assigned to all bank acceptance tags corresponding to the electronic bank acceptance bill body T. These differentiated risk control levels include three tiers: low risk control, medium risk control, and high risk control. When the frequency is less than 2 times / hour, the differentiated risk control level of the bank acceptance gold tag corresponding to the electronic bank acceptance bill body T is set to the low risk control level, and the split payment instruction corresponding to the bank acceptance gold tag is directly released; when When the frequency is greater than or equal to 2 times / hour and less than 5 times / hour, the differentiated risk control level is set to the medium risk control level. Before execution, the split payment instruction corresponding to the bank acceptance gold label undergoes an additional secondary risk control algorithm verification. This secondary verification includes querying the historical transaction relationship between the payer and payee and calculating the deviation between the current split payment instruction amount and the historical average amount. When the number of transactions is greater than or equal to 5 times / hour, which is the preset upper limit threshold for penetration, the differentiated risk control level is set to the high risk control level. The split payment instruction corresponding to the bank acceptance gold label must be manually reviewed by the risk control personnel of the payment account operator before it can be executed.

[0060] The preset penetration limit is determined by the payment account operator based on the statistical distribution characteristics of historical supply chain data and the regulatory requirements for supply chain penetration depth. In this embodiment, based on historical data collected from typical domestic supply chain finance platforms, normal supply chain penetration depth is typically between 4 and 6 layers, corresponding to the supply chain penetration index. Typical values ​​are less than 4 times / hour. Therefore, setting the preset penetration upper limit threshold to 5 times / hour can ensure the identification of abnormal high-frequency circulation events without causing excessive interference to normal supply chain circulation behavior. If the preset penetration upper limit threshold is too low, it will trigger too much manual review, reducing system efficiency; if it is too high, it will increase the risk of missing abnormal circulation events. Fine-tuning is required based on specific application scenarios.

[0061] Step S4: Link topology inversion settlement on the due date. (e.g., ...) Figure 6 As shown, the specific execution process of the link topology inversion settlement on the due date in step S4 is as follows.

[0062] When the maturity date of the electronic bank acceptance bill body T is... Upon arrival, the present invention initiates the maturity date link topology inversion settlement process. This maturity settlement process utilizes the physical constraints of the debt fluid conservation equation to achieve batch convergence settlement of multi-level circulation links, eliminating the need for step-by-step backtracking of the endorsement chain.

[0063] At the maturity date trigger time, the payment account operator scans all bank acceptance cards in the payment account whose maturity date time anchor field is equal to that maturity date, and aggregates them by current holder to obtain the settlement allocation set. Defined as:

[0064] ,

[0065] in: Let T be the settlement allocation set for the maturity date of the electronic bank acceptance bill body T, which is a variable-length vector set, where each element is a tuple. The value range is the current holder's identifier space and... The Cartesian product, which is unitless, is obtained by the aggregation operation in this step and represents all current holders and the amount of their claims at the time of the maturity date trigger. For the first The identifier of the current holder is a string scalar, whose value range is the entire user identifier space of the payment account, has no unit, and is assigned by the payment account when the user registers. The technical effect is to identify the final recipient of the claim. For the first The face value of the bank acceptance certificate held by each current holder at the time of the maturity date triggering is a scalar quantity, with a value range of [value missing]. The unit is yuan, and the payment account determines the maturity date of all the current holders' holdings based on the maturity date. The summation of the silver and gold labels is obtained, and the technical effect is to characterize the first The number of claims that the current holder can be redeemed upon maturity; The total number of current holders of the electronic bank acceptance bill body T at the time of its maturity date triggering is a positive integer, and its value ranges from [value missing]. The unit is not specified. It is obtained by deduplicating the current holders of the bank acceptance gold tag corresponding to the electronic bank acceptance bill body T at the time of maturity triggering by the payment account. The technical effect is to characterize the final holder scale corresponding to the penetration depth of the industrial chain.

[0066] The payment account operator uses the settlement allocation set Verify by executing the stated debt conservation equation:

[0067] ,

[0068] Where: the summation symbol on the left side of the equation Represents the settlement allocation set All Sum the face value of the bank acceptance bills held by each current holder; , , The definition is the same as the aforementioned definition of the settlement allocation set; The definition is the same as the aforementioned definition of a snapshot hash, with the unit being bytes. The left side of the equation is... The summation of the face value scalars, in yuan; the right side of the equation is the face value of the electronic bank acceptance bill body T, also in yuan, and the units on both sides are strictly consistent.

[0069] The physical meaning of the aforementioned debt conservation equation is that all derived bank acceptance tags originating from the same electronic bank acceptance bill entity T constitute a debt fluid conservation system. Regardless of how many levels of splitting and transfer occur, the sum of the debt amounts held by all current holders at the maturity date must be strictly equal to the face value of the electronic bank acceptance bill entity T. This conservation constraint is essentially a mathematical formalization of the legal mapping relationship between property rights and debts, and is the mathematical invariant of the two-layer heterogeneous ledger architecture of this invention.

[0070] When the aforementioned debt conservation equation holds, the payment account operator initiates a one-time payment request for the electronic bank acceptance bill T within the co-managed bank account. Upon receiving the one-time payment request, the co-managed bank account opening bank, following the current clearing process of the electronic commercial bill system, transfers the face value of the electronic bank acceptance bill T from the acceptor's account to the co-managed bank account. After receiving the payment arrival notification from the co-managed bank account, the payment account operator, according to the settlement allocation set... within The payment funds will be transferred to the cash account of the corresponding current holder item by item. After the transfer is completed, the payment account operator will remove all bank acceptance tags corresponding to the electronic bank acceptance bill body T and switch its status field from valid to settled.

[0071] Specifically, when the aforementioned debt conservation equation does not hold, i.e. This indicates that at some point before the maturity date, the mirror invariant periodic verification had an anomaly but was not corrected in time. The payment account operator then blocks the one-time payment request and triggers the reverse write-back correction instruction. The reverse write-back correction instruction first reverts to the most recent snapshot of the tag state at the point in time where the mirror invariant periodic verification passed. After restoring all bank acceptance tags corresponding to the electronic bank acceptance bill body T to the snapshot state at that point in time, the settlement allocation set aggregation and the debt conservation equation verification process are re-executed. If the debt conservation equation still fails after reverting, the payment account operator marks this maturity settlement event as an anomaly and submits it to the payment account operator's compliance audit team for manual handling.

[0072] Through the maturity date link topology inversion settlement mechanism of this invention, the number of bank interactions for maturity settlement is reduced from a linear increase with the number of levels in the industrial chain to a constant single redemption request. Furthermore, it is non-intrusive and compatible with the clearing process of the existing central bank's electronic commercial bill system. The co-managing bank account opening bank does not need to be aware of how many levels of tag layers the electronic bank acceptance bill T has undergone in the downstream of the industrial chain. In other words, regardless of how many levels or how many bank acceptance tags the electronic bank acceptance bill T has undergone at the payment account layer, from the perspective of the co-managing bank account opening bank, only one complete bill redemption event occurs at the maturity date trigger, which is completely consistent with the maturity redemption process of traditional, unsplit electronic bank acceptance bills, thus maintaining maximum compatibility with existing financial infrastructure.

[0073] In certain application scenarios, the current holder of a bank acceptance token may wish to liquidate their holdings through the bank acceptance token trading market before the maturity date. To support this application scenario, this invention also sets up a bank acceptance token trading account within the payment account as a dedicated sub-account for recording fund flows in the bank acceptance token trading market. The bank acceptance token trading account is used to record the fund flows of users' transactions in the bank acceptance token trading market.

[0074] When a user initiates a Silver Income Tag order placement request on the Silver Income Trading Market, the payment account operator transfers the Silver Income Tag from the user's Silver Income account to their Silver Income trading account. Specifically, this transfer involves switching the current holder identifier field of the Silver Income Tag from a user identifier to a reserved trading account escrow identifier, and simultaneously switching the status field of the Silver Income Tag from a transferable state to a frozen order state. During this transfer period, the Silver Income Tag cannot execute split payment instructions, nor can the corresponding user initiate new split payment instructions from the payment account client.

[0075] The matching engine of the bank acceptance bill trading market performs price matching on bank acceptance bill tags in the pending order status. The matching price conversion logic is usually calculated by subtracting the discount interest corresponding to the remaining days of the maturity date from the face value, where the discount interest is determined according to the real-time interest rate of the bank acceptance bill trading market. Once a match is successful, the payment account operator switches the current holder identifier field of the bank acceptance bill tag from the transaction account custody identifier to the counterparty's user identifier, and switches the status field of the bank acceptance bill tag from the pending order frozen state to the transferable state. During the matching process, the maturity date time anchor field of the bank acceptance bill tag remains unchanged to ensure that the transferred bank acceptance bill tag still belongs to the same tag set derived from the original electronic bank acceptance bill body. If the user chooses to cancel the order if it expires without matching, the current holder identifier field of the bank acceptance bill tag is restored to the original user identifier, and the status field is restored to the transferable state.

[0076] To protect user privacy, when the payment account pushes the privacy mode balance SMS to the user's client, the privacy mode balance includes the sum of the balances in the user's cash account, bank-accepted gold account, cash-accepted gold account, and gold-flow account, but excludes the fund flow of the bank-accepted gold trading account. This aggregation rule of the privacy mode balance ensures that the user's account message push content will not expose the specific details of their pending transactions in the bank-accepted gold trading market, complying with the compliance requirements of financial institutions for protecting user financial transaction privacy. The specific display format of the privacy mode balance is configured by the payment account operator in accordance with the relevant provisions of the "Implementation Measures for the Protection of Personal Information of Commercial Banks" and the "Measures for the Management of Customer Reserve Funds of Payment Institutions".

[0077] It is particularly important to note that there is a potential state conflict between the aforementioned bank acceptance bond trading account and the aggregation operation of the settlement allocation set at the maturity date trigger: if a bank acceptance bond tag is still in the pending order frozen state and has not yet been successfully matched as the maturity date approaches, the payment account operator automatically withdraws the pending order status of the bank acceptance bond tag at the maturity date trigger, restores the current holder identifier field to the original user identifier, restores the status field to the transferable state, and then includes the bank acceptance bond tag in the aggregation scope of the settlement allocation set. This automatic order cancellation mechanism ensures the validity of the debt conservation equation at the maturity date trigger.

[0078] The method of this invention operates entirely within the instruction feedback loop of the Caijinlian payment system. The Caijinlian payment system, acting as the upper-level instruction source for the split payment instruction, issues the split payment instruction to the payment account. After executing the split payment instruction, the payment account feeds back the tag status change result to the Caijinlian payment system. The tag status change result includes the amount after the change of the payer's bank acceptance tag, the amount after the change of the payee's bank acceptance tag, the due date time anchor field, and the tag status hash fingerprint. Four key data points. The label status change result is written to the operation log after being digitally signed by the elliptic curve before being fed back.

[0079] The elliptic curve digital signature uses the ECDSA-secp256k1 signature algorithm. The payment account operator uses its private key to perform an ECDSA signature on the SHA-256 digest value of the tag state change result, generating a digital signature value. Each log entry in the operation log includes a log timestamp, the instruction identifier of the split payment instruction, all fields of the tag status change result, and the elliptic curve digital signature value. The logs are then appended to the payment account operator's immutable log storage facility in chronological order of log timestamps. This immutable log storage facility can be implemented using a write-once, read-many storage medium or a relational database with a digital signature chain verification mechanism, ensuring that the operation logs cannot be tampered with by any entity after being written.

[0080] After receiving the tag status change result feedback, the financial chain payment system uses the public key of the payment account operator to verify the elliptic curve digital signature value. The validity of the split payment event is verified. If the verification passes, the split payment event is marked as confirmed; if the verification fails, the split payment event is marked as pending audit and recorded in the abnormal event queue. The abnormal event queue is manually checked by the operator of the Caijinlian payment system according to a preset audit cycle. After the check is completed, the events in the abnormal event queue will be removed from the pending audit status or upgraded to system abnormal events.

[0081] The operation log serves as the audit basis for the reverse write-back correction instruction. When an anomaly is detected in the periodic verification of the mirror invariant or the verification of the debt conservation equation, the payment account operator queries the most recently verified snapshot point in the operation log, restores the tag status of that snapshot point to the corresponding bank acceptance gold tag set within the payment account, and notifies the Caijinlian payment system to reissue the relevant split payment instruction via the reverse write-back correction instruction. The reverse write-back correction instruction includes an anomaly event identifier, a list of split payment instruction identifiers to be rolled back, a timestamp of the target snapshot point, and the elliptic curve digital signature of the payment account operator. This instruction feedback loop forms a complete audit closed loop between the tag status change result, the elliptic curve digital signature, the operation log, the periodic verification of the mirror invariant, and the reverse write-back correction instruction.

[0082] Through the design of the instruction feedback loop, this invention achieves strong consistency constraints among the three logical entities of the financial chain payment system, the payment account, and the co-managed bank account, and enables any abnormal event to be audited and traced back through the operation log, thus meeting the compliance requirements of financial regulatory agencies for the traceability, auditability, and non-repudiation of payment and settlement systems.

[0083] Although the core of this invention is the above-mentioned method for managing fund tags and processing bank acceptance bills, those skilled in the art should understand that the method for managing fund tags and processing bank acceptance bills can be implemented by various devices or systems, and these devices or systems also fall within the protection scope of this invention.

[0084] For example, the method of the present invention can be implemented by a fund tag management and bank acceptance card transfer processing device. This device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the fund tag management and bank acceptance card transfer processing method as described in any one of claims 1 to 10. The memory can be a non-volatile storage medium such as a solid-state drive or a hard disk drive, or it can be a volatile storage medium such as random access memory. The processor can be any processing unit capable of executing computer program instructions, such as a general-purpose central processing unit, a graphics processing unit, an application-specific integrated circuit, or a field-programmable gate array.

[0085] For example, the method of the present invention can also be implemented by a fund tag management and bank acceptance bond circulation processing system. This system includes a bill anchoring module, a tag splitting module, a maturity date inheritance module, a mirror verification module, and a maturity settlement module. Specifically, the bill anchoring module is used to perform step S1 of bill element acquisition and bank acceptance bond tag generation; the tag splitting module is used to perform step S2 of tag layer splitting payment; the maturity date inheritance module is used to perform step S2 of maturity date time anchor field inheritance assignment; the mirror verification module is used to perform step S3 of tag status hash fingerprint incremental verification; and the maturity settlement module is used to perform step S4 of maturity date link topology inversion settlement. The modules interact and transmit data through a service bus within the payment account operator's internal network. This service bus can be implemented using any communication architecture such as message queues, remote procedure calls, or event-driven architecture.

[0086] Furthermore, the method of the present invention can also be implemented by a computer-readable storage medium. This computer-readable storage medium stores a computer program that, when executed by a processor, implements the aforementioned fund tag management and bank acceptance fee transfer processing method.

[0087] It should be noted that the steps of the method described in this invention are not limited to being executed in the order described in the above embodiments. There is a strict sequential dependency between step S1 (bill anchoring and bank acceptance tag generation) and step S2 (tag layer splitting payment), but step S3 (tag state hash fingerprint incremental verification) and step S2 (tag layer splitting payment) are in parallel relationship of periodic triggering and event triggering. Step S4 (maturity date link topology inversion settlement) is an independent event triggered by the maturity date. Those skilled in the art can reasonably adjust the execution sequence of each step according to the specific implementation scenario, and all such adjustments fall within the protection scope of this invention.

[0088] The embodiments described above are merely preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention. Any person skilled in the art can easily make changes or substitutions within the technical scope disclosed in the present invention, and such changes or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for managing fund tags and processing bank acceptance bill transfers, characterized in that, Includes the following steps: Obtain the bill elements of the electronic bank acceptance bill body in the co-managed bank account, the bill elements including the face value and maturity date, perform physical freezing and locking on the electronic bank acceptance bill body, and generate at least one bank acceptance gold tag for the electronic bank acceptance bill body in the payment account, the bank acceptance gold tag including the maturity date time anchor field, the value of the maturity date time anchor field is forcibly assigned by the maturity date and cannot be modified by any entity; Receive a split payment instruction for any bank acceptance bill held by any payer in the payment account, perform the label layer operation of deducting the face value of the payer's bank acceptance bill and increasing the face value of the payee's bank acceptance bill only in the payment account, and keep the electronic bank acceptance bill body in the co-managed bank account from being physically split, and the maturity date time anchor field of the payee's bank acceptance bill inherits the maturity date time anchor field of the payer's bank acceptance bill; Construct the tag state hash fingerprint of the set of all bank acceptance tags corresponding to the electronic bank acceptance bill body. The tag state hash fingerprint The mirror snapshot hash of the electronic bank acceptance bill body within the co-managed bank account Perform periodic verification of mirror invariants; if the verification fails, issue a reverse write-back correction command. At the trigger time of the maturity date corresponding to the maturity date time anchor field, scan all bank acceptance bill tags in the payment account whose maturity date time anchor field is equal to the maturity date, aggregate them according to the current holder to obtain a settlement allocation set, initiate a one-time payment request to the electronic bank acceptance bill body in the co-managed bank account, and transfer the payment funds to the cash accounts of each holder according to the settlement allocation set.

2. The method for managing fund tags and processing bank acceptance bill transfers according to claim 1, characterized in that, The steps of physically freezing and locking the electronic bank acceptance bill and generating at least one bank acceptance gold tag for the electronic bank acceptance bill in the payment account specifically include: Within the co-managed bank account, the status field of the electronic bank acceptance bill body is set to a frozen and locked state, and the electronic bank acceptance bill body is prohibited from undergoing face value splitting, endorsement transfer or pledge operations within the co-managed bank account. A first bank acceptance gold tag is generated in the payment account for the first holder of the bill after it is issued. The face value of the first bank acceptance gold tag is equal to the face value of the electronic bank acceptance bill itself. Within the payment account, the sum of the face values ​​of all bank acceptance tags corresponding to the same electronic bank acceptance bill body always remains equal to the face value of the bill.

3. The method for managing fund tags and processing bank acceptance bill transfers according to claim 2, characterized in that, The specific steps of inheriting the due date anchor field of the payee's bank acceptance card from the payer's bank acceptance card include: The due date time anchor field of the payer's bank acceptance card is read from the split payment instruction; Write the exact same value as the expiry date time anchor field of the payer's bank acceptance card into the expiry date time anchor field of the payer's bank acceptance card; At any point after the split payment instruction is completed, the due date time anchor field of the payee's bank acceptance label cannot be modified by any of the payer, the payee, the payment account operator, or the co-managing bank account opening bank.

4. The method for managing fund tags and processing bank acceptance bill transfers according to claim 3, characterized in that, The tag state hash fingerprint is constructed by constructing the set of all bank acceptance tags corresponding to the electronic bank acceptance bill body. The specific steps include: All bank acceptance tags corresponding to the electronic bank acceptance bill body are sorted in lexicographical order according to the holder identifier to obtain a sorted tag record sequence. Perform a SHA-256 hash operation on the sorted tag record sequence to obtain the tag state hash fingerprint. ; When the split payment instruction causes a change in the set of bank acceptance tags corresponding to the electronic bank acceptance bill body, the tag status hash fingerprint is recalculated only for the changed set of bank acceptance tags. The hash fingerprint of the tag status of the bank acceptance tag set corresponding to the unchanged electronic bank acceptance bill body. Remain unchanged; hash the tag status fingerprint The sum of the face value of the corresponding silver and gold labels and the hash of the mirror snapshot The face value of the corresponding electronic bank acceptance bill is compared with the face value. If the comparison fails, the reverse write-back correction instruction sends a tag snapshot reset instruction to the payment account.

5. The method for managing fund tags and processing bank acceptance bill transfers according to claim 4, characterized in that, It also includes the supply chain penetration assessment step: Within the statistical period, the hash fingerprint of the tag status corresponding to the electronic bank acceptance bill body is calculated. The number of changes is used to construct a supply chain penetration index, which is equal to the ratio of the number of changes to the statistical period. Based on the aforementioned industry chain penetration index, all bank acceptance gold tags corresponding to the electronic bank acceptance bill body are classified into differentiated risk control levels, including low risk control level, medium risk control level and high risk control level; When the industry chain penetration index exceeds the preset penetration upper limit threshold, the differentiated risk control level of all bank acceptance gold tags corresponding to the electronic bank acceptance bill body is set to the high risk control level, and the manual review process of the split payment instruction of the corresponding payer's bank acceptance gold tag is triggered.

6. The method for managing fund tags and processing bank acceptance bill transfers according to claim 5, characterized in that, The step of aggregating the settlement allocation set by current holder specifically includes: At the time of the expiration date trigger, scan all the bank acceptance gold tags in the payment account whose expiration date time anchor field is equal to the expiration date, and aggregate them by the current holder to obtain the settlement allocation set. The settlement allocation set includes at least one holder record, and each holder record includes the current holder identifier and the face value of the bank acceptance gold tags held by the current holder. After verifying that the debt conservation equation holds, a one-time payment request is initiated to the electronic bank acceptance bill body in the co-managed bank account. The debt conservation equation is that the sum of the face value of all current holders of bank acceptance gold tags in the settlement allocation set is equal to the face value of the electronic bank acceptance bill body. When the debt conservation equation fails, the one-time payment request is blocked and the reverse write-back correction instruction is triggered.

7. The method for managing fund tags and processing bank acceptance bill transfers according to claim 1, characterized in that, This also includes the order placement process for bank acceptance gold trading accounts: The payment account also includes a bank acceptance gold trading account, which is used to record the flow of funds for users' transactions in the bank acceptance gold trading market; When a user initiates a Silver Income Gold Tag order placement request to the Silver Income Gold trading market, the Silver Income Gold Tag will be frozen and transferred from the user's Silver Income Gold account to the Silver Income Gold trading account. During the freeze and transfer period, the Silver Income Gold Tag cannot execute the split payment instruction. When the payment account sends a privacy mode balance SMS to the user's client, the privacy mode balance includes the sum of the balances of the user's cash account, bank-accepted gold account, cash-accepted gold account, and gold-flow account, and the privacy mode balance does not include the fund flow of the bank-accepted gold transaction account.

8. The method for managing fund tags and processing bank acceptance bill transfers according to claim 1, characterized in that, It also includes the instruction feedback steps of the FinanceChain payment system: The Caijinlian payment system, as the upper-level instruction source of the split payment instruction, issues the split payment instruction to the payment account; After executing the split payment instruction, the payment account sends a feedback result of the tag status change to the Caijinlian payment system. The tag status change result includes the amount after the change of the payer's bank acceptance tag, the amount after the change of the payee's bank acceptance tag, the due date time anchor field, and the tag status hash fingerprint. ; The label status change result is written into the operation log after being digitally signed by an elliptic curve before feedback, and the operation log serves as the audit basis for the reverse write-back correction instruction.

9. The method for managing fund tags and processing bank acceptance bill transfers according to claim 2, characterized in that, The step of setting the status field of the electronic bank acceptance bill body to a frozen and locked state within the co-managed bank account specifically includes: The co-managed bank account opening bank receives a physical freeze request submitted by the payment account operator. The physical freeze request carries the bill elements of the electronic bank acceptance bill body and the elliptic curve digital signature of the payment account operator. After the co-managed bank account opening bank verifies the elliptic curve digital signature, it switches the status field of the electronic bank acceptance bill body from the tradable state to the frozen and locked state. The electronic bank acceptance bill body does not respond to any endorsement, discounting, or pledge requests from outside the co-managed bank account opening bank under the frozen and locked state.

10. The method for managing fund tags and processing bank acceptance bill transfers according to claim 4, characterized in that, When there are two or more electronic bank acceptance drafts corresponding to the bank acceptance tag held by the payer, the execution steps of the split payment instruction specifically include: In the split payment instruction, the bank acceptance tokens held by the payer are divided into subsets according to the maturity date anchor field to obtain at least two subsets. All bank acceptance tokens in each subset have the same maturity date anchor field. Within each subset, the label layer operation of deducting the face value of the payer's bank acceptance label and increasing the face value of the payee's bank acceptance label is performed respectively, and the expiration date time anchor field of the bank acceptance label obtained by the payee in each subset is equal to the common expiration date time anchor field of all bank acceptance labels in that subset. After the split payment instruction is completed, the payee simultaneously holds multiple bank acceptance gold tags with different maturity date time anchor fields in the payment account.

Images