Secure permissioning of access to user accounts, including secure deauthorization of access to user accounts

A permissions management computing platform for securely enabling transactions with an external application without sharing user account data, comprising:

• one or more processors;
• a communication interface communicatively coupled to the one or more processors;
• and
• one or more non-transitory memory storing computer-readable instructions that, when executed by the one or more processors, cause the permissions management computing platform to:
• receive, via a normalized application programming interface (API), a request to authorize use of user account data held by a financial institution computing system having an API specific to the financial institution computing system that enables access to data stored by the financial institution computing system, wherein the request to authorize use of the user account data includes user credentials and one or more permissions limiting access to the use of the user account data by an external application system;
• access an institution-interface module corresponding to the financial institution computing system, wherein the institution-interface module models the API specific to the financial institution computing system and is generated based on at least one of (i) parsing source code of a first-party application of the financial institution computing system or (ii) parsing communication between the first-party application and the financial institution computing system;
• instantiate a software component configured to authenticate with the financial institution computing system as a first-party application of the financial institution computing system, the software component using the institution-interface module to communicate with the financial institution computing system via the API specific to the financial institution computing system;
• retrieve, via the software component, using the user credentials, and via the API specific to the financial institution computing system, the user account data from the financial institution computing system;
• format, using the institution-interface module, the user account data to a normalized format of the normalized API;
• generate an electronic record including the user account data and the one or more permissions;
• store the electronic record;
• generate a token identifying the electronic record;
• transmit, in response to the request to authorize use of the user account data, the token to the external application system;
• receive, from the external application system, a request for transaction processing for a transaction associated with a user, wherein the request for transaction processing includes transaction details and the token;
• retrieve, based on the token, the electronic record;
• compare the transaction details to the one or more permissions in the electronic record to determine whether the external application system is authorized to process the transaction;
• determine, based on the comparing, that the external application system is authorized to process the transaction;
• and
• process the transaction requested by the external application system via the software component and using the institution-interface module, the transaction processed using the user account data of the electronic record identified by the token while preventing the external application system from accessing the user account data.

One or more non-transitory computer-readable media storing instructions that, when executed, cause a permissions management computing platform for securely enabling transactions with an external application without sharing user account data to:

• receive, via a normalized application programming interface (API), a request to authorize use of user account data held by a financial institution computing system having an API specific to the financial institution computing system that enables access to data stored by the financial institution computing system, wherein the request to authorize use of the user account data includes user credentials and one or more permissions limiting access to the use of the user account data by an external application system;
• access an institution-interface module corresponding to the financial institution computing system, wherein the institution-interface module models the API specific to the financial institution computing system and is generated based on at least one of (i) parsing source code of a first-party application of the financial institution computing system or (ii) parsing communication between the first-party application and the financial institution computing system;
• instantiate a software component configured to authenticate with the financial institution computing system as a first-party application of the financial institution computing system, the software component using the institution-interface module to communicate with the financial institution computing system via the API specific to the financial institution computing system;
• retrieve, via the software component, using the user credentials, and via the API specific to the financial institution, the user account data from the financial institution computing system;
• formatting, using the institution-interface module, the user account data to a normalized format of the normalized API;
• generate an electronic record including the user account data and the one or more permissions;
• store the electronic record;
• generate a token identifying the electronic record;
• transmit, in response to the request to authorize use of the user account data, the token to the external application system;
• receive, from the external application system, a request for transaction processing for a transaction associated with a user, wherein the request for transaction processing includes transaction details and the token;
• retrieve, based on the token, the electronic record;
• compare the transaction details to the one or more permissions in the electronic record to determine whether the external application system is authorized to process the transaction;
• determine, based on the comparing, that the external application system is authorized to process the transaction;
• and
• process the transaction requested by the external application system via the software component and using the institution-interface module, the transaction processed using the user account data of the electronic record identified by the token while preventing the external application system from accessing the user account data.