[FR] getSkuDetails() should have a flag to return prices w/ ISO 4217 currency code instead of currency symbol

[GoogleCodeExporter]

We have realized that in the In-App billing APIv3 when you retrieve the 
products info, google gives you the item price with the currency symbol.

In our case, we are storing all the financial transactions in a database for 
internal analysis and with this info we cannot differentiate for example 
between USD and CAD because both shares the same symbol. 

We request to change the answer for this method and include the ISO 4217 code 
on the item price instead of the currency symbol. It is less ambiguous and it 
allows you to get the currency symbol from the Currency Java Class.

Original issue reported on code.google.com by djsatano...@gmail.com on 11 Jan 2013 at 7:30

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

#49 @nospamx24 : To test in other currency you must change the Billing address 
in your Credit cards in Google Wallet to the one that you want to see in your 
test.

Probably the bug is still not fixed, because I also receive different prices 
(RUB/USD):
{... 
"price":"31,38 руб.","price_currency_code":"USD","price_amount_micros":99000
0, ...}

Original comment by alexs...@gmail.com on 12 Sep 2013 at 2:06

[GoogleCodeExporter]

the price is NOT the actual price which user would be paying for that IAP. it 
is the list price from the seller's account. Please provide the localized 
currency code and amount. I dont understand why I can get the accurate price 
back from google play store but NOT with the getSKUDetail api. This is not 
good. Please fix this as soon as possible. 

Original comment by weist...@gmail.com on 8 Oct 2013 at 6:11

[GoogleCodeExporter]

I'm really curious whether guys from In App Billing ever read this: 
https://developers.google.com/analytics/devguides/collection/android/v3/ecommerc
e?hl=en#implementation

You are the same company but connect meaningfully your two (very closely 
related) services is almost impossible.

Original comment by tom.huba...@gmail.com on 11 Oct 2013 at 9:02

[GoogleCodeExporter]

So what is the verdict? will "price_currency_code" and "price_amount_micros" 
reflect the currency that the user submits the payment in? This is the 
*desired* behavior for me.
The currency that the price was set in is fairly worthless-- I know that 
already!

Original comment by kevin.c....@gmail.com on 26 Nov 2013 at 7:37

[GoogleCodeExporter]

Another easy way to solve this would be to just add the data we need, to
the Google Play Purchase API responses... Hello Google?! Hire me for an
hour or two or do _whatever you have to do_ to fix this stupid flaw.

/ Martin

Original comment by martino...@gmail.com on 27 Nov 2013 at 12:09

[GoogleCodeExporter]

Question: In my app this might not be a huge problem (though it will mess up my 
statistics!). I want to print the price of the item in the local currency, but 
for various reasons I can't print unicode characters. Will the getSkuDetails() 
"price" entry ever return Unicode? For example, how will the Euro symbol appear?

Original comment by lalitkum...@gmail.com on 4 Dec 2013 at 4:35

[GoogleCodeExporter]

Can we get another official status update on this?  It's been months...

As mentioned above in the thread, two new keys are now showing up in the sku 
details (price_currency_code and price_amount_micros) which seems to be getting 
at what we're asking for here.  But the usefulness hinges on the values being 
returned in the actual currency that the transaction would take place in which 
apparently is not the case.

Bueller? Bueller?

Original comment by jus...@rowshambow.com on 10 Dec 2013 at 2:49

[GoogleCodeExporter]

One year after the first report, is there still no solution to retrieve the 
amount and the currency of the transaction ? 

Original comment by t...@beemoov.com on 6 Feb 2014 at 3:47

[GoogleCodeExporter]

We are in desperate need for this feature for security purposes on our app and 
cannot release until this feature has been added. Whats going on here?

Original comment by theappsf...@gmail.com on 20 Feb 2014 at 3:15

[GoogleCodeExporter]

Any update or ETA on this ?

Original comment by sandeep....@mutualmobile.com on 18 Mar 2014 at 7:06

[GoogleCodeExporter]

