I have implemented subscriptions in my app and have the product listed on my developer Console. Test purchases are not currently supported for subscription in-app items so I need to test using a real credit card - no problem for me. Also I'm testing on a phone other than my developer phone because we are not allowed to test on our developer phone (can you make it any harder Google?) Previously I successfully tested consumable products using this phone using a bogus -0999 credit card and this worked well.
Now when I try to buy a subscription, Google Play wants to use the -0999 credit card and it fails to be approved. So I would like to change it to use a real credit card but I can't figure out how to do the. How can I test with a real credit card?
Thanks,
Dean
When you were testing your consumables, Google Play put that phoney credit card number into your Google Wallet Account. Going into Google Wallet, deleting the phoney CC and entering a valid CC solves the problem.
Related
I don't want to input my credit card for Google Play test. Is there any way I can do this like what we did in iOS IAP testing?
Or is it possible to create Redeem code for testing?
The reason is I'm not feeling comfortable to add my Credit Card number. One of my friends once was stolen about $600 through Google wallet (although Google paid him back later).
Another bad case is my another friend received the bill from his Credit Card company to pay for the testing of Google Play's In App Billing although Google said it's safe to do so.(He told me he even saw "This is a test order, you will not be charged" when he did testing)
Thanks
I think he was talking about the Google Play's In App Billing. So I don't think it's possible to use sandbox for testing.
Follow the documentation here. It will give you access to a group that will automatically input test cards into your current google account you're using within the sandbox https://developers.google.com/pay/api/android/guides/resources/test-card-suite
I'm using a test google checkout account I created using a credit card number from here: https://developers.google.com/checkout/developer/Google_Checkout_Basic_HTML_Sandbox
When I try to buy something in app from an unpublished app (the item itself is published) using the test account it requests I add a credit card, if I go to the drop down to select an existing card it shows the card from the aforementioned link I had added but says 'purchase currency is not supported'.
From http://mobility.forumsee.com/a/m/s/p12-22971-0373237--solved-purchase-currency-not-supported-error-when-buying-app.html
edit: AMEX works on Google Play only for purchases denominated in USD.
==
I had the same problem, switching to AMEX to VISA and that worked.
I'm developing a simple in-app billing library. It works with static responses from google, but now I'd like to test this lib with real in-app products.
I have created a test account and I'm trying to buy a product, but google Play is asking me for a credit card. Is there any way to test in-app billing without using a real credit card (a sandbox environment, fake credit card, etc)?
I have read here that the only way to test this is using a real credit card with a test account (so you don't have to pay google taxes) and once you have bought the product, refund it again, but it seems not to be a very 'developer-friendly' way.
Thanks.
Nope it absolutely SUCKS
You have to use a real credit card, then go into Google Play , select View Merchant Account and hit the individual order then refund to get your money back.
sorry!
As of today (or yesterday) Google has finally allowed "sandbox" testing of in app purchases, it goes through all the steps of an in app purchase except the actual charging of the credit card.
Although you will probobly have to wait for the cancelations/refunds like you did before.
More info here and here
Got this info from my developers console.
... and to add to Blundell's answer, it will take close to 6 hrs for refund to be posted, and then you'll probably want to give it another 6 hours before attempting the purchase.... or else.... Or else, what? Oh, I don't know, something like the "you already own this item" bug/glitch/bane of my existence
You can test in-app purchase subscription using testing accounts. For reference please go through the link-
You may use sandbox testing by adding you testers account to play console.
Go to the play console main screen--> setting--> search for license testers--> add your testers email-id there.
Then go to your app release-> go for your beta/alpha release.
Tap on manage testers and share opt-in URL with testers to accept an invite.
https://cheesecakelabs.com/blog/google-play-iap-first-setup-test-sandbox/
Inching slowly (but methodically) towards my first implementation of In-app Billing, I reached the point in which I can actually run the market billing sample application: The app is signed and uploaded to the AM, the "product list" has been created per the instructions and a test account has been set in both Google and the phone.
But when I proceed (successfully) with a purchase, despite selecting the test account on the AM, I am prompted to confirm the purchase with my real gmail account, to which my real credit card is linked.
When testing PayPal, for example, one can create test accounts, too, with fake CC numbers, to test freely w/o burdening the real CC system.
Is this available (or possible) for In-app Billing development & testing, too?
Update: I tested this on a different device, having only the test account set, and sure enough the Android Market behaves erroneously, responding the following error message:
The item you were attempting to purchase could not be found.
I know that the item is there and that it is set up properly in the Android Market because this error is never issued on the device with the real account with the CC number (there I receive a perfect behavior with the masked CC number, the Total and an Accept & buy button). Why does Google write such misleading error messages?
Update: I found this incredible thread, which seems to partially answer my question. Unless something new has been introduced by Google since then.
You have to use a real credit card. However, you can always refund your test purchases!
Note that you'll have to make the purchases from a test account that's separate from your developer account, since Google Checkout doesn't allow an account to buy from itself.
Test accounts are useful when you upload your application as a draft application,not published.Then using test account you can do even purchase of unpublished application.Hope this helps.
I've followed the steps to upload the In-App Billing Sample App as an unpublished, draft app on the Market for testing purposes. I have my google account set up as a Test Account under my Market credentials and was wondering if my credit card will actually be charged when I purchase the potion or sword?
I know that I should refund the purchase from my Google Checkout Merchant account but will it actually charge my card if I don't?
Okay, after actually trying it, my card is really charged. Just an fyi for anybody that was wondering. The four android.test.xxx product IDs are the only test transactions that are possible that won't use your real account info and card.