Google Pay compliance overview
This section is a placeholder. We're building out detailed Google Pay certification guidance and publishing it here as the content matures.
Before you can launch an app that adds cards to Google Pay, Google must approve your integration. The approval process verifies that your app meets Google's functional, security, and user-experience requirements for issuer appsIssuer app Apple's term for the mobile app that authenticates a cardholder and provisions their card to Apple Wallet. Apple's certification, brand, and Card Lifecycle Management requirements apply specifically to this app. In a primary + companion architecture, your primary app remains the issuer app even if the provisioning step happens in a companion app..
How our SDK fits in
Our Android Push Provisioning SDK handles the technical part of adding a card to Google Pay. It does not, on its own, satisfy Google's certification requirements — those depend on how the SDK is integrated, which app it lives in, and what surrounding controls (authentication, card lifecycle managementCard Lifecycle Management The set of in-app card operations Apple and Mastercard expect an issuer app to surface so cardholders can self-serve without leaving the app. Typical operations: view card number / CVV / PIN, lock and unlock, freeze and unfreeze, replace, report lost or stolen, view balance, and view transactions. Issuer apps that omit any of these are flagged at lab certification., deep links) are in place.
Talk to us early
Reach our support team if you're planning a Google Pay integration. We can walk you through the current requirements, share the technical artifacts Google asks for, and help you scope the work while we finish writing this section.