# US 10,372,762 B1 · Systems and methods for improved transactional mainframes > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,372,762 B1 - Document ID: US10372762B1 - Status: Granted - Kind: B1 - Application number: 16/005,075 - Filed: 2018-06-11 - Granted: 2019-08-06 - Earliest claimed: 2018-06-11 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Marc Hudak; Swathi Challkere Vijayaprakash; Matthew Coleman; Ashish Bassi; Anurag Andoji; Joe Vaughan; PhaniKrishna Hari; Michael Garner - Web page: https://patentgrep.com/patent/US10372762B1 ## CPC - G06F 16/2365: {Ensuring data consistency and integrity} - G06F 16/90335: {Query processing} - G06F 16/1865: {Transactional file systems} - G06F 16/2386: {Bulk updating operations (data conversion details G06F16/258)} - G06F 16/258: {Data format conversion from or to a database} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract In one aspect, the present disclosure relates to a system for improved transactional mainframes, the system comprising a processor, a database, an application programming interface (API) module, and a transaction import module. The API module can be configured to: receive transaction data comprising a transaction type, a user identifier, one or more transaction card identifiers, and one or more fields associated with the transaction card identifiers; validate the transaction data using one or more of the stored validation rules associated with the one or more transaction card identifiers; generate one or more transaction cards; and store the transaction data and transaction cards to the database. The transaction import module can be configured to submit the transaction cards to the mainframe, view the status of submitted records, and enable retrying of transaction cards that failed to process. ## Claims ### Claim 1 A system for improved transactional mainframes, the system comprising: a processor; a database for storing validation rules for one or more transaction card data formats supported by a transactional mainframe; and a storage medium for storing instructions executable by the processor that, when executed, cause the processor to: receive, from an application executing on a computing device, transaction data comprising a transaction type, a user identifier associated with the application, one or more transaction card identifiers, and one or more fields associated with the transaction card identifiers, the transaction data having a data format different from the one or more transaction card data formats supported by the transactional mainframe; validate the transaction data using one or more of the stored validation rules associated with the one or more transaction card identifiers; generate one or more transaction cards based on the validated transaction data; store the transaction data and transaction cards in the database; and send a success response to the application; submit the transaction cards to the transactional mainframe; determine that a first one of the transaction cards was successfully imported into the transactional mainframe; store, to the database, an indication that the first one of the transaction cards was successfully imported into the transactional mainframe; determine a batch transaction import should run based on a current time and a predetermined import schedule; query the database for one or more transaction cards that have not been successfully imported into the transactional mainframe; and submit the one or more transaction cards that have not been successfully imported into the transactional mainframe. ### Claim 2 (depends on 1) The system of claim 1 wherein the instructions, when executed, cause the processor to: generate a batch file comprising the one or more transaction cards that have not been successfully imported into the transactional mainframe; and import the batch file into the transactional mainframe. ### Claim 3 (depends on 2) The system of claim 2 wherein the instructions, when executed, cause the processor to group related transaction cards together within the batch file. ### Claim 4 (depends on 1) The system of claim 1 where the transaction data has a data format that is one of JavaScript Object Notation (JSON) or Extensible Markup Language (XML). ### Claim 5 (depends on 1) The system of claim 1 wherein the one or more transaction card data formats comprise a fixed-length string of characters with a defined set of options for each position in the string. ### Claim 6 (depends on 1) The system of claim 1 where the transaction data comprises two or more transaction card identifiers. ### Claim 7 (depends on 1) The system of claim 1 wherein the stored validation rules associated with the one or more transaction card identifiers comprise a rule specifying that transaction data must comprise one required fields and a rule specifying that transaction data may comprise one or more optional fields. ### Claim 8 (depends on 1) The system of claim 1 wherein the instructions, when executed, cause the processor to: determine that a second one of the transaction cards failed to import into the transactional mainframe; and store, to the database, an indication that the second one of the transaction cards failed to import into the transactional mainframe. ### Claim 9 (depends on 1) The system of claim 1 wherein the instructions, when executed, cause the processor to: present one or more UI controls for re-submitting transactions that failed to import into the transactional mainframe; and present one or more UI controls for rolling back transactions that were successfully imported into the transactional mainframe. ### Claim 10 A method for improving transactional mainframe systems, the method comprising: receiving, from an application executing on a computing device, transaction data comprising a transaction type, a user identifier associated with the application, one or more transaction card identifiers, and one or more fields associated with the transaction card identifiers, the transaction data having a data format different from one or more transaction card data formats supported by a transactional mainframe; retrieving, from a database, validation rules for the one or more transaction card data formats supported by a transactional mainframe; validating the transaction data using one or more of the stored validation rules associated with the one or more transaction card identifiers; generating one or more transaction cards based on the validated transaction data; storing the transaction data and transaction cards in the database; sending a success response to the application; submitting the transaction cards to the transactional mainframe; determining that a first one of the transaction cards was successfully imported into the transactional mainframe; storing, to the database, an indication that the first one of the transaction cards was successfully imported into the transactional mainframe; determining a batch transaction import should run based on a current time and a predetermined import schedule; and in response to determining the batch transaction import should run: querying the database for one or more transaction cards that have not been successfully imported into the transactional mainframe, and submitting the one or more transaction cards that have not been successfully imported into the transactional mainframe. ### Claim 11 (depends on 10) The method of claim 10 comprising: determining a batch transaction import should run based on a current time and a predetermined import schedule; and in response to determining the batch transaction import should run: querying the database for one or more transaction cards that have not been successfully imported into the transactional mainframe, and submitting the one or more transaction cards that have not been successfully imported into the transactional mainframe. ### Claim 12 (depends on 11) The method of claim 11 comprising: generating a batch file comprising the one or more transaction cards that have not been successfully imported into the transactional mainframe; and importing the batch file into the transactional mainframe. ### Claim 13 (depends on 12) The method of claim 12 comprising grouping related transaction cards together within the batch file. ### Claim 14 (depends on 10) The method of claim 10 where the transaction data has a data format that is one of JavaScript Object Notation (JSON) or Extensible Markup Language (XML). ### Claim 15 (depends on 10) The method of claim 10 wherein the one or more transaction card data formats comprise a fixed-length string of characters with a defined set of options for each position in the string. ### Claim 16 (depends on 10) The method of claim 10 where the transaction data comprises two or more transaction card identifiers. ### Claim 17 (depends on 10) The method of claim 10 comprising: determining that a second one of transaction cards failed to import into the transactional mainframe; and storing, to the database, an indication that the second one of the transaction cards failed to import into the transactional mainframe. ### Claim 18 (depends on 17) The method of claim 17 comprising, in response to user input, re-submitting the second one of the transaction cards to the transactional mainframe. ### Claim 19 A system for improved transactional mainframes, the system comprising: a processor; a database for storing validation rules for one or more transaction card data formats supported by a transactional mainframe; and a storage medium for storing instructions executable by the processor that, when executed, cause the processor to: receive, from an application executing on a computing device, transaction data comprising a transaction type, a user identifier associated with the application, one or more transaction card identifiers, and one or more fields associated with the transaction card identifiers, the transaction data having a data format different from the one or more transaction card data formats supported by a transactional mainframe; validate the transaction data using one or more of the stored validation rules associated with the one or more transaction card identifiers; generate one or more transaction cards based on the validated transaction data; store the transaction data and transaction cards in the database; send a success response to the application; determine a batch transaction import should run based on a current time and a predetermined import schedule; query the database for one or more transaction cards that have not been successfully imported into the transactional mainframe; submit the one or more transaction cards that have not been successfully imported into the transactional mainframe; submit the transaction cards to the transactional mainframe; determine that a first one of the transaction cards was successfully imported into the transactional mainframe; store, to the database, an indication that the first one of the transaction cards a successfully imported into the transactional mainframe; present one or more UI controls for re-submitting transactions that failed to import into the transactional mainframe; and present one or more UI controls for rolling back transactions that were successfully imported into the transactional mainframe.