Transaction information processing method, apparatus, device, medium, and program product

Abstract

The application provides a transaction information processing method and device of a corporate settlement account, equipment, a storage medium and a program product, which can be applied to the field of financial technology. The method comprises the following steps: pre-associating m card medium data with a corporate settlement account of an enterprise customer, wherein each card medium data comprises a unique card number, a card name, transaction channel authority, display authority, quota control parameters and a corresponding relationship; receiving a payment instruction comprising a target card number; in the case that the target card number matches any one of the unique card numbers under the m card medium data, real-time collection of transaction funds to the corporate settlement account corresponding to the unique card number matched with the target card number according to the payment instruction, and generation of a transaction detail according to the payment instruction, the unique card number matched with the target card number and the card name of the unique card number; and in response to a query request initiated by the enterprise customer, outputting a transaction statement after summarizing the transaction details according to the unique card number and / or the card name.

Description

Technical Field

[0001] This application relates to the field of financial technology, specifically to a method, apparatus, equipment, medium, and program product for processing transaction information of corporate settlement accounts. Background Technology

[0002] In corporate banking settlement transactions, enterprise clients typically need to differentiate payment details from different branches, distributors, or trading partners to achieve refined reconciliation and management of funds. Existing technical solutions mainly employ the following two methods.

[0003] The first approach involves opening multiple independent virtual sub-accounts under the main corporate settlement account, with each sub-account corresponding to a payer. After funds are credited to a sub-account, the sub-account aggregates the funds to the main corporate settlement account, and the system automatically distinguishes the source of funds based on the sub-account affiliation. This approach has the following technical drawbacks: 1. High storage resource consumption: Each sub-account contains independent entries, requiring maintenance of complete account attributes such as account number, account balance, and account status. Each additional payer necessitates the opening of a virtual sub-account, leading to a linear increase in the number of records in the bank's account table, consuming significant database storage space and index resources. 2. High system processing overhead: Opening a virtual sub-account requires a separate account approval process. Each virtual sub-account involves independent account opening transactions, status changes, and account maintenance, involving multiple inter-system interactions and status updates, resulting in multiple database read / write operations. This increases the I / O operations and transaction processing load of electronic devices. 3. Wasted account resources: A large number of virtual sub-accounts occupy system account resources for extended periods despite low usage frequency, causing unnecessary consumption of storage and maintenance costs.

[0004] The second approach involves recording payer information in transaction details or logs using text fields such as business purpose, summary, and remarks, for enterprise clients to manually verify and reconcile accounts. This solution has the following technical drawbacks: 1. Data integrity risk: During cross-system transmission, interface conversion, or log archiving, fields such as purpose, summary, and remarks may experience data truncation, character loss, or encoding errors, leading to irrecoverable loss of payer attribution information. 2. Low classification accuracy: The content of text fields depends on the payer's filling specifications and lacks standardized constraints, making it impossible for the system to automatically achieve high-accuracy classification based on unstructured text. 3. Waste of computational resources: Due to the inability to automatically and accurately classify, enterprise clients need to repeatedly query transaction details, export reports, and perform manual secondary sorting, increasing the database query load and network bandwidth consumption of electronic devices. Furthermore, the repeated queries introduced by manual operations further exacerbate system resource consumption.

[0005] Therefore, how to reduce the system processing load and improve the accuracy and automation of transaction information classification without increasing the storage overhead of virtual accounts has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0006] In view of the above problems, this application provides a method, apparatus, device, medium and program product for corporate settlement account transaction information that can reduce system processing load and improve the accuracy and automation of transaction information classification without increasing virtual account storage overhead.

[0007] According to the first aspect of this application, a method for processing transaction information of a corporate settlement account is provided, comprising: pre-associating m card media data with a corporate customer's corporate settlement account, wherein each card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and a mapping relationship between the unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters, where m is an integer greater than or equal to 1; receiving a payment instruction including a target card number; if the target card number matches any unique card number under the m card media data, real-time aggregating transaction funds to the corporate settlement account corresponding to the unique card number matching the target card number according to the payment instruction, and generating transaction details according to the payment instruction, the unique card number matching the target card number, and the card name of the unique card number; and responding to a query request initiated by the corporate customer, outputting a transaction statement summarizing the transaction details according to the unique card number and / or card name.

[0008] According to an embodiment of this application, the step of pre-associating m card media data with a corporate customer's corporate settlement account includes: generating a transaction agreement in response to the entered protocol configuration parameters for the corporate customer's corporate settlement account, wherein the protocol configuration parameters include account information of the corporate settlement account, the number of receiving accounts m, and transaction rule information; generating m card media data in batches according to the protocol configuration parameters of the transaction agreement, and associating the m card media data with the corporate settlement account.

[0009] According to embodiments of this application, the step of pre-associating m card media data with a corporate customer's corporate settlement account further includes: associating the transaction agreement with the signing branch that entered the agreement configuration parameters. The method for processing transaction information of the corporate settlement account further includes: being able to modify the agreement configuration parameters of the transaction agreement only with the authorization of the signing branch; and being able to modify the m card media data only with the authorization of the signing branch.

[0010] According to an embodiment of this application, the method for processing transaction information of a corporate settlement account further includes: in response to a termination instruction for the transaction agreement, deleting the agreement configuration parameters and retaining the data recovery function within a preset time window; in response to a deletion instruction for the unique card number, deleting the unique card number and the corresponding mapping relationship.

[0011] According to an embodiment of this application, the method for processing transaction information of a corporate settlement account further includes: pre-setting a payment pause button and a pause time period field in batches using a unique card number dimension; in response to triggering the payment pause button and filling the pause time period field, refusing to execute the payment instruction during the pause time period.

