                                                                                                                                                                                                                                                                
Date: Tue, 2 Oct 2012 15:50:40 -0700 (PDT)
From: spocky12 <spock...@gmail.com>
To: android-developers@googlegroups.com
Message-Id: <e2217f20-0571-4d12-bc57-7e3648be9f95@googlegroups.com>
In-Reply-To: <7050451a-4396-44f3-8656-ad94e7b15555@googlegroups.com>
References: <7050451a-4396-44f3-8656-ad94e7b15555@googlegroups.com>
Subject: Re: Google cancelled this order. Reason: Other
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_749_10484616.1349218240853"

------=_Part_749_10484616.1349218240853
Content-Type: multipart/alternative; 
	boundary="----=_Part_750_20632942.1349218240853"

------=_Part_750_20632942.1349218240853
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

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. 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 ?


------=_Part_750_20632942.1349218240853
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

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 regard=
ing this. My app uses in-app billing too.<div><br></div><div>I used to have=
 approximately 15% of canceled orders due to authorization refused and abou=
t 0 to 1% of "others" each day.</div><div>Since last saturday, "authorizati=
on refused"&nbsp;didn't change but "others" is now about 12% of my commands=
 :(<br></div><div><br></div><div>"Authorization refused" was not so problem=
atic because it's often related to bad account information. Most users usua=
lly corrected their account information and managed to finalize the command=
. This is unfortunately not true with "reason: other" as it seems that almo=
st 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).</div><div><br>=
</div><div>@Nathan : I can't confirm about the "0" account age and didn't f=
ind any specific pattern.</div><div><br></div><div>Can anybody confirm that=
 removing/adding back the credit card is a successful workaround ?</div><di=
v><br></div><div><br></div>
------=_Part_750_20632942.1349218240853--

------=_Part_749_10484616.1349218240853--