Masking a primary account number between a party and a service provider

12020,244

17/861709

July 11, 2022

A computer implemented method for masking a primary account number between a party and a service provider. A plurality of transaction records from a database is retrieved. A masking value is generated in response to having a first hash function executed on a primary account number. The receiving, at the service provider, the masking value from the client execution environment without the primary account number; wherein the server execution environment lacks identification of the affiliation between the primary account number and the party. Upon confirming that the first hash function is identical to the second hash function, matching the masking value to the second masking value. In response to a match, querying the database for transaction history associated with the masking value. An analysis report is generated.

VISA INTERNATIONAL SERVICE ASSOCIATION (San Francisco, CA, US)

Visa International Service Association (San Francisco, CA, US)

1. A computer implemented method for masking a primary account number between a party and a service provider comprising: retrieving, at the service provider, a plurality of transaction records from a database connected to a server execution environment of the service provider via an application programming interface (API), wherein each of the plurality of transaction records comprises a second masking value generated by a second hash function executed in the server execution environment; generating, at the service provider, a fillable document comprising a hash plugin of a first hash function, wherein the first hash function is updated to be the same as the second hash function; transmitting, at the service provider, the fillable document comprising the hash plugin of the first hash function to a client execution environment of the party; receiving, at the service provider, the fillable document comprising a first masking value from the client execution environment of the party, wherein the client execution environment generates the first masking value for a primary account number in response to executing the first hash function; querying, by the service provider, the database for transaction history associated with the first masking value, based on a comparison that the first masking value and the second masking value match; and transmitting, via the server execution environment of the service provider, each of the plurality of transaction records comprising the second masking value that matches the first masking value based on the query of the database.

2. The computer implemented method of claim 1 , wherein the first masking value comprises a set of 64-digit alphanumeric values.

3. The computer implemented method of claim 1 , wherein the analysis report is requested via a user interface that is in communication with the client execution environment.

4. The computer implemented method of claim 1 , wherein the fillable document is generated in response to input received from a user interface.

5. The computer implemented method of claim 1 , wherein the transaction history is a subset of the plurality of transaction records.

6. The computer implemented method of claim 1 , further comprising: in response to a determination that the first masking value and the second masking value do not match, communicating an alarm.

7. The computer implemented method of claim 1 , wherein the party and the service provider are different entities.

8. The computer implemented method of claim 1 , wherein the service provider is a payment processing service provider.

9. The computer implemented method of claim 1 , wherein the API delivers the transaction history associated with the first masking value.

10. A system for masking a primary account number between a party and a service provider comprising: a database connected to a server execution environment; and a processor of the server execution environment that is in communication with the database, the processor being physically configured according to computer executable instructions to: retrieve a plurality of transaction records from the database via an application programming interface (API), wherein each of the plurality of transaction records comprises a second masking value generated by a second hash function executed in the server execution environment; generate a fillable document comprising a hash plugin of a first hash function, wherein the first hash function is updated to be the same as the second hash function; transmit the fillable document comprising the hash plugin of the first hash function to a client execution environment of the party; receive the fillable document comprising a first masking value from the client execution environment of the party, wherein the client execution environment generates the first masking value for a primary account number in response to executing the first hash function; query the database for transaction history associated with the first masking value, based on a comparison that the first masking value and the second masking value match; and transmit each of the plurality of transaction records comprising the second masking value that matches the first masking value based on the query of the database.

6853987 February 2005 Cook
7677450 March 2010 Rajewski
8688524 April 2014 Ramalingam
8935797 January 2015 Silver
11429961 August 2022 Setia
20050240531 October 2005 Wolff
20120284175 November 2012 Wilson
20130246279 September 2013 Everett
20170364552 December 2017 Pattanaik
20180109508 April 2018 Wall
20200065814 February 2020 Fang
20200349559 November 2020 Setia
20220343321 October 2022 Setia
2018056992 March 2018
2019194962 October 2019

Office Action (Ex Parte Quayle Action) dated Mar. 21, 2022 for U.S. Appl. No. 16/401,434 (pp. 1-7). cited by applicant
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated May 4, 2022 for U.S. Appl. No. 16/401,434 (pp. 1-5). cited by applicant
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated May 19, 2022 for U.S. Appl. No. 16/401,434 (pp. 1-4). cited by applicant
Office Action dated Feb. 26, 2021 for U.S. Appl. No. 16/401,434 (pp. 1-9). cited by applicant
Office Action dated Jul. 15, 2021 for U.S. Appl. No. 16/401,434 (pp. 1-10). cited by applicant

edspgr.12020244