Control tower for prospective transactions
Systems, methods, and apparatuses for providing a customer a central location to manage permissions provided to third-parties and devices to access and use customer information maintained by a financial institution are described. The central location serves as a central portal where a customer of the financial institution can manage all access to account information and personal information stored at the financial institution. Accordingly, the customer does not need to log into each individual third-party system or customer device to manage previously provided access to the customer information or to provision new access to the customer information. A user additionally is able to have user data and third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal. Restrictions on how user data is used by devices, applications, and third-party systems can be imposed via a central portal.
1 . A method comprising:
presenting, by a central portal comprising one or more processors coupled to memory, one or more graphical interfaces allowing a user to disable, via a user device, selected financial accounts for identified entities such that payments from the selected financial accounts will be declined for the identified entities,
the one or more graphical interfaces comprising a first graphical interface comprising a recurring payments list that identifies, for a financial account, recurring payments to a first entity and to a second entity;
responsive to an interaction with a selectable element at the user device, transitioning, by the central portal, presentation of the first graphical interface to a second graphical interface accessed on the user device, the second graphical interface comprising a hide-payee selector configured to allow the user to select the first entity to be hidden from the recurring payments list;
accepting, by the central portal, from the user device, a first input that the hide-payee selector has been selected on the user device to hide the first entity from the recurring payments list;
modifying, by the central portal, the recurring payments list to hide the first entity from the recurring payments list;
accepting, by the central portal, a second input that one or more subsequent recurring payments from the financial account to the first entity are to be declined;
transmitting, by the central portal, an application programming interface (API) call to the first entity, the API call identifying the financial account and indicating that the one or more subsequent recurring payments from the financial account to the first entity will be declined; and
declining, by the central portal, a subsequent recurring payment request received from an entity device corresponding to the first entity subsequent to acceptance of the indication.
2 . The method of claim 1 , wherein the one or more graphical interfaces comprise a first selectable icon to view recurring payments to the first entity, and a second selectable icon to view recurring payments to the second entity.
3 . The method of claim 1 , wherein the one or more graphical interfaces allow for selection to view a listing of recent transactions made using the financial account to the first entity or the second entity.
4 . The method of claim 1 , further comprising presenting, by the central portal, a duration selector configured to allow the user to identify a duration during which subsequent recurring payment requests from the first entity or the second entity are to be declined.
5 . The method of claim 4 , wherein the duration selector is configured to allow the user to select a number of months during which subsequent recurring payment requests will be declined, after which subsequent recurring payment requests will resume.
6 . The method of claim 1 , wherein the central portal is implemented by a computing system of a financial institution holding the financial account used for the recurring payments.
7 . The method of claim 1 , further comprising allowing, by the central portal, the user to define a set of access permissions identifying an entity or device that may request information regarding the user from the central portal.
8 . The method of claim 1 , wherein the central portal is implemented by a computing system of a financial institution holding the financial account used for the recurring payments.
9 . The method of claim 8 , further comprising receiving, by the central portal, payment requests from a first entity device of the first entity and initiating debits from the financial account for each payment request.
10 . The method of claim 8 , further comprising receiving, by the central portal, payment requests from a first entity device of the first entity and from a second entity device of the second entity, and initiating debits from the financial account for each payment request.
11 . The method of claim 1 , wherein the central portal is accessed via a mobile application running on the user device.
12 . The method of claim 1 , further comprising displaying, by the central portal, one or more prior recurring payments to a selected one of the first and second entities.
13 . The method of claim 1 , further comprising displaying, by the central portal, a status of the financial account.
14 . The method of claim 1 , further comprising accepting, by the central portal, via the user device, an authorization to approve recurring payment requests from devices of the first and second entities.
15 . The method of claim 1 , wherein the financial account is a debit card of the user, and wherein the recurring payments are made using the debit card.
16 . The method of claim 1 , wherein the financial account is a credit card of the user, and wherein the recurring payments are made using the credit card.
17 . The method of claim 1 , further comprising declining a subsequent recurring payment request received from an entity device corresponding to the first entity.
18 . A computing system comprising one or more processors coupled to a memory comprising instructions that when executed by the one or more processors perform operations comprising:
presenting one or more graphical interfaces allowing a user to disable, via a user device, selected financial accounts for identified entities such that payments from the selected financial accounts will be declined for the identified entities, the one or more graphical interfaces comprising a first graphical interface comprising a recurring payments list that identifies, for a financial account, recurring payments to a first entity and to a second entity;
responsive to an interaction with a selectable element at the user device, transitioning presentation of the first graphical interface to a second graphical interface accessed on the user device, the second graphical interface comprising a hide-payee selector configured to allow the user to select the first entity to be hidden from the recurring payments list;
accepting, from the user device, a first input that the hide-payee selector has been selected on the user device to hide the first entity from the recurring payments list;
modifying the recurring payments list to hide the first entity from the recurring payments list;
accepting a second input that one or more subsequent recurring payments from the financial account to the first entity are to be declined;
transmitting an application programming interface (API) call to the first entity, the API call identifying the financial account and indicating that the one or more subsequent recurring payments from the financial account to the first entity will be declined, wherein declining the one or more subsequent recurring payments is subsequent to transmitting the API call; and
declining a subsequent recurring payment request received from an entity device corresponding to the first entity subsequent to acceptance of the indication.