[0012] According to embodiments of this application, the protocol configuration parameters further include a hierarchical relationship of m card media, and the mapping relationship of the card media data further includes the hierarchical number of each unique card number in the hierarchical relationship and its superior card number. The transaction information processing method for the corporate settlement account further includes: in response to a hierarchical query request including a superior card number, querying the transaction details of all subordinate card numbers under the superior card number according to the hierarchical relationship.

[0013] The second aspect of this application provides a transaction information processing device for corporate settlement accounts, comprising: an association module, which is used to pre-associate m card media data with corporate customer corporate settlement accounts, wherein each card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and a mapping relationship between the unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters, where m is an integer greater than or equal to 1; a receiving module, which is used to receive a payment instruction including a target card number; a generation module, which is used to, when the target card number matches any unique card number under the m card media data, real-time aggregate transaction funds to the corporate settlement account corresponding to the unique card number matching the target card number, and generate transaction details based on the payment instruction, the unique card number matching the target card number, and the card name of the unique card number; and an output module, which is used to respond to a query request initiated by the corporate customer and output a transaction statement summarizing the transaction details according to the unique card number and / or card name.

[0014] According to a third aspect of this application, an electronic device is provided, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the method described above.

[0015] According to a fourth aspect of this application, a computer-readable storage medium is also provided, on which a computer program or instructions are stored, wherein the computer program or instructions, when executed by a processor, implement the steps of the above-described method.

[0016] According to a fifth aspect of this application, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps of the above-described method.

[0017] According to some embodiments of this application, by pre-associating corporate settlement accounts with m lightweight card media data, and upon receiving a payment instruction, matching the corresponding card media according to the target card number, the funds are aggregated to the same master account in real time, while generating transaction details including card names. Finally, a statement is output summarizing by unique card number or card name. This application addresses the problem of high storage resource consumption in multi-virtual account schemes in the background art by using card media data instead of independent virtual accounts. The card media does not include an independent balance field and shares the master account balance, avoiding the account table data expansion and increased index depth caused by opening a complete account record for each payer, thereby reducing database storage usage. Addressing the problem of high system processing overhead caused by individual account approval in the background art, the card media data in this application does not require individual card approval; it can be used directly after batch association, reducing multiple system interactions and database transaction overhead in the account approval process and improving the processing efficiency of electronic devices. To address the issues of low classification accuracy and the need for manual re-sorting in the background technology that relies on unstructured text fields, this application achieves automated and accurate identification of fund sources by precisely matching unique card numbers and automatically generating transaction details with card names. This eliminates the risk of data loss during cross-system transmission of text fields. Simultaneously, it summarizes and outputs transaction statements by unique card number or card name, allowing enterprise customers to directly obtain classified accounting information without repeated queries and manual verification, reducing the burden of repeated database queries and network bandwidth consumption. Therefore, this application reduces system processing load and improves the accuracy and automation of transaction information classification without increasing virtual account storage overhead. Attached Figure Description

[0018] The above-mentioned contents, other objects, features and advantages of this application will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0019] Figure 1 The illustration schematically depicts an application scenario of a method, apparatus, device, medium, and program product for processing transaction information of a corporate settlement account according to embodiments of this application.

[0020] Figure 2 A flowchart illustrating a method for processing transaction information of a corporate settlement account according to an embodiment of this application is shown.

[0021] Figure 3 The diagram illustrates the structure of a transaction information processing apparatus for a corporate settlement account according to an embodiment of this application.

[0022] Figure 4 A block diagram of an electronic device suitable for implementing a transaction information processing method for corporate settlement accounts, according to an embodiment of this application, is shown schematically. Detailed Implementation

[0023] The embodiments of this application will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of this application. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of this application for ease of explanation. However, it will be apparent that one or more embodiments may be implemented without these specific details. Furthermore, descriptions of well-known structures and technologies are omitted in the following description to avoid unnecessarily obscuring the concepts of this application.

[0024] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this application. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0025] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0026] Figure 1 This diagram illustrates an application scenario of a method for processing transaction information of a corporate settlement account according to an embodiment of this application. Figure 1 As shown, application scenario 100 according to an embodiment of this application may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, and a server 105. The network 104 serves as a medium for providing a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, and the server 105. The network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables. For example, a user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send information, etc.

[0027] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be electronic devices such as smartphones, wearable devices, personal computers, intelligent voice interaction devices, smart home appliances, intelligent vehicles, in-vehicle terminals, aircraft, unmanned vending terminals, and extended reality devices. Extended reality devices can include virtual reality devices, augmented reality devices, and mixed reality devices. A client application for the target application can be installed and run on the terminal devices. This target application can include, but is not limited to, financial transaction applications, payment applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, and social media platform software (these are just examples). Furthermore, this application embodiment does not limit the form of the target application, and it can include, but is not limited to, applications, mini-programs, etc., installed on the terminal devices, and can also be in the form of web pages.

[0028] Server 105 can be a server providing various services, such as a backend management server supporting websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (this is just an example). The backend management server can analyze and process received user requests and other data, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services such as cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks, and basic cloud computing services such as big data. The server can be the backend server of the aforementioned target application, used to provide backend services to the clients of the target application.

[0029] It should be noted that the transaction information processing method for corporate settlement accounts provided in this application embodiment can generally be executed by server 105 and / or first terminal device 101, second terminal device 102, and third terminal device 103. Accordingly, the transaction information processing device for corporate settlement accounts provided in this application embodiment can generally be set in server 105 and / or first terminal device 101, second terminal device 102, and third terminal device 103.

[0030] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0031] Figure 2 A flowchart illustrating a method for processing transaction information of a corporate settlement account according to an embodiment of this application is shown. Figure 2As shown, the transaction information processing method for corporate settlement accounts according to the embodiments of this application may include steps S210 to S240.

