Abstract: A user registers for an account with an account management system, configures account settings to permit the account management system to receive user computing device data from a user computing device associated with the user, and logs into the account via the user computing device. The account management system receives a user voice purchase command and determines a purchase command context based on the received user computing device data. The account management system identifies a product that the user desires to purchase based on the purchase command context and directs the user computing device web browser to a merchant website to set up a transaction for the identified product.

Abstract: A user registers for an account with an account management system, configures account settings to permit the account management system to receive user computing device data from a user computing device associated with the user, and logs into the account via the user computing device. The account management system receives a user voice purchase command and determines a purchase command context based on the received user computing device data. The account management system identifies a product that the user desires to purchase based on the purchase command context and directs the user computing device web browser to a merchant website to set up a transaction for the identified product.

Abstract: A user registers for an account with an account management system, configures account settings to permit the account management system to receive user computing device data from a user computing device associated with the user, and logs into the account via the user computing device. The account management system receives a user voice purchase command and determines a purchase command context based on the received user computing device data. The account management system identifies a product that the user desires to purchase based on the purchase command context and directs the user computing device web browser to a merchant website to set up a transaction for the identified product.

Abstract: A user registers for an account with an account management system, configures account settings to permit the account management system to receive user computing device data from a user computing device associated with the user, and logs into the account via the user computing device. The account management system receives a user voice purchase command and determines a purchase command context based on the received user computing device data. The account management system identifies a product that the user desires to purchase based on the purchase command context and directs the user computing device web browser to a merchant website to set up a transaction for the identified product.

Abstract: Receiving a request for verification of a customer's identity. The request includes fields of customer identity data. Requesting, from a first verification resource, verification of the customer's identity using the customer identity data. Receiving from the first verification resource, first verification results including at least one new field of customer identity data. The first verification results being insufficient to verify the customer's identity. Requesting, from a second verification resource, verification of the customer's identity using the at least one new field of customer identity data. Receiving, from the second verification resource, second verification results. For second verification results sufficient to verify the customer's identity, communicating to the customer a successful verification of the customer's identity.

Abstract: Receiving a request for verification of a customer's identity. The request includes fields of customer identity data. Requesting, from a first verification resource, verification of the customer's identity using the customer identity data. Receiving from the first verification resource, first verification results including at least one new field of customer identity data. The first verification results being insufficient to verify the customer's identity. Requesting, from a second verification resource, verification of the customer's identity using the at least one new field of customer identity data. Receiving, from the second verification resource, second verification results. For second verification results sufficient to verify the customer's identity, communicating to the customer a successful verification of the customer's identity.

Abstract: Customer identity verification. Receiving a request for verification of a customer's identity. The request includes fields of customer identity data. Requesting, from a first verification resource, verification of the customer's identity using the customer identity data. Receiving from the first verification resource, first verification results including at least one new field of customer identity data. The first verification results being insufficient to verify the customer's identity. Requesting, from a second verification resource, verification of the customer's identity using the at least one new field of customer identity data. Receiving, from the second verification resource, second verification results. For second verification results sufficient to verify the customer's identity, communicating to the customer a successful verification of the customer's identity.

Abstract: Customer identity verification. Receiving a request for verification of a customer's identity. The request includes fields of customer identity data. Requesting, from a first verification resource, verification of the customer's identity using the customer identity data. Receiving from the first verification resource, first verification results including at least one new field of customer identity data. The first verification results being insufficient to verify the customer's identity. Requesting, from a second verification resource, verification of the customer's identity using the at least one new field of customer identity data. Receiving, from the second verification resource, second verification results. For second verification results sufficient to verify the customer's identity, communicating to the customer a successful verification of the customer's identity.

Abstract: Receiving a first set of customer identification and verification data. The first set of data is a proper subset of the data required for access to all the features of a computer-implemented account. Providing to the customer access to a first set of one or more features corresponding to the first set of data. Receiving a customer request for access to an additional feature of the account outside the first set of one or more features. Requesting a second set of customer identification and verification data, wherein the second set of data corresponds to the certain data required for access to the additional feature. Receiving the requested second set of data. Providing to the customer access to the additional feature.