Abstract: An identity risk score may be determined for subscribers of a service to indicate a level of confidence or certainty associated with a subscriber's identity. The identity risk score may be modified upward or downward in order to reflect changing levels of certainty. The changes may be based on transactions performed on behalf of and/or information submitted by the subscriber. Functionality provided to the subscriber may also be dependent upon whether the subscriber's identity risk score meets a threshold. In one or more arrangements, an identity risk score may be determined based on whether information entered by the subscriber can be confirmed and a level of confidence with which the information is confirmed.

Abstract: An identity risk score may be determined for subscribers of a service to indicate a level of confidence or certainty associated with a subscriber's identity. The identity risk score may be modified upward or downward in order to reflect changing levels of certainty. The changes may be based on transactions performed on behalf of and/or information submitted by the subscriber. Functionality provided to the subscriber may also be dependent upon whether the subscriber's identity risk score meets a threshold. In one or more arrangements, an identity risk score may be determined based on whether information entered by the subscriber can be confirmed and a level of confidence with which the information is confirmed.

Abstract: A system and method for determining and displaying a payment lead time or expected payment delivery time in an electronic payment system is disclosed. A payee associated with a payor is identified. Prior to receiving a payment request to pay the payee on behalf of the payor, an expected payment delivery time for a payment to fulfill the payment request is determined. The expected payment delivery time is based on at least one payment attribute associated with the payee and at least one payment attribute associated with the payor. An interface screen is then generated for displaying the determined expected payment delivery time.

Abstract: A system and method for determining and displaying a payment lead time or expected payment delivery time in an electronic payment system is disclosed. A payee associated with a payor is identified. Prior to receiving a payment request to pay the payee on behalf of the payor, an expected payment delivery time for a payment to fulfill the payment request is determined. The expected payment delivery time is based on at least one payment attribute associated with the payee and at least one payment attribute associated with the payor. An interface screen is then generated for displaying the determined expected payment delivery time.

Abstract: An identity risk score may be determined for subscribers of a service to indicate a level of confidence or certainty associated with a subscriber's identity. The identity risk score may be modified upward or downward in order to reflect changing levels of certainty. The changes may be based on transactions performed on behalf of and/or information submitted by the subscriber. Functionality provided to the subscriber may also be dependent upon whether the subscriber's identity risk score meets a threshold. In one or more arrangements, an identity risk score may be determined based on whether information entered by the subscriber can be confirmed and a level of confidence with which the information is confirmed.

Abstract: A system and method for determining and displaying a payment lead time or expected payment delivery time in an electronic payment system is disclosed. A payee associated with a payor is identified. Prior to receiving a payment request to pay the payee on behalf of the payor, an expected payment delivery time for a payment to fulfill the payment request is determined. The expected payment delivery time is based on at least one payment attribute associated with the payee and at least one payment attribute associated with the payor. An interface screen is then generated for displaying the determined expected payment delivery time.

Abstract: A technique for confirming an association between a deposit account and an account holder is provided. The technique includes receiving information identifying the deposit account and identifying the account holder. Other information associated with multiple deposit accounts, each maintained at one of multiple financial institutions, is accessed. The received information and the accessed information are then processed to authenticate the association between the account holder and the deposit account.

Abstract: A technique for confirming an association between a deposit account and an account holder is provided. The technique includes receiving information identifying the deposit account and identifying the account holder. Other information associated with multiple deposit accounts, each maintained at one of multiple financial institutions, is accessed. The received information and the accessed information are then processed to authenticate the association between the account holder and the deposit account.

Abstract: A system and method for processing electronic payment requests. A request to make a payment for a network user is received over a network. The request includes information identifying the network user. All user identifiers associated with the network user are determined. Then, information about previous payments made for the network user is processed. This information about previous payments is based upon the determined identifiers. This processing determines if the request will be honored. A notification of the decision to honor or not to honor the request is then transmitted.

Abstract: A system, method, and article of manufacture for making payments on a network by a payment service provider. The service provider receives information identifying both a network user and the network user's bank account, and a request to make a payment on behalf of the network user. This information is processed for verification. A unique user identifier is also generated. The information and the unique user identifier are stored together.