IP Library Granted Patent US 12,244,589
Granted Patent B2
US 12,244,589 · App. 17/473,630 · Granted Mar 4, 2025

Systems and methods for managing digital identities associated with mobile devices

Inventors: Sumeet Bhatt (Jericho, NY); Ashfaq Kamal (Stamford, CT)
Assignee: MASTERCARD INTERNATIONAL INCORPORATED
H04L63/0861G06Q50/265H04L9/0825H04L63/0442H04L63/0853H04L63/0884H04W12/06G06Q20/34G06Q20/4014G06Q20/40145H04L63/0815H04W12/65
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,244,589
App. No.
17/473,630
Granted
Mar 4, 2025
Kind
B2
Abstract

Systems and methods are provided for enabling, providing, and managing digital identities in association with mobile devices. One example method includes determining, by a mobile device, that identity data of a user is changed, and prompting the user to identify a third party separate from the mobile device to authenticate the user. The method also includes requesting the third party to authenticate the user, and causing an authentication interface of the third party to be displayed at the mobile device where the authentication interface solicits login credentials for an account of the user at the third party. The method then includes granting, by the mobile device, access to one or more aspects of a mobile application installed at the mobile device, in response to an indication of a successful authentication of the user from the third party.

Claims (55)

1. A computer-implemented method for use in managing access to digital identities associated with mobile devices, the method comprising:

upon launching a mobile application installed at a mobile device, determining, by the mobile device, that identity data of a user stored in the mobile device is changed, relative to input data from the user since a prior login to the mobile application at the mobile device, the identity data including a government identification number, a mailing address, and at least one of an email address and/or a phone number of the user; and then,

in response to determining that the identity data is changed:

presenting, by the mobile device, at a presentation unit of the mobile device, the user with multiple third parties, separate from the mobile device, to authenticate the user, wherein the user is associated with an account at each of the third parties and login credentials for the accounts;

prompting, by the mobile device, the user to select from the multiple third parties to authenticate the user, whereby the user selects one of the multiple third parties;

requesting the selected one of the multiple third parties to authenticate the user;

causing an authentication interface associated with the selected one of the multiple third parties to be displayed at the mobile device, wherein the authentication interface solicits the login credentials for the account associated with the user at the selected one of the multiple third parties; and

granting, by the mobile device, access to one or more services and/or functions of the mobile application installed at the mobile device, in response to an indication of a successful authentication of the user from the selected one of the multiple third parties, thereby relying on the authentication of the user by the selected one of the multiple third parties in order to grant the access to the one or more services and/or functions of the mobile application installed at the mobile device.

2. The computer-implemented method of claim 1 , wherein the selected one of the multiple third parties includes a financial institution; and

wherein the one or more services and/or functions of the mobile application include at least one of: mobile banking, a virtual wallet, and/or medical records.

3. The computer-implemented method of claim 1 , further comprising:

soliciting, by the mobile device, a biometric from the user;

capturing, by the mobile device, the biometric from the user; and

authenticating the user against a biometric template stored at the mobile device, based on the captured biometric, prior to granting the access to the one or more services and/or functions of the mobile application.

4. The computer-implemented method of claim 3 , wherein the mobile device includes a smartphone having the mobile application; and

wherein the biometric includes a fingerprint.

5. The computer implemented method of claim 1 , wherein the selected one of the multiple third parties is associated with an authentication server; and

wherein the method further comprises verifying authentication of the user with the authentication server, prior to granting the access to the one or more services and/or functions of the mobile application.

6. A non-transitory computer-readable storage medium comprising computer-executable instructions for use in managing digital identities associated with a mobile device, that when executed by at least one processor of the mobile device, cause the at least one processor of the mobile device to:

upon launching a mobile application installed at the mobile device, determine that identity data of a user stored in the mobile device is changed, relative to input data from the user since a prior login to the mobile application at the mobile device, the identity data including a government identification number, a mailing address, and at least one of an email address and/or a phone number of the user; and then,

in response to determining that the identity data is changed:

present, at a presentation unit of the mobile device, the user with multiple third parties, separate from the mobile device, to authenticate the user, wherein the user is associated with an account at each of the third parties and login credentials for the accounts;

prompt the user to select from the multiple third parties to authenticate the user, whereby the user selects one of the multiple third parties;

request the selected one of the multiple third parties to authenticate the user;

cause an authentication interface associated with the selected one of the multiple third parties to be displayed at the mobile device, wherein the authentication interface solicits the login credentials for the account associated with the user at the selected one of the multiple third parties; and

grant access to one or more services and/or functions of the mobile application installed at the mobile device, in response to an indication of a successful authentication from the selected one of the multiple third parties, thereby relying on the authentication of the user by the selected one of the multiple third parties in order to grant the access to the one or more services and/or functions of the mobile application installed at the mobile device.

