Questions? Contact us at

Wallet Database

Android Pay

21st of August 2016


  • SummaryAndroid Pay is a cards-based digital wallet platform for NFC contactless and In-App purchases operating in multiples markets and launched in Sep 2015. Android Pay has been developed by Google to power in-app and NFC contactless purchases on mobile devices, enabling users to make payments with Android phones, tablets or watches

  • Website

  • Status: Live

  • Market: US (Sept ’15), UK (June ’16), Singapore (June ’16), Australia (July ’16), Hong Kong (Oct ’16), Poland (Nov ’16) & New Zealand (Dec ’16)

  • Type: Other (Compatible with Android platform)

  • Ownership: Google (Although its an Open Source project, in reality Android is mainly developed and maintained by Google until the latest updates and changes are launched. At this time the source code is made available publicly. The Open Handset Alliance (OHA), a consortium of 84 firms, also has significant influence and control of Android.)

  • Functions: Retail payments only

  • Payment Mode: Cards based

  • Channel: POS via NFC, In-App

  • Roadmap: Web (New web API, called PaymentRequest, being developed to operate with Chrome browsers to bring Android Pay to web. Working with World Wide Web Consortium (W3C) to make the system a standard across web browsers); Contactless ATM withdrawals (being tested with BofA)

User Experience

  • Registration & set up: User opens Android Pay app which comes preloaded on several devices. Can also be downloaded from Google Play. But only available in markets that support Android Pay. User adds a credit or debit card within the app. Can also add any card in a Google account. Otherwise enter card details or take photo of card from a participating bank

  • Making a payment: NFC initiated by physically tapping the phone on  contactless terminal. No need to open Android Pay app. Authenticate with fingerprint. Also supports PIN code, password, or pattern in order to authenticate a transaction

Payment Flows & Technology

  • Merchant perspective: The merchant processes a payment using their existing payments processing systems. Android Pay simply facilitates the payment by securely passing payment credentials to the merchant, and is not a party to the transaction. Even though the transaction is facilitated by Google, the merchant is the seller of record for the purchase

  • SecurityAndroid Pay‘s tokens are generated within the cloud. Some tokens are stored locally for use when internet access is not available 

Business Model

  • StrategyAndroid Pay does not charge merchant any fees for purchases through Android Pay. Merchants pay standard fees to their merchant acquirers. Android does not charge card issuers either. Partly, as a result of Visa and MasterCard, deciding not to charge for their “tokenization” service. Android Pay revenue model is to contribute to Google mobile advertising and app sales

  • Payee fee: Standard acceptance rates apply. No additional charge for merchant

  • Payer fee: No charge for consumer 

Performance Data

Contact (MobeyForum Members only)

  • Name: N/A

  • Address: N/A

  • Email: N/A

  • Phone: N/A