A system and method that enables integrations with institutions to be carried out under a single common platform.

Abstract

This invention relates to a system (1) and method (100) that enables the technical determination of a definite outcome in cases where the outcome of the transaction is uncertain, the execution of an integration based on a parametric institutional profile, and the performance of a reconciliation classification process in integrations with third-party institutions using different communication protocols, data formats, and connection models.

Description

1 TARIFF THE ONLY INTEGRATION THAT IS CARRIED OUT WITH INSTITUTIONS ENSURING THAT IT IS CARRIED OUT UNDER A COMMON PLATFORM A SYSTEM AND METHOD Technical Area This invention utilizes different communication protocols, data formats, and connection models. In integrations with third-party organizations using the service; transaction In situations where the outcome remains uncertain, there is technically no definite outcome. determining and implementing an integration based on a parametric institutional profile. and a system and method that enables the reconciliation classification process to be carried out. It is related to. Previous Technique 15 In the current state of the technology, enterprise integrations are generally separate from each other. applications, specially developed service adapters, file transfer infrastructures and through integration layers dependent on specific products or technologies is being implemented. The current Enterprise Service Bus (Enterprise Service Bus-20) ESB), Integration Platform as a Service iPaaS), hybrid integration platform-based commercial solutions for data transfer and formatting. It offers transformation and orchestration capabilities; however, the uncertainty of the transaction outcome... technically resolving it involves a parametric reverse transaction policy dependent on the institution's profile, and It falls short in terms of consensus classification issues. Known solutions 25 It usually focuses separately on service integration or file integration. Online service calls and offline file streams operate on different platforms, in different ways. It is operated with decision logic. Known mapping / transformation solutions data format. It focuses on the cycle. The mapping output is usually transmitted to the target system and a decision is made. It is independent of the processes. Known orchestration solutions sequence the work steps in 30 steps. Orchestration manages, or conditionally manages, the outcome of which is usually success / failure. 2 It is expressed in binary form. Known pricing / saga pattern structures allow for error compensation. and focuses on reversal processes. The decision to reverse engineer is usually static. It depends on the rules or logic coded by the developer. Known tracking and Logging solutions generate technical logs. These logs are generally used for error analysis and... Used for performance monitoring purposes; direct input into consensus decision 5 They do not create known onboarding and configuration structures. It facilitates commissioning. Organizational parameters typically include connectivity and identification. It is limited to the information available. Therefore, considering the studies and shortcomings in the current technology, 10 when synchronous service calls and offline file streams are present. connecting to the same decision engine, both flow types having the same correlation ID by combining them under one record, allowing them to be tracked through a single transaction log and with the same reconciliation. subjection to the classification mechanism, transformation in the institutional profile the rules working in an integrated manner with the logic of determining the outcome, orchestration 15 Converting the output into predefined technical decision classes: successful collection, cancellation-approved collection, transaction not to be included in reconciliation, manual generating final agreement classes in the form of a process requiring review, Current status with parametric reverse engineering rules based on the corporate profile. the classification working together, reverse engineering trigger conditions, 20 query steps and final agreement class mapping institution-specific profile deriving the same correlation identity from its parameters at runtime Underneath, it is necessary to create not only a record but also a chain of technically sound evidence that can be used to make decisions, delayed response, retry result, file fate log, and reverse engineering The institution 25 requested that the results be combined in the same transaction record to produce evidence of reconciliation. Parameters in the profile at runtime; routing, timeout, mapping, reverse engineering policy and consensus classification rules jointly determining, profiling, and shaping the entire execution behavior It is understood that a system and method that provides this is needed. 3 Chinese patent no. CN212484357U, which falls under the known state of the art. in the document, a corporate information system belongs to the corporate information management system category. The integration and management system is being discussed. The invention in question involves a web management terminal, an enterprise information management server, a national household registry management system, an enterprise information data collection module, an information collection 5 It includes a terminal and a database server. Corporate information data collection. The module is connected to the data collection terminal; corporate information management server, It is connected to the corporate information data collection module; web management terminal, corporate It is connected to the information management server, and the corporate information management server is also national. It is connected to the household registration management system. The invention in question is a screening module and 10 through the national household registration management system, those whose registered place of business is in Guangxi or It can filter the relevant information of entrepreneurs whose legal representative is from Guangxi. Based on this information, staff can offer services to entrepreneurs and also to corporate clients. It facilitates the integration and management of information. Brief Description of the Invention The purpose of this invention is to create a system for different communication protocols, data formats, and connections. In integrations with third-party organizations that use these models; In cases where the outcome of the transaction remains uncertain, there is technically no definite outcome. 20 determining and implementing an integration based on a parametric institutional profile. and developed to enable the reconciliation classification process to be carried out. It is about implementing a system and a method. Another purpose of this invention is to reduce timeouts in synchronous enterprise transactions. whether the transaction occurred in the other system when it happened eliminating uncertainty, preventing duplicate payments and reducing the risk of disagreement reduction, automatic protection of transaction integrity, online and Enterprise integrations by connecting offline streams to a single decision engine. shortening the commissioning time and reducing the operational error rate 30 It is about developing a system and method to ensure this. 4 Detailed Description of the Invention The "Implemented with Institutions" project was carried out to achieve the purpose of this invention. A 5 that enables integrations to be carried out under a single common platform. The "System and Method" is shown in the attached figure; Figure 1 shows a schematic view of the system that is the subject of the invention. Figure 2 shows a schematic view of the invention method. The parts shown in the figures are individually numbered, and these numbers... The corresponding answers are given below. 1. System 2. Parametric Institutional Database 15 3. Common Data Model and Correlation ID Module 4. Operation Status Module 5. Consensus Classification Module 6. Persistent State Database and Chain of Evidence Module 7. Repeatable Single-Transaction and Data Deduplication Module 20 8. Institutional Connection, Adapter and Conversion Module Module 9: Orchestration 10. Monitoring and Channel Module D. External Server 25 Method 100 Third parties use different communication protocols, data formats, and connection models. In integrations carried out with partner institutions; the transaction outcome is uncertain. 30 In cases where it remains undecided, it is technically impossible to determine a definite outcome, parametrically. implementing an integration based on the organization profile and reconciliation classification. The system in question, developed to enable the operation to be carried out (1); - technical integration features of each third-party institution into a single system. Maintaining a parametric profile structure; Representational State Transfer, Simple Object Access Protocol, file transfer, email type connection 5 type, certificate, application programming interface key, identifier security parameters in the form of verification method, connection timeout, read timeout, total transaction timeout timeout values ​​in this format, source format, target format, Data transformation rules in the form of mapping / matching definitions, inverse 10 transaction trigger condition, reverse transaction query endpoint, wait time, the inverse operation policy in the form of number of retries, again availability key production method, data deduplication control repeatability rules in the form of a window in a single structure at least one parametric institutional profile structured to combine 15 database (2), - online incoming, online outgoing and offline file events are all the same. to ensure that it is combined under a canonical data model, for each operation generating a unique correlation identifier, this identifier, throughout the life of the process from the first trigger throughout the cycle to the final agreement class 20 as a point of reference in all steps until its determination enabling the use of files in offline file streams by linking its rows or records to the same correlation structure, File-based operations are monitored in the same way as synchronous service operations. at least one partner structured to be subject to the decision-making mechanism 25 data model and correlation identity module (3), - the lifecycle of each integration process in finite states and transitions Managing according to the rules; the process has been initiated, but it has not yet been transmitted to the other system. “Initiated” means the request has been sent to the receiving system, and a response has been received. "Sent," meaning awaiting a successful response from the other system. 30 "Completed," meaning received, is defined in the organization profile. 6 "Time has expired, no response received" "Expiration", time limit, or institution-specific adverse outcome due to uncertain result. "Reverse operation triggered" means the operation / query step has been triggered. "Reverse" means the reverse operation / query response has been received and evaluated. "Transaction approved", original response received after timeout 5 "Late response," meaning the transaction was mapped to the final reconciliation class, and "Reconciled" means finalized, the process has a permanent error. "Error" means it resulted in automatic classification. "Guide" means it couldn't be done, manual review is required. including "review" situations, defining additional intermediate situations 10 at least one process status module configured to provide (4), - the terminal states of the state machine are predefined final states mapping to consensus classes, classification rules institution Drawing inspiration from the profile and applying it during working hours leads to success. collection, cancellation-approved collection, transaction not to be included in reconciliation, 15 Manual review required, partial completion and permanent error. Defining consensus classes in this way, additional ones according to business needs. at least one configured to enable the definition of classes Consensus Classification Module (5), - Permanently record all events under the correlation ID of each transaction. save, delayed response, retry result, file status record, Reverse transaction response and final reconciliation class in the same transaction record. to combine, to form the technical evidence of the consensus decision, input as; correlation identity and transaction status module (4) Request generated, response, timeout, reverse operation, delayed response, classification 25 Taking a record of each event in the form of a decision, and outputting it as correlation. a chain of events unified under one identity, time-stamped and sequential. at least one persistent state configured to provide data in this format database and chain of evidence module (6), - To prevent the same process from being triggered repeatedly, the institution requires 30 for each process. a single-transaction key derived from profile and transaction parameters 7 to generate, a corresponding key before the transaction is executed Search for the record in the permanent status database and evidence chain module (6); If there is a record of a previously successful transaction, the process can be repeated. to prevent execution and to revert the current result At least one structured repeatable single-operation and data 5 deduplication module (7), - Representative State Transfer, Simple Object Access Protocol, application Programming interface and File Transfer Protocol / Secure File The Transfer Protocol supports email and similar institutional communication methods. to support and 10 according to the connection parameters in the organization profile Selecting the appropriate adapter, data conversion and schema matching functions to host, common data of institutions in different formats converting it to a model and mapping / matching rules for the institution at least one structured to ensure it feeds from its profile institutional connection, adapter and conversion module (8), 15 - the sequence of technical steps and conditions within the integration flow to manage its branches, integrated with the process status module (4) by working to trigger timeouts and reverse branching. at least one orchestration module configured (9), - Message details, error codes, task 20 as operational monitoring function to ensure the monitoring of status and technical records, operational working for visibility purposes, channel and product integration function as the platform's banking products, business services, channel External servers in the form of applications and third-party systems (D) at least one 25 configured to exchange data with It includes monitoring and channel module (10). The parametric institutional profile database (2) included in the system in question (1) each third-party technical integration features in a single parametric profile. to maintain its structure; Representational State Transfer (30) REST), Simple Object Access Protocol (SOAP), 8 file transfer, email type connection, certificate, application Application Programming Interface (API) key, identifier security parameters in the form of verification method, connection timeout (timeout), read timeout, total operation timeout, and other types of timeouts. The values ​​are categorized into 5 types: source format, target format, and mapping / mapping definitions. data transformation rules, reverse operation trigger condition, reverse operation query endpoint the point, the waiting time, the inverse operation in the form of number of retries policy, repeatability (idempotency) key production method, data repeatability rules in the form of a deduplication control window It is structured to be unified into a single structure. Parametric institutional profile 10 database (2), to keep the profile in a versionable structure and for the same institution Storing parameters from different periods, implementing a new institutional integration. When received, it works by creating only a profile definition without making any code changes. to enable the determination of time behavior, institutional code or process Taking the institution identifier derived from the context as input, the relevant institution's 15 The runtime parameter set is output as a connection type. timeout values, mapping reference, reverse operation policy, repeatability It is structured to use rules and classification rules. Common data model and correlation ID 20 in the system of invention (1) module (3), online inbound, online outbound and offline file events fall under the same canonical data model. to ensure their combination, a unique correlation identifier for each transaction. to produce, this identity, throughout the lifecycle of the process, from the initial trigger to the final 25 is used as a reference point in all steps up to the determination of the agreement class. to enable its use, file lines in offline file streams or By linking their records to the same correlation structure, file-based operations to subject synchronous service operations to the same monitoring and decision-making mechanism It is structured. Common data model and correlation identity module (3), input as a service response from the institution, file recording or application programming interim 30 Receiving raw data in the form of a face request and processing context, outputting canonical data. 9 Transaction data transformed into a data model and a unique correlation identifier. It is structured to provide. The transaction status module (4) in the system in question (1) is included in each integration The lifecycle of the process consists of finite states and transition rules. 5 Managing with; means the process has been initiated but has not yet been transmitted to the other system. “Initiated” means the request has been sent to the receiving system and a response is awaited. “Sent” means a successful response has been received from the other system. “Completed” indicates that the timeout period defined in the organization profile has expired. "Timeout," meaning no response was received, also known as a time-out or 10-minute delay. This means that an institution-specific reverse process / query step was triggered due to an uncertain outcome. The message "reverse_triggered" was received, and the reverse operation / query response was received. “Reverse operation confirmed” (reverse_confirmed), meaning it has been evaluated, "Late response" means the original response was received after a timeout. (late_response) means the transaction has been mapped to the final reconciliation class and finalized. 15 The incoming "Reconciled" means the operation resulted in a permanent error. "Failed" and automatic classification could not be performed, manual review required. "Manual review" statuses, which means it is needed. It is structured to include and allow for the definition of additional intermediate states. Transaction status module (4), transition rules with parameters in the institutional profile 20 To determine, in the case of "Sent", the time limit expires and it says "Timeout". Switching to the status, reversing the process in the institution profile in case of "Timeout" If the policy is defined, switching to the "Reverse trade triggered" state, reverse trade response Upon receipt, it switches to the "Reverse transaction confirmed" status and reconciliation classification. Transfer to module (5), if the original response is received late, it will be in the status "Late response" 25 to pass and evaluate within the context of the current state machine It is configured. The process status module (4) displays the current status and the trigger event. and taking the transition rules from the organization profile as input, the new status and It is configured to output the triggered action. The agreement classification module (5) in the system (1) which is the subject of the invention, status the terminal states of the machine to predefined final reconciliation classes matching, classification rules are based on the organizational profile and work It is structured to be implemented in a timely manner. Consensus classification module (5), successful_collection, cancellation confirmed collection 5 (cancelled_collection) - Transaction not to be included in reconciliation. (excluded_from_recon), a process requiring manual review. (manual_review_required), partial completion, and persistent error. Defining agreement classes as (failed), adding additional classes according to business needs. It is structured to enable its identification. Consensus classification 10 module (5), terminal or pre-terminal status of the state machine, from the institution returned technical response codes, information about delayed responses, and the organization profile. receiving data in the form of classification rules as input, final agreement. to provide data such as class and reason for assignment in output form It is being structured. 15 The reconciliation classification module (5) in the system (1) which is the subject of the invention, transaction When the status module (4) is in the “completed” state, from the institution when the returned technical response code is included in the list of success codes in the organization profile And in the absence of a delayed or contradictory response, successful collection is 20. It is structured to produce the result (successful_collection). Reconciliation Classification module (5), Operation status module (4) “Reverse operation confirmed” When in the (reverse_confirmed) state, the reverse operation response code is generated by the institution. when it appears in the list of "no transaction found" codes in your profile and arrives late In the absence of a contradictory response, transaction 25 will not be included in the agreement. It is configured to output the result (excluded_from_recon). Reconciliation classification module (5), transaction status module (4) “Reverse transaction When in the "reverse_confirmed" state, the reverse operation response code when it appears in the list of "transaction cancelled / reversed" codes in the institution profile And in the absence of a late, contradictory response, the cancellation-approved collection is 30. It is configured to produce a (cancelled_collection) result. Reconciliation 11 Classification module (5), process status module (4) “Late response” (late_response) when in this situation, the original response received late contains a success code and reverses. When the transaction response contains the code "transaction not found" or "transaction cancelled", extracting the result of the process requiring manual review (manual_review_required) It is structured as follows: Reconciliation classification module (5), transaction status 5 module (4) from “sent” status directly to “failed” status When this happens, the technical response code returned from the organization indicates a persistent error in the organization profile. When included in the list of codes, it is designed to output a permanent error (failed). is being structured. Consensus classification module (5), orchestration flow When it contains more than one sub-process, at least one of the sub-processes must be "Reconciled" 10 When it reaches the (Reconciled) status and at least one other subprocess has a persistent error (failed) or when in manual review mode, partial It is configured to output a partial completion result. Consensus classification module (5), none of the defined rules If they don't match, the process requires a manual review (manual_review_required), 15 It is structured to derive the result. Consensus classification module (5), defining the rules in a deterministic way, the same combination of inputs ensuring it always produces the same output, the rules are in the corporate profile. to ensure it is defined and can be customized to the specific needs of the institution. to ensure that the order of evaluation of the rules is fixed and 20 to ensure it is unchangeable, first directly checking for success, then to evaluate the results of the reverse operation, perform contradiction checking, identify persistent errors and to check for partial completion, apply the default rule, so that it is constant In order to prevent ambiguity between the rules, It is being structured. 25 The persistent state database and chain of evidence in the system of invention (1) module (6) permanently stores all events under the correlation ID of each transaction. save, delayed response, retry result, file fate record, reverse Combining the transaction response and final reconciliation class in the same transaction record, 30 To create the technical evidence for the consensus decision, as input; correlation identity and 12 Request, response, timeout, reverse operation generated by the operation status module (4), Receive each event record in the form of a delayed response or classification decision, as output; A timestamped and sequential chain of events, grouped under a correlation identity. It is structured to provide data in this format. The system of the invention includes repeatable single-process and data (1) The deduplication module (7) prevents the same operation from being triggered repeatedly, each operation a single transaction derived from the corporate profile and transaction parameters Generating an (idempotency) key, corresponding to this key before the transaction is executed. Searching for an incoming record in the permanent status database and evidence chain module (6); 10 If there is a record of a previously successful transaction, the process can be repeated. to prevent execution and to revert the current result It is being configured. Repeatable single-process and data deduplication module. (7), data deduplication control window time-based Defining it in the institutional profile, the control window, transaction count or unique 15 Configuring on a key-based system eliminates duplication in synchronous collection flows. to eliminate collection risk, payment, transfer or similar synchronous financial applicable to process flows, single derived from process parameters The operational key and existing records in the persistent state store are used as input. to get, "new operation-continue" or "duplicate operation-return current result" 20 It is structured to transmit decisions in the form of output. The invention concerns the institutional connection, adapter and conversion module in the system (1). (8), Representational State Transfer (REST), Simple Object Access Protocol (Simple Object Access Protocol - SOAP), application 25 programming interface (Application Programming Interface - API) and File File Transfer Protocol (FTP) / Secure File Transfer The protocol (Secure File Transfer Protocol - SFTP) is used by email and similar organizations. to support connection methods and connection parameters in the organization profile Selecting the appropriate adapter accordingly, data conversion and schema matching functions 30 to house organizational data in different formats into a common data model 13 to transform and ensure that the mapping / matching rules are derived from the organizational profile. It is structured to provide this. The orchestration module (9) in the system (1) which is the subject of the invention, integration flow Managing the sequence of technical steps and conditional branches within process 5 By working integrated with the status module (4), timeout and reverse operation branching It is configured to trigger. The monitoring and channel module (10) in the system (1) that is the subject of the invention, operational As a monitoring function, message details, error codes, task statuses, and technical information are displayed. To enable log tracking and to work towards operational visibility. The platform's banking products, business, as a channel and product integration function external servers in the form of services, channel applications and third-party systems It is configured to exchange data with (D). Third parties use different communication protocols, data formats, and connection models. In integrations carried out with partner institutions, the outcome of the transaction is uncertain. In cases where it remains undecided, it is technically impossible to determine a definite outcome, parametrically. implementing an integration based on the organization profile and reconciliation classification. The invention method developed to enable the process to be carried out (100); 20 - incoming online, outgoing online or offline file streaming required determining whether or not it exists, the parametric profile of the relevant institution. loading; connection type, timeout values, conversion the operation of the rules, the reverse transaction policy, and the single transaction rules transferring time into context (101), 25 - generating a unique correlation ID for the transaction, persistent state database. and a new transaction record under this identity in the evidence chain module (6) creation and operation status module (4) status “Started” adjustment (102), - Permanent status 30 with single-operation key derived from transaction parameters Searching in the database and evidence chain module (6) is the same as before 14 If there is a record that was successfully completed with the key, the process should be repeated. ensuring that it is not executed, reversing the current result and the flow termination (103), - source data is shared data according to the mapping rules in the organization profile. conversion to model 5, compression and decompression if necessary, decryption and signature 5 Performing verification procedures (104), - processed data, defined by the connection parameters in the organization profile. sending back in protocol and format and transaction status module (4) Switching to the “sent” status (105), - Waiting for a response within the timeout period defined in the organization profile, 10 If the response is received successfully, the transaction status module (4) will display “Completed”. the status module switches to this state if the timeout period expires. (4) Passing into the “statute of limitations” situation (106), - reverse transaction or situation according to the reverse transaction policy defined in the company profile. Sending the query request, the transaction status module (4) “Reverse transaction 15 The transition to the "triggered" state, when a reverse operation response is received, results in "Reverse operation". (107) - If the response to the original transaction is delayed after the timeout, the transaction status will be changed. If module (4) switches to the “Late response” status, the late response will be the current Evaluation together with the reverse process situation and the chain of evidence (108), 20 - by the agreement classification module (5), the status machine the current situation, the technical response codes returned from the institution, the reverse process the result and the delayed response information are evaluated together the sequential application of deterministic classification rules and the process Mapping to one of the final reconciliation classes, transaction “Reconciled”, error 25 or switching to manual inspection terminal status (109), - persistent state database of all events under correlation ID and The transaction record is stored in an integrated manner in the evidence chain module (6). finalization and transfer to the relevant agreement processes (110) It includes the following steps. 30 Industrial application of the invention The system (1) and method (100) subject to the invention are synchronous service calls and cycles connecting external file streams to the same decision engine, ensuring both stream types... 5 are combined under the same correlation ID through a single transaction record. monitoring and subjection to the same consensus classification mechanism, Transformation rules in the corporate profile are integrated with outcome-determining logic. his work, the orchestration output into predefined technical decision classes conversion: successful collection, cancellation-approved collection, included in reconciliation The final agreement in the form of a process that will not be carried out, requiring manual review, is 10. generation of classes, parametric reverse engineering based on institutional profile reverse engineering the interaction between the rules and the final status classification. trigger conditions, query steps, and final agreement class mapping to the institution. deriving specific profile parameters at runtime, the same correlation Under its identity, not only the record but also the chain of technical evidence that can be judged is 15 creation, delayed response, retry result, file fate record, and Reconciliation evidence obtained by combining them in the same transaction record as a result of reverse engineering. the generation of parameters in the organizational profile at runtime; routing, timeout, mapping, reverse engineering policy, and consensus jointly determining the classification rules, profile, execution behavior 20 It ensures the shaping of the entire thing. Around these fundamental concepts, the subject of the meeting is "Achievements Made with Institutions". A platform that enables integrations to be carried out under a single common platform. Developing a wide variety of applications related to "System (1) and Method (100)" 25 It is possible, and the invention is not limited to the examples described here, but is essentially As stated in the requests.

