US 12,217,252 B2
Hybrid identity as a service for decentralized browser based wallets
Jitendra Singh Dikhit, Bangalore (IN); Alaric M. Eby, Phoenix, AZ (US); Andras L. Ferenczi, Scottsdale, AZ (US); Ashish Kumar, Gunjurpalya Bangalore (IN); and Upendra Mardikar, Fremont, CA (US)
Assigned to AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC., New York, NY (US)
Filed by American Express Travel Related Services Company, Inc., New York, NY (US)
Filed on Dec. 6, 2023, as Appl. No. 18/530,519.
Application 18/530,519 is a continuation of application No. 16/239,017, filed on Jan. 3, 2019, granted, now 11,887,112.
Prior Publication US 2024/0104563 A1, Mar. 28, 2024
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 20/38 (2012.01); G06Q 20/40 (2012.01)
CPC G06Q 20/3829 (2013.01) [G06Q 20/3827 (2013.01); G06Q 20/4014 (2013.01); G06Q 2220/00 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method, comprising:
hashing, by a security provider, account creation information associated with a stored password hash to create hashed account creation information;
decrypting an encrypted first passcode stored in association with the account creation information to generate a first passcode, wherein a cryptowallet on a user device uses the first passcode to perform cryptographic processes on one or more keys stored by the cryptowallet on the user device, wherein an encrypted private key is at least one of the one or more keys;
generating, by the security provider, a second passcode in response to decrypting the encrypted first passcode, wherein the first passcode is different from the second passcode, wherein the cryptowallet on the user device uses the second passcode to perform cryptographic processes on the one or more keys stored by the cryptowallet on the user device;
encrypting, by the security provider, the second passcode using the hashed account creation information as an encryption key to create an encrypted passcode;
returning, by the security provider, the first passcode and the second passcode to the cryptowallet on the user device;
decrypting, by the user device via the cryptowallet, the encrypted private key using the returned first passcode to generate a decrypted private key;
signing, by the user device via the cryptowallet, a transaction request with the decrypted private key; and
in response to signing the transaction request, re-encrypting, by the user device via the cryptowallet, the decrypted private key using the returned second passcode.