US2021326875A1PendingUtilityA1

User account controls for online transactions

Assignee: CAPITAL ONE SERVICES LLCPriority: Oct 19, 2017Filed: Jun 28, 2021Published: Oct 21, 2021
Est. expiryOct 19, 2037(~11.2 yrs left)· nominal 20-yr term from priority
G06Q 30/0641G06Q 30/0609G06Q 20/385G06Q 20/3278G06Q 20/204G06Q 20/12G06Q 20/351G06Q 20/405G06Q 20/3221G06F 40/174
54
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A device may receive, from a user device, transaction data, the transaction data including: a user account identifier indicating a user account associated with the user device, and data indicating a particular merchant associated with a transaction. The device may provide the data indicating the particular merchant to a server device and receive, from the server device, a merchant identifier for the particular merchant associated with the transaction. The device may then identify, based on the merchant identifier and the user account identifier, a user account control, the user account control specifying a restriction for transactions associated with the user account and the particular merchant. Based on the transaction data, the device may determine whether the user account control is satisfied and perform an action based on a result of the determination.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method, comprising:
 receiving, by a device and from a user device, transaction data,
 the transaction data including:
 a user account identifier indicating a user account associated with the user device, and 
 data indicating a particular merchant associated with a transaction; 
 
   providing, by the device, the data indicating the particular merchant to a server device;   receiving, by the device and from the server device, a merchant identifier for the particular merchant associated with the transaction;   identifying, by the device and based on the merchant identifier and the user account identifier, a user account control,
 the user account control specifying a restriction for transactions associated with the user account and the particular merchant; 
   determining, by the device and based on the transaction data, whether the user account control is satisfied; and   performing, by the device, an action based on a result of the determination of whether the user account control is satisfied.   
     
     
         2 . The method of  claim 1 , wherein identifying the user account control includes:
 accessing, based on the user account identifier, user account data,
 the user account data specifying:
 a plurality of merchants that includes the particular merchant, 
 a user payment account associated with each merchant of the plurality of merchants, and 
 a user account control associated each merchant of the plurality of merchants. 
 
   
     
     
         3 . The method of  claim 2 , wherein the user payment account is associated with the particular merchant and at least one other merchant of the plurality of merchants. 
     
     
         4 . The method of  claim 2 , wherein performing the action includes:
 providing a secure token to the user device,
 the secure token including data representing the user payment account. 
   
     
     
         5 . The method of  claim 2 , wherein the user account control includes:
 a restriction on a total value of all transactions associated with the user payment account;   a restriction on a total value of all transactions associated with the particular merchant;   a restriction on a total value of all transactions associated with a particular merchant category associated with the particular merchant;   a restriction on an individual transaction value for a single transaction associated with the user payment account;   a restriction on an individual transaction value for a single transaction associated with the particular merchant;   a restriction on an individual transaction value for a single transaction associated with the particular merchant category associated with the particular merchant;   a restriction, associated with the user payment account, on a cumulative transaction value over a period of time;   a restriction, associated with the particular merchant, on a cumulative transaction value over a period of time;   a restriction, associated with the particular merchant category associated with the particular merchant, on a cumulative transaction value over a period of time;   a restriction on a transaction frequency for transactions associated with the user payment account;   a restriction on a transaction frequency for transactions associated with the particular merchant;   a restriction on a transaction frequency for transactions associated with the particular merchant category associated with the particular merchant;   a restriction on a user device for use in transactions associated with the user payment account;   a restriction on a user device for use in transactions associated with the particular merchant; or   a restriction on a user device for use in transactions associated with the particular merchant category associated with the particular merchant.   
     
     
         6 . A non-transitory computer-readable medium storing instructions, the instructions comprising:
 one or more instructions that, when executed by one or more processors, cause the one or more processors to:
 receive, from a user device, merchant payment data specifying payment data for each merchant of a plurality of merchants,
 the payment data indicating:
 a user payment account for making payments to the merchant, and 
 at least one merchant specific control that specifies at least one restriction for transactions associated with the merchant; 
 
 
 associate the merchant payment data with a user account associated with the user device; 
 receive transaction data from the user device,
 the transaction data including:
 a user account identifier indicating the user account, 
 data indicating a particular merchant associated with a transaction, 
  the particular merchant being one of the plurality of merchants, and 
 a transaction value associated with the transaction; 
 
 
 identify, based on the transaction data and the merchant payment data, at least one merchant specific control associated with the particular merchant; 
 determine, based on the transaction data, whether the at least one merchant specific control associated with the particular merchant is satisfied; and 
 perform an action based on the determination of whether the at least one merchant specific control associated with the particular merchant is satisfied. 
   
     
     
         7 . The non-transitory computer-readable medium of  claim 6 , where:
 the data, indicating the particular merchant associated with the transaction, includes at least a portion of a resource locator, and   where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
 determine that the data indicates the particular merchant by:
 providing the at least the portion of the resource locator to a server device; and 
 receiving, from the server device, data specifying that the at least the portion of the resource locator indicates the particular merchant. 
 
   
     
     
         8 . The non-transitory computer-readable medium of  claim 6 , wherein the one or more instructions, that cause the one or more processors to identify the at least one merchant specific control associated with the particular merchant, cause the one or more processors to:
 access, based on the user account identifier, the merchant payment data associated with the user account; and   identify the at least one merchant specific control from the merchant payment data and based on the data indicating the particular merchant.   
     
     
         9 . The non-transitory computer-readable medium of  claim 6 , wherein the one or more instructions, that cause the one or more processors to perform the action, cause the one or more processors to:
 provide response data to the user device,
 the response data indicating a result of the determination of whether the at least one merchant specific control associated with the particular merchant is satisfied. 
   
     
     
         10 . The non-transitory computer-readable medium of  claim 6 , wherein the one or more instructions, that cause the one or more processors to perform the action, cause the one or more processors to:
 provide auto-fill data to the user device,
 the auto-fill data including data indicating the user payment account. 
   
     
     
         11 . The non-transitory computer-readable medium of  claim 6 , wherein the one or more instructions, that cause the one or more processors to perform the action, cause the one or more processors to:
 provide a secure token to the user device,
 the secure token including data representing the user payment account. 
   
     
     
         12 . The non-transitory computer-readable medium of  claim 6 , wherein the one or more instructions, that cause the one or more processors to perform the action, cause the one or more processors to:
 provide authorization data to an authorization device associated with the user device,
 the authorization data including data that causes the authorization device to prompt a user of the authorization device for user input authorizing the transaction. 
   
     
     
         13 . The non-transitory computer-readable medium of  claim 6 , wherein the at least one merchant specific control specifies at least one of:
 a restriction on a total value of all transactions;   a restriction on an individual transaction value for a single transaction;   a restriction on a cumulative transaction value over a period of time;   a restriction on a transaction frequency for transactions; or   a restriction on a user device for use in transactions.   
     
     
         14 . A device, comprising:
 one or more memories; and   one or more processors, coupled to the one or more memories, configured to:
 receive, from a user device, transaction data,
 the transaction data including:
 a user account identifier indicating a user account associated with the user device, and 
 data indicating a particular merchant associated with a transaction; 
 
 
 provide the data indicating the particular merchant to a server device; 
 receive, from the server device, a merchant identifier for the particular merchant associated with the transaction; 
 identify, based on the merchant identifier and the user account identifier, a user account control,
 the user account control specifying a restriction for transactions associated with the user account and the particular merchant; 
 
 determine, based on the transaction data, whether the user account control is satisfied; and 
 perform an action based on a result of the determination of whether the user account control is satisfied. 
   
     
     
         15 . The device of  claim 14 , wherein the one or more processors, to identify the user account control, are configured to:
 access, based on the user account identifier, user account data,
 the user account data specifying:
 a plurality of merchants that includes the particular merchant, 
 a user payment account associated with each merchant of the plurality of merchants, and 
 a user account control associated each merchant of the plurality of merchants. 
 
   
     
     
         16 . The device of  claim 15 , wherein the user payment account is associated with the particular merchant and at least one other merchant of the plurality of merchants. 
     
     
         17 . The device of  claim 15 , wherein the one or more processors, to perform the action, are configured to:
 provide a secure token to the user device,
 the secure token including data representing the user payment account. 
   
     
     
         18 . The device of  claim 15 , wherein the user account control includes:
 a restriction on a total value of all transactions associated with the user payment account;   a restriction on a total value of all transactions associated with the particular merchant;   a restriction on a total value of all transactions associated with a particular merchant category associated with the particular merchant;   a restriction on an individual transaction value for a single transaction associated with the user payment account;   a restriction on an individual transaction value for a single transaction associated with the particular merchant;   a restriction on an individual transaction value for a single transaction associated with the particular merchant category associated with the particular merchant;   a restriction, associated with the user payment account, on a cumulative transaction value over a period of time;   a restriction, associated with the particular merchant, on a cumulative transaction value over a period of time;   a restriction, associated with the particular merchant category associated with the particular merchant, on a cumulative transaction value over a period of time;   a restriction on a transaction frequency for transactions associated with the user payment account;   a restriction on a transaction frequency for transactions associated with the particular merchant;   a restriction on a transaction frequency for transactions associated with the particular merchant category associated with the particular merchant;   a restriction on a user device for use in transactions associated with the user payment account;   a restriction on a user device for use in transactions associated with the particular merchant; or   a restriction on a user device for use in transactions associated with the particular merchant category associated with the particular merchant.   
     
     
         19 . The device of  claim 14 , wherein the one or more processors, when performing the action, are configured to:
 provide a secure token to be included in auto-fill data; and   transmit the secure token to a merchant device associated with the particular merchant.   
     
     
         20 . The device of  claim 19 , wherein the one or more processors are further configured to:
 receive the secure token from the server device.

Join the waitlist — get patent alerts

Track US2021326875A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.