RFC 3867: Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)
In plain English — editorial summary, not part of the RFC
The Internet Open Trading Protocol (IOTP) provides a data exchange format for trading purposes while integrating existing pure payment protocols seamlessly. This motivates the multiple layered system architecture which consists of at least some generic IOTP application core and multiple specific payment modules. This document addresses a common interface between the IOTP application core and the payment modules, enabling the interoperability between these kinds of modules. Furthermore, such an interface provides the foundations for a plug-in-mechanism in actual implementations of IOTP application cores. Such interfaces exist at the Consumers', the Merchants' and the Payment Handlers' installations connecting the IOTP application core and the payment software components/legacy systems. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3867
- Published
- November 2004
- Authors
- Y. Kawatsura; M. Hiroya; H. Beykirch
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 106
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9239Updates to ECMAScript Media TypesCurrent
May 2022
- RFC 3863Presence Information Data Format (PIDF)Current
August 2004
- RFC 3862Common Presence and Instant Messaging (CPIM): Message FormatCurrent
August 2004
- RFC 3861Address Resolution for Instant Messaging and PresenceCurrent
August 2004
- RFC 3860Common Profile for Instant Messaging (CPIM)Current
August 2004
- RFC 3859Common Profile for Presence (CPP)Current
August 2004
- RFC 3876Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)Current
September 2004
- RFC 3885SMTP Service Extension for Message TrackingCurrent
September 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?