Before Google Wallet, the numbering system for Google Order ID used the 
following format:

12345678901234567890.G.123456789012345

Where the Google Order Id passed in the in-app billing system is the 15 
digit number after the G.

This is the only identification information that was available to the user 
and the developer. It was easy to instruct the user to use this number to 
recover their premium access for unmanaged items by entering in their 
Google Order Id in a form inside the app. It worked flawlessly. We have the 
order number in our server and it's big enough that it's impossible to 
guess. No extra security or other means of identification are required, nor 
do we know who the user is. This has been a completely automated process up 
to now.

Google Wallet changed that. Instead, a new 50+ digit number is the order 
number and it isn't related nor searchable in the Google checkout developer 
console.

Example of the new format:

12345678901234567890123.07247902161068202818.1326318464.2

Now, a user cannot automatically recover their premium status when reseting 
or purchasing a new device. We have no way to tie this new number with 
their original purchase. The only way a user can recover their premium 
status now is for them to forward their invoice to us and we have to 
manually search by the date and time of the order to find it.

This is way too much work for a couple of dollars. It takes about ten 
minutes to just find the right order number. Once we do find the original 
order, we have to copy and paste the Google Order Id into an e-mail and the 
user has to do the automated process. 

I've filed a "bug" report with Google Checkout but as usual, that just 
disappeared into the ether. This is a real big problem for us as we get 
about 200 of these changes per month. That's 2,000 minutes of time to 
handle this per month, up from zero when it was automated.

The solution to this problem is incredibly simple. Either Google has to 
forward the new order number to us as part of the purchase information from 
the in-app billing api or (even simpler) pass the original Google Order Id 
to the user.

Has anyone else seen this problem?

-John Coryat


-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Reply via email to