5 ms·

We have an app for sale on the Android Market (which uses Google Checkout for transaction processing), and it seems like every week we have a support email clai

by kgrin 17y ago

We have an app for sale on the Android Market (which uses Google Checkout for transaction processing), and it seems like every week we have a support email claiming we charged them twice. We always apologize (even though it's not our fault), explain how the authorization charge works, assure them it'll be gone in a day, and point them to Google's help (bottom of): http://market.android.com/support/bin/answer.py?hl=en&answer=118685 http://market.android.com/support/bin/answer.py?hl=en&an... I do wonder why it's done that way on Checkout and not other payment systems, or why it seems more noticeable there; it seems to cause an awful lot of confusion.

Maro 17y ago
Even as a power-user, I can tell you it's confusing as hell. Can't you use PayPal?
- mbrubeck 17y ago
  The Android Market application uses only Google Checkout. There's no PayPal (or any other) option.
sachinag 17y ago
I'll tell you why: Google Checkout is doing the same PCI kludge that we do at Dawdle. We only do the $1 authorization charges, and we get people screaming at us all the time. Users hate being "charged" for stuff that they didn't purchase, and lots of people check their stuff online frequently. But it turns out that you can't be PCI compliant if you store credit cards in distributed virtual servers (it violates the physical access tenet), so they can't store CCs. So you have to do an auth and then a reference transaction off of the auth.