Android Pay can now be used as a payment method within websites without requiring an Android mobile application. It makes use of the Payment Request API built into Google Chrome. This guide explains what WePay partners need to know to support Android Pay on the Web.


Read and familiarize yourself with the Payment Request API before reading this guide.

Summary and Limitations

Android Pay on the web is integrated as an additional stored “card” in the Payment Request API. When the Payment Request API is activated, the payer can choose between:

  • Any previously stored cards
  • Android Pay (and whatever actual cards have been setup for use with Android Pay)

WePay supports both the Payment Request API and provides special support for Android Pay. The additional integration requirements to support Android Pay alongside regular stored cards via the Payment Request API are minimal.

Payer and Device

  • Android device with the Android Pay app installed and configured
  • Android Pay app requires Android v4.4 or higher
  • Payers must have a supported bank card loaded on their Android device
  • Supported for payers in all countries that support Android Pay and if the Issuer supports it

Platform Setup

The following steps are required for a partner to support Android Pay.

  • Contact your WePay account manager to request access to Android Pay for your application
  • Sign up for a merchant ID from Google:
    • This merchant ID will be needed in calls to the SDK
  • WePay generates and provides you with public keys (1 for stage, 1 for production)

Platform Integration

Use the public key provided to you by WePay as part of your PaymentRequest object when you call WePay.wallet.beginTokenization(). You must also supply the merchant ID provided to you by Google to the merchantId parameter in WePay.wallets.beginTokenization().