Systems and methods to manage transaction disputes using predictions based on anomalous data

1. A system for managing transaction disputes, the system comprising:

a first database storing dispute data associated with transactions;

a second database storing updated dispute data associated with the transactions;

a network interface;

at least one processor; and

a non-transitory computer-readable medium containing a set of instructions that, when executed by the at least one processor, cause the at least one processor to perform operations comprising:

accessing a transaction pattern model associated with a user account;

monitoring, at a first time, first data extracts received via the network interface and associated with the user account;

detecting deviation of a transaction from the transaction pattern model based on at least one of the first data extracts monitored at the first time;

transmitting, via the network interface and based on the detected deviation, transaction data to a user device;

receiving an input configured for a first application program interface (API) and entered at the user device in response to the transmitted data;

generating, based on the received input entered at the user device, dispute data configured for a second API different from the first API for which the input was configured;

storing the dispute data at the first database;

monitoring, at a second time, second data extracts for a data profile based on the dispute data, the second data extracts being received via the network interface and associated with the user account;

detecting, based on the monitoring at the second time, one of the second data extracts indicating a posted state of a transaction associated with the dispute data;

updating the dispute data based on the one of the second data extracts indicating the posted state; and

storing the updated dispute data at the second database.

2. The system of claim 1 , the operations further comprising generating the transaction pattern model based on unique transaction data of the user account.

3. The system of claim 1 , the operations further comprising updating the transaction pattern model based on the received input.

4. The system of claim 1 , wherein deviation includes a data element or combination of data elements of transaction data associated with the transaction deviating from at least one parameter of the transaction pattern model.

5. The system of claim 1 , wherein the data profile comprises a combination of data elements comprising at least one of a dispute identifier, a user account identifier, a disputed amount, a transaction amount, a product identifier, a date, a timestamp, an identifier of a method of payment, an image, a signature, or an agent identifier.

6. A method for managing transaction disputes, comprising:

accessing a transaction pattern model associated with a user account;

detecting deviation of a transaction from the transaction pattern model;

transmitting, based on the detected deviation, transaction data to a user device;

receiving an input entered at the user device in response to the transmitted transaction data;

translating the received input to a first application program interface (API) format;

generating, based on the translated input, dispute data configured for a second API different from the first API for which the input was configured;

storing the dispute data;

monitoring data extracts for a data profile based on the dispute data, the data extracts associated with the user account;

detecting, based on the monitoring, one of the data extracts indicating a posted state of a transaction associated with the dispute data; and

updating the dispute data based on the one of the data extracts indicating the posted state.

7. The method of claim 6 further comprising generating the transaction pattern model based on unique transaction data of the user account.

8. The method of claim 7 further comprising updating the transaction pattern model based on the received input.

9. The method of claim 7 , wherein:

the user account is a first user account; and

generating the transaction pattern model is further based on transaction data of a second user account.

10. The method of claim 6 , wherein:

the monitoring of the data extracts occurs during a first time period;

the method comprises monitoring data extracts during a second time period; and

the deviation is detected based on the monitoring during the second time period.

11. The method of claim 6 , wherein the transmitted transaction data comprises data from two similar transactions of the user account that are determined to be similar based on both transactions having at least one of: a same transaction date, a same merchant, a same transaction payment method, or a same transaction amount.

12. The method of claim 6 , wherein the transmitted transaction data comprises data from two similar transactions of the user account that are determined to be similar based on both transactions having at least one of: a transaction date within a threshold number of days of each other, merchants operating in the same industry, merchant names having a threshold number of characters or words in common, or a transaction amount within a threshold amount of each other.

13. The method of claim 6 further comprising formatting the transaction data for display at a user interface of the user device.

14. The method of claim 13 , wherein the input is received at the user interface and comprises at least one of: a dispute reason, a correct transaction amount, an image of a receipt, or an item identifier.

15. The method of claim 6 , wherein:

storing the dispute data comprises storing the dispute data in a first database; and

the method further comprises storing the updated dispute data in a second database.

16. The method of claim 6 further comprising, after detecting the data extract, transmitting an indication of the updated dispute data to the user device.

17. The method of claim 6 , wherein the transaction pattern model is unique to a financial service provider associated with the user account.

18. The method of claim 6 , wherein the deviation includes a data element or combination of data elements of transaction data associated with the transaction deviating from at least one parameter of the transaction pattern model.

19. The method of claim 6 , wherein the data profile comprises a combination of data elements comprising at least one of a dispute identifier, a user account identifier, a disputed amount, a transaction amount, a product identifier, a date, a timestamp, an identifier of a method of payment, an image, a signature, or an agent identifier.