Abstract: Systems for identifying multiple merchant category codes associated with a merchant include a database and a server. The database has a merchant table with several merchant records, which have unique merchant identifiers associated with distinct merchants and one or more active merchant category codes associated with the merchant identifiers. The server receives a clearing transaction message, which includes payment account data associated with an issuer. A transaction merchant identifier in the message is detected by the server. The server retrieves a merchant record that corresponds to the transaction merchant identifier. The server determines whether the merchant record includes several merchant category codes, and if it does, adds an indicator within a first data element and the active merchant category codes within a second data element of the clearing transaction message. The server then transmits the clearing transaction message to the issuer associated with the payment account data.

Abstract: A fair price estimator system has a memory device and a processor programmed to receive historical transaction data including historical payment transactions between account holders and merchants. The transaction data includes a merchant name, category code (MCC), and location associated with each of the payment transactions. The processor generates a first subset of data based on predetermined transaction parameters and stores the first subset in the memory device. The processor receives, from a consumer, a first input value including one or more of a merchant name and/or an MCC that are included in the first subset of data, and a second input value including a location identifier. The processor generates a second subset of data from the first subset based on the input values. The processor then determines one or more transaction value properties of the second subset of data and presents to the consumer the one or more transaction value properties.

Abstract: Described herein is a data optimization computer system for optimizing transaction authorization request messages directed to an authorizing party. The computer system includes a historical transaction database, a merchant database, and a data optimization computing device. The historical transaction database stores a plurality of historical transaction records. The merchant database stores a first merchant registered with the optimization computer system. The data optimization computing device may analyze at least a subset of the historical transaction records to generate a set of optimization rules. The set of optimization rules identifies optimal values for an optimized transaction authorization request message. The optimized transaction authorization request message may be associated with an improved likelihood of resulting in a positive request outcome.

Abstract: A computer-implemented method for enhancing authorization of prepaid payment cards is provided. The method is implemented using an authorization computing device in communication with a memory. The method includes storing a plurality of transaction histories associated with a plurality of prepaid payment cards, receiving an authorization request for a payment transaction between a cardholder and an originating merchant initiated using a prepaid payment card, determining a transaction history associated with the prepaid payment card based on the plurality of transaction histories, calculating a prepaid risk score for the payment transaction based on the authorization request and the determined transaction history, and transmitting the prepaid risk score to the originating merchant.

Abstract: A capacity analysis computing device for determining a restaurant capacity level is provided. The capacity analysis computing device is configured to store historical transaction data for a restaurant for a period of time, and analyze the historical transaction data to identify a maximum restaurant capacity for the restaurant over the period of time. The capacity analysis computing device is also configured to receive, from a user computing, a selected time interval for which a current capacity level is to be determined. The capacity analysis computing device is further configured to identify a similar historical time interval to the selected time interval, and determine a historical capacity level for the restaurant during the similar historical time interval. The capacity analysis computing device is further configured to assign the historical capacity level as the current capacity level for the restaurant, and display the current capacity level on the user computing device.

Abstract: An insight data computing system for generating a pre-chargeback record for a payment transaction between a customer and a merchant is provided. The payment transaction is authorized over a payment processing network based on transaction data submitted over the payment processing network. The transaction data is stored by the payment processing network in a historical transaction database. The insight data computing system includes an insight data interface computing device programmed to (i) receive, via an insight communication channel other than the payment processing network, an insight data message including insight data and transaction link data, (ii) store the insight data in an insight database, (iii) link the insight data to the transaction data by matching the transaction link data in the insight data to the transaction data in the historical transaction database, and (iv) generate the pre-chargeback record including the transaction data and the linked insight data.

Abstract: A dispute scoring computing device for generating chargeback dispute scores is provided. The dispute scoring computing device extracts historical transaction data and account profile data for a plurality of transactions associated with an account, and generates a chargeback dispute prediction model for the account based on the extracted data. The dispute scoring computing device further receives a candidate chargeback for a transaction initiated with a merchant using the account, extracts transaction data from the candidate chargeback, and determines, using the generated chargeback dispute prediction model, a chargeback dispute score indicating a likelihood that the candidate chargeback, if disputed by the merchant, would result favorably for the merchant.

Abstract: A computing network system including a historical authorization database, a lost and stolen card (LSC) database, an account data breach (ADB) database, and a compromised identification (CI) computing device is provided. The CI computing device retrieves a set of historical account identifiers associated with historical transactions of a candidate merchant from the historical authorization database. The CI computing device compares the historical account identifier to lost and/or stolen (LS) account data stored by the LSC database and breach data stored by the ADB database. The CI computing device generates a compromised account message when a historical account identifier has a matching account identifier within the LS account data and/or the breach data. The compromised account message includes the matching account identifier and an associated reason code indicating a cause of compromise. The CI computing device transmits the compromised account message to the candidate merchant for review and analysis.

Abstract: An auto-enrollment billing updater (AEBU) computing device for enrolling enrollees in an automatic updating program is provided.

Abstract: A chargeback analytics computing device for generating chargeback analytics associated with service chargebacks is provided. The chargeback analytics computing device is configured to retrieve transaction data for a merchant, the transaction data associated with transactions initiated at the merchant, and extract chargeback data from the transaction data, the chargeback data associated with chargeback transactions. The chargeback analytics computing device also parses the chargeback data to identify a chargeback reason code associated with each chargeback transaction. Based upon the chargeback reason codes, the chargeback analytics computing device isolates a fraud-related portion and a non-fraud-related portion of the chargeback data, and extracts a service subset of the non-fraud-related portion associated with service chargeback transactions, wherein a service chargeback transaction is initiated by a cardholder having an unsatisfactory experience with the merchant.

