Abstract: Processing a payment transaction from a payer (operating a payer computing system) to a payee (operating a merchant computing system) by a secure computing system. The secure computing system outputs a financial account registration request form to the payer computing system (e.g., within a window or frame that is displayed within an ecommerce webpage provided by the merchant computing system) for the payer to provide sensitive financial account information, securely stores the sensitive financial account information, maintains compliance with an information security standard (e.g., a Payment Card Industry Data Security Standard), and provides a non-sensitive electronic data token representing the sensitive financial account information to the merchant computing system.

Abstract: Processing a payment from a payer to a payee (operating a first computing system), by a second computing system, by receiving an electronically-generated payment transaction instruction (identifying the payer, specifying the amount of the payment, and specifying a communications link for the second computing system to obtain financial account information from the payer) from the first computing system, obtaining the financial account information from the payer via the specified communications link, generating an electronic data token representing the financial account information, outputting the electronic data token for transmittal to the first computing system (where the first computing system does not receive the financial account information and the second computing system does not provide the electronic data token to the payer), obtaining the amount from the payer using the financial account information, and forwarding at least a portion of the amount to the payee.

Abstract: Processing a payment from a payer to a payee (operating a first computing system), by a second computing system, by receiving an electronically-generated payment transaction instruction (identifying the payer, specifying the amount of the payment, and specifying a communications link for the second computing system to obtain financial account information from the payer) from the first computing system, obtaining the financial account information from the payer via the specified communications link, generating an electronic data token representing the financial account information, outputting the electronic data token for transmittal to the first computing system (where the first computing system does not receive the financial account information and the second computing system does not provide the electronic data token to the payer), obtaining the amount from the payer using the financial account information, and forwarding at least a portion of the amount to the payee.

Abstract: A session to enroll customers to make payments has two stages, a first stage completed on the telephone or on a merchant or debt collector website, and a second stage completed via a communications link such as a telephone or Internet link. The customer enrollment record is linked to financial account information received from the customer in the second stage and stored on a second, secure server. A token linked to the securely stored financial account information is returned to the merchant and then used by the merchant to initiate payments on that financial account. The merchant's personnel and customer record system do not store or have access to the underlying financial account information.

Abstract: A session to enroll customers to make payments has two stages, a first stage completed on the telephone or on a merchant or debt collector website, and a second stage completed via a communications link such as a telephone or Internet link. The customer enrollment record is linked to financial account information received from the customer in the second stage and stored on a second, secure server. A token linked to the securely stored financial account information is returned to the merchant and then used by the merchant to initiate payments on that financial account. The merchant's personnel and customer record system do not store or have access to the underlying financial account information.

Abstract: A session to enroll customers to make payments has two stages, a first stage completed on the telephone or on a merchant or debt collector website, and a second stage completed via a communications link such as a telephone or Internet link. The customer enrollment record is linked to financial account information received from the customer in the second stage and stored on a second, secure server. A token linked to the securely stored financial account information is returned to the merchant and then used by the merchant to initiate payments on that financial account. The merchant's personnel and customer record system do not store or have access to the underlying financial account information.