SECURE AUTHORIZATION OF ACCESS TO USER ACCOUNTS BY ONE OR MORE AUTHORIZATION MECHANISMS
A permissions management system is disclosed for enabling a user to securely authorize access to user accounts and/or securely authorize execution of transactions related to user accounts via one or more application programming interfaces (“APIs”) and/or one or more authorization mechanisms.
1 . A device, comprising:
one or more memories;
one or more processors, coupled to the one or more memories, configured to:
receive a first account identifier and account credentials associated with an account;
access, via an application programming interface (API) associated with an institution and based on using the account credentials, a second account identifier associated with the account;
generate, based on determining that the first account identifier and the second account identifier match, a token usable to authorize access to account data associated with the account or initiate transactions related to the account;
perform, based on determining that at least one of the institution does not support a first fallback authorization mechanism or the first fallback authorization mechanism failed, actions, wherein the actions comprise:
initiating a second fallback authorization mechanism;
initiating one or more authorization transactions to the account using the first account identifier and an institution identifier associated with the institution; and
verifying the one or more authorization transactions; and
generate, based on verifying the one or more authorization transactions, another token.
2 . The device of claim 1 , wherein the other token is usable to authorize access to the account data or initiate transactions related to the account.
3 . The device of claim 1 , wherein the one or more processors are further configured to:
instantiate a simulated instance of an application associated with the institution,
wherein the simulated instance is configured to communicate with the institution via the API.
4 . The device of claim 1 , wherein the one or more processors are further configured to:
generate, based on initiating the one or more authorization transactions and before verifying the one or more authorization transactions, an interim token.
5 . The device of claim 1 , wherein the one or more processors are further configured to:
provide permissions code configured to generate one or more user interfaces,
wherein the one or more user interfaces are configured to receive the first account identifier and the account credentials associated with the account.
6 . The device of claim 1 , wherein the second account identifier is extracted from a document accessed based on the API.
7 . The device of claim 1 , wherein the one or more authorization transactions are verified based on at least one of:
transaction type, transaction description, transaction amount, transaction identifier, datestamps, timestamps, source, or other transaction metadata.
8 . A device, comprising:
one or more memories; and
one or more processors, coupled to the one or more memories, configured to:
receive a first identifier and account credentials associated with an account;
access, via an application programming interface (API) associated with an institution and based on using the account credentials, a second identifier associated with the account;
generate, based on determining that the first identifier and the second identifier match, a token usable to authorize access to account data associated with the account or initiate transactions related to the account;
perform, based on determining that at least one of the institution does not support a first fallback authorization mechanism or the first fallback authorization mechanism failed, actions, wherein the actions comprise:
initiating a second fallback authorization mechanism;
initiating one or more authorization transactions to the account using the first identifier and an institution identifier associated with the institution; and
verifying the one or more authorization transactions; and
generate, based on verifying the one or more authorization transactions, another token.
9 . The device of claim 8 , wherein the other token is usable to authorize access to the account data or initiate transactions related to the account.
10 . The device of claim 8 , wherein the one or more processors are further configured to:
instantiate a simulated instance of an application associated with the institution,
wherein the simulated instance is configured to communicate with the institution via the API.
11 . The device of claim 8 , wherein the one or more processors are further configured to:
generate, based on initiating the one or more authorization transactions and before verifying the one or more authorization transactions, an interim token.
12 . The device of claim 8 , wherein the one or more processors are further configured to:
provide permissions code configured to generate one or more user interfaces,
wherein the one or more user interfaces are configured to receive the first identifier and the account credentials associated with the account.
13 . The device of claim 8 , wherein the second identifier is extracted from a document accessed based on the API.
14 . The device of claim 8 , wherein the one or more authorization transactions are verified based on at least one of:
transaction type, transaction description, transaction amount, transaction identifier, datestamps, timestamps, source, or other transaction metadata.
15 . A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising:
one or more instructions that, when executed by one or more processors of a device, cause the device to:
receive a first identifier and account credentials associated with an account;
access, via at least an application programming interface (API) associated with an institution and based on using the account credentials, a second identifier associated with the account;
generate, based on determining that the first identifier and the second identifier match, a token usable to authorize access to account data associated with the account or initiate transactions related to the account;
perform, based on determining that at least one of the institution does not support a first fallback authorization mechanism or the first fallback authorization mechanism failed, actions, wherein the actions comprise:
initiating a second fallback authorization mechanism;
initiating one or more authorization transactions to the account using the first identifier and an institution identifier associated with the institution; and
verifying the one or more authorization transactions; and
generate, based on verifying the one or more authorization transactions, another token.
16 . The non-transitory computer-readable medium of claim 15 , wherein the other token is usable to authorize access to the account data or initiate transactions related to the account.
17 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:
instantiate a simulated instance of an application associated with the institution,
wherein the simulated instance is configured to communicate with the institution via the API.
18 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:
generate, based on initiating the one or more authorization transactions and before verifying the one or more authorization transactions, an interim token.
19 . The non-transitory computer-readable medium of claim 15 , wherein the one or more instructions further cause the device to:
provide permissions code configured to generate one or more user interfaces,
wherein the one or more instructions further cause the device to receive at least the first identifier and the account credentials associated with the account.
20 . The non-transitory computer-readable medium of claim 15 , wherein the second identifier is extracted from a document accessed based on the API.