Systems and methods for verified communication between mobile applications

Patent metadata

Field	Value
Publication number	US-12314951-B2
Application number	US-202418755254-A
Country	US
Kind code	B2
Filing date	Jun 26, 2024
Priority date	May 19, 2022
Publication date	May 27, 2025
Grant date	May 27, 2025

Abstract

Systems and methods for establishing trust between a conventional mobile application and a micro application are disclosed. In accordance with aspects, a method may include authenticating user credentials with a backend processing infrastructure of a provider of a mobile application, wherein the authenticating generates session information; receiving, at the mobile application, a uniform resource identifier (URI), wherein the URI includes the session information as a parameter of the URI; receiving, at the mobile application, a user-activation of the URI; receiving, at the backend processing infrastructure of the provider of the mobile application and from a backend processing infrastructure of a third party, the session information; verifying, by the backend processing infrastructure of the provider of the mobile application the session information; and sending, by the backend processing infrastructure of the provider of the mobile application and to the backend processing infrastructure of the third party, requested user information.

First claim

The invention claimed is:

1. A method, comprising:
authenticating, by a backend processing infrastructure of a provider of a mobile application, user credentials for a user;
generating, by the backend processing infrastructure of the provider of the mobile application, a uniform resource identifier (URI) comprising session information;
receiving, at the mobile application, the URI;
receiving, at the mobile application, activation of the URI;
receiving, at the backend processing infrastructure of the provider of the mobile application and from a backend processing infrastructure of a third party, the session information and a request for information;
verifying, by the backend processing infrastructure of the provider of the mobile application, the session information; and
sending, by the backend processing infrastructure of the provider of the mobile application and to the backend processing infrastructure of the third party, the information.

2. The method of claim 1 , wherein the URI further comprises a third-party identifier that identifies the third party.

3. The method of claim 2 , wherein the mobile application sends the third-party identifier to a mobile device operating system and the mobile device operating system downloads and launches a micro-application provided by the third party.

4. The method of claim 3 , further comprising:
completing, by the backend processing infrastructure of the third party, an action using the information.

5. The method of claim 4 , further comprising:
sending, by the backend processing infrastructure of the third party, a notification to the micro-application, wherein the notification indicates that the action has been completed.

6. The method of claim 1 , wherein the session information includes a username.

7. The method of claim 1 , wherein the information includes an address associated with the user credentials.

8. The method of claim 1 , wherein the information includes payment information associated with the user credentials.

9. The method of claim 1 , wherein the session information is received by the backend processing infrastructure of the provider of the mobile application via an API call to an external API gateway exposed by the backend processing infrastructure of the provider of the mobile application.

10. The method of claim 1 , wherein the session information is hashed.

11. A non-transitory computer readable storage medium, including instructions stored thereon, which when read and executed by one or more computers cause the one or more computers to perform steps comprising:
authenticating user credentials with a backend processing infrastructure of a provider of a mobile application;
generating a uniform resource identifier (URI) comprising session information;
receiving the URI;
receiving activation of the URI;
receiving, from a backend processing infrastructure of a third party, the session information and a request for information;
verifying the session information; and
sending, by the backend processing infrastructure of the provider of the mobile application and to the backend processing infrastructure of the third party, the information.

12. The non-transitory computer readable storage medium of claim 11 , wherein the URI further comprises a third-party identifier identifies the third party.

13. The non-transitory computer readable storage medium of claim 11 , wherein the information includes an address associated with the user credentials.

14. The non-transitory computer readable storage medium of claim 11 , wherein the information includes payment information associated with the user credentials.

15. The non-transitory computer readable storage medium of claim 11 , wherein the session information is received by the backend processing infrastructure of the provider of the mobile application via an API call to an external API gateway exposed by the backend processing infrastructure of the provider of the mobile application.

16. A system comprising:
a backend processing infrastructure of a provider of a mobile application; and
a mobile device that executes the mobile application;
wherein:
the backend processing infrastructure of a provider of the mobile application authenticates, user credentials for a user;
the backend processing infrastructure of the provider of the mobile application generates a uniform resource identifier (URI) comprising session information;
the mobile application receives the URI;
the mobile application, receives activation of the URI;
the backend processing infrastructure of the provider of the mobile application receives, from a backend processing infrastructure of a third party, the session information and a request for information;
the backend processing infrastructure of the provider of the mobile application verifies the session information; and
the backend processing infrastructure of the provider of the mobile application sends, to the backend processing infrastructure of the third party, the information.

17. The system of claim 16 , wherein the URI further comprises a third-party identifier that identifies the third party.

18. The system of claim 16 , wherein the session information includes a username.

19. The system of claim 16 , wherein the information includes an address associated with the user credentials.

20. The system of claim 16 , wherein the information includes payment information associated with the user credentials.

Assignees

• Jpmorgan Chase Bank Na

Inventors

• Spector Howard
• Ouellette Scott H
• Carey Dave

Classifications

• H04L67/53 Primary

  using third party service providers · CPC title

• G06Q20/326

  Payment applications installed on the mobile devices · CPC title

• G06F21/32

  using biometric data, e.g. fingerprints, iris scans or voiceprints · CPC title

• G06Q20/3821

  Electronic credentials · CPC title

• G06Q20/40145

  Biometric identity checks · CPC title