This issue is over a year old and still not fix :( and no ETA?

Original comment by Eric.Lab...@gmail.com on 19 Mar 2014 at 5:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It seems a bit strange that there is no method to get the standard 
currency-code for my in-app purchase items (like USD,CAD etc.) while the 
PlayStore dialog has that info when the user has to proceed to payment.

Original comment by shantan...@gmail.com on 30 Mar 2014 at 1:55

[GoogleCodeExporter]

Any news on this? It would be really useful to get this data, same thing we are 
getting right now but with an extra currency_code attribute

Original comment by sergio.m...@swrve.com on 31 Mar 2014 at 3:53

[GoogleCodeExporter]

I've been on this thread for more than a year, I don't believe anyone from 
Google has ever commented and obviously the issue is not fixed.

I have a serious question (not being sarcastic) -- does anyone know if this 
site is actually used by Google? My impression is Android's support staff pay 
more attention to stackoverflow.

Original comment by m...@lootworks.com on 31 Mar 2014 at 4:33

[GoogleCodeExporter]

This is sad! There is still no ETA! 

Original comment by omer.sa...@gmail.com on 9 Jul 2014 at 11:36

[GoogleCodeExporter]

This functionality is imperative for proper revenue tracking. Please adjust the 
Priority to High. Anybody who needs this functionality, please comment wrt 
priority for your need.

Original comment by peter.ya...@gmail.com on 24 Jul 2014 at 4:45

[GoogleCodeExporter]

Piling on with Peter.  We process many millions in international revenue.  
Millions of WHAT?  Good question and one we can't answer reliably due to this 
shortcoming.

Original comment by sloan.lo...@gmail.com on 24 Jul 2014 at 8:51

[GoogleCodeExporter]

I'm speechless. Sorry everyone, tbh, it seems they just won't fix it...?!

It's is of course a serious crime not to be able to do the book-keeping 
properly. We can neither calculate VAT figures, nor revenue etc and *Google is 
just blatantly ignoring this fact*!

I guess in the end the tax authorities will prohibit the use of Google In-App 
Payments for sales (or possibly prosecute Google for forcing us into this by 
being the largest app market and allowing their own "solution" only?)

***HIGH PRIORITY IS URGED***
***THIS ISSUE MUST BE FIXED IMMEDIATELY***

Original comment by martino...@gmail.com on 24 Jul 2014 at 10:58

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Well, 'price_currency_code' and 'price_amount_micros' were mentioned in
this thread before, around Dec 2013: It turned out they did NOT give us the
values we need, because the implementation (at that time) only gave us the
price and currency of the merchant account, which is basically meaningless
information (since we already know what prices we gave our products though
the dev console).
The real issue is that the system don't (didn't?) give us the information
about what has actually been charged from the end-customers, i.e. the price
and currency localized to _them_.

I got confirmed last week from a contact within Google that the awaited
functionality does not exist yet. It also doesn't seem very likely they
would suddenly change the behavior of a method using the same keys as
before, but I would be happy to be proven wrong.

2014-08-18 18:04 GMT+02:00 <marketbilling@googlecode.com>:

Original comment by martino...@gmail.com on 19 Aug 2014 at 7:10

[GoogleCodeExporter]

http://developer.android.com/google/play/billing/billing_reference.html#getSkuDe
tails

'price_currency_code' and 'price_amount_micros' has been added in this 
document. Dose it work?

Original comment by mizushim...@dena.jp on 22 Aug 2014 at 1:24

[GoogleCodeExporter]

It works! After all this time...

Original comment by Syntax...@gmail.com on 22 Aug 2014 at 2:10

[GoogleCodeExporter]

I have tested it myself and confirmed that it works! :)

Original comment by alexjloc...@gmail.com on 22 Aug 2014 at 2:12

[GoogleCodeExporter]

Please see above comments. It sounds like the price_currency_code and
price_amount_micros fields only return information on the currency set by
the merchant account, not the actual currency of the transaction.

Original comment by fadoo...@gmail.com on 22 Aug 2014 at 3:30

[GoogleCodeExporter]

Reply to #77:

I have read those comments and have tested it myself with multiple currencies 
and have confirmed that prices are no longer only returned in the currency set 
by the merchant account. The price is now returned in the currency of the 
actual transaction. 

Original comment by alexjloc...@gmail.com on 22 Aug 2014 at 3:34

[GoogleCodeExporter]

That's some good news! I'm very happy to read your confirmations, but I
guess I need to see it with my own eyes to truly believe it.. ;) I'll get
back when I've had tested it thoroughly myself.

Have a great weekend everybody.

2014-08-22 17:34 GMT+02:00 <marketbilling@googlecode.com>:

Original comment by martino...@gmail.com on 22 Aug 2014 at 8:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

So while it's great that we have this new field it doesn't solve the problem of 
validations. If we are comparing prices assigned on a company server to the 
google prices to detect invalid products then this would cause failures in 
every user that doesn't use the same currency as the native currency of the 
developers, in my case US dollar.

Am I correct in understanding that this "price_amount_micros" will return a 
number who's value is the same currency as the user's wallet?

Original comment by ka...@agilemd.com on 28 Aug 2014 at 6:37

[GoogleCodeExporter]

To #81, I've noticed that the "double" type values provided in SKUDetails refer 
only to the non-localized price set in Google Play, i.e. the one with the 
"Default price" label in the "In-app Products" section in the Google Play 
console. So, for these numeric (double) values, the values in the "Local 
prices" list are ignored, which are the ones the users will see from their 
Google Wallet service...

Original comment by christ...@busuu.com on 2 Sep 2014 at 9:26

[GoogleCodeExporter]

@#82 Thank you! I was worried that we price validation wasn't going to work 
with out of merchant currency. Saved me a lot of headache :)

Original comment by ka...@agilemd.com on 2 Sep 2014 at 5:53

[GoogleCodeExporter]

This issue has been reported as officially fixed by the Play team.

Original comment by trevorjohns@google.com on 6 Nov 2014 at 6:06

• Changed state: Fixed