Provide PDF Format
X9 X9.59-2006
- Electronic Commerce for the Financial Services Industry: Account Based Secure Payments Objects
- standard by Accredited Standards Committee X9 Incorporated, 05/24/2006
- Publisher: X9
$50.00$100.00
1 Scope
This standard addresses the following:
A) Payment Model Description
This standard describes a model of account based electronic payments. It identifies the roles played bydifferent components of the payment process and the flow of information between those roles. The roles arethe consumer, who wishes to make a payment, a merchant which provides value, and their respectiveFinancial Institutions, the consumer financial institution and the merchant financial institution.
B) Secure Object Specifications
This standard specifies a collection of electronic payment objects and references digital signature techniquesto secure their content. The objects are all defined in terms of how they need to be constructed, signed andverified in computing machinery that is acting on behalf of a consumer and a merchant. A concrete syntax isspecified in order that the signature can be constructed or verified at any location that has access to theconsumer's public key and associated data. A business recommendation is made that the payment routingcode (or PAN) used in conjunction with secure payment objects defined by this standard is not accepted asvalid in non-authenticated transactions. Several usage scenarios are given to show examples of realapplications where the standard objects may be applicable.
Confidentiality for the payment information may be desired and is neither required, nor precluded, by thisstandard. Prudent implementers may choose to conduct a risk assessment to determine the need forconfidentiality. Also policy issues, including terms and conditions of the agreements between the parties, are notcovered in this standard. . While some of the information described in the standard must survive interchangebetween cooperating financial institutions, the syntax of how it appears in any particular payment protocol is notspecified.
This standard addresses the following:
A) Payment Model Description
This standard describes a model of account based electronic payments. It identifies the roles played bydifferent components of the payment process and the flow of information between those roles. The roles arethe consumer, who wishes to make a payment, a merchant which provides value, and their respectiveFinancial Institutions, the consumer financial institution and the merchant financial institution.
B) Secure Object Specifications
This standard specifies a collection of electronic payment objects and references digital signature techniquesto secure their content. The objects are all defined in terms of how they need to be constructed, signed andverified in computing machinery that is acting on behalf of a consumer and a merchant. A concrete syntax isspecified in order that the signature can be constructed or verified at any location that has access to theconsumer's public key and associated data. A business recommendation is made that the payment routingcode (or PAN) used in conjunction with secure payment objects defined by this standard is not accepted asvalid in non-authenticated transactions. Several usage scenarios are given to show examples of realapplications where the standard objects may be applicable.
Confidentiality for the payment information may be desired and is neither required, nor precluded, by thisstandard. Prudent implementers may choose to conduct a risk assessment to determine the need forconfidentiality. Also policy issues, including terms and conditions of the agreements between the parties, are notcovered in this standard. . While some of the information described in the standard must survive interchangebetween cooperating financial institutions, the syntax of how it appears in any particular payment protocol is notspecified.