[0032] In step S210, m card media data are pre-associated with the corporate customer's corporate settlement account. Each card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and the correspondence between the unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters. m is an integer greater than or equal to 1.

[0033] In some examples, the card medium refers to a virtual or physical bank data carrier associated with a corporate settlement account, used to identify the source or purpose of payment. The card medium in this application does not include a separate balance field; all transaction funds are aggregated to the associated corporate settlement account. The card medium exists in the form of a virtual card number or a physical card, supporting transactions at bank counters, self-service terminals, e-banking, corporate mobile banking, and POS channels.

[0034] In some examples, card media data refers to a set of structured records stored in an electronic device that describe the attributes of a single card. This card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and the relationships between these attributes. The card media data is stored as configuration information in a database table within the bank's system, associated with but not independent of the corporate settlement account records.

[0035] In some examples, a corporate settlement account refers to a master account opened by the banking system for corporate clients to handle fund receipts and payments. This account is the target account for fund aggregation; all funds from payment transactions initiated through card media are ultimately deposited into this account. At the database level, a corporate settlement account is represented as an account record containing core fields such as account number, account balance, and account status.

[0036] In some examples, a unique card number is a unique numerical identifier generated by the banking system for each card, and is not repeated globally within the system. As a primary key field in the card data, the unique card number is used to locate the target card in payment instructions and to mark the source of funds in transaction details. There is a many-to-one mapping relationship between the unique card number and the corporate settlement account.

[0037] In some examples, the card name refers to a textual identifier that a corporate customer sets for each card medium to distinguish different branches, distributors, or trading partners. The card name is linked to a unique card number and displayed to corporate customers in transaction details, statements, and electronic receipts, making it easy for customers to identify the source of payments.

[0038] In some examples, transaction channel permissions refer to a set of Boolean flags set for each card, used to control whether the card is allowed to perform operations such as inquiries, transfers, and cash deposits on different business channels (including counters, self-service terminals, e-banking, corporate mobile banking, and POS channels). When an electronic device receives a payment instruction, it determines whether to allow the transaction based on the transaction channel permission field.

[0039] In some examples, display permissions refer to visibility control flags set for the card name on each card medium. These flags determine whether certain fields in the card medium's data are displayed to corporate clients in transaction details, statements, or electronic receipts. Display permissions are used to prevent legal risks arising from displaying sensitive fields and to support differentiated control over name display for different levels of organizations.

[0040] In some examples, the credit limit control parameters refer to a set of numerical thresholds set for each card, including daily and monthly cumulative limits at the currency level, as well as daily and monthly cumulative limits at the account level. When an electronic device receives a payment instruction, it compares the accumulated transaction amount on that card with the credit limit control parameters to determine whether to reject or allow the transaction.

[0041] In some examples, the mapping relationship refers to the association between a unique card number and a card name, as well as the structured correspondence between a unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters. The mapping relationship is stored as a single record in a database table, allowing electronic devices to retrieve all attribute information of the card medium using the unique card number as the index key.

[0042] As one possible approach, the step of pre-associating m card media data with the corporate customer's corporate settlement account may include a generation operation and an association operation.

[0043] Generation Operation: In response to the entered protocol configuration parameters for the corporate client's corporate settlement account, a transaction agreement is generated. The protocol configuration parameters include the account information of the corporate settlement account, the number of receiving accounts m, and transaction rule information.

[0044] In some examples, protocol configuration parameters refer to a set of structured configuration data entered by the bank system through counter or electronic channels to define the multi-card media management rules under a corporate customer's corporate settlement account. Protocol configuration parameters include at least the account information of the corporate settlement account, the number of receiving accounts (m), and transaction rule information. These parameters serve as input data for generating the transaction protocol and are stored in the bank system's protocol configuration table.

[0045] In some examples, a transaction agreement refers to a persistent data record generated by an electronic device based on entered agreement configuration parameters, representing the agreement between a corporate customer and a bank regarding multi-card media management. At the database level, the transaction agreement is represented as an agreement record, which may include a complete copy of the agreement number, signing time, agreement status, and agreement configuration parameters.

[0046] In some examples, generating a transaction agreement in response to the entered protocol configuration parameters for a corporate client's corporate settlement account means that after the electronic device detects the protocol configuration parameters submitted by a bank teller or corporate client through electronic channels, it triggers a protocol generation process. This process involves format validation, integrity checks, and business rule verification of the protocol configuration parameters. Upon successful verification, a unique protocol number is assigned to the protocol configuration parameter, the signing time is recorded, the protocol status is initialized to valid, and this information is written as a new record to the protocol data table. In this process, the electronic device completes the entire transaction processing from receiving parameters to persistent storage.

[0047] In some examples, the account information for a corporate settlement account refers to the core data set that uniquely identifies a corporate settlement account in the banking system. Account information includes at least the account number, account name, bank identifier, account status, and account balance fields. As part of the protocol configuration parameters, account information is used to specify the primary account associated with the transaction protocol.

[0048] In some examples, the number of receiving accounts, *m*, is an integer value field in the protocol configuration parameters, specifying the number of single card media objects that the electronic device should create when generating card media data. *m* is an integer greater than or equal to 1. The electronic device iteratively calls the card media data generation logic based on the value of *m*, repeating this process *m* times to create *m* card media data records in batches. Once the *m* value is generated in the transaction protocol, it is stored as a fixed parameter at the protocol level, affecting the subsequent batch issuance quantity of card media.

[0049] In some examples, transaction rule information refers to a set of configuration items in the protocol configuration parameters used to define card media generation rules and transaction processing rules. Transaction rule information may include at least batch card media generation rules, default transaction channel permission templates, default credit limit control parameter templates, payment information, extension information, and personalized function switches. When generating card media data in batches, the electronic device uses the default template in the transaction rule information as the initial value, and subsequent personalized overlay configurations can be applied to individual card media. Extension information can be understood as a set of configuration parameters stored in the electronic device used to control the transaction protocol or card media validity extension behavior.