Abstract: A computer-implemented method for identifying errors in transaction messages associated with payment transactions. The method includes a step of receiving a transaction message associated with a financial transaction, whereby the financial transaction originates from a merchant and is processed by an acquirer. The transaction message comprises a plurality of data element fields, with at least one of the data element fields being a merchant identification field used to identify the merchant originating the financial transaction. An additional step includes performing an error-identification routine on the transaction message, with the error-identification routine including analyzing a merchant identification (ID) data element populated in the merchant identification field to determine if the merchant ID data element is not uniquely associated with the merchant.

Abstract: A system and computer-implemented method includes the operations of receiving an electronic transaction message including transaction data from an interchange network. The transaction message may include a type of transaction associated with a primary account number of the cardholder. A type of transaction may be determined from the electronic transaction message. Transaction details may be extracted from the transaction data. The operations may also include determining whether the cardholder is registered for the account event notification service. If based on the determination, the cardholder is registered for the account event notification service, a notification message may be generated. The notification message may include the type of transaction. The notification message may be transmitted to the cardholder.

Abstract: Systems and methods for verifying the current status of a payment card are provided that may efficiently aggregate and distribute non-visible information regarding a recovered payment card. More particularly, the systems and computer-implemented methods of the present invention permit the efficient aggregation of the non-visible payment account data associated with a payment card and the distribution of such data to investigators in possession of the card. Such systems and methods for verifying a payment card typically involve: (a) aggregating payment account data associated with the payment card in an aggregated data storage site; (b) obtaining visible verification data associated with the payment card from an investigator; (c) verifying the visible verification data associated with the payment card; (d) retrieving the payment account data from the aggregated data storage site; and (e) submitting the payment account data to the investigator.

Abstract: An auto-enrollment billing updater (AEBU) computing device for enrolling enrollees in an automatic updating program is provided. The AEBU computing device is configured to receive, from an acquirer computing device, an account update request for updated account data for a set of account identifiers, the account update request including an input acquirer identifier and an input merchant identifier. The AEBU computing device is further configured to perform a lookup within a transaction database using a combination of the input acquirer identifier and the input merchant identifier, wherein the transaction database includes transaction data involving a plurality of cardholders and a plurality of merchants.

Abstract: An automatic billing updater (ABU) computing device is provided. The ABU computing device receives, from a candidate merchant, a batch update request including a plurality of account identifiers and retrieves a plurality of historical account identifiers from an historical authorization database. Each account identifier of the historical account identifiers is associated with a respective historical transaction of the candidate merchant. The ABU computing device further compares the account identifiers of the batch update request to the historical account identifiers, identifies at least one unrequested account identifier from the historical account identifiers based on the comparison, retrieves unrequested billing data associated with the unrequested account identifier from a billing database that stores updated billing data associated with a plurality of payment accounts, and transmits the unrequested billing data to the candidate merchant.

Abstract: Systems and methods are provided for implementing account controls for accounts based on regions in which users associated with the accounts are located. One exemplary method includes receiving location data indicating a location of a communication device associated with an account, where the account is subject to an account control defined in a default currency, and determining a local region of the communication device based on the location data. The method also includes determining a local currency of the local region and converting the account control amount from the default currency to the local currency. The method then further includes notifying a user associated with the account, at the communication device, of the converted account control amount, thereby informing the user of the account control amount in the local currency in connection with transactions to be initiated by the user in the local region and funded by the account.

Abstract: A chargeback processing computing device is provided.

Abstract: Systems and methods for validating and adjusting local transaction times are provided. A host computing system includes a processor and a memory in communication with the processor. The host computing system receives a computer message comprising authorization data associated with a transaction, the authorization data including a location identifier and a local transaction time set by a remote computing device used in processing the transaction. The host computing system also appends a header including a header processor time to the computer message, determines a time zone associated with the local transaction time based on the location identifier, converts the header processor time to a local header processor time based on the time zone, and determines that the local transaction time is validated based on the local header processor time.

Abstract: A merchant advice code system and computer-implemented method for populating a merchant advice code in a payment authorization response message includes a memory device for storing data and a processor communicatively coupled to the memory device. The processor is programmed to receive a payment authorization request message including a primary account number relating to the payment account of a cardholder. The processor is programmed to extract a copy of the primary account number from the payment authorization request message and determine whether the primary account number exists in an automated billing service database. In response to determining that the primary account number exists in the automated billing service database, the processor is programmed to store an indicator in the memory device and populate the merchant advice code in the payment authorization response message with the indicator, thereby generating an edited payment authorization response message.

Abstract: A computer-implemented method for verifying a payment transaction over a payment network. One step of the method includes receiving, from a sender, a transaction message, with the transaction message including a plurality of data element fields, and with at least one of the data element fields being a network-specific field configured to be populated by an interchange network of the payment network. An additional step includes performing a validation routine on the transaction message. The validation routine includes analyzing the network-specific field of the transaction message to determine if the network-specific field is populated with data. A further step includes transmitting a financial transaction denial to the sender if the network-specific field of the transaction message is populated with data.