Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Android Developers
Home
+ new post
About this group
Join this group
Message from discussion Google cancelled this order. Reason: Other
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Kostya Vasilyev  
View profile  
 More options Oct 2 2012, 7:09 pm
From: Kostya Vasilyev <kmans...@gmail.com>
Date: Wed, 3 Oct 2012 03:03:48 +0400
Local: Tues, Oct 2 2012 7:03 pm
Subject: Re: [android-developers] Re: Google cancelled this order. Reason: Other
Print | View thread | Show original | Report this message | Find messages by this author

2012/10/3 spocky12 <spock...@gmail.com>

> I was about to post about the exact same problem when I saw this. Good
> news is I'm not alone. Bad news is we don't have any kind of information
> regarding this.

This is the best we have at this time, I believe:

http://support.google.com/googleplay/android-developer/bin/static.py?...


Purchasing Issues
Problems with in-app billing and licensing server
We are aware the reports regarding in-app billing and Google licensing
server (LVL) issues, and are working on resolving these problems. Please
stay tuned and thank you for your patience.

Report this issue

<<

> My app uses in-app billing too.

> I used to have approximately 15% of canceled orders due to authorization
> refused and about 0 to 1% of "others" each day.
> Since last saturday, "authorization refused" didn't change but "others" is
> now about 12% of my commands :(

> "Authorization refused" was not so problematic because it's often related
> to bad account information. Most users usually corrected their account
> information and managed to finalize the command. This is unfortunately not
> true with "reason: other" as it seems that almost every user in that case
> can't manage to buy the app, no matter how many tries they make. This means
> I'm losing 12% of commands each day (hopefully users will try again in a
> few hours/days and won't abandon).

> @Nathan : I can't confirm about the "0" account age and didn't find any
> specific pattern.

> Can anybody confirm that removing/adding back the credit card is a
> successful workaround ?

Since I was the one who mentioned that, I can confirm that sometimes it
works and sometimes it doesn't, based on my limited interaction with users
regarding failed orders (not everyone writes, and I usually set up a
license in my own, back-up system, when Google's fails).

Large scale, cloud-based computing sure is fun.

Now imagine this in a different setting -- "Sorry Captain, the life support
systems have shut down due to an unexpected thread deadlock".

HAL 9000 wasn't malicious, just buggy.

-- K


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google