RFC 4154: Voucher Trading System Application Programming Interface (VTS-API)
In plain English — editorial summary, not part of the RFC
This document specifies the Voucher Trading System Application Programming Interface (VTS-API). The VTS-API allows a wallet or other application to issue, transfer, and redeem vouchers in a uniform manner independent of the VTS implementation. The VTS is a system for securely transferring vouchers; e.g., coupons, tickets, loyalty points, and gift certificates. This process is often necessary in the course of payment and/or delivery transactions. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4154
- Published
- September 2005
- Authors
- M. Terada; K. Fujimura
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4918HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)Updated
June 2007
- RFC 2980Common NNTP ExtensionsUpdated
October 2000
- RFC 5336SMTP Extension for Internationalized Email AddressesObsoleted
September 2008
- RFC 2936HTTP MIME Type Handler DetectionCurrent
September 2000
- RFC 2935Internet Open Trading Protocol (IOTP) HTTP SupplementCurrent
September 2000
- RFC 2577FTP Security ConsiderationsCurrent
May 1999
- RFC 2518HTTP Extensions for Distributed Authoring -- WEBDAVObsoleted
February 1999
- RFC 2310The Safe Response Header FieldCurrent
April 1998
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?