Claims

16 REQUESTS 1. Using different communication protocols, data formats, and connection models In integrations carried out with third-party institutions; transaction In situations where the outcome remains uncertain, there is technically no definite outcome. 5 determination, integration based on parametric institutional profile to ensure the execution and completion of the reconciliation classification process developed for this purpose; - technical integration features of each third-party institution into a single system. Maintaining a parametric profile structure; Representational State Transfer, Simple 10 Object Access Protocol is a link used for file transfer and email. type, certificate, application programming interface key, identifier security parameters in the form of verification method, connection timeout, read timeout, total transaction timeout Timeout values ​​in the following format: source format, target format, 15 reverse data transformation rules in the form of mapping / matching definitions transaction trigger condition, reverse transaction query endpoint, wait time, the inverse operation policy in the form of number of retries, again availability key production method, data deduplication control repeatability rules in the form of a window in a single structure 20 at least one parametric institutional profile structured to be combined database (2), - online incoming, online outgoing and offline file events are all the same. to ensure that it is combined under a canonical data model, for each operation generating a unique correlation identifier, this identifier, the life of the transaction 25 from the first trigger throughout the cycle to the final agreement class as a point of reference in all steps until its determination enabling the use of files in offline file streams by linking its rows or records to the same correlation structure, File-based operations are monitored in the same way as synchronous service operations, and 30 17 at least one partner structured to be subject to the decision-making mechanism data model and correlation identity module (3), - the lifecycle of each integration process in finite states and transitions Managing according to the rules; the process has been initiated, but it has not yet been transmitted to the other system. “Initiated” means the request has been sent to the receiving system, response 5 "Sent," meaning a successful response from the receiving system is expected. "Completed," meaning received, is defined in the organization profile. "Time has expired, no response received" "Expiration", time limit, or institution-specific adverse outcome due to uncertain result. “Reverse operation triggered”, meaning the operation / query step has been triggered, 10 "Reverse" means the reverse operation / query response has been received and evaluated. "Transaction approved", original response received after timeout. "Late response," meaning the transaction was mapped to the final reconciliation class, and "Reconciled" means finalized, the process has a permanent error. "Incorrect" means it has been concluded, and automatic classification 15 "Guide" means it couldn't be done, manual review is required. including "review" states, defining additional intermediate states. at least one process status module configured to provide (4), - the terminal states of the state machine are predefined final states mapping to agreement classes, classification rules institution 20 Drawing inspiration from the profile and applying it during working hours leads to success. collection, cancellation-approved collection, transaction not to be included in reconciliation, Manual review required, partial completion and permanent error. Defining consensus classes in this way, additional ones according to business needs. at least one 25 configured to enable the definition of classes Consensus Classification Module (5), - permanently records all events under the correlation ID of each transaction save, delayed response, retry result, file status record, Reverse transaction response and final reconciliation class in the same transaction record. combine, create technical evidence of the consensus decision, input 30 as; correlation identity and transaction status module (4) 18 generated request, response, timeout, reverse operation, delayed response, classification Taking a record of each event in the form of a decision, and outputting it as correlation. a chain of events unified under one identity, time-stamped and sequential. at least one persistent state configured to provide data in this format database and chain of evidence module (6), 5 - to prevent the same process from being triggered repeatedly, the institution requires a separate system for each process. a single-transaction key derived from profile and transaction parameters to generate, a corresponding key before the transaction is executed Search for the record in the permanent status database and evidence chain module (6); If there is a record that has been successfully completed before, the process can be repeated 10 times. to prevent execution and to revert the current result At least one structured, repeatable single-process operation and data. deduplication module (7), - Representative State Transfer, Simple Object Access Protocol, application Programming interface and File Transfer Protocol / Secure File 15 The Transfer Protocol supports email and similar institutional communication methods. to support and according to the connection parameters in the organization profile Selecting the appropriate adapter, data conversion and schema matching functions to host, common data of institutions in different formats converting it to a model and mapping / matching rules institution 20 at least one structured to ensure it feeds from its profile institutional connection, adapter and conversion module (8), - the sequence of technical steps and conditions within the integration flow to manage its branches, integrated with the process status module (4) 25 by working to trigger timeout and reverse operation branching. at least one orchestration module configured (9), - Message details, error codes, tasks as operational monitoring function to ensure the monitoring of status and technical records, operational working for visibility purposes, channel and product integration function as the platform's banking products, business services, channel 30 External servers in the form of applications and third-party systems (D) 19 at least one configured to exchange data with a system characterized by monitoring and channel module (10) (1).

