Hosting account linking services to enable dynamic authentication and multi-computer event processing

A method, comprising:

• receiving, by a computing platform, the computing platform having at least one processor and memory registration data, the registration data including data associated with a plurality of payment devices associated with a user, each payment device of the plurality of payment devices being associated with a respective entity;
• receiving, by the at least one processor and via a vendor computing device, a request to initiate a transaction, the request to initiate the transaction including a customer identifier;
• retrieving, by the at least one processor and based on the customer identifier, user information associated with the user;
• transmitting, by the at least one processor and via a secure application programming interface (API) call method, a request for user profile data to each respective entity associated with each payment device of the plurality of payment devices;
• receiving, by the at least one processor and from each respective entity associated with each payment device of the plurality of payment devices, user profile data, the user profile data including encrypted authentication data associated with each respective payment device and raw user data;
• segregating, by the at least one processor, the encrypted authentication data from the raw user data for each user profile received;
• generating, by the at least one processor and for each user profile received, an encrypted hash of the segregated encrypted authentication data;
• storing, by the at least one processor and for each user profile received, the encrypted hash of the segregated encrypted authentication data;
• dynamically generating, by the at least one processor, a rendering including each payment device of the plurality of payment devices;
• transmitting, by the at least one processor, the rendering to the vendor computing device;
• receiving, by the at least one processor and from the vendor computing device, selection of a first payment device of the plurality of payment devices;
• generating, by the at least one processor, a request for user authentication data and instruction to initiate a handshake protocol between the vendor computing device and a user computing device;
• transmitting, by the at least one processor, the request for user authentication data and instruction to initiate the handshake protocol to the vendor computing device;
• receiving, by the at least one processor, an indication that the handshake protocol was successful;
• receiving, by the at least one processor and from one of the vendor computing device and the user computing device, authentication response data;
• generating, by the at least one processor, an encrypted hash of the authentication response data;
• comparing, by the at least one processor, the encrypted hash of the authentication response data to an encrypted hash of the segregated encrypted authentication data for the first payment device;
• when it is determined that the encrypted hash of the authentication response data matches the encrypted hash of the segregated encrypted authentication data for the first payment device, processing, by the at least one processor, the transaction;
• and
• when it is determined that the encrypted hash of the authentication response data does not match the encrypted hash of the segregated encrypted authentication data for the first payment device, denying, by the at least one processor, the transaction.

One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, memory, and a communication interface, cause the computing platform to:

• receive registration data, the registration data including data associated with a plurality of payment devices associated with a user, each payment device of the plurality of payment devices being associated with a respective entity;
• receive, via a vendor computing device, a request to initiate a transaction, the request to initiate the transaction including a customer identifier;
• retrieve, based on the customer identifier, user information associated with the user;
• transmit, via a secure application programming interface (API) call method, a request for user profile data to each respective entity associated with each payment device of the plurality of payment devices;
• receive, from each respective entity associated with each payment device of the plurality of payment devices, user profile data, the user profile data including encrypted authentication data associated with each respective payment device and raw user data;
• segregate the encrypted authentication data from the raw user data for each user profile received;
• generate, for each user profile received, an encrypted hash of the segregated encrypted authentication data;
• store, for each user profile received, the encrypted hash of the segregated encrypted authentication data;
• dynamically generate a rendering including each payment device of the plurality of payment devices;
• transmit the rendering to the vendor computing device;
• receive, from the vendor computing device, selection of a first payment device of the plurality of payment devices;
• generate a request for user authentication data and instruction to initiate a handshake protocol between the vendor computing device and a user computing device;
• transmit the request for user authentication data and instruction to initiate the handshake protocol to the vendor computing device;
• receive an indication that the handshake protocol was successful;
• receive, from one of the vendor computing device and the user computing device, authentication response data;
• generate an encrypted hash of the authentication response data;
• compare the encrypted hash of the authentication response data to an encrypted hash of the segregated encrypted authentication data for the first payment device;
• responsive to determining that the encrypted hash of the authentication response data matches the encrypted hash of the segregated encrypted authentication data for the first payment device, process the transaction;
• and
• responsive to determining that the encrypted hash of the authentication response data does not match the encrypted hash of the segregated encrypted authentication data for the first payment device, deny the transaction.