Abstract: A method of performing an off-us deposit with reversal is provided. The method includes receiving, by a depository bank computing system associated with a depository bank, a request identifying an amount of a transfer of funds from a paying bank, different from the depository bank, into an account associated with a customer of the depository bank. The method further includes crediting, by the depository bank computing system, the account of the customer of the depository bank by the amount of the transfer of funds. The method further includes determining, by the depository bank computing system, a need for a reversal of the transfer of funds from the account of the customer of the depository bank. The method further includes reversing, by the depository bank computing system, the transfer of funds from the account of the customer by the amount of the transfer of funds.

Abstract: Systems, methods, and apparatuses for providing a central location to manage permissions provided to third-parties and devices to access and use user data and to manage accounts at multiple entities. A central portal may allow a user to manage all access to account data and personal information as well as usability and functionality of accounts. The user need not log into multiple third-party systems or customer devices to manage previously provided access to the information, provision new access to the information, and to manage financial or other accounts. A user 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. The user is able to impose restrictions on how user data is used by devices, applications, and third-party systems, and control such features as recurring payments and use of rewards, via a central portal.

Abstract: A method for provisioning a payment account to a mobile wallet on a mobile device includes receiving, by a provider computing system, an encrypted network return address of the mobile wallet that uniquely identifies a network address of the mobile wallet when the encrypted network return address is decrypted from an initiating device, receiving, by the provider computing system, an encryption key configured to decrypt the encrypted network return address, wherein the encryption key is not provided to the initiating device, decrypting, by the provider computing system, the encrypted network return address using the encryption key, and provisioning, by the provider computing system, a payment token associated with the payment account to the mobile wallet based on the decrypted network return address received from the initiating device by transmitting the payment token to the mobile device without going through the initiating device.

Abstract: 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.

Abstract: A system and method for card control includes a card control computing system configured to enforce a card control rule based upon transactions made with a payment card. The card control computing system includes a memory unit configured to store information associated with a card control dashboard, and a processing unit configured to cause presentation of the card control dashboard via a display associated with a remote computing device, such that the card control dashboard is associated with the payment card and the card control rule. The card control dashboard includes a user interface. The processing unit is further configured to receive an input via the user interface to activate or deactivate one or more features associated with the card control rule, and trigger the card control rule based upon the one or more features that are activated or deactivated.

Abstract: A method of authenticating a user on behalf of a third party provider by an identity provider computing system is disclosed. The method includes receiving a user token and user device information from the third party provider; identifying the user based on the user token; identifying related user activity based on the user device information; and authenticating the user based on the related user activity.

Abstract: A computer implemented method performed by an identity verification computing system includes generating a user-level token associated with a user-level profile. The user-level profile is associated with a user and is unique to the user. The method includes receiving a request to provide an identity verification of a user via an entity computing system, the request comprising a card-based transaction message associated with a card-based transaction, the card-based transaction message comprising the user-level token. The method further includes accessing the user-level profile associated with the user-level token, obtaining the user-level token from the card-based transaction message, validating the user-level token, and transmitting an identity verification approval to the entity computing system.

Abstract: Various examples described herein are directed to systems and methods for sentiment data retrieval. A customer is recognized and customer data associated with the customer is retrieved based on the recognizing the customer. A relationship with the customer is determined based on the customer data. Input data associated with the customer is received from an input device. A sentiment analysis is run on the input data. A customer need based on the sentiment analysis, the customer data, and the determined relationship is determined. Customer data associated with the customer need is retrieved and provided.

Abstract: 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.

Abstract: 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.

Abstract: 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/or third-party accounts of the user deleted from devices, applications, and third-party systems via a central portal.

Abstract: Methods and systems of managing payment cards are disclosed. A financial institution computing system includes a token database storing a plurality of tokens and token information, a network interface circuit enabling the financial institution computing system to exchange information over a network; and a token management circuit. The token management circuit enables a graphical user interface on a customer device over the network that can be used to generate new token requests, re-provision token requests, and management requests. The management requests enable and disable tokens, such that transactions against a payment card account using an enabled token are completed, and transactions against the payment card account using a disabled token are denied.

