Autofilling data based on account authentication using a contactless card
US-2023162187-A1 · May 25, 2023 · US
US12062045B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12062045-B2 |
| Application number | US-202217664136-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 19, 2022 |
| Priority date | May 19, 2022 |
| Publication date | Aug 13, 2024 |
| Grant date | Aug 13, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: 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. 2. The method of claim 1 , wherein the URI includes a third-party identifier as a second parameter of the URI, wherein the third party identifier 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. 4. The method of claim 3 , wherein the mobile device operating system downloads and launches a micro-application provided by the third party. 5. The method of claim 4 , further comprising: completing, by the backend processing infrastructure of the third party, an action using the requested information. 6. The method of claim 5 , 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. 7. The method of claim 1 , wherein the session information includes a username. 8. The method of claim 1 , wherein the requested user information includes an address associated with the user credentials. 9. The method of claim 1 , wherein the requested user information includes payment information associated with the user credentials. 10. 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. 11. The method of claim 1 , wherein the session information is hashed. 12. The method of claim 11 , wherein the session information is hashed using a SHA-2 algorithm. 13. 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, 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. 14. The non-transitory computer readable storage medium of claim 13 , wherein the URI includes a third-party identifier as a second parameter of the URI, wherein the third party identifier identifies the third party. 15. The non-transitory computer readable storage medium of claim 13 , wherein the mobile application sends the third-party identifier to a mobile device operating system. 16. The non-transitory computer readable storage medium of claim 13 , wherein the session information includes a username. 17. The non-transitory computer readable storage medium of claim 13 , wherein the requested user information includes an address associated with the user credentials. 18. The non-transitory computer readable storage medium of claim 13 , wherein the requested user information includes payment information associated with the user credentials. 19. The non-transitory computer readable storage medium of claim 13 , 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. 20. 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 the provider of the mobile application is configured to authenticate user credentials, and wherein the authentication of the user credentials generates session information; wherein the mobile application is configured to: receive a uniform resource identifier (URI), wherein the URI includes the session information as a parameter of the URI; receive a user-activation of the URI; and wherein the backend processing infrastructure of the provider of the mobile application is further configured to: receive, from a backend processing infrastructure of a third party, the session information; verify the session information; and send, to the backend processing infrastructure of the third party, requested user information.
using third party service providers · CPC title
Payment applications installed on the mobile devices · CPC title
using biometric data, e.g. fingerprints, iris scans or voiceprints · CPC title
Electronic credentials · CPC title
Biometric identity checks · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.