Patent Grant
12056702
This invention relates generally to the financial transaction field, and more specifically to a new and useful system and method for facilitating programmatic verification of transactions in the financial transaction field.
Despite various technologies and services providing various financial transaction services and tools, traditional ACH transfers remain a common mechanism for transferring funds between two accounts. Such transfers however, have numerous problems. As a first problem, the user experience requires a user to provide account number and routing number information. This is a cumbersome task for users who frequently do not know this information and may not have the proper documents to access such information. Additionally, the entering of such information is very error prone and can lead to failed transfer, which can result in financial repercussions for one if not more parties involved in the transaction. Beyond that, a common approach to verifying account ownership includes the use of micro-deposits. The micro-deposit adds significant delays to transferring funds and can additionally be a slow and confusing process for involved parties. Thus, there is a need in the financial transaction field to create a new and useful system and method for facilitating programmatic verification of transactions. This invention provides such a new and useful system and method.
The following description of preferred embodiments of the invention is not intended to limit the invention to these preferred embodiments, but rather to enable any person skilled in the art to make and use this invention.
1. Method for Facilitating Programmatic Verification of Transactions
As shown in
Block S110, which includes acquiring institution account credentials, functions to obtain login information for a financial institution (e.g., the financial institution 241 of
The account credentials are preferably provided through an API request of a developer or application account. The API is preferably used in establishing, setting up, or enrolling a new user account. One end user will preferably have at least one associated financial account, but may be linked or associated with multiple financial accounts. Account credentials are preferably obtained for each financial account.
Block S120, which includes receiving a transaction request associated with at least one endpoint, functions to initiate the retrieval of transaction addressing information of an endpoint. The endpoint is preferably a transaction endpoint, which may be any suitable endpoint from which funds may be withdrawn or deposited. In a common transaction, there is a single withdrawal account and a single deposit account. The method can be used in obtaining information for one or more endpoints. In some variations, there may be a plurality of withdrawal and/or deposit accounts. In one variation, the transaction request is identical to an enroll user request used to obtain the user credentials of block S110. The account credentials may alternatively be previously obtained or obtained in response to the transaction request.
In one variation, the transaction request is for information about an account, the API request preferably specifies an institution and account credentials. Additional credentials may additionally be required such as a pin code, state in which an account was created, or MFA challenge answers. A second request with similar parameters may be submitted to obtain the account credentials for other involved transaction endpoints.
In another variation, the transaction request may explicitly define the transaction details. The transaction request preferably includes at least one withdrawal account endpoint and deposit account endpoint. Account credentials are preferably specified for each endpoint. In one variation, a single API request may include account credentials for both endpoints. In another variation, a transaction resource is used, such that withdrawal endpoint information, deposit account information, and transaction details can be specified asynchronous. For example, a transaction resource is created through an API request. Later, an API request hits the new transaction resource (by specifying a transaction identifier) to specify withdrawal information, then deposit information, and then the amount to be transferred. Once all the information is populated, the transaction may be executed either automatically, in response to an executed command, or scheduled for a later time. Bulk, aggregate, or group transactions may additionally be specified in a request. If multiple entities are withdrawal endpoints, then the division of funds may be specified (e.g., a percentage breakdown or amount break down). Similarly, funds for multiple deposit endpoints may be specified.
Block S130, which includes collecting transaction information of the endpoint, functions to access and determine properties of a transaction endpoint. Collecting transaction information of the endpoint preferably involves using the account credentials to gain account access in a financial institution. Preferably, the account access is facilitated by using a proxy application, which simulates an application accessing the system of an external institution such as in the system and method described in U.S. Provisional Application No. 62/001,452, filed on 21 May 2014, which is hereby incorporated in its entirety by this reference. The proxy application preferably appears as a first party application instance of the institution, but is actually programmatically controlled communication of the system. The headers, body, encryption, communication protocol negotiation are preferably configured to approximate application communication. The account access can be used to request and obtain account documents that include endpoint information. The account documents may include bank statements or other suitable documents. If the documents are in pdf or other alternative formats, the content is preferably scraped to identify transaction information.
Block S130, which includes collecting transaction information of the endpoint, preferably includes collecting transaction addressing information of the endpoint. The account addressing information is preferably the account number and the routing number of an account. Billing address, wire routing number, and/or other account information can additionally be pulled. In one variation, the account number and routing number are available in banking statements. An extraction script may be used to pull the document and then isolate the information from the document. Accessing the account number and the routing number in an automated fashion preferably avoids chances of error. As a first benefit, access to the account provides evidence of that the owner of the account participated in providing the transaction endpoint information. As another benefit, the information is automatically pulled, which avoids human error.
Collecting transaction information of the endpoint S130 may additionally include collecting transaction status information of the endpoint, which can include indication of fund requirements, account fraud checks, and other status information. Various stages can be built into providing the transaction information, which provide different safeguards and/or features into financial transactions.
In a first optional stage, the transaction status information can determine a sufficient funds status. The sufficient funds status is preferably applied to a withdrawal account to ensure that the account has funds to complete the transaction. Transaction history and/or current fund value may be accessed through the account access. In one variation, the fund amount is returned in the response such that the developer/application can respond appropriately. In another variation, the transaction amount is compared to available funds. If sufficient funds are not found, then an error or warning may be raised.
In another optional stage, the account may be processed for fraud patterns. For example, the age of the account may be accessed. Newly created accounts may be less trustworthy than established accounts with significant history. Similarly transaction history may be assessed for fraudulent behavior. If the account is used for a diverse range of transactions indicative of normal behavior then the account may be identified as normal. If the account only participates in repeated high value transactions or other fraud patterns, then the account may be flagged as fraudulent. Additionally, the entities involved in the transaction may be indicative of fraud.
The method may additionally include verifying transaction conditions during one or more stage. Transaction conditions may be used to take any suitable action. The available actions can include permitting a transaction or preventing a transaction. Additionally, the action can include sending a notification. The notification can include an email, text message, a platform message, a phone call, or any suitable notification. The action may additionally include triggering a programmatic event. In one variation the programmatic event is a callback event, wherein and HTTP message is sent to a destination. Conditions may be customized or selected from a set of provided conditions. Exemplary conditions can include a condition that triggers a notification for transactions over a particular amount; a condition based on available funds after the transaction to alert a user to funds below a threshold; and a condition based on the frequency of transactions or the entities involved in the transaction account. Conditions can be scoped for a developer account, a particular institution account, or for any suitable scope of entities.
Block S140, which includes returning a transaction response functions to transmit the results of the transaction request. The transaction response is preferably made in a synchronous API message that is sent in response to an initial request. Alternatively, a status API resource may be used such that an application/service can periodically check the status API resource to determine the processing status and/or the results. Alternatively, any suitable approach may be used to provide the results to the initial request.
In one preferred implementation, the response provides the addressing information used for a financial endpoint. If there are no errors or warnings with respect to the account, then account information is preferably NACHA compliant as the financial endpoint information was accessed and obtained in a manner that validates the ownership of the account (e.g., by providing credentials and optionally multi-factor authentication responses). The transaction response can include the account number, the routing number, and/or any additional information for the endpoint that is used in executing the transaction. The transaction response may additionally include the available funds, such that the requesting entity can check for sufficient funds. The response may additionally indicate if sufficient funds are available if the transaction amount was provided, which functions to hide the available funds from the requesting entity while preventing overdraft transaction. The transaction response can additionally include other fields such as a status field, where the account may be labeled according to any categorization of the account. For example, the status may indicate that the account is normal or fraudulent.
Additionally or alternatively, the method can include executing the transaction S150, which functions process the transaction between two endpoints. In this variation a request to execute a transaction between at least two endpoints is received. Additionally, returning a transaction response may include returning results of the transaction in the response. In another preferred implementation, the method includes executing the transaction. The transaction response can include information about the status of the transaction when the transaction is submitted, being processed, and/or completed. Transactions may not be instantaneous, and as such the initial transaction response may indicate if the transaction was successfully initiated. Successfully initiated means that the transaction endpoint information was successfully retrieved, that any conditional stages (such as a sufficient funds stage, a fraud-check stage, and custom conditions) are satisfied. A subsequent response or status resource may be updated that reflects the status of the transaction. A transaction resource may be updated with a pending process, when the transaction is initiated and proceeding normally. The transaction resource can be updated with a completed status possibly indicating the time of completion. If an error or issue is encountered, the status of the transaction resource may be updated to reflect the error or issue. The method may additionally include monitoring status of transaction and triggering programmatic event according to the status.
In one variation, executing the transaction can include establishing proxy accounts in at least two institutions, and expediting transactions between the two institutions through a an internal deposit to a first proxy account in a first institution and a second internal deposit from a second proxy account in the second institution. In some cases, transactions between institutions are slower than transactions made within an institution. By establishing cross institution account network, transactions can be facilitated between two accounts in different institutions with similar speeds of internal transactions. The proxy accounts preferably include a funds reserve, which may be periodically balanced between proxy accounts to maintain an operational reserve of funds.
Additionally, the method may be applied to create an abstraction between a user and the underlying account. A transaction endpoint can be abstracted to a user entity, which may be associated with multiple optional transactional endpoints (e.g., different bank accounts). Accordingly, the method may include selecting a financial institution, which functions to dynamically select a connected financial account to participate in a transaction. Various conditions may be set to respond to events when receiving a transaction request, collecting information for the transaction, and/or executing a transaction. In one variation, one financial institution is set as a primary account and another account managed by the same entity is set as a secondary account. If the primary account is not able to complete a transaction, the method preferably detects an error condition and automatically fails over to the secondary account. In another variation, a set of accounts may be preconfigured to be used depending on properties of the request. In combination with the proxy transfer endpoint, the identifying information for the proxy endpoint can be used, but the underlying service automatically will use an automatically selected financial account to use for the funds. For example, a set of entities and/or category of entities/transactions may be set to use particular accounts. Similarly, transactions to one proxy account may be automatically split into transactions with multiple associated accounts. For example, an account holder may set a proxy account to automatically split deposits between two accounts in a 30/70 balance.
2. System for Facilitating Programmatic Verification of Transactions
As shown in
The API service 210 functions to provide an interface for accessing financial institution transaction endpoint information. The API service 210 can additionally provide normalized customer/user facing interface. In one preferred implementation the API service 210 can be substantially similar to the API service and system described in U.S. Provisional Application No. 62/001,452, incorporated above. Preferably the API service 210 leverages an application proxy instance 221, which simulates a proprietary native application accessing a closed API of a financial institution (e.g., the financial institution 241 of
The API service 210 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 communication platform 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 210 can include various resources, which act as mechanisms 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. Alternative implementations may use an internal interface and provide a user-facing interface such as a graphical user interface in a web application or native application.
In one variation, the API service 210 allows an API request to specify an account, and a response output provides the information related to executing a transaction with the endpoint. In one exemplary implementation, the API service 210 can include at least one API resource for interacting with transaction endpoint. As shown in
An institution interface module (institution integration system) (e.g., 231 of
The system 200 may additionally include a transaction engine 291, which can facilitate the transfer of funds between two accounts. The transaction engine 291 can be integrated with the API service 210, such that an API request can direct the execution of a transaction. The transaction engine 291 preferably can execute ACH transactions, but may alternatively or additionally use other financial tools to withdrawal funds and/or deposit funds. With a transaction engine, transactions can be executed between two accounts that have been configured with account credentials, the API response may include the status of the transaction, transaction errors, a status URI or any suitable response to facilitate executing a transaction as shown in
The system 200 can additionally include other components such as a messaging/notification system, which can manage alerts and/or triggering programmatic events (e.g., callbacks). The system 200 may additionally or alternatively include any suitable components
3. Financial Platform System
As shown in
In some implementations, the financial platform system 500 includes a transaction engine 521. In some implementations, the transaction engine 521 is similar to the transaction engine 291 of
In some implementations, the financial platform system 500 includes a document processing engine 522. In some implementations, the document processing engine 522 is constructed to process financial documents (e.g., the financial documents 592) of a financial institution system (e.g., 542) of a user account of the financial institution system to identify transaction information. In some implementations, in a case where the financial documents are in a PDF format, the document processing engine 522 is constructed to scrape content of the PDF financial documents to identify the transaction information. In some implementations, the document processing engine 521 is an extraction script that is constructed to pull the financial document and then isolate the transaction information from the document (e.g., as described above for block S130 of
As shown in
As shown in
In some implementations, each application proxy instance (e.g., proxy instances 621-625) specifies the developer account, the user account of the developer account, the associated financial institution system, and credentials of the user account for the financial institution system, as shown in
In some implementations, each proprietary API (e.g., 561-563) is different from a web browser interface (e.g., 591) used by a web browser (e.g., 581).
3.1 Multi-Tenant Financial Platform System
As shown in
3.2 Single-Tenant Financial Platform System
In some implementations, the financial platform system is a single-tenant financial platform system, and the financial applications are included in a financial application system of the financial platform system 500. Each application proxy instance is constructed to provide a proprietary financial API request to the respective external financial institution system on behalf of a user of the application system (of the financial platform system) by simulating an application of the external financial institution system.
As shown in
In some implementations, the collected transaction information for each financial account endpoint includes at least an account number and a corresponding routing number for use in automated clearing house (ACH) transactions.
In some implementations, the transaction information is collected by processing at least one financial statement accessed from the corresponding external financial institution system.
In some implementations, the financial platform system includes an institution interface module (e.g., 531-533 of
In some implementations, the financial platform system generates each institution interface module (e.g., 531-533 of
In some implementations, each institution interface module defines headers of messages sent to the associated external financial institution system.
In the example embodiment of
4.1 Normalized Financial API Request
The process S810, which includes receiving a normalized financial API request associated with at least one financial account endpoint, functions to control the financial platform system 500 to receive the normalized financial API by using the API 510 of the financial platform system 500. In the embodiment of
In some implementations, the normalized financial API request is received as described above for the process S120 of
4.2 Collecting Transaction Information
The process S820, which includes collecting transaction information of each financial account endpoint of the normalized financial API request, is performed responsive to the normalized financial API request. The process S820 functions to control the financial platform system 500 to use an application proxy instance associated with a financial account endpoint (of the normalized API request) to collect the transaction information from a corresponding financial institution system. The application proxy instance collects the transaction information by using the associated account credentials specified by the normalized financial API request and a proprietary API (e.g., one of the proprietary APIs 561-563 of
In the example embodiment, the application proxy system 520 includes application proxy instances for each financial institution system corresponding to the normalized financial API request.
In some implementations, the transaction information is collected as described above for the process S130 of
In some implementations, the financial platform system 500 collects the transaction information by using an application proxy instance (e.g., 623 of
4.2 Generation of an Application Proxy Instance
In the example embodiment of
In some implementations, the application proxy instance management module 641 generates the application proxy instance responsive to a request to generate an application proxy instance. In some implementations, the request to generate an application proxy instance specifies information identifying an external financial institution system, and a user account of an application system (e.g., a user account of an application system of the application 552 of
In some implementations, the application proxy instance management module 641 stores the generated application proxy instance in association with a user account of an application system (e.g., a user account of an application system of the application 552 of
In some implementations, generating the application proxy instance includes controlling the application proxy instance management module 641 to construct the application proxy instance to simulate communication of an application (e.g., application 553 of
In some implementations, generating the application proxy instance includes controlling the application proxy instance management module 641 to register the generated application proxy instance with the external financial institution system.
In some implementations, generating the application proxy instance includes controlling the application proxy instance management module 641 to negotiate registration of the application proxy instance with the financial institution system.
In some implementations, the request to generate an application proxy instance is provided by an application system (e.g., an external application system of the application 552 of
4.4 Providing Transaction Information
The process S830, which includes providing a normalized financial API response to the external financial application system, is performed responsive to the normalized financial API request. The process S830 functions to control the financial platform system 500 to provide the normalized financial API response, which includes the transaction information of each financial account endpoint of the normalized financial API request.
In some implementations, the transaction information is provided as described above for the process S140 of
As shown in
Responsive to the normalized financial API request, transaction information of each financial account endpoint of the normalized financial API request is collected (process S920). The transaction information is collected by using an application proxy instance associated with the financial account endpoint to collect the transaction information from a corresponding financial institution system by using at least one of an associated account token and associated account credentials specified by the normalized financial API request and by using a proprietary API of the financial institution system. The transaction specified by the normalized financial API request is executed by using the collected transaction information (process S930). A normalized financial API response is provided to the external system (process S940). The normalized financial API response provides results of the transaction. Each application proxy instance is constructed to simulate an application of the corresponding external financial institution system.
In some implementations, the collected transaction information for each financial account endpoint includes at least an account number and a corresponding routing number for use in automated clearing house (ACH) transactions.
In some implementations, the transaction information is collected by processing at least one financial statement accessed from the corresponding external financial institution system.
In some implementations, the financial platform system includes an institution interface module (e.g., 531-533 of
In some implementations, the financial platform system generates each institution interface module (e.g., 531-533 of
In some implementations, each institution interface module defines headers of messages sent to the associated external financial institution system.
In some implementations, the normalized financial API request is received as described above for the process S810 of
In the example embodiment of
The process S1010 includes using at least one application proxy instance (e.g., 621-625) associated with the normalized API request to collect transaction information from a corresponding financial institution system by providing the financial institution system with a proprietary financial API request that specifies at least account credentials associated with the user information specified by the normalized financial API request. The transaction information is included in at least one proprietary financial API response provided by the financial institution system.
The process S1020 includes generating a normalized financial API response based on the collected transaction information. The process S1030 includes providing the normalized financial API response to the financial application system.
Each application proxy instance is constructed to simulate an application (e.g., 553 of
In some implementations, each proprietary API (e.g., 561-563) is a private API of the respective financial institution system, and each proprietary API is different from a web browser interface (e.g., 591 of
In some implementations, the normalized financial API request is provided on behalf of a user account of the financial application system (e.g., the application system of the application 552 of
In some implementations, the normalized financial API request is provided on behalf of a user account of the financial application system, and the specified user information includes information associated with a user that is different from a user of the user account of the financial application system.
In some implementations, the normalized financial API request is a request for financial account endpoint information, and each proprietary financial API request is a request for financial account endpoint information, and wherein the transaction information includes financial account endpoint information.
In some implementations, the normalized financial API request is a request to transfer funds from at least one withdrawal account endpoint to at least one deposit account endpoint and the normalized financial API request specifies an amount of funds to be transferred.
In some implementations, the collected transaction information for each financial account endpoint includes at least an account number and a corresponding routing number for use in automated clearing house (ACH) transactions.
In some implementations, the transaction information is collected by processing at least one financial statement accessed from the corresponding external financial institution system.
In some implementations, the financial platform system includes an institution interface module (e.g., 531-533 of
In some implementations, the financial platform system generates each institution interface module (e.g., 531-533 of
In some implementations, each institution interface module defines headers of messages sent to the associated external financial institution system.
In some implementations, the normalized financial API request is received as described above for the process S810 of
In the example embodiment of
6.1 Collecting Transaction Information
The process S1010, which includes using at least one application proxy instance associated with the normalized API request to collect transaction information from a corresponding financial institution system, functions to control the financial platform system 500 to use at least one application proxy instance (e.g., 623) associated with the normalized API request to collect transaction information from a corresponding financial institution system (e.g., 542) by providing the financial institution system with a proprietary financial API request that specifies at least account credentials associated with the user information specified by the normalized financial API request. The transaction information is included in at least one proprietary financial API response provided by the financial institution system (e.g., 542).
In some implementations, each proprietary financial API response provides a financial document (e.g., one of the financial documents 592) of a user corresponding to the account credentials of the associated proprietary financial API request, and each financial document includes the requested transaction information. The financial platform system 500 stores the financial documents of each proprietary financial API response (e.g., in a memory 1122 of
In some implementations, the financial platform system 500 determines application proxy instances (e.g., 621-625) associated with the normalized financial API request. In some implementations, the financial platform system 500 determines application proxy instances (e.g., 621-625) associated with the normalized financial API request by using the application proxy system 520.
In some implementations, the financial platform system 500 determines application proxy instances (e.g., 621-625) associated with the normalized financial API request based on the user information specified by the normalized financial API request.
6.2 Generating a Normalized Financial API Response
The process S1020, which includes generating a normalized financial API response based on the collected transaction information, functions to control the financial platform system 500 to generate a normalized financial API response to the normalized financial API request. In some implementations, the financial platform system 500 generates the normalized financial API response to include the transaction information collected from each proprietary financial API response provided by an external financial institution system. In some implementations, the financial platform system 500 generates the normalized financial API response based on parameters included in the normalized financial API request. In some implementations, the financial platform system 500 generates the normalized financial API response based on properties of the application proxy instances used to collect the transaction information.
In some implementations, in a case where the normalized financial API request is a request to transfer funds from at least one withdrawal account endpoint to at least one deposit account endpoint, the process S1020 includes using a transaction engine (e.g., 521 of
In some implementations, in a case where the normalized financial API request is a request to transfer funds from at least one withdrawal account endpoint to at least one deposit account endpoint, the transaction information collected from each proprietary financial API response provided by an external financial institution system corresponds to financial account endpoint information of each withdrawal account endpoint and deposit account endpoint of the normalized financial API request. The application platform system uses the transaction engine 521 to perform the transfer of funds from each withdrawal account endpoint to each respective deposit account endpoint by using the collected financial account endpoint information. The financial platform system 500 generates the normalized financial API response to include at least one of a status of the transfer and results of the requested transfer of funds.
6.3 Providing a Normalized Financial API Response
In some implementations, the process S1030, which includes providing the normalized financial API response to the financial application system, functions to control the financial platform system 500 to provide the normalized financial API response by using the API 510. In some implementations, the financial platform system 500 provides the normalized financial API response as described above for
6.4 Request for Transaction Information
In some implementations, the normalized financial API request is a request for transaction information. In some implementations, the normalized financial API request is a request for transaction information for one user for one external financial intuition. In some implementations, the normalized financial API request is a request for transaction information for one user for more than one external financial intuition. In some implementations, the normalized financial API request is a request for transaction information for more than one user for one or more respective external financial intuitions.
6.4.1 Request for Transaction Information for a User Identified by a User Account Identifier
In some implementations, the user information of the normalized financial API request includes a user account identifier for each user account of the application system (e.g., the application system of the financial application 552 of
In some implementations, the normalized financial API request includes parameters as shown in Table 1.
In some implementations, the <User Account Identifier> is used to select at least one corresponding application proxy instance (e.g., 621-625), and each selected application proxy instance includes user credentials (e.g., as depicted in
In some implementations, the financial platform system 500 determines an application proxy instance (e.g., 621-625) associated with the normalized API request based on the <Financial Platform Account ID> parameter, the <User Account Identifier> parameter, and the <Financial Institution ID> parameter. In some implementations, the financial platform system 500 identifies an application proxy instance of the application proxy system 520 that is managed in association with the <Financial Platform Account ID> parameter, the <User Account Identifier> parameter, and the <Financial Institution ID> parameter, and uses the identified application proxy instance to collect the transaction information.
For example, in a case where the application proxy system 520 manages application proxy instances 621-625 as shown in
In some implementations, each proprietary financial API request includes parameters as shown in Table 2.
6.4.2 Request for Transaction Information for a User Identified by User Credentials
In some implementations, the user information of the normalized financial API request includes at least one set of user credentials for each user account of the application system (e.g., the application system of the financial application 552 of
In some implementations, the normalized financial API request includes parameters as shown in Table 3.
In some implementations, the financial platform system 500 determines an application proxy instance (e.g., 621-625) associated with the normalized API request based on the <Financial Platform Account ID> parameter and the <Financial Institution ID> parameter. In some implementations, the financial platform system 500 identifies an application proxy instance of the application proxy system 520 that is managed in association with the <Financial Platform Account ID> parameter and the <Financial Institution ID> parameter, and uses the identified application proxy instance to collect the transaction information.
In some implementations in which the normalized financial API request includes at least one set of user credentials, rather than using an application proxy instance, the financial platform system 500 identifies an institution interface module (e.g., 531-533) of the financial institution system identified by the <Financial Institution ID> parameter, and uses the identified institution interface module to collect the transaction information.
In some implementations, each proprietary financial API request includes parameters as shown in Table 4.
6.4.3 Request for Transaction Information for a User Identified by a User Account Token
In some implementations, the user information of the normalized financial API request includes a user account token for each user account of the application system (e.g., the application system of the financial application 552 of
In some implementations, the normalized financial API request includes parameters as shown in Table 5.
In some implementations, each application proxy instance is stored in association with a respective user account token. In some implementations, each application proxy instance is stored in association with information that identifies a respective user account token. In some implementations, each account token is stored at the financial platform system 500 in association with a user account identifier.
In some implementations, the <User Account Token> is used to select at least one corresponding application proxy instance (e.g., 621-625), and each selected application proxy instance includes user credentials (e.g., as depicted in
In some implementations, the financial platform system 500 determines an application proxy instance (e.g., 621-625) associated with the normalized API request based on the <Financial Platform Account ID> parameter, the <User Account Token> parameter, and the <Financial Institution ID> parameter. In some implementations, the financial platform system 500 identifies an application proxy instance of the application proxy system 520 that is managed in association with the <Financial Platform Account ID> parameter, the <User Account Token> parameter, and the <Financial Institution ID> parameter, and uses the identified application proxy instance to collect the transaction information.
In some implementations, the financial platform system 500 determines a user account identifier associated with the user account token, and identifies an application proxy instance of the application proxy system 520 that is managed in association with the <Financial Platform Account ID> parameter, the determined user account identifier, and the <Financial Institution ID> parameter, and uses the identified application proxy instance to collect the transaction information.
For example, in a case where the application proxy system 520 manages application proxy instances 621-625 as shown in
In some implementations, each proprietary financial API request includes parameters as shown in Table 6.
6.5 Request To Transfer Funds
In some implementations, the normalized financial API request is a request to transfer funds from at least one withdrawal account endpoint to at least one deposit account endpoint. In some implementations, each endpoint is identified by user information specified by the normalized financial API transfer request. In some implementations, user information for an endpoint includes at least one of a user account identifier, a user account token, and user credentials. In some implementations, one or more endpoints are identified by financial account endpoint information (e.g., an account number and corresponding routing number) specified by the normalized financial API transfer request and one or more endpoints are identified by user information specified by the normalized financial API transfer request. In some implementations, the normalized financial API request specifies an amount of funds to be transferred. In some implementations, the normalized financial API request specifies an originating financial institution system that initiates the transfer of funds.
In some implementations, the financial platform system 500 processes a normalized financial API request to transfer funds by determining withdrawal account endpoints and deposit account endpoints specified by the normalized financial API request to transfer funds. For each endpoint identified by user information of the normalized financial API request, the financial platform system 500 collects transaction information as described above for processes S130 of
In some implementations, in a case where more than one withdrawal account endpoint is specified by the normalized financial API transfer request, the financial platform system 500 selects one or more of the withdrawal account endpoints for the transfer based on at least one of capabilities of the withdrawal account endpoints, availability of the withdrawal account endpoints, configuration for the withdrawal account endpoints, and parameters of the normalized financial API request.
In some implementations, in a case where more than one deposit account endpoint is specified by the normalized financial API transfer request, the financial platform system 500 selects one or more of the deposit account endpoints for the transfer based on at least one of capabilities of the deposit account endpoints, availability of the deposit account endpoints, configuration for the deposit account endpoints, and parameters of the normalized financial API request.
In some implementations, in a case where a user (identified by a user account identifier, a user account token, or a set of user credentials) specified by the normalized financial API transfer request is associated with multiple account endpoints (e.g., a user has accounts at different financial institution systems, or multiple accounts at one financial institution system), the financial platform system 500 selects one or more of the endpoints associated with the user for the transfer based on at least one of capabilities of the account endpoints, availability of the account endpoints, configuration for the account endpoints, and parameters of the normalized financial API request.
In some implementations, one endpoint of a user is configured as a primary account and another account of the user is configured as a secondary account. In a case where the transaction engine 521 cannot complete the transfer by using the primary account, the transaction engine 521 selects the secondary account for use in execution of the transfer.
In some implementations, a set of accounts may be preconfigured to be used depending on properties of the normalized financial API transfer request. In some implementations, the normalized financial API transfer request specifies user information that identifies a proxy transfer endpoint, and the financial platform system 500 automatically selects a financial account to use for the transfer of funds based on configuration information of the proxy transfer endpoint.
In some implementations, during processing of a normalized financial API transfer request that specifies a proxy transfer endpoint, the financial platform system 500 automatically splits the requested transaction into multiple sub-transactions by using multiple accounts associated with the proxy transfer endpoint, in accordance with configuration for the proxy transfer endpoint. For example, an account holder may set a proxy transfer endpoint to automatically split deposits between two accounts in a 30/70 balance.
6.5.1 Request To Transfer Funds By using Proxy Accounts
In some implementations, the transaction engine 522 executes the transfer by establishing proxy accounts in at least two institutions, and expedites transactions between the two institutions through a an internal deposit to a first proxy account in a first institution and a second internal deposit from a second proxy account in the second institution. In some implementations, the proxy accounts include a funds reserve, which may be periodically balanced between proxy accounts to maintain an operational reserve of funds.
7. System Architecture: Financial Platform System
The bus 1101 interfaces with the processors 1101A-1101N, the main memory (e.g., a random access memory (RAM)) 1122, a read only memory (ROM) 1104, a processor-readable storage medium 1105, a display device 1107, a user input device 1108, and a network device 1111.
The processors 1101A-1101N may take many forms, such as ARM processors, X86 processors, and the like.
In some implementations, the system (e.g., 500) includes at least one of a central processing unit (processor) and a multi-processor unit (MPU).
The processors 1101A-1101N and the main memory 1122 form a processing unit 1199. 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, one or more instance interface modules, financial documents, a transaction engine, and a document processing engine.
The network adapter device 1111 provides one or more wired or wireless interfaces for exchanging data and commands between the system (e.g., 500) and other devices, such as financial institution systems (e.g., 541-543), user devices (e.g., 571-572). 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 1122 (of the processing unit 1199) from the processor-readable storage medium 1105, the ROM 1104 or any other storage location. During execution of these software programs, the respective machine-executable instructions are accessed by at least one of processors 1101A-1101N (of the processing unit 1199) via the bus 1101, and then executed by at least one of processors 1101A-1101N. Data used by the software programs are also stored in the memory 1122, and such data is accessed by at least one of processors 1101A-1101N during execution of the machine-executable instructions of the software programs. The processor-readable storage medium 1105 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 1105 includes an operating system 1112, software programs 1113, device drivers 1114, the API Service 510, the application proxy system 520, the institution Interface modules 531-533, and financial documents 1101. In some implementations, the processor-readable storage medium 1105 includes the transaction engine 521 and the document processing engine 522.
8. Machines
The system and methods 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 application programming interface platform. 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.
As a person skilled in the art will recognize from the previous detailed description and from the figures and claims, modifications and changes can be made to the preferred embodiments of the invention without departing from the scope of this invention defined in the following claims.
This application is a continuation of U.S. patent application Ser. No. 16/800,543, filed 25 Feb. 2020, which is a continuation of U.S. patent application Ser. No. 15/455,959, filed 10 Mar. 2017, which application is a continuation of U.S. patent application Ser. No. 14/790,897, filed 2 Jul. 2015, which application is a continuation of U.S. patent application Ser. No. 14/719,117, filed 21 May 2015, which claims the benefit of U.S. Provisional Application Ser. No. 62/001,461, filed on 21 May 2014, the entire content of each of which is hereby incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5063507 | Lindsey et al. | Nov 1991 | A |
| 5237499 | Garback | Aug 1993 | A |
| 5347632 | Filepp | Sep 1994 | A |
| 5634127 | Cloud | May 1997 | A |
| 5649186 | Ferguson | Jul 1997 | A |
| 5701451 | Rogers | Dec 1997 | A |
| 5710884 | Dedrick | Jan 1998 | A |
| 5710918 | Lagarde | Jan 1998 | A |
| 5721908 | Lagarde | Feb 1998 | A |
| 5727159 | Kikinis | Mar 1998 | A |
| 5745754 | Lagarde | Apr 1998 | A |
| 5752246 | Rogers | May 1998 | A |
| 5778065 | Hauser et al. | Jul 1998 | A |
| 5778367 | Wesinger, Jr. et al. | Jul 1998 | A |
| 5787403 | Randle | Jul 1998 | A |
| 5793964 | Rogers | Aug 1998 | A |
| 5813007 | Nielsen | Sep 1998 | A |
| 5815665 | Teper | Sep 1998 | A |
| 5819284 | Farber | Oct 1998 | A |
| 5835724 | Smith | Nov 1998 | A |
| 5838910 | Domenikos et al. | Nov 1998 | A |
| 5838916 | Domenikos et al. | Nov 1998 | A |
| 5845073 | Carlin | Dec 1998 | A |
| 5855018 | Chor et al. | Dec 1998 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5870559 | Leshem et al. | Feb 1999 | A |
| 5875296 | Shi | Feb 1999 | A |
| 5878219 | Vance | Mar 1999 | A |
| 5892905 | Brandt et al. | Apr 1999 | A |
| 5892909 | Grasso | Apr 1999 | A |
| 5898836 | Freivald | Apr 1999 | A |
| 5901287 | Bull | May 1999 | A |
| 5903881 | Schrader | May 1999 | A |
| 5908469 | Botz | Jun 1999 | A |
| 5913214 | Madnick | Jun 1999 | A |
| 5918216 | Miksovsky et al. | Jun 1999 | A |
| 5920848 | Schutzer | Jul 1999 | A |
| 5926798 | Carter | Jul 1999 | A |
| 5930764 | Melchione et al. | Jul 1999 | A |
| 5930777 | Barber | Jul 1999 | A |
| 5933604 | Inakoshi | Aug 1999 | A |
| 5933816 | Zeanah | Aug 1999 | A |
| 5956720 | Fernandez et al. | Sep 1999 | A |
| 5961593 | Gabber et al. | Oct 1999 | A |
| 5961601 | Iyengar | Oct 1999 | A |
| 5963915 | Kirsch | Oct 1999 | A |
| 5963925 | Kolling | Oct 1999 | A |
| 5966967 | Agrawal | Oct 1999 | A |
| 5978828 | Greer | Nov 1999 | A |
| 5978842 | Noble | Nov 1999 | A |
| 5983267 | Shklar et al. | Nov 1999 | A |
| 5983268 | Freivald | Nov 1999 | A |
| 5987440 | O'Neil | Nov 1999 | A |
| 5987454 | Hobbs | Nov 1999 | A |
| 5995943 | Bull | Nov 1999 | A |
| 5999971 | Buckland | Dec 1999 | A |
| 6003032 | Bunney et al. | Dec 1999 | A |
| 6006333 | Nielsen | Dec 1999 | A |
| 6023698 | Lavey | Feb 2000 | A |
| 6041362 | Mears et al. | Mar 2000 | A |
| 6047327 | Tso et al. | Apr 2000 | A |
| 6055570 | Nielsen | Apr 2000 | A |
| 6078929 | Rao | Jun 2000 | A |
| 6082776 | Feinberg | Jul 2000 | A |
| 6092196 | Reiche | Jul 2000 | A |
| 6092197 | Coueignoux | Jul 2000 | A |
| 6105131 | Carroll | Aug 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6138158 | Boyle | Oct 2000 | A |
| 6148337 | Estberg et al. | Nov 2000 | A |
| 6151581 | Kraftson et al. | Nov 2000 | A |
| 6151601 | Papierniak | Nov 2000 | A |
| 6182142 | Win | Jan 2001 | B1 |
| 6185567 | Ratnaraj et al. | Feb 2001 | B1 |
| 6195698 | Lillibridge et al. | Feb 2001 | B1 |
| 6199077 | Inala | Mar 2001 | B1 |
| 6205433 | Boesch | Mar 2001 | B1 |
| 6208975 | Bull | Mar 2001 | B1 |
| 6209007 | Kelley et al. | Mar 2001 | B1 |
| 6243816 | Fang et al. | Jun 2001 | B1 |
| 6246999 | Riley et al. | Jun 2001 | B1 |
| 6278449 | Sugiarto et al. | Aug 2001 | B1 |
| 6278999 | Knapp | Aug 2001 | B1 |
| 6292789 | Schutzer | Sep 2001 | B1 |
| 6297819 | Furst | Oct 2001 | B1 |
| 6301584 | Ranger | Oct 2001 | B1 |
| 6308203 | Itabashi et al. | Oct 2001 | B1 |
| 6311275 | Jin et al. | Oct 2001 | B1 |
| 6317783 | Freishtat | Nov 2001 | B1 |
| 6360205 | Iyengar | Mar 2002 | B1 |
| 6366933 | Ball et al. | Apr 2002 | B1 |
| 6401118 | Thomas | Jun 2002 | B1 |
| 6405245 | Burson | Jun 2002 | B1 |
| 6412073 | Rangan | Jun 2002 | B1 |
| 6424968 | Broster | Jul 2002 | B1 |
| 6430539 | Lazarus | Aug 2002 | B1 |
| 6484155 | Kiss | Nov 2002 | B1 |
| 6499042 | Markus | Dec 2002 | B1 |
| 6510451 | Wu | Jan 2003 | B2 |
| 6519571 | Guhen et al. | Feb 2003 | B1 |
| 6567411 | Dahlen | May 2003 | B2 |
| 6567850 | Freishtat | May 2003 | B1 |
| 6594766 | Rangan | Jul 2003 | B2 |
| 6632248 | Isaac et al. | Oct 2003 | B1 |
| 6633910 | Rajan | Oct 2003 | B1 |
| 6631402 | Devine | Nov 2003 | B1 |
| 6725200 | Rost | Apr 2004 | B1 |
| 6802042 | Rangan | Oct 2004 | B2 |
| 6859931 | Cheyer et al. | Feb 2005 | B1 |
| 6957199 | Fisher | Oct 2005 | B1 |
| 7028049 | Shelton | Apr 2006 | B1 |
| 7072932 | Stahl | Jul 2006 | B1 |
| 7092913 | Cannon, Jr. | Aug 2006 | B2 |
| 7200578 | Paltenghe et al. | Apr 2007 | B2 |
| 7263548 | Daswani | Aug 2007 | B2 |
| 7275046 | Tritt et al. | Sep 2007 | B1 |
| 7340411 | Cook | Mar 2008 | B2 |
| 7370011 | Bennett et al. | May 2008 | B2 |
| 7424520 | Daswani | Sep 2008 | B2 |
| 7640210 | Bennett et al. | Dec 2009 | B2 |
| 7752535 | Satyavolu | Jul 2010 | B2 |
| 8006291 | Headley et al. | Aug 2011 | B2 |
| 8010783 | Cahill | Aug 2011 | B1 |
| 8086508 | Dheer et al. | Dec 2011 | B2 |
| 8140431 | Murphy | Mar 2012 | B1 |
| 8145914 | Steeves | Mar 2012 | B2 |
| 8166562 | Holvey et al. | Apr 2012 | B2 |
| 8209194 | Nidy et al. | Jun 2012 | B1 |
| 8266515 | Satyavolu | Sep 2012 | B2 |
| 8613066 | Brezinski et al. | Dec 2013 | B1 |
| 8645264 | Allison et al. | Feb 2014 | B2 |
| 8676611 | McLaughlin et al. | Mar 2014 | B2 |
| 8739260 | Damm-Goossens | May 2014 | B1 |
| 8788416 | Vu | Jul 2014 | B1 |
| 8995967 | Billman | Mar 2015 | B1 |
| 9106642 | Bhimanail | Aug 2015 | B1 |
| 9202250 | Palaniappan | Dec 2015 | B1 |
| 9418387 | Aaron et al. | Aug 2016 | B1 |
| 9430892 | Amdahl | Aug 2016 | B2 |
| 9449346 | Hockey | Sep 2016 | B1 |
| 9595023 | Hockey et al. | Mar 2017 | B1 |
| 9699187 | Chen et al. | Jul 2017 | B2 |
| 9774590 | Bronshtein et al. | Sep 2017 | B1 |
| 9906520 | Fouad et al. | Feb 2018 | B2 |
| 9946996 | Bedell | Apr 2018 | B1 |
| 10003591 | Hockey | Jun 2018 | B2 |
| 10104059 | Hockey | Oct 2018 | B2 |
| 10319029 | Hockey | Jun 2019 | B1 |
| 10339608 | Haitz et al. | Jul 2019 | B1 |
| 10523653 | Hockey | Dec 2019 | B2 |
| 10530761 | Hockey et al. | Jan 2020 | B2 |
| 10546348 | Lesner et al. | Jan 2020 | B1 |
| 10614463 | Hockey et al. | Apr 2020 | B1 |
| 10679303 | Aaron et al. | Jun 2020 | B1 |
| 10726491 | Hockey et al. | Jul 2020 | B1 |
| 10762559 | Alejo et al. | Sep 2020 | B2 |
| 10878421 | Putnam | Dec 2020 | B2 |
| 10904239 | Hockey et al. | Jan 2021 | B2 |
| 10984468 | Hockey et al. | Apr 2021 | B1 |
| 11030682 | Hockey et al. | Jun 2021 | B1 |
| 11050729 | Hockey et al. | Jun 2021 | B2 |
| 11216814 | Hockey et al. | Jan 2022 | B1 |
| 11316862 | Pate et al. | Apr 2022 | B1 |
| 11327960 | Jin et al. | May 2022 | B1 |
| 11430057 | Hockey et al. | Aug 2022 | B1 |
| 11468085 | Putnam et al. | Oct 2022 | B2 |
| 11503010 | Hockey et al. | Nov 2022 | B2 |
| 20010011274 | Klug et al. | Aug 2001 | A1 |
| 20020002596 | Sugiarto et al. | Jan 2002 | A1 |
| 20020065772 | Saliba et al. | May 2002 | A1 |
| 20020091635 | Dilip et al. | Jul 2002 | A1 |
| 20020095588 | Shigematsu et al. | Jul 2002 | A1 |
| 20030023879 | Wray | Jan 2003 | A1 |
| 20030028646 | Wray | Feb 2003 | A1 |
| 20030060896 | Hulai | Mar 2003 | A9 |
| 20030158960 | Engberg | Aug 2003 | A1 |
| 20030163425 | Cannon, Jr. | Aug 2003 | A1 |
| 20030182035 | DiLodovico et al. | Sep 2003 | A1 |
| 20030185370 | Rosera et al. | Oct 2003 | A1 |
| 20030204460 | Robinson et al. | Oct 2003 | A1 |
| 20040059672 | Baig et al. | Mar 2004 | A1 |
| 20050027617 | Zucker et al. | Feb 2005 | A1 |
| 20050154913 | Barriga et al. | Jul 2005 | A1 |
| 20050177510 | Hilt et al. | Aug 2005 | A1 |
| 20050222929 | Steier et al. | Oct 2005 | A1 |
| 20050234822 | VanFleet | Oct 2005 | A1 |
| 20050246269 | Smith | Nov 2005 | A1 |
| 20060015358 | Chua | Jan 2006 | A1 |
| 20060116949 | Wehunt et al. | Jun 2006 | A1 |
| 20060136332 | Ziegler | Jun 2006 | A1 |
| 20060190569 | Neil | Aug 2006 | A1 |
| 20060236384 | Lindholm et al. | Oct 2006 | A1 |
| 20070179883 | Questembert | Aug 2007 | A1 |
| 20070179942 | Heggem | Aug 2007 | A1 |
| 20070198432 | Pitroda et al. | Aug 2007 | A1 |
| 20070225047 | Bakos | Sep 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20070289002 | van der Horst et al. | Dec 2007 | A1 |
| 20080051059 | Fisher | Feb 2008 | A1 |
| 20080052192 | Fisher | Feb 2008 | A1 |
| 20080052233 | Fisher | Feb 2008 | A1 |
| 20080120129 | Seubert et al. | May 2008 | A1 |
| 20080162361 | Sklovsky | Jul 2008 | A1 |
| 20080183628 | Oliver et al. | Jul 2008 | A1 |
| 20080243784 | Stading | Oct 2008 | A1 |
| 20080249931 | Gilder et al. | Oct 2008 | A1 |
| 20080250246 | Arditti et al. | Oct 2008 | A1 |
| 20090037308 | Feinstein | Feb 2009 | A1 |
| 20090070257 | Csoka | Mar 2009 | A1 |
| 20090157555 | Biffle et al. | Jun 2009 | A1 |
| 20090222900 | Benaloh et al. | Sep 2009 | A1 |
| 20090228779 | Williamson et al. | Sep 2009 | A1 |
| 20090245521 | Vembu | Oct 2009 | A1 |
| 20090271847 | Karjala et al. | Oct 2009 | A1 |
| 20090328177 | Frey et al. | Dec 2009 | A1 |
| 20100027552 | Hill | Feb 2010 | A1 |
| 20100043054 | Kidwell | Feb 2010 | A1 |
| 20100049850 | Nanduri et al. | Feb 2010 | A1 |
| 20100169072 | Zaki et al. | Jul 2010 | A1 |
| 20100185868 | Grecia | Jul 2010 | A1 |
| 20100223160 | Brown | Sep 2010 | A1 |
| 20100235882 | Moore | Sep 2010 | A1 |
| 20100313255 | Khuda | Dec 2010 | A1 |
| 20100325710 | Etchegoyen | Dec 2010 | A1 |
| 20110055079 | Meaney et al. | Mar 2011 | A1 |
| 20110196790 | Milne | Aug 2011 | A1 |
| 20110238550 | Reich et al. | Sep 2011 | A1 |
| 20110247060 | Whitmyer, Jr. | Oct 2011 | A1 |
| 20110295731 | Waldron, III et al. | Dec 2011 | A1 |
| 20120059706 | Goenka et al. | Mar 2012 | A1 |
| 20120116880 | Patel et al. | May 2012 | A1 |
| 20120129503 | Lindeman et al. | May 2012 | A1 |
| 20120191603 | Nuzzi | Jul 2012 | A1 |
| 20120209775 | Milne | Aug 2012 | A1 |
| 20120215688 | Musser et al. | Aug 2012 | A1 |
| 20120233212 | Newton et al. | Sep 2012 | A1 |
| 20120246073 | Gore et al. | Sep 2012 | A1 |
| 20120253876 | Hersch | Oct 2012 | A1 |
| 20120278201 | Milne | Nov 2012 | A1 |
| 20120281058 | Laney et al. | Nov 2012 | A1 |
| 20120284175 | Wilson et al. | Nov 2012 | A1 |
| 20120323717 | Kirsch | Dec 2012 | A1 |
| 20130019297 | Lawson et al. | Jan 2013 | A1 |
| 20130041736 | Coppinger | Feb 2013 | A1 |
| 20130041739 | Coppinger | Feb 2013 | A1 |
| 20130041744 | Coppinger | Feb 2013 | A1 |
| 20130046599 | Coppinger | Feb 2013 | A1 |
| 20130097685 | Kennedy et al. | Apr 2013 | A1 |
| 20130125223 | Sorotokin et al. | May 2013 | A1 |
| 20130174015 | Jeff L. | Jul 2013 | A1 |
| 20130191526 | Zhao | Jul 2013 | A1 |
| 20130232006 | Holcomb et al. | Sep 2013 | A1 |
| 20130232159 | Daya et al. | Sep 2013 | A1 |
| 20130247005 | Hirsch et al. | Sep 2013 | A1 |
| 20130282577 | Milne | Oct 2013 | A1 |
| 20130318592 | Grier, Sr. et al. | Nov 2013 | A1 |
| 20140032414 | Beisner et al. | Jan 2014 | A1 |
| 20140040148 | Ozvat et al. | Feb 2014 | A1 |
| 20140044123 | Lawson et al. | Feb 2014 | A1 |
| 20140067499 | Stepanovich | Mar 2014 | A1 |
| 20140150072 | Castro et al. | May 2014 | A1 |
| 20140165156 | Fushman et al. | Jun 2014 | A1 |
| 20140173695 | Valdivia | Jun 2014 | A1 |
| 20140180962 | Fiala et al. | Jun 2014 | A1 |
| 20140189002 | Orioli et al. | Jul 2014 | A1 |
| 20140189808 | Mahaffey et al. | Jul 2014 | A1 |
| 20140189828 | Baghdasaryan et al. | Jul 2014 | A1 |
| 20140208389 | Kelley | Jul 2014 | A1 |
| 20140215551 | Allain et al. | Jul 2014 | A1 |
| 20140229462 | Lo | Aug 2014 | A1 |
| 20140236716 | Shapiro et al. | Aug 2014 | A1 |
| 20140245411 | Meng et al. | Aug 2014 | A1 |
| 20140258063 | Chourasia et al. | Sep 2014 | A1 |
| 20140280555 | Tapia et al. | Sep 2014 | A1 |
| 20140344141 | Cook | Nov 2014 | A1 |
| 20140358704 | Banerjee et al. | Dec 2014 | A1 |
| 20140365350 | Shvarts | Dec 2014 | A1 |
| 20150026024 | Calman et al. | Jan 2015 | A1 |
| 20150046338 | Laxminarayanan et al. | Feb 2015 | A1 |
| 20150066719 | Agrawal et al. | Mar 2015 | A1 |
| 20150066765 | Banks et al. | Mar 2015 | A1 |
| 20150088707 | Drury et al. | Mar 2015 | A1 |
| 20150088732 | DeVan, Jr. et al. | Mar 2015 | A1 |
| 20150113511 | Poulin | Apr 2015 | A1 |
| 20150161608 | Gilbert | Jun 2015 | A1 |
| 20150193871 | Murphy | Jul 2015 | A1 |
| 20150254672 | Huesch et al. | Sep 2015 | A1 |
| 20150281225 | Schoen et al. | Oct 2015 | A1 |
| 20150310562 | Chourasia et al. | Oct 2015 | A1 |
| 20150339664 | Wong et al. | Nov 2015 | A1 |
| 20150365399 | Biswas et al. | Dec 2015 | A1 |
| 20160063657 | Chen et al. | Mar 2016 | A1 |
| 20170118301 | Kouru et al. | Apr 2017 | A1 |
| 20170132633 | Whitehouse | May 2017 | A1 |
| 20170148021 | Goldstein et al. | May 2017 | A1 |
| 20170193112 | Desineni et al. | Jul 2017 | A1 |
| 20170193486 | Parekh | Jul 2017 | A1 |
| 20170200137 | Vilmont | Jul 2017 | A1 |
| 20170200234 | Morse | Jul 2017 | A1 |
| 20170262840 | Dunwoody | Sep 2017 | A1 |
| 20170300960 | Khvostov et al. | Oct 2017 | A1 |
| 20170301013 | Alejo et al. | Oct 2017 | A1 |
| 20170308902 | Quiroga et al. | Oct 2017 | A1 |
| 20180060927 | Gupta | Mar 2018 | A1 |
| 20180157851 | Sgambati et al. | Jun 2018 | A1 |
| 20180191685 | Bajoria | Jul 2018 | A1 |
| 20180196694 | Banerjee et al. | Jul 2018 | A1 |
| 20180232734 | Smets et al. | Aug 2018 | A1 |
| 20180246943 | Avagyan et al. | Aug 2018 | A1 |
| 20180267847 | Smith et al. | Sep 2018 | A1 |
| 20180267874 | Keremane et al. | Sep 2018 | A1 |
| 20180330342 | Prakash et al. | Nov 2018 | A1 |
| 20180349909 | Allen et al. | Dec 2018 | A1 |
| 20180367428 | Di Pietro et al. | Dec 2018 | A1 |
| 20190075115 | Anderson et al. | Mar 2019 | A1 |
| 20190180364 | Chong et al. | Jun 2019 | A1 |
| 20190333159 | Chourasia et al. | Oct 2019 | A1 |
| 20190354544 | Hertz et al. | Nov 2019 | A1 |
| 20200110585 | Perry | Apr 2020 | A1 |
| 20200201878 | Putnam et al. | Jun 2020 | A1 |
| 20200234376 | Lord et al. | Jul 2020 | A1 |
| 20210004439 | Xiong et al. | Jan 2021 | A1 |
| 20210165960 | Eisenschlos et al. | Jun 2021 | A1 |
| 20210217016 | Putman | Jul 2021 | A1 |
| 20210233162 | Hockey et al. | Jul 2021 | A1 |
| 20210281558 | Hockey et al. | Sep 2021 | A1 |
| 20210288956 | Hockey et al. | Sep 2021 | A1 |
| 20210350340 | Lai et al. | Nov 2021 | A1 |
| 20220217147 | Pate et al. | Jul 2022 | A1 |
| 20220229980 | Jin et al. | Jul 2022 | A1 |
| 20220327141 | Putnam et al. | Oct 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 0 848 336 | Jun 1998 | EP |
| 0 848 338 | Jun 1998 | EP |
| 0 848 339 | Jun 1998 | EP |
| 2 747 374 | Jun 2014 | EP |
| 3 347 846 | Jul 2018 | EP |
| WO 9638795 | Dec 1996 | WO |
| WO 9710542 | Mar 1997 | WO |
| WO 9709682 | May 1997 | WO |
| WO 9726612 | Jul 1997 | WO |
| WO 9737314 | Oct 1997 | WO |
| WO 9814896 | Apr 1998 | WO |
| WO 0025227 | May 2000 | WO |
| WO 2017044479 | Mar 2017 | WO |
| WO 2017173021 | Oct 2017 | WO |
| WO 2022082186 | Apr 2022 | WO |
| Entry |
|---|
| U.S. Appl. No. 14/719,110, System and Method for Programmatically Accessing Financial Data, filed May 21, 2015. |
| U.S. Appl. No. 17/302,630, System and Method for Programmatically Accessing Financial Data, filed May 7, 2021. |
| U.S. Appl. No. 17/303,432, Secure Permissioning of Access to User Accounts, Including Secure Deauthorization of Access to User Accounts, filed May 28, 2021. |
| U.S. Appl. No. 17/126,673, Secure Permissioning of Access to User Accounts, Including Secure Deauthorization of Access to User Accounts, filed Dec. 18, 2020. |
| U.S. Appl. No. 16/900,052, Parameter-Based Computer Evaluation of User Accounts Based on User Account Data Stored in One or More Databases, filed Jun. 12, 2020. |
| U.S. Appl. No. 17/230,835, Systems and Methods for Estimating Past and Prospective Attribute Values Associated with a User Account, filed Apr. 14, 2021. |
| U.S. Appl. No. 16/570,630, Secure Authorization of Access to User Accounts by One or More Authorization Mechanisms, filed Sep. 13, 2019. |
| U.S. Appl. No. 16/042,147, Browser-Based Aggregation, filed Jul. 23, 2018. |
| U.S. Appl. No. 17/103,267, Data Verified Deposits, filed Nov. 24, 2020. |
| U.S. Appl. No. 17/302,499, Secure Updating of Allocations to User Accounts, filed May 4, 2021. |
| U.S. Appl. No. 17/499,696, Systems and Methods for Data Parsing, filed Oct. 12, 2021. |
| “A Single Login Web Service Integrator—WebEntrance”, Yan Zhao, Sixth International World Wide Web Conference, Santa Clara, CA, Apr. 7-11, 1997, 10 pages. |
| “Automatic Notification of Web Sites Changes,” Google Groups, Aug. 30, 1995, 1 page. |
| “Boeing Chooses NetMind Enterprise Minder to Help Thousands of Employees Track Web-Based Information,” PR Newswire, Nov. 19, 1998, 3 pages. |
| “Caravelle's InfoWatcher 1.1 Keeps an Eye on the Web,” PC Week 1997, 2 pages. |
| “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, Aug. 14, 1996, 4 pages. |
| “FirstFloor and AirMedia Announce Partnership,” Business Wire 1997 (“FirstFloor”), 2 pages. |
| “Fujitsu Announces ‘WebAgent’ Application as part of ByeDesk Link Wireless Server Software,” Business Wire, Sep. 1, 1998, 3 pages. |
| “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, 3 pages. |
| “Fujitsu Picks NetMind for Wireless Web Agent Software,” Computergram International, Sep. 2, 1998, 1 page. |
| “Fujitsu's ByeDesk Link Now Available On the PalmPilot,” Business Wire, Sep. 21, 1998, 4 pages. |
| “GC Tech's GlobeID Payment Internet Commerce Software Supports Microsoft, Merchant Server,” Business Wire, Jan. 21, 1997, 3 pages. |
| “Highly Scalable On-Line Payments via Task Decoupling,” Financial Cryptography First International Conference, 1998, 2 pages. |
| “Minding Web Site Changes,” PC Week, Sep. 14, 1998, 3 pages. |
| “NetMind Accepts $7 Million Strategic Investment From Three Prominent VC Firms—BancBoston, Softbank and Draper Fisher Jurvestson,” PR Newswire, Nov. 6, 1998, 3 pages. |
| “NetMind Updates the World's Largest Free Web Tracking Service,” PR Newswire, Sep. 18, 1998, 4 pages. |
| “The AT&T Internet Difference Engine: Tracking and Viewing Changes on the Web,” World Wide Web 1 (1); Jan. 1998, pp. 1-29. |
| “Versatile Intelligent Agents in Commercial Applications,” Google Groups, Dec. 12, 1998, 9 pages. |
| “Web Interface Definition Language (WIDL)”, W3 Consortium submission from webMethods, Inc., Sep. 22, 1997, 15 pages. |
| 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, 8 pages. |
| 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, 6 pages. |
| Chaulagain et al., “Cloud Based Web Scraping for Big Data Application.” IEEE International Conference on Smart Cloud, 2017, pp. 138-143. |
| Corena et al., “Secure and fast aggregation of financial data in cloud-based expense tracking applications.” Journal of Network and Systems Management 20.4 (2012): 534-560. |
| Hagel et al. “The Coming Battle for Customer Information.” Harvard Business Review, Jan.-Feb. 1997, reprint No. 97104, 20 pages. |
| Hummer, Waldemar, Philipp Leitner, and Schahram Dustdar. “Ws-aggregation: distributed of web services data.” Proceedings of the 2011 ACM Symposium on Applied Computing. ACM, 2011, 8 pages. |
| 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, 7 pages. |
| 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. |
| Kim, Young-Gon et. al., ‘A Design of User Authentication System Using QR code Identifying Method’, 6th International Conference on Computer Sciences and Convergence Information Technology (ICCIT), pp. 31-35, 2011. |
| Kyeongwon C., et. al., ‘A Mobile based Anti-Phishing Authentication Scheme using QR code’, IEEE International Conference on Mobile IT Convergence, pp. 109-113, 2011. |
| M. C. McChesney, “Banking in cyberspace: an investment in itself,” IEEE Spectrum, vol. 34, No. 2, Feb. 1997, pp. 54-59. |
| Mancini et al., “Simulation in the Cloud Using Handheld Devices,” Workshop on Modeling and Simulation on Grid and Cloud Computing, Apr. 25, 2012, 8 pages. |
| 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, 9 pages. |
| Mohammed et al. A Multi-layer of Multi Factors Authentication Model for Online Banking Services, Oct. 15, 2013, 2013 International Conference on Computing, Electrical and Electronic Engineering (ICCEEE), pp. 220-224. |
| Neville, S.W. et al. Efficiently Archieving Full Three-Way Non-repudiation in Consumer-level eCommerce and M-Commerce Transactions, Nov. 1, 2011, 2011 IEEE 10th International Conference on Trust, Security and Privacy in Computing and Communications, pp. 664-672. |
| Optimizing Information Agents by Selectively Materializing Data, Naveen Ashish, Craig A. Knoblock, and Cyrus Shahabi. In Proceedings of the AAAI'98 Workshop on AI and Information Integration, Madison, WI, 1998. Jul. 26-30, 1998, 6 pages. |
| O'Riain et al., “XBRL and open data for global financial ecosystems: A linked data approach.” International Journal of Accounting Information Systems 13.2 (2012): 141-162. |
| Quwaider et al., “Experimental Framework for Mobile Cloud Computing System”, Jordan University of Science and Technology, Procedia Computer Science 52, 2015, pp. 1147-1152. |
| 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, 10 pages. |
| Sunwoo et al., “A Structured Approach to the Simulation, Analysis and Characterization of Smartphone Applications”, IEEE 2013, pp. 113-122. |
| The ariadne approach to web-based information integration, Craig A. Knoblock and Steven Minton. IEEE Intelligent Systems, 13(5), Sep./Oct. 1998, 4 pages. |
| Wrapper generation for semi-structured Internet sources, Naveen Ashish and Craig A. Knoblock. In Proceedings of the Workshop on Management of Semistructured Data, Tucson, AZ, 1997. May 13-15, 1997, 8 pages. |
| Wrapper induction for semistructured, 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, 6 pages. |
| Y. Zhao, “WebEntree: A Web Service Aggregator”, IBM Systems Journal, vol. 37, No. 4, 1998, pp. 584-595. |
| Examination Report in CA Application No. 2997115, dated Jun. 20, 2019,4 pages. |
| Examination Report in CA Application No. 2997115, dated Nov. 13, 2019, 8 pages. |
| Examination Report in CA Application No. 2997115 dated Apr. 2, 2020, 5 pages. |
| Examination Report in CA Application No. 2997115 dated Nov. 2, 2020, 3 pages. |
| Supplementary European Search Report in EP Application No. 16844973.4, dated Jan. 4, 2019, 2 pages. |
| Examination Report in EP Application No. 16844973.4 dated Nov. 4, 2020, 6 pages. |
| Examination Report in AU Application No. 2016321166 dated Dec. 7, 2020, 5 pages. |
| International Search Report in PCT Application No. PCT/US2016/050536, dated Dec. 15, 2016, 8 pages. |
| International Search Report and Written Opinion in PCT Application No. PCT/US2021/030808, dated Jun. 21, 2021, 11 pages. |
| Devlin, J. et al., “BERT: Pre-training of Deep Bidirectional Transformers for Language Understanding,” arXive, May 24, 2019, retrieved from the internet, URL: https://arxiv.org/pdf/1810.04805.pdf, 16 pages. |
| Jin, C., “How Plaid parses transaction data,” Oct. 22, 2020, retrieved from the internet, URL: https://plaid.com/blog/how-plaid-parsestransaction-data/, 10 pages. |
| Examination Report in CA Application No. 3119897 dated Jul. 30, 2021, 6 pages. |
| International Search Report and Written Opinion in PCT Application No. PCT/US2021/071851, dated Dec. 13, 2021, 10 pages. |
| U.S. Appl. No. 17/303,432, Secure Permissioning of Access to User Accounts, Including Secure Deautherization of Access to User Accounts, filed May 28, 2021. |
| U.S. Appl. No. 17/815,024, Parameter-Based Computer Evaluation of User Accounts Based on User Account Data Stored in One or More Databases, filed Jul. 26, 2022. |
| U.S. Appl. No. 17/656,528, Secure Authorization of Access to User Accounts by One or More Authorization Mechanisms, filed Mar. 25, 2022. |
| U.S. Appl. No. 17/842,444, Browser-Based Aggregation, filed Jun. 16, 2022. |
| U.S. Appl. No. 17/658,416, Systems and Methods for Data Parsing, filed Apr. 7, 2022. |
| Adam et al., “Backend Server System Design Based on Rest API for Cashless Payment System on Retail Community”, International Electronics Symposium (IES), Sep. 2019, pp. 208-213. |
| Chard et al., “Efficient and Secure Transfer, Synchronization, and Sharing of Big Data”, IEEE Cloud Computing, 2014, vol. 1, Issue 3, pp. 46-55. |
| European Search Report in EP Application No. 21215799.4 dated Mar. 25, 2022, 8 pages. |
| U.S. Appl. No. 14/719,117, System and Method for Facilitating Programmatic Verification of Transactions, filed May 21, 2015. |
| Dec. 7, 2023—U.S. Non-Final Office Action—U.S. Appl. No. 18/382,152. |
| Number | Date | Country | |
|---|---|---|---|
| 62001461 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16800543 | Feb 2020 | US |
| Child | 17533728 | US | |
| Parent | 15455959 | Mar 2017 | US |
| Child | 16800543 | US | |
| Parent | 14790897 | Jul 2015 | US |
| Child | 15455959 | US | |
| Parent | 14719117 | May 2015 | US |
| Child | 14790897 | US |
