Here''s an example of the changes that ECML will require on your HTML forms.
Before:
<INPUT type="text" name="Credit_Card_Number" size=19>Credit Card Number
After:
<INPUT type="text" name="Ecom_Payment_Card_Number" size=19>Credit Card Number
That''s all there is to it!
The specification also defines a common taxonomy for ship-to information, bill-to information, receipt information, payment card information, and schema version information.
By implementing changes of this nature on your HTML forms and your CGI or ASP scripts, you''ll gain all the initial benefits of ECML while maintaining complete control over all other aspects of your operation. The standard was designed for independence from security mechanisms, payment instrument implementation details, and transport protocols. ECML is not intending to compete with any other related processes or protocols such as SSL, SET, or the XML-based payment mechanisms. Rather, ECML may be used in conjunction with one or more these mechanisms, providing degrees of interoperability not commonly found today.
Implementation notes, also found in the specification, can help to clarify and further the standardization of the contents of form fields, including date formats, credit card issuer names, country names, etc.
ECML For The Future
ECML is built with evolution in mind. As it evolves, it will likely provide support for:
- Corporate purchasing cards
- Other payment systems
- Travel and Entertainment related data (preferences, etc.)
- Affinity, frequent flyer, and customer loyalty programs
- Business-to-business electronic commerce
Future support for Merchant to Consumer data feeds may include:
- Total purchase amounts (including taxes, shipping and handling charges, etc.)
- Receipt information
- Package tracking information
- Merchant-specific attributes
The developers of ECML also expect that an XML-based schema will be developed to help standardize its use where XML has already taken root.
You can help in defining future needs and uses of ECML by contacting the coordinator at ecml.org. Once ECML is deemed sufficiently mature, its supporters intend to turn it over to the World Wide Web Consortium (W3C) or the Internet Engineering Task Force (IETF) where it can be maintained and promoted throughout the world.
Over the last year or so, we''ve used up lots of ink on the topic of electronic wallets. As ECML advances in form, function, and adoption, many of the concerns that were raised by earlier industry efforts may finally be put to rest for all time.
IE 7
Firefox 2.0
