Reconciliation code embedding method, reconciliation method and related equipment

Abstract

The embodiment of the invention discloses a reconciliation code embedding method, a reconciliation method and related equipment, which are used for accurately attaching a reconciliation code of a corresponding payment request in a request message under the condition of being compatible with different transaction interfaces of different banks. The method comprises the following steps: receiving a payment request and a financial institution indicated by the payment request, wherein the financial institution is provided with a corresponding payment interface; determining a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface comprises the preset reconciliation field; determining a request message corresponding to the payment request, wherein a preset reconciliation field of the request message comprises a reconciliation code associated with the payment request; and sending the request message to a payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in a transaction detail entry corresponding to the payment request.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of account reconciliation, and in particular, to an account reconciliation code embedding method, an account reconciliation method, and related equipment. Background Art

[0002] The reconciliation system is an important tool in the financial field to ensure the consistency of transaction data. For enterprises, the reconciliation system is mainly used to check various transaction data such as inter-bank transfers and payment services.

[0003] In order to achieve accurate reconciliation, the existing reconciliation system will attach the reconciliation code of the corresponding transaction to the request message when sending the request message to the bank's transaction interface. In this way, when the bank generates transaction details based on the request message, it will also record the reconciliation code in the request message in the transaction details. Later, when the reconciliation system needs to compare the local transaction documents with the transaction details provided by the bank, it can use the reconciliation code in the transaction documents and transaction details as the matching basis for comparison.

[0004] In actual applications, bank interfaces have different standards for reconciliation codes. Even different interfaces of the same bank have their own requirements for reconciliation codes. Due to the different standards for reconciliation codes of different bank interfaces, manual code development and configuration are required. The newly added reconciliation code embedding code will invade the native code of the reconciliation system, which will affect the stability of system functions to a certain extent. Summary of the invention

[0005] The embodiments of the present application provide a reconciliation code embedding method, a reconciliation method and related equipment, which are used to accurately attach the reconciliation code of the corresponding payment request in the request message while being compatible with different transaction interfaces of different financial institutions.

[0006] A first aspect of an embodiment of the present application provides a method for embedding a reconciliation code, comprising:

[0007] A financial institution receiving a payment request and an instruction of the payment request, wherein the financial institution has a corresponding payment interface;

[0008] Determine a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface includes the preset reconciliation field;

[0009] Determining a request message corresponding to the payment request, wherein a preset reconciliation field of the request message includes a reconciliation code associated with the payment request;

[0010] The request message is sent to a payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in a transaction detail entry corresponding to the payment request.

[0011] In a specific implementation, the determining a request message corresponding to the payment request includes:

[0012] If the payment request is received, an original request message corresponding to the payment request is generated based on a preset message generation plug-in;

[0013] If the generation of the original request message is identified, the reconciliation code is generated based on the payment request, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain the request message.

[0014] In a specific implementation, the preset reconciliation field has a corresponding field length and offset, and the step of filling the reconciliation code in the preset reconciliation field of the original request message to obtain the request message includes:

[0015] Determine the content between the first byte bit and the second byte bit in the original request message as the original value of the preset reconciliation field, the first byte bit is the byte bit where the offset is located, and the field length is equal to the number of bytes between the second byte bit and the first byte bit;

[0016] The original value in the original request message is replaced with the reconciliation code to obtain the request message.

[0017] In a specific implementation, the generating the reconciliation code based on the payment request includes:

[0018] If the payment request is received, generating a business serial number corresponding to the payment request based on the payment request;

[0019] Obtaining a reconciliation code identifier corresponding to the financial institution;

[0020] The reconciliation code is obtained by combining the reconciliation code identifier and the business serial number.

[0021] A second aspect of an embodiment of the present application provides a reconciliation method, including:

[0022] Obtaining a payment entry of the business system, and obtaining a detailed transaction entry from a detailed query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with the corresponding payment request, and the detailed transaction entry is generated based on the reconciliation code embedding method according to any one of claims 1 to 6;

[0023] Determine the preset reconciliation fields corresponding to the financial institution;

[0024] Acquire, from the preset reconciliation field of the transaction detail record, a reconciliation code associated with the payment request corresponding to the transaction detail record;

[0025] Reconciliation is performed on payment entries and transaction detail records corresponding to the same reconciliation code.

[0026] In a specific implementation, the acquiring, from the preset reconciliation field of the transaction detail record, the reconciliation code associated with the payment request corresponding to the transaction detail record includes:

[0027] Obtaining the field length and offset corresponding to the preset reconciliation field;

[0028] The content between the first byte and the second byte in the transaction detail record is determined as the reconciliation code associated with the payment request corresponding to the transaction detail record.

