The invention provides improved verification solutions for blockchain-implemented transfers. It is suited for, but not limited to, implementation in an SPV wallet. In accordance with one embodiment, a system or resource is provided which comprises a plurality of novel SPV verification components, the activities of which are coordinated by a coordination component. The system enables Bob to send Alice a payment transaction template (template Tx3) and requests: the full transaction data for all input transactions (Tx1, Tx2) comprising at least one output that Alice wants to spend as inputs to a transfer (Tx3); the Merkle path for all input transactions (Tx1, Tx2) linking them to their respective Merkle roots associated with their respective block headers; the completed transfer transaction (Tx3). Alice provides this information plus her signature. Bob can then perform local SPV checks on the input transactions Tx1, Tx2 using transactions Tx1 and Tx2, their corresponding Merkle paths Path 1, Path 2, and Bob's local list of block headers. Bob broadcasts the transfer transaction (Tx3) to the P2P network.

The invention provides improved verification solutions for blockchain-implemented transfers. It is suited for, but not limited to, implementation in an SPV wallet. In accordance with one embodiment, a method, system or resource is provided which enables Alice to transfer an asset eg cryptocurrency or token to Bob across a blockchain. Alice stores complete transaction data relating to at least one blockchain transaction; and the complete Merkle path of the at least one blockchain transaction. This enables her to send Bob the full transaction data for all input transactions (eg Tx1, Tx2) comprising at least one output that she wants to spend as inputs to a transfer (eg Tx3); the Merkle path for all input transactions (Tx1, Tx2) linking them to their respective Merkle roots associated with their respective block headers; a transfer transaction (Tx3). Alice also provides her signature. Bob is then able to perform local SPV checks on the input transactions Tx1, Tx2 using transactions Tx1 and Tx2, their corresponding Merkle paths Path 1, Path 2, and his local list of block headers. Bob broadcasts the transfer transaction (Tx3) to the P2P network.

An approach is disclosed on a blockchain platform for one or more intermediaries for receiving an encrypted file from a user for storage on the blockchain platform. Mapping the user to be the owner of the encrypted file. Receiving one or more security policy parameters for the encrypted file from the owner. Enforcing the security policy parameters for all access requests to the file on the blockchain platform. Optionally providing audit report of the encrypted file storage and access. The owner may be established using past read or write transactions. The encrypted file may be divided into two or more parts before sending for storage on the blockchain platform.

In some embodiments, exemplary user interfaces for provisioning an electronic device with an account are described. In some embodiments, exemplary user interfaces for providing usage information of an account are described. In some embodiments, exemplary user interfaces for providing visual feedback on a representation of an account are described. In some embodiments, exemplary user interfaces for managing the tracking of a category are described. In some embodiments, exemplary user interfaces for managing a transfer of items are described. In some embodiments, exemplary user interfaces for managing an authentication credential connected with an account are described. In some embodiments, exemplary user interfaces for activating a physical account object are described. In some embodiments, exemplary user interfaces for managing balance transfers are described.

Described herein is a system for providing version control across APIs. In an embodiment, an application of a client device may transmit communications to a service application API that are in a format not accepted by the service application API, using the application API. A central (or public) API may receive the communication transmitted by the application's API. The central API may identify the versions of the application's API and the service application API. The central API may format the communication based on the mapped fields, to a format accepted by the service application API. The central API 106 may forward the formatted communication to the service application.

Aspects of the disclosure relate to cash handling devices that provide intelligent monitoring and management of cash cycles. A cash handling device having at least one processor, a communication interface, and memory may receive, from a mobile device, a request to process a pre-staged transaction. Subsequently, the cash handling device may generate and present a graphical identifier based on the mobile device requesting access to the cash handling device. Next, the cash handling device may verify that the mobile device is authorized to perform the pre-staged transaction based on the graphical identifier being scanned by the mobile device and cause a connection to be established between the cash handling device and the mobile device. Thereafter, the cash handling device may identify and process the pre-staged transaction associated with the mobile device. Then, the cash handling device may generate a notification indicating completed processing of the identified pre-staged transaction.

Aspects of the disclosure relate to cash handling devices that provide intelligent monitoring and management of cash cycles. A cash handling device having at least one processor, a communication interface, and memory may receive, from a mobile device, a request to process a pre-staged transaction. Subsequently, the cash handling device may generate and present a graphical identifier based on the mobile device requesting access to the cash handling device. Next, the cash handling device may verify that the mobile device is authorized to perform the pre-staged transaction based on the graphical identifier being scanned by the mobile device and cause a connection to be established between the cash handling device and the mobile device. Thereafter, the cash handling device may identify and process the pre-staged transaction associated with the mobile device. Then, the cash handling device may generate a notification indicating completed processing of the identified pre-staged transaction.

Aspects of the disclosure relate to cash handling devices that provide intelligent monitoring and management of cash cycles. A cash handling device having at least one processor, a communication interface, and memory may receive, from a mobile device, a request to process a pre-staged transaction. Subsequently, the cash handling device may generate and present a graphical identifier based on the mobile device requesting access to the cash handling device. Next, the cash handling device may verify that the mobile device is authorized to perform the pre-staged transaction based on the graphical identifier being scanned by the mobile device and cause a connection to be established between the cash handling device and the mobile device. Thereafter, the cash handling device may identify and process the pre-staged transaction associated with the mobile device. Then, the cash handling device may generate a notification indicating completed processing of the identified pre-staged transaction.

Systems and methods of remotely configuring a transaction based, in part, on location information for execution by a computing device associated with a financial institution computing system include a backend system configured to receive location information associated with a user device, determine the location information associated with the user device matches a location configured for pre-staging an ATM transaction, transmit an ATM pre-stage authorization signal to the user device, transmit an authentication decision to the user device, and transmit a transaction code to the user device.

A dynamic transaction card comprising an outer surface, a sensor, and a display disposed on the outer surface is disclosed. The dynamic transaction card can include an antenna and a microcontroller controlling a dynamic transaction card application. The dynamic transaction card can also include a secure payment chip having a plurality of contact points and storing a passive tag associated with a user. The passive tag can include a unique identifier and one or more log-in credentials for the user. When making a purchase, the user can be authenticated via a connection between the dynamic transaction card and a user device. The unique identifier can be used as an authentication token and the one or more log-in credentials can be verified against log-in credentials associated with the user.