Abstract: Arrangements for providing secure document distribution are provided. In some aspects, a request to distribute a file may be received. The request may include identification of the file being distributed, as well as identification of a recipient. The identified file may be encrypted and stored in a distributed hash table. In some examples, a file reference key associated with the encrypted file may be generated and stored in a distributed ledger. A secure QR code based on the file reference key may be generated and transmitted to a recipient computing device. In some arrangements, an indication of a scan of the secure QR code may be received. Responsive to receiving the indication of the scan, the file reference key may be retrieved and a decrypted file of the encrypted file may be generated and provided to the recipient for viewing and/or downloading.

Abstract: Arrangements for account linking and dynamic device selection are provided. Registration data including one or more user accounts and/or payment devices may be received. A request to process a transaction may be received via a first device. User data may be retrieved to identify other devices. One or more external entities may provide user profile data including raw customer data and encrypted authentication data. A hash of the encrypted authentication data may be generated and stored. The system may dynamically generate a rendering displaying one or more payment devices available for selection. A second payment device may be selected and a handshake protocol initiated between a vendor device and a user device. Authentication data may be provided and a hash generated. The hashes may be compared and, if a match occurs, the transaction may be processed.

Abstract: Arrangements for account linking and dynamic device selection are provided. Registration data including one or more user accounts and/or payment devices may be received. A request to process a transaction may be received via a first device. User data may be retrieved to identify other devices. One or more external entities may provide user profile data including raw customer data and encrypted authentication data. A hash of the encrypted authentication data may be generated and stored. The system may dynamically generate a rendering displaying one or more payment devices available for selection. A second payment device may be selected and a handshake protocol initiated between a vendor device and a user device. Authentication data may be provided and a hash generated. The hashes may be compared and, if a match occurs, the transaction may be processed.

Abstract: Arrangements for account linking and dynamic device selection are provided. Registration data including one or more user accounts and/or payment devices may be received. A request to process a transaction may be received via a first device. User data may be retrieved to identify other devices. One or more external entities may provide user profile data including raw customer data and encrypted authentication data. A hash of the encrypted authentication data may be generated and stored. The system may dynamically generate a rendering displaying one or more payment devices available for selection. A second payment device may be selected and authentication data associated with the second payment device received. A hash of the authentication data may be generated and compared to the stored hash of the encrypted authentication data. If the hashes match, the transaction may be processed. If there is not a match, the transaction may be denied.