Abstract: Systems and methods for transforming data for a batch-based legacy software program into data suitable for processing by a streaming-based new software program. In some aspects, the system generates an information stream for multiple threads from batch information received from the legacy software program. The system processes the information stream for the multiple threads using the new software program. If there is a mismatch between outputs of the legacy and new software programs for at least one thread, the system adjusts a data model of the new software program to address the mismatch and generates an updated information stream for processing by the new software program.

Abstract: Systems and methods for determining that a new software program is in parity with a legacy software program. In some aspects, the system receives information for multiple threads processed by a legacy software program. The system processes the information using the new software program, which is executed in parallel with the legacy software program. If an output of a particular thread from the new software program varies outside a threshold distance from a corresponding output for the thread from the legacy software program, the system ceases further processing of the particular thread by the new software program. Otherwise, the system allows processing of the particular thread by the new software program to continue.

Abstract: Systems and methods for migrating data from a legacy software program to a new software program. In some aspects, the system captures a snapshot of the current state of static data for multiple threads from the legacy software program. The system processes the static data for the multiple threads using the new software program to generate dynamic data for a period of time. During the same period of time, the legacy software program also produces dynamic data for the multiple threads. If there is a mismatch between dynamic data from the new and legacy software programs for at least one thread, the system generates metadata for the at least one thread to supplement static data for the at least one thread for processing by the new software program.

Abstract: Systems and methods for determining a difference in performance for a software program processing input data for multiple threads based on different termination time periods for handling an exception. In some aspects, the system receives input data and corresponding performance data for multiple threads with respect to a first termination time period for terminating the thread when an exception is detected. The system processes the input data to generate corresponding performance data for the multiple threads with respect to a second termination time period for terminating the thread when the exception is detected. The system determines a difference in performance for a particular thread based on performance data with respect to the first termination time period and corresponding performance data with respect to the second termination time period.

Abstract: Systems and methods for transforming data for a batch-based legacy software program into data suitable for processing by a streaming-based new software program. In some aspects, the system generates an information stream for multiple threads from batch information received from the legacy software program. The system processes the information stream for the multiple threads using the new software program. If there is a mismatch between outputs of the legacy and new software programs for at least one thread, the system adjusts a data model of the new software program to address the mismatch and generates an updated information stream for processing by the new software program.

Abstract: A real-time third-party payment system accepts payments to a lender from third-party merchants in real-time. The payment system may receive real-time payment information from the third-party, and various services within the payment system validate the customer account information, create a payment, store the payment in a database, and post the payment to a real-time ledger. The payment system may also receive an end-of-day file including file-based payment information. The file-based payment information may be verified against the real-time payments stored in the database. Upon validation, the payment system creates a file based payment and posts the file-based payment to a file-based ledger. The payment system may detect fraud, errors, and other discrepancies in real-time payments and make corrections based on settlement rules and self-healing rules provided by the third-party.

Abstract: A real-time third-party payment system accepts payments to a lender from third-party merchants in real-time. The payment system may receive real-time payment information from the third-party, and various services within the payment system validate the customer account information, create a payment, store the payment in a database, and post the payment to a real-time ledger. The payment system may also receive an end-of-day file including file-based payment information. The file-based payment information may be verified against the real-time payments stored in the database. Upon validation, the payment system creates a file based payment and posts the file-based payment to a file-based ledger. The payment system may detect fraud, errors, and other discrepancies in real-time payments and make corrections based on settlement rules and self-healing rules provided by the third-party.