Patent application number | Description | Published |
20140156480 | PERSONAL FINANCIAL MANAGEMENT PAYMENT ALLOCATION - Devices, methods and computer program are defined that provide recommendations to users based on the user's personal financial management information and a benefit to the user. The personal financial management information may include a snapshot of the user's accounts, a timeline of the user's accounts, or a cash flow of the user's accounts. The benefit can be a financial benefit, such as a lower interest rate, or a non-financial benefit, such as an improved return policy. In a further embodiment, the recommendation is determined by crowdsourcing using a cohort of financial institution customers that share some characteristics with the user. As a result the user makes informed decisions on which payment type to use or other change for a future transaction at the merchant. | 06-05-2014 |
20140278736 | UTILIZING SHARED CUSTOMER DATA - Methods, systems, computer-readable media, and apparatuses for utilizing shared customer data are presented. In some embodiments, a computing device may detect a mobile device that is linked to a user account. Subsequently, the computing device may identify a user of the mobile device, based on shared customer data associated with the user account. The computing device also may retrieve customer information associated with the identified user from the shared customer data. Then, the computing device may provide the retrieved customer information to at least one merchant device. In one or more embodiments, the shared customer data may be collected by at least two different commercial entities, and the shared customer data may be available for use by the at least two different commercial entities. | 09-18-2014 |
20140279497 | Secure Identity Element - Methods, systems, computer-readable media, and apparatuses for providing a secure identity element are presented. In some embodiments, a computing device may authenticate a user of the computing device. Subsequently, the computing device may capture an image of the user, and further may store the image in a secure element. Then, responsive to receiving a request to provide a credential for a payment transaction, the computing device may cause the image from the secure element to be provided as the credential. In some instances, the image from the secure element may be provided as an identity credential for a payor in the transaction, while in other instances, the image from the secure element may be provided as an identity credential for a payee in the transaction. | 09-18-2014 |
20140279498 | Secure Identity Element - Methods, systems, computer-readable media, and apparatuses for utilizing a secure identity element to facilitate transactions are presented. In some embodiments, a computing device may detect a payment device. Subsequently, the computing device may cause a payment credential to be displayed on the payment device, where the payment credential includes an image of an authorized user of the computing device. Thereafter, the computing device may receive, from the payment device, a request to complete a payment transaction. Responsive to receiving user input approving the payment transaction, the computing device may cause a payment to be made to an account associated with the payment device. In some embodiments, in receiving the request to complete the payment transaction, the computing device also may receive a photo credential for an authorized user of the payment device and/or an amount to be paid in the payment transaction, which can be displayed by the computing device. | 09-18-2014 |
20150227724 | SORTING MOBILE BANKING FUNCTIONS INTO AUTHENTICATION BUCKETS - Embodiments are directed to systems, methods and computer program products for sorting mobile banking functions into authentication buckets. Embodiments determine, for each of a plurality of mobile banking functions, a corresponding authentication buckets, where each authentication bucket corresponds with a level of authentication. Some embodiments receive a request, from a user, to access a function; access the plurality of authentication buckets to determine which of the authentication buckets corresponds with the requested function; determine the level of authentication associated with the determined authentication bucket; determine which authentication types are associated with the level of authentication; request authentication credentials corresponding to the authentication types; receive authentication credentials from the user; validate the authentication credentials, thereby resulting in a successful validation of the authentication credentials; and, in response to the successful validation of the authentication credentials, enable access to the function requested by the user. | 08-13-2015 |
20150227725 | PROVIDING AUTHENTICATION USING PREVIOUSLY-VALIDATED AUTHENTICATION CREDENTIALS - Embodiments of the invention are directed to systems, methods and computer program products for providing authentication using previously-validated authentication credentials. An exemplary apparatus is configured to receive a request to access a framework application, request, from a user, one or more authentication credentials corresponding to a primary level of user authentication, receive and validate the one or more authentication credentials, create, using the framework application, an authentication token based at least partially on the validation of the primary level of user authentication, wherein the authentication token is accessible by a plurality of applications, receive a request, from the user, to access one or more non-framework applications; and authenticate the one or more non-framework applications, where authenticating the non-framework applications requires accessing the authentication token created by the framework application such that the authentication is at least partially based on the primary level of user authentication. | 08-13-2015 |
20150227903 | REMOTE REVOCATION OF APPLICATION ACCESS BASED ON LOST OR MISAPPROPRIATED CARD - Embodiments of the invention relate to systems, methods, and computer program products for accessing a remotely located mobile device of a user based on certain events is provided. The system, method, and computer program product are configured to: (a) receive an indication that a transaction vehicle of the user is compromised; (b) identify a mobile device of the user that is associated with the transaction vehicle of the user that is compromised; (c) upon identifying the mobile device of the user, remotely access the mobile device of the user; and (d) reconfigure one or more applications accessible to the mobile device or one or more functional features of the mobile device based at least partially on receiving the indication. | 08-13-2015 |
20150227924 | DETERMINING AUTHENTICATION REQUIREMENTS ALONG A CONTINUUM BASED ON A CURRENT STATE OF THE USER AND/OR THE SERVICE REQUIRING AUTHENTICATION - Systems, apparatus, methods, and computer program products are provided for determining a user's authentication requirements/credentials for a specific service access request based on determining a location along a an authentication continuum. The location along the authentication continuum defines the degree of authentication/credentials required to access the service and is determined based on a current state of the user and/or service attributes. The more or less that is known about the current state of the user, in comparison to historical data about the user, the more or less likely the user is, in fact, the user that is attempting to access the service and, thus, the authentication requirements required to access the service can be adjusted according (increased or decreased). | 08-13-2015 |
20150227927 | REVOCATION OF APPLICATION ACCESS BASED ON NON-CO-LOCATED - Embodiments of the invention relate to an invention for accessing a remotely located mobile device of a user based on certain events is provided. The system, method, and computer program product are configured to: (a) monitor one or more transaction involving a transaction vehicle of a user; (b) determine a physical location of a transaction vehicle based at least partially on the one or more transactions; (c) determine a geographic location of a mobile device of the user, wherein the mobile device is associated with the transaction vehicle; (d) determine whether or not the transaction vehicle of the user and the mobile device of the user are co-located; and (e) reconfigure one or more applications accessible to the mobile device or one or more functional features of the mobile device based at least partially on determining that the mobile device and the transaction vehicle of the user are not co-located. | 08-13-2015 |
20150229622 | SHUTTING DOWN ACCESS TO ALL USER ACCOUNTS - Disclosed is a system and associated method or restricting access to a user's account via one or more account access channels. The system typically includes a processor, a memory, and an access restriction module stored in the memory. The module is typically configured for: integrating one or more account access channels associated with the user's account with an access restriction procedure; receiving a request from the user to implement the access restriction procedure; based on receiving the request from the user to implement the access restriction procedure, implementing the access restriction procedure, wherein implementing the access restriction procedure comprises restricting access to the user's account via the account access channel(s). | 08-13-2015 |
20150229625 | AUTHENTICATION LEVEL OF FUNCTION BUCKET BASED ON CIRCUMSTANCES - Embodiments are directed to systems, methods and computer program products for assigning a level of authentication to an authentication bucket. Embodiments determine a current level of authentication corresponding to a first authentication bucket comprising a plurality of mobile banking functions; collect a set of circumstantial data corresponding with the apparatus; determine a circumstances score based at least in part on the set of circumstantial data; and determine whether the current level of authentication corresponding to the first authentication bucket is appropriate based at least in part on the circumstances score. | 08-13-2015 |