Abstract: The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto-generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.

Abstract: Described herein are techniques that employ a data engine for providing service to endpoints such as automated banking machines. For example, when a maintenance task is to be performed, the appropriate skill and parts for completing the task are determined. A maintenance technician is selected to perform the maintenance task who is the closet technician to the endpoint that has the appropriate skill and part. The data engine is also operable to gather and correlate data for the various components of the endpoint and determine predictive and proactive actions for maintaining the components.

Abstract: The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto-generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.

Abstract: The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.

Abstract: A cash-dispensing banking terminal has a housing, a transmitter, a receiver, a cash dispenser, and a processor to control the cash dispenser. A pre-created transaction request was earlier created with a mobile device before a banking customer and the mobile device arrive at the cash-dispensing banking terminal. A remote computing device authenticates and authorizes the transaction request before the customer and the mobile device arrive at the cash-dispensing banking terminal. When the transaction is authenticated and authorized, a remote computer generates an executable transaction request and generates and sends a transaction identifier associated with an executable transaction request to the mobile device. The receiver receives the transaction identifier from the mobile device, when the customer is at the banking terminal. The remote computer and/or other devices verify the transaction identifier is valid. The banking terminal performs the transaction request while the customer is at the banking terminal.

Abstract: The invention relates to a system that implements application lineage metadata and registration. An embodiment of the present invention is directed to auto generating Application Lineage data. This may be accomplished by implementing code markers, such as @Annotations, within the code. An embodiment of the present invention may scan the code each time a build is kicked off by a continuous integration and continuous delivery (CI/CD) pipeline. At the end of the build, the documentation may be automatically generated with application lineage information.

Abstract: A cash-dispensing banking terminal can execute a transaction request created with a mobile device before a banking customer and the mobile device arrive at the cash-dispensing banking terminal. A remote computing device authenticates and authorizes the transaction request. When the transaction is authenticated and authorized, the remote computing device generates an executable transaction request and sends a transaction identifier to the mobile device. The receiver receives the transaction identifier from the mobile device, when the customer is at the banking terminal. The remote computer and/or other devices verify the transaction identifier is valid. The banking terminal performs the transaction request while the customer is at the banking terminal. The amount of the cash withdrawal is pre-deducted from the banking account of the banking customer before the banking customer is at the banking terminal.

Abstract: A cash-dispensing banking terminal has a housing, a transmitter, a receiver, a cash dispenser, and a processor to control the cash dispenser. A pre-created transaction request was earlier created with a mobile device before a banking customer and the mobile device arrive at the cash-dispensing banking terminal. A remote computing device authenticates and authorizes the transaction request before the customer and the mobile device arrive at the cash-dispensing banking terminal. When the transaction is authenticated and authorized, a remote computer generates an executable transaction request and generates and sends a transaction identifier associated with an executable transaction request to the mobile device. The receiver receives the transaction identifier from the mobile device, when the customer is at the banking terminal. The remote computer and/or other devices verify the transaction identifier is valid. The banking terminal performs the transaction request while the customer is at the banking terminal.