Source independent consistent tokenization

Abstract

A gateway encryption service is used to ensure consistent, source independent tokenization for payment accounts and synchronizing payment account information with merchants. A consistent, evergreen merchant-facing token is generated and used for each payment account for the merchant, ensuring that regardless of the payment method used by the customer (e.g., plastic card point-of-sale, pay wallet, saved card information) for the same underlying account, the merchant has a single token. Further, if the account number for the underlying payment account changes (e.g., the card expires or is stolen) the merchant-facing token remains consistent. The evergreen token ensures that the system functions more efficiently, saving resources in processing and storage and ensuring less network traffic for failed transactions. The system further implements encryption and security despite the consistent tokenization, further saving resources.

What is claimed is: 
     
         1 . A system for source independent consistent tokenization, the system comprising:
 one or more processors; and   one or more memories having computer-readable instructions stored thereon that, upon execution by the one or more processors, cause the one or more processors to:   receive, from a merchant server, an authorization request for a transaction, the authorization request comprising a token representing an account of the customer, wherein the token is not a merchant-facing token or a primary account number of the customer;   detokenize the token;   identify the merchant-facing token based on the detokenized token;   request an authorization for the transaction from an issuing host platform based on the token;   receive, from the issuing host platform, the authorization for the transaction; and   transmit, to the merchant server, an indication of the authorization for the transaction comprising the merchant-facing token.   
     
     
         2 . The system of  claim 1 , wherein the token represents a pay wallet token for the account of the customer. 
     
     
         3 . The system of  claim 1 , wherein the primary account number received from the merchant server is encrypted. 
     
     
         4 . The system of  claim 1 , wherein the computer-readable instructions to identify the merchant-facing token based on the detokenized token further cause the one or more processors to search a mapping database for the merchant-facing token based on the token. 
     
     
         5 . The system of  claim 1 , wherein the computer-readable instructions to identify the merchant-facing token based on the detokenized token further cause the one or more processors to:
 obtain the primary account number based on the detokenized token; and   search a mapping database for the merchant-facing token based on the primary account number.   
     
     
         6 . The system of  claim 1 , wherein the computer-readable instructions further cause the one or more processors to:
 receive, from the merchant server, a second authorization request for a second transaction, the second authorization request comprising the primary account number for the account of a customer; and   generate the merchant token.   
     
     
         7 . The system of  claim 6 , wherein the computer-readable instructions further cause the one or more processors to:
 request a second authorization for the second transaction from the issuing host platform based on the primary account number;   receive, from the issuing host platform, a second authorization for the second transaction; and   transmit, to the merchant server, an indication of the second authorization for the second transaction comprising the token.   
     
     
         8 . The system of  claim 7 , wherein the computer-readable instructions further cause the one or more processors to:
 receive, from the merchant server, a third authorization request for a third transaction, the third authorization request comprising the merchant-facing token;   request a third authorization for the third transaction from an issuing host platform based on the merchant-facing token;   receive, from the issuing host platform, the third authorization for the third transaction; and   transmit, to the merchant server, an indication of the third authorization for the third transaction comprising the merchant-facing token.   
     
     
         9 . A system for synchronizing payment account information with merchants, the system comprising:
 one or more processors; and
 one or more memories having computer-readable instructions stored thereon that, upon execution by the one or more processors, cause the one or more processors to:
 receive a request to facilitate saving a payment account to a first merchant, the request comprising merchant provision data for the first merchant; 
 obtain a merchant token associated with the first merchant and the payment account based on the merchant provision data and a primary account number for the payment account; and 
 transmit the merchant token to a merchant server of the first merchant. 
 
   
     
     
         10 . The system of  claim 9 , wherein the computer-readable instructions further cause the one or more processors to:
 receive confirmation that the first merchant successfully saved the merchant token; and   transmit a success indication to an issuer server, wherein the issuer server is associated with the payment account.   
     
     
         11 . The system of  claim 10 , wherein the computer-readable instructions further cause the one or more processors to:
 receive, from the merchant server, an authorization request comprising the merchant token; and   detokenize the token to identify the merchant token.   
     
     
         12 . The system of  claim 11 , wherein detokenizing the token to identify the merchant token comprises obtaining the primary account number based on the detokenized token; and
 search a mapping database for the merchant-facing token based on the primary account number.   
     
     
         13 . The system of  claim 9 , wherein the computer-readable instructions further cause the one or more processors to:
 receive, from an issuer server, a primary account number for a payment account of a user and a list comprising:
 a plurality of merchant names, wherein each merchant name corresponds to a respective one of the plurality of merchants, and 
 an access link for each of the plurality of merchants; 
   obtain a token status for each merchant in the list, where each token status is associated with the primary account number and the associated merchant;   provide the token status for each merchant in the list to the issuer server;   
     
     
         14 . The system of  claim 9 , wherein the computer-readable instructions to obtain a merchant token associated with the first merchant and the payment account further cause the one or more processors to:
 transmit a provision request to a token service provider, the provision request comprising at least a portion of the merchant provision data;   receive, in response to the provision request, an issuer token associated with the merchant token from the token service provider, wherein the merchant token is different from the issuer token; and   save the merchant token, the issuer token, and a mapping that associates the merchant token and the issuer token in a secure data store.   
     
     
         15 . The system of  claim 9 , wherein the computer-readable instructions to obtain a merchant token associated with the first merchant and the payment account further cause the one or more processors to save the merchant token, the primary account number, and a mapping that associates the merchant token and the primary account number in a secure data store. 
     
     
         16 . The system of  claim 15 , wherein the computer-readable instructions further cause the one or more processors to:
 receive a second request to facilitate deleting the payment account from the first merchant; and   responsive to the second request, deleting at least one of the merchant token and the mapping that associates the merchant token and the primary account number from the secure data store.   
     
     
         17 . The system of  claim 9 , wherein the request to facilitate saving the payment account to the first merchant comprises an indication that the payment account is a default payment account at the first merchant for the user and wherein the instructions to transmit the merchant token to the merchant server of the first merchant comprises further instructions that, upon execution by the one or more processors, cause the one or more processors to transmit an indication to save the merchant token as the default payment account for the user. 
     
     
         18 . The system of  claim 11 , wherein obtaining the merchant token comprises generating the token. 
     
     
         19 . A system for synchronizing payment account information at a merchant, the system comprising:
 one or more processors; and   one or more memories having computer-readable instructions stored thereon that, upon execution by the one or more processors, cause the one or more processors to:
 receive, from a merchant server of a merchant, a save request to facilitate saving a payment account of a user at the merchant server; 
 transmit for display via a merchant user interface of the merchant and responsive to receiving the save request, a form comprising a data entry field for the user to enter a primary account number of the payment account; 
 receive the primary account number received from the user via the form; 
 generate a merchant-facing token associated with the merchant and the payment account; and 
 transmit the merchant-facing token to the merchant server; 
 receive an authorization request comprising a second token; and 
 detokenize the second token to identify the merchant token. 
   
     
     
         20 . The system of  claim 19 , wherein the computer-readable instructions further cause the one or more processors to:
 transmit a provision request to a token service provider, the provision request comprising the primary account number and an indication of the merchant; and   receive, in response to the provision request, the second token associated with the primary account number and the merchant.