7. The non-transitory computer readable storage medium of claim 6 , wherein the selected one of the multiple third parties is associated with an authentication server; and

wherein the computer-executable instructions, when executed by the at least one processor of the mobile device, further cause the at least one processor to verify authentication of the user with the authentication server, prior to granting the access to the one or more services and/or functions of the mobile application.

8. The non-transitory computer readable storage medium of claim 6 , wherein the computer-executable instructions, when executed by the at least one processor of the mobile device, further cause the at least one processor to:

solicit a biometric from the user; and

authenticate the user based on a captured biometric as compared to a biometric template stored at the mobile device, prior to granting the access to the one or more services and/or functions of the mobile application.

9. The non-transitory computer readable storage medium of claim 8 , wherein the computer-executable instructions, when executed by the at least one processor of the mobile device, further cause the at least one processor to capture the biometric from the user, after soliciting the biometric; and

wherein the biometric includes one of: a fingerprint and a facial image.

10. The non-transitory computer readable storage medium of claim 9 , wherein the mobile device includes a smartphone having the mobile application; and

wherein the biometric includes the fingerprint.

11. The non-transitory computer readable storage medium of claim 6 , wherein the selected one of the multiple third parties includes a financial institution.

12. The non-transitory computer readable storage medium of claim 6 , wherein the one or more services and/or functions of the mobile application include at least one of: mobile banking, a virtual wallet, and medical records.

13. A system for use in managing digital identities associated with a mobile device, the system comprising:

a mobile device including a non-transitory memory, a presentation unit, and a processor coupled to the presentation unit and the memory, the memory including identity data of a user and executable instructions, wherein the processor is configured by the executable instructions to:

upon launching a mobile application installed at the mobile device, determine that the identity data of the user stored in the mobile device is changed, relative to input data from the user since a prior login to the mobile application at the mobile device, the identity data including a government identification number, a mailing address, and at least one of an email address and/or a phone number of the user; and then,

in response to determining that the identity data is changed:

present, at the presentation unit, the user with multiple third parties, separate from the mobile device, to authenticate the user, wherein the user is associated with an account at each of the third parties and login credentials for the accounts;

prompt the user to select from the multiple third parties to authenticate the user, whereby the user selects one of the multiple third parties;

request the selected one of the multiple third parties to authenticate the user;

cause an authentication interface associated with the selected one of the multiple third parties to be displayed at the mobile device, wherein the authentication interface solicits the login credentials for the account associated with the user at the selected one of the multiple third parties; and

grant access to one or more services and/or functions of the mobile application installed at the mobile device, in response to an indication of a successful authentication of the user from the selected one of the multiple third parties, thereby relying on the authentication of the user by the selected one of the multiple third parties in order to grant the access to the one or more services and/or functions of the mobile application installed at the mobile device.

14. The system of claim 13 , wherein the executable instructions are defined by a software development kit (SDK) included in the mobile application; and

wherein the one or more services and/or functions of the mobile application include at least one of: mobile banking, a virtual wallet, and medical records.

15. The system of claim 14 , wherein the processor is further configured, by the executable instructions to verify authentication of the user with an authentication server, prior to granting the access to the one or more services and/or functions of the mobile application.

16. The system of claim 13 , wherein the processor is further configured, by the executable instructions, to:

solicit a biometric of the user;

capture the biometric of the user; and

authenticate the user based on the captured biometric as compared to a biometric template stored at the mobile device, prior to granting the access to the one or more services and/or functions of the mobile application.

17. The system of claim 16 , wherein the mobile device includes a smartphone having the mobile application; and