[0029] In a specific implementation, determining the preset reconciliation field corresponding to the financial institution includes:

[0030] Acquire a current reconciliation code rule corresponding to the financial institution, wherein the current reconciliation code rule includes an initial reconciliation field, a field length corresponding to the initial field, and an offset;

[0031] If, based on the current reconciliation code rule, a reconciliation code that meets the current reconciliation code rule cannot be parsed from the transaction detail record, the historical reconciliation code rule corresponding to the financial institution is obtained, and the reconciliation field in the historical reconciliation code rule is determined as the preset reconciliation field corresponding to the financial institution.

[0032] A third aspect of an embodiment of the present application provides a computer device, including:

[0033] A receiving unit, configured to receive a payment request and a financial institution indicated by the payment request, wherein the financial institution has a corresponding payment interface;

[0034] A determination unit, configured to determine a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface includes the preset reconciliation field;

[0035] The determining unit is further configured to determine a request message corresponding to the payment request, wherein the preset reconciliation field of the request message includes a reconciliation code associated with the payment request;

[0036] The sending unit is used to send the request message to the payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in the transaction details entry corresponding to the payment request.

[0037] In a specific implementation, the determining unit is specifically configured to generate an original request message corresponding to the payment request based on a preset message generation plug-in if the payment request is received;

[0038] If the generation of the original request message is identified, the reconciliation code is generated based on the payment request, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain the request message.

[0039] In a specific implementation, the preset reconciliation field has a corresponding field length and offset, and the determining unit is specifically configured to determine the content between a first byte position and a second byte position in the original request message as the original value of the preset reconciliation field, the first byte position being the byte position where the offset is located, and the field length being equal to the number of byte positions between the second byte position and the first byte position;

[0040] The original value in the original request message is replaced with the reconciliation code to obtain the request message.

[0041] In a specific implementation, the determining unit is specifically configured to generate a business serial number corresponding to the payment request based on the payment request if the payment request is received;

[0042] Obtaining a reconciliation code identifier corresponding to the financial institution;

[0043] The reconciliation code is obtained by combining the reconciliation code identifier and the business serial number.

[0044] A fourth aspect of an embodiment of the present application provides a computer device, including:

[0045] an acquisition unit, configured to acquire a payment entry of a business system and acquire a detailed transaction entry from a detailed query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with a corresponding payment request, and the detailed transaction entry is generated based on the reconciliation code embedding method according to any one of claims 1 to 6;

[0046] A determination unit, configured to determine a preset reconciliation field corresponding to the financial institution;

[0047] The acquisition unit is further configured to acquire, from the preset reconciliation field of the transaction detail record, a reconciliation code associated with the payment request corresponding to the transaction detail record;

[0048] The reconciliation unit is used to perform reconciliation operations on payment entries and transaction detail records corresponding to the same reconciliation code.

[0049] In a specific implementation, the acquisition unit is specifically used to acquire the field length and offset corresponding to the preset reconciliation field;

[0050] The content between the first byte and the second byte in the transaction detail record is determined as the reconciliation code associated with the payment request corresponding to the transaction detail record.

[0051] In a specific implementation, the determining unit is specifically configured to obtain a current reconciliation code rule corresponding to the financial institution, wherein the current reconciliation code rule includes an initial reconciliation field, a field length corresponding to the initial field, and an offset;

[0052] If, based on the current reconciliation code rule, a reconciliation code that meets the current reconciliation code rule cannot be parsed from the transaction detail record, the historical reconciliation code rule corresponding to the financial institution is obtained, and the reconciliation field in the historical reconciliation code rule is determined as the preset reconciliation field corresponding to the financial institution.

[0053] A fifth aspect of an embodiment of the present application provides a computer device, including:

[0054] CPU, memory and input / output interface;

[0055] The memory is a short-term storage memory or a persistent storage memory;

[0056] The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method described in the first aspect or the second aspect.

[0057] A sixth aspect of the embodiments of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect.

[0058] A seventh aspect of an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores instructions, and when the instructions are executed on a computer, the computer executes the method described in the first aspect or the second aspect.

[0059] It can be seen from the above technical solutions that the embodiments of the present application have the following advantages: by using the interface specification of the payment interface of the financial institution, the preset reconciliation field in which the reconciliation code can be recorded is found in the fields included in the interface specification. And, this preset reconciliation field is configured as the preset reconciliation field corresponding to the financial institution. In this way, when generating a request message corresponding to the payment request, the associated reconciliation code can be directly attached to the preset reconciliation field of the request message. In this way, the financial institution will record the reconciliation code in the corresponding transaction detail entry generated based on the payment request, which can be used for matching between the payment entry and the transaction detail entry during the subsequent reconciliation. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] Figure 1 A system architecture diagram of the reconciliation system disclosed in the embodiment of the present application;

