Learn about the new merchant initiated transactions (MITs) available with Google Pay, designed to enhance your checkout experiences. We’ll dive into the mechanics of automatic reloads, deferred transactions, and recurring payments, highlighting API changes and lifecycle notifications. Developers will find clear explanations and an example of implementing a recurring transaction, ensuring seamless payment integration for their users.

Connect with us:

Join the conversation in the #payments channel on Discord → https://goo.gle/payments-dev-community
Watch more Live Google Pay integrations on Android → https://goo.gle/live-google-pay 
Follow @GooglePayDevs on X for more content like this → https://goo.gle/GooglePayDevs  
Subscribe to Google for Developers → https://goo.gle/developers  

Get support: 

For assistance with your implementation, create a support ticket from the Google Pay & Wallet Console → https://goo.gle/4hSy658 

Speaker: Jose Ugia
Products Mentioned: Google Pay

Google for Developers

Google Pay now supports merchant-initiated transactions (MITs) including recurring, deferred, and automatic reload use cases. The Google Pay API has been extended with three new transaction info objects: recurring, deferred, and automatic reload transaction info, all backwards compatible with the existing API. When a user selects a card, Google Pay returns a merchant token ID within an encrypted payload, which payment service providers store for future lifecycle management. A walkthrough example shows how to configure a monthly recurring subscription at $9.99 using the recurring transaction info object. Part two of this series will cover lifecycle notifications for credential changes.

How to implement Google Pay merchant-initiated transactions