Abstract: A system for bill payment services includes a computer system for accessing biller data, the biller data comprising at least an account identifier, an amount due, and a nominal bill due date. A payment option generator is configured for developing at least one payment option, where a payment is specified responsive to a difference between a proposed payment date and the nominal bill due date. A payer interface is configured for presenting the payment option to the payer, and for accepting a payer option selection and payment funding confirmation. A payment execution controller is responsive to the payer option selection and funding confirmation, for initiating payment to a biller account on behalf of the payer.

Abstract: A system for third party bill payment services used by a payer to pay a biller with whom a payer has an account includes a third party computer system for accessing biller data, the biller data for the payer comprising at least one account identifier an amount due, and a nominal bill due date; a payment option generator for developing at least one payment option wherein the payment specified is responsive to a difference between a proposed payment date and the nominal bill due date; a payer interface for presenting the at least one payment option to the payer and for accepting a payer option selection and a payment funding confirmation; and a payment execution controller responsive to the payer option selection and funding confirmation, for initiating payment to a biller account on behalf of the payer.

Abstract: A system for third party bill payment services used by a payer to pay a biller with whom a payer has an account includes a third party computer system for accessing biller data, the biller data for the payer comprising at least one account identifier, an amount due, and a nominal bill due date; a payment option generator for developing at least one payment option wherein the payment specified is responsive to a difference between a proposed payment date and the nominal bill due date; a payer interface for presenting the at least one payment option to the payer and for accepting a payer option selection and a payment funding confirmation; and a payment execution controller responsive to the payer option selection and funding confirmation, for initiating payment to a biller account on behalf of the payer.

Abstract: A user interface is used to customize fraud rules. In the interface, the user sets a customized threshold trigger and a customized limit trigger for a fraud rule set. The fraud rule set is applied to an action. Triggering the threshold trigger by the action causes a threshold trigger report to be generated and allows the action. Triggering the limit trigger by the action denies the action.

Abstract: A system for third party bill payment services is provided.