Is it too soon to start implementing Google wallet?
Google wallet In-App Payments https://developers.google.com/in-app-payments/ developer documentation and tools are at the present at best broken, incomplete, and lacking relevant information. I feel I must write this in the hope that they take note and perhaps listen and change. Also because there isn't much developer information out there right now about this new payment system, so I hope this will generate positive activity.

The support points to a very quiet forum. https://groups.google.com/group/in-app-payments/topics When it could just point here where things are alive! ;)


Server side examples are documented only in part, directions point to use one of around five/six different libraries but directions completely end there.

One library link leads to a git hub stored library written in python wich 'apparently' you must somehow rewrite one of the main files inorder to use (again this has not been written by google wallet team any where in the docs). Its also very bissare that they would choose to only part write a bit of a php tutorial (a very popular, familiar, if not most widely used server side code) and instead write a main example in python when the first example on the page you see here https://developers.google.com/in-app-payments/docs/tutorial is Ruby...

The other amazing quality about the docs is the page where they list the various error codes that 'one' may come across while debugging. Its truly amazing that it's missing.

The errors may look something like this:
    Uh oh. There was a problem. 
    We couldn't complete your purchase because of a technical issue. 
    Details of the problem below: 
    Unfortunately, we could not confirm your purchase with the merchant's 
    server. Your order has been canceled. Please contact the merchant if 
    this problem continues.

But nothing is written about this error

nor this one:
Uh oh. There was a problem. 
We couldn't start your purchase because of a technical issue. 
Details of the problem below: 
Looks like there is an error in the setup for your purchase. Please 
contact the merchant with this error message: Expected 3 components in 
jwt: W29iamVjdCBPYmplY3Rd

nor any!

The tools for producing jwt are broken:
http://developers.google.com/in-app-payments/docs/jwtdecoder 
The decoder decodes the JWT header as this: 
{"alg":"HS256","typ":"JWT"} 
https://checkout.google.com/customer/gadget/inapp/demo.html 
But the encoder only encodes the JWT header as  this: 
{"alg":"HS256"}

At least there is one thing the docs have taught me, one very useful thing. "The In-App Payments API uses a JSON Web Token—or JWT, pronounced like the English word jot", 'jot', always good to to know how to pronounce these things when your down the pub 'wouldn't want to make fool of myself chatting up a girl pronouncing that one wrong now' huh looser!!

Hmmm... in conclusion I think that the funniest part of what I have to sa
Is it too soon to start implementing Google wallet?
===

Google wallet In-App Payments https://developers.google.com/in-app-payments/ developer documentation and tools are at the present at best broken, incomplete, and lacking relevant information. I feel I must write this in the hope that they take note and perhaps listen and change. Also because there isn't much developer information out there right now about this new payment system, so I hope this will generate positive activity.

The support points to a very quiet forum. https://groups.google.com/group/in-app-payments/topics When it could just point here where things are alive! ;)


Server side examples are documented only in part, directions point to use one of around five/six different libraries but directions completely end there.

One library link leads to a git hub stored library written in python wich 'apparently' you must somehow rewrite one of the main files inorder to use (again this has not been written by google wallet team any where in the docs). Its also very bissare that they would choose to only part write a bit of a php tutorial (a very popular, familiar, if not most widely used server side code) and instead write a main example in python when the first example on the page you see here https://developers.google.com/in-app-payments/docs/tutorial is Ruby...

The other amazing quality about the docs is the page where they list the various error codes that 'one' may come across while debugging. Its truly amazing that it's missing.

The errors may look something like this:
    Uh oh. There was a problem. 
    We couldn't complete your purchase because of a technical issue. 
    Details of the problem below: 
    Unfortunately, we could not confirm your purchase with the merchant's 
    server. Your order has been canceled. Please contact the merchant if 
    this problem continues.

But nothing is written about this error

nor this one:
Uh oh. There was a problem. 
We couldn't start your purchase because of a technical issue. 
Details of the problem below: 
Looks like there is an error in the setup for your purchase. Please 
contact the merchant with this error message: Expected 3 components in 
jwt: W29iamVjdCBPYmplY3Rd

nor any!

The tools for producing jwt are broken:
http://developers.google.com/in-app-payments/docs/jwtdecoder 
The decoder decodes the JWT header as this: 
{"alg":"HS256","typ":"JWT"} 
https://checkout.google.com/customer/gadget/inapp/demo.html 
But the encoder only encodes the JWT header as  this: 
{"alg":"HS256"}

At least there is one thing the docs have taught me, one very useful thing. "The In-App Payments API uses a JSON Web Token—or JWT, pronounced like the English word jot", 'jot', always good to to know how to pronounce these things when your down the pub 'wouldn't want to make fool of myself chatting up a girl pronouncing that one wrong now' huh looser!!

Hmmm... in conclusion I think that the funniest part of what I have to sa