Release notes

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

2019-10

• Added Brazil debit and credit combo card support. See Card parameters object reference for more details.

2019-09

• Added NCCC, eCard, and BlueGate (NTTData) to the list of participating processors. Updated the URL for Worldpay.
• Revamped the "Reference" tab to improve user experience.

2019-08

• Added PayAnyWay, Paragon Payment Solutions, and Paylane to the list of participating processors.
• Added new images to the UX best practices guide.
• Added instructions to customize your API integration for SCA compliance.

2019-07

• Added Cathay United Bank, Chase Merchant Services (formerly Chase Paymentech), LogPay, Nuvei, Payler, Paymetric, and RBS to the list of participating processors.
• Added new, optional steps to the Web tutorial for authorized payments and dynamic price updates.

2019-05

• Added Dynamic Price Updates for web integrations to support shipping address and shipping option changes for purchases. Dynamic Price Updates is coming soon for Android.

2019-04

• Added PayPal as a supported payment method. For more details, see object reference.
• Added Computop, MyCheck, Sipay, TPay.com, and Wirecard to the list of supported gateways.

2019-03

• Added iQmetrix, Portmone, and Vindicia to the list of supported gateways.

2019-02

• Added a section called Test with sample tokens that provides information about encryption and sample payloads returned when a DIRECT integration is performed.
• Added Frequently asked questions about Google Pay online.
• Added Gestpay, iPay88, Multicarta, Square, and WayForPay to the list of supported gateways.

2019-01

• 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)
• Updated JSON Object Reference: PaymentMethodTokenizationSpecification now includes examples for supported payment processors: Alfa-Bank, Blue Media, BlueSnap, Chase Merchant Services (formerly Chase Paymentech), CloudPayments, GoPay, HiTrust, Lyra, Mastercard Payment Gateway Services (MPGS), Money.Mail.Ru, Newebpay

2018-12

• Added Arabic to the "Buy with Google Pay" resource for button asset localization.
• Launched ECv2 for DIRECT integrations. ECv2 is an updated cryptography protocol that allows merchants to store a static, long living, Google signing key that only needs to be updated every 10 years.
  Note: If you've implemented support for ECv1, your implementation should continue to work. If you wish to upgrade to ECv2 in production, notify your Google contact to verify your implementation.
• Updated the Tink library to support ECv2 payloads as of version 1.1.0. See the Tink release notes for more information.

2018-11

• Updated the Web Brand guidelines. Developers can no longer download and use the Google Pay logo, and must now only use the Google Pay mark.
• Added NMI to the list of supported gateways.

2018-10

• Added instructions for Key rotation for DIRECT integrations.

2018-07

• Released a new version of Google Pay API, APIv2.
  Note: Apps that have integrated wtih APIv1 should continue to work.