Systems and methods for authentication of physical access tokens at access terminals
View Patent ↗In certain embodiments, a physical network access token at a network access terminal may be authenticated for modification of records at a remote server system. In some embodiments, a set of records and counterpart records having the same record identifiers and resource amounts may be stored independently on a physical token or user device and the remote server system. When a connection is established between an access terminal and the physical token (e.g., for authenticating a modification of record(s)), the access terminal may transmit input data to the token, which may use the input data with the records stored on the token to generate authentication data, which may be used by the remote server to authenticate a network action requested via the token.
1 . An access terminal for facilitating authentication of a physical access token for modification of records at a remote server system, the access terminal comprising:
one or more processors and non-transitory, computer-readable media comprising instructions that, when executed by the one or more processors, cause operations comprising:
establishing a connection with the physical access token associated with a user, wherein the physical access token stores a set of records including a first record comprising (a) a record identifier identifying the first record of the user and (b) a resource amount associated with the first record of the user, and wherein the record identifier and resource amount are a same record identifier and resource amount of a first counterpart record of a set of counterpart records stored at a remote server system;
responsive to establishing connection with the physical access token, transmitting input data comprising a random seed value and a requested resource amount to the physical access token;
receiving, from the physical access token, authentication data generated based on (i) the random seed value, (ii) the requested resource amount, and (iii) the set of records stored at the physical access token;
transmitting, to the remote server system, a verification request for verifying the physical access token, wherein the verification request comprises the authentication data, the requested resource amount, and the random seed value, and wherein, in connection with the verification request, the remote server system performs verification using a hash-based value derived from hashing a combination of inputs including data from a first counterpart record of the set of counterpart records stored at the remote server system; and
in response to the verification indicating a match between the authentication data and the hash-based value derived from hashing of the combination of inputs, receiving an indication of authorization and causing presentation of an authorization related to the requested resource amount.
2 . The access terminal of claim 1 , wherein, in connection to the verification, the remote server system is configured to update the set of counterpart records to reflect a transfer corresponding to the requested resource amount by generating a new counterpart record that (i) is a modified instance of the first counterpart record and (ii) comprises a resource amount and a record identifier different from the record identifier of the first counterpart record.
3 . The access terminal of claim 1 , wherein, in connection to the verification, the remote server system is configured to modify the set of counterpart records to reflect (i) a first transfer of at least some of the resource amount of the first counterpart record to a second counterpart record or (ii) a second transfer of at least some of the resource amount of the second counterpart record to one or more records associated with one or more users by modifying record identifiers and resource amounts of each.
4 . The access terminal of claim 1 , wherein performing verification by the remote server system comprises:
hashing the first counterpart record of the set of counterpart records to a hash value;
generating a reference value based on the authentication data and a public key associated with the user; and
comparing the hash value and the reference value.
5 . A method for facilitating authentication of a physical access token for modification of records at a remote server system, the method comprising:
establishing a connection with the physical access token, wherein the physical access token stores a set of records including a first record of a user comprising (a) a record identifier identifying the first record and (b) a resource amount for transfer between the first record and a second record, and wherein the record identifier and resource amount are a same record identifier and resource amount of a first counterpart record of a set of counterpart records stored at a remote server system;
responsive to transmitting input data comprising a random seed value and a requested resource amount, receiving, from the physical access token, authentication data generated based on (i) the random seed value, (ii) the requested resource amount, and (iii) the set of records stored at the physical access token;
transmitting, to the remote server system, a verification request for verifying the physical access token, wherein the verification request comprises the authentication data, the requested resource amount, and the random seed value, and wherein, in connection with the verification request, the remote server system performs verification using a hash-based value derived from hashing a combination of inputs including data from the first counterpart record of the set of counterpart records stored at the remote server system; and
in response to the verification indicating a match between the authentication data and the hash-based value derived from hashing of the combination of inputs, receiving an indication of authorization and causing presentation of an authorization related to the requested resource amount.
6 . The method of claim 5 , wherein, in connection to the verification, the remote server system is configured to update the set of counterpart records to reflect a transfer corresponding to the requested resource amount by generating a new counterpart record that (i) is a modified instance of the first counterpart record and (ii) comprises a resource amount and a record identifier different from the record identifier of the first counterpart record.
7 . The method of claim 5 , wherein, in connection to transmitting input data comprising the requested resource amount, the physical access token is configured to update the set of records to reflect a transfer corresponding to the requested resource amount by generating a new record that (i) is a modified instance of the first record and (ii) comprises a resource amount and a record identifier different from the record identifier of the first record.
8 . The method of claim 7 , wherein the record identifier of the new record is based on an output generated by inputting a combination of (i) a secret key stored at the remote server system and the physical access token, (ii) a time associated with an establishment of connection to the physical access token, or (iii) the record identifier of the first record into a hash-based message authentication code (HMAC) algorithm.
9 . The method of claim 5 , wherein, in connection to the verification, the remote server system is configured to modify the set of counterpart records to reflect (i) a first transfer of at least some of the resource amount of the first counterpart record to a second counterpart record or (ii) a second transfer of at least some of the resource amount of the second counterpart record to one or more records associated with one or more users by modifying record identifiers and resource amounts of each.
10 . The method of claim 5 , wherein, in connection to transmitting input data comprising the requested resource amount, the physical access token is configured to modify the set of records to reflect (i) a first transfer of at least some of the resource amount of the first record to the second record, or (ii) a second transfer of at least some of the resource amount of the second record to one or more records associated with one or more users by modifying record identifiers and resource amounts of each.
11 . The method of claim 5 , wherein performing verification by the remote server system comprises:
hashing the first counterpart record of the set of counterpart records to a hash value;
generating a reference value based on the authentication data and a public key associated with the user; and
comparing the hash value and the reference value.
12 . The method of claim 5 , wherein the authentication data is configured to be generated by:
hashing a combination of record identifiers of one or more records of the set of records stored at the physical access token, the random seed value, or the requested resource amount to obtain a hash value; and
encrypting the hash value using a private key associated with the user.
13 . One or more non-transitory, computer-readable media comprising instructions recorded thereon that, when executed by one or more processors, cause operations for facilitating authentication of a physical access token for modification of records at a remote server system, comprising:
establishing a connection with the physical access token, wherein the physical access token stores a set of records including a first record of a user comprising (a) a record identifier identifying the first record and (b) a resource amount for transfer between the first record and a second record, and wherein the record identifier and resource amount are a same record identifier and resource amount of a first counterpart record of a set of counterpart records stored at a remote server system;
responsive to transmitting input data comprising a random seed value and a requested resource amount, receiving, from the physical access token, authentication data generated based on (i) the random seed value, (ii) the requested resource amount, and (iii) the set of records stored at the physical access token;
transmitting, to the remote server system, a verification request for verifying the physical access token, wherein the verification request comprises the authentication data, the requested resource amount, and the random seed value, and wherein, in connection with the verification request, the remote server system performs verification using a hash-based value derived from hashing a combination of inputs including data from the first counterpart record of the set of counterpart records stored at the remote server system; and
in response to the verification indicating a match between the authentication data and the hash-based value derived from hashing of the combination of inputs, receiving an indication of authorization and causing presentation of an authorization related to the requested resource amount.
14 . The one or more non-transitory, computer-readable media of claim 13 , wherein, in connection to the verification, the remote server system is configured to update the set of counterpart records to reflect a transfer corresponding to the requested resource amount by generating a new counterpart record that (i) is a modified instance of the first counterpart record and (ii) comprises a resource amount and a record identifier different from the record identifier of the first counterpart record.
15 . The one or more non-transitory, computer-readable media of claim 13 , wherein, in connection to transmitting input data comprising the requested resource amount, the physical access token is configured to update the set of records to reflect a transfer corresponding to the requested resource amount by generating a new record that (i) is a modified instance of the first record and (ii) comprises a resource amount and a record identifier different from the record identifier of the first record.
16 . The one or more non-transitory, computer-readable media of claim 15 , wherein the record identifier of the new record is based on an output generated by inputting a combination of (i) a secret key stored at the remote server system and the physical access token, (ii) a time associated with an establishment of connection to the physical access token, or (iii) the record identifier of the first record into a hash-based message authentication code (HMAC) algorithm.
17 . The one or more non-transitory, computer-readable media of claim 13 , wherein, in connection to the verification, the remote server system is configured to modify the set of counterpart records to reflect (i) a first transfer of at least some of the resource amount of the first counterpart record to a second counterpart record or (ii) a second transfer of at least some of the resource amount of the second counterpart record to one or more records associated with one or more users by modifying record identifiers and resource amounts of each.
18 . The one or more non-transitory, computer-readable media of claim 13 , wherein, in connection to transmitting input data comprising the requested resource amount, the physical access token is configured to modify the set of records to reflect (i) a first transfer of at least some of the resource amount of the first record to the second record or (ii) a second transfer of at least some of the resource amount of the second record to one or more records associated with one or more users by modifying record identifiers and resource amounts of each.
19 . The one or more non-transitory, computer-readable media of claim 13 , wherein performing verification by the remote server system comprises:
hashing the first counterpart record of the set of counterpart records to a hash value;
generating a reference value based on the authentication data and a public key associated with the user; and
comparing the hash value and the reference value.
20 . The one or more non-transitory, computer-readable media of claim 13 , wherein the authentication data is configured to be generated by hashing a combination of record identifiers of one or more records of the set of records stored at the physical access token, the random seed value, or the resource amount to obtain a hash value and encrypting the hash value using a private key associated with the user.