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

1. 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, via a network interface and based on the detected deviation, transaction data to a user device, the transaction data including deviation data, wherein the deviation data indicates a potentially erroneous transaction;

receiving input data entered at the user device in response to the transmitted transaction data, wherein the input data includes a transaction status indicator that indicates that a user identifies the transaction as erroneous;

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

determining a dispute status based on the transaction data, the deviation data, the transaction status indicator, and the input data; and

on a condition that the dispute status indicates that a transaction is disputed, generating dispute data based on the input data, the transaction status indicator, and the transaction data.

2. The method of claim 1 , wherein the dispute status includes a likelihood of an accuracy of the transaction status indicator.

3. The method of claim 2 , wherein the likelihood is based on at least one of: the transaction data, account data relating to the user, the input data, or the deviation data.

4. The method of claim 1 , further comprising:

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.

5. The method of claim 4 , 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.

6. The method of claim 4 , wherein:

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

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

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

7. The method of claim 1 , further comprising:

generating the transaction pattern model based on unique transaction data of the user account.

8. 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.

9. The method of claim 7 , further comprising:

updating the transaction pattern model based on the received input.

10. The method of claim 1 , 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.

11. The method of claim 1 , 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.

12. The method of claim 1 , further comprising:

formatting the transaction data for display at a user interface of the user device, 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.

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

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;

detecting deviation of a transaction from the transaction pattern model;

transmitting, via the network interface and based on the detected deviation, transaction data to a user device, the transaction data including deviation data, wherein the deviation data indicates a potentially erroneous transaction;

receiving input data entered at the user device in response to the transmitted transaction data, wherein the input data includes a transaction status indicator that indicates that a user identifies the transaction as erroneous;

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

determining a dispute status based on the transaction data, the deviation data, the transaction status indicator, and the input data; and

on a condition that the dispute status indicates that a transaction is disputed, generating dispute data based on the input data, the transaction status indicator, and the transaction data.

14. The system of claim 13 , the operations further comprising:

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.

15. The system of claim 14 , wherein:

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

the operations further comprise storing the updated dispute data in a second database.

16. The system of claim 14 , wherein:

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

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

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

17. The system of claim 13 , the operations further comprising:

generating the transaction pattern model based on unique transaction data of the user account.

18. The system of claim 17 , 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.

19. The system of claim 17 , the operations further comprising:

updating the transaction pattern model based on the received input.

20. The system of claim 13 , 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.