2. Integration of the technical features of each third-party institution into a single system. Maintaining a parametric profile structure; Representational State Transfer, Simple Object 5 Access Protocol refers to the type of connection used for file transfer, email, etc. certificate, application programming interface key, authentication security parameters in the form of method, connection timeout, reading timeout, total transaction timeout in the form of timeout values, source format, target format, mapping / mapping definitions 10 data transformation rules in the form of reverse operation trigger condition, reverse operation The query endpoint displays the wait time in reverse morphological terms, specifically the number of retries. process policy, repeatability key production method, data repeatability rules in the form of a deduplication control window Parametric institutional profile data structured to be combined into a single structure 15 A system like the one in Claim 1, characterized by its base (2) (1).

3. Maintaining a versionable profile structure and having different profiles for the same institution. Storing parameters from different periods, new institutional integration. When activated, only profile definition 20 is changed without any code modification. by creating and enabling the determination of working time behavior, the institution Input the institutional identifier derived from the code or transaction context. Obtaining it in this way, the relevant institution's working time parameter set is output. providing it in this way, as connection type, timeout values, mapping Reference, reverse processing policy, repeatability rules and classification 25 Parametric institutional profile data structured to use its rules any of the above claims characterized by its base (2) such a system (1).

4. Online incoming, online outgoing, and offline file events are all the same 30 to ensure that it is combined under a canonical data model, for each operation generating a unique correlation identifier, this identifier, throughout the life of the process from the first trigger throughout the cycle to the final agreement class to be used as a reference point in all steps until its determination to provide file lines or records in offline file streams by connecting it to the same correlation structure, file-based operations are synchronized. 5 to subject service operations to the same monitoring and decision-making mechanisms with the structured common data model and correlation identity module (3) as in any of the above characterized claims system (1).

5. Input: Service response, file record, or application received from the institution. raw data and processing context in the form of a programming interface request to receive, as output, the transaction data converted into a canonical data model, and Collaborative data structured to yield a unique correlation identifier. The above 15 is characterized by the model and correlation identity module (3). a system like any of the requests (1).

6. The lifecycle of each integration operation consists of finite states and transitions. Managing according to the rules; the process has been initiated, but it has not yet been transmitted to the other system. “Initiated” means the request has been sent to the receiving system and a response is awaited. 20 "Transmitted" means that a successful response has been received from the other system. The message received says "Completed," indicating that the timeout period defined in the organization profile has expired. "Timeout," meaning no response was received, also known as time-out or uncertain. This means that an institution-specific reverse process / query step was triggered due to the result. The incoming message was “Reverse operation triggered”, reverse operation / query response received and 25 “Reverse transaction approved”, meaning it has been evaluated, timeout. "Late response" means that the original response was received after a delay in processing. It means it has been mapped to the final agreement class and finalized. “Reconciled” means the transaction resulted in a permanent error, while “Error” means the transaction ended in a permanent error. Automatic classification could not be performed, meaning manual review is required. 30 21 including incoming “guide review” statuses, additional intermediate statuses with the process status module (4) configured to enable its identification as in any of the above characterized claims system (1).

