New enhancements for merchant initiated transactions with the Google Pay API
- Google Developers Blog
Community/Events
Learn
Blog
YouTube
Search
Community/Events
Learn
Blog
YouTube
Pay
New enhancements for merchant initiated transactions with the Google Pay API
APRIL 15, 2026
Dominik Mengelt
Developer Relations Engineer
Payments
Kenneth Tu
Software Engineer
Kushagra Patel
Senior Product Manager
Share
Facebook
Twitter
LinkedIn
Mail
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
{
"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:
Pay
Mobile
Web
Tutorials
Announcements
Best Practices
Learn
Solve
Google Pay
google pay api
Previous
Next
Related Posts
Mobile
Web
Case Studies
Community
Bridging the Domain Gap: AI Race Coach built with Antigravity and Gemini
JULY 8, 2026
AI
Cloud
Tutorials
Announcements
ML Development in VS Code with Google Cloud Power: Workbench Extension Now Available
JULY 1, 2026
Pay
Google Pay
Mobile
Web
Announcements
Problem-Solving
Supercharge your integration workflow with the Google Pay & Wallet Developer MCP server
MAY 28, 2026
Pay
Web
How-To Guides
Best Practices
Google Pay inside sandboxed iframe for PCI DSS v4 compliance
JUNE 10, 2025
AI
Cloud
Tutorials
Announcements
We terminated a TPU mid-training and it recovered in seconds:  Introduction to elastic training with MaxText
JULY 6, 2026
Mobile
Web
Announcements
Best Practices
Enhance Security and Trust: New Session Metadata in Sign in with Google
JUNE 16, 2026
Connect
Blog
Bluesky
Instagram
LinkedIn
X (Twitter)
YouTube
Programs
Google Developer Program
Google Developer Groups
Google Developer Experts
Accelerators
Women Techmakers
Google Cloud & NVIDIA
Developer consoles
Google API Console
Google Cloud Platform Console
Google Play Console
Firebase Console
Actions on Google Console
Cast SDK Developer Console
Chrome Web Store Dashboard
Google Home Developer Console
Android
Chrome
Firebase
Google Cloud Platform
All products
Manage cookies
Terms
Privacy