Abstract: A refund tracking (RT) computing device including a processor and a memory in communication with the processor is provided. The RT computing device is configured to receive historical transaction data from a payment network or a merchant data source, the historical transaction data received in different formats, parse data fields from the historical transaction data, store the parsed data fields for each of the transactions in a respective harmonized refund data structure in a database, receive current transaction data for a current transaction from a merchant computing device, retrieve at least one harmonized refund data structure from the database, determine a refund risk score based on comparing the current transaction data to the at least one harmonized refund data structure, and transmit the refund risk score to the merchant terminal.

Abstract: An automatic billing enrollment (ABE) computing device and methods for automatically enrolling a merchant in a bill paying application are provided. The ABE computing device receives a payment transaction associated with a cardholder account, identifies a merchant associated with the payment transaction, and determines whether the merchant is enrolled with a bill pay application associated with the cardholder account by performing a database lookup of enrolled merchants. The ABE computing device then transmits a message to a user device associated with the cardholder account indicating that the identified merchant is not enrolled by the cardholder with the bill pay application and includes an option for the cardholder to enroll the merchant. To enroll the merchant, the ABE computing device determines merchant-associated data elements required by the bill pay application to enroll the merchant, retrieves the data elements, and inputs the data elements into the bill pay application.

Abstract: A method for verified data storage via blockchain includes: storing a blockchain comprised of a plurality of blocks, each comprised of a block header and a plurality of transaction values, the block header including a timestamp; receiving a transaction notification including an entity identifier and data values; validating the data values based on a validation notification received from a verifying entity; generating a new block header comprised of a current timestamp, a block reference value, and a transaction reference value, the block reference value being generated via hashing of the block header included in a most recent block based on the timestamp, and the transaction reference value being generated via hashing of new transaction values including the data values; generating a new block comprised of the generated new block header and the new transaction values; and transmitting the new block to a node associated with the blockchain.

Abstract: An automatic billing enrollment (ABE) computing device and methods for automatically enrolling a merchant in a bill paying application are provided. The ABE computing device receives a payment transaction associated with a cardholder account, identifies a merchant associated with the payment transaction, and determines whether the merchant is enrolled with a bill pay application associated with the cardholder account by performing a database lookup of enrolled merchants. The ABE computing device then transmits a message to a user device associated with the cardholder account indicating that the identified merchant is not enrolled by the cardholder with the bill pay application and includes an option for the cardholder to enroll the merchant. To enroll the merchant, the ABE computing device determines merchant-associated data elements required by the bill pay application to enroll the merchant, retrieves the data elements, and inputs the data elements into the bill pay application.

Abstract: An automatic billing enrollment (ABE) computing device and methods for automatically enrolling a merchant in a bill paying application are provided. The ABE computing device receives a payment transaction associated with a cardholder account, identifies a merchant associated with the payment transaction, and determines whether the merchant is enrolled with a bill pay application associated with the cardholder account by performing a database lookup of enrolled merchants. The ABE computing device then transmits a message to a user device associated with the cardholder account indicating that the identified merchant is not enrolled by the cardholder with the bill pay application and includes an option for the cardholder to enroll the merchant. To enroll the merchant, the ABE computing device determines merchant-associated data elements required by the bill pay application to enroll the merchant, retrieves the data elements, and inputs the data elements into the bill pay application.

Abstract: A refund tracking (RT) computing device including a processor and a memory in communication with the processor is provided. The RT computing device is configured to receive historical transaction data from a payment network or a merchant data source, the historical transaction data received in different formats, parse data fields from the historical transaction data, store the parsed data fields for each of the transactions in a respective harmonized refund data structure in a database, receive current transaction data for a current transaction from a merchant computing device, retrieve at least one harmonized refund data structure from the database, determine a refund risk score based on comparing the current transaction data to the at least one harmonized refund data structure, and transmit the refund risk score to the merchant terminal.

Abstract: A method for verified data storage via blockchain includes: storing a blockchain comprised of a plurality of blocks, each comprised of a block header and a plurality of transaction values, the block header including a timestamp; receiving a transaction notification including an entity identifier and data values; validating the data values based on a validation notification received from a verifying entity; generating a new block header comprised of a current timestamp, a block reference value, and a transaction reference value, the block reference value being generated via hashing of the block header included in a most recent block based on the timestamp, and the transaction reference value being generated via hashing of new transaction values including the data values; generating a new block comprised of the generated new block header and the new transaction values; and transmitting the new block to a node associated with the blockchain.