search

demon99 / marketbilling

Automatically exported from code.google.com/p/marketbilling
0 stars 0 forks source link

Untraceable ORDER ID's: API returns order ID's in the old format (seems like it), while Wallet shows the new ones only #186

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Wasn't able to reproduce in-house.  About 20% of our orders coming from the 
field have the following format
9170416xxxxx5019212
instead of
12999763xxxxx4705758.139441xxxxx94837

We are able to match a few orders by timestamps. It's clear that some users 
ALWAYS have the order ID's in the old format, but on the Google Wallet page 
their orders have new order ID's. So, there is no way for us, having the old 
format order ID on our server, to find the user's order on Google Wallet (or 
the other way around).

This is a severe issue, because customer support cannot be provide to about 20% 
of the customers.

Is there a way to see both ID's or match them?

Original issue reported on code.google.com by o...@wevideo.com on 22 Apr 2014 at 9:42

GoogleCodeExporter commented 8 years ago 
I can provide the exact ID's if necessary

Original comment by o...@wevideo.com on 22 Apr 2014 at 9:45

GoogleCodeExporter commented 8 years ago 
Have you implemented receipt verification?

It is possible that these order ids are coming in from an older implementation 
of Google IAP (specifically version 2 and Google "Market").  If you only 
support API 8 and higher for your app,  then only implement version 3 in your 
application as Google IAP v3 and Google "Play" will support the newer 
transaction model.

Original comment by petetan...@gmail.com on 3 May 2014 at 7:36