7. Define transition rules using parameters in the organization profile, “Sent” In this case, when the statute of limitations expires, it is marked as "Statute of Limitations". to pass, reverse action policy in the institution profile in case of "Timeout" If defined, switching to the "Reverse operation triggered" state, reverse operation response Upon receipt, it switches to the "Reverse transaction confirmed" status and reconciliation 10 to transfer to classification module (5) if the original response is received late Switching to a "delayed response" state and within the context of the current state machine. with the transaction status module (4) configured for evaluation as in any of the above characterized claims system (1). 15 8. Current status, triggering event, and transition rules in the organization profile. Taking the input, the new state and the triggered action as output. characterized by the process status module (4) which is configured to give a system like any of the above requests (1). 20 9. Predefined final reconciliation of the state machine's terminal states. matching to classes, classification rules are based on the institution's profile. and agreement structured to be implemented during working hours 25 of the above requests characterized by the classification module (5) a system like any other (1).

10. Successful collection, cancellation-approved collection, transaction not to be included in reconciliation, Manual review required, partial completion and permanent error. Defining consensus classes in this way, adding additional classes according to business needs. 30 22 consensus classification structured to enable identification any of the above requests characterized by module (5) a system like one of them (1).

11. The terminal or pre-terminal status of the status machine is 5 from the institution. returned technical response codes, information about delayed responses, and the organization profile. Taking data in the form of classification rules as input, the final The data is output in the form of agreement class and reason for assignment. with the reconciliation classification module (5) structured to give a 10 as in any of the above characterized claims system (1).

