SELECTING PAYMENT MECHANISMS OVER HTTP Or, Seven Examples of UPP Over PEP (as used in JEPI)
draft-khare-jepi-uppflow-00

Document Type Expired Internet-Draft (individual)
Last updated 1996-08-19
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-khare-jepi-uppflow-00.txt

Abstract

The Joint Electronics Payment Initiative aims to bring key industry players together to assure that multiple payment protocols can operate effectively in Web applications. The concrete goal is automatable payment selection over HTTP. The first step towards this was Don Eastlake's development of the Universal Payment Preamble, which is also available as an internet-draft (draft-eastlake-universal-payment). The second is the development of an HTTP Extension Protocol to embed UPP in HTTP. The latter proposal is part of the chartered activities of the IETF HTTP G (draft-ietf-http-pep-03). This document describes how to use UPP over PEP to support payment selection between clients and merchants. It explains basic operations: requesting available payment choices, presenting multiple choices, demanding a selection, making a selection, and accepting and rejecting choices.

Authors

Donald Eastlake (Donald.Eastlake@motorola.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)