API release notes

This page lists the major changes in each release of Google Pay API for Android. The release notes are ordered and identified by date, and they include descriptions of the changes.

July 2024

The PayButton API now offers a personalization feature that displays the user's card network (e.g., Visa, Mastercard) and the last four digits of their card on the following Google Pay payment buttons:

Button Type	Before	After
BUY
PAY

This enhancement is available only to users who have an eligible card linked to their Google Pay account.

February 2024

This release deprecates the AutoResolveHelper#resolveTask(Task, Activity, int) method. Use the new Activity Result API contracts introduced in this release instead.

Released version 19.3.0 of the Play Services Wallet library, which adds support for the new Activity Result API on Android with the introduction of new contracts to handle loadPaymentData task results. Get started with the API by creating activity result launchers using the GetPaymentData and GetPaymentDataResult contracts.

December 2023

Beta release. Share feedback through the issue tracker.

Released version 19.3.0-beta01 of the Play Services Wallet library, which adds support for the new Activity Result API on Android with the introduction of new contracts to handle loadPaymentData task results. Get started with the API by creating activity result launchers using the GetPaymentData and GetPaymentDataResult contracts.

This version deprecates the AutoResolveHelper#resolveTask(Task, Activity, int) method. Use the new Activity Result API contracts introduced in this release instead.

September 2023

Released version 19.2.1 of the Play Services Wallet library, which updates the PayButton API to fall back to a static button asset for users with Google Play services version less than 23.21.0.

June 2023

Upgrades the PayButton API on Android from beta to stable, while including changes:

Button text with the same size as the "GPay" logo.
Adjustable button margins to the minimum and maximum button heights.
Configurable corner radius to match your UI design.

April 2023

Beta:

• Added a PayButton API for Android to generate Google Pay payment buttons styled with the latest Google Pay branding. See developer documentation for instructions to update to the new payment button
.

February 2023

Beta:

• Added a Gateway Test Cards to facilitate end-to-end testing. Merchants can select one of these cards to get a token they can send to a processor's test environment and recieve appropriate responses. Refer to the test card suite documentation.

February 2021

• Added AsiaBill, bePaid, ConnexPay, EpicPay, Mixplat, Netopia, PaymentFusion, Pikassa, and PSCB to the list of participating processors.
• Added the new Google Pay Mark asset to all of the examples in UX best practices.

January 2021

• Added CardKnox, Cloud9 Payment Gateway (C9PG), Corefy, Pay.nl, and ReePay to the list of participating processors.
• Added the new Google Pay Mark asset to Brand guidelines.

December 2020

• Added ЮKassa, IMOJE, Modulbank, PayNearMe, QIWI, and QualPay to the list of participating processors.

November 2020

• Added AllPayments, CellPoint Mobile, Evopay, and Primer to the list of participating processors.
• Added instructions to configure the Google Pay API to comply with Strong Customer Authentication (SCA) to SCA and Google Pay API.

October 2020

• Added InPlat, IntellectMoney, Rebilly, TAS Link, and UAPay to the list of participating processors.
• Added instructions on how to use our TEST merchant ID value to test decryption with the TINK library to Payment data cryptography.

September 2020

• Added Alfa-Bank Ukraine, AsiaPay, Bizzon, Credorax, and Payload to the list of participating processors.
• Added a video that explains the Google Pay API in Brazilian Portuguese to Overview.
• Added sample code and examples in the Kotlin programming language to Tutorial.
• Added instructions to access our test card suite in the TEST environment to Test card suite.

June 2020

• Added ConcordPay, Payfacto, Radial to the list of participating processors.

May 2020

• Added Kassa to the list of participating processors.
• Added payment flow figures that explain the relationship between Merchants, Google, and Payment Processors to Overview.
• Added more information about the isReadytoPay client reference to Reference.

April 2020

• Added FreedomPay, Paymo, Oceanpayment, and PayU India to the list of participating processors.

March 2020

