Methods and systems for secure cross-platform token exchange
Systems and methods are disclosed for cross-platform token exchange. One method comprises receiving a primary token exchange request from an upstream entity, generating an ancillary detokenization request based on the primary token exchange request, and transmitting the ancillary detokenization request to an input token vault. An ancillary detokenization response comprising sensitive data may then be received from the input token vault, and one or more ancillary tokenization requests may be generated based on the ancillary detokenization response and the primary token exchange request. The one or more ancillary tokenization requests may be transmitted to one or more output token vaults. Subsequently, one or more ancillary tokenization responses may be received from the one or more output token vaults, each ancillary tokenization response comprising an output token. A primary token exchange response may be generated based on the one or more ancillary tokenization responses and transmitted to the upstream entity.
1. A method for cross-platform token exchange, comprising:
receiving, by a token exchange service system, a signed primary token exchange request from an upstream entity;
verifying, by the token exchange service system, one or more values in a header of the signed primary token exchange request;
retrieving, by the token exchange service system, a shared key from a token exchange database associated with the upstream entity;
extracting, by the token exchange service system, a plurality of signature elements from the signed primary token exchange request using the shared key;
generating, by the token exchange service system, a plurality of hash values using the plurality of signature elements;
comparing, by the token exchange service system, the generated plurality of hash values to a plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a globally unique identifier (GUID) for the signed primary token exchange request based on the comparison of the generated plurality of hash values and the plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a primary token exchange response based on the primary token exchange request; and
transmitting, by the token exchange service system, the primary token exchange response to the upstream entity, wherein the primary token exchange response includes the GUID.
2. The method of claim 1 , wherein the signed primary token exchange request is an application programming interface (API) request.
3. The method of claim 1 , wherein the one or more values in the header of the primary token exchange request includes one or more of: a timestamp, a merchant reference, and a non-duplicate nonce value.
4. The method of claim 1 , wherein the shared key is associated with a merchant reference.
5. The method of claim 1 , further comprising, based on the comparison of the generated plurality of hash values and the plurality of hash values in the header of the signed primary token exchange request:
denying, by the token exchange service system, the signed primary token exchange request; and
transmitting, by the token exchange service system, an authentication failure message to the upstream entity.
6. The method of claim 1 , wherein the GUID includes one or more entries associated with one or more electronic transactions associated with the signed primary token exchange request.
7. The method of claim 6 , further comprising:
logging, by the token exchange service system, one or more electronic transaction events associated with the one or more electronic transactions in the database; and
transmitting, by the token exchange service system, the one or more electronic transaction events to the upstream entity.
8. The method of claim 3 , further comprising:
comparing, by the token exchange service system, the timestamp in the header of the signed primary token exchange request to a current time; and
based on the comparison, evaluating, by the token exchange service system, whether the timestamp in the header of the signed primary token exchange request and the current time are within a predetermined amount of time.
9. The method of claim 8 , further comprising:
receiving, by the token exchange service system, a usage table; and
comparing, by the token exchange service system, the nonce value against the usage table.
10. The method of claim 6 , wherein each of the one or more electronic transactions includes sensitive data.
11. A system for cross-platform token exchange, the system comprising:
one or more processors; and
a data storage storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving, by a token exchange service system, a signed primary token exchange request from an upstream entity;
verifying, by the token exchange service system, one or more values in a header of the signed primary token exchange request;
retrieving, by the token exchange service system, a shared key from a token exchange database associated with the upstream entity;
extracting, by the token exchange service system, a plurality of signature elements from the signed primary token exchange request using the shared key;
generating, by the token exchange service system, a plurality of hash values using the plurality of signature elements;
comparing, by the token exchange service system, the generated plurality of hash values to a plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a globally unique identifier (GUID) for the signed primary token exchange request based on the comparison of the generated plurality of hash values and the plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a primary token exchange response based on the primary token exchange request; and
transmitting, by the token exchange service system, the primary token exchange response to the upstream entity, wherein the primary token exchange response includes the GUID.
12. The system of claim 11 , wherein the signed primary token exchange request is an application programming interface (API) request.
13. The system of claim 11 , wherein the one or more values in the header of the primary token exchange request includes one or more of: a timestamp, a merchant reference, and a non-duplicate nonce value.
14. The system of claim 11 , wherein the shared key is associated with a merchant reference.
15. The system of claim 11 , the operations further comprising, based on the comparison of the generated plurality of hash values and the plurality of hash values in the header of the signed primary token exchange request:
denying, by the token exchange service system, the signed primary token exchange request; and
transmitting, by the token exchange service system, an authentication failure message to the upstream entity.
16. The system of claim 11 , wherein the GUID includes one or more entries associated with one or more electronic transactions associated with the signed primary token exchange request.
17. The system of claim 16 , the operations further comprising:
logging, by the token exchange service system, one or more electronic transaction events associated with the one or more electronic transactions in the database; and
transmitting, by the token exchange service system, the one or more electronic transaction events to the upstream entity.
18. The system of claim 13 , the operations further comprising:
comparing, by the token exchange service system, the timestamp in the header of the signed primary token exchange request to a current time; and
based on the comparison, evaluating, by the token exchange service system, whether the timestamp in the header of the signed primary token exchange request and the current time are within a predetermined amount of time.
19. The system of claim 18 , the operations further comprising:
receiving, by the token exchange service system, a usage table; and
comparing, by the token exchange service system, the nonce value against the usage table.
20. A non-transitory computer readable medium for cross-platform token exchange, the non-transitory computer readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
receiving, by a token exchange service system, a signed primary token exchange request from an upstream entity;
verifying, by the token exchange service system, one or more values in a header of the signed primary token exchange request;
retrieving, by the token exchange service system, a shared key from a token exchange database associated with the upstream entity;
extracting, by the token exchange service system, a plurality of signature elements from the signed primary token exchange request using the shared key;
generating, by the token exchange service system, a plurality of hash values using the plurality of signature elements;
comparing, by the token exchange service system, the generated plurality of hash values to a plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a globally unique identifier (GUID) for the signed primary token exchange request based on the comparison of the generated plurality of hash values and the plurality of hash values in the header of the signed primary token exchange request;
generating, by the token exchange service system, a primary token exchange response based on the primary token exchange request; and
transmitting, by the token exchange service system, the primary token exchange response to the upstream entity, wherein the primary token exchange response includes the GUID.