12. When the transaction status module (4) is in the “Completed” state, from the institution The returned technical response code is included in the list of success codes in the organization profile. When received and in the absence of a delayed or contradictory response, successful collection is 15. a consensus classification module structured to derive the result (5) like any of the above-mentioned claims characterized by system (1).

13. When the transaction status module (4) is in the “Reverse transaction confirmed” state, 20 Reverse operation response code, "operation not found" codes in the organization profile when it is on the list and there is no late, contradictory response, to deduce the transaction result that will not be included in the agreement characterized by the structured consensus classification module (5) a system like any of the above requests (1). 25 14. When the transaction status module (4) is in the “Reverse transaction confirmed” state, The reverse transaction response code is "transaction cancelled / reversed" in the organization profile. when it is included in the list of codes and there is no late, contradictory response In this case, 30 is configured to generate a cancellation-approved collection result. 23 The above is characterized by the consensus classification module (5). a system like any of the requests (1).

15. When the transaction status module (4) is in the “Delayed response” state, the delayed response when the original response contains a success code and the reverse operation response is "operation 5" When the code contains "not found" or "transaction cancelled", manual review is required. reconciliation structured to derive the result of the required operation from the above requests characterized by the classification module (5) a system like any other (1).

16. Transaction status module (4) From “Sent” status directly to “Error” When this situation occurs, the technical response code returned from the institution When it appears in the list of persistent error codes in your profile, it is a persistent error. a consensus classification module structured to derive the result (5) like any of the above-mentioned claims characterized by 15 system (1).