• Added 2C2P, Windcave, dLocal, and Paymentwall to the list of participating processors.
• Added gateway parameter values to Tutorial.
• Added the allowedCreditCards property to the CardParameters request object that allows merchants to filter out credit card transactions to Reference.
• Added instructions to gain production access using registering with Google Pay & Wallet Console to Request production access.
• Added instructions to contact support for onboarding and technical questions using Google Pay & Wallet Console to How to get help and Troubleshooting.

February 2020

• Added PayOnline to the list of participating processors.

January 2020

• Added Paygent, Judopay, Paymark, e-SiTef - Software Express, and noon payments to the list of participating processors.
• Added a summary view to Brand guidelines.

December 2019

• Added Billing Systems, Spreedly, theMAP, and APPEX to the list of participating processors.
• Added DIRECT integration requirements to Overview.

November 2019

• Added Tranzzo, MOBI.Money, Suntech, and Best2Pay to the list of participating processors.
• Added OpenCart to the list of participating platforms.

October 2019

• Added instructions to enable Brazil debit and credit combo card support in the allowedCardNetworks property for the CardParameters request object to Reference.

September 2019

• Added NCCC, eCard, and BlueGate (NTTData) to the list of participating processors.

August 2019

• Added PayAnyWay, Paragon Payment Solutions, and Paylane to the list of participating processors.
• Removed the merchantId property from the example MerchantInfo object.
• Added CheckoutActivity.java to replace YourActivity.java to Tutorial.
• Added PaymentsUtil.java to replace GooglePay.java to Tutorial.
• Added new supplemental images to UX best practices.
• Added instructions to customize your integration for SCA compliance to Strong Customer Authentication.

July 2019

• Added Cathay United Bank, Chase Merchant Services (formerly Chase Paymentech), LogPay, Nuvei, Payler, Paymetric, and RBS to the list of participating processors.

June 2019

• Added CardConnect, eGHL, and LogPay to the list of participating processors.
• Added a diverse set of sample token examples to Test with sample tokens.
• Added more information and examples to UX best practices.
• Added new allowedCardNetworks option, INTERAC, to the Tutorial.

May 2019

• Added Braspag, Ecard, Redsys, and Worldnet to the list of participating processors.

April 2019

• Added Computop, MyCheck, Sipay, TPay.com, and Wirecard to the list of supported gateways.
• Added PayPal as a supported payment method in the type property for the PaymentMethod request object to Reference.

March 2019

• Added iQmetrix, Portmone, and Vindicia to the list of participating processors.

February 2019

• Added Gestpay, iPay88, MultiCarta, Square, and WayForPay to the list of participating processors.
• Added more information about encryption and sample payloads returned with a DIRECT integration to Test with sample tokens.
• Added frequently asked product and troubleshooting questions and answers to FAQ.

January 2019

• Added Assist, GMO Payment Gateway, and Moneris to the list of supported gateways.

• Added localized content in the following languages:

  • Russian
  • Portuguese (Brazilian)
  • Japanese
  • Polish
  • Chinese (Traditional)
• Added examples for participating processors to the gateway table and gatewayMerchantId properties for the TokenizationSpecification Request Object to Reference.

December 2018

• Added Arabic for the "Buy with Google Pay" resource to Brand guidelines.
• Added information about ECv2, an updated cryptography protocol that allows merchants to store a static, long-term, Google signing key that only needs to be updated every 10 years, for DIRECT integrations to Payment data cryptography.
  Note: If you've implemented support for ECv1, your implementation should continue to work. If you want to upgrade to ECv2 in production, notify your Google contact to verify your implementation.
• Added information about ECv2 payload support for the Tink Library version 1.1.0 to Tink release notes.

November 2018

• Added NMI to the list of participating processors.
• Added more information about the Google Pay mark to Brand guidelines.

October 2018

• Added instructions for key rotation for DIRECT integrations to Payment data cryptography.

September 2018

• Added information about APIv2 to GitHub code sample.

August 2018

• Added information about the new version of Google Pay API, APIv2, to Update to latest version.
  Note: Apps that have integrated with APIv1 should continue to work.