Abstract: Embodiments of the present disclosure provide systems and methods for automated chargeback processing, including hardware and software for storing, in a database, transaction data associated with one or more transactions in a queue, retrieving transaction data associated with one or more transactions stored in the queue, for each transaction in the queue, applying, using an automated chargeback processor, one or more rules to the transaction data, identifying, using the automated chargeback processor, the transaction data as eligible or ineligible for chargeback processing based on the one or more rules, determining, using the automated chargeback processor, whether additional documentation is required, and sending, via a network, instructions to perform a chargeback operation for an account associated with the transaction data.

Abstract: A system and method in accordance with example embodiments may determine whether or not an item requiring overdraft lending is eligible for the lending. Additionally, a system and method in accordance with example embodiments may receive a request to authorize an overdraft of an item and a first authorization credentials, determine whether or not the first authorization credentials are associated with a lending authority amount greater than the overdraft item request, and generate at least one message to at least one authorized user associated with a lending authority amount greater than the overdraft item request when the lending module determines the first authorized credentials are not associated with the lending authority amount great than the overdraft item request.

Abstract: A secure fob that enables a user to pay for an item or items without needing to present a mobile device. A secure fob may include a proximity capability to ensure that a mobile device is within a particular range, thereby eliminating the risk of fraudulent charges on a stolen fob. In such an embodiment, a fob may be disabled if the fob is not paired with the mobile device by virtue of being disconnected and/or physically separated from the mobile device. The secure fob also may include enhanced features to authorize transactions and locate the mobile device and/or the secure fob.

Abstract: The disclosed embodiments include methods and systems for providing a real-time application programming interface for merchant enrollment and underwriting. In one embodiment, a process is disclosed that may include receiving, from a first computing device, a request for applying for the merchant financial account for a merchant applicant. The request may also include verifying the information associated with the merchant applicant and providing, via the first computing device, at least one question with a plurality of answer choices to the merchant applicant if the merchant applicant information associated with the applicant is verified. In one aspect, the method may include receiving an answer choice to the at least one question from the merchant applicant via the first computing device and validating the received answer choice. If the answer choice is validated, the method may include activating the first computing device and authenticating the merchant applicant for the merchant financial account.

Abstract: Systems and methods for identifying a customer include storing account information, the account information including one or more associated phone numbers and an account number, the account number having a last 4-digit portion, receiving a phone number, comparing the phone number to the account information of various account holders to determine whether the phone number matches an associated phone number, prompting the user to input 4 digits if there is a match, and comparing the received 4 digits to the respective 4-digit portion to identify the customer.

Abstract: In one embodiment, a system configured to configure an inactive financial account is provided. The system, which may be a mobile device, may include one or more memory devices storing software instructions, and one or more processors configured to execute the software instructions to perform one or more operations. The processor(s) may be configured to receive from a server financial account configuration option data relating to a configurable inactive financial account product. The one or more processors may also generate and display interface(s) for activating the inactive financial account product, and receive input through the one or more interfaces to activate the inactive general financial account product. The processor(s) may further generate user selected financial account configuration option data based on the input, and provide the data to the server for configuring and activating the inactive financial account product in accordance with the input.

Abstract: A system and method in accordance with example embodiments may include third party payments with non-integrated merchants. A system and method in accordance with example embodiments may utilize a plug in or application to intercept retailer data from a third party, analyze data, and present information to a customer based on the intercepted data and the analysis.

Abstract: Systems and methods for determining a transaction location based on transaction history data include storing, in a database, transaction history data related to a plurality of account holders, storing, in a database, location data for a plurality of locations, wherein each of the plurality of locations is associated with a respective merchant store location, receiving, via a network, transaction data associated with one of the plurality of account holders' recent transaction, obtaining, using a processor, the location data for a plurality of locations, retrieving, using a processor, transaction history data associated with the account holder from a transaction history data store associated with a financial institution, creating transactions clusters based on the transaction history data, analyzing a location associated with each of the transaction clusters and the location data, and determining a predicted transaction location based on the analysis of the one or more transaction clusters and the location data

Abstract: The disclosed embodiments include methods and systems for collecting, managing, and processing data for lending services. In one embodiment, a computerized system is disclosed that may receive a loan request from a customer, and collect data from the customer and third parties having information about the customer. The system may utilize the collected data in an ability-to-pay (ATP) calculator to determine the customer's ability to pay the requested loan, in addition to the customer's current financial obligations, and considering additional contextual factors. Different selectable versions of the ATP calculator may incorporate different contextual data and non-traditional financial data to provide a customized, accurate determination of the customer's ability-to-pay.

