US 11,687,926 B2
Privacy protected consumers identity for centralized P2P network services
Raj Gandhi, Foster City, CA (US); Gyan Prakash, Foster City, CA (US); Yue Chen, Foster City, CA (US); and Ketki Gawande, Foster City, CA (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Filed by VISA INTERNATIONAL SERVICE ASSOCIATION, San Francisco, CA (US)
Filed on Jul. 12, 2019, as Appl. No. 16/510,175.
Prior Publication US 2021/0012329 A1, Jan. 14, 2021
Int. Cl. G06Q 20/38 (2012.01); G06Q 20/40 (2012.01); G06Q 20/22 (2012.01)
CPC G06Q 20/383 (2013.01) [G06Q 20/223 (2013.01); G06Q 20/4016 (2013.01)] 14 Claims
OG exemplary drawing
 
1. A method of communicating a payment request from a first payment platform to a second payment platform, the method comprising:
receiving, from the first payment platform at a service computing device, a protected payment request generated by a sending user via the first payment platform and intended for a receiving user associated with the second payment platform, wherein the protected payment request includes at least:
a payment amount,
a receiver ID, and
a hashed sender ID generated by translating a sender ID associated with the sending user using a hash function;
reviewing, by the service computing device, the protected payment request to confirm that the sending user is a known user of the first payment platform by comparing the hashed sender ID to stored known hashed user IDs that are associated with the first payment platform;
in response to confirming that the sending user is a known user of the first payment platform:
generating a hashed receiver ID by translating the receiver ID from the protected payment request using the hash function, and
identifying the second payment platform by searching a user database for the hashed receiver ID, the user database including matches of known users with a plurality of additional payment platforms including the second payment platform;
in response to identifying the second payment platform, generating, by the service computing device, a unique payment token including the hashed receiver ID and the payment amount of the protected payment request;
communicating, from the service computing device, the unique payment token to the first payment platform for delivery to a first computing device associated with the sending user, wherein the first computing device communicates the unique payment token to a second computing device associated with the receiving user and the second computing device redeems the token with the second payment platform;
receiving, at the service computing device from the second payment platform, a request for validation including the unique payment token and the hashed receiver ID;
validating the unique payment token at the service computing device by matching the hashed receiver ID to the receiver ID included in the protected payment request; and
communicating the validation from the service computing device to the second payment platform.