US 12,293,355 B2
Status system with data security for transactions
Deborah Bernert, Stamford, CT (US); Ashok Uppalapati, Stamford, CT (US); Taylor Young, Stamford, CT (US); Jonathan Schmidt, Stamford, CT (US); Nicholas White, Stamford, CT (US); James J. Wallace, Stamford, CT (US); and Viveka Vardhan Ravi, Stamford, CT (US)
Assigned to Synchrony Bank, Stamford, CT (US)
Filed by Synchrony Bank, Stamford, CT (US)
Filed on Jun. 17, 2021, as Appl. No. 17/350,415.
Claims priority of provisional application 63/040,258, filed on Jun. 17, 2020.
Prior Publication US 2021/0398113 A1, Dec. 23, 2021
Int. Cl. G06Q 20/38 (2012.01); G06Q 20/40 (2012.01)
CPC G06Q 20/3825 (2013.01) [G06Q 20/389 (2013.01); G06Q 20/401 (2013.01)] 15 Claims
OG exemplary drawing
 
1. A computer-implemented method, comprising:
receiving client information, wherein when the client information is received from a client device via a modal on the client device, the modal is automatically generated;
receiving, at an account security system having one or more processors, a status inquiry associated with a secure transaction, a merchant system, and a closure of the modal on a client device;
automatically processing the status inquiry in real-time to determine that the merchant system has been previously validated and that the status inquiry is from the merchant system;
verifying the status inquiry using a machine learning model, wherein the machine learning model is trained to identify one or more patterns in status queries, wherein the patterns are associated with fraud, and wherein the machine learning model is trained to generate fraud alerts when fraudulent patterns are identified;
generating a tokenized client account number using the client information, wherein generating is based on verifying the status inquiry;
accessing data including the tokenized client account number, wherein accessing is part of a real-time automatic response to the determination that the merchant system has been previously validated;
sharing the tokenized client account number with a separate system to allow the merchant system to settle payment for the secure transaction with the separate system without the merchant system having access to the client information; and
automatically transmitting the data in real time, wherein when the data is associated with a push system, the data is pushed to a merchant uniform resource locator, wherein the data includes the tokenized client account number, and wherein the tokenized client account number facilitates processing of the secure transaction by the merchant system without the merchant system having access to the client information.