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: 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: 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: 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: Methods and systems of exchanging data using payment cards with universal reference numbers are disclosed. A merchant computing system includes a merchant input/output assembly receiving a universal reference number from a customer at a point of sale. A merchant database retrievably stores a plurality of universal reference numbers and customer information associated with each of the plurality of universal reference numbers. A transaction circuit receives the universal reference number from the merchant input/output assembly, retrieves customer information associated with the universal reference number, and provides an output relating to a transaction based on the customer information.

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 method further includes receiving a card-based transaction message associated with a card-based transaction. The card-based transaction message includes a card information portion and a point-of-sale data portion. The user-level token is inserted into at least one of the card information portion or the point-of-sale data portion. The method further includes obtaining the user-level token from the received card-based transaction message, validating the user-level token responsive to receiving a validation confirmation from a token service provider, and transmitting an identity verification to the entity computing system responsive to validating the user-level token.

Abstract: A method includes verifying the identity of an individual. The method further includes receiving non-financial data from the individual and generating a user-level profile. The user-level profiles include the non-financial data received from the individual. The method further includes generating a user-level token unique to the individual. The user-level token is associated with the generated user-level profile. The method also includes provisioning the user-level token to a device associated with the individual. The method further includes receiving an identity verification request comprising the user-level token, wherein the identity verification request is structured as a financial transaction card-originated message, validating the user-level token, and analyzing a context of the received user-level token to determine a relevant non-financial data element included in the non-financial information within the user-level profile.

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: 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: Systems, methods, and non-transitory computer-readable media for performing exchanges. One method includes receiving a request identifying a payor account and an amount of funds to transfer an account associated with a customer of the depository bank computing system, determining the request qualifies for a non-inquiry transaction (NIT) protocol, transmitting, by the depository bank computing system to an account verification service computing system over the real-time data channel, a guarantee offer including a payor account token based on the shared account status information, receiving, over the real-time data channel and from the account verification service computing system, an accepted guarantee offer, crediting an account of the customer, receiving, over the real-time data channel, a guarantee override, and reversing the transfer of funds associated with the guarantee.

Abstract: A computing system includes an interface configured to communicate with an entity computing system associated with a merchant via a network, an identity database storing verified personal identifying information, a memory, and at least one processor configured to: determine whether an individual is associated with an existing user account; prompt the individual to create a user account; verify an identity of the individual using personal identifying information associated with the individual; receive non-financial information associated with the individual; generate a user-level profile having the non-financial information; generate a user-level token unique to the individual; transmit the user-level token to a device associated with the individual; receive an identity verification request having the user-level token; validate the user-level token; determine that the identity verification request includes contextual data; determine the non-financial information that is relevant to the contextual data; and tra

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: 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, 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 includes receiving, by a provider computing system from an initiating device, an encrypted network return address of an user device that identifies a network address of the user device; receiving, by the provider computing system and from the user device, an encryption key configured to decrypt the encrypted network return address; decrypting, by the provider computing system, the encrypted network return address using the encryption key; and providing, by the provider computing system, a code to the user device based on the decrypted network return address by transmitting the code to the user 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: 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 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.