Roger Clarke's Web-Site


© Xamax Consultancy Pty Ltd,  1995-2016

Roger Clarke's 'Mobile Payments Risk Assessment Framework'

A Risk Assessment Framework for Mobile Payments

Roger Clarke **

Preprint of 17 April 2008

Proc. 21st Bled eCommerce Conf., June 2008, pp. 63-77

© Xamax Consultancy Pty Ltd, 2008

Available under an AEShareNet Free
for Education licence or a Creative Commons 'Some
Rights Reserved' licence.

This document is at

The accompanying slide-set is at


Progress in Mobile Commerce is heavily dependent upon effective and reliable payment mechanisms. Security concerns loom as a major impediment to widespread and rapid adoption, and there is accordingly an urgent need for a framework within which security issues in mobile commerce can be evaluated. This paper draws on lessons from prior payment mechanisms in order to present such a framework. It provides insights into the use of the framework by performing a test application. Implications for policy, practice and research are drawn.


1. Introduction

A variety of mobile technologies and mobile services have emerged during the last two decades. The term M-Commerce was adopted by marketers in the late 1990s, and predictions were made of rapid growth in the volume of commerce conducted through mobile devices. Recklies (2001) reported a Boston Consulting Group prediction that "global M-Commerce sales" would rise rapidly to $20bn in 2001, $60bn in 2002 and $100bn in 2003. The guesses of other consultants were wildly different. For example, Vrechopoulos et al. (2002) said that "According to Jupiter Research (2001), the global m-commerce revenues will reach $22.2 billion in 2005". See also (2002).

By 2004, Jupiter Research had become vastly more optimistic, offering "Global mCommerce Revenue Projections for 2009" of $426 billion, most of it in "phone-based retail POS sales" (2002). On the other hand, the slow growth had led other organisations to offer much more circumspect prognostications, e.g. "2006 will continue to see the development of experiential mobile applications and the emergence of m-commerce services, increasing in reach and importance over the next two years" (Atos 2005, p. 12). Juniper Research remains unabashed, and was quoted in early 2008 as forecasting that "over 612 million mobile phone users would generate over $US587 billion ... worth of financial transactions by 2011" (Moses 2008).

Despite one or two consultancy groups' wild enthusiasm, the growth of M-Commerce has a very patchy record. One major concern is that the risk of financial loss acts as an impediment to the adoption of mobile commerce. This may be because of widespread knowledge of actual losses, or reports of vulnerabilities, or just from uninformed concerns and natural risk-aversion. In order to understand the substance of the issue, and to avoid unnecessary delays in mobile service adoption, it is highly advisable that payment schemes intended for use in mobile contexts be subjected to risk assessment.

As with any form of trading, M-Commerce involves multiple steps, including partner discovery, information exchange, negotiation, contracting, delivery and settlement. The settlement step necessitates considerably greater care than the others, because the payments process creates considerable opportunities for funds to be stolen, with low likelihood of the thief being apprehended or the proceeds recovered, and with the possibility that the victim may not even be aware that the theft has occurred.

The term 'mobile payments' is used in this paper to refer to any payment that is conducted by means of a mobile access device and wireless network connection. By 'mobile access device' is meant 'any device that provides users with the capacity to participate in transactions with adjacent and remote devices by wireless means'. Such devices comprise at least a processor, systems software, application software and wireless communications capability. They are commonly also capable of at least some forms of physical interaction with one or more storage devices such as magnetic disks, CDs, DVDs, and solid-state tools (e.g. 'thumb drives' or 'memory sticks' or, currently, 'USB sticks').

In 2008, relevant mobile access devices fall into the following categories:

In general, transactions from desktops and portable PCs are excluded from this analysis, even if conducted over a wireless network connection. It may, however, be appropriate to include within the scope the nomadic use of portables, e.g. transactions conducted on the move, in aircraft, trains and cars.

Relevant transmission means include:

Mobile payments using such devices over such networks may be made in a variety of circumstances (Pousttchi 2003), including:

A considerable technical literature exists, but it is characterised by enthusiasm and narrow focus. Typical of the approach adopted is Herzberg (2003), which focusses on the links and flows between providers, and makes unjustified assumptions about the links and flows between users' devices and providers. Many of the infrastructural features assumed in this literature have not been deployed, or have been deployed but not adopted. In addition, industry coalitions have published technical specifications, such as MPF (2006). But these lack clear requirements statements against which specific designs and implementations can be assessed.

In a survey of papers published in the IS literature between January 2000 and September 2004, Scornavacca et al. (2005) found only 4 of 253 articles that addressed security. By the end of 2007, the specialist M-Business literature index at Scornavacca (2007) contained over 1,100 references, of which 30 had 'security' in the title, 33 had 'payment' in the title, but only one had both (Linck et al. 2006). Dahlberg et al. (2007) identified three that "discussed technologies in terms of m-payment security", three that "proposed new tools or mechanisms to improve security", and a further four papers of an empirical nature that dealt with security topics. Lee et al. (2004) includes several chapters on the security of mobile transactions. A limited amount of attention has also been paid to it in adjacent literatures, e.g. Choi et al. (2006).

Many authors have considered mobile payments from a technical perspective, but far less attention has been paid to practical application, security aspects, and acceptability by the users of mobile devices. See, however, Rawson (2002) which considered legal aspects of mobile transactions, Pousttchi (2003) and Kreyer et al. (2003) which discussed security as one among many factors in the adoption of mobile commerce, and Zmijewska (2005). Based on an empirical study, van der Heijden H. (2002) found that "security was emphasized, both for merchants and for consumers, but it was usually framed in a factor that can best be described as 'perceived risk'". Misra & Wickramasinghe (2004) proposed a 'trust model' for mobile commerce generally.

The purpose of this paper is to present a framework within which risk assessment of mobile payment arrangements can be undertaken. It commences by reviewing the experiences of payment mechanisms that have been used both prior to the emergence of open, public networks and more recently. This provides a basis on which a framework can be developed which reflects the technical and commercial infrastructure, and the relevant categories of harm, threats, vulnerabilities and safeguards. A report is provided of a small test application of the framework. Implications are drawn for policy, practice and research.

2. Payment Mechanisms

A rich set of payment mechanisms exists, reflecting the enormously varied circumstances in which people and organisations conduct transfers of value. The designs of these mechanisms also reflect the risks that the circumstances embody. It is strongly advisable that mobile payment schemes take into account the accumulated knowledge about risks and risk management. This section accordingly provides a brief catalogue of payment mechanisms, and then draws some inferences of significance for the security of mobile payments.

2.1 A Catalogue of Payment Mechanisms

Barter was an early form of reciprocal exchange of value. The conduct of trade transactions was greatly facilitated by the emergence of general-purpose items that had the characteristic of 'fungibility' or commonly-accepted value-in-exchange. Davies (2002) provides a history of money.

Many other schemes have emerged over the centuries. Banking services emerged, as deposits were placed with trusted parties, and instructions given to them to transfer value from those deposits to another party. This was extended to the borrowing of funds, and to instructions given to the lender to deliver value to another party, and increase the balance on the loan account. Histories of banking suggest that these practices were well-established by the time of the Ancient Greeks, some centuries BCE. An index of publications on contemporary payment systems is maintained at RBA (2007). Descriptions of the payment systems in countries around the world are available at BIS (2007).

Exhibit 1 identifies major payment mechanisms that have emerged during various phases prior to and during the electronic era. An endeavour has been made to use terms in at least broad correspondence with the Glossary published by the Bank for International Settlements (BIS 2003).

Exhibit 1: Payment Mechanisms

Pre-Electronic Payment Mechanisms

Early Electronic Payment Mechanisms

Wired Payment Mechanisms

Unwired Payment Mechanisms

A particular characteristic of payment schemes that is often overlooked is the question of the identifiability of the parties. Barter and cash payment systems are inherently anonymous (although of course other aspects of the transaction may identify either or both transacting parties). Most other payment mechanisms carry at least some form of identifier, which may enable the transaction to be associated with a particular natural or legal person. The parties may, however, be pseudonymous, if there are significant barriers to be overcome in order to establish the association. Electronic payment mechanisms have the potential to generate a comprehensive and intensive record of a person's transactions, and even of the person's movements. Designers who fail to reflect the interests of payees, and particularly payers, in avoiding the creation of such dangerous data, create impediments to adoption.

The following section briefly extracts some lessons from prior payment mechanisms.

2.2 Lessons for the Security of Mobile Payments

A breakthrough application in the use of large-scale data networks was Automated Teller Machines (ATMs, called by various names in various countries), which became widespread during the early 1980s. ATMs are not a payment mechanism in themselves, because their primary and still dominant usage is for the withdrawal of cash. They are important to the discussion for two reasons.

The first is that they embodied a relatively quite robust security design. They involve two-factor identification ('have' a card and 'know' the PIN); the PIN is keyed in a manner that makes observation reasonably difficult; the design ensures that the PIN is not accessible outside the secure PIN-pad and/or a secure device on the financial institution's premises; and hence the authenticator is protected from both physical and electronic observation.

The second reason ATMs are important is that they paved the way for EFTPOS schemes (Electronic Funds Transfer at Point of Sale). These automated the capture and validation of debit-card transactions at merchants' points of sale, resulting in charges against the account-holder's deposit with their financial institution (Clarke & Walters 1989, Clarke 1990, 1992). Debit EFTPOS embodied similarly strong security features to those used in ATM systems.

The scope of EFTPOS was rapidly extended to the capture of credit-card transactions. This used far less secure arrangements, however, because no PIN was required. The primary purpose was the transfer of data capture costs to the merchant. The security improvements were largely limited to the automation of processes for checking stop-lists of cancelled credit-card numbers - although the lists may as a result be somewhat less out-of-date.

ATM and EFTPOS networks are closed, and people's interactions with them are tightly controlled. The same is not true of the open, public Internet that became available from about 1993 and that ushered in what is now commonly referred to as the 'Wired' era. Key differences were:

With closed payment systems, transactions at point-of-sale required presentation of the card, and production of a signature that could be matched against the previously-recorded signature on the back of the card; whereas in Mail-Order-Telephone-Order (MOTO) / Card-Not-Present transactions that safeguard was completely missing.

The use of credit-cards on the Internet adopted the MOTO model, and hence two-factor authentication was reduced to single-factor, because there is no requirement that the payer demonstrate that they 'know a secret'. Moreover, the 'have' factor is reduced from 'have the card' to 'have the details recorded on the card'. The MOTO model, as applied to Wired-Era Payments, is based on the pretence that credit-card details are in some way protected. It relies on:

An attempt was made during the late 1990s to impose stronger safeguards. The Secure Electronic Transactions (SET) initiative involved three-way authentication, but foundered in the marketplace (see for example Clarke 1996b). Since 2000, another attempt is being made, in the form of 3-D Secure, a Visa initiative branded as 'Verified by Visa', and cross-licensed to MasterCard as SecureCode' and to JCB as J/Secure (Visa 2008). It requires some kind of authentication of the payer's claim to be the cardholder; but it does not specify what form authentication should take, and adoption has been slow.

Internet Banking involves an account-holder with a financial services organisation conducting transactions on their account from an Internet-connected device. It took some years to emerge as a reliable and accepted service, to a considerable extent because of the need for a security design with at least the same level of robustness as ATMs and debit-card transactions via EFTPOS terminals. The threat profiles change rapidly, and safeguards are in a state of flux. Conventional two-factor authentication is increasingly considered to be inadequate, because the PIN is keyed into an insecure key-pad on an insecure access device. Three-factor schemes are being increasingly implemented. These commonly feature one-time passwords extracted from an electronic token (often carried on a key-ring) or delivered through an 'out of band' channel such as an SMS message.

Debit transactions over the Internet are emerging as an extension to Internet Banking. For example, the Canadian Interac Online service re-directs the payer to their bank, and the payment instruction is captured within the bank's Internet Banking environment. This leverages well-trusted infrastructure, but requires careful interfacing between the web-based applications of very large number of merchants and moderate numbers of financial services organisations.

The transition into the 'Unwired' / M-Commerce era brings with it further changes. These include:

As credit-card transactions migrate into the mobile context, all of the issues with MOTO transactions arise, and are joined by additional threats and vulnerabilities. The much more responsible approaches involving Internet Banking, debit-card transactions linked to Internet Banking and even credit-card transactions with authentication, are not as severely deficient, but they still involve additional risks when used in a mobile context. The framework proposed below reflects lessons such as these, that have been learnt from prior payment mechanisms.

3. The Framework

This section expresses a framework intended to assist in defining and addressing the risk profiles of the unwired payment mechanisms that underpin M-Commerce. Risk assessment is an established business process, and is described in text-books (e.g. Peltier 2005, Landoll 2005, Slay & Koronios 2006) and industry standards (e.g. AS/NZS 3931-1998, AS/NZS 4360-1999 and the long-promised ISO 27005 standard that is currently scheduled to emerge in 2009 to complement the foundation Information Security Management Systems standards ISO 27001 and 27002).

In order to perform a risk assessment, it is necessary to establish a sufficiently deep appreciation of a range of aspects of the relevant infrastructure, processes and contexts. The framework proposed here reflects the 'trust model' of Misra & Wickramasinghe (2004), but it is more comprehensive, and is specifically focussed on payments. The framework comprises the following dimensions, which are represented in diagrammatic form in Exhibit 2:

Exhibit 2: A Risk Assessment Framework for Mobile Payments

3.1 The Security Model

The conventional computer security model is adopted in this paper (e.g. Clarke 2001a, OECD 2002, ISO 2005). Under this model, threatening events impinge on vulnerabilities to cause harm. Safeguards are used in an endeavour to protect against threats and overcome vulnerabilities, in order to deter, prevent, detect, investigate or ameliorate the events or the harm. Security is a condition in which harm does not arise, because threats and vulnerabilities are countered by safeguards.

More fully:

3.2 The Technical Architecture Aspect

The purpose of the technical architecture model is to identify the physical locations and components and the inter-relationships among them, which together make up the relevant technical infrastructure. Because of the considerable diversity in mobile services, a single definitive model is not feasible. This section accordingly sets out to provide a comprehensive catalogue of elements, supported by an indicative diagram in Exhibit 3.

The relevant infrastructural elements are as follows:

Exhibit 3: An Indicative Technical Architecture Model

3.3 The Commercial Architecture Aspect

The purpose of the commercial architecture model is to identify the relevant categories of natural and legal persons, their interests, the interactions among them, and their legal rights and duties, particularly those arising under commercial law including contract.

According to Slay & Koronios (2006), the Internet Online Trading Protocol (IOTP) framework classifies five roles: customer (i.e. payer), seller (i.e. payee), payment handler, delivery handler and customer support. However, this is too limited for the more complex patterns that are already evident in Internet payment systems. Many more categories of actors are directly involved, including Internet access providers, carriage service providers, commercial intermediaries (such as Paypal), transaction service providers (such as banks and credit-card companies), and payment services providers (such as deposit-holders, lenders and insurers). Yet more actors may need to be considered, such as regulators, complaints bodies such as financial services ombudsmen, and consumer rights representative and advocacy organisations. Moreover, consumers may need to be segmented rather than treated as a single category, e.g. to separate out the particular interests of the mobility-disadvantaged and the sight-impaired, and to reflect the needs of people with limited financial assets, particularly those who have no credit-card.

When undertaking a risk assessment, a clear understanding is needed of the laws, policies and practices that apply to the categories of mobile transaction under consideration. The study may need to extend across multiple jurisdictions.

In some circumstances, there may also be a need to allow for the organisational context within which the access device is used. Employers may see it as being to their advantage to assist their employees to protect themselves, because they are very likely to conduct company and personal business on the same device. Support of a similar kind may be available from computer clubs, and may be able to be acquired from suppliers of consumer devices and related services, perhaps as an extension to the basic services package. Locations that make network connections available for free or for fee (such as libraries, Internet cafés, and coffee-shops that operate Wifi 'hot-spots') may provide protections. On the other hand, the access networks in such locations may lack protections that the consumer might assume to be in place; and they may even be set up by the operator or a third party to create opportunities for mis-deeds.

The Editor of the specialist journal Computing & Security commented in May 2007, that "Mobile computing presents serious security challenges in part because mobile workers are physically removed from the immediate control of organizations' security staff. ... Furthermore, many security controls that are in effect when users connect to an organization's network from a location within the workplace are not likely to be in effect when users engage in mobile computing while on travel or at home. ... Mobile users also create new entry points into networks. ... When risks related to "shoulder surfing" are also taken into account, it is impossible to conclude anything else but that mobile computing is becoming downright dangerous" (Schultz 2007).

3.4 The Transaction Process Aspect

In order to undertake a risk assessment of a mobile payment service, it is essential that a sufficient appreciation be gained of the mechanisms involved. A wide variety of modelling formalisms is available. An example of a simple overview diagram is in Exhibit 4.

Exhibit 4: A Sample Process Flow

From Herzberg (2003), p. 56

This has the advantage of enabling easy cross-referencing with the commercial architecture considered in the previous section. Commonly, there will be a need for both an overview of that nature and more detailed models, whether modelled using tools associated with procedure-oriented flowcharts, structured analysis and design such as Yourdon & deMarco or Gane & Sarson Data Flow Diagrams (DFDs), or object-oriented forms.

3.5 The Harm Aspect

Generically, categories of harm include:

In the current context, it is appropriate for the harm model to focus primarily on financial loss to users, and (under the commercial arrangements that exist within the credit-card system) to merchants, and to a lesser extent to card-issuers and transaction-processing organisations.

It is also necessary, however, to consider the perspective of the various service providers. The perception of unacceptable risk would be likely to result in non-adoption or slow adoption or abandonment (whether by consumers or by merchants), and hence low return on investment and even (as has occurred several times before) outright loss of the investment.

3.6 The Threat and Vulnerability Aspects

A threat is a circumstance that could result in harm, and may be natural, accidental or intentional. A vulnerability is a feature or weakness that gives rise to susceptibility to a threat. It is convenient to address both together in a single section.

Second-party threats arise from behaviour, or more particularly misbehaviour, by (from the payer's perspective) the payee. Categories include non-performance (such as failure to deliver or perform in accordance with the contract), and malperformance (such as late delivery or performance, the extraction of funds from the payer's account greater than that authorised or more often than was authorised, and slow and/or unsatisfactory response or outright non-response to enquiries and complaints).

Third party threats arise from organisations and individuals other than the payee, whose behaviour or misbehaviour accidentally or intentionally results in harm. Parties who intentionally cause harm, i.e. attackers, are usefully categorised into the following groups:

Checklists of threats and vulnerabilities relevant to mobile payments are provided in the following Appendices to this paper:

A great deal of research has been conducted by computer scientists into the interplay between access devices and the infrastructure that enables eCommerce and M-Commerce. On the other hand, far less consideration has been given to threats that arise from the physical contexts in which access devices are used.

Specific threats include the observation of authenticators, unnoticed and unauthorised use of the device, and possibly of authenticated sessions and processes that are running on it at the time. Categories of perpetrator include fellow householders, friends in social environments, and colleagues in work-environments - and perhaps cleaners, security staff, repairmen and supervisors if the device is left unattended and in a usable state. If the device's capabilities are abused, the authorised user may or may not be aware of it. Furthermore, there may or may not be a way in which the user, or someone acting on the user's behalf, may be able to discover that someone else has used it, and, if so, what for.

3.7 The Safeguards Aspect

Several categories of safeguard strategy need to be distinguished. Proactive strategies include avoidance and prevention, and deterrence. Less substantial but nonetheless of value are reactive strategies such as detection, recovery and insurance. Least effective are non-reactive strategies, i.e. self-insurance, 'taking the risk', or putting up with the harm done. An alternative structure for proactive and reactive strategies distinguishes 'before the fact', 'during the fact' and 'after the fact' approaches. Further conventional distinctions are between physical and logical protections; and among technological, organisational and legal measures.

Practical physical measures are not easy to contrive. Mobile devices are small, and in many cases 'always on', including to some extent at least even when the user thinks they have turned them off. Hardware-based protections such as locks and 'dongles' (tokens that must be inserted into ports on the device, in the absence of which the device is disabled) are expensive, inconvenient and impracticable for consumers juggling handhelds. All are subject to countermeasures by attackers. As a result, few consumer devices are subject to them.

Logical safeguards include:

Such measures vary greatly in their effectiveness. Many significantly reduce the scope for use of the device by unintended people, but they do not reliably prevent it, because all such logical security safeguards are subject to countermeasures. For example:

Generally, mobile access devices are subject to little in the way of logical security measures. Most users of handhelds are only vaguely aware of the threats, and do not appreciate the harm that could arise if colleagues or visitors use their devices. Few are aware of the available safeguards. Of those who are, many regard the benefits as being too uncertain to justify the inconvenience.

A variety of technological measures have been invented, such as message encryption, digital certificates and the authentication of transaction devices. A few have been deployed, and a very few are even used, but most are ineffective in practice (Clarke 2001b).

Some sets of authentication guidelines propose organisational safeguards based on risk assessment, such as dual-authority for transactions, the application of heuristics to detect risk-prone transactions, the maintenance of log-files, and the audit of log-files for patterns associated with inappropriate transactions. These may be applied where the payer is acting on behalf of a corporation or government agency, or even where they are doing personal business but using an access device or infrastructure provided by their employer. Individuals acting on their own behalf commonly do not have the benefit of such safeguards.

Legal safeguards may exist. In most jurisdictions, however, the expectations of consumers are very poorly supported by consumer protection laws (Clarke 2006). The terms of consumers' relationships with merchants and financial services providers are generally imposed by the corporation rather than negotiated, and serve its own needs far better than those of consumers. Moreover, very few jurisdictions have adapted their consumer protection laws to reflect the realities of mobile payment addressed in this paper. Indeed, financial institutions in at least some countries have been arguing for consumer protection to be reduced, including New Zealand (at this stage successfully) and Australia (so far unsuccessfully. See Clarke & Maurushat 2007).

4. Application of the Framework

In order to provide an initial test of the applicability of the framework, a sample threat / vulnerability / safeguard analysis was undertaken, and consideration given to the implications of the evaluation. To be a suitable candidate, a scheme needed to be sufficiently well-established and well-understood. It was also important that this initial test be conducted on a relatively simple scheme. Several current examples of mobile payment schemes were considered, including:

The scheme selected as the basis for the pilot was the Hong Kong Octopus Card. This is a contactless smartcard that is very widely used for public transport, particularly on the strongly patronised MTR - the urban underground railway system (Paynter & Law 2001, Chau & Poon 2003, Wikipedia 2008). It can also be used for parking meters, at some merchants, and in some vending machines, pay phones, photo booths and car parks. It has been operational since 1997. It is highly used. The scheme uses the Sony Felica smartcard, and was designed and project-managed by the Australian company ERG.

To make a payment, the card (which may be inside a wallet or purse) is waved within a few centimetres of a fixed reader. An audio-acknowledgement is provided (a 'beep' sound). A visual display is provided of the amount of the transaction and the remaining balance. In merchant applications, the display of the amount is available before the card is presented. In transport applications with distance-dependent fares, the card is presented at both entry to and exit from the transport system and the deduction and display occur at the exit-point. The balance and the amounts of the last ten transactions can be displayed at special terminals that are available in some locations. The fixed devices transfer transaction data to a central clearance location either real-time or in batch-mode overnight, using cryptographic techniques to authenticate the remote device and to protect the data during transmission.

Value reload is performed at some merchants and in fixed devices in train-stations. All devices accept cash, and many also accept debit-card transactions and credit-card transactions. Automatic top-up from a pre-registered credit-card is also available. With the exception of a couple of categories of low-volume identified cards, the card is a bearer-instrument, transactions using it are anonymous, the value on the card is cash-like, and hence a card-holder cannot recover the remaining value on a lost card, and a finder can use it.

In most applications, card-holders receive no receipt, and the only record of transactions is the ephemeral one on the card. They are forced to trust that the system is functioning preferably as they expect it to, but at least in accordance with the operator's specifications. They have no direct control over the amounts that are deducted from their card-balances by the fixed devices that they present their cards to, and have to trust that the display that they see is accurate. They are at risk of having amounts 'skimmed' from their cards through deductions higher than those which should be made. The amount that a fraudulent or erroneous scheme could skim from individual transactions is limited by such factors as the amounts on the cards and the detectability of a mis-match between actual balance remaining and that which the card-holder expected.

In transport applications, the card-holder has no opportunity to disagree with the amount displayed, because it has already been deducted. It is not clear whether the card authenticates the fixed device (although the scope for rogue devices is constrained because the card must be passed within a few centimetres of the reader). It is not clear whether any independent audit has been conducted of the scheme, and hence it would appear that card-holders must again simply trust the operator.

There appear to have been no suggestions that the inherent card-holder insecurity has been exploited by the operator or any third party. However, error is known to have occurred, at cost to card-holders. During 2007, it came to light that the reloading process had been mis-designed. When a transaction was commenced and then cancelled before completion, the card-holder's bank account was nonetheless debited but the card-balance was not incremented. This came to light only in 2007, despite the error having been made no later than 2000. The lateness of detection was despite 15,270 false deductions having been made during the 7 years for which records were available, for a total of $HK 3.7 million (about $US 0.5 million or Euro 0.32 million) (Wikipedia 2008). This represents an average of $HK 242 per transaction (about $US 32 or Euro 20). On the basis of the Hong Kong experience, it would appear to be inadvisable to assume either that consumers reconcile their bank accounts, or that banks will carefully investigate complaints about transactions involving relatively small amounts of money.

Several further inferences can be drawn from an application of the risk assessment framework to the Octopus Card. Little information about the architecture and business processes is available. Key assurance factors are the close proximity needed for value to be withdrawn from the card, and the apparently tight control over data flows between the collecting device and the central server. As regards the commercial architecture, there is little transparency concerning consumers' rights apart from a very limited ability to audit the effect of transactions on the card's remaining balance. The individual transactions are small, convenience is the dominant consideration, and there is a marked absence of credible accusations of fraud even after a decade of high-volume use. However, if any of the assurance factors were to be compromised, public confidence in the scheme could well sag. Otherwise, levels of use would appear likely to remain high until some even more attractive alternative is available.

The considerable success of the Octopus Card in Hong Kong, and of a related but differently structured scheme in Japan, is balanced by failure of stored value cards in Switzerland in the mid-1990s (Clarke 1998), and severe criticism of a U.K. scheme in 2008 (Leyden 2008). In both of the latter schemes, banks unilaterally replaced customers' magnetic-stripe cards with chip-bearing cards and included a service that many customers had not asked for, and were suspicious about.

Compared to predecessor forms, mobile payments involve less visible payees, less visible processes, and transaction data that, at the time of payment, is less visible and that, at a later time, may well not be visible at all. It would seem that some minimum standards may be needed in relation to the following:

There may even be a need to impose requirements on the architecture of schemes, in particular that access devices authenticate transacting devices before they enable their users to conduct transactions.

Compromise to the last three safeguards might be reasonable for very-low-value transactions. The reasonableness decreases rapidly, however, as the payer's exposure increases, both on a per-transaction and an aggregate basis. At some level of transaction-value, additional safeguards are needed such as authentication of the individual's right to use the card to make the payment, and protections for the authenticator. Judging by Visa's current PayWave initiative, the norms adopted by card-issuers for this threshold appear to be settling at a transaction-value of about US$ 25, [[currency]]20 or Stg 10.

5. Implications

The framework presented in this paper, and the pilot application of it presented in the previous section, give rise to a variety of implications. Organisations can assess the security of existing and proposed mobile payment schemes, clarify weaknesses, and identify alternative safeguards. Designers of new schemes, and designers of relevant technologies can use the checklists as guidance, and as motivators for new features.

Consumers could be informed by the paper, although it would be unrealistic to expect many to find it, let alone to commit the effort necessary to grasp its contents and implications. Consumers have little understanding of the risks involved, and little or no control over them. Their rational position would be at least wariness about M-Payment schemes, but perhaps suspicion of them and their sponsors, and even hostility to them.

The framework therefore also has implications for public policy. Payers, especially consumers and micro and small business enterprises, have very little power in comparison with merchant-payees, financial services providers, network services providers, and manufacturers and suppliers of mobile access devices. It is the responsibility of Parliaments to provide a legal context that ensures that mobile payment schemes are subject to appropriate levels of security, and that appropriately allocates risks. There are ample examples of both market failure and Parliamentary failure. Parliaments may wish to delegate the details of regulatory measures, but they will continue to fail the public need if they bring no pressure to bear to force regulatory agencies and industry associations to impose requirements on scheme designers and operators.

Areas in which regulatory action may be needed include:

For academics, the framework gives rise to a range of questions that are in need of research. Do consumers have different risk-aversion profiles in a mobile context compared with Internet Commerce and with conventional commerce? To what extent, and under what circumstances, are mobile consumers prepared to trade off convenience against payment risk? To what extent are various consumer segments capable of understanding risk/convenience trade-offs? What reference-points will various consumer segments use in deciding whether to adopt particular payment schemes, and to continue using them? How fragile will trust by consumers be in mobile payment systems? Will a security-related scare reduce adoption, or even halt it, or even reverse the patterns of usage a scheme has achieved? Will a scheme, and will a technology, be able to recover from a justified (or even merely perceived) security-related scare?

It would appear likely that the risk/convenience trade-off will vary, even within a homogeneous consumer segment, and even for the individual consumer, depending on various factors. Is the familiarity of the payment process sufficient assurance to stimulate adoption? How important an adoption factor is the value of the transaction? Does the existence of a prior relationship with the payee make a difference to adoption behaviour?

6. Conclusions

Mobile payments mechanisms inherit many of the characteristics of the payment schemes that are already in place. These vary greatly in their security profiles, and in their fit to the many different contexts in which payment transactions are conducted.

Conventional credit-card payment is inherently insecure - particularly when conducted under MOTO conditions, particularly over networks, and particularly using mobile access devices. In many cases, debit-card payments may also prove to be much more susceptible to fraud than has been the case with EFTPOS and Internet Banking, because of the context in which data is captured, and the reduced capacity of handheld devices to implement the protections that have been important to the successful deployment of Internet Banking applications.

Mobile payment processes can be quick, intuitive and convenient, and hence need not be an obstacle to M-Commerce. On the other hand, they can be just as quick, intuitive and convenient for an unauthorised user of the access device as for its owner. Financial losses by consumers, and even the perception that they are likely, would appear to be a strong impediment to adoption.

The risk assessment framework presented in this paper provides a means whereby that impediment can be addressed.


Unless otherwise noted, all links were accessed during January 2008.

AS/NZS 3931 (1998) `Risk Analysis of Technological Systems - Application Guide' Standards Australia, 1998

AS/NZS 4360 (1999) `Risk Management' Standards Australia, 1995, 1999

Atos (2005) 'Telecoms Predictions 2006', Atos Consulting, at

BIS (2003) 'A glossary of terms used in payments and settlement systems', Committee on Payment and Settlement Systems, Bank for International Settlements, at

BIS (2007) 'Central bank payment system information' Bank for International Settlements, 2007, at

Chau P.Y.K. & Poon S. (2003) 'Octopus: an e-cash payment system success story' Communications of the ACM 46, 9 (September 2003)

Choi Y.B., Crowgey R.L., Price J.M. & VanPelt J.S. (2006) 'The state-of-the-art of mobile payment architecture and emerging issues'Int. J. of Electronic Finance 1, 1 (2006) 94 - 103

Clarke R. (1990) 'Consumer EFTS in Australia: Security Issues' Comp. & Security Law Reporter 5,5 (January/February 1990)

Clarke R. (1992) 'Case Study Cardomat/Migros: An Open EFT/POS System' Austral. Comp. J. 24,1 (February 1992), at

Clarke R. (1996a) 'Message Transmission Security (or 'Cryptography in Plain Text')' Privacy Law & Policy Reporter 3, 2 (May 1996), pp. 24-27, at

Clarke R. (1996b) 'The SET Approach to Net-Based Payments' Xamax Consultancy Pty Ltd, November 1996, at

Clarke R. (1997) 'Cookies' Xamax Consultancy Pty Ltd, 1997, at

Clarke R. (1998) 'Europay Switzerland's SVC Project' Xamax Consultancy Pty Ltd, 1998, at

Clarke R. (2001a) 'Introduction to Information Security' Xamax Consultancy Pty Ltd, February 2001, at

Clarke R. (2001b) 'The Fundamental Inadequacies of Conventional Public Key Infrastructure' Proc. Conf. ECIS'2001, Bled, Slovenia, 27-29 June 2001, at

Clarke R. (2003) 'Authentication Re-visited: How Public Key Infrastructure Could Yet Prosper' Proc. 16th Int'l eCommerce Conference, Bled, Slovenia, 9-11 June 2003, at

Clarke R. (2006) 'A Major Impediment to B2C Success is ... the Concept 'B2C' Invited Keynote, Proc. ICEC'06, Fredericton NB, Canada, 14-16 August 2006, at

Clarke R. & Maurushat A. (2007) 'The Feasibility of Consumer Device Security' Xamax Consultancy Pty Ltd, April 2007, at

Clarke R. & Walters M. (1989) 'Consumer EFTS in Australia: An Introduction' Comp. & Security Law Reporter 5,4, (November/December 1989)

Dahlberg T., Mallata N., Ondrusb J. & Zmijewska A. (2007) 'Past, present and future of mobile payments research: A literature review' Working Paper, February 2007

Davies G. (2002) 'A History of money from ancient times to the present day' University of Wales Press, 3rd. ed., 2002, at (2002) ' Statistics' 2002, at

Grand J. (2004) 'Introduction to Mobile Device Security' Proc. Black Hat Europe 2004 Briefings, Grand Idea Studio, Inc., May 2004, at

Gutmann P. (2005?) 'The Convergence of Internet Security Threats (Spam, Viruses, Trojans, Phishing)', at

Herzberg A. (2003) 'Payments and Banking with Mobile Personal Devices' Commun. ACM 46, 5 (May 2003)

ISO (2005) 'Information Technology - Code of practice for information security management', International Standards Organisation, ISO/IEC 27002:2005

Jakobsson M. & Myers S. (eds.) (2006) 'Phishing and Countermeasures: Understanding the Increasing Problem of Electronic Identity Theft' Wiley, 2006

Kreyer N., Pousttchi K. & Turowski K. (2003) 'Mobile Payment Procedures: Scope and Characteristics' e-Service Journal 2, 3 (Summer 2003) 7-22

Landoll D.J. (2005) 'The Security Risk Assessment Handbook: A Complete Guide for Performing Security Risk Assessments' CRC, 2005

Lee C., Kou W. & Hu W.C. (Eds.) (2004) 'Advances in Security and Payment Methods for Mobile Commerce' IGI Global, 2004

Leyden J. (2008) 'Bank turns London man into RFID-enabled guinea pig: Halifax customer bites back' The Register, 27 January 2008, at

Linck K., Pousttchi K. & Wiedemann D. G. (2006) 'Security issues in mobile payment from the customer viewpoint' Proc. 14th Euro. Conf. on Information Systems (ECIS), 2006

Misra S.K. & Wickramasinghe N. (2004) 'Security of a mobile transaction: A trust model' Electronic Commerce Research 4, 4 (October 2004) 359-372

Mitnick K.D. & Simon W.L. (2002) 'The Art of Deception: Controlling the Human Element of Security' Wiley, 2002

Moses A. (2008) 'Mobile banking steps up a gear' The Melbourne Age, 31 January 2008, at

MPF (2006) 'Mobile Proximity Payment Issues and Recommendations: Mobile Payment Configuration and Maintenance' Mobile Payment Forum, v.1.0, October 2006, at

OECD (2002) 'OECD Guidelines for the Security of Information Systems and Networks: Towards A Culture Of Security' Organisation For Economic Co-Operation And Development, July 2002, at

Paynter J. & Law P. (2001) 'An arm's length evaluation of Octopus' Proc. 1st Int'l Conf. on eCommerce, 2001, at

Peltier T.R. (2005) 'Information Security Risk Analysis, Auerbach, 2nd Edition, 2005

Pousttchi K. (2003) 'Conditions for Acceptance and Usage of Mobile Payment Procedures' In Giaglis G.M., Werthner H., Tschammer V. & Foeschl K. (Eds.) 'mBusiness 2003 - The Second International Conference on Mobile Business' Vienna, 2003 (pp. 201-210), at

Rawson S. (2002) 'E-commerce mobile transactions: Mobility and liability: The hazards of handhelds' Computer Law & Security Report 18, 3 (2002) 164-172

RBA (2007) 'Payments In Other Countries' Reserve Bank of Australia, May 2007, at

Recklies O. (2001) 'M-Commerce - the next Hype?', March 2001, at

Schultz E.E. (2007) 'Mobile computing: The next Pandora's Box' Computers & Security 26, 3 (May 2007) 187, Editorial

Scornavacca E. (2007) 'M-Lit Search' Victoria University of Wellington, at

Scornavacca E.,Barnes S.J. & Huff S.L. (2005) 'Mobile Business Research, 2000-2004: Emergence, Current Status, And Future Opportunities' Proc. Euro. Conf. on Information Systems, 2005

Slay J. & Koronios A. (2006) 'Information Technology Security & Risk Management' Wiley, 2006

Stafford T.F. & Andrew Urbaczewski A. (2004) 'Spyware: The Ghost in the Machine' Commun. Association for Information Systems 14 (2004) 291-306, at

van der Heijden H. (2002) 'Factors Affecting the Successful Introduction of Mobile Payment Systems' Proc. 15th Bled Electronic Commerce Conference, Bled, Slovenia, June 17 - 19, 2002

Visa (2008) 'Visa Authenticated Payment Program', February 2008, at

Vrechopoulos A.P., Constantiou, I.D., Mylonopoulos N. & Sideris I. (2002) 'Critical Success Factors for Accelerating Mobile Commerce Diffusion in Europe' Proc. 15th Bled Electronic Commerce Conference, Bled, Slovenia, June 17 - 19, 2002

Wikipedia (2007) 'Computer Insecurity' at, accessed January 2007, plus many articles linked to from the article

Wikipedia (2008' 'Octopus card', at, accessed January 2008

Zheng X. & Chen D. (2003) 'Study of mobile payments system' Proc. IEEE International Conference on E-Commerce, 2003, 24-27 June 2003, pp. 24- 27

Zmijewska A. (2005) 'Evaluating Wireless Technologies in Mobile Payments - A Customer Centric Approach' Proc. International Conference on Mobile Business (ICMB'05),  2005, pp. 354-362

Appendix 1: Threats and Vulnerabilities Associated with the Access Device




The Device as a Whole, incl.:

  • Hardware, Systems
  • Software
  • Application Software

Anti-User Design Features



Installation of Malware, incl.:

  • Spyware
  • Bots
  • Cracking Tools (e.g. Backdoors, Rootkits)

Unauthorised Actions

Lack of User Understanding

Bugs (e.g. Buffer Overflows)

Insecure Features

Insecure Parameter Settings

Insecure User Accounts

Lack of Product Audit



Remote Invocation

Lack of Supplier Warranties and Indemnities

Blanket Release of Supplier from Liabilities

Systems Software Specifically

Unauthorised Transactions

Lack of a 'Sandbox' for Applications

Application Software

Unauthorised Transactions

Auto-Storage of Cookies on Server Request

Auto-Disclosure of Cookies

Appendix 2: Threats and Vulnerabilities Associated with Transactions




Physical Surroundings

Unauthorised Use:

  • of the Device, incl. Abuse of Privilege
  • of Authorised Processes

Unauthorised Observation, esp. of Authenticators


Physical Violence


Lack of Authentication of Local User

Lack of Physical Security Safeguards

Lack of Logical Security Safeguards

Manual Processes

Inappropriate User Behaviour, incl.:

  • accidental (through ignorance)
  • accidental (through lack of concentration)
  • encouraged or enveigled

Lack of User Understanding

Ambient Noise

Competition for Attention

Susceptibility to Masquerade

Susceptibility to Social Engineering (incl. Phishing)

Software Processes

Inappropriate Transaction Partner

Lack of User Understanding

Lack of Authentication of Value Being Transferred

Lack of Authentication of Partner Identity


Inappropriate Transaction

Lack of User Understanding

Initiation by an Unauthorised User


Unauthorised Amendment to a Transaction

Replay of a Captured Transaction


Capture of Authenticators (Password, PIN,

secret key, private key)

Lack of User Understanding

Masquerading Transaction Partner

Man-in-the-Middle Attack

Resident Malware

Insecure Storage

Insecure Transmission of Authenticators


Message Interception

Lack of User Understanding

Insecure Transmission of Message

Appendix 3: Threats and Vulnerabilities Associated with Other Interactions




Software Download

Anti-User Design Features



Lack of User Understanding

Openness to Download driven by a Remote Device



Lack of User Understanding

Lack of Authentication of Remote Users

Software Errors

Software Features


Infiltration Vectors

Pre-Installed Software

User-Installed Software



Lack of User Understanding

Lack of Authentication of:

  • Pre-Installed Software
  • Newly-Loaded Software

Infiltration Payloads

Trojans, esp. bot software

Spyware, esp.:

  • software monitors
  • content monitors
  • adware
  • keystroke loggers
  • private key harvesters

Lack of User Understanding

Lack of Authentication of:

  • Pre-Installed Software
  • Newly-Loaded Software

Lack of Checks for Malware Signatures and Malware-Related Behaviour

Appendix 4: Threats and Vulnerabilities Associated with Mobile Infrastructure




Transacting Device

Rogue Device

Lack of Authentication of Transacting Devices

Manual Business Processes

Inappropriate Performance

Lack of Training


Susceptibility to Masquerade

Susceptibility to Social Engineering

Data Storage

Second Party:

  • Inappropriate Access / Abuse of Privilege
  • Inappropriate Use
  • Inappropriate Disclosure

Third Party:

  • Inappropriate Access / Abuse of Privilege
  • Inappropriate Use
  • Inappropriate Disclosure

Lack of Physical Security Safeguards

Lack of Access Control Safeguards

Physical Surroundings

Inappropriate Access

Lack of Physical Controls

Computing Facilities

Second Party

Third Party

Lack of Access Controls

Lack of Organisational Controls

Lack of Process Controls

Network Facilities

Second Party:

  • Inappropriate Access / Abuse of Privilege
  • Inappropriate Use
  • Inappropriate Disclosure
  • Inappropriate Amendment
  • Inappropriate Replay

Third Party (Message Interception):

  • Inappropriate Access / Abuse of Privilege
  • Inappropriate Use
  • Inappropriate Disclosure
  • Amendment
  • Replay

Lack of Understanding

Messages Sent in Clear Text

Supporting Infrastructure



Fire Protection


Disabling Attack

Author Affiliations

Roger Clarke is Principal of Xamax Consultancy Pty Ltd, Canberra. He is also a Visiting Professor in the Cyberspace Law & Policy Centre at the University of N.S.W., a Visiting Professor in the E-Commerce Programme at the University of Hong Kong, and a Visiting Professor in the Department of Computer Science at the Australian National University.

xamaxsmall.gif missing
The content and infrastructure for these community service pages are provided by Roger Clarke through his consultancy company, Xamax.

From the site's beginnings in August 1994 until February 2009, the infrastructure was provided by the Australian National University. During that time, the site accumulated close to 30 million hits. It passed 50 million in early 2015.

Sponsored by Bunhybee Grasslands, the extended Clarke Family, Knights of the Spatchcock and their drummer
Xamax Consultancy Pty Ltd
ACN: 002 360 456
78 Sidaway St, Chapman ACT 2611 AUSTRALIA
Tel: +61 2 6288 6916

Created: 4 January 2008 - Last Amended: 17 April 2008 by Roger Clarke - Site Last Verified: 15 February 2009
This document is at
Mail to Webmaster   -    © Xamax Consultancy Pty Ltd, 1995-2013   -    Privacy Policy