TechPrufer
Get started
Google
Google logoGoogle · Feature trail

Google Checkout API and Payment Processing

34 posts · Jun 2006 – May 2026

What this trail covers

Google Pay API continues to evolve, enhancing checkout experiences with features like liability shift for eligible Visa device token transactions globally. This includes updates to the eciIndicator for transaction qualification and opt-in mechanisms for merchants. The API also supports dynamic price updates and callback mechanisms, with ongoing rollouts for specific features. The Android native app experience now supports dynamic callbacks for payment and address updates within the Google Pay sheet. New optional properties, `allowedIssuerCountryCodes` and `blockedIssuerCountryCodes`, have been added to the `CardParameters` object to enable filtering by issuer country codes, providing more granular control over accepted payment methods.

All Google trails
  1. The latest updates to Google Pay- Google Developers BlogIntroduced dynamic callbacks (onPaymentAuthorized, onPaymentDataChanged) for Android, enabling upstream Google Pay button placement and real-time updates within the payment sheet. Extended Google Pay support to social app WebViews. Added a cardFundingSource signal to API responses for routing logic and introduced Eftpos routing for Australia. Enabled lifecycle notifications for Google Pay payment tokens to support Merchant-Initiated Transactions (MITs). Launched Cross-Device Authentication to move high-friction desktop checkouts to a mobile-first authentication flow.
  2. Enhancing Android Checkout with Dynamic Callbacks in Google Pay- Google Developers BlogThis post introduces the implementation of dynamic callbacks (`onPaymentDataChanged` and `onPaymentAuthorized`) for Google Pay on Android native apps, mirroring existing web capabilities. It details how to extend `BasePaymentDataCallbacks` and `BasePaymentDataCallbacksService` to handle real-time updates to shipping options, taxes, and total prices based on user interactions within the Google Pay sheet. It also covers handling authorization feedback and retries directly within the sheet. The post provides code examples in Kotlin and XML manifest updates, and highlights the benefits of reduced friction, increased accuracy, and improved authorization handling.
  3. New enhancements for merchant initiated transactions with the Google Pay API- Google Developers BlogIntroduces new objects (`recurringTransactionInfo`, `deferredTransactionInfo`, `automaticReloadTransactionInfo`) and properties within the `PaymentDataRequest` to support merchant-initiated transactions (MIT) for recurring, deferred, and automatic reload payments. Details specific parameters within `recurringTransactionInfo` such as `introductoryPeriodInfo`, `recurrenceItems`, `price`, `managementUrl`, and `tokenUpdateUrl`. Provides a JSON example for a simple monthly subscription.
  4. Google Pay inside sandboxed iframe for PCI DSS v4 compliance- Google Developers BlogThis post details a method for achieving PCI DSS v4 compliance for checkout pages by integrating Google Pay within a sandboxed iframe. It explains how to configure the iframe with specific sandbox attributes (`allow-scripts`, `allow-popups`, `allow-same-origin`, `allow-forms`) and the `allow='payment'` attribute to ensure secure script execution and communication via `window.postMessage()`. It also highlights Shopify's successful implementation of this solution.
  5. Adding support for Google Pay within Android WebView- Google Developers BlogIntroduces support for Google Pay within Android WebView, leveraging the Payment Request API and Google Play Services 25.18.30 to trigger the native payment sheet. Requires adding androidx.webkit:webkit:1.14.0 dependency, specific <queries> tags in AndroidManifest.xml, and enabling the Payment Request API for the WebView. No other Google Pay specific changes are needed for the app.
  7. New Google Pay features to enhance your payment flows- Google Developers BlogIntroduces Google Pay in Android WebViews, enabling native Android payment experiences and device tokens within in-app browsers. Enhances the Google Pay payment sheet with richer card art, names, and dark mode support. Expands the createButton API for Web with more customization options. Introduces a new API for displaying card-identifying information without a payment button. Adds support for Merchant-Initiated Transactions (MITs) to the Google Pay Online API, including user-facing details, device-independent tokens, and lifecycle notifications. Improves the test card suite for more relevant test cards in the `TEST` environment. Provides more fine-grained build time error logs and detailed runtime exceptions/error codes for debugging on Android. Launches new codelabs, Firebase Studio templates, and a learning pathway for web developers. Introduces the Google Pay API Status Dashboard. Enhances fraud detection by allowing chargeback data upload and enables built-in identity verification challenges for suspicious transactions. Plans to enhance API responses with more detailed risk information.
  8. Want a smoother checkout with Google Pay? Configure your payment options!- Google Developers BlogThis post details the configuration options for accepted payment methods in Google Pay integrations. It explains how to set `CardParameters` to control authentication methods (PAN_ONLY, CRYPTOGRAM_3DS), card networks (AMEX, DISCOVER, INTERAC, JCB, MASTERCARD, VISA, ELECTRON, MAESTRO, ELO, ELO_DEBIT), card types (prepaid, credit), and assurance details. It also introduces new optional properties, `allowedIssuerCountryCodes` and `blockedIssuerCountryCodes`, for filtering payment methods based on the issuer's country code, providing examples of their implementation in JavaScript.
  9. Google Pay - Enabling liability shift for eligible Visa device token transactions globally- Google Developers BlogThis post announces the general availability of liability shift for eligible Visa device tokens in Google Pay globally. It details what liability shift is, how to identify shifted transactions via the `eciIndicator` value (specifically '05'), and the required API parameters (`totalPrice`, `totalPriceStatus`) for qualification. It also outlines merchant enrollment within the Google Pay & Wallet console, ineligible merchant categories (MCC codes), and ineligible transaction types. The post also mentions that qualified transactions can still be downgraded by the network during authorization.
  10. Aligning the user experience across surfaces for Google Pay- Google Developers BlogThis post details the alignment of the Google Pay user experience across Web and Android, including the adoption of the Material 3 design system for bottom sheets on Android and Chrome on Android. It reports a ~2.5% increase in conversion rate and a ~39% reduction in errors for users using Google Pay with Chrome on Android. The web experience also received a revamped, minimalistic Payment Handler window, leading to a ~9% conversion rate increase. No changes are required from merchants or PSPs as these updates are rolled out progressively.
  11. What’s new in Google Pay- Google Developers BlogThis post details several new features and improvements for Google Pay, focusing on enhancing security, developer integration, and user experience. Key contributions include: expanding zero fraud liability protection to eligible Visa online transactions, introducing Secure Payment Authentication for risk and compliance-based authentication using device-bound tokens, releasing a new dynamic Google Pay button view for Android with Material 3 design principles and simplified XML configuration, upgrading the test suite with PSP test cards for end-to-end and automated testing, and mentioning improvements to virtual cards and autofill functionality. The post also highlights the upcoming ability to configure the new button view for Android to show the last used card and similar customization for websites.
  12. Jetpack Compose Buttons for Google Pay and Google Wallet- Google Developers BlogIntroduced `compose-pay-button` and `compose-wallet-button` open-source libraries for Jetpack Compose developers. These libraries simplify the integration of Google Pay and Google Wallet buttons into Android applications, offering customization options via Jetpack Compose modifiers and supporting various button types and asset versions.
  13. Introducing the new Google Pay button view on Android- Google Developers BlogIntroduces a new Google Pay button view for Android, adhering to Material 3 design principles with enhanced customization for shape, corner radius, and theme (dark/light). Simplifies integration via XML layout or programmatic configuration, including pre-packaged graphics and translations. Mentions upcoming support for displaying the last used card's details and a Jetpack Compose UI element. This post details the technical implementation and customization options for the Android button view.
  14. Test your payments integrations end-to-end with the new test suite for Google Pay- Google Developers BlogIntroduces an upgraded test suite for the Google Pay API, featuring PSP test cards from major payment processors (Stripe, Adyen, Braintree, WorldPay, Checkout.com) for end-to-end testing of payment flows, including successful and failed transactions. This enhances testing strategies by allowing validation against diverse payment outcomes and supports test automation using tools like UIAutomator and Espresso on Android, integrating into CI/CD flows. Web support is planned for later.
  15. When to step-up your Google Pay transactions as a PSP- Google Developers BlogThis post details the implementation of step-up authentication for Google Pay transactions from a Payment Service Provider (PSP) perspective. It explains the concept of step-up authentication, how the Google Pay API response indicates whether it's needed (authenticated payload vs. PAN requiring 3D Secure), and the role of `allowedAuthMethods` (`CRYPTOGRAM_3DS`, `PAN_ONLY`). It further elaborates on the `assuranceDetails` object (`cardHolderAuthenticated`, `accountVerified`) within the decrypted payment token to guide PSPs on when to skip or require step-up authentication, recommending step-up unless both fields are true.
  16. Make Payments with Google Pay and Firebase - Google Developers BlogThis post details how to integrate Google Pay with Firebase for in-app payments, focusing on setting up Firebase projects, configuring Google Pay, and handling payment flows within an Android application. It covers aspects like creating payment intents, processing responses, and managing transaction states, providing a practical guide for developers to implement payment functionality.
  17. Easily connect Google Pay with your preferred payment processor - Google Developers BlogThis post announces the general availability of the Google Pay API, enabling developers to integrate Google Pay into their applications. It highlights the ability to connect Google Pay with preferred payment processors, offering a streamlined checkout experience for users. The post details how developers can implement Google Pay by using the API to create payment requests and handle payment responses, emphasizing the ease of integration and the benefits of a unified payment experience.
  18. Google Pay plugin for Magento 2- Google Developers BlogThis post announces the launch of the official Google Pay plugin for Magento 2, detailing its installation, configuration, and benefits for merchants. It highlights integration with various payment service providers and the ability for customers to use saved payment credentials for a faster checkout. Updates include support for Cybersource, Magento 2.4, and Magento 2.3.
  19. Google Pay introduces a Flutter plugin for payments- Google Developers BlogIntroduces a new Flutter plugin for Google Pay, enabling developers to integrate Google Pay payments into their Flutter applications. This plugin simplifies the process of handling payment flows within Flutter apps, leveraging the existing Google Pay infrastructure.
  20. Simpler Google Pay integration for React and web developers- Google Developers BlogThis post introduces the Google Pay API for React and web developers, simplifying integration with features like the Payment Request API. It highlights the ability to use Google Pay as a payment method within web applications, streamlining the checkout process for users and developers. The post focuses on the developer experience for web integration, including code examples and best practices for implementing Google Pay on websites.
  21. Google Pay launches new, dynamic features for Online Payments and Passes APIs- Google Developers BlogIntroduced the ability to show card-identifying information without a button, and added support for Merchant-Initiated Transactions (MITs) for subscriptions and auto-reloads. Also enhanced developer experience with an improved test card.
  22. All you need to know about Google Pay if you’re a developer- Google Developers BlogThis post provides developers with an overview of the Google Pay API, highlighting its capabilities for in-app and web payments. It details how to integrate Google Pay for a seamless checkout experience, including features like tokenization, payment sheet customization, and support for various payment methods. The post emphasizes the developer-friendly nature of the API and its role in simplifying payment processing for businesses.
  23. Google Play Developer API new fields for In-app Billing information- Google Developers BlogIntroduced new fields to the Google Play Developer API to provide more detailed information about In-app Billing, enabling developers to gain deeper insights into their billing data.
  24. Improvements to Google Checkout Module for osCommerce- Google Developers BlogThis post announces improvements to the Google Checkout Module for osCommerce, a popular e-commerce platform. The improvements focus on enhancing the integration and functionality of Google Checkout within the osCommerce environment. This likely involved updates to the module's code to support new features or address issues related to payment processing, order management, or user experience within the osCommerce framework. The specific technical details of the improvements are not provided in the title, but it signifies an ongoing effort to refine the integration of Google's payment services with third-party e-commerce platforms.
  25. Google Checkout API- Google Developers BlogThis post announces the Google Checkout API, a new API for developers to integrate Google's checkout services into their applications. It highlights the benefits of using the API, such as simplified payment processing and enhanced user experience. The post also mentions that the API will be available for developers to use in their applications.