Methods and systems for securely facilitating cross-platform token compatibility via multi-tokenization

Abstract

Systems and methods are disclosed for cross-platform token compatibility. One method comprises receiving, by a token exchange service system, a primary tokenization request from an upstream entity, generating, by the token exchange service system, one or more ancillary tokenization requests based on the primary tokenization request, and transmitting, by the token exchange service system, the one or more ancillary tokenization requests to respective one or more output token vaults. One or more ancillary tokenization responses may then be received from the one or more output token vaults, and a primary tokenization response may be generated based on the one or more ancillary tokenization responses. The primary tokenization response may be transmitted to the upstream entity.

What is claimed is: 
     
         1 . A computer-implemented method for cross-platform token compatibility, comprising:
 receiving, by a token exchange service system, a primary tokenization request from an upstream entity;   generating, by the token exchange service system, one or more ancillary tokenization requests based on the primary tokenization request;   transmitting, by the token exchange service system, the one or more ancillary tokenization requests to respective one or more output token vaults;   receiving, by the token exchange service system, one or more ancillary tokenization responses from the respective one or more output token vaults;   generating, by the token exchange service system, a primary tokenization response based on the one or more ancillary tokenization responses; and   transmitting, by the token exchange service system, the primary tokenization response to the upstream entity.   
     
     
         2 . The method of  claim 1 , wherein the primary tokenization request is an application programming interface (API) request. 
     
     
         3 . The method of  claim 1 , wherein the primary tokenization request comprises:
 sensitive data.   
     
     
         4 . The method of  claim 3 , further comprising:
 determining the one or more output token vaults using one or more output token service provider configuration identifiers.   
     
     
         5 . The method of  claim 3 , wherein each of the one or more ancillary tokenization requests comprises the sensitive data. 
     
     
         6 . The method of  claim 3 , wherein the primary tokenization request further comprises supplemental information. 
     
     
         7 . The method of  claim 6 , wherein the supplemental information comprises at least one of: a payment vehicle expiration date, an address, and a card security code. 
     
     
         8 . The method of  claim 6 , wherein each of the one or more ancillary tokenization requests comprises the sensitive data, and at least one of the one or more ancillary tokenization requests further comprises supplemental information. 
     
     
         9 . The method of  claim 8 , wherein each of the one or more output token vaults generates an output token that corresponds to the sensitive data, and at least one of the one or more output token vaults generates an output token that corresponds to the sensitive data and the supplemental information. 
     
     
         10 . The method of  claim 1 , wherein the upstream entity is an intermediary system that is not a merchant system. 
     
     
         11 . A system for cross-platform token compatibility, the system comprising:
 one or more processors; and   at least one data storage comprising instructions which, when executed by the one or more processors, cause the one or more processors to perform a method comprising:
 receiving, by a token exchange service system, a primary tokenization request from an upstream entity; 
 generating, by the token exchange service system, one or more ancillary tokenization requests based on the primary tokenization request; 
 transmitting, by the token exchange service system, the one or more ancillary tokenization requests to respective one or more output token vaults; 
 receiving, by the token exchange service system, one or more ancillary tokenization responses from the respective one or more output token vaults; 
 generating, by the token exchange service system, a primary tokenization response based on the one or more ancillary tokenization responses; and 
 transmitting, by the token exchange service system, the primary tokenization response to the upstream entity. 
   
     
     
         12 . The system of  claim 11 , wherein the primary tokenization request comprises:
 sensitive data.   
     
     
         13 . The system of  claim 12 , further comprising:
 determining the one or more output token vaults using one or more output token service provider configuration identifiers.   
     
     
         14 . The system of  claim 12 , wherein each of the one or more ancillary tokenization requests comprises the sensitive data. 
     
     
         15 . The system of  claim 12 , wherein the primary tokenization request further comprises supplemental information. 
     
     
         16 . The system of  claim 15 , wherein the supplemental information comprises at least one of: a payment vehicle expiration date, an address, and a card security code. 
     
     
         17 . The system of  claim 15 , wherein each of the one or more ancillary tokenization requests comprises the sensitive data, and at least one of the one or more ancillary tokenization requests further comprises supplemental information. 
     
     
         18 . The system of  claim 17 , wherein each of the one or more output token vaults generates an output token that corresponds to the sensitive data, and at least one of the one or more output token vaults generates an output token that corresponds to the sensitive data and the supplemental information. 
     
     
         19 . The system of  claim 11 , wherein the upstream entity is an intermediary system that is not a merchant system. 
     
     
         20 . A non-transitory computer-readable medium for cross-platform token compatibility, the non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform a method comprising:
 receiving, by a token exchange service system, a primary tokenization request from an upstream entity;   generating, by the token exchange service system, one or more ancillary tokenization requests based on the primary tokenization request;   transmitting, by the token exchange service system, the one or more ancillary tokenization requests to respective one or more output token vaults;   receiving, by the token exchange service system, one or more ancillary tokenization responses from the respective one or more output token vaults;   generating, by the token exchange service system, a primary tokenization response based on the one or more ancillary tokenization responses; and   transmitting, by the token exchange service system, the primary tokenization response to the upstream entity.