Abstract: The disclosed embodiments include methods, systems, and articles of manufacture for providing tipping suggestion services. A financial service provider configures a financial service account for a user. After the user makes a purchase at a merchant associated with leaving a tip, such as a restaurant, the financial service provider may determine metrics related to tipping, such as the user's own tipping behavior, or the tipping behavior of other users at the same merchant over time. The financial service provider may rapidly transmit the tipping metrics to a client device when a notification is received that a user has made a tip-eligible purchase, so that the user may factor the metrics into a decision of how much to tip in real time as the decision is being made.

Abstract: A system and method in accordance with exemplary embodiments may include systems and methods for providing first-in-wallet payment account auctioning. In an exemplary embodiment, a method for providing first-in-wallet payment account auctioning includes, receiving, via a network, consumer preference data, current consumer financial situation data associated with a plurality of payment accounts, and account terms associated with each of the plurality of payment accounts; scoring each of the plurality of payment accounts based on the consumer preference data, the current consumer financial situation data, and the account terms and determining an optimal payment account to be the first-in-wallet account out of the plurality of payment accounts based on the scoring.

Abstract: A system and method for providing same-day funding to a vendor of a sale from a financial institution including the substantially real-time procedures of applying for funding, processing of the application, and providing same-day funding. The system and methods also including utilizing an open exchange platform for data communication and processing between a vendor system and a financial institution system. The same-day funding including an initial assessment and processing to determine if an application is eligible for same-day funding followed by further assessments and processing of application data where it is determined that the application is eligible for same-day funding.

Abstract: A system is provided for funding changes regarding financial transactions. The system may include one or more memory devices storing software instructions and one or more processors configured to execute the software instructions to, for example, identify a first financial transaction for a first amount involving a first financial account associated with a user, and determine a second financial account associated with the user that can be used to fund the first financial transaction. The one or more processors may also be configured to provide a funding type change option that identifies the second financial account as an alternate financial account for funding the first financial transaction, receive a funding type change indication to change the funding type of the first financial transaction from the first financial account to the second financial account, and process the funding type change indication.

Abstract: Systems and methods are disclosed for managing customer data. In one embodiment, a system may include one or more memory devices storing instructions, and one or more processors configured to execute the instructions to receive data related to a customer's first account from a first line of business server. The one or more processors may also be configured to determine that the customer has a second account in a second line of business, and receive data related to the second account from a second line of business server. The one or more processors may also be configured to receive updated data related to the customer, and transmit the updated data to at least one of the first and second line of business servers.

Abstract: Example systems and methods provide comprehensive sales and service data processing and reporting. Sales and service events that take place at a front end branch of an enterprise may be input into a front end system and transmitted to a backend system where various modules then use the front end system data to generate various data and reports to determine sales incentive metrics and key performance indicators.

Abstract: Systems and methods provide for notifying an account holder of an attempted transaction. The systems and methods include a transaction data communication module that receives, via a network, transaction data associated with a transaction, a transaction processor that associates the transaction data with an account of an account holder, compares the transaction data to one or more spending limits associated with the account, and compares the transaction data to one or more fraud detection rules associated with the account, an account holder notification system associated with the transaction processor that notifies the account holder, via a network, based on the results of the comparison steps, and an authorization response module that receives, via a network, a response from the account holder and approves or deny the transaction based at least in part on a response received.

Abstract: A system and method in accordance with example embodiments may include evaluating account holder data, determining an account holder specific rewards program, and providing the account holder specific rewards program to the account holder. The rewards program may include a rewards and/or cash-back eligibility for a number of rewards or cash-back options.

Abstract: Systems and methods for automatically responding to a mass compromise event include storing, in a financial institution database, transaction histories for each of a plurality of accounts associated with the financial institution, analyzing, using an account detection processor, the transaction histories to identify one or more accounts among the plurality of accounts that are associated with a mass compromise event, segmenting, using the account detection processor, the identified one or more accounts into first and second segments, applying, using the account detection processor, risk splitters to first segment to identify mass compromise queue processing accounts, providing, using the account detection processor, the mass compromise queue processing accounts, and automatically processing, using a mass compromise queue processor, the mass compromise queue processing accounts.

Abstract: The disclosed embodiments include methods, systems, and articles of manufacture for providing payment options. In one embodiment, a system may receive transaction information regarding a plurality of purchase transactions involving a plurality of merchants and customers of a financial service provider. The system may also determine a merchant and payment type for each of the plurality of purchase transactions based on the received transaction information. The system may further associate one or more of the determined payment types with each of the determined merchants. The system may also generate at least one configuration file reflecting the one or more of the determined payment types associated with each of the determined merchants. The system may also provide the at least one configuration file to at least one client device.

Abstract: Systems and methods are disclosed for providing access and authentication scenarios for mobile, or remote, banking via a client device. A financial service provider system determines a desired level of security for various mobile banking transactions, and configures a unique login credential or attribute for each level or tier of security. After receiving an indication that a user desires to perform a mobile banking transaction, and determining the mobile banking transaction desired by the user, the financial service provider system prompts the user for the associated login credential or attribute. Finally, the system receives and validates the credential.