Abstract: A method including storing a record in an information directory of a computer system. The method also includes receiving a confirmation that a particular identifier of the one or more public identifiers is useable to contact the recipient based on one or more responses to one or more authentication request messages. The method additionally includes receiving, through the computer network, a funds transfer request from a sender having a sender account at a second financial institution. The method further includes determining a private identifier for the recipient account using the information directory based on the particular public identifier of the one or more public identifiers.

Abstract: Systems and methods of authenticating online purchases by detecting a presence of an authorized smart card at a personal computing device of a customer are disclosed. An issuer computing system maintains a customer database of personal information and financial information for a plurality of customers with issued smart cards. An authentication logic receives an authentication request sent from a local merchant circuit at the personal computing device over a network. The authentication request comprises an authentication code provided to the local merchant circuit by a contactless chip of a smart card. The authentication logic authenticates the authentication request by comparing the authentication code with stored information in the customer database and transmits an authentication approval to the personal computing device, wherein the authentication approval enables an online purchase transaction request corresponding to the authentication request.

Abstract: A method includes collecting account data for an account from an authentication server. The method also includes receiving a request for the account data from an owner of the account or from a custodial entity. The method further includes determining a portion of the account data that may be accessed based on a permissions grid. The permissions grid includes a list of authorized entities including at least one of the owner or the custodial entity. The permissions grid also includes a list of permissions associated with each entity from the list of authorized entities. The method includes transmitting the portion of the account data in response to the request.

Abstract: A method of performing a real-time non-inquiry electronic transaction is provided. The method includes receiving, by a paying bank computing system associated with a paying bank, a posting of a transaction from an account verification service, the transaction corresponding to a transfer of funds from the paying bank computing system to a depository computing system associated with a depository bank. The method further includes sending, by the paying bank computing system, an acknowledgement of the transaction to the account verification service, wherein the transaction is determined to be a non-inquiry transaction such that the transaction is posted at the depository bank computing system without performing an initial inquiry regarding the transaction at the account verification service.

Abstract: Systems, methods, and apparatuses for providing a central location to manage permissions provided to third-parties and devices to access and use user data and to manage accounts at multiple entities. A central portal may allow a user to manage all access to account data and personal information as well as usability and functionality of accounts. The user need not log into multiple third-party systems or customer devices to manage previously provided access to the information, provision new access to the information, and to manage financial or other accounts. A user 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. The user is able to impose restrictions on how user data is used by devices, applications, and third-party systems, and control such features as recurring payments and use of rewards, via a central portal.

Abstract: Methods and systems of managing payment cards are disclosed. A financial institution computing system includes a token database storing a plurality of tokens and token information, a network interface circuit enabling the financial institution computing system to exchange information over a network; and a token management circuit. The token management circuit enables a graphical user interface on a customer device over the network that can be used to generate new token requests, re-provision token requests, and management requests. The management requests enable and disable tokens, such that transactions against a payment card account using an enabled token are completed, and transactions against the payment card account using a disabled token are denied.

Abstract: Methods and systems of managing payment cards are disclosed. A financial institution computing system includes a token database storing a plurality of tokens and token information, a network interface circuit enabling the financial institution computing system to exchange information over a network; and a token management circuit. The token management circuit enables a graphical user interface on a customer device over the network that can be used to generate new token requests, re-provision token requests, and management requests. The management requests enable and disable tokens, such that transactions against a payment card account using an enabled token are completed, and transactions against the payment card account using a disabled token are denied.

Abstract: Systems and methods for facilitating finance by monitoring behavior of users indicative of behavioral patterns or deviations from behavioral patterns and inviting users to make financial changes that may be appropriate based on the monitored behavior. In some embodiments, a minimum amount of relevant data must be collected to support the existence of a behavioral pattern or deviation before a user is invited to make appropriate changes to their finances.