[0061] Figure 2A schematic diagram of a flow chart of a method for embedding a reconciliation code disclosed in an embodiment of the present application;

[0062] Figure 3 A schematic diagram of a flow chart of the reconciliation method disclosed in an embodiment of the present application;

[0063] Figure 4 Another system architecture diagram of the reconciliation system disclosed in the embodiment of the present application;

[0064] Figure 5 Another flowchart of the method for embedding a reconciliation code and the method for reconciliation disclosed in the embodiments of the present application;

[0065] Figure 6 A schematic diagram of an interface for configuring the reconciliation code rules disclosed in an embodiment of the present application;

[0066] Figure 7 A schematic diagram of the structure of a computer device disclosed in an embodiment of the present application;

[0067] Figure 8 A schematic diagram of the structure of a computer device disclosed in an embodiment of the present application;

[0068] Fig. 9 Another structural schematic diagram of the computer device disclosed in the embodiment of the present application. DETAILED DESCRIPTION

[0069] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0070] The embodiments of the present application provide a reconciliation code embedding method, a reconciliation method and related equipment, which are used to accurately attach the reconciliation code of the corresponding payment request in the request message while being compatible with different transaction interfaces of different financial institutions.

[0071] In order to better implement the reconciliation code embedding method and the reconciliation method of the present application, the present application embodiment provides the following Figure 1The reconciliation system shown, under the reconciliation system in the embodiment of the present application, there are at least one requester 101 and at least one financial institution 102, wherein in the payment scenario, the requester 101 is used to generate a payment request, and generate a request message corresponding to the payment request, and send the generated request message to the payment interface of the corresponding financial institution 102, and the financial institution 102, after receiving the request message sent by the requester 101, will execute the payment operation corresponding to the request message, and generate the corresponding transaction details based on the request message. In the reconciliation scenario, the requester 101 is used to generate a query request for transaction details, and generate a request message corresponding to the query request, and send the generated request message corresponding to the query request to the detail query interface of the corresponding financial institution 102, and the financial institution 102, after receiving the request message of the query request sent by the requester 101, will execute the query request to obtain the corresponding transaction details, and return the obtained transaction detail entries to the requester 101. Finally, the requester 101 can perform reconciliation operations on the payment entries and transaction detail entries corresponding to the same reconciliation code,

[0072] In some specific implementations, payment requests may come from different business systems 1011. If the business system 1011 and the payment system 1012 are integrated, each business system 1011 needs to be configured with the same set of payment systems 1012, resulting in resource redundancy. Therefore, the embodiment of the present application splits the requester 101 into at least one business system 1011 and a payment system 1012, wherein in the payment scenario, the business system 1011 is used to generate a payment request and send the payment request to the payment system 1012, and the payment system 1012 is used to receive the payment request sent by the business system 1011, and generates a request message that is consistent with the corresponding payment interface and contains the corresponding code according to the financial institution indicated by the payment request, and sends the generated request message to the financial institution 102. In the reconciliation scenario, the business system 1011 is used to generate a query request for transaction details and send it to the payment system 1012, and the payment system 1012 is used to generate a request message corresponding to the query request, and send the generated request message corresponding to the query request to the detail query interface of the corresponding financial institution 102, and receive the transaction detail entry returned by the detail query interface. Finally, the business system 1011 can perform reconciliation operations on the payment entry and transaction detail entry corresponding to the same reconciliation code, wherein the payment entry corresponds to the payment document in the business system 1011.

[0073] See also Figure 2 Based on the aforementioned reconciliation architecture, in the payment scenario, the present application embodiment provides the following Figure 1 The reconciliation code embedding method shown includes the following steps:

[0074] 201. A financial institution receives a payment request and a payment request instruction, where the financial institution has a corresponding payment interface.

[0075] The reconciliation code embedding method of the present application is mainly for enterprises or companies. Therefore, the received payment request usually indicates a clear payee bank, that is, the financial institution indicated by the payment request in the embodiment of the present application. Moreover, in actual application, the execution of the corresponding business is usually achieved by calling the interface of the financial institution. For example, the payment interface of the financial institution is called when executing the payment request, and the detail query interface of the financial institution is called when executing the transaction detail query request.

[0076] The financial institution may be a bank or an institution that owns online payment software.

[0077] 202. Determine a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface includes the preset reconciliation field.

[0078] It is understandable that any interface has a corresponding interface specification, which specifies the message format that an external object should have when accessing the interface. In general, the message format records each field that the message needs to contain and the position of each field in the entire message. Therefore, the embodiment of the present application can combine the analysis of the transaction details of the financial institution and the message specifications of the corresponding payment interface of the financial institution to find out the fields in the request message that will be recorded in the corresponding transaction details, and the need to fill in the reconciliation code in this field will not affect the financial institution's processing of this request message. If a field that meets the above conditions is found, this field can be set as the preset reconciliation field corresponding to the financial institution.

