Source: https://patents.google.com/patent/US9449346B1/en
Timestamp: 2019-05-19 11:47:17
Document Index: 286598498

Matched Legal Cases: ['art 1', 'art 2', 'art 1', 'art 10', 'art 11', 'art 2', 'art 3', 'art 4', 'art 5', 'art 6', 'art 7', 'art 8', 'art 9']

US9449346B1 - System and method for programmatically accessing financial data - Google Patents
System and method for programmatically accessing financial data Download PDF
US9449346B1
US9449346B1 US14/790,840 US201514790840A US9449346B1 US 9449346 B1 US9449346 B1 US 9449346B1 US 201514790840 A US201514790840 A US 201514790840A US 9449346 B1 US9449346 B1 US 9449346B1
US14/790,840
2014-05-21 Priority to US201462001452P priority Critical
2015-05-21 Priority to US201514719110A priority
2015-07-02 Application filed by Plaid Technologies, Inc. filed Critical Plaid Technologies, Inc.
2015-07-02 Priority to US14/790,840 priority patent/US9449346B1/en
2015-08-10 Assigned to Plaid Technologies, Inc. reassignment Plaid Technologies, Inc. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LI, CHARLES, PERRET, ZACH, HOCKEY, WILLIAM
2015-12-11 Assigned to Plaid Technologies, Inc. reassignment Plaid Technologies, Inc. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LI, CHARLES, HOCKEY, WILLIAM, PERRET, ZACH
2016-09-20 Publication of US9449346B1 publication Critical patent/US9449346B1/en
Systems and methods for programmatic access of external financial service systems. An application proxy instance is created that simulates an application of an external financial service system. A normalized account request is received for financial data of the external financial service system for a specified account. The normalized account request is provided by an external financial application system by using a financial data API of the financial platform system. Responsive to the normalized account request, communication is negotiated with the external financial service system by using the application proxy instance to access the requested financial data from the external financial service system by using a proprietary Application Programming Interface (API) of the external financial service system. The financial data is provided to the external financial application system as a response to the normalized account request.
This application is a continuation of co-pending U.S. patent application Ser. No. 14/719,110, filed 21 May 2015, which claims the benefit of U.S. Provisional Application Ser. No. 62/001,452, filed on 21 May 2014, which is incorporated in its entirety by this reference.
This invention relates generally to the financial API field, and more specifically to a new and useful system and method for programmatically accessing financial data in the financial API field.
Banks and other financial institutions hold considerable information relating to a user's current financial status and financial history. Such data is often presented through a bank's website or sometimes applications (e.g., mobile applications). However, such tools only provide information about the single institution, and do not combine multiple institutions. Furthermore, such institutions commonly do not expose a public version of an API, providing a large barrier to other parties to solve such a problem. Some online products offer capabilities to merge information from different institutions. One such commonly used approach is to simulate user access of a bank website to access information. There are numerous problems with such solutions. Web-crawling solutions such as these are slow to the end user because full pages have to be rendered and sometimes depend on executing javascript and other user interface simulations. Related to this, such methods are more costly to the financial institutions because numerous web resources are consumed for a given piece of information. Additionally, such a web-crawling approach is highly dependent on the visual representation of the information. A change in the layout or visual representation can break such web crawling. Thus, there is a need in the financial API field to create a new and useful system and method for programmatically accessing financial data. This invention provides such improved/new and useful system and method.
FIG. 1 is a schematic representation of a system of an embodiment;
FIG. 2 is a flow diagram of a method of an embodiment;
FIG. 3 is a representation of exemplary proxy instances of an embodiment;
FIG. 4 is a schematic representation of a system of an embodiment;
FIG. 5 is a representation of an application proxy system of an embodiment;
FIG. 6 is a representation of exemplary proxy instances of an embodiment;
FIG. 7 is a flow diagram of a method of an embodiment;
FIG. 8 is a flow diagram of a method of an embodiment; and
FIG. 9 is an architecture diagram of system of an embodiment.
1. System for Programmatically Accessing Financial Data
As shown in FIG. 1, a system 100 for programmatically accessing financial data of a preferred embodiment can include an application programming interface (API) service 110, an application proxy system 120, and at least one institution interface module (e.g., the modules 131-133 of FIG. 1). The system functions to provide programmatic access to an external service (e.g., the services 141-143 of FIG. 1) that lacks exposed programmatic access. The external services are preferably proprietary and external financial services. The external services can include banks, credit card providers, investment services, loan providers, and other suitable financial institutions. Such institutions may have first party applications that enable users to access account information from a mobile or desktop application. Such first party applications will commonly use a proprietary or customized application programming interface (API) (e.g., the APIs 161-163 of FIG. 1). The API is commonly not public and not exposed. For example, a developer is commonly prevented from registering an account and using an open API authentication approach to arbitrarily access the API resources. Additionally, the API (e.g., the APIs 161-163 of FIG. 1) of the institution is a non-trivial customized interface protocol that isn't shared with other institutions—each institution conforms to its own interface. The method can additionally function to provide a normalized interface (e.g., the API service 110 of FIG. 1) to a plurality of external services (e.g., the services 141-143 of FIG. 1). The system 100 enables access to an account within an institution by leveraging the application proxy system 120. A virtualized “image” or digital simulation of an application instance is maintained in the application proxy system 120 and used to access the unexposed API (e.g., 161-163) of the institution. While the system is preferably applied to financial institutions, the system may additionally or alternatively be applied to providing API access to other external entities with closed or limited API access.
The API service no, which functions to provide a normalized customer/user facing interface. The API interface is preferably normalized in the sense that the underlying API to the external institution (e.g., 141-143) that acts as the source of the information is abstracted away, and the interface to different institution information is substantially similar. In some variations, various aspects of the API no may be limited when interfacing with particular institutions. For example, one institution may not support a feature such as digital check deposit, while a second institution does. In this case, the API no may define the API such that the API feature for check deposit is prevented for the first institution. The system 100 and more specifically the API service 110 is preferably used to provide an accessible API service to outside developers. As such, the system 100 is preferably a multi-tenant system that allows numerous accounts to share use of the system 100. The system 100 and more particularly the API 110 may alternatively be a single tenant system. For example, the system may be used as an internal system to a website providing an online financial management product.
The API service 110 is preferably a RESTful API but may alternatively be any suitable API such as SOAP or custom protocol. The RESTful API works according to an HTTP request and response model. HTTP requests (or any suitable request communication) to the system 100 preferably observe the principles of a RESTful design. RESTful is understood in this document to describe a Representational State Transfer architecture as is known in the art. The RESTful HTTP requests are preferably stateless, thus each message communicated contains all necessary information for processing the request and generating a response. The API service no can include various resources which act as endpoints which act as a mechanism for specifying requested information or requesting particular actions. The resources can be expressed as URI's or resource paths. The RESTful API resources can additionally be responsive to different types of HTTP methods such as GET, PUT, POST and/or DELETE.
The API service 110 can provide an interface into a variety of information and action resources. Information relating to an account is preferably accessible through querying particular API resources. For example, a list of transactions and information about each individual transaction may be accessible through different API calls. Information can additionally relate to account summary information, account details such as address and contact information, information about other parties such as the entities involved in a transaction, and/or any suitable information. The API may additionally be used to trigger or facilitate performing some action. For example, an API call may be used in transferring money, updating account information, setting up alerts, or performing any suitable action. Those skilled in the art will appreciate that such exemplary API features that any suitable API feature possibilities and semantic architecture may be used.
In one exemplary implementation, an API call can support adding a user, completing authentication, accessing transaction information, and other actions. For example, an application may POST to a “/connect” REST API resource to authenticate a user; if the institution includes multi-factor authentication, then a “/connect/step” resource can be submitted to complete multi-factor authentication credentials; and then performing a GET on the “/connect” resource can access transactional data. The API may additionally include informational resources to access information about entities involved in transactions. For example, the API 110 may allow a particular business resource to be accessed to obtain contextual information about the business such as name, location, and classification.
The application proxy system 120 functions to manage the simulation of application access to an institution. The application proxy system 120 operates in cooperation with an institution interface module (e.g., one of the modules 131-133 of FIG. 1) to establish a data model or some data image that acts as a virtualized application instance—an application proxy instance (e.g., 121-123) preferably serves as such a virtualized instance. From the perspective of the institution, the proxy instance (e.g., 121-123) appears as an application (e.g., the Bank 2 application 153 of FIG. 1) installed on a physical user device (e.g., user devices 171 and 172 of FIG. 1) that is being used. In other words, the requests received from the proxy instance are treated like requests from a mobile app, desktop app, or web-based application of a user. The application proxy system 120 preferably stores and maintains a plurality of application proxy instances (e.g., proxy instances 121-123). The proxy instances are preferably configuration settings and properties that when used according to a defined institution interface (e.g., an institution interface of an institution interface module 131-133), will appear as requests from first party applications (e.g., the application 153) of the institution (e.g., 141-143). A different proxy instance is preferably created and maintained for each account-institution pair. A given user may have multiple accounts with different institutions. A proxy instance preferably includes a set of properties that can be used to authenticate the proxy instance with the institution system (e.g., 141-143). The API service 120 preferably provides a method to programmatically create a proxy instance for a user. The user preferably provides some account credentials that can be used in an initial registration of the proxy instance with the API of the institution. The proxy instance may be characterized as a set of properties that can be stored and maintained. Some of those properties may be automatically generated, may be provided from the institution during negotiating registration, may be properties of the application that is being simulated, or include any suitable identifying and authenticating information. The properties may include a unique user identifier code, an authentication token, a MAC address (e.g., a MAC address of a user device 171-172), or any suitable information. When a request is made to a bank on behalf of a user, the properties of the proxy instance are preferably invoked to gain access to the institution on behalf of the associated user.
FIG. 3 depicts exemplary proxy instances 121-123 of FIG. 1. As shown in FIG. 3, User A has accounts in Bank 1 and Bank 2, and User B has accounts in Bank 2. As shown in FIG. 3, each proxy instance includes account credentials and properties.
An institution interface module (e.g., one of the modules 131-133 of FIG. 1) functions to model the internal interface (e.g., 161-163) of at least one application (e.g., the application 153) with an external institution (e.g., 141-143). An institution interface module is preferably established for each institution with which the system 100 can interface. For example, an institution interface module may exist for each bank and/or credit card company that is available in the system. The institution interface module is preferably a set of rules and processes of a particular institution. The institution interface module preferably includes a proxy sub-module that defines how the institution recognizes and/or authenticates a particular application. Some banks may depend on the MAC address of a device (e.g., a MAC address of user devices 171 and 172), some depend on asymmetric cryptography tokens, while others may generate encrypted tokens. The proxy sub-module is preferably used in establishing the proxy instance information. The institution interface module can additionally include institution protocol sub-module, which defines a mapping between provided API no functionality and the form and mode of communication with the external institution (e.g., 141-143). The institution protocol sub-module can define the headers, body, and other properties of messages sent to the associated institution. The protocol sub-module may additionally define how data should be processed to form that message. In some cases, the data may be encrypted in a standard or proprietary format, which the protocol sub-module can define. Additionally, the protocol sub-module can define the communication flow to fulfill a request. In some cases, multiple requests may need to be made to complete a request objective. Other aspects of dealing with an interface (e.g., 161-163) of an external institution (e.g., 141-143) may additionally be built into the institution interface module such as multi-factor authentication rules. An institution interface module is preferably constructed based on use of an actual application (e.g., the application 153). The communication and/or the source code can be parsed and analyzed to establish some or all of an institution interface module. In some implementations, source code of a first party application (e.g. the application 153) of an external financial service is parsed and analyzed to establish some or all of an institution interface module for the external financial institution. In some implementations, communication between an external financial service and a first party application (e.g. the application 153) of the external financial service is parsed and analyzed to establish some or all of an institution interface module for the external financial institution.
2. Method for Programmatically Accessing Financial Data
As shown in FIG. 2, a method for programmatically accessing financial data of a preferred embodiment can include creating an application proxy instance S110, receiving a normalized account request S120, negotiating communication with an external interface through a proxy instance S130, returning results S140. The method functions to provide programmatic access to an external service that lacks exposed programmatic access. The external services are preferably proprietary and external financial services. The external services can include banks, credit card providers, investment services, loan providers, and other suitable financial institutions. Such institutions may have first party applications (e.g., the application 153 of FIG. 1) that enable users to access account information from a mobile or desktop application. Such first party applications will commonly use a proprietary or customized application programming interface (API) (e.g., 161-163 of FIG. 1). The API is commonly not public and not exposed. For example, a developer is commonly prevented from registering an account and using an open API authentication approach to arbitrarily access the API resources. Additionally the API is a non-trivial customized interface protocol that isn't shared with other institutions—each institution conforms to its own interface. The method can additionally function to provide a normalized interface to a plurality of external services (e.g., 141-143 of FIG. 1). The method enables a programmatic interface into an account within an institution by leveraging an application proxy approach. A virtualized “image” or digital simulation of an application instance is maintained in the application proxy system 120 and used to access the unexposed API (e.g., 161-163) of the institution. While the system 100 is preferably applied to financial institutions, the system 100 may additionally or alternatively be applied to providing API access to other external entities with closed or limited API access. The method is preferably implemented through a system as described above (e.g, the system 100 of FIG. 1), but may alternatively be implemented by any suitable system.
Block S110, which includes creating an application proxy instance (e.g., an application proxy instance 121-123 of FIG. 1), functions to establish a digital image of an application instance (e.g., the application instance 153 of FIG. 1) for a selected institution (e.g., the Bank 142 of FIG. 1). Creating an application proxy instances is preferably initiated in response to receiving an initial request. The initial request is initiated by a user (or entity) (e.g., User A or User B of FIG. 1) interacting with a system of a developer account (e.g., a system of the application instances 152 of the user devices 171 and 172 of FIG. 1) and the system of the developer account (e.g., the system of the application instances 152) will then send the initial request to the system 100. The user (e.g., User A and User B of FIG. 1) will preferably have an institution account in a system of the external institution (e.g., an online bank account). An application proxy instance (e.g., 121-123 of FIG. 1) can be created during the initial registration or at a later time, which will provide access to account information of the external institution (e.g., 141-143). Once created, the application proxy instance of that user can be persisted and used at a later time for that given user-institution combination (e.g., “User A-Bank 1”, “User A-Bank 2”, “User B-Bank 2”). However, a new proxy instance may be created when the proxy instance becomes invalid (e.g., as a result of institution API changes, password/login changes made within the institution, or other reasonable changes to invalidate a proxy instance). The initial request is preferably received through a normalized API (e.g., 110 of FIG. 1) as a connection request. The connection request is preferably accompanied by parameters that specify a selected institution (if there are multiple institution options) and user credentials for the institution. The user credentials may include a username, password, pin code, and/or any suitable credentials. The API request may additionally include authentication credentials such as a client identifier and secret token that is associated with the account in the system.
Creating a proxy instance preferably includes negotiating registration of the proxy instance with the institution, which functions to establish the proxy instance with the selected external institution. An institution interface module (e.g., one of the modules 131-133 of FIG. 1) preferably facilitates navigating the communication handshaking during the initial login. Different institutions may have different processes to register or enroll a new application (which in the method is a proxy instance) such as multi-factor authentication. During the negotiation, various elements may be extracted and stored as part of the proxy instance. Similarly, some properties may be generated based on communication with the institution. For example, a MAC address or a unique device identifier may be used in connecting to the services of the external institution. Such properties are preferably stored as part of the proxy instance.
As mentioned above, multifactor authentication (MFA) may be part of negotiating with an external institution. Frequently, an external institution will respond with indication of a MFA credential requirement. Such MFA requirements are preferably fulfilled by relaying the MFA challenge/task up to a user. In one implementation, the system 100 will receive a message indicating that a security question should be asked to complete the negotiation. The security question is passed back to the associated application, e.g., the applications 151 and 152 of FIG. 1, (which may be operated by a developer account of the system 100), then that application (e.g., the application 152 of FIG. 1) will present the security question in some manner to obtain the user response. The MFA can include security questions, additional pin codes (such as those supplied by a one time password generator or a code transmitted to a secondary device), or any suitable form of MFA.
Block S120, receiving a normalized account request, functions to receive an API request in the format of the system 100. As mentioned above, the syntax and mode of communicating an API request is normalized such that the form is independent of the institution (e.g., one of the institutions 141-143 of FIG. 1). The requests can include a variety of types of requests which may include: Obtaining a list of transactions; requesting details on a particular transaction; performing some financial transfer (moving money from savings to checking, setting up transfer to another account, making scheduled payments, digital deposit of a check, and the like), updating account information (e.g., updating contact information, changing password, manage alerts, and the like), and/or requesting services (e.g., new cards, reporting fraud, and the like). A normalized account request is preferably mapped to an institution interface module (e.g., one of the institution interface modules 131-133 of FIG. 1) or other suitable component that defines communication to fulfill the API request.
Block S130, which includes negotiating communication with an external interface (e.g., one of APIs 161-163) through a proxy instance (e.g., one of the proxy instances 121-123) functions to execute and manage communication between the system 100 and an external institution system (e.g., a 141-143) when fulfilling an account request. The proxy instance (e.g., one of the proxy instances 121-123) preferably provides a mechanism through which access will be granted. The communication is preferably executed while an authenticated session is active. Communication sessions may be expired by the system 100 or the external institution (e.g., a 141-143) for various reasons such as remaining inactive for a set amount of time. A communication session may be active subsequent to enrolling a proxy instance or may require setting up a session through the proxy instance as described below.
Negotiating communication preferably includes creating requests that conform to expected messages of the external institution (e.g., a 141-143). This can include setting headers, body contents, and other message properties. An institution is preferably expecting particular headers. For example, the headers may include a host or path, a data, content type, cookies, MAC address, a user identifier, auth properties, or other suitable headers. Creating requests can additionally include transforming request properties into expected form, which may primarily include applying a set encryption pattern to a request. In one variation, transforming the request involves encrypting content according to a public key, wherein the public key may be stored as part of the proxy instance. The institutions may take varying approaches to how information is communicated. In an alternative institution, the contents of a message may be unencrypted; in which case, the contents are submitted in a plaintext, unencrypted form. In addition to creating requests that conform to expected messages of the external institution, the method can include following a request-response pattern. That pattern can involve a single request and response, but may alternatively include a sequence of different request and responses to obtain desired information.
In some variations, information or actions may not be available through the first proxy instance and so the method may include automatically switching to a second proxy instance with supported functionality. For example, full bank statements may not be available in a mobile application, and the institution API (e.g., one of 161-163 of FIG. 1) may not include such functionality. Accordingly, when that functionality is required to fulfill an API request, then a second proxy interface may be used. In some variations, an API request may be require multiple institutions to be queried. Such an API request may be particularly useful for summarizing financial statements across multiple accounts. The method can include negotiating communication for multiple institutions and combining results into a combined form.
Block S140, which includes returning results, functions to deliver the results as a response to the request. Returning the results preferably includes transforming the data obtained from the external institution into a normalized form. The information is preferably formatted into a standardized format that is substantially similar in representation between different institutions served by the system 100. Transforming the data can additionally include processing, supplementing, and/or otherwise enhancing information. Some information provided by an institution may be poorly formed. For example, store information for a particular transaction may be poorly labeled and may be represented different from other institutions. Such contextual information about external entities can preferably cleaned and supplemented with additional information. For example, an entity may be supplemented with categorical labels, tags, geo location information, and/or other suitable information. The returned results can be represented data format such as JSON, XML, or any suitable format.
The method can additionally include setting up a session through the proxy instance S150, functions to facilitate accessing information after negotiating a proxy instance for an account and institution. The proxy instance (e.g., 121-123 of FIG. 1) will preferably store and maintain information required for subsequent access. The institutions will commonly restrict access to set sessions, which may expire after some amount of time or may require reconfirming user credentials. So when an API request for an account occurs after a communication session has expired then the method preferably automatically sets up a new session using the previous user credentials and proxy instance credentials. In some variations, MFA challenges, such as security questions, may be automatically completed.
The method can additionally include re-capturing updated credentials, which functions to update user credentials for an institution. Updated credentials are preferably updated when a user changes them within the institution or when the proxy instance is otherwise locked out of the account. An error will preferably occur indicating that a communication session was not successful, and then an API request can be submitted to update a proxy instance with new credentials.
3. Financial Platform System
As shown in FIG. 4, a multi-tenant financial platform system 400 of an embodiment includes an application programming interface (API) service 410, an application proxy system 420, and at least one institution interface module (e.g., the modules 431-433 of FIG. 4). The API service 410, application proxy system 420, and institution interface modules 431-433 of FIG. 4 are similar to the API service 110, application proxy system 120, and institution interface modules 131-133 of FIG. 1.
As shown in FIG. 4, the financial service system 441 includes a public Web browser interface 491 for accessing the financial service system 441 via a Web Browser (or any suitable Web client) (e.g., the web browser 481 of the user device 473). As described below for FIGS. 7 and 8, the methods of FIGS. 7 and 8 provide access to the financial service system 441 via a private, proprietary API (e.g., 461), as opposed to access via the public Web browser interface 491. In some implementations, the Web browser interface 491 is a web server that hosts a web site for access of the financial system via a Web browser over the Internet.
As shown in FIG. 5, the application proxy system 420 includes application proxy instances (e.g., proxy instances 521-525) for user accounts (e.g., user accounts 511, 512 and 513) of developer accounts (e.g., Dev Account B 531 and Dev Account A 532) at the financial platform system 400. The application proxy system 420 includes an application proxy instance management module 541 that is constructed to generate application proxy instances, configure application proxy instances, and remove application proxy instances.
In some implementations, each application proxy instance (e.g., proxy instances 521-525), specifies the developer account, the user account of the developer account, the associated financial service system (e.g., “Institution”), and credentials of the user account for the financial service system, as shown in FIG. 6. In some implementations, each application proxy instance specifies properties of the application proxy instance. In some implementations, properties include one or more of a unique user identifier code, an authentication token, a MAC address (e.g., a MAC address of a user device 471-472), or any suitable information.
4. Method for Accessing Financial Data
As shown in FIG. 7, a method 700 for accessing financial data includes: creating at least one application proxy instance (e.g., a proxy instance 521-525 of FIG. 5) that simulates an application (e.g., application 453 of FIG. 4) of an external financial service system (e.g., an external financial service system 441-443 of FIG. 4) (process S710); receiving a normalized API account request for financial data of at least one external financial service system for a specified account, the normalized API account request being provided by an external financial application system (e.g., a financial application system of the application 452 of FIG. 4) by using a normalized financial data API (e.g., API 410 of FIG. 4) of the financial platform system (process S720). Responsive to the normalized API account request (of the process S720): communication is negotiated with each external financial service system (of the normalized account request) by using the respective application proxy instance to access the requested financial data from the external financial service system by using a proprietary Application Programming Interface (API) (e.g., one of the proprietary APIs 461-463 of FIG. 4) of the external financial service system (process S730); and the financial data is provided to the external financial application system as a response to the normalized account request (process S740).
In the example embodiment of FIG. 7, the method 700 is implemented by the financial platform system 400. In the example embodiment, the financial platform system is constructed to programmatically access financial data as described herein for the method 700.
4.1 Creating an Proxy Instance
Process S710, which includes creating an application proxy instance that simulates an application of an external financial service system, functions to control the application proxy instance management module 541 of FIG. 5 to create an application proxy instance. In some implementations, the application proxy instance management module 541 creates the application proxy instance as described above for the process S110 of FIG. 1.
In some implementations, the application proxy instance management module 541 creates the application proxy instance responsive to a request to create an application proxy instance. In some implementations, the request to create an application proxy instance specifies information identifying an external financial service system, and a user account of an external application system (e.g., a user account of an external application system of the application 452 of FIG. 4). In some implementations, the request to create an application proxy instance specifies user credentials for the financial service system. In some implementations, the request to create an application proxy instance specifies information identifying an account of the financial platform system 400 associated with the external application system. In some implementations, the request to create an application proxy instance specifies properties for the application proxy instance. In some implementations, properties for the application proxy instance include at least one of a unique user identifier code, an authentication token, a MAC address (e.g., a MAC address of a user device 471-472), financial accounts of the corresponding financial service system, and any other suitable information.
In some implementations, the application proxy instance management module 541 stores the created application proxy instance in association with a user account (e.g., “User A” 511 of FIGS. 5 and 6) of an external application system (e.g., a user account of an external application system of the application 452 of FIG. 4). In some implementations, the application proxy instance management module 541 stores the created application proxy instance in association with an account (e.g., “Dev Account B” 531 of FIGS. 5 and 6) of the financial platform system 400 associated with an external application system (e.g., an external application system of the application 452 of FIG. 4). In some implementations, the application proxy instance management module 541 stores the created application proxy instance (e.g., “Proxy Instance User A Bank 1” 521 of FIGS. 5 and 6) in association with an account (e.g., “Dev Account B” 531) of the financial platform system 400 associated with an external application system, and a user account (e.g., “User A” 511) of the application system. In some implementations, the application proxy instance management module 541 stores the created application proxy instance in association with an account of the financial platform system 400 associated with an external application system, a user account of the application system, and information identifying the financial service system (e.g., “Bank 1 441” of FIG. 6) of the application proxy instance. In some implementations, the application proxy instance management module 541 stores the created application proxy instance in association with an account of the financial platform system 400 associated with an external application system, a user account of the application system, information identifying the financial service system of the application proxy instance, and information identifying financial accounts of the application proxy instance.
In some implementations, creating the application proxy instance includes controlling the application proxy instance management module 541 to construct the application proxy instance to simulate communication of an application (e.g., application 453 of FIG. 4) (of the external financial service system of the application proxy instance) with the financial service system on behalf of the user account (e.g., “User A”, “User B”) of the application system.
In some implementations, creating the application proxy instance includes controlling the application proxy instance management module 541 to register the created application proxy instance with the external financial service system.
In some implementations, creating the application proxy instance includes controlling the application proxy instance management module 541 to negotiate registration of the application proxy instance with the financial service system (e.g., institution) as described above for the process S110 of FIG. 1.
In some implementations, the request to create an application proxy instance is provided by an external application system (e.g., an external application system of the application 452 of FIG. 4). In some implementations, the request to create an application proxy instance is provided by an external application system (e.g., an external application system of the application 452 of FIG. 4) responsive to user input received at a user device (e.g., 471, 472) executing machine-readable instructions of an application (e.g., 452 of FIG. 4) of the application system.
4.2 Accessing Financial Data
Process S720, which includes receiving a normalized API account request for financial data, functions to control the financial platform system 400 to receive the normalized API account request by using the normalized API 410 of the financial platform system 400. In the example embodiment, the application proxy system 420 includes application proxy instances for each financial service system corresponding to the normalized API account request for financial data. Each application proxy instance is an application proxy instance that is created as described above for the process S710.
In an implementation, receiving a normalized API account request for financial data includes determining whether the application proxy system 420 includes application proxy instances for each financial service system corresponding to the normalized API account request for financial data, and responsive to a determination that the application proxy system 420 does not include an application proxy instance for a financial service system of the normalized API account request for financial data, the financial platform system 400 provides a normalized API account response to the application system that has provided the normalized API account request for financial data. The normalized API account response prompts the application system (e.g., the system of the application 452) to provide a normalized API create request to create an application proxy instance for a financial service system identified in the normalized API account response. In some implementations, the application system provides the normalized API create request to create the application proxy instance as described above for the process S710.
In some implementations, the normalized API account request is a request in accordance with the normalized financial data API (e.g., 410) of the financial platform system 400, and the normalized financial data API is constructed to provide a normalized interface for accessing financial data from external financial service systems (e.g., 441-443) having different proprietary APIs (e.g., 461-463).
4.2.1 Request Parameters
In some implementations, the normalized API account request for financial data specifies a user account (e.g., “User A”, “User B”) of an external application system (e.g., a user account of an external application system of the application 452 of FIG. 4). In some implementations, the normalized API account request for financial data specifies information identifying an account (e.g., “Dev Account A”, “Dev Account B”) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4). In some implementations, the normalized API account request for financial data specifies information identifying an external financial service system (e.g., “Bank 1”, “Bank 2”). In some implementations, the normalized API account request for financial data specifies information identifying an account of an external financial system. In some implementations, the normalized API account request for financial data specifies information identifying a transaction of an account of a financial data system. In some implementations, the normalized API account request for financial data specifies parameters. In some implementations, the financial platform system 400 accesses financial data from at least one external financial system by using the parameters. In some implementations, the financial platform system 400 processes financial data accessed from at least one external financial system by using the parameters.
4.2.2 Request for Financial Data of all Accounts
In some implementations, the normalized API account request for financial data is a request for financial data of financial accounts of all financial service systems corresponding to application proxy instances for a user account (e.g., “User A”, “User B” of FIGS. 4-6) specified in the request. For example, is a user of the user account has financial accounts at multiple financial service systems, such a request would access financial data for all the financial accounts of the user.
4.2.3 Request for Financial Data of Specified Financial Service System
In some implementations, the normalized API account request for financial data is a request for financial data of financial accounts of a financial service system (e.g., “Bank 1”, “Bank 2” of FIGS. 4-6) specified in the request.
4.2.4 Request for Financial Data of Specified Account
In some implementations, the normalized API account request for financial data is a request for financial data of an account of a financial service system, and information identifying the account (e.g., an account number) and the financial service system (e.g., “Bank 1”, “Bank 2” of FIGS. 4-6) is specified in the request.
4.2.5 Request for Details of Specified Account Transaction
In some implementations, the normalized API account request for financial data is a request for detailed financial data of an account transaction of an account of a financial service system, and information identifying the transaction (e.g., a credit card purchase, a transfer, a check entry, and the like), the account and the financial service system is specified in the request.
4.3 Negotiating Communication
Process S730, which includes negotiating communication with each external financial service system, functions to control the application proxy system 420 to use a respective application proxy instance to access the requested financial data from an external financial service system by using a proprietary API.
In some implementations, in the case of a normalized API account request for financial data of financial accounts of all financial service systems corresponding to application proxy instances for a user account (e.g., “User A”, “User B”) specified in the request, the application proxy system 420 uses application proxy instances stored by the application proxy system 420 in association with the specified user account (e.g., “User A”, “User B”, as shown in FIGS. 5 and 6).
In some implementations, in the case of a normalized API account request for financial data of financial accounts of a financial service system specified in the request, the application proxy system 420 uses application proxy instances stored by the application proxy system 420 in association with the specified user account (e.g., “User A”) and the specified financial service system (e.g., “Bank 1”).
In some implementations, in the case of a normalized API account request for financial data of an account of a financial service system, the application proxy system 420 uses application proxy instances stored by the application proxy system 420 in association with the specified user account and the specified financial service system.
In some implementations, in the case of a normalized API account request for detailed financial data of an account transaction of an account of a financial service system, the application proxy system 420 uses application proxy instances stored by the application proxy system 420 in association with the specified user account and the specified financial service system.
In some implementations, negotiating communication with a financial service system includes forming a proprietary API request in accordance with the proprietary API (e.g., 461-463 of FIG. 4) based on information specified by the normalized API account request (e.g., account information, transaction information, parameters, and the like).
As described above, the financial platform system 400 includes an institution interface module (e.g., an institution interface module 431-433 of FIG. 4) for each external financial service system (e.g., 441-443), and the institution interface module models the proprietary API (e.g., 461-463) of the external financial service system. In the example embodiment, each application proxy instance (e.g., 521-525) uses the institution interface module (e.g., 431-433 of FIG. 4) corresponding to the financial service system (e.g., 441-443) of the application proxy instance (e.g., 521-525) to access the requested financial data from the external financial service system in accordance with the proprietary API (e.g., 461-463) of the external financial service system.
In some implementations, the financial platform system 400 generates each institution interface module (e.g., 432) by at least one of: parsing source code of the application (e.g., the application 453 of FIG. 4) of the external financial service system, and parsing communication between the application (e.g., 453) and the external financial service system (e.g., 442). In some implementations, each institution interface module defines headers of messages sent to the corresponding external financial service system.
4.4 Providing Financial Data to the Application System
Process S730, which includes providing financial data to the external financial application system as a response to the normalized API account request, functions to control the application proxy system 420 to provide the financial data received by negotiating communication with each external financial service system associated with the normalized API account request.
In some implementations, providing the financial data includes transforming the received financial data into a normalized form. In some implementations, providing the financial data includes transforming the received financial data based on parameters of the normalized API account request. In some implementations, transforming the received financial data includes at least one of processing the financial data, cleaning the financial data, supplementing the financial data with additional information, and enhancing the financial data. In some implementations, additional information includes at least one of categorical labels, tags, and geo location information.
In some embodiments, the method 700 includes: setting up a session through at least one application proxy instance (e.g., one of the proxy instances 521-525 of FIG. 5) associated with the normalized request.
In some implementations, the process S710 is similar to the process S110 of FIG. 1. In some implementations, the process S720 is similar to the process S120 of FIG. 1. In some implementations, the process S730 is similar to the process S130 of FIG. 1. In some implementations, the process S740 is similar to the process S140 of FIG. 1.
5. Method for Accessing a Financial Service System
As shown in FIG. 8, a method 800 for programmatic access of at least one financial service system (e.g., 441-443 of FIG. 4) external to a financial platform system (e.g., 400 of FIG. 4) includes, responsive to a normalized API financial service request provided by an external application system (e.g., a system of the application 452 of FIG. 4) associated with an account of the financial platform system (e.g., 400): for each external financial service system corresponding to the normalized API financial service request, using an application proxy instance (e.g., 521-525 of FIG. 5) associated with the account of the financial platform system to provide a proprietary API request to the financial service system in accordance with a proprietary API (e.g., 461-463) of the financial service system (process S10); and providing a normalized API financial service response to the external application system based on at least one proprietary API response received from an external financial service system (process S820). In the example embodiment of FIG. 8, using an application proxy instance includes using an application proxy instance that is constructed to provide a proprietary API request (e.g., by using the API 462) to the respective external financial service system (e.g., 442) on behalf of a user account (e.g., “User B”) of the external application system by simulating an application (e.g., 453 of FIG. 4) of the external financial service system (e.g., 442).
In some implementations, each application proxy instance is an application proxy instance that is created as described above for the process S710 of the method 700.
In some implementations, proprietary API requests of a proprietary API (e.g., 461-463 of FIG. 4) of a financial service system include at least one of: a request for a list of transactions for at least one account of the financial service system; a request for details of a transaction associated with an account of the financial service system; a financial transfer request, a payment scheduling request; an electronic check deposit request; an account update request; a fraud reporting request; and a services request.
In some implementations, normalized API requests of the normalized API 410 of the financial platform system include at least one of: a request for a list of transactions for a user account of an external application system (e.g., a user account of an external application system of the application 452 of FIG. 4); a request for details of a transaction associated with the user account; a financial transfer request; a payment scheduling request; an electronic check deposit request; an account update request; a fraud reporting request; and a services request.
In some implementations, a primary application proxy instance and at least one secondary application proxy instance are associated with a financial service system corresponding to the normalized API financial service request, and responsive to a determination that the normalized API financial service request cannot be processed by using the primary application proxy instance, the financial platform system 400 uses the secondary application proxy instance to process the normalized API financial service request. In some implementations, the primary proxy instance corresponds to a mobile application of a respective financial service system, and the secondary proxy instance corresponds to at least one of a web-based application and a desktop application of the respective financial service system.
In some implementations, providing a normalized API financial service response to the external application system based on at least one proprietary API response received from an external financial service system (the process S820) includes transforming financial data of the proprietary API response into a normalized form. In some implementations, transforming the received financial data includes at least one of processing the financial data, cleaning the financial data, supplementing the financial data with additional information, and enhancing the financial data, and additional information includes at least one of categorical labels, tags, and geo location information. In some implementations, the received financial data is transformed as described above for S140 of FIG. 2.
In the example embodiment of FIG. 8, the method 800 is implemented by the financial platform system 400. In the example embodiment, the financial platform system is a multi-tenant financial platform system that is constructed to programmatically access at least one financial service system external to the financial platform system, as described above for the method 800.
5.1 Normalized API Financial Service Requests
In some implementations, the normalized API financial service request is provided by an external application system in a manner similar to the process of providing a normalized API account request described above for process S720 of FIG. 7.
5.1.1 Financial Data Requests
In some implementations, the normalized API financial service request is a normalized API account request for financial data, as described above for the method 700 of FIG. 7.
5.1.2 Financial Transfer Between Accounts of a Financial Service System
In some implementations, the normalized API financial service request is a financial transfer request to transfer funds between accounts of a financial service system, and the accounts are associated with user credentials of the user account (e.g., “User A”, “User B” of FIGS. 4-6) of an external application system (e.g., a user account of an external application system of the application 452 of FIG. 4). For example, a user associated with the user account can request a transfer between accounts of the user at a same financial service system by using a financial application (e.g., 452) that uses the financial platform system 400.
In some implementations, the financial transfer request to transfer funds between accounts of a financial service system specifies the user account (e.g., “User A”, “User B” of FIGS. 4-6) of the application system, the financial service system (e.g., “Bank 1”, “Bank 2”), information identifying the source account, information identifying the destination account, and an amount of funds to be transferred. In some implementations, the financial transfer request to transfer funds between accounts of a financial service system specifies parameters. In some implementations, the financial transfer request to transfer funds between accounts of a financial service system specifies an account (e.g., a developer account) (e.g., “Dev Account A”, “Dev Account B”) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified financial service system to perform the transfer. The application proxy system 420 uses the application proxy instance to perform the transfer by using an institution interface module (e.g., 431-433) of the specified financial service system to provide the financial service system with a proprietary API transfer request in accordance with the proprietary API (e.g., 461-463) of the financial service system.
5.1.3 Financial Transfer Between Accounts of a Same User and Different Financial Service Systems
In some implementations, the normalized API financial service request is a financial transfer request to transfer funds from a source account of a source financial service system to a destination account of a destination financial service system, and the source and destination accounts are associated with respective user credentials of the user account (e.g., “User A”, “User B”) of the external application system. For example, a user associated with the user account can request a transfer between accounts of the user at different financial service systems by using a financial application (e.g., 452) that uses the financial platform system 400.
In some implementations, the financial transfer request to transfer funds from a source account of a source financial service system to a destination account of a destination financial service system specifies the user account (e.g., “User A”, “User B”) of the application system, the source financial service system, information identifying the source account, the destination financial serviced system, information identifying the destination account, and an amount of funds to be transferred. In some implementations, the financial transfer request specifies parameters. In some implementations, the financial transfer request specifies an account (e.g., a developer account) (e.g., “Dev Account A”, “Dev Account B”) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses at least one of an application proxy instance stored in association with the specified user account and the specified source financial service system and an application proxy instance stored in association with the specified user account and the specified destination financial service system to perform the transfer.
In some implementations, the application proxy system 420 selects one of the application proxy instance of the specified source financial service system and the application proxy instance of the specified destination financial service system, and uses the selected application proxy instance to perform the transfer by using an institution interface module (e.g., 431-433) of the associated financial service system to provide the financial service system with a proprietary API transfer request in accordance with the proprietary API (e.g., 461-463) of the financial service system.
In some implementations, the application proxy system 420 selects one of the application proxy instance of the specified source financial service system and the application proxy instance of the specified destination financial service system based on capabilities of the respective financial service systems.
In some implementations, the application proxy system 420 selects one of the application proxy instance of the specified source financial service system and the application proxy instance of the specified destination financial service system based on properties of the application proxy instances.
In some implementations, the application proxy system 420 selects one of the application proxy instance of the specified source financial service system and the application proxy instance of the specified destination financial service system based on transaction fees of the corresponding financial service systems.
5.1.4 Financial Transfer Between Accounts of Different Users
In some implementations, the normalized financial service request is a financial transfer request to transfer funds from a source account of a source financial service system to a destination account of a destination financial service system, the source account is associated with user credentials of the user account (e.g., “User A” of FIGS. 4-6) of the external application system, and user credentials of the destination account are not associated with the user account of the external application system. For example, a user associated with the user account (e.g., “User A” of FIGS. 4-6) can initiate the transfer (to a destination account of a different user) from the source financial service system.
In some implementations, the normalized API financial transfer request specifies the user account (e.g., “User A” of FIGS. 4-6) of the application system, the source financial service system (e.g., “Bank 1”), information identifying the source account, information identifying the destination account, and an amount of funds to be transferred. In some implementations, the normalized API financial transfer request specifies parameters. In some implementations, the normalized API financial transfer request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified source financial service system to perform the transfer. The application proxy system 420 uses the application proxy instance to perform the transfer by using an institution interface module (e.g., 431-433) of the specified source financial service system to provide the source financial service system with a proprietary API transfer request in accordance with the proprietary API (e.g., 461-463) of the source financial service system.
In some implementations, the normalized API financial service request is a financial transfer request to transfer funds from a source account of a source financial service system to a destination account of a destination financial service system, the destination account is associated with user credentials of the user account of the external application system, and user credentials of the source account are not associated with the user account of the external application system. For example, a user associated with the user account (e.g., “User A” of FIGS. 4-6) can initiate the transfer (from a source account of a different user) from the destination financial service system.
In some implementations, the normalized API financial transfer request specifies the user account of the application system, the destination financial service system, information identifying the destination account, information identifying the source account, and an amount of funds to be transferred. In some implementations, the normalized API financial transfer request specifies parameters. In some implementations, the normalized API financial transfer request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified destination financial service system to perform the transfer. The application proxy system 420 uses the application proxy instance to perform the transfer by using an institution interface module (e.g., 431-433) of the destination source financial service system to provide the destination financial service system with a proprietary API transfer request in accordance with the proprietary API (e.g., 461-463) of the destination financial service system.
5.1.5 Scheduled Payments
In some implementations, the normalized API financial service request is a request to schedule payment from a source account of a source financial service system to a destination account of a destination financial service system, the source account is associated with user credentials of the user account of the external application system. For example, a user associated with the user account can schedule payment (to a destination account of a different user) from the source financial service system.
In some implementations, the normalized API schedule payment request specifies the user account of the application system, the source financial service system, information identifying the source account, information identifying the destination account, and an amount of funds to be transferred. In some implementations, the normalized API schedule payment request specifies parameters. In some implementations, the normalized API schedule payment request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified source financial service system to schedule the payment. The application proxy system 420 uses the application proxy instance to schedule the payment by using an institution interface module (e.g., 431-433) of the specified source financial service system to provide the source financial service system with a proprietary API schedule payment request in accordance with the proprietary API (e.g., 461-463) of the source financial service system.
5.1.6 Electronic Check Deposit
In some implementations, the normalized API financial service request is a request for electronic deposit of a check in a destination account of a destination financial service system, and the destination account is associated with user credentials of the user account of the external application system. For example, a user associated with the user account can electronically deposit a check (to a destination account of the user) by capturing a digital image of the check.
In some implementations, the normalized API electronic deposit request specifies the user account of the application system, the destination financial service system, information identifying the destination account, and a digital image of the check. In some implementations, the normalized API electronic deposit request specifies an amount of funds indicated by the digital image of the check. In some implementations, the normalized API electronic deposit request specifies parameters. In some implementations, the normalized API electronic deposit request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified destination financial service system to perform the electronic deposit. The application proxy system 420 uses the application proxy instance to perform the electronic deposit by using an institution interface module (e.g., 431-433) of the destination financial service system to provide the destination financial service system with a proprietary API electronic deposit request in accordance with the proprietary API (e.g., 461-463) of the destination financial service system.
5.1.7 Update Account Information
In some implementations, the normalized API financial service request is a request to update account information of a specified financial service system.
In some implementations, the normalized API update account information request specifies the user account of the application system, the financial service system, and account update information. In some implementations, the normalized API update account information request specifies information indicating an account of the specified financial service system. In some implementations, the normalized API update account information request specifies parameters. In some implementations, the normalized API update account information request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
In some implementations, the normalized API request to update account information includes a request to update contact information, and the account update information includes updated contact information.
In some implementations, the normalized API request to update account information includes a request to change a password, and the account update information includes a new password.
In some implementations, the normalized API request to update account information includes a request to update account alert settings, and the account update information includes updated account alert settings.
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified financial service system to perform the account information update. The application proxy system 420 uses the application proxy instance to perform the account information update by using an institution interface module (e.g., 431-433) of the financial service system to provide the financial service system with a proprietary API update account information request in accordance with the proprietary API (e.g., 461-463) of the financial service system. In some embodiments, the proprietary API update account information request in accordance with the proprietary API includes at least one of an update contact information request, a change password request, and an update account alert settings request.
5.1.8 Request for Services
In some implementations, the normalized API financial service request is a request for services of a specified financial service system.
In some implementations, the normalized API services request specifies the user account of the application system, the financial service system, and service request information. In some implementations, the normalized API services request specifies parameters. In some implementations, the normalized API services request specifies an account (e.g., a developer account) of the financial platform system 400 associated with the external application system (e.g., an external application system of the application 452 of FIG. 4).
In some implementations, the normalized API services request includes a request for at least one of a new bank card and a request for new checks.
In some implementations, the normalized API services request includes a request to report fraud, and the service request information includes fraud report information.
The application proxy system 420 uses an application proxy instance stored in association with the specified user account and the specified financial service system to perform the service request. The application proxy system 420 uses the application proxy instance to perform the service request by using an institution interface module (e.g., 431-433) of the financial service system to provide the financial service system with a proprietary API service request in accordance with the proprietary API (e.g., 461-463) of the financial service system. In some embodiments, the proprietary API service request in accordance with the proprietary API includes at least one of a new bank card request, check request, and a fraud report request.
6. System Architecture Financial Platform System
FIG. 9 is an architecture diagram of a system (e.g., the system 100 of FIG. 1, the financial platform system 400 of FIG. 4) according to an implementation in which the system is implemented by a server device. In some implementations, the system is implemented by a plurality of devices.
The bus 901 interfaces with the processors 901A-901N, the main memory (e.g., a random access memory (RAM)) 922, a read only memory (ROM) 904, a processor-readable storage medium 905, a display device 907, a user input device 908, and a network device 911.
The processors 901A-901N may take many forms, such as ARM processors, X86 processors, and the like.
In some implementations, the system (e.g., 400) includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).
The processors 901A-901N and the main memory 922 form a processing unit 999. In some embodiments, the processing unit includes one or more processors communicatively coupled to one or more of a RAM, ROM, and machine-readable storage medium; the one or more processors of the processing unit receive instructions stored by the one or more of a RAM, ROM, and machine-readable storage medium via a bus; and the one or more processors execute the received instructions. In some embodiments, the processing unit is an ASIC (Application-Specific Integrated Circuit). In some embodiments, the processing unit is a SoC (System-on-Chip). In some embodiments, the processing unit includes one or more of an API Service, an Application Proxy System, and one or more Instance Interface Modules.
The network adapter device 911 provides one or more wired or wireless interfaces for exchanging data and commands between the system (e.g., 400) and other devices, such as financial service systems (e.g., 441-443), user devices (e.g., 471-472). Such wired and wireless interfaces include, for example, a universal serial bus (USB) interface, Bluetooth interface, Wi-Fi interface, Ethernet interface, near field communication (NFC) interface, and the like.
Machine-executable instructions in software programs (such as an operating system, application programs, and device drivers) are loaded into the memory 922 (of the processing unit 999) from the processor-readable storage medium 905, the ROM 904 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 901A-901N (of the processing unit 999) via the bus 901, and then executed by at least one of processors 901A-901N. Data used by the software programs are also stored in the memory 922, and such data is accessed by at least one of processors 901A-901N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 905 is one of (or a combination of two or more of) a hard drive, a flash drive, a DVD, a CD, an optical disk, a floppy disk, a flash storage, a solid state drive, a ROM, an EEPROM, an electronic circuit, a semiconductor memory device, and the like. The processor-readable storage medium 905 includes an operating system 912, software programs 913, device drivers 914, the API Service 410, the Application Proxy System 420, and the Institution Interface Modules 431-433.
The system and method of the preferred embodiment and variations thereof can be embodied and/or implemented at least in part as a machine configured to receive a computer-readable medium storing computer-readable instructions. The instructions are preferably executed by computer-executable components preferably integrated with the financial data API system. The computer-readable medium can be stored on any suitable computer-readable media such as RAMs, ROMs, flash memory, EEPROMs, optical devices (CD or DVD), hard drives, floppy drives, or any suitable device. The computer-executable component is preferably a general or application specific processor, but any suitable dedicated hardware or hardware/firmware combination device can alternatively or additionally execute the instructions.
execute an Application Programming Interface (API) of the computer system, the API of the computer system configured to receive and provide responses to requests from a developer computing device according to a normalized format of the API of the computer system;
receive, via the API and according to the normalized format, a request from the developer computing device for transaction data associated with a user, the request including at least:
a username associated with the user,
a password associated with the user, and
an external institution identifier;
determine, based on the external institution identifier, an external institution associated with the request;
access an institution interface module of the computer system, wherein:
the institution interface module is uniquely configured to enable communication with an external computing device of the external institution via a non-public API of the external computing device of the external institution, and
the institution interface module is generated based on an analysis of interactions between an actual instance of a mobile device application associated with the external institution and the external computing device of the external institution; and
instantiate a virtualized instance of the mobile device application associated with the external institution, wherein:
the virtualized instance of the mobile device application is configured to communicate with the institution interface module of the computer system so as to interface with the external computing device of the external institution via the non-public API of the external computing device of the external institution,
the non-public API of the external computing device of the external institution is configured to interact with the mobile device application, and
the virtualized instance of the mobile device application is generated based on an analysis of the mobile device application;
authenticate, via the institution interface module, the virtualized instance of the mobile device application with the external computing device of the external institution based on at least one of:
an mobile device identifier code,
an mobile device authentication token, or
a mobile device Media Access Control (MAC) address;
request, by the virtualized instance of the mobile device application and via the non-public API of the external computing device of the external institution, the transaction data associated with the user from the external computing device of the external institution by:
providing the username associated with the user and the password associated with the user to the external computing device of the external institution;
receiving a request for second factor authentication information from the external computing device of the external institution;
requesting, via the API of the computer system, the second factor authentication information from the developer computing device;
receiving, via the API of the computer system, the second factor authentication information from the developer computing device;
providing the second factor authentication information to the external computing device of the external institution;
receiving, from the external computing device of the external institution, a response indicating acceptance of the second factor authentication information;
requesting the transaction information from the external computing device of the external institution; and
receiving the transaction data associated with the user from the external computing device of the external institution;
enhance the transaction data associated with the user to generate enhanced transaction data by:
augmenting, based on an analysis of the transaction data, a plurality of transaction data items of the transaction data with respective category labels;
augmenting, based on a further analysis of the transaction data, the plurality of transaction data items of the transaction data with respective geolocation information; and
standardizing a format of the transaction data such that the enhanced transaction data may be provided by the computer system in the normalized format;
provide, via the API of the computer system and in the normalized format, the enhanced transaction data to the developer computing device; and
persist, in the one or more computer readable storage devices of the computer system, the virtualized instance of the mobile device application such that future requests for transaction data associated with the user may be obtained via the virtualized instance of the mobile device application.
2. The computer system of claim 1, wherein the one or more hardware computer processors are configured to execute the plurality of computer executable instructions in order to further cause the computer system to:
further in response to the request:
determine a second external institution from which second transaction data associated with the user is to be obtained to fulfill the request;
access a second institution interface module of the computer system, wherein:
the second institution interface module is uniquely configured to enable communication with an external computing device of the second external institution via a non-public API of the external computing device of the second external institution,
the non-public API of the external computing device of the second external institution is different from the non-public API of the external computing device of the external institution, and
the second institution interface module is generated based on an analysis of interactions between an actual instance of a second mobile device application associated with the second external institution and the external computing device of the second external institution; and
instantiate a virtualized instance of the second mobile device application associated with the second external institution, wherein:
the virtualized instance of the second mobile device application is configured to communicate with the second institution interface module of the computer system so as to interface with the external computing device of the second external institution via the non-public API of the external computing device of the second external institution,
the non-public API of the external computing device of the second external institution is configured to interact with the second mobile device application, and
the virtualized instance of the second mobile device application is generated based on an analysis the second mobile device application;
authenticate, via the second institution interface module, the virtualized instance of the second mobile device application with the external computing device of the second external institution based on at least one of:
an identifier code associated with a mobile device,
an authentication token associated with a mobile device, or
a Media Access Control (MAC) address associated with a mobile device;
request, by the virtualized instance of the second mobile device application and via the non-public API of the external computing device of the second external institution, the second transaction data associated with the user from the external computing device of the second external institution by:
providing the username associated with the user and the password associated with the user to the external computing device of the second external institution;
requesting the second transaction information from the external computing device of the second external institution; and
receiving the second transaction data associated with the user from the external computing device of the second external institution;
enhance the second transaction data associated with the user to generate second enhanced transaction data by:
augmenting, based on an analysis of the second transaction data, a plurality of transaction data items of the second transaction data with respective category labels;
augmenting, based on a further analysis of the second transaction data, the plurality of transaction data items of the second transaction data with respective geolocation information; and
standardizing a format of the second transaction data such that the second enhanced transaction data may be provided by the computer system in the normalized format;
combine the enhanced transaction data and the second enhanced transaction data to generate combined enhanced transaction data;
provide, via the API of the computer system and in the normalized format, the combined enhanced transaction data to the developer computing device; and
persist, in the one or more computer readable storage devices of the computer system, the virtualized instance of the second mobile device application such that future requests for transaction data associated with the user may be obtained via the virtualized instance of the second mobile device application.
3. The computer system of claim 1, wherein the institution interface module is further generated based on at least one of: parsing source code of the mobile device application or parsing communication between the mobile device application and the external computing device of the external institution.
4. The computer system of claim 1, wherein the institution interface module defines headers of messages sent to the external computing device of the external institution.
5. The computer system of claim 1, wherein the one or more hardware computer processors are configured to execute the plurality of computer executable instructions in order to further cause the computer system to:
receive, via the API and according to the normalized format, a request from the developer computing device for at least one of: a list of transactions associated with an account of the user at the external institution, details of a transaction associated with an account of the user at the external institution, a financial transfer from or to and account of the user at the external institution, payment scheduling at the external institution, an electronic check deposit to an account of the user at the external institution, an update of an account of the user at the external institution, a fraud report at the external institution, or a service request at the external institution.
6. The computer system of claim 1, wherein, in response to receiving, from the developer computing device, a request for financial transfer from or to and account of the user at the external institution, the one or more hardware computer processors are configured to execute the plurality of computer executable instructions in order to further cause the computer system to:
request, by the virtualized instance of the mobile device application and via the non-public API of the external computing device of the external institution, a transfer from or two, based on the request for financial transfer, the account of the user at the external financial institution.
by one or more hardware computer processors executing a plurality of computer executable instructions:
executing an Application Programming Interface (API) of the computer system, the API of the computer system configured to receive and provide responses to requests from a developer computing device according to a normalized format of the API of the computer system;
receiving, via the API and according to the normalized format, a request from the developer computing device for transaction data associated with a user, the request including at least:
determining, based on the external institution identifier, an external institution associated with the request;
accessing an institution interface module of the computer system, wherein:
instantiating a virtualized instance of the mobile device application associated with the external institution, wherein:
authenticating, via the institution interface module, the virtualized instance of the mobile device application with the external computing device of the external institution based on at least one of:
requesting, by the virtualized instance of the mobile device application and via the non-public API of the external computing device of the external institution, the transaction data associated with the user from the external computing device of the external institution by:
in response to receiving a request for second factor authentication information from the external computing device of the external institution:
providing the second factor authentication information to the external computing device of the external institution; and
enhancing the transaction data associated with the user to generate enhanced transaction data by:
providing, via the API of the computer system and in the normalized format, the enhanced transaction data to the developer computing device; and
persisting, in the one or more computer readable storage devices of the computer system, the virtualized instance of the mobile device application such that future requests for transaction data associated with the user may be obtained via the virtualized instance of the mobile device application.
determining a second external institution from which second transaction data associated with the user is to be obtained to fulfill the request;
accessing a second institution interface module of the computer system, wherein:
instantiating a virtualized instance of the second mobile device application associated with the second external institution, wherein:
authenticating, via the second institution interface module, the virtualized instance of the second mobile device application with the external computing device of the second external institution based on at least one of:
requesting, by the virtualized instance of the second mobile device application and via the non-public API of the external computing device of the second external institution, the second transaction data associated with the user from the external computing device of the second external institution by:
enhancing the second transaction data associated with the user to generate second enhanced transaction data by:
combining the enhanced transaction data and the second enhanced transaction data to generate combined enhanced transaction data;
providing, via the API of the computer system and in the normalized format, the combined enhanced transaction data to the developer computing device; and
persisting, in the one or more computer readable storage devices of the computer system, the virtualized instance of the second mobile device application such that future requests for transaction data associated with the user may be obtained via the virtualized instance of the second mobile device application.
9. The computer-implemented method of claim 7, wherein the institution interface module is further generated based on at least one of: parsing source code of the mobile device application or parsing communication between the mobile device application and the external computing device of the external institution.
10. The computer-implemented method of claim 7, wherein the institution interface module defines headers of messages sent to the external computing device of the external institution.
receiving, via the API and according to the normalized format, a request from the developer computing device for at least one of: a list of transactions associated with an account of the user at the external institution, details of a transaction associated with an account of the user at the external institution, a financial transfer from or to and account of the user at the external institution, payment scheduling at the external institution, an electronic check deposit to an account of the user at the external institution, an update of an account of the user at the external institution, a fraud report at the external institution, or a service request at the external institution.
12. The computer-implemented method of claim 7 further comprising:
in response to receiving, from the developer computing device, a request for financial transfer from or to and account of the user at the external institution:
requesting, by the virtualized instance of the mobile device application and via the non-public API of the external computing device of the external institution, a transfer from or two, based on the request for financial transfer, the account of the user at the external financial institution.
13. A non-transitory computer-readable medium storing software instructions that, in response to execution by one or more hardware computer processors, configure the one or more hardware computer processors to perform operations comprising:
14. The non-transitory computer-readable medium of claim 13, wherein further in response to execution by one or more hardware computer processors, the software instructions configure the one or more hardware computer processors to perform operations comprising:
15. The non-transitory computer-readable medium of claim 13, wherein the institution interface module is further generated based on at least one of: parsing source code of the mobile device application or parsing communication between the mobile device application and the external computing device of the external institution.
16. The non-transitory computer-readable medium of claim 13, wherein the institution interface module defines headers of messages sent to the external computing device of the external institution.
17. The non-transitory computer-readable medium of claim 13, wherein further in response to execution by one or more hardware computer processors, the software instructions configure the one or more hardware computer processors to perform operations comprising:
18. The non-transitory computer-readable medium of claim 13, wherein further in response to execution by one or more hardware computer processors, the software instructions configure the one or more hardware computer processors to perform operations comprising:
US14/790,840 2014-05-21 2015-07-02 System and method for programmatically accessing financial data Active US9449346B1 (en)
US201462001452P true 2014-05-21 2014-05-21
US201514719110A true 2015-05-21 2015-05-21
US14/790,840 US9449346B1 (en) 2014-05-21 2015-07-02 System and method for programmatically accessing financial data
US201514719110A Continuation 2015-05-21 2015-05-21
US9449346B1 true US9449346B1 (en) 2016-09-20
ID=56896164
US14/790,840 Active US9449346B1 (en) 2014-05-21 2015-07-02 System and method for programmatically accessing financial data
US (1) US9449346B1 (en)
WO1996038795A1 (en) 1995-05-30 1996-12-05 Corporation For National Research Initiatives System for distributed task execution
WO1997010542A1 (en) 1995-09-15 1997-03-20 Infonautics Corporation Royalty management in an information retrieval system
EP0848336A1 (en) 1996-12-12 1998-06-17 SONY DEUTSCHLAND GmbH Server with automatic update tracking
US5966967A (en) 1998-01-22 1999-10-19 Air Products And Chemicals, Inc. Efficient process to produce oxygen
WO2000025227A1 (en) 1998-10-28 2000-05-04 Verticalone Corporation Apparatus and method for automated aggregation and delivery of electronic personal information or data
US20090070257A1 (en) 2006-09-12 2009-03-12 Daniel Csoka Systems and methods for transferring funds from a sending account
US20120278201A1 (en) 2011-04-26 2012-11-01 Dwolla Corp. Location transaction processing system
US20130282577A1 (en) 2012-04-19 2013-10-24 Benjamin P. Milne Social network transaction processing system
US8645264B2 (en) 2008-10-23 2014-02-04 Bank Of America Corporation Apparatus and methods for verifying a credit applicant's income that enhance a credit applicant's experience
US20140180962A1 (en) 2012-12-21 2014-06-26 Edward Jones & Co. System and method for income managed account
US20140258063A1 (en) * 2013-03-11 2014-09-11 Yodlee, Inc. Automated financial data aggregation
US20150066719A1 (en) 2013-08-30 2015-03-05 Yodlee, Inc. Financial Account Authentication
2015-07-02 US US14/790,840 patent/US9449346B1/en active Active
US8266515B2 (en) 1999-06-01 2012-09-11 Yodlee.Com, Inc. Categorization of summarized information
US7263548B2 (en) 1999-09-16 2007-08-28 Yodlee.Com Method and apparatus for restructuring of personalized data for transmission from a data network to connected and portable network appliances
"A Single Login Web Service Integrator-WebEntrance", Yan Zhao, Sixth International World Wide Web Conference, Santa Clara, CA, Apr. 7-11, 1997. Retrieved from <http://decweb.ethz.ch/WWW6/Posters/760/760-WEB9.htm> on Mar. 15, 2004, entire reference.
"A Single Login Web Service Integrator-WebEntrance", Yan Zhao, Sixth International World Wide Web Conference, Santa Clara, CA, Apr. 7-11, 1997. Retrieved from on Mar. 15, 2004, entire reference.
"Automatic Notification of Web Sites Changes," Google Groups, Aug. 30, 1995, entire reference. Retrieved from <http://groups.google.com/comp.infosystems.www.announce.msg/2a6c7fbb1c7162ae?hl=en &> on Sep. 29, 2005.
"Automatic Notification of Web Sites Changes," Google Groups, Aug. 30, 1995, entire reference. Retrieved from on Sep. 29, 2005.
"Boeing Chooses NetMind Enterprise Minder to Help Thousands of Employees Track Web-Based Information," PR Newswire, Nov. 19, 1998, entire reference.
"Caravelle's InfoWatcher 1.1 Keeps an Eye on the Web," PC Week, Jul. 14, 1997, entire reference.
"Cognisoft Announces IntelliServ, A Revolutionary Intranet Information Management Application; a Powerful Solution that Enables the Right Information to Find the Right User at the Right Time," Business Wire, p. 8140125, Aug. 14, 1996, entire reference.
"FirstFloor and AirMedia Announce Partnership," Business Wire, Jul. 29, 1997., entire reference.
"Fujitsu Announces Availability of ByeDesk Link for Alpha-Numeric Pagers; Next Step in Empowering Mobile Workforces with 'Anyplace, Anytime' Information," Business Wire, Jul. 9, 1998, entire reference.
"Fujitsu Announces 'WebAgent' Application as part of ByeDesk Link Wireless Server Software" Business Wire, Sep. 1, 1998, entire reference.
"Fujitsu Picks NetMind for Wireless Web Agent Software," Computergram International, Sep. 2, 1998, entire reference.
"Fujitsu's ByeDesk Link Now Available on the PalmPilot," Business Wire, Sep. 21, 1998, entire reference.
"GC Tech's GlobeID Payment Internet Commerce Software Supports Microsoft, Merchant Server," Business Wire, Jan. 21, 1997, p. 1211286.
"Minding Web Site Changes," PC Week, Sep. 14, 1998, entire reference.
"NetMind Accepts $7 Million Strategic Investment From Three Prominent VC Firms-BancBoston, Softbank and Draper Fisher Jurvestson," PR Newswire, Nov. 6, 1998, entire reference.
"NetMind Updates the World's Largest Free Web Tracking Service," PR Newswire, Sep. 18, 1998, entire reference.
"The AT&T Internet Difference Engine: Tracking and Viewing Changes on the Web," World Wide Web 1 (1); Jan. 1998, pp. 27-44.
"Versatile Intelligent Agents in Commercial Applications," Google Groups, Dec. 12, 1998, entire reference. Retrieved from <http://groups.google.com/group/aus.org.acs/msg/c20flc2913905ff?hl=en&> on Sep. 29, 2005.
"Versatile Intelligent Agents in Commercial Applications," Google Groups, Dec. 12, 1998, entire reference. Retrieved from on Sep. 29, 2005.
"Web Interface Definition Language (WIDL)", W3 Consortium submission from webMethods, Inc., Sep. 22, 1997, pp. 584-595.
"WebEntree: A Web Service Aggregator", Y. Zhao, IBM Systems Journal, vol. 37, No. 4, 1998.
A hierarchical approach to wrapper induction, Ion Muslea, Steve Minton, and Craig A. Knoblock. In Proceedings of the 3rd International Conference on Autonomous Agents 1999, Seattle, WA, 1999. May 1-5, 1999, entire reference.
Abstract in 2 pages for "Highly Scalable On-Line Payments via Task Decoupling," Financial Cryptography First International Conference, 1998, p. 355-373.
Building agents for internet-base supply chain integration, Craig A. Knoblock and Steven Minton. In Proceedings of the Workshop on Agents for Electronic Commerce and Managing the Internet-Enabled Supply Chain, Seattle, WA, 1999. May 1-5, 1999, entire reference.
Hagel et al. "The Coming Battle for Customer Information." Harvard Business Review, Jan.-Feb. 1997, reprint No. 97104.
Hummer, Waldemar, Philipp Leitner, and Schahram Dustdar. "Ws-aggregation: distributed aggregation of web services data." Proceedings of the 2011 ACM Symposium on Applied Computing. ACM, 2011. *
Intelligent caching for information mediators: A kr based approach, Naveen Ashish, Craig A. Knoblock, and Cyrus Shahabi. In Proceedings of the Workshop on Knowledge Representation meets Databases (KRDB), Seattle, WA, 1998. Presented May 1, 1998, pp. 1-7.
Johner et al. "Sign on with IBM's Global Sign-On!" IBM manual, Nov. 1998. Part 1, in 184 pages.
Johner et al. "Sign on with IBM's Global Sign-On!" IBM manual, Nov. 1998. Part 2, pp. 166-307.
Modeling web sources for information integration, Craig A. Knoblock, Steven Minton, Jose Luis Ambite, Naveen Ashish, Pragnesh Jay Modi, Ion Muslea, Andrew G. Philpot, and Sheila Tejada. In Proceedings of the Fifteenth National Conference on Artificial Intelligence, Madison, WI, 1998. Jul. 26-30, 1998, entire reference.
Optimizing Information Agents by Selectively Materializing Data, Naveen Ashish, Craig A. Knoblock, and Cyrus Shahabi. In Proceedings of the AAAI'98 Workshop on Al and Information Integration, Madison, WI, 1998. Jul. 26-30, 1998, entire reference.
Part 1 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 10 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 11 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 2 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-Lps and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-Si. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 3 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 4 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 5 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 6 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 7 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 8 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Part 9 of various documents related to MaxMiles and/or MileageManager, as obtained from Yodlee Inc. v. Plaid Technologies Inc., Civil Action No. 14-cv-01445-LPS and/or Yodlee Inc. v. Cashedge Inc., Civil Action No. 05-cv-01550-SI. To the best of Applicant's knowledge, MaxMiles and/or MileageManager were products and/or services offered around 1997 or earlier.
Semi-automatic wrapper generation for Internet information sources, Naveen Ashish and Craig A. Knoblock. In Proceedings of the Second IFCIS International Conference on Cooperative Information Systems, Kiawah Island, SC, 1997. Jun. 24-27, 1997, pp. 1-10.
The ariadne approach to web-based information integration, Craig A. Knoblock and Steven Minton. IEEE Intelligent Systems, 13(5), Sep./Oct. 1998, pp. 17-20.
U.S. Appl. No. 14/790,897, filed Jul. 2, 2015, including its ongoing prosecution history, including without limitation Office Actions, Amendments, Remarks, and any other potentially relevant documents.
U.S. Appl. No. 14/790,897, System and Method for Facilitating Programmatic Verification of Transactions, Filed Jul. 2, 2015.
WebVCR product bulletin, NetResults Corporation, 1996, entire reference.
WebVCR product documentation, NetResults Corporation. <http://www.netresultscorp.com/fs-webvcr-info.html> date retrieved Nov. 28, 2005, entire reference.
WebVCR product documentation, NetResults Corporation. date retrieved Nov. 28, 2005, entire reference.
Wrapper generation for semi-structured Internet sources, Naveen Ashish and Craig A. Knoblock. In Proceedings of the Workshop on Management of Sem istructured Data, Tucson, AZ, 1997. May 13-15, 1997, entire reference.
Wrapper induction for sem istructured, web-based information sources, Ion Muslea, Steven Minton, and Craig A. Knoblock. In Proceedings of the Conference on Automated Learning and Discovery Workshop on Learning from Text and the Web, Pittsburgh, PA, 1998. Jun. 11-13, 1998, entire reference.
US8555363B2 (en) 2013-10-08 Authenticating a user of a system using near field communication
US8935747B2 (en) 2015-01-13 Access right management system, access right management method, and access right management program
US20160125414A1 (en) 2016-05-05 Mobile wallet as a consumer of services from a service provider
US9038142B2 (en) 2015-05-19 Authorization flow initiation using short-term wireless communication
Owner name: PLAID TECHNOLOGIES, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOCKEY, WILLIAM;LI, CHARLES;PERRET, ZACH;SIGNING DATES FROM 20150528 TO 20150529;REEL/FRAME:036289/0375
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOCKEY, WILLIAM;LI, CHARLES;PERRET, ZACH;SIGNING DATES FROM 20151204 TO 20151207;REEL/FRAME:037276/0571