Google is retiring its Google Wallet for Digital Goods API and is encouraging users to go find other solutions. It will be retired on March 2, 2015, and Google has said that there will be no replacement product.
The API was intended for selling digital goods via in-browser desktop and mobile Web apps. Google's move, however, only applies to Web developers accepting payments on their own sites. "It does not affect our other Wallet offerings," the company said. Services not affected include Instant Buy, the Google Wallet App, in-app payment services like Play In-app Billing, and Google marketplaces like Play Store. "If you don't have your own payment processing, you will need to transition to an alternate solution and remove calls to our APIs before March 2, 2015."
Believing Google Wallet merchants know their buyers best, Google encourages users to research payment processing solutions on their own. The company initially launched browser-based digital goods payments in 2011; the intent with was to make it simple for game developers to accept payments for digital goods on their desktop gaming systems. "The industry has matured a lot since then, providing a number of alternative payment solutions to choose from."
Users of the API must remove client-side integration code, server-side code generating JWT (Java Web Token), and server-side code handling the postback.
Google Wallet buyers will not be proactively notified. "Keep in mind that if you do not remove your integration before March 2, 2015, your buyers will get 404 errors upon checking out with Google Wallet for digital goods API." Earlier this year, Google added PayPal as a payment option on Google Play, which previously was known as Android Market.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.