[0079] That is, before this step, the embodiment of the present application has found a suitable reconciliation field for the financial institution indicated by the payment request, and has set the suitable reconciliation field as the preset reconciliation field corresponding to the financial institution.

[0080] 203. Determine a request message corresponding to the payment request, wherein a preset reconciliation field of the request message includes a reconciliation code associated with the payment request.

[0081] Based on the foregoing embodiments, it can be known that the preset reconciliation field corresponding to the financial institution is a field included in the request message sent by the payment interface of the financial institution, and the field will be recorded in the corresponding transaction detail entry. Therefore, according to the interface specification of the payment interface for the preset reconciliation field (such as field length, offset, encoding and parsing, etc.), a request message containing the preset reconciliation field and the reconciliation code associated with the payment request is generated.

[0082] Among them, the reconciliation code associated with the payment request can be generated according to the payment batch number or other identification information of the payment request, and has the function of uniquely identifying different payment requests. The specific generation method is not limited here.

[0083] 204. Send a request message to the payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in the transaction detail entry corresponding to the payment request.

[0084] After obtaining the available request message in step 203, the request message corresponding to the payment request can be directly sent to the payment interface of the financial institution, and then the financial institution will execute the corresponding payment request based on the content in the request message, and transfer the payment amount indicated in the payment request to the payee indicated in the payment request. In addition, after the payment transfer is completed, the transaction details corresponding to this payment request will be generated according to the request message, and the transaction details corresponding to the payment request will be accompanied by the reconciliation code associated with the payment request.

[0085] In the embodiment of the present application, the interface specification of the payment interface of the financial institution is used to find out the preset reconciliation field in the field included in the interface specification, which can record the reconciliation code. In addition, this preset reconciliation field is configured as the preset reconciliation field corresponding to the financial institution. In this way, when generating a request message corresponding to the payment request, the associated reconciliation code can be directly attached to the preset reconciliation field of the request message. In this way, the financial institution will record the reconciliation code in the corresponding transaction detail entry generated based on the payment request, which can be used for matching between the payment entry and the transaction detail entry during the subsequent reconciliation.

[0086] In some specific implementations, the aforementioned step 203 can be implemented in the following manner: if a payment request is received, an original request message corresponding to the payment request is generated based on a preset message generation plug-in; if the generation of the original request message is identified, a reconciliation code is generated based on the payment request, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain a request message.

[0087] Specifically, in the case of a native request message generation plug-in, in order to avoid excessive modifications to the code layer, the reconciliation code can be intercepted based on the original request message generation logic. For example, after generating the original request message corresponding to the payment request based on the preset message generation plug-in, the reconciliation code can be generated based on the payment request, and the reconciliation code can be filled in the preset reconciliation field of the original request message to obtain the final required request message. Figure 5 The interception method shown in , realizes the acquisition of request message.

[0088] Furthermore, in some implementations, the preset reconciliation field has a corresponding field length and offset, and the step of "filling the reconciliation code in the preset reconciliation field of the original request message to obtain the request message" includes: determining the content between the first byte position and the second byte position in the original request message as the original value of the preset reconciliation field, the first byte position is the byte position where the offset is located, and the field length is equal to the number of bytes between the second byte position and the first byte position; replacing the original value in the original request message with the reconciliation code to obtain the request message.

[0089] It is understandable that the field length and offset corresponding to the preset reconciliation field need to be consistent with the provisions in the interface specification to ensure accurate assembly and parsing. Specifically, the first byte position is the byte position where the offset is located, and the first byte position will reach the second byte position after passing through the number of bytes equal to the field length.

[0090] Among them, in addition to locating the preset reconciliation field through field length and offset, it may also be achieved through field identification, which is not limited in the embodiments of the present application.

[0091] Furthermore, the aforementioned step of "generating a reconciliation code based on a payment request" includes: if a payment request is received, generating a business serial number corresponding to the payment request based on the payment request; obtaining a reconciliation code identifier corresponding to the financial institution; and obtaining the reconciliation code by combining the reconciliation code identifier and the business serial number.

