•

APIs that enable two-way exchange of data between electronic forms and database records into databases, including calling and using translator programs (these APIs would allow the automatic fill-in of electronic forms from databases, and the update of database records from electronic forms);

•

APIs, where possible, complying to a plug-in/plug-out model that enables embedding and transmission of electronic forms and documents into e-mail messages, automatic conversion of these e-mail messages into their original format at the receiver site, and subsequent processing of the forms/ documents;

•

APIs that allow data from an electronic form or document to be transmitted from sender to receiver as a database record update or file transfer via FTP;

•

APIs between translators that can translate electronic forms into database commands and/or electronic commerce remote procedure calls, and vice versa;

•

APIs that define operations such as writing, reading, certifying, authenticating, and transporting of bill and payment objects; and

•

APIs that link electronic orders and electronic form messages with electronic payment messages and exchanges.