wherein the biometric includes one of: a fingerprint and a facial image.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2021
From: BHATT, SUMEET; KAMAL, ASHFAQ
To: MASTERCARD INTERNATIONAL INCORPORATED
Reel/Frame 057470/0176 →
Continuity (4)
Continuation 16134348 · Sep 18, 2018
Provisional Application 62560016 · Sep 18, 2017
Provisional Application 62560039 · Sep 18, 2017
Related Publication 20210409397A1 · Dec 30, 2021
References Cited (101)
US 7680819B1 · Mellmer et al. · 2010 [cited by applicant]
US 9124433B2 · Marien et al. · 2015 [cited by applicant]
US 9137228B1 · Newstadt · 2015 [cited by examiner]
US 9519901B1 · Dorogusker · 2016 [cited by applicant]
US 9635000B1 · Muftic · 2017 [cited by applicant]
US 9992022B1 · Chapman et al. · 2018 [cited by applicant]
US 10454677B1 · Nagelberg et al. · 2019 [cited by applicant]
US 10476862B2 · Kamal · 2019 [cited by applicant]
US 11100503B2 · Iyer et al. · 2021 [cited by applicant]
US 11122036B2 · Bhatt et al. · 2021 [cited by applicant]
US 11528139B2 · Smets et al. · 2022 [cited by applicant]
US 11663595B1 · Houseworth et al. · 2023 [cited by applicant]
US 20020100803A1 · Sehr · 2002 [cited by applicant]
US 20030163708A1 · Tang · 2003 [cited by applicant]
US 20060000892A1 · Bonalle · 2006 [cited by examiner]
US 20060157759A1 · Levy et al. · 2006 [cited by applicant]
US 20060229979A1 · Sato et al. · 2006 [cited by applicant]
US 20070208869A1 · Adelman et al. · 2007 [cited by applicant]
US 20070214093A1 · Colella · 2007 [cited by applicant]
US 20070250704A1 · Hallam-Baker · 2007 [cited by applicant]
US 20080256594A1 · Satish et al. · 2008 [cited by applicant]
US 20090164526A1 · Hayashi · 2009 [cited by applicant]
US 20090327144A1 · Hatter et al. · 2009 [cited by applicant]
US 20100067691A1 · Lin et al. · 2010 [cited by applicant]
US 20110191829A1 · Fischer et al. · 2011 [cited by applicant]
US 20110289318A1 · Zhang et al. · 2011 [cited by applicant]
US 20130226813A1 · Voltz · 2013 [cited by applicant]
US 20140068722A1 · Hayat · 2014 [cited by applicant]
US 20140101453A1 · Senthurpandi · 2014 [cited by applicant]
US 20140189808A1 · Mahaffey et al. · 2014 [cited by applicant]
US 20140279516A1 · Rellas · 2014 [cited by examiner]
US 20140279519A1 · Mattes et al. · 2014 [cited by applicant]
US 20140282884A1 · Bao et al. · 2014 [cited by applicant]
US 20150038118A1 · Berteau et al. · 2015 [cited by applicant]
US 20150059003A1 · Bouse · 2015 [cited by applicant]
US 20150095999A1 · Toth · 2015 [cited by applicant]
US 20150295906A1 · Ufford et al. · 2015 [cited by applicant]
US 20150319170A1 · Grossemy · 2015 [cited by applicant]
US 20150356523A1 · Madden · 2015 [cited by applicant]
US 20160210621A1 · Khan · 2016 [cited by examiner]
US 20160239653A1 · Loughlin-Mchugh · 2016 [cited by examiner]
US 20160300236A1 · Wiley et al. · 2016 [cited by applicant]
US 20160328713A1 · Ebrahimi · 2016 [cited by applicant]
US 20160330027A1 · Ebrahimi · 2016 [cited by applicant]
US 20160330035A1 · Ebrahimi et al. · 2016 [cited by applicant]
US 20160364703A1 · Bhatt et al. · 2016 [cited by applicant]
US 20160364730A1 · Rans et al. · 2016 [cited by applicant]
US 20170111175A1 · Oberhauser et al. · 2017 [cited by applicant]
US 20170201498A1 · Baig et al. · 2017 [cited by applicant]
US 20170213211A1 · Sibert et al. · 2017 [cited by applicant]
US 20170222814A1 · Oberhauser et al. · 2017 [cited by applicant]
US 20170250972A1 · Ronda et al. · 2017 [cited by applicant]
US 20170257358A1 · Ebrahimi et al. · 2017 [cited by applicant]
US 20170316409A1 · Smith et al. · 2017 [cited by applicant]
US 20180048864A1 · Taylor et al. · 2018 [cited by applicant]
US 20180068173A1 · Kolleri · 2018 [cited by applicant]
US 20180137512A1 · Georgiadis et al. · 2018 [cited by applicant]
US 20180165781A1 · Rodriguez et al. · 2018 [cited by applicant]
US 20180173871A1 · Toth · 2018 [cited by applicant]
US 20180181964A1 · Zagarese et al. · 2018 [cited by applicant]
US 20180204191A1 · Wilson et al. · 2018 [cited by applicant]
US 20180288033A1 · Kamal · 2018 [cited by applicant]
US 20180351747A1 · Spangemacher et al. · 2018 [cited by applicant]
US 20190087825A1 · Bhatt et al. · 2019 [cited by applicant]
US 20190089702A1 · Bhatt et al. · 2019 [cited by applicant]
US 20190166118A1 · Lee et al. · 2019 [cited by applicant]
US 20190190724A1 · Sundaresan et al. · 2019 [cited by applicant]
US 20190230496A1 · Wane · 2019 [cited by examiner]
US 20190245693A1 · Iyer et al. · 2019 [cited by applicant]
US 20190333054A1 · Cona et al. · 2019 [cited by applicant]
US 20200007322A1 · Weldemariam et al. · 2020 [cited by applicant]
US 20200076795A1 · Kamal · 2020 [cited by applicant]
US 20200322152A1 · Smets et al. · 2020 [cited by applicant]
US 20200374129A1 · Dilles et al. · 2020 [cited by applicant]
US 20210042600A1 · Jang · 2021 [cited by applicant]
US 20210319192A1 · Rodriguez et al. · 2021 [cited by applicant]
US 20210327547A1 · Praszczalek et al. · 2021 [cited by applicant]
US 20210383388A1 · Iyer et al. · 2021 [cited by applicant]
CA 2886548A · 2015 [cited by applicant]
EP 3073670A1 · 2016 [cited by applicant]
WO WO2008061344 · 2008 [cited by applicant]
WO WO2015002608 · 2015 [cited by applicant]
WO WO2018022850 · 2018 [cited by applicant]
U.S. Appl. No. 16/134,348, filed Sep. 18, 2018, Bhatt et al. [cited by applicant]
U.S. Appl. No. 15/891,062, filed Feb. 7, 2018, Iyer et al. [cited by applicant]
U.S. Appl. No. 15/476,526, filed Mar. 31, 2017, Ashfaq Kamal. [cited by applicant]
U.S. Appl. No. 16/679,115, filed Nov. 8, 2019, Ashfaq Kamal. [cited by applicant]
U.S. Appl. No. 16/134,371, filed Sep. 18, 2018, Bhatt et al. [cited by applicant]
U.S. Appl. No. 17/409,530, filed Aug. 23, 2021, Iyer et al. [cited by applicant]
F. No. K-11020/217/2018-UISAI (Auth-I), Government of India; https://uidai.gov.in/images/resource/UIDAL_Circular_11012018.pdf; Jan. 10, 2018; 5 pgs. [cited by applicant]
Times of India; Use 16-digit virtual No. for KYC; https://timesofindia.indiatimes.com/business/india-business/use-16-digit-virtual-no-for-kyc-fromtoday/articleshow/64810724.cms; web accessed Oct. 2, 2018; 56 pgs. [cited by applicant]
Economic Times; UIDAI introduces new two-layer security system to improve Aadhaar privacy; https://economictimes.indiatimes.com/news/economy/policy/uidai-introduces-new-two-layersecurity-system-to-improve-aadhaar-privac… [cited by applicant]
“Moving Beyond Social Security Numbers”; Blake Hall; https://medium.com/@blake_hall/moving-beyond-social-security-numbers-part-3-283bbf28ce74; Oct. 11, 2017; 5 pgs. [cited by applicant]
“Are you overlooking toeknization as a data security measure?”; Linda Musthaler; https://www.networkworld.com/article/3002307/security/are-you-overlooking-tokenization-as-adala-security-measure.html; Nov. 6, 2015; 5 pgs. [cited by applicant]
“Digital Identity—Why Now?”; David G. W. Birch; https://www.paymentsnz.co.nz/.../Digital_Identity_Seminar_Presentation_Final.pdf; Jan. 8, 2017; 79 pgs. [cited by applicant]
“Your guide to UPI—the world's most advanced payments system”; Sasi Desai et al.; https://medium.com/wharton-fintech/your-quide-to-upi-the-worlds-most-advanced-payments-system-b4e0b372b/0b; May 11, 2017; 20 pgs. [cited by applicant]
“Lessons from the World's Largest e-Identity Program”; procivis; https://procivis.ch/2018/02/13/lessons-from-the-worlds-largest-e-identity-program-indias-aadhaar/; Feb. 13, 2018; 6 pgs. [cited by applicant]
Times of India; “Treat virtual ID, UID token as Aadhaar number”; https://timesofindia.indiatimes.com/business/india-business/treat-virtual-id-uid-token-as-aadhaar-number-uidai-to-agencies/articleshow/65038574.cms: Jul. … [cited by applicant]
Neustar; “Neustar Selected as Digital Identity Solution Partner for Visa's ID Intelligence Ecosystem”; https://www.home.neustar/about-us/news-room/press-releases/2017/VisalDIntelligence: Oct. 24, 2017; 1 pg. [cited by applicant]
Crush Crypto; Selfkey ICO Review—Digital Identity Management System; https://crushcrypto.com/analysis-of-selfkev/; Dec. 5, 2017; 6 pgs. [cited by applicant]
U.S. Appl. No. 16/838,666, filed Apr. 2, 2020, Smets et al. [cited by applicant]