[0092] Specifically, the reconciliation code identifier is used to identify payments initiated by the business system through the payment system (which is part of the enterprise management system), and is not used to distinguish payment / collection business. Customers usually use different bank accounts to transfer money. In this payment scenario, the payment flow of bank account A and the receipt flow of bank account B can be matched to the payment slip of bank account A transferring money to bank account B. For the detailed entries of customers receiving payments from other parties, there is generally no reconciliation code identifier. The embodiment of the present application can automatically derive a receipt to complete the business reconciliation. In other words, the reconciliation code identifier is used to determine whether the payment source is the payment system that fills in the reconciliation code identifier, because there is no reconciliation code identifier, which means it is an external ERP system or a third-party payment. There is a difference in the matching process of the receipt and payment slip and the detailed transaction entries. The embodiment of the present application only matches and reconciles the payment entries initiated by the enterprise-side payment system with the detailed transaction entries.

[0093] The foregoing describes various implementations of the reconciliation code embedding method of the present application in payment scenarios. Based on the foregoing embodiments, the following describes various implementations of the reconciliation method of the present application embodiment in payment scenarios.

[0094] See also Figure 3 , the present application embodiment provides a reconciliation method, comprising the following steps:

[0095] 301. Obtain a payment entry from a business system, and obtain a detailed transaction entry from a detailed query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with a corresponding payment request, and the detailed transaction entry is generated based on the reconciliation code embedding method described in any of the aforementioned embodiments.

[0096] Among them, the payment entry is a detailed record corresponding to a payment request generated by the business system after the business system confirms that a payment request has been completed; the transaction detailed entry of a financial institution is similar, which is a detailed record of the payment request generated by the financial institution after the financial institution confirms that the payment request has been completed.

[0097] Payment entries are recorded in the business system, and transaction detail entries are recorded in the financial institution. In order to compare the payment entries and transaction detail records, the payment entries and transaction detail records corresponding to the same payment request need to be matched first. In the embodiment of the present application, in order to ensure that matching payment entries and transaction detail records can be found during reconciliation, the reconciliation code corresponding to the payment request needs to be recorded in both the payment entry and the transaction detail record.

[0098] 302. Determine the preset reconciliation fields corresponding to the financial institution.

[0099] Similar to the above embodiment, the preset reconciliation field corresponding to the financial institution is a field included in the request message sent by the payment interface of the financial institution, and the field will be recorded in the corresponding transaction detail entry. Therefore, based on the preset reconciliation field corresponding to the financial institution, the reconciliation code associated with the payment request corresponding to the transaction detail record can be found.

[0100] 303. Obtain a reconciliation code associated with the payment request corresponding to the transaction detail record from a preset reconciliation field of the transaction detail record.

[0101] Specifically, a reconciliation code is recorded in the preset reconciliation field, and the reconciliation code is associated with the corresponding payment request. Therefore, the reconciliation code associated with the payment request corresponding to the transaction detail record can be obtained directly from the preset reconciliation field of the transaction detail record.

[0102] 304. Perform reconciliation operations on payment entries and transaction detail records corresponding to the same reconciliation code.

[0103] As described in the above embodiment, the payment entry and transaction detail record corresponding to the same reconciliation code must correspond to the same unique payment request. Under the above premise, the embodiment of the present application can perform reconciliation operations on the payment entry and transaction detail record corresponding to the same reconciliation code. Specifically, the specific implementation method of the reconciliation operation is not limited in the embodiment of the present application.

[0104] It should be noted that in the reconciliation scenario of the embodiment of the present application, only the transaction details involving payment are processed, and the transaction details obtained may include not only the transaction details of the payment request, but also the transaction details of the collection operation, which is not limited here.

[0105] In some specific implementations, the aforementioned step of "obtaining, from the preset reconciliation field of the transaction detail record, the reconciliation code associated with the payment request corresponding to the transaction detail record" includes: obtaining the field length and offset corresponding to the preset reconciliation field; determining the content between the first byte and the second byte in the transaction detail record as the reconciliation code associated with the payment request corresponding to the transaction detail record.

[0106] Specifically, the field length and offset corresponding to the preset reconciliation field need to be consistent with the provisions in the interface specification to ensure accurate assembly and parsing.

[0107] The above describes various embodiments of the method for embedding a reconciliation code and the method for reconciliation of the present application. Figure 4 , the following describes the specific implementation method of the payment scenario and the reconciliation scenario of the embodiment of the present application in a specific business scenario.

[0108] The embodiment of the present application adopts the low-code concept to abstract the reconciliation business model that can be oriented to the payment scenario and the whole process of the reconciliation scenario: basic data layer, business framework layer, data processing layer, and business application layer. Among them, the basic data layer needs to maintain the current reconciliation code rules and historical reconciliation code rules of the payment interface, the current reconciliation code rules and historical reconciliation code rules of the transaction detail interface, and locate the preset reconciliation fields such as the business reference number or transfer remarks in the bank message through the low-code framework of the business layer, and then complete the embedding and parsing of the reconciliation code (from the transaction detail record) at the data processing layer, and correspondingly complete the generation of request messages and the parsing of response messages at the business application layer, so as to realize the corresponding functions of the reconciliation code without invading the existing bank interface with zero code.

