US2014372322A1PendingUtilityA1

Registered tokens for secure transaction management

Assignee: FIRST DATA CORPPriority: Dec 30, 2009Filed: Jun 19, 2014Published: Dec 18, 2014
Est. expiryDec 30, 2029(~3.4 yrs left)· nominal 20-yr term from priority
G06Q 20/04G06Q 20/382G06Q 20/10G06Q 20/4014G06Q 2220/00H04L 9/3234H04L 2209/56G06Q 20/20G06Q 20/204G06Q 20/385G06Q 20/3829H04L 63/083G06Q 40/00G06Q 20/40G06Q 40/02G06Q 20/3821H04L 9/3236
58
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Methods, systems, and devices for secure transaction management are provided. Embodiments include a method for providing secure transactions that include receiving an identifier of a financial account at a payment processor system. A token may be generated that is linked with the identifier of the financial account at the payment processor system. The identifier of the financial account and the token may be stored securely at the payment processor system. The token may be transmitted without the identifier of the financial account to at least a recipient system or a recipient device where the token replaces the identifier of the financial account.

Claims

exact text as granted — not AI-modified
1 - 22 . (canceled) 
     
     
         23 . A method for providing secure transactions, the method comprising:
 receiving an identifier of a financial account;   creating a customer identifier linking a customer to a merchant, the customer identifier associated with the identifier of the financial account;   storing the identifier of the financial account and the customer identifier;   initiating a transaction using the customer identifier;   transmitting the customer identifier or the identifier of the financial account to a payment processor system for transmission to a financial institution;   receiving authorization and a token associated with the customer identifier and the identifier of the financial account, wherein the token comprises a random number; and   replacing the identifier of the financial account with the token to limit the use of the identifier of the financial account for enhanced security.   
     
     
         24 . The method for providing secure transactions of  claim 23 , further comprising:
 encrypting the identifier of the financial account.   
     
     
         25 . The method for providing secure transactions of  claim 24 , wherein:
 encrypting the identifier of the financial account utilizes an asymmetric key.   
     
     
         26 . The method for providing secure transactions of  claim 23 , wherein:
 a first checksum from the token equals a second checksum from the identifier of the financial account.   
     
     
         27 . The method for providing secure transactions of  claim 23 , further comprising:
 initiating at least a transaction adjustment, a transaction refund, or a transaction settlement using the token.   
     
     
         28 . The method for providing secure transactions of  claim 23 , further comprising:
 enrolling the customer in a registered card program.   
     
     
         29 . The method for providing secure transactions of  claim 23 , wherein:
 the token includes a subset of digits that form a sequence of digits that are the same as in the identifier of the financial account.   
     
     
         30 . A computer program embodied on a computer readable medium, the computer program comprising instructions executable by a computer to:
 receive an identifier of the financial account;   create a customer identifier linking a customer to a merchant, the customer identifier associated with the identifier of the financial account;   store the identifier of the financial account and the customer identifier;   initiate a transaction using the customer identifier;   transmit the customer identifier or the identifier of the financial account to a payment processor system for transmission to a financial institution;   receive authorization and a token associated with the customer identifier and the identifier of the financial account, wherein the token comprises a random number; and   replace the identifier of the financial account with the token to limit the use of the identifier of the financial account for enhanced security.   
     
     
         31 . The computer program embodied on a computer readable medium of  claim 30 , wherein the computer program further comprises instructions executable by a computer to:
 encrypt the at least one of the one or more identifiers of financial accounts.   
     
     
         32 . The computer program embodied on a computer readable medium of  claim 31 , wherein:
 encryption of the identifier of the financial account utilizes an asymmetric key.   
     
     
         33 . The computer program embodied on a computer readable medium of  claim 30 , wherein:
 a first checksum from the token equals a second checksum from the identifier of the financial account.   
     
     
         34 . The computer program embodied on a computer readable medium of  claim 30 , wherein the computer program further comprises instructions executable by a computer to:
 initiate at least a transaction adjustment, a transaction refund, or a transaction settlement using the token.   
     
     
         35 . The computer program embodied on a computer readable medium of  claim 30 , wherein the computer program further comprises instructions executable by a computer to:
 enroll the customer in a registered card program.   
     
     
         36 . The computer program embodied on a computer readable medium of  claim 30 , wherein:
 the token includes a subset of digits that form a sequence of digits that are the same as in the identifier of the financial account.   
     
     
         37 . A system for providing secure transactions, the system comprising:
 an input component for receiving an identifier of the financial account;   a processor communicatively coupled with the input component;   an output component communicatively coupled with the processor;   a memory communicatively coupled with and readable by the processor, the memory having stored therein a series of instructions which, when executed by the processor, cause the processor to:
 create a customer identifier linking a customer to a merchant, the customer identifier associated with the identifier of the financial account; 
 store the identifier of the financial account and the customer identifier; 
 initiate a transaction using the customer identifier; 
 transmit the customer identifier or the identifier of the financial account to a payment processor system for transmission to a financial institution; 
 receive authorization and a token associated with the customer identifier and the identifier of the financial account, wherein the token comprises a random number; and 
 replace the identifier of the financial account with the token to limit the use of the identifier of the financial account for enhanced security. 
   
     
     
         38 . The system for providing secure transactions of  claim 37 , wherein the series of instructions further comprises instructions causing the processor to:
 encrypt the identifier of the financial account.   
     
     
         39 . The system for providing secure transactions of  claim 38 , wherein:
 encryption of the identifier of the financial account utilizes an asymmetric key.   
     
     
         40 . The system for providing secure transactions of  claim 37 , wherein:
 a first checksum from the token equals a second checksum from the identifier of the financial account.   
     
     
         41 . The system for providing secure transactions of  claim 37 , wherein the series of instructions further comprises instructions causing the processor to:
 enroll the customer in a registered card program.   
     
     
         42 . The system for providing secure transactions of  claim 37 , wherein:
 the token includes a subset of digits that form a sequence of digits that are the same as in the identifier of the financial account

Join the waitlist — get patent alerts

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

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