[0050] Association operation: Based on the protocol configuration parameters of the transaction agreement, generate m card media data in batches and associate the m card media data with the corporate settlement account.

[0051] In some examples, generating m card media data in batches according to the protocol configuration parameters of the transaction protocol means: the electronic device reads the protocol configuration parameters stored in the transaction protocol, parses the number of receiving accounts m and the transaction rule information, and performs the card media data record insertion operation m times in a loop within a database transaction. In each loop, the electronic device generates a system-globally unique card number, uses the default transaction channel permissions and default limit control parameters in the transaction rule information as the initial configuration, creates a card name placeholder, and establishes a mapping record between the unique card number and the above configuration items. This batch generation process is completed within a single database transaction, ensuring the atomic creation of m records.

[0052] In some examples, associating m card media data records with a corporate settlement account means that when the electronic device generates each card media data record, it adds a corporate settlement account identifier field to each record. The value of this field comes from the account number of the corporate settlement account in the protocol configuration parameters. After the association is established, all m card media data records associated with that account number can be retrieved, and the associated corporate settlement account can be located through the unique card number of any card media data record. This association is implemented in the form of database foreign key constraints or index associations to ensure data consistency and query efficiency.

[0053] This embodiment further clarifies the steps for associating card media data with corporate settlement accounts. By generating a transaction agreement and creating m card media data entries in batches, the multiple account approvals, authorizations, and database write operations required for opening virtual accounts one by one in existing technologies are merged into a single agreement configuration and batch write transaction. Compared to the scheme of opening virtual accounts independently for each payer, in this embodiment, the card media is stored as a lightweight configuration record and does not include an independent balance field, avoiding the accumulation of a large number of complete account records in the account table, thereby reducing the database storage space occupation and index depth. At the same time, generating m records in a single batch reduces the number of I / O operations of electronic devices and database transaction overhead, significantly improving the system's processing efficiency and response speed in multi-payer scenarios.

[0054] In step S220, a payment instruction including the target card number is received.

[0055] In some examples, the target card number refers to the field value included in the payment instruction that identifies the card medium of the recipient. After parsing the target card number from the payment instruction, the electronic device matches it with the unique card numbers of m stored card medium data to determine the card medium and corporate settlement account corresponding to the payment.

[0056] In some examples, a payment instruction refers to an electronic data packet containing transaction elements initiated by the payer through a business channel. A payment instruction may include at least the target card number, transaction amount, currency, payer account number, and transaction channel identifier. Upon receiving a payment instruction, the electronic device triggers processing steps such as fund collection, transaction detail generation, and account balance updates.

[0057] In step S230, if the target card number matches any unique card number under m card media data, the transaction funds are collected in real time to the corporate settlement account corresponding to the unique card number that matches the target card number according to the payment instruction, and transaction details are generated according to the payment instruction, the unique card number that matches the target card number and the card name of the unique card number.

[0058] In some examples, real-time aggregation of transaction funds to the corporate settlement account corresponding to a unique card number matching the target card number, based on the payment instruction, means that after the electronic device parses the payment instruction to obtain the target card number, it uses that target card number as an index to retrieve the card media data, obtains the associated corporate settlement account identifier, and adds the transaction amount to the balance field of that corporate settlement account. During this process, the funds do not enter the card media's independent balance (because the card media does not have an independent balance), but are directly aggregated to the main account. Real-time aggregation means completing the fund transfer and account balance update within the same transaction processing cycle after receiving the payment instruction.

[0059] In some examples, a transaction detail refers to an immutable, original transaction record generated by an electronic device for each successfully processed payment transaction. A transaction detail may include at least the following fields: transaction serial number, transaction time, target card number, card name, transaction amount, currency, payer account, and transaction status. As the most granular data source, the transaction detail is stored in a transaction detail data table for subsequent querying, summarizing, and reconciliation.

[0060] In some examples, generating transaction details based on payment instructions, a unique card number matching the target card number, and the card name of that unique card number means that after completing the fund collection operation, the electronic device extracts fields such as transaction amount, payer account, and transaction time from the payment instructions, combines them with the unique card number and card name from the card media data, and generates a complete transaction detail record. The card name field in this record comes from the entry corresponding to the unique card number in the lookup table and is used to identify the recipient of the transaction (such as a branch or distributor).

[0061] In step S240, in response to the query request initiated by the enterprise customer, a transaction statement summarizing the transaction details by unique card number and / or card name is output.

[0062] In some examples, a query request refers to an electronic data packet containing query criteria initiated by a corporate customer to the banking system through counter or online banking channels. A query request may at least include a corporate settlement account identifier, a query time range, and optional filtering criteria (such as specifying a unique card number or card name). In response to the query request, the electronic device retrieves records matching the criteria from the transaction details data table.

[0063] In some examples, a transaction statement refers to report data generated by an electronic device based on a transaction details table, aggregated and calculated according to a specified time range and summary dimensions (unique card number and / or card name). A transaction statement includes at least the beginning balance, total revenue categorized by card number or card name, number of transactions, and ending balance. Transaction statements are output to enterprise clients in the form of a structured data table or a formatted file.

[0064] In some examples, outputting a transaction statement summarizing transaction details by unique card number and / or card name means that: In response to a query request from a corporate customer, the electronic device filters transaction records that meet the criteria from the transaction details table, performs aggregation calculations using the unique card number or card name as the grouping key, generates the total transaction amount and number of transactions for each card number or card name, and formats and assembles the aggregation results into a transaction statement data table. This is then presented to the corporate customer via online banking, file download, or printing. Two aggregation modes are supported: single-dimensional (by unique card number only or by card name only) and combined-dimensional (by unique card number first, then by card name).

