When you use the Android Pay app on your smartphone, you’re paying for a single tap to pay with your credit card, but that tap isn’t actually being displayed.

It’s just being stored as an in-app payment token, which Google says is what makes it a better option for payments than credit cards.

Google is using the Tap platform to let developers build apps that let users tap an item in a store to pay.

Android Pay is the first major app to integrate with the platform, and Google says it will be used to add more payment options.

But some of the app’s early customers are unhappy that Google isn to the credit of making it easier for merchants to tap a customer’s credit card.

They want a way to pay by paying with Android Pay, but the tap is being stored on the device, not the app, and there’s no way to add a way for the user to pay via credit card when they want to.

The Android Pay developer community has been vocal about its frustration with Google’s tap-based payment options, especially in the wake of the Paypal hack.

And in an effort to alleviate some of those frustrations, Google is finally making it possible for Android Pay apps to include a way the user can tap a card to pay for an item.

A small update that Google announced on Wednesday lets developers make payment with Android pay even if the card is not present.

Google’s decision to release the feature for developers was prompted by feedback from users who complained that tapping their credit card to make a purchase in the app wouldn’t let them make purchases using the traditional checkout process.

Google says the feature will be available to apps built using the Android Payments SDK starting on March 23.

It is not available to any other Google-branded app, including the Play Store or the Play store for Google Home.

Developers can also tap an NFC tag to make payments from within Android Pay.

The change is a small but welcome development, but it’s likely to make it harder for developers to make apps that use Android Pay work with credit cards in the future.

For now, Google says there are no plans to add support for the Tap payment system to any of its existing apps.

That means developers can use Android pay only on the Google Wallet app, the Android Appstore, the Google Search app, or other apps built on top of Android Pay’s framework.

Google has previously made it easy to use credit cards with the Android app, but not as easy as it is with Google Pay.

In fact, Google has a “pay” button on the Android Wallet app for all apps that accept credit cards that you tap on your phone.

To use Android payments with Google Wallet, users first need to enable the “tap” payment option in their Google Wallet settings.

That’s the same way you can enable the Google Pay payment system from within the Google Accounts app.

Android Payments has a few other other payment options that are available to developers.

Developers who want to offer a payment option within AndroidPay can use the app as a payment gateway, which is a feature that allows developers to offer payments via credit cards or debit cards in addition to payments from Android Pay itself.

Google Pay for Android will be free for developers.

AndroidPay will remain free, and will still work on devices running stock Android.

That includes the Nexus 6, Nexus 5X, Nexus 6P, Nexus Player, Nexus 7, Nexus 10, Pixel, Pixel XL, and Pixel XL 2.

Developers will be able to add payments to Android Pay through third-party applications as well, including Amazon and PayPal.

Google hopes that more developers will add support to AndroidPay in the near future.