Internet Open Trading Protocol (IOTP) Codes

Created

  • 2000-04

Last Updated

  • 2012-02-02

Expert(s)

  • David Burdett

Available Formats

Algorithm/Name

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Unassigned

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Note

When Algorithm is a child of an AuthReq Component. Further information see Section 12.1 in the RFC.

Available Formats

Attribute Values Reference
"sha1" Indicates that a [SHA1] authentication will apply RFC 2801
"signature" Indicates that authentication consists of the generation of a digital signature. RFC 2801
"Pay:ppp" Where "ppp" may be set to any valid value for "iotpbrand" RFC 2801

Brand/BrandId

Registration Procedure(s)

  • First Come First Served

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Note

IETF Trade mailing list for three weeks

Available Formats

Brand/BrandID Organization Contact Person/E-mail address Reference
"Amex" American Express RFC 2801
"Dankort" Dankort RFC 2801
"JCB" JCB RFC 2801
"Maestro" Maestro RFC 2801
"MasterCard" MasterCard RFC 2801
"NICOS" NICOS RFC 2801
"VISA" Visa Tony Lewis RFC 2801
"atCredits" @UK PLC Ronald_Duncan_ukplc RFC 2801
"EZpay" ITI Services Admin_itinternet_net RFC 2801
"GeldKarte" GeldKarte RFC 2801
"Mondex" Mondex RFC 2801
"paybox" paybox.net AG guillaume_taglang_pa RFC 2801

CurrencyAmount/CurrCode

Registration Procedure(s)

  • First Come First Served

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Note

IETF Trade mailing list for three weeks

Note

Currency codes are dependent on CurrCodeType (see below).

CurrencyAmount/CurrCode Reference
No registrations at this time.

CurrencyAmount/CurrCodeType

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Unassigned

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Note

New values of CurrCodeType attribute are allocated following review on the IETF Trade mailing list and by the Designated Expert.

Available Formats

CurrencyAmount/CurrCodeType Reference
"ISO4217-A" RFC 2801
"IOTP" RFC 2801

DeliveryData/DelivMethod

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Unassigned

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

DeliveryData/DelivMethod Reference
"Post" RFC 2801
"Web" RFC 2801
"Email" RFC 2801

PackagedContent/Content

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Unassigned

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

PackagedContent/Content Reference
"PCDATA" RFC 2801
"MIME" RFC 2801
"MIME:mimetype" (where mimetype must be the same as content-type as defined by [MIME] ) RFC 2801
"XML" RFC 2801

RelatedTo/RelationshipType

Registration Procedure(s)

  • Expert Review

Expert(s)

  • Unassigned

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

RelatedTo/RelationshipType Reference
"IotpTransaction" RFC 2801
"Reference" RFC 2801

Status/StatusType

Registration Procedure(s)

  • RFC Required

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

Status/StatusType Reference
Offer RFC 2801
Payment RFC 2801
Delivery RFC 2801
Authentication RFC 2801
Unidentified RFC 2801

TradingRole/Trading Role

Registration Procedure(s)

  • RFC Required

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

TradingRole/Trading Role Reference
"Consumer" RFC 2801
"Merchant" RFC 2801
"PaymentHandler" RFC 2801
"DeliveryHandler" RFC 2801
"DelivTo" RFC 2801
"CustCare" RFC 2801

TransId/IotpTransType

Registration Procedure(s)

  • RFC Required

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Available Formats

TransId/IOtpTransType Reference
"BaselineAuthentication" RFC 2801
"BaselineDeposit" RFC 2801
"BaselinePurchase" RFC 2801
"BaselineRefund" RFC 2801
"BaselineWithdrawal" RFC 2801
"BaselineValueExchange" RFC 2801
"BaselineInquiry" RFC 2801
"BaselinePing" RFC 2801

Attribute/Content

Registration Procedure(s)

  • RFC Required

Reference

  • RFC 2801: Internet Open Trading Protocol - IOTP Version 1.0

Note

see Signature Component

Available Formats

Attribute/Content Reference
"OfferResponse" RFC 2801
"PaymentResponse" RFC 2801
"DeliveryResponse" RFC 2801
"AuthenticationRequest" RFC 2801
"AuthenticationResponse" RFC 2801
"PingRequest" RFC 2801
"PingResponse" RFC 2801

Contact Information

Name Contact URI Last Updated
Admin&itinternet.net
Ronald.Duncan&ukplc.net
Tony Lewis TLewis&visa.com
guillaume.taglang&paybox.net