[0065] The transaction information processing method for corporate settlement accounts according to embodiments of this application pre-associates corporate settlement accounts with m lightweight card media data. Upon receiving a payment instruction, the corresponding card media is matched according to the target card number, and funds are aggregated to the same main account in real time. Simultaneously, transaction details containing card names are generated, and finally, a statement is output summarizing by unique card number or card name. This application addresses the problem of high storage resource consumption in multi-virtual account schemes in the background art by using card media data instead of independent virtual accounts. Card media do not include independent balance fields and share the main account balance, avoiding the data expansion of account tables and increased index depth caused by opening complete account records separately for each payer, thereby reducing database storage usage. Addressing the problem of high system processing overhead caused by individual account approval in the background art, the card media data in this application does not require individual card approval; it can be used directly after batch association, reducing multiple system interactions and database transaction overhead in the account approval process and improving the processing efficiency of electronic devices. To address the issues of low classification accuracy and the need for manual re-sorting in the background technology that relies on unstructured text fields, this application achieves automated and accurate identification of fund sources by precisely matching unique card numbers and automatically generating transaction details with card names. This eliminates the risk of data loss during cross-system transmission of text fields. Simultaneously, it summarizes and outputs transaction statements by unique card number or card name, allowing enterprise customers to directly obtain classified accounting information without repeated queries and manual verification, reducing the burden of repeated database queries and network bandwidth consumption. Therefore, this application reduces system processing load and improves the accuracy and automation of transaction information classification without increasing virtual account storage overhead.

[0066] According to some embodiments of this application, the step of pre-associating m card media data with corporate customer's corporate settlement account may also include a branch association step.

[0067] Branch association steps: Associate the transaction agreement with the contracted branch that has entered the agreement configuration parameters.

[0068] In some examples, associating a transaction agreement with the contracting branch where the configuration parameters are entered means that when the electronic device generates a transaction agreement, it obtains the branch identifier (i.e., the contracting branch ID) to which the current entry operation belongs, and writes this branch identifier as an independent field in the transaction agreement data record. The contracting branch ID, along with the agreement number and the corporate settlement account number, constitutes the core index information of the transaction agreement. After establishing this association, each transaction agreement record has a clearly defined affiliated branch, and subsequent modifications to the agreement configuration parameters require permission verification based on this contracting branch ID.

[0069] The transaction information processing method for corporate settlement accounts may also include a first modification step and a second modification step.

[0070] The first modification step: Only with the authorization of the contracted outlet can the protocol configuration parameters of the transaction agreement be modified.

[0071] The second modification step: Only with the authorization of the contracted outlets can the data of m card media be modified.

[0072] In some examples, the ability to modify the protocol configuration parameters of a transaction agreement, only with the authorization of the contracted branch, means that when the electronic device receives a request to modify the protocol configuration parameters, it extracts the branch ID of the operator carried in the request message and reads the pre-stored contracted branch ID from the target transaction agreement data record. The electronic device compares the operator's branch ID with the contracted branch ID. Modification is only allowed if the two are the same or if a preset hierarchical organizational tree matching relationship exists between the operator's branch ID and the contracted branch ID; otherwise, the electronic device rejects the modification request and returns an insufficient authorization error message.

[0073] In some examples, the ability to modify m card media data only under the authorization of contracted outlets means that when an electronic device receives a modification request for any card media data (including unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, or correspondence relationships), it first performs a reverse lookup of the transaction agreement associated with the unique card number to obtain the contracted outlet ID of that transaction agreement. The electronic device compares the operator's outlet ID with the contracted outlet ID. Modification is only permitted if the two are identical or if a pre-defined hierarchical organizational tree matching relationship exists between the operator's outlet ID and the contracted outlet ID; otherwise, the electronic device rejects the modification request and returns an error message indicating insufficient permissions. This mechanism ensures that the permission to modify card media data is strictly controlled by the contracted outlets, preventing unauthorized outlets from modifying card configurations without authorization.

[0074] This embodiment establishes a data isolation and access control mechanism based on institutional affiliation by associating the transaction agreement with the contracted branch and restricting modification of agreement configuration parameters and card media data to only authorized branch access. This avoids the risk of data tampering caused by unauthorized cross-branch operations and prevents errors in account fund collection or legal risks arising from unauthorized modifications to critical configurations such as card names and permissions. Simultaneously, with the contracted branch acting as the sole authorized node, it reduces data conflicts and consistency maintenance overhead that may arise from concurrent modifications by multiple branches, improving data security, operational traceability, and configuration management efficiency in a distributed institutional environment.

[0075] According to some embodiments of this application, the method for processing transaction information of corporate settlement accounts may further include a first deletion step and a second deletion step.

[0076] First deletion step: In response to the termination instruction of the transaction agreement, delete the agreement configuration parameters and retain the data recovery function within a preset time window.

[0077] Second deletion step: In response to the deletion command for the unique card number, delete the unique card number and its corresponding mapping relationship.

[0078] In some examples, responding to a termination command for a transaction agreement by deleting the protocol configuration parameters and retaining the data recovery function within a preset time window means that after receiving a termination command for a specified transaction agreement, the electronic device obtains the protocol identifier of the transaction agreement, marks the corresponding protocol configuration parameter data record as deleted from the protocol configuration table, or performs a physical deletion operation. Simultaneously, the electronic device writes the deleted protocol configuration parameter data to an archive table or a retention area and starts a timer for a preset time window. Within this preset time window, the electronic device retains the ability to fully recover the protocol configuration parameter data from the archive table or retention area, including restoring the correspondence between the protocol number, contract information, payment information, extension information, and all card media data associated with the agreement. After the preset time window expires, the electronic device automatically clears the corresponding data in the archive table or retention area, releasing storage space.