[0109] First, maintain basic information such as the interface specifications of the payment interface, the interface specifications of the transaction details interface, and the reconciliation code rules, maintain different versions of the reconciliation code rules for different interfaces, and provide field positioning algorithms for different message formats such as xml format / json format / text format, which are used to find the preset reconciliation fields in the message according to the corresponding reconciliation code rules. At the same time, provide a business framework to extend the low-code processing framework, define the reconciliation code embedding process and the reconciliation code parsing process (to assist the operation of the reconciliation method of the embodiment of the present application). Finally, considering that bank plug-ins are usually deployed in existing bank-enterprise applications to generate payment messages or transaction details messages, in order to minimize changes to existing software, the embodiment of the present application abstracts the reconciliation code embedding process from the bank plug-in layer downward and embeds it in the business framework layer.

[0110] See also Figure 5 The reconciliation code embedding method and the reconciliation method process of the embodiment of the present application are as follows: 1. Intercept the payment message / transaction detail response message at the business aspect; 2. According to the routed bank interface (i.e., the payment interface or transaction detail interface of the financial institution), find the corresponding reconciliation code rule, which contains information such as offset and length; 3. Find the field value of the preset reconciliation field to be processed through the field positioning algorithm, and then embed the reconciliation code or parse the reconciliation code according to the reconciliation code rule, and be compatible with the historical reconciliation code rule during the reconciliation code embedding or reconciliation code parsing process; 4. Return the reconciliation code to the business system to complete the business reconciliation.

[0111] Among them, the historical reconciliation code rules are for product iterations. Due to different payment interface specifications of different banks, for example, the previous payment interface used the transfer remark field as the preset reconciliation field. The bank version update introduced a reconciliation field after the payment interface upgrade, which can be directly used as the preset reconciliation field. Therefore, it is necessary to maintain new reconciliation code rules, such as maintaining new preset reconciliation fields and setting the original reconciliation code rules as historical reconciliation code rules. After the customer upgrades the bank version, the historical reconciliation code rules can be used to compatibly handle the parsing of the reconciliation code in the payment message that originally used the transfer remark field as the preset reconciliation field.

[0112] Next, the reconciliation code embedding and reconciliation code parsing in the above step 3 are further explained.

[0113] 1. Embedding the reconciliation code

[0114] After the business framework captures the original request message (corresponding to the transaction detail message sent), it uses the positioning algorithm to find the start and end positions of the preset reconciliation field, then generates the reconciliation code according to the configuration rules and embeds it into the field, and finally reassembles it into a sendable request message.

[0115] Specifically, the low-code business framework can route the field positioning algorithm of the payment business, obtain the reconciliation code rules and generate the reconciliation code based on the business serial number, and finally embed the reconciliation code into the preset reconciliation field in the message, where the business serial number is completed by the serial number generator. Taking the payment message as an example, first find the location of the preset reconciliation field in the original request message generated by the bank plug-in (that is, the message generation plug-in), then cut the payment message into several substrings, and then generate the reconciliation code according to the reconciliation code rules and recombine the substrings, and finally complete the reconciliation code embedding. Among them, the reconciliation code generation process is as follows: 1. Determine the payment bank interface according to the thread context; 2. Determine the payment bank interface according to the bank interface; Figure 61. Find the corresponding reconciliation code rule in the reconciliation code rules shown; 2. Find the reconciliation code identifier, format, reconciliation code offset and reconciliation code length and other information from the reconciliation code rules; 3. Find the business serial number of the preset reconciliation field in the original request message based on the aforementioned reconciliation code rules, and fill in the reconciliation code identifier in front, generate the reconciliation code according to the number of pieces format, reconciliation code offset and reconciliation code length and other information, and obtain the request message.

[0116] 2. Analysis of reconciliation code

[0117] The low-code business framework routes the field positioning algorithm of the transaction detail business, obtains the reconciliation code rules, and parses the reconciliation codes in the transaction detail entries.

[0118] It should be noted that the bank interface usually carries business fields in the xml / json / format. In order to accurately find the preset reconciliation field, in addition to recording the offset, the full path of the business field can also be predefined. For example, use "root / body / list / yuref" as the full path expression in xml and json format, and use "|6" as the offset of the preset reconciliation field, which means obtaining the 6th field value of each line of data parsed by the separator character '|'.

[0119] The embodiment of the present application realizes lightweight development, which only requires maintaining patch data upgrade scripts to meet user reconciliation business needs. In addition, business rule visualization is realized, zero intrusion into the original interface code, and compatibility with historical versions of business rules. Business rule visualization, such as Figure 6 You can see that each payment interface and detail interface carries the reconciliation code field and reconciliation code composition rules. Previously, these were written in the code and were not visible to the rules.

