Management of reloadable credentials on an electronic device using an online resource
US-2015371226-A1 · Dec 24, 2015 · US
US12572933B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12572933-B2 |
| Application number | US-202318386024-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 1, 2023 |
| Priority date | Jan 15, 2015 |
| Publication date | Mar 10, 2026 |
| Grant date | Mar 10, 2026 |
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.
A method for providing an application programming interface (API) service that enables a third-party to provide screens that allow account holders to provide credentials to an institution while bypassing the third-party, comprising transmitting an API to a third-party device for integration into a website served by the third-party, the API configured to generate a portal that accepts the credentials without revealing the credentials to the third-party; receiving, via the API integrated into the third-party website, a request for verification of a user; instructing the API integrated into the third-party website to display a screen of the institution within a window through which transmissions can be received directly from the user without the third-party receiving the transmissions; receiving, directly from the user and through the window, user credentials input into the screen without revealing the input user credentials to the third-party; and verifying the user by confirming the user credentials.
Opening claim text (preview).
What is claimed is: 1 . A method for providing services including an application programming interface (API) service that enables a third-party to provide screens that allow account holders to provide credentials to an institution while bypassing the third-party, the method comprising: transmitting a login API to a third-party device for integration into a third-party website served by the third-party, the login API configured to generate, through the third-party website, a portal that accepts the credentials without revealing the credentials to the third-party; receiving, via the login API integrated into the third-party website, a request for verification of a user; instructing the login API integrated into the third-party website to display a screen of the institution within a window through which transmissions can be received directly from the user without the third-party receiving the transmissions; receiving, directly from the user and through the window, user credentials input into the screen without revealing the input user credentials to the third-party; and verifying the user by confirming the user credentials. 2 . The method of claim 1 , wherein the request for verification comprises an information request by the third-party requesting information concerning the user. 3 . The method of claim 2 , further comprising: receiving a transmission comprising an approval from the user to provide the information concerning the user to the third-party. 4 . The method of claim 3 , further comprising: transmitting, to the third-party, the requested information concerning the user. 5 . The method of claim 1 , further comprising: identifying a user option associated with the user credentials; transmitting, to the user, account options including the user option associated with the user credentials; and receiving, from the user, a selection of a user account corresponding to the identified user option. 6 . The method of claim 5 , wherein the account options include a checking account with a financial institution or a credit card issued by the financial institution. 7 . The method of claim 1 , further comprising: verifying that the third-party subscribes to the API service, wherein verifying that the third-party subscribes to the API service comprises cross-referencing third-party identification to a plurality of registered third-party identifications in a database. 8 . The method of claim 1 , wherein the login API is configured to generate a login portal that accepts login credentials through the third-party website without leaving the third-party website. 9 . The method of claim 1 , wherein the user credentials comprise at least one of a username and a passcode used by the user. 10 . A computing system that provides services including an application programming interface (API) service that enables a third-party to provide screens that allow account holders to provide credentials to the computing system directly while bypassing the third-party, the computing system comprising: a memory; and one or more processors configured to: transmit a login API to a third-party device, the login API configured to generate, through a third-party website, a portal that accepts the credentials without revealing the credentials to the third-party; receive, via the login API integrated into the third-party website, a request for verification of a user; instruct the login API integrated into the third-party website to display a screen of an institution in a window through which the computing system can receive transmissions directly from the user without the third-party receiving the transmissions; receive, directly from the user through the window, user credentials input into the screen without revealing the input user credentials to the third-party; and verifying the user based on the user credentials. 11 . The computing system of claim 10 , wherein the one or more processors are further configured to: receive a transmission comprising approval from the user to provide information concerning the user to the third-party. 12 . The computing system of claim 10 , wherein the one or more processors are further configured to: identify a user option associated with the user credentials; transmit account options to the user, wherein the account options include the identified user option and another option; and receive a selection of a user account corresponding to the identified user option. 13 . The computing system of claim 12 , wherein the account options include a checking account with a financial institution or a credit card issued by the financial institution. 14 . The computing system of claim 13 , wherein the financial institution is a first financial institution, and wherein the account options include an account at a second financial institution. 15 . The computing system of claim 10 , wherein the login API is configured to generate a login portal that accepts login credentials through the third-party website without leaving the third-party website, and wherein the one or more processors are further configured to: cross-reference third-party identification with a plurality of registered third-party identifications to verify that the third-party subscribes to the API service provided. 16 . A non-transitory computer-readable media with computer- executable instructions embodied thereon that, when executed by one or more processors of a computing system, cause the computing system to perform operations, the operations comprising: transmitting a login application programming interface (API) to a third-party for integration into a third-party website, the login API configured to generate, through the third- party website, a portal that accepts credentials without revealing the credentials to the third- party; receiving, via the login API integrated into the third-party website, a request for verification of a user; instructing the login API integrated into the third-party website to display a screen of an institution within a window through which transmissions can be received directly from the user without the third-party receiving the transmissions; receiving, directly from the user through the window, user credentials input into the screen without revealing the input user credentials to the third-party; and verifying the user by confirming the user credentials. 17 . The non-transitory computer-readable media of claim 16 , wherein the request for verification comprises an information request by the third-party requesting information concerning the user, and wherein the operations further comprise: receiving an approval from the user to provide the information concerning the user to the third-party; and transmitting the requested information concerning the user to the third-party. 18 . The non-transitory computer-readable media of claim 16 , wherein the operations further comprise: identifying a user option associated with the user credentials; transmitting to the user account options including the user option associated with the user credentials; and receiving from the user a selection of an account corresponding to an identified user payment option. 19 . The non-transitory computer-readable media of claim 18 , wherein the user account options include a checking account with a financial institution or a credit card issued by the financial institution. 20 . The non-transitory computer-readable media of claim 16 , wherein the login API is configured to ge
Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) · CPC title
Bill distribution or payments · CPC title
the neutral party being a clearing house · CPC title
comprising security or operator identification provisions, e.g. password entry · CPC title
comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.