[0079] In some examples, responding to a deletion command for a unique card number, deleting the unique card number and its corresponding mapping means: after receiving a deletion command for a specified unique card number, the electronic device obtains the unique card number, locates the data record corresponding to the unique card number in the card medium data table, and deletes the unique card number field, card name field, transaction channel permission field, display permission field, credit limit control parameter field, and the mapping between the unique card number and the above fields. When the electronic device performs the deletion operation, it simultaneously clears all associated data with the unique card number as the primary key or foreign key, including historical transaction records of the card medium in the transaction details data table (which are retained for reconciliation and auditing), but the association mapping between the card number and the corporate settlement account is canceled. After the deletion operation is completed, the unique card number can no longer be used to receive new payment instructions, and subsequent payments initiated to this card number will be rejected by the electronic device.

[0080] This embodiment achieves fine-grained data lifecycle management at both the protocol and card levels by deleting protocol configuration parameters and setting a preset data recovery time window in response to termination commands, and deleting specified card numbers and their corresponding relationships in response to deletion commands. This solution releases storage resources while preventing irreversible data loss due to misoperation or business changes through data recovery within the preset time window, thus reducing system maintenance risks. For card-level deletion, only the card number and its corresponding relationship are removed while historical transaction records are retained. This releases storage space occupied by invalid configurations while ensuring the traceability and audit integrity of historical accounts, achieving a technical balance between storage optimization and data security.

[0081] According to some embodiments of this application, the method for processing transaction information of corporate settlement accounts may further include a suspension step.

[0082] Pause Procedure: Pre-set the payment pause button and pause period field in batches using the unique card number dimension. In response to triggering the payment pause button and filling the pause period field, the payment instruction will be refused during the pause period.

[0083] In some examples, a batch configuration interface can be provided to operators. This interface uses a unique card number as the filtering dimension, allowing operators to select one or more card media data records simultaneously and trigger a payment pause button and fill in the pause time period field for the selected records. After receiving the above operations, the electronic device writes each target unique card number and its corresponding pause start time and pause end time as a set of pause rules into the payment pause control table. When the electronic device subsequently receives a payment instruction including the target card number, before executing the payment processing, it first checks whether there is a valid rule in the payment pause control table that matches the target card number and whose current system time is between the pause start time and pause end time. If it exists, the electronic device refuses to execute the payment instruction and returns a payment pause prompt message; if it does not exist, it continues to execute the normal fund collection and transaction detail generation process. This batch setting mechanism allows operators to configure pause rules for multiple card media data at once, eliminating the need to set them individually for each card, reducing the system interaction overhead caused by repetitive operations.

[0084] This embodiment utilizes a batch payment suspension mechanism based on card numbers, enabling electronic devices to automatically reject payment instructions sent to specified card numbers within a preset time period, without requiring manual intervention for each transaction or modification of card media permissions. In certain scenarios, this application can block non-compliant incoming transactions in real time, avoiding the complex transaction processing and data consistency issues arising from the need for reverse reversals after erroneous fund inflows. Simultaneously, the batch setting interface reduces the number of system interactions required for operator card-by-card configuration, lowers the instruction processing load on electronic devices, and achieves refined and automated time-based control of payment entry points, thereby improving system transaction security and operational efficiency.

[0085] According to some embodiments of this application, the protocol configuration parameters may also include the hierarchical relationship of m card media, and the correspondence of card media data may also include the hierarchical number of each unique card number in the hierarchical relationship and its superior card number.

[0086] The transaction information processing method for corporate settlement accounts may also include a query step.

[0087] Query steps: In response to a hierarchical query request including the parent card number, query the transaction details of all subordinate card numbers under the parent card number according to the hierarchical relationship.

[0088] In some examples, when an electronic device receives a hierarchical query request initiated by a business customer or operator, it parses the parent card number field from the query request. Based on the total number of hierarchies preset in the transaction agreement and the hierarchical number and parent card number field corresponding to each unique card number stored in the card media data mapping relationship, the electronic device executes a recursive query algorithm, starting with the parsed parent card number: First, it searches for all card media data records where the parent card number field equals the target parent card number, obtaining the unique card number corresponding to these records as the first-level lower-level card number; then, for each first-level lower-level card number, it continues to search for all card media data records where the parent card number field equals the lower-level card number, obtaining the second-level lower-level card number; this recursive process is repeated until no new lower-level card numbers are found or the preset maximum hierarchical depth is reached. The electronic device collects the unique card numbers of all lower-level card numbers obtained during the recursive query process, forming a lower-level card number set. Then, using all card numbers in this set as filtering conditions, it retrieves transaction detail records from the transaction detail data table and returns the retrieval results as the query response. This recursive query mechanism supports penetrating viewing of fund details across multi-level organizational structures, eliminating the need for enterprise clients to query each level separately and then manually merge the results.

[0089] This embodiment enables electronic devices to recursively query transaction details of all subordinate card numbers based on the superior card number by pre-setting the total number of levels in the protocol and maintaining the level number and superior card number of each card number in the card media mapping relationship. This application maps the multi-level organizational structure of branches, distributors, etc., in real-world business to a hierarchical relationship between card numbers, achieving a penetrating aggregation and display of fund details according to management dimensions. Enterprise customers do not need to query each subordinate card number separately and then manually summarize, reducing the system interaction overhead and network transmission load caused by multiple query requests. Simultaneously, the recursive query is completed by the electronic device at the database level in one go, avoiding multiple I / O operations caused by layer-by-layer queries, reducing query latency, and improving the efficiency of fund reconciliation and data retrieval performance in multi-level organizational scenarios.

[0090] Based on the above-mentioned method for processing transaction information of corporate settlement accounts, this application also provides a device for processing transaction information of corporate settlement accounts. The following will be combined with... Figure 3 The device is described in detail.