[0120] See also Figure 7 , an embodiment of the present application provides a computer device, including:

[0121] A receiving unit 701, for receiving a payment request and a financial institution indicating the payment request, the financial institution having a corresponding payment interface;

[0122] A determination unit 702, configured to determine a preset reconciliation field corresponding to a financial institution, wherein the message specification of the payment interface includes the preset reconciliation field;

[0123] The determining unit 702 is further configured to determine a request message corresponding to the payment request, wherein the preset reconciliation field of the request message includes a reconciliation code associated with the payment request;

[0124] The sending unit 703 is used to send a request message to the payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in the transaction details entry corresponding to the payment request.

[0125] In a specific implementation, the determination unit 702 is specifically configured to generate an original request message corresponding to the payment request based on a preset message generation plug-in if a payment request is received;

[0126] If the generation of the original request message is identified, a reconciliation code is generated based on the payment request, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain the request message.

[0127] In a specific implementation, the preset reconciliation field has a corresponding field length and offset, and the determination unit 702 is specifically configured to determine the content between the first byte position and the second byte position in the original request message as the original value of the preset reconciliation field, the first byte position is the byte position where the offset is located, and the field length is equal to the number of bytes between the second byte position and the first byte position;

[0128] Replace the original value in the original request message with the reconciliation code to obtain the request message.

[0129] In a specific implementation, the determining unit 702 is specifically configured to generate a business serial number corresponding to the payment request based on the payment request if a payment request is received;

[0130] Obtain the corresponding reconciliation code identifier of the financial institution;

[0131] Combine the reconciliation code identifier and the transaction serial number to obtain the reconciliation code.

[0132] See also Figure 8 , an embodiment of the present application provides a computer device, including:

[0133] An acquisition unit 801 is used to acquire a payment entry of a business system and acquire a transaction detail entry from a detail query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with a corresponding payment request, and the transaction detail entry is generated based on the reconciliation code embedding method according to any one of claims 1 to 6;

[0134] A determination unit 802, configured to determine a preset reconciliation field corresponding to a financial institution;

[0135] The acquisition unit 801 is further configured to acquire a reconciliation code associated with the payment request corresponding to the transaction detail record from a preset reconciliation field of the transaction detail record;

[0136] The reconciliation unit 803 is used to perform reconciliation operations on payment entries and transaction detail records corresponding to the same reconciliation code.

[0137] In a specific implementation, the acquisition unit 801 is specifically used to acquire the field length and offset corresponding to the preset reconciliation field;

[0138] The content between the first byte and the second byte in the transaction detail record is determined as the reconciliation code associated with the payment request corresponding to the transaction detail record.

[0139] In a specific implementation, the determination unit 802 is specifically configured to obtain a current reconciliation code rule corresponding to a financial institution, where the current reconciliation code rule includes an initial reconciliation field, a field length corresponding to the initial field, and an offset;

[0140] If, based on the current reconciliation code rules, a reconciliation code that meets the current reconciliation code rules cannot be parsed from the transaction detail records, the historical reconciliation code rules corresponding to the financial institution are obtained, and the reconciliation fields in the historical reconciliation code rules are determined as the preset reconciliation fields corresponding to the financial institution.

[0141] Fig. 9 It is a schematic diagram of a computer device structure provided in an embodiment of the present application. The computer device 900 may include one or more central processing units (CPU) 901 and a memory 905. The memory 905 stores one or more application programs or data.

[0142] The memory 905 may be a volatile storage or a persistent storage. The program stored in the memory 905 may include one or more modules, each of which may include a series of instruction operations in the computer device. Furthermore, the central processing unit 901 may be configured to communicate with the memory 905 and execute a series of instruction operations in the memory 905 on the computer device 900.

[0143] The computer device 900 may also include one or more power supplies 902, one or more wired or wireless network interfaces 903, one or more input and output interfaces 904, and / or one or more operating systems, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0144] The CPU 901 can execute the aforementioned Figures 1 to 8 The operations performed by the computer device in the illustrated embodiment will not be described in detail here.

[0145] It should be noted that, although the steps in the flowcharts involved in the embodiments are drawn in sequence according to the instructions of the arrows, unless otherwise clearly stated in this document, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0146] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0147] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0148] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0149] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0150] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, read-only memory), random access memory (RAM, random access memory), disk or optical disk and other media that can store program code.

[0151] An embodiment of the present application also provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the above-mentioned reconciliation code embedding method or reconciliation method.

Claims

