Abstract: A computing system can receive, from a mobile application executing on a mobile device, at least one image that has been captured on the mobile device and corresponds to an interaction. The computing system can extract interaction data from each image. The computing system can transmit a notification to the mobile device indicating that the interaction data has been extracted from the images. The computing system can receive a request to transmit the plurality of interactions to an entity server for processing. The computing system can generate, based on the interaction data, an application programming interface request that is configured to cause the entity server to process the plurality of interactions. The computing system can transmit the application programming interface request to the entity server and receive a confirmation from the entity server that the plurality of interactions have been processed.

Abstract: A remote deposit capture (RDC) processing anomaly detection and remediation tool that can communicate with the RDC system over a network, and determine whether a RDC transaction is missing from the RDC system by comparing created and assigned unique identifiers represented in RDC transaction data received at a selected RDC system location or component with unique identifiers represented in RDC transaction data received at a RDC system location or component that is upstream thereof. In response to finding a missing RDC transaction, the tool can determine one or more RDC system remediation actions, execute the one or more RDC system remediation actions on the RDC system, and report the missing RDC transaction and any RDC system remediation actions executed on the RDC system.

Abstract: A computing system can receive, from a mobile application executing on a mobile device, at least one image that has been captured on the mobile device and corresponds to an interaction. The computing system can extract interaction data from each image. The computing system can transmit a notification to the mobile device indicating that the interaction data has been extracted from the images. The computing system can receive a request to transmit the plurality of interactions to an entity server for processing. The computing system can generate, based on the interaction data, an application programming interface request that is configured to cause the entity server to process the plurality of interactions. The computing system can transmit the application programming interface request to the entity server and receive a confirmation from the entity server that the plurality of interactions have been processed.

Abstract: A remote deposit capture (RDC) monitoring tool in the form of a computerized system that can communicate with the RDC system over a network, receive RDC transaction data for RDC transactions initiated within some period of time, and create and assign to each RDC transaction, a unique identifier comprising selected items of deposit information. The system can compare the unique identifiers associated with RDC transaction data at a selected layer or component of the RDC system with the unique identifiers associated with RDC transaction data at a downstream layer or component. The system can determine, in response to the comparison of unique identifiers, that a unique identifier and corresponding RDC transaction are missing from the downstream layer or component, while storing and processing only a fraction of the total information included in the RDC transaction data received from the RDC system.

Abstract: File status updates can be proactively monitored in transaction systems. For example, a system can send an X9 file comprising transaction data associated with a plurality of transactions to a downstream transaction processing system. The system can receive, via an X9 file status application programming interface (API), a message indicating a status of the X9 file. The X9 file status API can be configured to receive the message from a listener system monitoring for X9 file status updates. The system can cause an action based on the status of the X9 file.