Testing custom SKU purchases costs real money

[GoogleCodeExporter]

STEPS TO REPRODUCE:
1. Attempt to test custom SKU purchases by making real purchases. As 
recommended by the documentation here: 
http://developer.android.com/google/play/billing/billing_testing.html#billing-te
sting-static 
2. Enter real payment details into the device and get charged money.
3. Lose internet connection.
4. Unable to refund the purchase.

EXPECTED OUTPUT:

Testing accounts should not be charged in the first place.

ACTUAL OUTPUT:

As I understand from the documentation and other posts:
http://stackoverflow.com/questions/15652117/android-in-app-billing-purchasing-re
al-items-with-test-accounts-without-spendin

money is actually taken out of my account.

For a large number of purchases this could cost me a significant amount of 
money.

Original issue reported on code.google.com by davidfo...@turbulenz.biz on 22 Apr 2013 at 11:42

[GoogleCodeExporter]

This also means that either:

- Testers have to enter their own card details.
- We have to give testers a company card and trust them to remember to refund 
the purchases (and not take the card details).

What happens if you charge an account with no funds? Will I get charged an 
unauthorized overdraft fee?

Original comment by davidfo...@turbulenz.biz on 22 Apr 2013 at 1:30

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

It looks like this has now been fixed. I now get a message saying that I won't 
be charged and there is no change listed in the transaction logs. Still need to 
wait for my bank statement to be completely sure though.

Original comment by davidfo...@turbulenz.biz on 24 Jun 2013 at 3:13

• Added labels: ****
• Removed labels: ****