Accounting result generation method, device, equipment and computer readable storage medium
By obtaining transaction orders from the trading platform and combining them with the prefix, type, and amount of the merchant's order number, the transaction environment can be accurately determined. This solves the problem of low reconciliation efficiency and accuracy under multi-environment deployment and enables the generation of efficient and accurate reconciliation results.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- AVATR CO LTD
- Filing Date
- 2026-02-24
- Publication Date
- 2026-06-02
AI Technical Summary
Traditional reconciliation systems are less efficient and accurate when deployed in multiple environments, especially when the test and production environments share the same transaction environment, leading to frequent one-sided accounting issues.
By obtaining transaction orders from the trading platform, and combining the prefix, type, and transaction amount of the merchant's order number, the transaction environment can be determined. Based on the transaction environment and the transaction number, reconciliation results can be generated to avoid confusion of transaction data.
This improved the accuracy and efficiency of reconciliation, reduced the occurrence of one-sided accounts, and ensured the accuracy and consistency of reconciliation results.
Smart Images
Figure CN122134482A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of reconciliation technology, specifically to a method, apparatus, device, and computer-readable storage medium for generating reconciliation results. Background Technology
[0002] As transaction systems become increasingly complex, multi-environment deployments, including development, testing, and production, have become commonplace. However, traditional reconciliation systems only support a single production environment. When the testing and production environments share the same transaction environment, simulated transactions in the testing environment are recorded in the production environment, leading to one-sided accounting entries such as "debits without credits" or "credits without debits." For example, during joint testing on a transaction platform, testers initiated 100 transactions through a simulated payment interface. Due to environment confusion, 30 of these transactions were recorded in the production environment, resulting in 30 one-sided accounting entries that required manual correction. Traditional solutions, relying on static configurations (such as IP restrictions) or manual verification during reconciliation, suffer from incomplete isolation and low efficiency. Summary of the Invention
[0003] In view of the above problems, embodiments of the present invention provide a method, apparatus, device and computer-readable storage medium for generating reconciliation results, which are used to solve the problem of low reconciliation efficiency and accuracy in the case of multi-environment deployment of trading platforms in the prior art.
[0004] According to one aspect of the present invention, a method for generating reconciliation results is provided, the method comprising:
[0005] Obtain the transaction order generated by the transaction platform based on the transaction request issued by the merchant. The transaction order includes: merchant order number, transaction amount, and transaction serial number. The transaction environment is determined based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount, wherein the prefix is determined based on the generation environment of the merchant order number; Reconciliation results are generated based on the transaction environment and the transaction serial number.
[0006] According to another aspect of the present invention, an apparatus for generating reconciliation results is provided, comprising: The transaction order acquisition module is used to acquire transaction transaction orders generated by the transaction platform based on transaction requests issued by merchants. The transaction transaction order includes: merchant order number, transaction amount, and transaction serial number. The environment determination module is used to determine the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount; The reconciliation result generation module is used to generate reconciliation results based on the transaction environment and the transaction serial number.
[0007] According to another aspect of the present invention, a reconciliation result generation device is provided, comprising: a processor, a memory, a communication interface, and a communication bus, wherein the processor, the memory, and the communication interface communicate with each other through the communication bus; The memory is used to store at least one executable instruction that causes the processor to perform the operation of the reconciliation result generation method described above.
[0008] According to another aspect of the present invention, a computer-readable storage medium is provided, the storage medium storing at least one executable instruction, the executable instruction causing a reconciliation result generating device / apparatus to perform the operation of the reconciliation result generating method described above.
[0009] This invention, in its embodiments, obtains transaction orders generated by a trading platform based on transaction requests issued by merchants. These transaction orders include: merchant order number, transaction amount, and transaction serial number. Then, it determines the transaction environment based on the prefix, type, and transaction amount of the merchant order number. Finally, it generates reconciliation results based on the transaction environment and transaction serial number. This invention first obtains the transaction orders returned by the trading platform based on transaction requests, then determines the transaction environment based on the prefix, type, and transaction amount of the merchant order number. This combined design of the order number prefix, order number type, and amount mechanisms accurately determines the transaction environment corresponding to the transaction request, and then generates reconciliation results based on the transaction environment and transaction serial number. This avoids transaction data confusion and improves reconciliation efficiency and accuracy.
[0010] The above description is merely an overview of the technical solutions of the embodiments of the present invention. In order to better understand the technical means of the embodiments of the present invention and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description
[0011] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This invention illustrates a flowchart of a first embodiment of the reconciliation result generation method provided by the present invention. Figure 2 A flowchart illustrating a second embodiment of the reconciliation result generation method provided by the present invention is shown. Figure 3 A flowchart illustrating a third embodiment of the reconciliation result generation method provided by the present invention is shown; Figure 4 This diagram illustrates the overall process of an embodiment of the reconciliation result generation method provided by the present invention. Figure 5 This invention shows a schematic diagram of the structure of a first embodiment of the reconciliation result generation device provided by the present invention; Figure 6 A schematic diagram of an embodiment of the reconciliation result generation device provided by the present invention is shown. Detailed Implementation
[0012] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be implemented in various forms and should not be limited to the embodiments set forth herein.
[0013] Figure 1 A flowchart illustrating a first embodiment of the reconciliation result generation method provided by the present invention is shown. This method is executed by a reconciliation result generation device. Figure 1 As shown, the method includes the following steps: Step 10: Obtain the transaction order generated by the transaction platform based on the transaction request issued by the merchant. The transaction order includes: merchant order number, transaction amount, and transaction serial number.
[0014] In this scenario, the transaction platform can be a financial institution, such as a bank. The bank only has a production environment, while the merchant has four environments: development, testing, acceptance, and production. A transfer request from account A to account B originates in the testing environment. This request, through the testing environment's application, calls the real bank's production interface and enters the bank's core production system. The bank's core system cannot distinguish between a test request and a production request; it will execute the transaction, deducting funds from the debit side of the real account A and crediting funds to the credit side of the real account B. If account A is a real, test-driven account with low balance (e.g., a small balance), while account B is a production account, then this transfer appears complete and balanced on the bank's ledger. However, in the production environment's business system, there is no record of this transaction because it originated in the testing environment. For example, if the merchant's production system has 100 transactions and the testing environment has 10, the transaction platform's transaction records will have 110 entries. Matching the bank's production environment reconciliation statement with the merchant's production environment payment records will result in 100 balanced entries and 10 one-sided entries on the bank's side, creating a one-sided accounting risk.
[0015] In one implementation, after a merchant sends a transaction request, the bank generates a transaction link. The merchant clicks the link and completes the transaction through a third-party payment platform. Upon successful payment, the bank sends a callback notification containing the generated transaction order, which includes the merchant's order number, transaction amount, and transaction serial number. If the payment transaction fails, no corresponding invoice is generated.
[0016] Step 20: Determine the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount. The prefix is determined based on the generation environment of the merchant order number.
[0017] Merchants may exist in four environments: development, testing, acceptance, and production. For each environment, a prefix can be added via environment variables. This prefix is determined based on the environment in which the merchant order number was generated. For example, a unique environment prefix (e.g., TEST_) is added to merchant order numbers generated in the testing environment, a production prefix (e.g., PROD_) is added to merchant order numbers generated in the production environment, and a development prefix (e.g., UAT_) is added to merchant order numbers generated in the development environment. Specifically, in the testing environment, when interacting with the bank, the merchant order number field format is TEST_order sequence number (e.g., TEST_transaction number); in the production environment, the merchant order number field format is PROD_order sequence number (e.g., PROD_transaction number); and in the development environment, the merchant order number field format is UAT_order sequence number (e.g., UAT_transaction number).
[0018] In one implementation, the merchant order number can be either a blacklist or a whitelist type. Merchant order numbers generated in the test environment during historical periods can be exported to a blacklist. If a merchant order number requiring reconciliation is in this blacklist, it indicates that the order number is blacklisted; if it is not, it indicates that it is whitelisted. In a non-production environment, such as a test environment, after a transaction is completed, the merchant order number is synchronously exported and updated to the blacklist. In a production environment, when generating a reconciliation statement, the blacklist is queried; if the merchant order number exists, it is marked as a test transaction. This embodiment can also update the blacklist in real time, using real-time synchronization or scheduled batch updates to ensure the timeliness of the blacklist data.
[0019] In one implementation, the transaction amount can be the amount corresponding to the transaction request, i.e., the payment amount.
[0020] Step 30: Generate reconciliation results based on the transaction environment and the transaction serial number.
[0021] In one implementation, reconciliation results can be generated based on the transaction environment and transaction serial number. All bills for the day can be obtained the next day. For each bill, the corresponding transaction environment and transaction serial number can be determined. When the transaction environment is a production environment, reconciliation results are generated based on the transaction serial number. The reconciliation results may include incorrect accounts, reconciled accounts, and accounts with one side.
[0022] As can be seen from the above, the reconciliation result generation method provided in this embodiment of the invention obtains the transaction business order generated by the transaction platform based on the transaction request issued by the merchant. The transaction business order includes: merchant order number, transaction amount, and transaction serial number. Then, the transaction environment is determined based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount. Finally, the reconciliation result is generated based on the transaction environment and the transaction serial number. This embodiment of the invention first obtains the transaction business order returned by the transaction platform based on the transaction request, and then determines the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount. Thus, by combining the collaborative design of the three mechanisms of order number prefix, order number type, and amount, the transaction environment corresponding to the transaction request is accurately determined. Then, the reconciliation result is generated based on the transaction environment and the transaction serial number, avoiding transaction data confusion and improving reconciliation efficiency and accuracy.
[0023] Figure 2 A flowchart illustrating a second embodiment of the reconciliation result generation method provided by the present invention is shown. This method is executed by a reconciliation result generation device. Figure 2 As shown, step 20 includes the following steps: Step 201: Determine whether the merchant's order number has a prefix.
[0024] Once the reconciliation process begins, the system can periodically retrieve the previous day's transaction records from the trading platform. For example, if the records are not retrieved by 10:00 AM, they can be retrieved again at 11:00 AM, and so on, until the previous day's transaction records are retrieved.
[0025] In one implementation, each time a merchant initiates a transaction request, they need to call the bank's order placement interface and pass in the merchant order number. After the merchant order number is generated, environment variables are appended, i.e., the corresponding environment prefix is appended, such as PROD_, TEST_, etc. There may be some scenarios, such as when bills in the test environment are manually deleted or have not yet been synchronized to the production environment, which may result in a mismatch. In such cases, the prefix may be lost. Therefore, this embodiment can determine whether the merchant order number has a prefix.
[0026] Step 202: If yes, then match the prefix of the merchant order number with the preset prefix, and determine the transaction environment based on the matching result.
[0027] If the merchant order number has a prefix, it is matched against a preset prefix. The preset prefix can include prefixes corresponding to the production environment and prefixes corresponding to non-production environments. Non-production environments refer to environments other than the production environment, such as testing, acceptance, and development environments. After matching the prefix of the merchant order number with the above two types of preset prefixes, the transaction environment can be determined based on the matching results. Accordingly, the transaction environment can also include production and non-production environments.
[0028] In one optional approach, matching the prefix of the merchant order number with a preset prefix and determining the transaction environment based on the matching result includes: determining the transaction environment as a production environment if the prefix of the merchant order number matches the production prefix corresponding to the production environment in the preset prefix; and determining the transaction environment as a non-production environment if the prefix of the merchant order number matches the non-production prefix corresponding to the non-production environment in the preset prefix.
[0029] The preset prefix can include the production prefix corresponding to the production environment and the non-production prefix corresponding to the non-production environment. The production prefix can be PROD_, and the non-production prefix can include TEST_, UAT_, etc.
[0030] In one implementation, if the prefix of the merchant order number matches the production prefix, the transaction environment can be determined to be a production environment; if the prefix of the merchant order number matches the non-production prefix, the transaction environment can be determined to be a non-production environment.
[0031] Step 203: If not, determine the transaction environment based on the type of the merchant order number and the transaction amount.
[0032] In one implementation, if the prefix of the merchant order number is lost, the transaction environment can be determined based on the type of the merchant order number and the transaction amount. That is, the transaction environment is determined by whether the order number is in the blacklist corresponding to the test environment and the transaction amount.
[0033] In one optional approach, determining the transaction environment based on the type of the merchant order number and the transaction amount includes: determining whether the merchant order number is in a preset blacklist list, and determining the type of the merchant order number based on the determination result, wherein the preset blacklist list includes order numbers corresponding to non-production environments; if the type of the merchant order number is a non-production type, determining the transaction environment as a non-production environment; if the type of the merchant order number is a production type, determining the transaction environment based on the transaction amount.
[0034] The preset blacklist refers to a pre-set list that includes merchant order numbers corresponding to non-production environments, namely the order numbers corresponding to testing, acceptance, and development environments.
[0035] In one implementation, it can be determined whether the order number is in a preset blacklist. If so, the merchant order number is determined to be of a non-production type; otherwise, the merchant order number is determined to be of a production type.
[0036] In one implementation, if the merchant order number is of a non-production type, the transaction environment can be determined to be a non-production environment, which may be a test environment, an acceptance environment, or a development environment; if the merchant order number is of a production type, the transaction environment can be determined based on the transaction amount of each bill.
[0037] In one optional approach, determining the transaction environment based on the transaction amount includes: if the transaction amount is greater than or equal to a preset amount, then determining the transaction environment as a production environment; if the transaction amount is less than the preset amount, then determining the transaction environment as a suspected test environment.
[0038] In practice, transaction amounts in a production environment are usually higher than those in a non-production environment. Therefore, the transaction amount can be compared with a preset amount, and the transaction environment can be determined based on the comparison results.
[0039] In one implementation, the preset amount can be set to 100, 200, etc. If the transaction amount is greater than or equal to the preset amount, the transaction environment is determined to be a production environment; if the transaction amount is less than the preset amount, the transaction environment is determined to be a suspected test environment, that is, it may be a test environment or a production environment.
[0040] As can be seen from the above, in the reconciliation result generation method provided in this embodiment of the invention, the method determines whether the merchant order number has a prefix. If so, the prefix of the merchant order number is matched with a preset prefix, and the transaction environment is determined based on the matching result. If not, the transaction environment is determined based on the type of the merchant order number and the transaction amount. This embodiment of the invention, by determining whether the merchant order number has a prefix and determining the transaction environment based on the determination result, can accurately determine the transaction environment of each invoice.
[0041] Figure 3 A flowchart illustrating a third embodiment of the reconciliation result generation method provided by the present invention is shown. This method is executed by a reconciliation result generation device. Figure 3 As shown, step 30 includes the following steps: Step 301: Obtain the business transaction number corresponding to the transaction request issued by the merchant.
[0042] In one implementation, the merchant's transaction number corresponding to the transaction request issued by the merchant can be obtained, that is, the merchant's transaction number recorded internally by the merchant, which may include the merchant's order number, transaction number, etc.
[0043] Step 302: If the transaction environment is a production environment or a suspected test environment, match the merchant serial number with the transaction serial number, and generate a reconciliation result based on the matching result.
[0044] In one implementation, when the transaction environment is a production environment or a suspected test environment, the merchant's internal transaction number can be matched with the transaction number recorded on the transaction platform, and a reconciliation result can be generated based on the matching result.
[0045] In one optional approach, matching the merchant transaction number with the transaction transaction number and generating a reconciliation result based on the matching result includes: if the merchant transaction number and the merchant order number in the transaction transaction number are equal but the transaction amount is not equal, then the reconciliation result is determined to be an error; if the merchant transaction number and the merchant order number in the transaction transaction number are equal and the transaction amount is equal, then the reconciliation result is determined to be balanced; if the merchant order number in the merchant transaction number or the transaction order number in the transaction transaction number is missing, then the reconciliation result is determined to be a one-sided account.
[0046] In one implementation, if the merchant order number corresponding to the merchant transaction number is equal to the merchant order number corresponding to the transaction transaction number, but the transaction amount corresponding to the merchant transaction number is not equal to the transaction amount corresponding to the transaction transaction number, then the reconciliation result is determined to be an error; if the merchant order number corresponding to the merchant transaction number is equal to the merchant order number corresponding to the transaction transaction number, and the transaction amount corresponding to the merchant transaction number is equal to the transaction amount corresponding to the transaction transaction number, then the reconciliation result is determined to be balanced; if the merchant order number corresponding to the merchant transaction number or the transaction order number corresponding to the transaction transaction number is missing, then the reconciliation result is determined to be a one-sided account.
[0047] In one embodiment, a reconciliation result report can be generated based on the above reconciliation results. If the transaction environment is a suspected test environment, the generated reconciliation results can be manually confirmed to improve the accuracy of the generated billing results.
[0048] In one implementation, Figure 4 This diagram illustrates the overall process of an embodiment of the reconciliation result generation method provided by the present invention. Figure 4As shown, after reconciliation begins, if the daily reconciliation is not generated, it can be retrieved from the bank. If no reconciliation file is generated, it indicates that the reconciliation is complete and awaits the next reconciliation task. If the reconciliation file is generated, the prefix of the business order can be determined. If it matches the test prefix, the corresponding order's transaction environment is marked as the test environment and will not participate in the reconciliation; only the result is recorded. If it matches the production prefix, the corresponding order's transaction environment is marked as the production environment. If the prefix is missing, the test environment can be matched. If the test environment is not imported or the matching fails, the amount is matched. Specifically, the merchant order number can be compared with a preset blacklist. If it is in the list, it indicates... If a match is successful, the corresponding order's transaction environment is marked as a test environment. If it is not in the list, the match fails, and the transaction amount is matched. If the transaction amount is ≥100, the corresponding order's transaction environment is marked as a production environment. If the transaction amount is <100, the corresponding order's transaction environment is marked as a suspected test environment. In this case, the merchant order number and the third-party transaction number can be matched. If the merchant order numbers are the same but the amounts are different, the reconciliation result is an error. If the merchant order numbers are the same and the amounts are the same, the reconciliation result is balanced. If either the bank or merchant order number is missing, the reconciliation result is a one-sided account.
[0049] As can be seen from the above, in the reconciliation result generation method provided by the embodiments of the present invention, by obtaining the business transaction number corresponding to the transaction request issued by the merchant, and matching the merchant transaction number with the transaction transaction number in the case of a production environment or a suspected test environment, a reconciliation result is generated based on the matching result. The embodiments of the present invention, by matching the merchant transaction number with the transaction transaction number in the case of a production environment or a suspected test environment, enable reconciliation to be performed only in a production environment, thereby improving reconciliation efficiency.
[0050] Figure 5 A schematic diagram of an embodiment of the reconciliation result generation device of the present invention is shown. Figure 5 As shown, the device 500 includes: a business order acquisition module 510, an environment determination module 520, and a reconciliation result generation module 530.
[0051] The transaction order acquisition module 510 is used to acquire transaction transaction orders generated by the transaction platform based on transaction requests issued by merchants. The transaction transaction order includes: merchant order number, transaction amount, and transaction serial number. The environment determination module 520 is used to determine the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount, wherein the prefix is determined based on the generation environment of the merchant order number; The reconciliation result generation module 530 is used to generate reconciliation results based on the transaction environment and the transaction serial number.
[0052] In one optional approach, the environment determination module 520 is further configured to determine whether the merchant order number has a prefix; if so, the prefix of the merchant order number is matched with a preset prefix, and the transaction environment is determined based on the matching result; if not, the transaction environment is determined based on the type of the merchant order number and the transaction amount.
[0053] In an alternative embodiment, the environment determination module 520 is further configured to determine the transaction environment as a production environment if the prefix of the merchant order number matches the production prefix corresponding to the production environment in the preset prefix; and to determine the transaction environment as a non-production environment if the prefix of the merchant order number matches the non-production prefix corresponding to the non-production environment in the preset prefix.
[0054] In an optional manner, the environment determination module 520 is further configured to determine whether the merchant order number is in a preset blacklist list, and determine the type of the merchant order number based on the determination result, wherein the preset blacklist list includes order numbers corresponding to non-production environments; if the type of the merchant order number is a non-production type, the transaction environment is determined to be a non-production environment; if the type of the merchant order number is a production type, the transaction environment is determined based on the transaction amount.
[0055] In one alternative approach, the environment determination module 520 is further configured to determine the transaction environment as a production environment if the transaction amount is greater than or equal to a preset amount; and to determine the transaction environment as a suspected test environment if the transaction amount is less than the preset amount.
[0056] In one optional approach, the reconciliation result generation module 530 is further configured to obtain the business transaction number corresponding to the transaction request issued by the merchant; if the transaction environment is a production environment or a suspected test environment, the merchant transaction number is matched with the transaction transaction number, and a reconciliation result is generated based on the matching result.
[0057] In one optional manner, the reconciliation result generation module 530 is further configured to determine the reconciliation result as an error if the merchant transaction number is equal to the merchant order number in the transaction transaction number but the transaction amount is not equal; if the merchant transaction number is equal to the merchant order number in the transaction transaction number and the transaction amount is equal, the reconciliation result is determined to be balanced; if the merchant order number in the merchant transaction number or the transaction order number in the transaction transaction number is missing, the reconciliation result is determined to be a one-sided account.
[0058] The reconciliation result generation device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0059] Figure 6The diagram shows a structural schematic of an embodiment of the reconciliation result generation device of the present invention. The specific embodiments of the present invention do not limit the specific implementation of the reconciliation result generation device.
[0060] like Figure 6 As shown, the reconciliation result generating device may include: a processor 603, a communications interface 604, a memory 606, and a communications bus 608.
[0061] The processor 603, communication interface 604, and memory 606 communicate with each other via communication bus 608. Communication interface 604 is used to communicate with other network elements, such as clients or other servers. The processor 603 executes program 610, specifically performing the relevant steps described in the embodiment of the reconciliation result generation method.
[0062] Specifically, program 610 may include program code, which includes computer-executable instructions.
[0063] Processor 603 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The reconciliation result generation device includes one or more processors, which may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.
[0064] Memory 606 is used to store program 610. Memory 606 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.
[0065] Specifically, program 610 can be called by processor 603 to cause the reconciliation result generating device to execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0066] This invention provides a computer-readable storage medium storing at least one executable instruction that, when executed on a reconciliation result generation device / app, causes the reconciliation result generation device / app to perform the reconciliation result generation method in any of the above method embodiments.
[0067] The executable instructions can be used to cause the reconciliation result generating device / app to execute the method provided in the above method embodiment. The implementation principle and technical effect are similar, and will not be described in detail here.
[0068] Furthermore, all information to be extracted in this application was obtained with the user's permission or consent; that is, when this application is applied to a specific product or technology, user permission is required to obtain and process the relevant data, and the processing of the relevant data must comply with the relevant laws, regulations and regulatory standards of the relevant countries and regions.
[0069] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Furthermore, the embodiments of this invention are not directed to any particular programming language.
[0070] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. Similarly, for the sake of brevity and to aid in understanding one or more aspects of the invention, in the description of exemplary embodiments of the invention above, various features of the embodiments are sometimes grouped together in a single embodiment, figure, or description thereof. The claims, which follow the detailed description, are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.
[0071] Those skilled in the art will understand that the modules in the device of the embodiment can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiment can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components, except that at least some of such features and / or processes or units are mutually exclusive.
[0072] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.
Claims
1. A method for generating reconciliation results, characterized in that, The method includes: Obtain the transaction order generated by the transaction platform based on the transaction request issued by the merchant. The transaction order includes: merchant order number, transaction amount, and transaction serial number. The transaction environment is determined based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount, wherein the prefix is determined based on the generation environment of the merchant order number; Reconciliation results are generated based on the transaction environment and the transaction serial number.
2. The method according to claim 1, characterized in that, The step of determining the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount includes: Determine if the merchant's order number has a prefix; If so, the prefix of the merchant's order number is matched with a preset prefix, and the transaction environment is determined based on the matching result; If not, the transaction environment is determined based on the type of the merchant order number and the transaction amount.
3. The method according to claim 2, characterized in that, The step of matching the prefix of the merchant's order number with a preset prefix and determining the transaction environment based on the matching result includes: If the prefix of the merchant's order number matches the production prefix corresponding to the production environment in the preset prefix, the transaction environment is determined to be the production environment; If the prefix of the merchant's order number matches the non-production prefix corresponding to the non-production environment in the preset prefix, the transaction environment is determined to be a non-production environment.
4. The method according to claim 2, characterized in that, The step of determining the transaction environment based on the type of the merchant order number and the transaction amount includes: Determine whether the merchant order number is in a preset blacklist, and determine the type of the merchant order number based on the determination result. The preset blacklist includes order numbers corresponding to non-production environments. If the merchant order number is of a non-production type, the transaction environment is determined to be a non-production environment; If the merchant order number is of the production type, the transaction environment is determined based on the transaction amount.
5. The method according to claim 4, characterized in that, The step of determining the transaction environment based on the transaction amount includes: If the transaction amount is greater than or equal to the preset amount, the transaction environment is determined to be a production environment; If the transaction amount is less than the preset amount, the transaction environment is determined to be a suspected test environment.
6. The method according to any one of claims 1 to 5, characterized in that, The process of generating reconciliation results based on the transaction environment and the transaction serial number includes: Obtain the business transaction number corresponding to the transaction request issued by the merchant; If the transaction environment is a production environment or a suspected test environment, the merchant's transaction number is matched with the transaction number, and a reconciliation result is generated based on the matching result.
7. The method according to claim 6, characterized in that, The step of matching the merchant's transaction ID with the transaction serial number and generating a reconciliation result based on the matching result includes: If the merchant serial number is equal to the merchant order number in the transaction serial number but the transaction amount is not equal, then the reconciliation result is determined to be an error. If the merchant's transaction number is equal to the merchant's order number in the transaction transaction number and the transaction amount is equal, then the reconciliation result is determined to be balanced. If the merchant order number in the merchant serial number or the transaction order number in the transaction serial number is missing, the reconciliation result is determined to be a one-sided account.
8. A reconciliation result generation device, characterized in that, The device includes: The transaction order acquisition module is used to acquire transaction transaction orders generated by the transaction platform based on transaction requests issued by merchants. The transaction transaction order includes: merchant order number, transaction amount, and transaction serial number. The environment determination module is used to determine the transaction environment based on the prefix of the merchant order number, the type of the merchant order number, and the transaction amount; The reconciliation result generation module is used to generate reconciliation results based on the transaction environment and the transaction serial number.
9. A device for generating reconciliation results, characterized in that, include: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction that causes the processor to perform the operation of the reconciliation result generation method as described in any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The storage medium stores at least one executable instruction, which, when executed on the reconciliation result generation device / apparatus, causes the reconciliation result generation device / apparatus to perform the operation of the reconciliation result generation method as described in any one of claims 1-7.