Methods and systems for enhanced endpoint identity validation in electronic transactions
Methods and systems are disclosed for merchant system identity validation. One method comprises generating, by an access management system, a primary key associated with an integrator system and transmitting the primary key to the integrator system. The access management system may also generate a hash value associated with a merchant system, and may transmit the hash value to the merchant system. When a payment transaction is initiated at the merchant system, the access management system may receive an authorization request comprising a key-hash pair. The key-hash pair may be validated against a validation database. Upon successful validation, the access management system may transmit the authorization request to an acquirer processor.
1. A method for merchant system identity validation, comprising:
transmitting, by an access management system, a primary key to the merchant system;
generating, by the access management system, a hash value associated with the merchant system;
transmitting, by the access management system, the hash value to the merchant system;
receiving, by the access management system, an authorization request comprising a key-hash pair;
determining, by the access management system, whether the key-hash pair matches a reference key-hash pair stored in a validation database; and
transmitting, by the access management system, the authorization request to an acquirer processor based on validating the key-hash pair.
2. The method of claim 1 , further comprising:
upon determining that the key-hash pair does not match the reference key-hash pair, flagging the authorization request.
3. The method of claim 2 , wherein flagging the authorization request prevents data associated with the authorization request from being transmitted to a downstream entity.
4. The method of claim 1 , wherein the hash value is generated in response to a request for a hash value from the merchant system.
5. The method of claim 1 , wherein the validation database comprises primary keys and hash values that are previously-generated by the access management system.
6. The method of claim 1 , wherein the key-hash pair comprises the primary key and the hash value transmitted to the merchant system.
7. The method of claim 1 , further comprising:
generating, by the access management system, the hash value associated with the merchant system.
8. A system for merchant system identity validation, the system comprising:
one or more processors;
at least one data storage comprising instructions which, when executed by the one or more processors, cause the one or more processors of an access management system to perform operations comprising:
transmitting, by an access management system, a primary key to the merchant system;
generating, by the access management system, a hash value associated with the merchant system;
transmitting, by the access management system, the hash value to the merchant system;
receiving, by the access management system, an authorization request comprising a key-hash pair;
determining, by the access management system, whether the key-hash pair matches a reference key-hash pair stored in a validation database; and
transmitting, by the access management system, the authorization request to an acquirer processor based on validating the key-hash pair.
9. The system of claim 8 , wherein the operations further comprise:
upon determining that the key-hash pair does not match the reference key-hash pair, flagging the authorization request.
10. The system of claim 9 , wherein flagging the authorization request prevents data associated with the authorization request from being transmitted to a downstream entity.
11. The system of claim 8 , wherein the hash value is generated in response to a request for a hash value from the merchant system.
12. The system of claim 8 , wherein the validation database comprises primary keys and hash values that are previously-generated by the access management system.
13. The system of claim 8 , wherein the key-hash pair comprises the primary key and the hash value transmitted to the merchant system.
14. A non-transitory computer readable medium for merchant system identity validation, the non-transitory computer readable medium storing instructions which, when executed by one or more processors of an access management system, cause the one or more processors to perform operations comprising:
transmitting, by an access management system, a primary key to the merchant system;
generating, by the access management system, a hash value associated with the merchant system;
transmitting, by the access management system, the hash value to the merchant system;
receiving, by the access management system, an authorization request comprising a key-hash pair;
determining, by the access management system, whether the key-hash pair matches a reference key-hash pair stored in a validation database; and
transmitting, by the access management system, the authorization request to an acquirer processor based on validating the key-hash pair.
15. The non-transitory computer readable medium of claim 14 , wherein the operations further comprise:
upon determining that the key-hash pair does not match the reference key-hash pair, flagging the authorization request.
16. The non-transitory computer readable medium of claim 15 , wherein flagging the authorization request prevents data associated with the authorization request from being transmitted to a downstream entity.
17. The non-transitory computer readable medium of claim 14 , wherein the hash value is generated in response to a request for a hash value from the merchant system.
18. The non-transitory computer readable medium of claim 14 , wherein the validation database comprises primary keys and hash values that are previously-generated by the access management system.
19. The non-transitory computer readable medium of claim 14 , wherein the key-hash pair comprises the primary key and the hash value transmitted to the merchant system.
20. The non-transitory computer readable medium of claim 14 , wherein the operations further comprise:
generating, by the access management system, the hash value associated with the merchant system.