[0091] Figure 3 The diagram illustrates the structure of a transaction information processing apparatus for a corporate settlement account according to an embodiment of this application.

[0092] like Figure 3 As shown, the transaction information processing device 10 for corporate settlement accounts includes an association module 1, a receiving module 2, a generating module 3, and an output module 4.

[0093] The association module 1 is used to pre-associate m card media data with corporate customer's corporate settlement account. Each card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and the correspondence between the unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters. m is an integer greater than or equal to 1.

[0094] The receiving module 2 is used to receive payment instructions including the target card number.

[0095] The generation module 3 is used to, in the case that the target card number matches any unique card number under the data of m card media, collect the transaction funds in real time to the corporate settlement account corresponding to the unique card number that matches the target card number according to the payment instruction, and generate transaction details according to the payment instruction, the unique card number that matches the target card number and the card name of the unique card number.

[0096] Output module 4 is used to respond to query requests initiated by enterprise customers and output a transaction statement summarizing transaction details according to unique card number and / or card name.

[0097] According to some embodiments of this application, the association module may include an auxiliary generation unit and an auxiliary association unit.

[0098] Auxiliary generation unit: In response to the entered protocol configuration parameters for the corporate client's corporate settlement account, it generates a transaction protocol, wherein the protocol configuration parameters include the account information of the corporate settlement account, the number of receiving accounts m, and transaction rule information.

[0099] Auxiliary association unit: Based on the protocol configuration parameters of the transaction agreement, generate m card media data in batches and associate the m card media data with the corporate settlement account.

[0100] According to some embodiments of this application, the association module may also include a branch association unit.

[0101] Branch Linkage Unit: Associates the transaction agreement with the contracted branch that has entered the agreement configuration parameters.

[0102] The transaction information processing device for corporate settlement accounts may also include a first modification module and a second modification module.

[0103] The first modification module: It can modify the protocol configuration parameters of the transaction agreement only with the authorization of the contracted outlet.

[0104] The second modification module: can modify the media data of m cards only with the authorization of the contracted outlets.

[0105] According to some embodiments of this application, the transaction information processing device for corporate settlement accounts may further include a first deletion module and a second deletion module.

[0106] First deletion module: In response to the termination command of the transaction agreement, deletes the agreement configuration parameters and retains the data recovery function within a preset time window.

[0107] The second deletion module: In response to the deletion command for a unique card number, deletes the unique card number and its corresponding mapping relationship.

[0108] According to some embodiments of this application, the transaction information processing device for corporate settlement accounts may further include a pause module.

[0109] Pause Module: Pre-set payment pause buttons and pause time periods in batches using unique card numbers. In response to triggering the payment pause button and filling in the pause time period, payment instructions will be refused during the pause period.

[0110] According to some embodiments of this application, the transaction information processing device for corporate settlement accounts may further include a query module.

[0111] Query module: In response to a hierarchical query request including the parent card number, it queries the transaction details of all child cards under the parent card number according to the hierarchical relationship.

[0112] The transaction information processing device for corporate settlement accounts according to embodiments of this application pre-associates corporate settlement accounts with m lightweight card media data. Upon receiving a payment instruction, it matches the corresponding card media according to the target card number and then aggregates the funds to the same main account in real time. Simultaneously, it generates transaction details including card names and finally outputs a statement summarizing by unique card number or card name. This application addresses the problem of high storage resource consumption in multi-virtual account schemes in the background art by using card media data instead of independent virtual accounts. Card media do not include independent balance fields and share the main account balance, avoiding the data expansion and increased index depth of account tables caused by opening complete account records separately for each payer, thereby reducing database storage usage. Addressing the problem of high system processing overhead caused by individual account approval in the background art, the card media data in this application does not require individual card approval; it can be used directly after batch association, reducing multiple system interactions and database transaction overhead in the account approval process and improving the processing efficiency of electronic devices. To address the issues of low classification accuracy and the need for manual re-sorting in the background technology that relies on unstructured text fields, this application achieves automated and accurate identification of fund sources by precisely matching unique card numbers and automatically generating transaction details with card names. This eliminates the risk of data loss during cross-system transmission of text fields. Simultaneously, it summarizes and outputs transaction statements by unique card number or card name, allowing enterprise customers to directly obtain classified accounting information without repeated queries and manual verification, reducing the burden of repeated database queries and network bandwidth consumption. Therefore, this application reduces system processing load and improves the accuracy and automation of transaction information classification without increasing virtual account storage overhead.

[0113] According to embodiments of this application, any plurality of modules among the association module 1, receiving module 2, generating module 3, and output module 4 can be combined into one module, or any one of these modules can be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules can be combined with at least part of the functionality of other modules and implemented in one module. According to embodiments of this application, at least one of the association module 1, receiving module 2, generating module 3, and output module 4 can be at least partially implemented as hardware circuitry, such as field-programmable gate arrays, programmable logic arrays, systems-on-a-chip, systems-on-a-substrate, systems-on-package, application-specific integrated circuits, or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the association module 1, receiving module 2, generating module 3, and output module 4 can be at least partially implemented as a computer program module, which can perform corresponding functions when the computer program module is run.

[0114] Figure 4A block diagram schematically illustrates an electronic device suitable for implementing the above-described method according to an embodiment of this application.

[0115] like Figure 4 As shown, an electronic device 900 according to an embodiment of this application includes a processor 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory 902 or a program loaded from a storage portion 908 into a random access memory 903. The processor 901 may include, for example, a general-purpose microprocessor, an instruction set processor and / or an associated chipset and / or a dedicated microprocessor. The processor 901 may also include onboard memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for executing different steps of the method flow according to an embodiment of this application.

