Aggregating data from multiple issuers and automatically organizing the data
First Claim
1. A method comprising:
- receiving, by an aggregator via a network, first data from a first issuer, the first data including;
confidential information associated with a user;
an account identifier to enable the first issuer to access an account hosted by the aggregator that is associated with the user, the account identifier including at least a portion of user registration data provided to the user when the user initially registered with the aggregator; and
an issuer identifier associated with the first issuer;
authenticating an identity of the first issuer based on the issuer identifier;
determining whether the first issuer is authorized to provide the first data based at least in part on the account identifier and the issuer identifier;
in response to determining that the first issuer is authorized to provide the first data, identifying the account associated with the user based on the account identifier;
in response to determining, based on a type of the first data, that the first data is to be stored using a hierarchical structure, determining whether the account includes the hierarchical structure;
in response to determining that the account does not include the hierarchical structure, automatically creating the hierarchical structure within the account based on the type of the first data;
in response to determining that the account includes a user-specified location provided by the user, storing the first data in the account based on the user-specified location;
in response to determining that the account does not include the user-specified location, determining whether the first data includes a first storage location identifier;
in response to determining that the first data includes the first storage location identifier, storing the first data in a first location within the account based on the first storage location identifier;
in response to determining that the first data does not include the first storage location identifier, storing the data in a default location in the account;
receiving, by the aggregator via a network, second data from a second issuer, the second data including the account identifier to indicate that the second data is associated with the user, wherein the second issuer is an auto-issuer that sends user data to the aggregator using an application programming interface (API) provided by one of the aggregator or the auto-issuer, the API enabling the auto-issuer to automatically send the user data to multiple user accounts hosted by the aggregator; and
in response to authenticating the identity of the second issuer based at least partly on the account identifier, storing the second data in a second location within the account based on a second storage location identifier included in the second data, the second location used to store data received from the second issuer.
2 Assignments
0 Petitions
Accused Products
Abstract
Some implementations provide techniques and arrangements to aggregate data from multiple issuers. An aggregator server may receive data associated with a user from an issuer. The data may include an issuer identifier associated with the issuer, account access data associated with the user, and a storage location identifier. The aggregator server may authenticate an identity of the issuer based on the issuer identifier and determine whether the issuer is authorized to provide the data for the user. In response to determining that the issuer is authorized to provide the data for the user, he aggregator server may identify an account associated with the user based on the account access data and store the data in the account associated with the user based at least partially on the storage location identifier.
-
Citations
20 Claims
-
1. A method comprising:
-
receiving, by an aggregator via a network, first data from a first issuer, the first data including; confidential information associated with a user; an account identifier to enable the first issuer to access an account hosted by the aggregator that is associated with the user, the account identifier including at least a portion of user registration data provided to the user when the user initially registered with the aggregator; and an issuer identifier associated with the first issuer; authenticating an identity of the first issuer based on the issuer identifier; determining whether the first issuer is authorized to provide the first data based at least in part on the account identifier and the issuer identifier; in response to determining that the first issuer is authorized to provide the first data, identifying the account associated with the user based on the account identifier; in response to determining, based on a type of the first data, that the first data is to be stored using a hierarchical structure, determining whether the account includes the hierarchical structure; in response to determining that the account does not include the hierarchical structure, automatically creating the hierarchical structure within the account based on the type of the first data; in response to determining that the account includes a user-specified location provided by the user, storing the first data in the account based on the user-specified location; in response to determining that the account does not include the user-specified location, determining whether the first data includes a first storage location identifier; in response to determining that the first data includes the first storage location identifier, storing the first data in a first location within the account based on the first storage location identifier; in response to determining that the first data does not include the first storage location identifier, storing the data in a default location in the account; receiving, by the aggregator via a network, second data from a second issuer, the second data including the account identifier to indicate that the second data is associated with the user, wherein the second issuer is an auto-issuer that sends user data to the aggregator using an application programming interface (API) provided by one of the aggregator or the auto-issuer, the API enabling the auto-issuer to automatically send the user data to multiple user accounts hosted by the aggregator; and in response to authenticating the identity of the second issuer based at least partly on the account identifier, storing the second data in a second location within the account based on a second storage location identifier included in the second data, the second location used to store data received from the second issuer. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. An aggregator server comprising:
-
one or more processors; and one or more non-transitory computer-readable media including instructions that are executable by the one or more processors to perform operations comprising; receiving first data from a first issuer via a network, the first data including; confidential information associated with a user; an account identifier to enable the first issuer to access an account hosted by the aggregator server that is associated with the user, the account identifier including at least a portion of user registration data provided to the user when the user initially registered with the aggregator server; and an issuer identifier associated with the first issuer; authenticating an identity of the first issuer based on the issuer identifier; determining whether the first issuer is authorized to provide the first data based at least in part on the account identifier and the issuer identifier; in response to determining that the first issuer is authorized to provide the first data, identifying the account associated with the user based on the account identifier; in response to determining, based on a type of the first data, that the first data is to be stored using a hierarchical structure, determining whether the account includes the hierarchical structure; in response to determining that the account does not include the hierarchical structure, automatically creating the hierarchical structure within the account based on the type of the first data; in response to determining that the account includes a user-specified location provided by the user, storing the first data in the account based on the user-specified location; in response to determining that the account does not include the user-specified location, determining whether the first data includes a first storage location identifier; in response to determining that the first data includes the first storage location identifier, storing the first data in a first location within the account based on the first storage location identifier; in response to determining that the first data does not include the first storage location identifier, storing the data in a default location in the account; receiving, by the aggregator via a network, second data from a second issuer, the second data including the account identifier to indicate that the second data is associated with the user, wherein the second issuer is an auto-issuer that sends user data to the aggregator server using an application programming interface (API) provided by one of the aggregator server or the auto-issuer, the API enabling the auto-issuer to automatically send the user data to multiple user accounts hosted by the aggregator server; and in response to authenticating the identity of the second issuer based at least partly on the account identifier, storing the second data in a second location within the account based on a second storage location identifier included in the second data, the second location used to store data received from the second issuer. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
15. One or more non-transitory computer-readable media to store instructions executable by one or more processors to perform operations comprising:
-
receiving, by an aggregator via a network, first data from a first issuer, the first data including; confidential information associated with a user; an account identifier to enable the first issuer to access an account hosted by the aggregator that is associated with the user, the account identifier including at least a portion of user registration data provided to the user when the user initially registered with the aggregator; and a first issuer identifier associated with the first issuer; authenticating an identity of the first issuer based on the first issuer identifier; determining whether the first issuer is authorized to provide the first data based at least in part on the account identifier and the first issuer identifier; in response to determining that the first issuer is authorized to provide the first data, identifying the account associated with the user based on the account identifier; in response to determining, based on a type of the first data, that the first data is to be stored using a hierarchical structure, determining whether the account includes the hierarchical structure; in response to determining that the account does not include the hierarchical structure, automatically creating the hierarchical structure within the account based on the type of the first data; in response to determining that the account includes a user-specified location provided by the user, storing the first data in the account based on the user-specified location; in response to determining that the account does not include the user-specified location, determining whether the first data includes a first storage location identifier; in response to determining that the first data includes the first storage location identifier, storing the first data in a first location within the account based on the first storage location identifier; in response to determining that the first data does not include the first storage location identifier, storing the data in a default location in the account; receiving, by the aggregator via a network, second data from a second issuer, the second data including the account identifier to indicate that the second data is associated with the user, wherein the second issuer is an auto-issuer that sends user data to the aggregator using an application programming interface (API) provided by one of the aggregator or the auto-issuer, the API enabling the auto-issuer to automatically send the user data to multiple user accounts hosted by the aggregator; and in response to authenticating the identity of the second issuer based at least partly on the account identifier, storing the second data in a second location within the account based on a second storage location identifier included in the second data, the second location used to store data received from the second issuer. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification