Canada: Mobile Payments 2012

On October 25, 2012, McCarthy Tétrault's national Consumer Retail group held a lunchtime client conference on mobile payment systems and digital wallets. For those of you unable to attend, the following is a few of the highlights.

But first, a little context for the uninitiated:

  • Near-field communication technology (NFC) allows a user with a mobile phone, equipped with the necessary mobile application, to pass card data stored on the phone to the point-of-sale device to complete payment and other transactions.
  • Mobile payments are often grouped into two levels of transaction: convenience vs. high value/risk transactions. Convenience transactions are characterized by low value/risk (e.g., under $50) and may be effected just by swiping the mobile device at the POS terminal. The other type of transaction involves high value/risk (e.g., $50 and greater), and would require a combination of a swipe of the mobile device at the POS and a pass code to be entered.

Mobile Payments and Financial Regulations

Jim Archer, of McCarthy Tetrault's Financial Services Group in Toronto, presented the regulatory infrastructure behind the proposed system of mobile payments.

Prompted by the federal government's Payments Systems Task Force, Canada's banks and credit unions worked together to develop guidelines to help grow a mobile payment marketplace in Canada. In May 2012, the Canadian Bankers Association released an initial draft of the Canadian NFC Mobile Payments Reference Model.

The Reference Model sets out the roles of each of the participants in the mobile payments industry, including end users (i.e., the consumer making the mobile payment from his/her mobile device), credential issuers (i.e., the bank or financial institution behind the payment application on the end user's device), trusted service managers (TSMs) (i.e., the entity that loads the payment credentials of the end user into the wallet application on the end user's device), payment networks (e.g., Visa, MasterCard, Interac), acquirers (e.g., Moneris), merchants, and mobile network operators (MNOs) (e.g., Bell, Rogers, TELUS). For some of these entities, such as the payment networks and acquirers, their roles in the context of the mobile payment "ecosystem" are not expected to change significantly from their traditional roles in processing credit and debit card payments. In contrast, the MNOs, which have a direct relationship with the consumer, supply mobile phones on which the mobile payment application will be installed, and operate the networks across which the mobile transaction will take place may see a more significant transformation of their historical role as mere "carrier" under the new payment process.

In order for a consumer to make a mobile payment using NFC technology, a certain number of agreements and transactions must first be put in place:

  • end user applies to credential issuer for credit and/or debit card account which contemplates mobile payment application.
  • end user applies to MNO for a wallet application (i.e., a mobile wallet) to be installed on mobile device.
  • end user requests credential issuer to install payment application on mobile device and to personalize payment credentials (i.e., personal encrypted information, including a pass code). This could be done through the wallet application, website, telephone or in person.
  • credential issuer instructs its TSM to transmit payment credentials to mobile device.

Once these preliminary steps have occurred, the consumer is ready to use his/her mobile device as a payment mechanism.  The actual purchase procedure steps are as follows:

  • end user opens payment application (NFC mobile device must ensure that only one payment application may be turned on at one time) and passes the mobile device within the range of the POS device.
  • convenience transactions (that do not exceed a high value or high risk threshold) will occur automatically. For high value or high risk transactions, a pass code will be prompted which must be verified.
  • transaction completed.

Credential issuers, wherein consist primarily of banks, are currently governed by the Bank Act and related regulation (e.g. Cost of Borrowing and Credit Business Practices regulations). On the whole, relatively few changes are required for the legislation to regulate mobile payments in a similar fashion as it does to other modes of payment. In addition, payment card networks (both credit and debit) are currently regulated by various voluntary codes of conduct, including a Code of Conduct for the Credit and Debit Card Industry in Canada (the "Code"), released by the Department of Finance in 2010. In September 2012, the federal government proposed an addendum to the existing Code to address mobile payments. The amendments were necessary, among other reasons, to clarify that both debit and credit transactions may be performed using a single mobile device. In the end, the mobile payments system involves similar relationships and is governed by similar types of credit/debit agreements as those that exist in the conventional payment system. Consequently, it should be possible for mobile payments to occur with only minor regulatory changes to the applicable regulatory regime. By contrast, a mobile payments "ecosystem", will inevitably result in a fairly extensive range of new contractual relationships (as new "players" participate in the payment process), as well as consequential changes to standard credit and debit account agreements to account for some of the particularities of the new mobile payment services.

Mobile Payments and Digital Wallets

Charles Morgan, the Quebec regional leader of McCarthy Tetrault's Technology Group practice, discussed the technology behind mobile payments.

Near-field communication (NFC) is the primary technology being used in mobile phones to implement mobile payment systems. It allows for the two-way transmission of data at very close distances (up to approximately 4 cm). Instead of individual phone manufacturers developing their own proprietary technologies for near-field communication, the NFC Forum has developed uniform technical specifications to facilitate interoperability among devices and services. NFC technology has recently been implemented in new model smartphones, including Nokia, Android, and BlackBerry devices. Noticeably, Apple has chosen to forgo such implementation in their latest iPhone 5 model. In 2010, several U.S. mobile service providers (AT&T, Verizon, T-Mobile) launched a joint venture, Isis, to work with MasterCard Worldwide to develop a point-of-sale payment system for NFC-enabled smartphones. Other NFC initiatives include the launch of Google Wallet (2011), a joint mobile payment initiative between CIBC and Rogers (May 2012), a joint mobile payment initiative between Deutsche Telekom and MasterCard (July 2012), and a recent agreement between Research in Motion (RIM) and Enstream (a Bell, Telus, Rogers joint venture), to have RIM manage security credentials for SIM.

An NFC enabled smartphone requires two software applications in order to execute a payment transaction. The user's payment credentials are stored in a payment application in a secure element embedded in the device. This payment application is distinct from the user interface application, known as a mobile wallet, which will interact with the payment application to execute a mobile payment. A mobile wallet may be designed for use with only a single provider, a collective of credential issuers, or in the case of an open standard, any number of credential issuers. The possible functions of mobile wallets are endless, as they may incorporate not only credit payment products (e.g., Visa, MasterCard, etc.) but debit payment products (e.g., Interac), prepaid payment products, transit passes (e.g., OPUS), loyalty/reward cards (e.g., Air Miles), and targeted coupons/offers.

Key Elements of a Mobile Wallet

  • Credential Provisioning: a mobile wallet may provide end users with the option to request provisioning of payment credentials (i.e. initiate the installation process).
  • Mobile Wallet Access: for security, a mobile wallet must provide end users with the option to lock/unlock the wallet using a user defined password. This standard does not require that a wallet password must be used, only that the end user must be given the option to set a password.
  • Default Credential Selection: a mobile wallet must provide end users with the option to enable/disable a default payment credential. A default credential allows end users to initiate a payment without having to take the mobile device out of standby mode and without having to manually select a wallet.
  • Manual Default Override: a mobile wallet must provide end users with the option to override a default payment credential and manually select a payment credential to present.
  • High Value & High Risk Payments: a mobile wallet must have the ability to support entry of a pass code for end user verification of high value and high risk payments.
  • Transaction Data: a mobile wallet may capture transaction data for all linked payment applications; however, if it does capture this data, access to and usage of this data must be restricted as per the standards in the Data & Security section of the Reference Model.
  • Electronic Receipts: a mobile wallet may store, retrieve and transmit electronic receipts. If the wallet does store electronic receipts, receipts need only be maintained on the instance of the wallet used to make a payment.
  • Enabling a Return Transaction: a mobile wallet and payment application must be able to facilitate return transactions. For return transactions, the end user will select the payment application to be used and will then tap the mobile device against the POS reader.
  • Loyalty & Reward: a mobile device may be used to store and manage information on loyalty and rewards programs.

Data security is a concern for participants of the mobile payments ecosystem. The guiding principle outlined in the Reference Model is that each participant in the mobile payment process should only have access to those elements of the user's data that are necessary for it to carry out its functions in relation to the mobile transaction. Further, each ecosystem participant should put in place processes to track, monitor and mitigate fraud and security concerns including malware, hacking and theft of mobile devices. However, no specific standards on fraud and security are specified in the Reference Model. In the event of a lost or stolen mobile device, the end user should be instructed to contact both the MNO and the credential issuer. Once informed of a lost or stolen mobile device, the MNO or the secure domain manager (SDM) (i.e., the entity that manages access to the secure element that stores the end user's sensitive payment credentials on the mobile phone) should lock the mobile device. Once informed of a lost or stolen mobile device, the credential issuer should lock/block the payment method.

Additional Topics of Discussion

McCarthy Tétrault's Consumer Retail practice group also had two guest speakers on its mobile payments panel. Mohamed Kahlain, Vice President, Marketing and Product Innovation at Mediative (a division of Yellow Pages Group), provided a marketing perspective on mobile payment business opportunities. Bill Abbott, Senior Counsel and Privacy Ombudsmen at Bell Canada, provided a carrier's perspective on mobile payment privacy issues.

Over the last two years, the basic regulatory, contractual and technological infrastructure to make mobile payments possible has been put in place. Over the next year or two, we anticipate that mobile payments will go "mainstream".

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.