1. A method for embedding a reconciliation code, characterized in that: include: A financial institution receiving a payment request and an instruction of the payment request, wherein the financial institution has a corresponding payment interface; Determine a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface includes the preset reconciliation field; Determining a request message corresponding to the payment request, wherein a preset reconciliation field of the request message includes a reconciliation code associated with the payment request; The request message is sent to a payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in a transaction detail entry corresponding to the payment request.

2. The method for embedding a reconciliation code according to claim 1, characterized in that: The determining the request message corresponding to the payment request includes: If the payment request is received, an original request message corresponding to the payment request is generated based on a preset message generation plug-in; If the generation of the original request message is identified, the reconciliation code is generated based on the payment request, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain the request message.

3. The method for embedding a reconciliation code according to claim 2, characterized in that: The preset reconciliation field has a corresponding field length and offset, and the reconciliation code is filled in the preset reconciliation field of the original request message to obtain the request message, including: Determine the content between the first byte bit and the second byte bit in the original request message as the original value of the preset reconciliation field, the first byte bit is the byte bit where the offset is located, and the field length is equal to the number of bytes between the second byte bit and the first byte bit; The original value in the original request message is replaced with the reconciliation code to obtain the request message.

4. The method for embedding a reconciliation code according to claim 2, characterized in that: The generating the reconciliation code based on the payment request comprises: If the payment request is received, generating a business serial number corresponding to the payment request based on the payment request; Obtaining a reconciliation code identifier corresponding to the financial institution; The reconciliation code is obtained by combining the reconciliation code identifier and the business serial number.

5. A reconciliation method, characterized in that: include: Obtaining a payment entry of a business system, and obtaining a detailed transaction entry from a detailed query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with a corresponding payment request, and the detailed transaction entry is generated based on the reconciliation code embedding method according to any one of claims 1 to 4; Determine the preset reconciliation fields corresponding to the financial institution; Acquire, from the preset reconciliation field of the transaction detail record, a reconciliation code associated with the payment request corresponding to the transaction detail record; Reconciliation is performed on payment entries and transaction detail records corresponding to the same reconciliation code.

6. The reconciliation method according to claim 5, characterized in that: The acquiring, from the preset reconciliation field of the transaction detail record, a reconciliation code associated with the payment request corresponding to the transaction detail record comprises: Obtaining the field length and offset corresponding to the preset reconciliation field; The content between the first byte and the second byte in the transaction detail record is determined as the reconciliation code associated with the payment request corresponding to the transaction detail record.

7. The reconciliation method according to claim 5, characterized in that: The determining of the preset reconciliation field corresponding to the financial institution includes: Acquire a current reconciliation code rule corresponding to the financial institution, wherein the current reconciliation code rule includes an initial reconciliation field, a field length corresponding to the initial field, and an offset; If, based on the current reconciliation code rule, a reconciliation code that complies with the current reconciliation code rule cannot be parsed from the transaction detail record, the historical reconciliation code rule corresponding to the financial institution is obtained, and the reconciliation field in the historical reconciliation code rule is determined as the preset reconciliation field corresponding to the financial institution.

8. A computer device, characterized in that: include: A receiving unit, configured to receive a payment request and a financial institution indicated by the payment request, wherein the financial institution has a corresponding payment interface; A determination unit, configured to determine a preset reconciliation field corresponding to the financial institution, wherein the message specification of the payment interface includes the preset reconciliation field; The determining unit is further configured to determine a request message corresponding to the payment request, wherein the preset reconciliation field of the request message includes a reconciliation code associated with the payment request; The sending unit is used to send the request message to the payment interface corresponding to the financial institution, so that the financial institution records the reconciliation code in the transaction details entry corresponding to the payment request.

9. A computer device, characterized in that: include: an acquisition unit, configured to acquire a payment entry of a business system and acquire a detailed transaction entry from a detailed query interface of a financial institution, wherein the payment entry includes a reconciliation code associated with a corresponding payment request, and the detailed transaction entry is generated based on the reconciliation code embedding method according to any one of claims 1 to 6; A determination unit, configured to determine a preset reconciliation field corresponding to the financial institution; The acquisition unit is further configured to acquire, from the preset reconciliation field of the transaction detail record, a reconciliation code associated with the payment request corresponding to the transaction detail record; The reconciliation unit is used to perform reconciliation operations on payment entries and transaction detail records corresponding to the same reconciliation code.

10. A computer device, characterized in that: include: CPU, memory and input / output interface; The memory is a short-term storage memory or a persistent storage memory; The central processing unit is configured to communicate with the memory and execute instructions in the memory to perform the method according to any one of claims 1 to 4 or 5 to 7.

11. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 4 or 5 to 7.

12. A computer storage medium, characterized in that: The computer storage medium stores instructions, and when the instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 4 or 5 to 7.

Images