17. When the orchestration flow contains more than one sub-operation, at least one of the sub-operations must be present. when one reaches the “Reconciled” status and at least one other sub-process remains permanent In case of error or manual review, partial completion 20 a consensus classification module structured to derive the result (5) like any of the above-mentioned claims characterized by system (1).

18. When none of the defined rules match, 25 requires manual review. reconciliation classification structured to derive the result of the transaction any of the above requests characterized by module (5) a system like one of them (1). 24 19. Defining rules deterministically, using the same input The rules ensure that the combination always produces the same output. to ensure it is defined in the organization profile and is specific to the organization to ensure customizability, the order in which the rules are evaluated To ensure it is fixed and unchangeable, first 5 directly check the success, then the reverse operation results. to evaluate, check for contradictions, identify persistent errors and partial errors to check for completion, apply the default rule, so it stays constant In order to prevent ambiguity between the rules, 10 characterized by the structured consensus classification module (5) a system like any of the above requests (1).

20. Permanently record all events under the correlation ID of each transaction. save, delayed response, retry result, file fate record, reverse Combining the transaction response and final reconciliation class in the same transaction record, 15 To create the technical evidence for the consensus decision, the input is correlation. Request, response, time generated by the identity and transaction status module (4) any event such as overrun, reverse operation, delayed response, classification decision to record it, output; combined under correlation ID, 20 to provide data in the form of timestamped and sequential event chains. with the structured persistent state database and evidence chain module (6) as in any of the above characterized claims system (1).

