Systems and methods for verifying digital payments

Abstract

Embodiments of the disclosure provide systems and methods for verifying digital payments for a payment platform. The system includes a communication interface configured to receive service data associated with a transaction from a terminal device associated with a user of the payment platform. The system further includes at least one processor configured to automatically determine whether an authentication is waived for the transaction based on the received service data and a blacklist generated using a machine learning model. The blacklist includes a list of suspicious users and transaction behaviors. The at least one processor further configured to approve the transaction without requesting user authentication information from the terminal device when the authentication is waived. The at least one processor also configured to request the user authentication information from the terminal device and validate the user authentication information when the authentication is not waived.

What is claimed is: 
     
         1 . A payment verification system for a payment platform, comprising:
 a communication interface configured to receive service data associated with a transaction from a terminal device associated with a user of the payment platform;   at least one processor configured to:
 generate a blacklist using at least one machine learning model, wherein the blacklist includes a set of keys associated with suspicious users and transaction behaviors; 
 maintain the blacklist in a memory associated with the payment platform; 
 automatically determine an authentication is waived for the transaction and approve the transaction without requesting user authentication information from the terminal device when the service data received from the terminal device do not match any key of the set of keys associated with the suspicious users and the transaction behaviors included in the blacklist; and 
 automatically determine the authentication is not waived and request the user authentication information from the terminal device for validation when at least one of the service data matches one or more keys of the set of keys included in the blacklist. 
   
     
     
         2 . The payment verification system of  claim 1 , wherein to generate the blacklist using the at least one machine learning model, the at least one processor is further configured to:
 classify users into a group of suspicious users and a group of safe users using the at least one machine learning model; and   add identifications of the suspicious users to the blacklist.   
     
     
         3 . The payment verification system of  claim 1 , wherein to generate the blacklist using the at least one machine learning model, the at least one processor is further configured to:
 generate rules of suspicious transaction behaviors using the at least one machine learning model; and   add thresholds associated with the rules of the suspicious transaction behaviors to the blacklist.   
     
     
         4 . The payment verification system of  claim 1 , wherein the keys associated with the suspicious users are generated by a first machine learning model and the keys associated with the transaction behaviors are generated by a second machine learning model different from the first machine learning model. 
     
     
         5 . The payment verification system of  claim 4 , wherein the first machine learning model and the second machine learning model are trained at different frequencies. 
     
     
         6 . The payment verification system of  claim 1 , wherein the service data associated with the transaction further comprises at least one of a transaction amount, service information, recipient information, a user profile, previous trips, geo-locations, an Internet Protocol (IP) address of the terminal device, or an environmental identifier of the terminal device. 
     
     
         7 . The payment verification system of  claim 1 , the at least one processor is further configured to:
 validate the user authentication information;   approve the transaction when the user authentication information is validated; and   block the transaction when the user authentication information fails to validate.   
     
     
         8 . The payment verification system of  claim 1 , wherein the at least one machine learning model is retrained using service data logs that reflect an updated transaction pattern,
 wherein the at least one processor is further configured to:
 update the blacklist using the retrained machine learning model. 
   
     
     
         9 . The payment verification system of  claim 8 , wherein the at least one machine learning model is retained at a predetermined frequency,
 wherein blacklist is updated periodically using the retrained machine learning model.   
     
     
         10 . The payment verification system of  claim 1 , wherein the at least one machine learning model includes at least one of a deep learning model, a rule-based model, or a support vector machine (SVM). 
     
     
         11 . A payment verification method for a payment platform, comprising:
 receiving, by a communication interface of a processing device, service data associated with a transaction from a terminal device associated with a user of the payment platform;   generating, by at least one processor of the processing device, a blacklist using at least one machine learning model, wherein the blacklist includes a set of keys associated with suspicious users and transaction behaviors;   maintaining, by the at least one processor of the processing device, the blacklist in a memory of the processing device;   automatically determining, by the at least one processor of the processing device, an authentication is waived for the transaction and approve the transaction without requesting user authentication information from the terminal device when the service data received from the terminal device do not match any key of the set of keys associated with the suspicious users and the transaction behaviors included in the blacklist; and   automatically determining, by the at least one processor of the processing device, the authentication is not waived and request the user authentication information from the terminal device for validation when at least one of the service data matches one or more keys of the set of keys included in the blacklist.   
     
     
         12 . The payment verification method of  claim 11 , wherein generating the blacklist using the at least one machine learning model further comprises:
 classifying users into a group of suspicious users and a group of safe users using the at least one machine learning model; and   adding identifications of the suspicious users to the blacklist.   
     
     
         13 . The payment verification method of  claim 11 , wherein generating the blacklist using the at least one machine learning model further comprises:
 generating rules of suspicious transaction behaviors using the at least one machine learning model; and   adding thresholds associated with the rules of the suspicious transaction behaviors to the blacklist.   
     
     
         14 . The payment verification method of  claim 11 , wherein the keys associated with the suspicious users are generated by a first machine learning model and the keys associated with the transaction behaviors are generated by a second machine learning model different from the first machine learning model. 
     
     
         15 . The payment verification method of  claim 14 , wherein the first machine learning model and the second machine learning model are trained at different frequencies. 
     
     
         16 . The payment verification method of  claim 11 , wherein the service data associated with the transaction further comprises at least one of a transaction amount, service information, recipient information, a user profile, previous trips, geo-locations, an Internet Protocol (IP) address of the terminal device, or an environmental identifier of the terminal device. 
     
     
         17 . The payment verification method of  claim 11 , further comprising:
 validating the user authentication information;   approving the transaction when the user authentication information is validated; and   blocking the transaction when the user authentication information fails to validate.   
     
     
         18 . The payment verification method of  claim 11 , wherein the at least one machine learning model is retrained at a predetermined frequency using service data logs that reflect an updated transaction pattern,
 wherein the method further comprises:
 updating the blacklist periodically using the retrained machine learning model. 
   
     
     
         19 . The payment verification method of  claim 11 , wherein the at least one machine learning model includes at least one of a deep learning model, a rule-based model, or a support vector machine (SVM). 
     
     
         20 . A non-transitory computer-readable medium having instructions stored thereon that, when executed by at least one processor, causes the at least one processor to perform a payment verification method for a payment platform, the payment verification method comprising:
 receiving, by a communication interface of a processing device, service data associated with a transaction from a terminal device associated with a user of the payment platform;   generating a blacklist using at least one machine learning model, wherein the blacklist includes a set of keys associated with suspicious users and transaction behaviors;   automatically determining, by the at least one processor of the processing device, an authentication is waived for the transaction and approve the transaction without requesting user authentication information from the terminal device when the service data received from the terminal device do not match any key of the set of keys associated with the suspicious users and the transaction behaviors included in the blacklist; and   automatically determining the authentication is not waived and request the user authentication information from the terminal device for validation when at least one of the service data matches one or more keys of the set of keys included in the blacklist.