Technical Trigger
The Google Pay API has introduced new objects within the PaymentDataRequest, including recurringTransactionInfo, deferredTransactionInfo, and automaticReloadTransactionInfo. These objects allow developers to provide granular details about the intended future transactions, such as introductory periods, billing frequency, and reload amounts.
Developer / Implementation Hook
Developers can now use the new objects to create more flexible and secure payment experiences. For example, they can specify the recurrenceItems array to describe one or more recurring periods, each with its own price, status, and duration. Additionally, the tokenUpdateUrl property allows developers to receive notifications about the underlying payment credential, such as card expiry updates, helping to ensure uninterrupted service for recurring payments.
The Structural Shift
The Google Pay API is moving from supporting only immediate customer-initiated transactions to also supporting merchant-initiated transactions with more flexibility and control.
Early Warning — Act Before Mainstream
To take advantage of this change, developers can: 1. Review the updated API reference documentation to understand the new objects and properties. 2. Implement the recurringTransactionInfo object to support recurring transactions, such as subscriptions. 3. Use the tokenUpdateUrl property to receive notifications about payment credential updates and ensure uninterrupted service for recurring payments.