Encapsulation of payment accounts with nested tokens

Abstract

A method for encapsulating transaction instrument information in a transaction includes storing, in association with a first transaction and by a processor of the primary transaction processor server, payment data associated with a payment instrument used to settle a cost of a first transaction. The primary transaction processor server transmits the transaction data to a payment network processor. The primary transaction processor server receives an authorization package from the payment network processor that includes a cryptograph and a first network token. The processor of the primary transaction processor server generates a secondary token, and stores a correlation record to a computer-readable memory. The correlation record associates the secondary token to a second object stored by the primary transaction processor. The processor of the primary transaction processor server transmits a second transaction package including at least one of the network token and the secondary token to a merchant device.

What is claimed is: 
     
       1. A method comprising:
 receiving, by a server of a primary transaction processor, payment instrument data associated with a payment instrument used to settle a cost of a first transaction; 
 storing, by the server of the primary transaction processor, the payment instrument data; 
 sending, by the server of the primary transaction processor and to a payment network processor, a first request for authorization of the first transaction including the payment instrument data; 
 receiving, by server of the primary transaction processor and from the payment network processor, an authorization package comprising a cryptograph and a network token; 
 generating, by the server of the primary transaction processor, a secondary token associated with the payment instrument, wherein the secondary token comprises a token identification field indicating an initiator of a transaction occurring after the first transaction; 
 assigning, by the server of the primary transaction processor in association with a merchant device associated with a merchant, a merchant identifier of the merchant device as a value of the token identification field; 
 generating, by the server of the primary transaction processor, a correlation record of the associated secondary token with the payment instrument stored by the primary transaction processor, wherein the secondary token is a multi-use token; 
 sending, by the server of the primary transaction processor, a transaction package comprising the network token and the secondary token to the merchant device; 
 receiving, by the server of the primary transaction processor, information associated with a second transaction from the merchant device, wherein the information associated with the second transaction includes the secondary token comprising the token identification field, wherein the token identification field indicates the initiator of the second transaction is the merchant; and 
 sending, by the server of the primary transaction processor to the payment network processor, a second request for authorization of the second transaction, wherein the second request comprises the information associated with the second transaction including the secondary token. 
 
     
     
       2. The method of  claim 1 , wherein a payment object is associated with the payment instrument. 
     
     
       3. The method of  claim 1 , wherein the secondary token does not include a cryptograph. 
     
     
       4. The method of  claim 1 , further comprising determining, by the merchant device, to refrain from storing a copy of the payment instrument after sending the payment instrument to the primary transaction processor to settle the cost of the first transaction. 
     
     
       5. The method of  claim 1 , further comprising, storing the secondary token in a merchant datastore as a proxy for the payment instrument. 
     
     
       6. The method of  claim 1 , further comprising:
 connecting the primary transaction processor via an I-frame portal to the merchant device such that the payment instrument data is not sent to a storage medium on the merchant device. 
 
     
     
       7. A system comprising:
 one or more processors; and 
 non-transitory computer-readable media storing instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
 receiving payment instrument data associated with a payment instrument used to settle a cost of a first transaction; 
 storing the payment instrument data to settle the cost of the first transaction; 
 sending the payment instrument data to a payment network processor; 
 receiving, from the payment network processor, an authorization package comprising a cryptograph and a network token; 
 generating a secondary token associated with the payment instrument, wherein the secondary token comprises a token identification field indicating an initiator of a transaction occurring after the first transaction; 
 assigning, in association with a merchant device of a merchant, a merchant identifier of the merchant device as the value of the token identification field; 
 storing a correlation record of the associated secondary token with the payment instrument, wherein the secondary token is a multi-use token; 
 sending a transaction package comprising the network token and the secondary token to the merchant device; 
 receiving information associated with a second transaction from the merchant device, wherein the information associated with the second transaction includes the secondary token comprising the token identification field, wherein the token identification field indicates the initiator of the second transaction is the merchant; and 
 sending, to the payment network processor, a second request for authorization of the second transaction, wherein the second request comprises the information associated with the second transaction including the secondary token. 
 
 
     
     
       8. The system of  claim 7 , wherein a payment object is associated with the payment instrument. 
     
     
       9. The system of  claim 7 , wherein the secondary token does not include a cryptograph. 
     
     
       10. The system of  claim 7 , wherein the merchant device refrains from storing a copy of the payment instrument data after sending the payment instrument data. 
     
     
       11. The system of  claim 7 , the operations further comprising, storing the secondary token in a merchant datastore as a proxy for the payment instrument. 
     
     
       12. Non-transitory computer-readable media comprising computer readable instructions that when executed by one or more processors, cause the one or more processors to perform operations comprising:
 receiving payment instrument data associated with a payment instrument used to settle a cost of a first transaction; 
 storing the payment instrument data to settle the cost of the first transaction; 
 sending a first request for authorization of the first transaction including the payment instrument data to a payment network processor; 
 receiving, from the payment network processor, an authorization package comprising a cryptograph and a network token; 
 generating a secondary token associated with the payment instrument, wherein the secondary token comprises a token identification field indicating an initiator of a transaction occurring after the first transaction; 
 assigning, in association with a merchant device of a merchant, a merchant identifier of the merchant device as the value of the token identification field; 
 storing a correlation record of the associated secondary token with the payment instrument, wherein the secondary token is a multi-use token; 
 sending a transaction package comprising the network token and the secondary token to the merchant device; 
 receiving information associated with a second transaction from the merchant device, wherein the information associated with the second transaction includes the secondary token comprises the token identification field, wherein the token identification field indicates the initiator of the second transaction is the merchant; and 
 sending, to the payment network processor, a second request for authorization of the second transaction, wherein the second request comprises the information associated with the second transaction including the secondary token. 
 
     
     
       13. The non-transitory computer-readable media of  claim 12 , wherein the secondary token does not include a cryptograph. 
     
     
       14. The non-transitory computer-readable media of  claim 12 , wherein the merchant device refrains from storing a copy of the payment instrument data after sending the payment instrument data. 
     
     
       15. The non-transitory computer-readable media of  claim 12 , the operations further comprising storing the secondary token in a merchant datastore as a proxy for the payment instrument. 
     
     
       16. The method of  claim 1 , wherein approval for the second transaction is based at least in part on an identified relationship between a merchant of the merchant device and a secondary transaction processor. 
     
     
       17. The system of  claim 7 , wherein the approval for the second transaction is based at least in part on an identified relationship between a merchant of the merchant device and a transaction processing server. 
     
     
       18. The non-transitory computer-readable media of  claim 12 , wherein the approval for the second transaction is based at least in part on an identified relationship between the merchant and a transaction processing server.