Electronic Commerce Modeling Language
Electronic Commerce Modeling Language (ECML) is a protocol which enables the e-commerce merchants to standardize their online payment processes. Through the application of ECML, customers' billing information in their digital wallet can be easily transferred to fill out the checkout forms.[1]
There are various companies that have participated in ECML's alliances, including American Express and Mastercard.[1]
As a standard developed by the alliance, ECML has solved the problem of complex and confusing online manual payments caused by diverse web designs, and further reduces the chance of customer dropout (also called shopping cart abandonment).[1] On the other hand, ECML deals with sensitive information such as credit card numbers and home addresses -- its data security is controversial, and privacy considerations should be taken. [2][3]
Alliances
The members of ECML Alliance listed in alphabetical order below:[1]
- American Express (www.americanexpress.com>
- AOL (www.aol.com)
- Brodia (www.brodia.com)
- Compaq (www.compaq.com)
- CyberCash (www.cybercash.com)
- Discover (www.discovercard.com)
- FSTC (www.fstc.org)
- IBM (www.ibm.com)
- Mastercard (www.mastercard.com)
- Microsoft (www.microsoft.com)
- Novell (www.novell.com>
- SETCo (www.setco.org)
- Sun Microsystems (www.sun.com)
- Trintech (www.trintech.com>
- Visa International (www.visa.com)
ECML and Customer Dropout Behaviors
Customer dropout is also called shopping cart abandonment -- it is a type of behavior which customers display inclination of purchase without completing the final payment. According to a commercial study, there is a rate 25% to 75% that the customer would abandon a transaction before it is completed due to various reasons.[4] Aside from motivational factors such as customer's fundamental needs and spontaneous purchases, emotional factors such as irritation and disappointment also determine whether a transaction would be successful. Research has shown that payment inconvenience and perceived wasting time are factors that would contribute to customer's irritation.[4]
Electronic Commerce Modeling language could potentially decrease customer irritation in two ways, and further benefit the industry of electronic commerce as a whole. First of all, it provides a standardized set of information fields which would improve the manual process of online payment. Entering relevant information into the checkout form would become an easier task for customers. Secondly, ECML allows a smooth information transfer between customer's digital wallet and e-commerce checkout form. Information does not has to be manually entered into the system. [1]
Privacy Considerations and Suggestions
Electronic Commerce Modeling Language is consistent with Platform for Privacy Preferences (P3P),[5] a controversial protocol which addresses online privacy concern. Initially, P3P is designed to simplify users' access and understanding on privacy policies posted on the websites. It has employed a multiple choice format to make connections between human readable privacy notices and privacy policies, as well as offering agents conduct policy evaluations.[2] On the other side, some studies have also argued that P3P has made users' private information more vulnerable.[3] The platform is accused for its exclusive nature that would disadvantage non-compliant websites with good privacy practices, and its lack of privacy policies' enforcements.[3]
Although the developers of electronic commerce modeling language have not explicitly specified how the information can be safely stored and protected, object security protocols (include XML encryption and XMLDsig), and channel security are all possible ways of privacy protection.[6]
Since ECML is an application related with sensitive information such as credit card numbers and home addresses. Privacy considerations thus have became crucial. There are several suggestions listed below to protect customer's privacy:[1][6]
- ECML memory of sensitive information cannot exist. If it is installed on a public terminal, the wallet has to be configurable.
- A password should be set up and required each time when the user wants to access the stored information.
- Users need to have control of whether the stored sensitive information is released or not.
See Also
Platform for Privacy Preferences
References
- ^ a b c d e f Goldstein <tgoldstein@brodia.com>, Ted. "ECML v1.1: Field Specifications for E-Commerce". tools.ietf.org. Retrieved 2020-10-29.
- ^ a b Cranor, L.F. (2003). "P3P: making privacy policies more useful". IEEE Security & Privacy. 1 (6): 50–55. doi:10.1109/msecp.2003.1253568. ISSN 1540-7993.
- ^ a b c "Pretty Poor Privacy: An Assessment of P3P andInternet Privacy". epic.org. Retrieved 2020-10-31.
- ^ a b Bell, Lynne; McCloy, Rachel; Butler, Laurie; Vogt, Julia (2020-07-03). "Motivational and Affective Factors Underlying Consumer Dropout and Transactional Success in eCommerce: An Overview". Frontiers in Psychology. 11. doi:10.3389/fpsyg.2020.01546. ISSN 1664-1078. PMC 7351522. PMID 32714258.
{{cite journal}}: CS1 maint: unflagged free DOI (link) - ^ "RFC 3505 - Electronic Commerce Modeling Language (ECML): Version 2 Requirements". datatracker.ietf.org. Retrieved 2020-10-31.
- ^ a b Eastlake 3rd <donald.eastlake@motorola.com>, Donald E. "Electronic Commerce Modeling Language (ECML) Version 2 Specification". tools.ietf.org. Retrieved 2020-11-05.
{{cite web}}: CS1 maint: numeric names: authors list (link)