[0116] Random access memory 903 stores various programs and data required for the operation of electronic device 900. Processor 901, read-only memory 902, and random access memory 903 are interconnected via bus 904. Processor 901 executes various steps of the method flow according to embodiments of this application by executing programs stored in read-only memory 902 and / or random access memory 903. It should be noted that the programs may also be stored in one or more memories other than read-only memory 902 and random access memory 903. Processor 901 may also execute various steps of the method flow according to embodiments of this application by executing programs stored in said one or more memories.

[0117] According to embodiments of this application, the electronic device 900 may further include an input / output interface 905, which is also connected to a bus 904. The electronic device 900 may also include one or more of the following components connected to the input / output interface 905: an input section 906 including a keyboard, mouse, etc.; an output section 907 including a cathode ray tube, liquid crystal display, etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card, such as a local area network card, modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output interface 905 as needed. A removable medium 911, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 910 as needed so that computer programs read from it can be installed into the storage section 908 as needed.

[0118] Embodiments of this application also provide a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs, which, when executed, implement the method according to the embodiments of this application.

[0119] According to embodiments of this application, the computer-readable storage medium can be a non-volatile computer-readable storage medium, such as including but not limited to: portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination thereof. In embodiments of this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this application, the computer-readable storage medium may include the read-only memory 902 described above, and / or random access memory 903, and / or one or more memories other than read-only memory 902 and random access memory 903.

[0120] Embodiments of this application also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this application.

[0121] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 909, and / or installed from a removable medium 911. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0122] In embodiments of this application, the computer program can be downloaded and installed from a network via communication section 909, and / or installed from removable medium 911. When the computer program is executed by processor 901, it performs the functions defined in the system of embodiments of this application. According to embodiments of this application, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0123] According to embodiments of this application, program code for executing the computer programs provided in the embodiments of this application can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. The program code can be executed entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0124] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0125] Those skilled in the art will understand that the features described in the various embodiments of this application can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in this application. In particular, the features described in the various embodiments of this application can be combined and / or combined in various ways without departing from the spirit and teachings of this application. All such combinations and / or combinations fall within the scope of this application.

Claims

1. A method for processing transaction information of a corporate settlement account, characterized in that, include: m card media data are pre-associated with corporate clients' corporate settlement accounts. Each card media data includes a unique card number, card name, transaction channel permissions, display permissions, credit limit control parameters, and a mapping relationship between the unique card number, card name, transaction channel permissions, display permissions, and credit limit control parameters. m is an integer greater than or equal to 1. Receive payment instructions including the target card number; If the target card number matches any unique card number under the m card medium data, the transaction funds are collected in real time to the corporate settlement account corresponding to the unique card number that matches the target card number according to the payment instruction, and transaction details are generated according to the payment instruction, the unique card number that matches the target card number and the card name of the unique card number; In response to the query request initiated by the enterprise customer, output a transaction statement summarizing the transaction details according to the unique card number and / or card name.

2. The method for processing transaction information of a corporate settlement account according to claim 1, characterized in that, The steps for pre-linking m card media data with corporate clients' corporate settlement accounts include: In response to the entered protocol configuration parameters for the corporate customer's corporate settlement account, a transaction agreement is generated, wherein the protocol configuration parameters include the account information of the corporate settlement account, the number of receiving accounts m, and transaction rule information; Based on the protocol configuration parameters of the transaction agreement, generate m card media data in batches, and associate the m card media data with the corporate settlement account.

3. The method for processing transaction information of corporate settlement accounts according to claim 2, characterized in that, The step of pre-linking m card media data with the corporate customer's corporate settlement account also includes: Associate the transaction agreement with the contracting outlets that have entered the agreement configuration parameters. The method for processing transaction information in corporate settlement accounts also includes: The protocol configuration parameters of the transaction agreement can only be modified with the authorization of the contracted outlet; The data of the m cards can only be modified with the authorization of the contracted outlets.

4. The method for processing transaction information of corporate settlement accounts according to claim 1, characterized in that, Also includes: In response to the termination command of the transaction protocol, the protocol configuration parameters are deleted, and the data recovery function is retained within a preset time window; In response to the deletion command for the unique card number, the unique card number and the corresponding mapping relationship are deleted.

5. The method for processing transaction information of a corporate settlement account according to claim 1, characterized in that, Also includes: A payment pause button and a pause time period field are pre-set in batches using a unique card number. In response to triggering the payment pause button and filling the pause time period field, the payment instruction is refused to be executed during the pause period.

6. The method for processing transaction information of a corporate settlement account according to claim 2, characterized in that, The protocol configuration parameters also include the hierarchical relationship of m card media, and the mapping relationship of the card media data also includes the hierarchical number of each unique card number in the hierarchical relationship and its parent card number. The method for processing transaction information of corporate settlement accounts further includes: in response to a hierarchical query request including a superior card number, querying the transaction details of all subordinate card numbers under the superior card number according to the hierarchical relationship.

7. A transaction information processing device for a corporate settlement account, characterized in that, include: The association module is used to pre-associate m card media data with corporate customer's corporate settlement account. Each card media data includes a unique card number, card name, transaction channel permission, display permission, credit limit control parameter, and the correspondence between the unique card number, card name, transaction channel permission, display permission, and credit limit control parameter. m is an integer greater than or equal to 1. A receiving module, the receiving module being used to receive a payment instruction including a target card number; The generation module is used to, when the target card number matches any unique card number under the m card medium data, collect the transaction funds in real time to the corporate settlement account corresponding to the unique card number that matches the target card number according to the payment instruction, and generate transaction details according to the payment instruction, the unique card number that matches the target card number and the card name of the unique card number; The output module is used to respond to the query request initiated by the enterprise customer and output a transaction statement summarizing the transaction details according to the unique card number and / or card name.

8. An electronic device, comprising: One or more processors; Memory, used to store one or more computer programs. The characteristic feature is that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 6.

Images