New enhancements for merchant initiated transactions with the Google Pay API

[Facebook](https://www.facebook.com/sharer/sharer.php?u={url} "Share on Facebook")
[Twitter](https://twitter.com/intent/tweet?text={url} "Share on Twitter")
[LinkedIn](https://www.linkedin.com/shareArticle?url={url}&mini=true "Share on LinkedIn")
[Mail](mailto:[email protected]?subject=Check%20out%20this%20site&body=Check%20out%20{url} "Send via Email")
[](http://developers.googleblog.com/new-enhancements-for-merchant-initiated-transactions-with-the-google-pay-api/# "Get shareable link")

Link to Youtube Video (visible only when JS is disabled)

We are excited to announce new enhancements to the Google Pay API that provide more flexibility and control over merchant initiated transactions (MIT). These updates enable developers to create seamless and secure payment experiences for a wider range of use cases, including subscriptions, deferred payments, and automatic reloads.

While the Google Pay API has always supported merchant initiated transactions, the existing specification was primarily designed for immediate customer initiated transactions (CIT). This meant that the merchant's intent for future charges couldn't be fully captured within the API request.

With the new enhancements, you can now clearly define the terms of future payments, providing transparency for users and ensuring smoother processing. The updates focus on three key MIT categories:

Recurring Transactions: Ideal for subscriptions or any scenario where a user is charged at regular intervals. You can specify details such as introductory periods, billing frequency (daily, weekly, monthly, yearly), fixed or variable amounts, and the duration of the recurrence.
Deferred Transactions: Useful for situations like hotel reservations or pre-orders where the payment is authorized upfront but charged at a single point in the future. You can now specify the exact date and time for the deferred charge.
Automatic Reload Transactions: Designed for services where a user's account balance is automatically topped up when it falls below a certain threshold. You can define the minimum balance trigger and the reload amount. Note: You are still responsible for charging the user according to the billing agreement yourself.

Benefits for Developers and Users

Improved Payment Success Rate: The tokenUpdateUrl allows you to receive notifications about the underlying payment credential, such as card expiry updates, helping to ensure uninterrupted service for recurring payments.
Improved Transparency: Users will have a clearer understanding of future payment schedules presented within the Google Pay interface.
Enhanced Flexibility: Support a wider variety of billing models beyond immediate payments.
Future-Proofing and Compliance: Google Pay facilitates the correct token type to ensure optimal transaction performance and meet future network mandates.

Key API Changes

To support these new use cases, we've introduced new objects within the PaymentDataRequest:

recurringTransactionInfo: To describe recurring payment schedules.
deferredTransactionInfo: To detail future one-time payments.
automaticReloadTransactionInfo: To configure balance-based reloads.

These new objects allow you to provide granular details about the intended future transactions. For example, within recurringTransactionInfo, you can specify:

introductoryPeriodInfo: Details about any trial or special introductory pricing.
recurrenceItems: An array describing one or more recurring periods, each with its own price, status, and duration.
price: The total amount for the entire recurrence, if fixed.
managementUrl: A link for the user to manage their recurring payment.
tokenUpdateUrl: A webhook URL for Google to send token lifecycle event notifications.

Example: Simple Monthly Subscription

json

{
  "apiVersion": 2,
  "apiVersionMinor": 0,
  "allowedPaymentMethods": [
    {
      "type": "CARD",
      // ... other card parameters
    }
  ],
  "recurringTransactionInfo": {
    "label": "Monthly Subscription",
    "transactionId": "SUB12345",
    "recurrenceItems": [
      {
        "label": "Regular Charge",
        "price": "9.99",
        "priceStatus": "FINAL",
        "recurrencePeriod": {
          "unit": "MONTH",
          "count": 1
        }
      }
    ],
    "managementUrl": "https://example.com/subscriptions",
    "tokenUpdateUrl": "https://example.com/api/token-updates"
  }
}

JSON

Copied

Getting Started

These new Merchant Initiated Transaction features are now available. We encourage you to review the updated API reference documentation for complete details on the new objects and properties.

We believe these enhancements will empower developers to build even more robust and user-friendly payment solutions with the Google Pay API.

posted in:

[](http://developers.googleblog.com/get-ready-for-google-io-livestream-schedule-revealed/)Previous

Next[](http://developers.googleblog.com/build-better-ai-agents-5-developer-tips-from-the-agent-bake-off/)

Related Posts

![Image 3: Introducing Wednesday Build Hour Cloud Tutorials Community Introducing Wednesday Build Hour MARCH 9, 2026](http://developers.googleblog.com/introducing-wednesday-build-hour/)![Image 4: Boost Training Goodput: How Continuous Checkpointing Optimizes Reliability in Orbax and MaxText AI Cloud Tutorials Case Studies Boost Training Goodput: How Continuous Checkpointing Optimizes Reliability in Orbax and MaxText MARCH 31, 2026](http://developers.googleblog.com/boost-training-goodput-how-continuous-checkpointing-optimizes-reliability-in-orbax-and-maxtext/)![Image 5: Google Pay inside sandboxed iframe for PCI DSS v4 compliance Pay Web How-To Guides Best Practices Google Pay inside sandboxed iframe for PCI DSS v4 compliance JUNE 10, 2025](http://developers.googleblog.com/google-pay-inside-sandboxed-iframe-for-pci-dss-v4-compliance/)![Image 6: Adding support for Google Pay within Android WebView Android Pay Mobile Web How-To Guides Announcements Adding support for Google Pay within Android WebView MAY 28, 2025](http://developers.googleblog.com/adding-support-for-google-pay-within-android-webview/)![Image 7: Jump to play: Building with Gemini & MediaPipe Mobile Web Case Studies How-To Guides Jump to play: Building with Gemini & MediaPipe MARCH 24, 2026](http://developers.googleblog.com/jump-to-play-building-with-gemini-mediapipe/)![Image 8: Bring state-of-the-art agentic skills to the edge with Gemma 4 Mobile Web Announcements Bring state-of-the-art agentic skills to the edge with Gemma 4 APRIL 2, 2026](http://developers.googleblog.com/bring-state-of-the-art-agentic-skills-to-the-edge-with-gemma-4/)

New enhancements for merchant initiated transactions with the Google Pay API

TL;DR · AI 摘要

核心要点