Skip to main content

Google Pay: review and go live

When integrating Google Pay into your website or mobile application, you must submit screenshots of your end-to-end purchase flow for review. Google uses these screenshots to verify that your implementation meets their user experience requirements before granting production access.

This guide outlines the required screenshots, what to include in each one, and best practices to ensure approval.

What you need depends on where the button lives​

Google approves Google Pay per website domain and per native app, under a merchant profile in the Google Pay & Wallet Console. Straumur is the payment gateway in every case (integration type Gateway); what varies is whose Google merchant profile the approval sits under, and therefore who submits.

You useWhose Google merchant profileWho submits to GoogleWhat you do
Hosted Checkout or Payment LinksStraumur'sNobody on your side. The button is on Straumur's own payment page, which is already approved.Ask developers@straumur.is to enable Google Pay on your store. No screenshots.
Web Components on your websiteStraumur'sStraumur. We register your domain under our Google Pay merchant and submit the review.Send us your top-level domain and the screenshots below, taken from your test integration.
Native app (Flutter, React Native, Android)Yours. Google approves apps per package name, so this has to be your own profile.You. Create a merchant profile in the console, request production access for the app, and complete Google's integration checklist.Send us your Google merchant ID; we add it to the Google Pay payment method on your Adyen configuration. Then do the app-side setup: release-signed build, screenshots from the app, environment set to production once approved.

Two things hold for every row:

  • The screenshots below are the same whichever profile the approval sits under; only who uploads them changes.
  • Test works without any of this. Google Pay in the test environment does not need approval, so you can build and test first and start the approval when your integration is ready.

If you are not sure which row applies, ask developers@straumur.is before you start collecting screenshots.

General Requirements​

All submitted screenshots must meet the following criteria:

  • File size: Maximum 1 MB per file
  • Format: PNG or JPEG
  • Clarity: All text and UI elements must be clearly visible
  • Authenticity: Screenshots must show actual purchase flows, not mockups or wireframes
  • Capture method: If your device prevents screenshots (common on Android for Google Pay screens), use a second device to photograph the screen with no glare or reflections

Required Screenshots​

1. Item Selection Screen​

Purpose: Demonstrate how users browse and select items or services.

Required elements:

  • Products or services displayed clearly with images
  • Item details including name and price
  • Call-to-action button (e.g., "Add to cart" or "Buy now")
  • Clear path to proceed toward checkout

Examples:

  • Product detail page in an e-commerce application
  • Service selection screen in a booking application

2. Pre-purchase Screen​

Purpose: Show the order review stage before payment method selection.

Required elements:

  • Complete order summary with selected items or services
  • Item quantities and individual prices
  • Total amount including all applicable taxes, fees, and shipping costs
  • Clear call-to-action button (e.g., "Continue" or "Proceed to Payment")

Examples:

  • Shopping cart page displaying order summary
  • Checkout review page with shipping address and order details

3. Payment Method Selection Screen​

Purpose: Display how users select Google Pay as their payment method.

Required elements:

  • All available payment options (e.g., credit card, PayPal, Google Pay)
  • Google Pay option clearly visible and accessible
  • Correct Google Pay branding following official guidelines

Important:

  • Use the official Google Pay button and mark
  • Do not create custom variations or misleading representations

4. Google Pay Payment Sheet​

Purpose: Show the Google Pay interface where users confirm their payment details.

Required elements:

  • Google Pay payment sheet displaying saved card information
  • Shipping address and contact information (if applicable)
  • Final confirmation button (e.g., "Pay" or "Continue")
  • Price breakdown (if displayed)
Screenshot Restrictions

Android devices typically prevent screenshots of this screen for security reasons. Use a second device to photograph the screen clearly, ensuring there is no glare or reflection that obscures the content.

5. Post-purchase Confirmation Screen​

Purpose: Show the transaction confirmation after successful payment.

Required elements:

  • Order confirmation message or success indicator
  • Order reference number or summary
  • Next steps or available actions (e.g., "View receipt" or "Continue shopping")

Examples:

  • Order confirmation screen with delivery information
  • Booking confirmation page with reservation details

Best Practices​

  • Verify all branding and UI elements comply with Google Pay brand guidelines
  • Ensure prices and order details are consistent across all screenshots
  • Do not display sensitive customer information such as full credit card numbers
  • Screenshots must accurately represent your production-ready flow as users will experience it
  • Test the complete flow before capturing screenshots to ensure a smooth, error-free experience

Submitting Your Screenshots​

Once you have prepared all required screenshots following the guidelines above, send them to:

developers@straumur.is