21. To prevent the same process from being triggered repeatedly, the institution requires 25 for each process. a single-transaction key derived from profile and transaction parameters to generate a record corresponding to this key before the transaction is executed Search in the permanent status database and evidence chain module (6); if more If a successful transaction has already been completed, the process should not be repeated. 30 configured to provide and return the current result with repeatable single-process and data deduplication module (7) as in any of the above characterized claims system (1).

22. Data deduplication control window time-based institution 5 Defining it in the profile, the control window, transaction count or unique Configuring on a key-based system eliminates duplication in synchronous collection flows. to eliminate collection risk, payment, transfer or similar synchronization applicable to financial transaction flows, transaction parameters the derived single-operation key and the existing 10 in the persistent state store Receiving records as input, "new transaction - continue" or "duplicate" Decisions such as "operation - return current result" are communicated as output. repeatable single-transaction processing and data deduplication structured accordingly. any of the above requests characterized by module (7) a system like one of them (1). 15 23. Representative State Transfer, Simple Object Access Protocol, application Programming interface and File Transfer Protocol / Secure File The Transfer Protocol supports email and similar institutional communication methods. to support and suitable 20 according to the connection parameters in the organization profile selecting the adapter, including data conversion and schema mapping functions, to transform organizational data in different formats into a common data model and To ensure that mapping / matching rules are derived from the organization's profile. with the institution connection, adapter and conversion module (8) configured for a 25 as in any of the above characterized claims system (1).

24. The sequence of technical steps and conditions within the integration flow. to manage its branches by working integrated with the process status module (4) 30 configured to trigger timeout and reverse operation branching. 26 from the above requests characterized by the orchestration module (9) a system like any other (1).

25. Operational monitoring function: message details, error codes, tasks To ensure the monitoring of status and technical records, operational 5 working for visibility purposes, as a channel and product integration function. the platform's banking products, business services, channel applications and third-party data exchange with external servers (D) in the form of side systems with the monitoring and channel module (10) configured to perform a 10 as in any of the above characterized claims system (1).

26. Using different communication protocols, data formats, and connection models. In integrations carried out with third-party institutions; transaction In situations where the outcome remains uncertain, there is technically no definite outcome. 15 determination, integration based on parametric institutional profile to ensure the execution and completion of the reconciliation classification process developed for this purpose; - incoming online, outgoing online or offline file streaming required determining whether or not it exists, the parametric profile of the relevant institution 20 loading; connection type, timeout values, conversion the operation of the rules, the reverse transaction policy, and the single transaction rules transferring time into context (101), - generating a unique correlation ID for the transaction, persistent state database. and in the evidence chain module (6) a new transaction record under this identity 25 creation and operation status module (4) status “Started” adjustment (102), - Persistent status with a single-operation key derived from transaction parameters Searching in the database and evidence chain module (6) is the same as before If there is a record that was successfully completed with the key, the process will be repeated 30 27 ensuring that it is not executed, reversing the current result and the flow termination (103), - source data is shared data according to the mapping rules in the organization profile. conversion to the model, compression, decompression, decryption and signing if necessary. Performing verification procedures (104), 5 - processed data, defined by the connection parameters in the organization profile. sending back in protocol and format and transaction status module (4) Switching to the “sent” status (105), - Waiting for a response within the timeout period defined in the organization profile, If the response is received successfully, the transaction status module (4) will display “Completed” 10 the status module switches to this state if the timeout period expires. (4) Passing into the “statute of limitations” situation (106), - reverse transaction or situation according to the reverse transaction policy defined in the company profile. Sending the query request, the transaction status module (4) “Reverse transaction The transition to the "triggered" state, when a reverse operation response is received, results in "Reverse operation 15". (107) - If the response to the original transaction is delayed after the timeout, the transaction status will be changed. If module (4) switches to the “Late response” status, the late response will be the current Evaluation of the reverse process situation and the chain of evidence (108), - by the agreement classification module (5), the status machine 20 the current situation, the technical response codes returned from the institution, the reverse process the result and the delayed response information are evaluated together the sequential application of deterministic classification rules and the process Mapping to one of the final reconciliation classes, transaction “Reconciled”, error or switching to manual inspection terminal status (109), 25 - persistent state database of all events under correlation ID and The transaction record is stored in an integrated manner in the evidence chain module (6). finalization and transfer to the relevant agreement processes (110) a method characterized (100).

Images