Systems and methods for linking high-value tokens using a low-value token
Embodiments include methods and systems for linking high-value tokens using a low-value token, comprising receiving, from an electronic data server, a first high-value token and a request for a low-value token, the first high-value token being associated with sensitive data associated with a user, and the low-value token being associated with a subset of the sensitive data associated with the user. The methods and systems further comprise providing the low-value token to the electronic data server, and receiving, from a second electronic data server, the low-value token and a request for a second high-value token, the low-value token having been provided to the second electronic data server by the electronic data server. The methods and systems further comprise generating a second high-value token associated with the sensitive data associated with the user, and providing the second high-value token to the second electronic data server.
1. A method for performing secure electronic transactions utilizing tokens, the method comprising:
receiving, by a transaction processor server from a merchant system, a request for a low-value token, the request comprising a high-value token, wherein the high-value token is associated with sensitive data and the low-value token is associated with a subset of sensitive data of the sensitive data associated with the high-value token;
providing, by the transaction processor server, the low-value token to the merchant system;
receiving, by the transaction processor server, the low-value token from a third-party service, wherein the third-party service is prohibited from providing sensitive data to the merchant;
validating, by the transaction processor server, the third-party service based on one or more attributes of the low-value token;
in response to validating the third-party service, de-tokenizing, by the transaction processor server, the low-value token to obtain the subset of sensitive data;
providing, by the transaction processor server, the subset of sensitive data associated with the low-value token to the third-party service;
receiving, by the transaction processor server, the low-value token, a request to authorize a transaction, and third-party service data from the merchant system; and
providing, by the transaction processor server, the high-value token and an authorization response to the merchant system.
2. The method of claim 1 , wherein the high-value token specifies the sensitive data to which the low-value token will correspond.
3. The method of claim 1 , wherein the receiving the low-value token from the third-party service comprises receiving the low-value token from the third-party service based on the merchant system providing the low-value token to the third-party service.
4. The method of claim 1 , wherein the third-party service data is generated by the third-party service based on the sensitive data, and is provided to the merchant system from the third-party service.
5. The method of claim 1 , further comprising:
receiving, by the transaction processor server, a fraud check score obtained by the third-party service using the sensitive data.
6. The method of claim 1 , wherein the third-party service data is 3-D Secure Data.
7. A transaction processor server for performing secure electronic transactions utilizing tokens, the transaction processor server comprising:
a data storage device storing instructions; and
one or more processors configured to execute the instructions to perform a method comprising:
receiving a request for a low-value token from a merchant system, the request comprising a high-value token, wherein the high-value token is associated with sensitive data and the low-value token is associated with a subset sensitive data of the sensitive data associated with the high-value token;
providing the low-value token to the merchant system;
receiving the low-value token from a third-party service, wherein the third-party service and the merchant system are prohibited from direct communication;
validating, the third-party service based on one or more attributes of the low-value token;
in response to validating the third-party service, de-tokenizing, the low-value token to obtain the subset of sensitive data;
providing the subset of sensitive data associated with the low-value token to the third-party service;
receiving the low-value token, a request to authorize a transaction, and third-party service data from the merchant system; and
providing the high-value token and an authorization response to the merchant system.
8. The transaction processor server of claim 7 , wherein the high-value token specifies the sensitive data to which the low-value token will correspond.
9. The transaction processor server of claim 7 , wherein the receiving the low-value token from the third-party service comprises receiving the low-value token from the third-party service based on the merchant system providing the low-value token to the third-party service.
10. The transaction processor server of claim 7 , wherein the third-party service data is generated by the third-party service based on the sensitive data, and is provided to the merchant system from the third-party service.
11. The transaction processor server of claim 7 , wherein the method further comprises:
receiving, by the transaction processor server, a fraud check score obtained by the third-party service using the sensitive data.
12. The transaction processor server of claim 7 , wherein the third-party service data is 3-D Secure Data.
13. A non-transitory computer-readable medium storing instructions that, when executed by a transaction processor server, cause the transaction processor server to perform a method for performing secure electronic transactions utilizing tokens, the method comprising:
receiving a request for a low-value token from a merchant system, the request comprising a high-value token, wherein the high-value token is associated with sensitive data and the low-value token is associated with a subset sensitive data of the sensitive data associated with the high-value token;
providing the low-value token to the merchant system;
receiving the low-value token from a third-party service, wherein the third-party service and the merchant system are prohibited from direct communication;
validating, the third-party service based on one or more attributes of the low-value token;
in response to validating the third-party service, de-tokenizing, the low-value token to obtain the subset of sensitive data;
providing the subset of sensitive data associated with the low-value token to the third-party service;
receiving the low-value token, a request to authorize a transaction, and third-party party service data from the merchant system; and
providing the high-value token and an authorization response to the merchant system.
14. The non-transitory computer-readable medium of claim 13 , wherein the high-value token specifies the sensitive data to which the low-value token will correspond.
15. The non-transitory computer-readable medium of claim 13 , wherein the receiving the low-value token from the third-party service comprises receiving the low-value token from the third-party service based on the merchant system providing the low-value token to the third-party service.
16. The non-transitory computer-readable medium of claim 13 , wherein the third-party service data is generated by the third-party service based on the sensitive data, and is provided to the merchant system from the third-party service.
17. The non-transitory computer-readable medium of claim 13 , wherein the method further comprises:
receiving, by the transaction processor server, a fraud check score obtained by the third-party service using the sensitive data.